System Analysis &

Design
Unit-III
Topic covered
Logical to Physical design Implementation
Logical to Physical Design
Implementation
• The design phase focuses on the detailed implementation of the
system recommended in the feasibility study.
• The design phase is a transition from a user-oriented document to a
document, oriented to the programmers or data base personnel.

System design goes through two phases of development

• Logical design
• Physical design
Logical Design
• The logical system design specifies the abstract representation of the
data flows, inputs and outputs of the system. This is often conducted
via modelling, using an over abstract (and sometimes graphical)
model of the actual system. Logical design includes entity-relationship
diagrams (ER diagrams).
Logical design covers the following:
1. Reviews the current physical system -its data flow, file content, volumes, frequencies,
etc.
2. Prepares output specifications - determines the format, content, and frequency of
reports, including terminal specifications and locations.
3. Prepares input specifications - format, content, and most of the input functions. This
includes determining the flow of the document from the input data source to the
actual input location.
4. Prepares edit, security and control specifications.
5. Specifies the implementation plan.
6. Prepares a logical design of the information flow, output, input, controls
and implementation plan.
7. Reviews benefits, costs, target dates and system constraints
Physical design
The physical design relates to the actual input and output processes of the
system. This is explained in terms of how data is input into a system, how it is
verified or authenticated, how it is processed, and how it is displayed.
In physical design, the following requirements about the system are decided.
• Input requirement
• Output requirements
• Storage requirements
• Processing requirements
• System control and backup or recovery
Subtasks of physical design
The physical portion of system design can generally be broken down into three sub-tasks:
• 1. User Interface Design
• 2. Data Design
• 3. Process Design

1. User Interface Design is concerned with how users add information to the system
and with how the system presents information back to them.
2. Data Design is concerned with how the data is represented and stored within the
system.
3. Process Design is concerned with how data moves through the system, and with
how and where it is validated, secured and/or transformed as it flows into, through
and out of the system.
Example
A personal computer's physical design involves
• input via a keyboard, processing within the CPU
• output via a monitor, printer, etc.
• It involves a detailed design of a user and a product database
structure processor and a control proc
Physical system design consists of
the following steps.
1. Design the physical system.
a. Specify input/output media.
b. Design the database and specify backup procedures.
c. Design physical information flow through the system and a physical design
walkthrough.
2. Plan system implementation
a. Prepare conversion schedule and a target date.
b. Determine training procedure, courses, and timetable.
3. Devise a test and implementation plan and specify any new hardware
/software
4. Update benefits, costs, conversion date, and system constraints.
Mapping of Logical design to
Physical design
Mapping of Logical design to
Physical design

The ER diagram i.e logical design is given below

Steps of conversion ER (logical) to
tables(physical)
• Entity type becomes a table.
• All single-valued attribute becomes a column for the table.
• A key attribute of the entity type represented by the primary key.
• The multivalued attribute is represented by a separate table.
• Composite attribute represented by components.
• Derived attributes are not considered in the table.
Mapping of Logical design to
Physical design

Tabular structure i.e Physical design made by converting ER Diagram into tables