System Design

Design is a solution- a ‘how to’ approach compared to analysis, a ‘what is’

approach.

System design is the 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?”
It is the phase where the Software Requirement Specification (SRS) document is
converted into a format that can be implemented and decides how the system will
operate.

Objectives of system design:

◆ System designing leads to ensure that the system is created in such a way
that it fulfills the need of the users and keep them at ease being user-
oriented.
◆ In terms of the flexibility, one of the main objectives of this phase is that it
is intended to design such a system which can be dynamic in nature and
responsive to the changes if required.
 ◆ Another important objective is that the phase of system designing is
concerned with creating the system which can work efficiently providing the
required output and being responsive to the time within a given time limit.
◆ The aspect of reliability and physical security of data cannot be ignored.
With this respect, the system designing phase ensures security measures of the
system effectively and efficiently.
◆ System Design also helps us to achieve fault tolerance which is ability of a
software to continue working where even its 1 or 2 component fails.

So, Systems design is the process of defining the architecture, components,

modules, interfaces, and data for a system to satisfy specified requirements.

Inputs to System Design

System design takes the following inputs −
• Statement of work
• Requirement determination plan
• Current situation analysis
• Proposed system requirements including a conceptual data model, modified
DFDs,
• and Metadata (data about data).

Outputs for System Design

System design gives the following outputs −
• Infrastructure and organizational changes for the proposed system.
• A data schema, often a relational schema.
• Metadata to define the tables/files and columns/data-items.
• A function hierarchy diagram or web page map that graphically describes the
program structure.
• Actual or pseudocode for each module in the program.
• A prototype for the proposed system.

Process of System Design

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:

◆ Pertains to an abstract representation of inputs(source),

output(destination),data base(data stores) and procedures(data flows)- all in a
format that meet user’s requirements. That is, it is Graphical representation of
a system showing the system’s processes and the flows of data into and out of
the processes. e.g. entity-relationship diagrams (ER diagrams).
◆ We use logical design to document information systems because it specifies
what the system is doing without having to specify how, where and by whom
task is accomplished.
◆ What the system is doing will change less over time than how it is doing it.
◆ This design covers the following:
 (i) Review the current physical system.
(ii) Prepares output specifications
(iii) Prepares input specifications.
(iv) Prepares edit, security and control specifications.
(v) Specifies the implementation plan.
(vi) Prepares a logical design walk-through of information flow, input,
output, controls and implementation plan.
(vii)Reviews benefits, costs, target dates and system constraints.

• Physical Design:

◆ Following logical design is physical design.

◆ This produces the working system by defining design specifications (that
tells the programmers exactly what the candidate system must do)
◆ It is the graphical representation of a system showing the system’s internal
and external entities and flows of data into and out of these entities.
◆ Physical system design relates to the actual input and output processes of
the system.
◆ It specifies how, where and by whom it is accomplished rather than what is
being accomplished.
◆ Physical system design consists of the following steps:
(i) Design physical system

a) Specify input/output media: how users add information to the

system and how the system present information back to them.
b) Design the database: how data is represented and stored within
the system.
c) Specify backup procedures
d) Design process: how data moves through the system. Where it
is validated, secured, and transformed as it flows through and out of the
system.
e) Prepare physical design walk-through.

(2) Plan system implementation

(1) Devise test and implementation plan
(2) Update benefits, costs, conversion date.
(3) Specify training procedure.