Design

Introduction
• Design is the creative process of
transforming the problem into a solution,
• The description is also called design.
• The designer goal is to produce a model
or representation.
 Level of design
• Data Structures.
• System architecture.
• Interface Representation.
• Component level detail.
 Design model
• Data design.
• Architectural design.
• Interface design.
• Component level design.
 Cont..

• Data design- Translates the information

domain model into data structures needed
for design.
• Involves data objects, relationships and
data dictionary.
• Architectural Design:
It derived from the system specification.
 Cont…
• It is also defines the relationship between major
structural elements of the software.

• Interface design:
Describes how the communication exists
between the software.
Component Level Design:
transforms structural elements of the software
architecture into procedural description of
software components.
 Design process
• Software design is an iterative process
through which requirements are translated
into a blueprint for constructing the
software.
Design parts:
 Conceptual Design (or) System Design.
 Technical Design.
 Cont…

• Conceptual Design: Which tells the

customer exactly what the system will do.
• Technical design: Which allows the
system builders to understand the
hardware and software needed to solve
the customers problem.
 Conceptual design concept
• Where will the data come from?
• What will happen to the data in the
system?
• What will the system look to users?
• What choices will be offered to users?
• What is the timing of events?
• What will the report and screen look like?
Characteristics of good Conceptual
Design
• It is written in customers languages
• It contains no technical jargon.
• It describe the function of the system.
• It is independent of implementation.
• It is linked to requirements documents.
 Technical design concepts
• Description of major hardware
components and their functions.
• Hierarchy and function of software
components.
• Data structures and data flow.
 Characteristics of good design
• The design must implement all the explicit
requirements of analysis model and
implicit requirements of customer.
• A design should be modular (i.e.) logically
partitioned to perform functions and
subfunctions.
• A design should contain distinct
representation of data, architecture,
interfaces and components.
 Cont..
• The design must readable and
understandable for the developers, testers
and users.
• The design should provide a complete
picture of the software.
 Design principles
• The design should minimize the distance
between the problem and the proposed
software.
• Design should be traceable to analysis
model.
• The design should exhibit uniformity and
integration.
• The design should be an iterative process
to accommodate existing changes.
 Cont…
• Design should be able to meet all the
quality criteria set by the software.
• The design process should not suffer from
tunnel vision.
• Design is not coding, coding is not design.
• Design should ensure to minimize
conceptual errors.