Chapter 2: System design

 System design is the SDLC phase that bridges

the gap between problem domain and the
existing system in a manageable way.
 This phase focuses on the solution domain, i.e.
“how to implement?”
 During this phase, we design an information
system that satisfies the requirements.
 We must design all aspects of the system from
input and output screens to reports,
databases, and computer processes.
08/05/2022 DaDu system analysis and design 1
 Database Design
 Database design methodology has two main phases:
1. Logical database design.
2. Physical database design.

1. Logical database design

 Process of constructing a model of information used
in an enterprise based on a specific data model (e.g.
relational), but independent of a particular DBMS
and other physical considerations.

08/05/2022 DaDu system analysis and design 2

 2. Physical Design
 Process of producing a description of the
implementation of the database on secondary storage
 It describes the base relations, file organizations, and
indexes design used to achieve efficient access to the
data, and any associated integrity constraints and
security measures.

Purpose of Database Design

 Structure the data in stable structures, called
normalized tables
 Not likely to change over time
 Minimal redundancy
 Develop a logical database design that reflects actual
data requirements
 It forms the base for a physical database design
08/05/2022 DaDu system analysis and design 3
 Cont…
 Translate a relational database model into a
technical file and database design that
balances several performance factors
 Choose data storage technologies that will
efficiently, accurately and securely process
database activities

08/05/2022 DaDu system analysis and design 4

 Process of Database Design

 Logical Design
 Based upon the conceptual data model there are
four key steps
1. Develop a logical data model for each known user
interface for the application using normalization
principles.
2. Combine normalized data requirements from all user
interfaces into one consolidated logical database model
3. Translate the conceptual E-R data model for the
application into normalized data requirements
4. Compare the consolidated logical database design with the
translated E-R model and produce one final logical
database model for the application

08/05/2022 DaDu system analysis and design 5

 Process of Database Design
• Physical Design
– Based upon results of logical database design
– Key decisions
1. Choosing storage format for each attribute from the
logical database model
2. Grouping attributes from the logical database model
into physical records
3. Arranging related records in secondary memory
(hard disks and magnetic tapes) so that records can be
stored, retrieved and updated rapidly
4. Selecting media and structures for storing data to
make access more efficient
08/05/2022 DaDu system analysis and design 6
 Relational Database Model

• Data represented as a set of related tables or relations

• Relation
– A named, two-dimensional table of data. Each relation
consists of a set of named columns and an arbitrary number
of unnamed rows
– Properties
• Entries in cells are simple
• Entries in columns are from the same set of values
• Each row is unique
• The sequence of columns can be interchanged without
changing the meaning or use of the relation
• The rows may be interchanged or stored in any sequence

08/05/2022 DaDu system analysis and design 7

 Normalization

• Normalization is a technique of organizing the

data in the database.
• It is a systematic approach of decomposing
tables to eliminate data redundancy and
undesirable characteristics like
insertion,update,deletion anamolies.
• It is a multi-step process that puts data into
tabular form by removing duplicated data from
the relation tables.
08/05/2022 DaDu system analysis and design 8
 Cont…
• It is a process that breaks down data into record
groups for efficient processing.
• Normalization is used for mainly two purpose.
- Eliminating reduntant(useless) data.
- Ensuring data dependencies make sense i.e
data is logically stored.

08/05/2022 DaDu system analysis and design 9

 Designing the human interface

• Focus on how information is provided to and captured from

users.
• A good human-computer interface provides a uniform structure
for finding, viewing and invoking the different components of a
system.
• Designing Interfaces includes:
1. Designing layout,
2. Structuring data entry field
3. controlling data entry field,
4. providing feedback,
5. designing online help

08/05/2022 DaDu system analysis and design 10

 1. Designing Layouts
• Designing Layouts
– Standard formats similar to paper-based forms and reports
should be used.
– Screen navigation on data entry screens should be left-to-
right, top-to-bottom as on paper forms.
• Flexibility and consistency are primary design goals
Users should be able to move freely between fields (e.g.
back & Forth)
Data should not be permanently saved until the user
explicitly requests this
Each key and command should be assigned to one function.

08/05/2022 DaDu system analysis and design 11

 2. Structuring Data Entry

08/05/2022 DaDu system analysis and design 12

 3. Controlling Data Input
• One objective of interface design is to reduce
data entry errors
• Role of systems analyst is to anticipate user
errors and design features into the system’s
interfaces to avoid, detect, and correct data
entry mistakes

08/05/2022 DaDu system analysis and design 13

 4. Providing Feedback
1. Status Information
– Keeps users informed of what is going on in system
• Displaying status information is especially important
if the operation takes longer than a second or two
2. Prompting Cues /reminder
– Best to keep as specific as possible
3. Error and Warning Messages
– Messages should be specific and free of error codes and
jargon
– User should be guided toward a result rather than scolded
– Use terms familiar to user
– Be consistent in format and placement of messages

08/05/2022 DaDu system analysis and design 14

 5. Providing Help
• Place yourself in user’s place when designing help
• Guidelines
– Simplicity
• Help messages should be short and to the point
– Organization
• Information in help messages should be easily
absorbed by users
– Demonstrate
• It is useful to explicitly show users how to
perform an operation
08/05/2022 DaDu system analysis and design 15
 Cont…
• Context-Sensitive Help
– Enables user to get field-specific help
• Users should always be returned to where
they were when requesting help

08/05/2022 DaDu system analysis and design 16