問題一覧
1
describes the high-level entities in an organization and the relationship between these entities
Enterprise Data Model
2
What are the example of Enterprise Data Model (7)
First step in database development, Specifies scope and general content, Overall picture of organizational data at high level of abstraction, Entity-relationship diagram, Business rules, Relationships between entities, Descriptions of entity types
3
Conceptual blueprint for organization’s desired information systems structure
Information Systems Architecture (ISA)
4
- A data-oriented methodology to create and maintain information systems
Information Engineering
5
a generic IS planning methodology for obtaining a broad understanding of the IS needed by the entire organization
Top-down planning
6
There are Four steps to Top-Down planning: • Planning • Analysis • Design • Implementation
True
7
Whar are the examples of Identify Strategic Planning Factors(3)
Organization goals, critical success factors, Problem areas
8
What are the examples of Identify Corporate Planning Objects (5)
Ogranizational units, Organizational locations, Business Functions, Entity types, Information systems
9
Iterative process breaking system description into finer and finer detail
Functional decomposition
10
Describe interrelationships between planning objects/Describe relationships between planning objects in the organization.
Planning matrixes
11
What are the Type of Matrixes:(5)
Location-to-function, Unit-to-function, IS-to-data entity, Supporting function-to-data entity, IS-to-business objective
12
Two Approaches to Database and IS Development:
SDLC & Prototyping
13
Systems Development Life Cycle • Purpose–preliminary understanding Deliverable–request for study • Database activity– enterprise modeling and early conceptual data modeling.
Planning
14
• Purpose–thorough requirements analysis and structuring Deliverable–functional system specifications • Database activity–thorough and integrated conceptual data modeling.
Analysis
15
• Purpose–information requirements elicitation and structure Deliverable–detailed design specifications • Database activity– logical database design (transactions, forms, displays, views, data integrity and security).
Logical Design
16
• Purpose–develop technology and organizational specifications Deliverable– program/data structures, technology purchases, organization redesigns • Database activity– physical database design (define database to DBMS, physical data organization, database processing programs).
Physical Design
17
• Purpose–programming, testing, training, installation, documenting Deliverable– operational programs, documentation, training materials • Database activity– database implementation, including coded programs, documentation, installation and conversion.
Implementation
18
• Purpose–monitor, repair, enhance Deliverable–periodic audits • Database activity– database maintenance, performance analysis and tuning, error corrections.
Maintenance
19
Analyze requirements/ Develope preliminary data model.
Conceptual Data Modeling
20
Analyze requirements in detail/ integrate database views into conceptual data model.
Logical database Design
21
Define new database contents to DBMS/ Decide on physical organization for new data/Design database processing programs
Physical database design and definition
22
Code database processing/Install new database contents, usually from existing data source
Database Implementation
23
Analyze database to ensure it meets application needs/ Fix errors in database.
Database maintenance
24
software tools providing automated support for systems development
Computer-Aided Software Engineering (CASE)
25
Three database features: • Data modeling–drawing entity-relationship diagrams • Code generation–SQL code for table creation • Repositories–knowledge base of enterprise information
True
26
Model components that can be purchased, customized, and assembled into full-scale data models.
Packaged Data Models
27
Packaged Data Models • Two types:
• Universal data models • Industry-specific data models
28
a planned undertaking of related activities to reach an objective that has a beginning and an end.
Managing Projects
29
review of systems development project after each development phase with rejustification after each phase
Incremental Commitment
30
Managing Projects: People Involved(8)
Database analysts and data modelers, Users, Programmers, Database architects , Data administrators , Project managers
31
Example of Database Schema/Three-schema architecture: • External Schema:(4)
User views, Subsets, Can be determined, DBA determines schema
32
Example of Database Schema/Three-schema architecture: • Conceptual Schema:(1)
E-R models
33
Example of Database Schema/Three-schema architecture: • Internal Schema:(2)
Logical structures , Physical structures