Chapter 10 - 11 Flashcards

(46 cards)

1
Q

Information system

A

Provides for data collection, storage and retrieval
-people, hardware, software
-Databases, application programs and procedures

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

System analysis

A

Establishes need for and extent of information system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Systems development

A

Process of creating information system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Performance factors of an information system

A

-Database design and implementation
-Application design and implementation
-Administrative procedures

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Database development

A

Process of database design and its implementation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

System Development Life Cycle (SDLC)

A

Traces history of an information system
-Provides a picture within which database design and application development are mapped out and evaluated.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Traditional SDLC is divided into five phases

A

-Planning
-Analysis
-Detailed systems design
-Implementation
-Maintenance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Planning (SDLC)

A

Yields a general overview of tha company and its objects

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Analysis (SDLC)

A

Problems defined during the planning phase are examined in greater detail.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Detailed systems design (SDLC)

A

Designer completes the design of the systems process

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Implementation

A

Hardware, DBMS software and application programs are installed, and the database design is implemented

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Maintenance

A

Corrective, adaptive and perfective

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Computer-Aided systems Engineering (CASE) tools

A

Tools used to automate part of or all of the SDLC

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

CASE tools description

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Database life cycle (DBLC) six phases

A

-Database initial study
-Database design
-Implementation and loading
-Testing and evaluation
-Operation
-Maintenance and evolution

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Purpose of database initial study

A

Analyse company situation
Define problems and constraints
Define objectives
Define scope and boundaries

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Description of operations

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Conceptual design Goal

A

Design a database independent of database software and physical details.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Conceptual data model

A

Describes main data entities, attributes, relationships and constrains

20
Q

Minimum data rule

A

All that is needed is there, and all that is there is needed.

21
Q

Conceptual design steps

A
  1. Data analysis and requirements
  2. Entity relationship modelling and normalisation
  3. Data model verification
  4. Distributed database design.
22
Q

Developing the conceptual model using ER diagrams

A
  1. Identify, analyse and refine business rules.
  2. Identify the main entities, using the results of step 1.
  3. Define the relationships among the entities, using the results of steps 1 and 2.
  4. Define the attributes, primary keys and foreign keys for each of the entities.
  5. Normalise the entities.
  6. Complete the initial ER diagram.
  7. Validate the ER model against the end users’ information and processing requirements.
  8. Modify the ER model, using the results of step 7.
23
Q

Data model verification

A

Verified against proposed system processes
-Run through a series of test.

24
Q

Module

A

Information system component that handles specific business functions

25
Cohesivity
Strength of the relationship among the module entities.
26
Module coupling
Extent to which modules are independent to one another -Low coupling decreases unnecessary inter-module dependencies
27
ER Model verification process
1. Identify the ER model's central entity 2. Identify each module and its components. 3. Identify each module's transaction requirements. -Internal: updates/inserts/deletes/queries/reports -External: Module interfaces 4. Verify all processes against the module's processing and reporting requirements. 5. Make all necessary changes suggested in step 4. 6. Repeat steps 2-5 for all modules.
28
Distributed database design
Portions of database may reside in different physical locations.
29
Database fragment
Subset of a database stored at a given location
30
DBMS Software selection factors
Cost DBMS features and tool Underlying model Portability DBMS hardware requirements
31
Logical design goal
Design an enterprise-wide database that is based on a specific data model but independent of physical-level details.
32
Logical design steps
1. Map the conceptual model to the logical model components. 2. Validate the logical model using normalisation. 3. Validate the logical model integrity constraints. 4. Validate the logical model against user requirements.
33
Mapping the conceptual model to the relational model
1. Map strong entities 2. Map supertype/subtype relationships 3. Map weak entities 4. Map binary relationships 5. Map higher-degree relationships.
34
Physical design
Process of data storage organisation and data access characteristics of the database; ensures integrity, security and performance.
35
Physical design steps
Define storage organisation Define integrity and security measures Determine performance measures
36
Top-down design strategy
Design starts by identifying the data sets and then defines the data elements for each of those sets.
37
Bottom-up design strategy
Design first identifies the data elements (items) and then groups them together in data sets.
38
Centralised design
Process by which all database design decisions are carried out centrally by a small group of people
39
Decentralised design
Process in which a conceptual design models subsets of an organisations database requirements, which are then aggregated into a complete design.
40
Virtualisation
Creates a logical representation of computing resources independent of underlying physical computing resources.
41
Implementation and loading
Install the DBMS Create the databases Load or convert the data
42
Testing and evaluation
Physical security Password security Access rights Audit trails Data encryption Diskless encryption Optimisation
43
Full backup / dump
All database objects are backed up in their entirety.
44
Differential backup
Only modified/update objects since last full back up are backed up
45
Transaction log backup
Only the transaction log operations that are not reflected in a previous backup are backed up
46
Maintenance and evolution
Preventive maintenance (backup) Corrective maintenance(recovery) Adaptive maintenance (improving performance, adding entities and attributes) Assignment of access permissions and their maintenance for new and old users. Generations of database access statistics Periodic security audits based on statistics Periodic system-usage summaries for billing and budgeting