Chapter 10 - 11 Flashcards
(46 cards)
Information system
Provides for data collection, storage and retrieval
-people, hardware, software
-Databases, application programs and procedures
System analysis
Establishes need for and extent of information system
Systems development
Process of creating information system
Performance factors of an information system
-Database design and implementation
-Application design and implementation
-Administrative procedures
Database development
Process of database design and its implementation
System Development Life Cycle (SDLC)
Traces history of an information system
-Provides a picture within which database design and application development are mapped out and evaluated.
Traditional SDLC is divided into five phases
-Planning
-Analysis
-Detailed systems design
-Implementation
-Maintenance
Planning (SDLC)
Yields a general overview of tha company and its objects
Analysis (SDLC)
Problems defined during the planning phase are examined in greater detail.
Detailed systems design (SDLC)
Designer completes the design of the systems process
Implementation
Hardware, DBMS software and application programs are installed, and the database design is implemented
Maintenance
Corrective, adaptive and perfective
Computer-Aided systems Engineering (CASE) tools
Tools used to automate part of or all of the SDLC
CASE tools description
Includes a system architect and visio professional
Helps produce better systems in a reasonable amount of time and reasonable
Applications are more structured, better documented and standardized
-prolongs operational life of systems
-easier and cheaper to update and maintain
Database life cycle (DBLC) six phases
-Database initial study
-Database design
-Implementation and loading
-Testing and evaluation
-Operation
-Maintenance and evolution
Purpose of database initial study
Analyse company situation
Define problems and constraints
Define objectives
Define scope and boundaries
Description of operations
Provides precise, up-to-date and reviewed description of activities defining an organisation’s operating environment.
Business rules are derived from a description of operations.
Conceptual design Goal
Design a database independent of database software and physical details.
Conceptual data model
Describes main data entities, attributes, relationships and constrains
Minimum data rule
All that is needed is there, and all that is there is needed.
Conceptual design steps
- Data analysis and requirements
- Entity relationship modelling and normalisation
- Data model verification
- Distributed database design.
Developing the conceptual model using ER diagrams
- Identify, analyse and refine business rules.
- Identify the main entities, using the results of step 1.
- Define the relationships among the entities, using the results of steps 1 and 2.
- Define the attributes, primary keys and foreign keys for each of the entities.
- Normalise the entities.
- Complete the initial ER diagram.
- Validate the ER model against the end users’ information and processing requirements.
- Modify the ER model, using the results of step 7.
Data model verification
Verified against proposed system processes
-Run through a series of test.
Module
Information system component that handles specific business functions