Term
|
Definition
Set of related components that work together to accomplish some objectives; objectives are accomplished by interacting with the environment and performing functions |
|
|
Term
|
Definition
Manipulates data rather than a physical object; accepts data from its environment, processes data, and produces output data for decision making |
|
|
Term
Preliminary Investigation Phase |
|
Definition
Produces a problem statement and feasibility study; includes objectives, constraints, and scope of the system; identifies costs and benefits |
|
|
Term
|
Definition
Produces requirements describing processes, data, and environment interactions; diagramming techniques are used to document processes, data, and environment interactions; current system is studied and users of proposed system are interviewed to produce the requirements |
|
|
Term
|
Definition
Produces a plan to efficiently implement the requirements; design specifications are created for processes, data, and environment interaction; focuses on choices to optimize resources given constraints |
|
|
Term
Systems Implementation Phase |
|
Definition
Produces executable code, databases, and user documentation; design specs are coded and tested; before making the new system operational, a transition plan from the old system to the new system is devised; to gain confidence and experience with the new system, the two systems may be run parallel to each other for awhile |
|
|
Term
|
Definition
Produces corrections, changes, and enhancements to an operating information system; commences when an information system becomes operational; comprises activities from all the other phases; ends when a replacement system is deployed and the current system is retired; can last decades |
|
|
Term
|
Definition
Scaled-down versions of a system; used to clarify requirements |
|
|
Term
|
Definition
Describes the kinds of data and relationships |
|
|
Term
|
Definition
Describes relationships among processes |
|
|
Term
Environment Interaction Model |
|
Definition
Describes relationships between events and processes |
|
|
Term
|
Definition
Database represents all important parts of the information system |
|
|
Term
|
Definition
Each part of the database has only one meaning |
|
|
Term
|
Definition
Database contains values perceived by the user |
|
|
Term
|
Definition
Business changes are posted to the database without excessive delays |
|
|
Term
|
Definition
Failures or interference do not corrupt database |
|
|
Term
|
Definition
Different parts of the database do not conflict |
|
|
Term
Entity Relationship Diagram (ERD) |
|
Definition
Graphical representation that depicts things of interest (entities) and relationships among entities |
|
|
Term
|
Definition
Transforms ERDs into table designs using conversion rules, (links to other related tables), and other constraints |
|
|
Term
|
Definition
Removes redundancies in a table design using constraints or dependencies among columns |
|
|
Term
|
Definition
Auxiliary file that can improve performance; can improve performance on retrievals but reduce performance on updatesData |
|
|
Term
|
Definition
Designer decides how data should be clustered or located close together on a disk |
|
|
Term
|
Definition
An ERD is constructed for each group of users; a view is typically small enough for a single person to design; multiple designers can work on views covering different parts of the database |
|
|
Term
|
Definition
Process that merges views into a complete and consistent conceptual schema |
|
|
Term
|
Definition
Qualitative, subjective, and people-oriented |
|
|
Term
|
Definition
Quantitative, objective, and data intensive |
|
|
Term
|
Definition
Mostly involved in the conceptual data modeling and logical database design phases |
|
|
Term
Database Performance Experts |
|
Definition
Mostly involved in the distribution and physical design phases |
|
|
Term
|
Definition
Database of the CASE tool; also known as the repository or encyclopedia |
|
|
Term
|
Definition
Group of changes and enhancements to a system that is released together |
|
|