Software

Design
Prepared by: BILAL UL RAHMAN
ID: 21-RB200-362

Rana University
Computer Science Department
Class 301 Evening 5th semester
2023
 Outline
01 What is Software Design
08 Structured Design

02 Software Design
level
09 Function Oriented
Design
03 Modularization

10 Design Process
04 Cohesion

05 Coupling

06 Design
Verification

07 SOFTWARE
DESIGN
STRATEGIES
What is software Design?

Software design is a process to transform user requirements into some suitable form,
which helps the programmer in software coding and implementation.

For assessing user requirements, an SRS (Software Requirement Specification) document

is created whereas for coding and implementation, there is a need of more specific and
detailed requirements in software terms. The output of this process can directly be used
into implementation in programming languages.

Software design is the first step in SDLC (Software Design Life Cycle), which moves the
concentration from problem domain to solution domain. It tries to specify how to fulfill the
requirements mentioned in SRS.
Software Design Levels

Software design yields three levels of results:

1-Architectural Design - The architectural design is the highest abstract version of the system. It identifies the
software as a system with many components interacting with each other. At this level, the designers get the idea of
proposed solution domain.
2-High-level Design- The high-level design breaks the ‘single entity-multiple component’ concept of architectural
design into less-abstracted view of sub-systems and modules and depicts their interaction with each other. High-level
design focuses on how the system along with all of its components can be implemented in forms of modules. It
recognizes modular structure of each sub-system and their relation and interaction among each other.
Software Design Levels continue

3-Detailed Design- Detailed design deals with the implementation part of what is seen as a system
and its sub-systems in the previous two designs. It is more detailed towards modules and their
implementations. It defines logical structure of each module and their interfaces to communicate with
other modules.
Modularization

Modularization is a technique to divide a software system into multiple discrete and independent modules, which
are expected to be capable of carrying out task(s) independently. These modules may work as basic constructs for
the entire software. Designers tend to design modules such that they can be executed and/or compiled separately
and independently.

Modular design unintentionally follows the rules of ‘divide and conquer’ problem-solving strategy this is because
there are many other benefits attached with the modular design of a software.
Advantages of Modularization

 Smaller components are easier to maintain

 Program can be divided based on functional aspects
 Desired level of abstraction ca n be brought in the program
 Components with high cohesion can be re-used again.
 Concurrent execution can be made possible
 Desired from security aspect
Cohesion

Cohesion is a measure that defines the degree of intra-dependability within elements of a module. The greater the cohesion, the better is the program
design.

There are seven types of cohesion, namely –

1. Co-incidental cohesion - It is unplanned and random cohesion, which might be the result of breaking the program into smaller modules for the sake
of modularization. Because it is unplanned, it may serve confusion to the programmers and is generally not-accepted.

2. Logical cohesion - When logically categorized elements are put together into a module, it is called logical cohesion.

3. Temporal Cohesion - When elements of module are organized such that they are processed at a similar point in time, it is called temporal cohesion.
4. Procedural cohesion - When elements of module are grouped together, which are executed sequentially in order to perform a task, it is called
procedural cohesion.
5. Communicational cohesion - When elements of module are grouped together, which are executed sequentially and work on same data
(information), it is called communicational cohesion.
6. Sequential cohesion - When elements of module are grouped because the output of one element serves as input to another and so on, it is called
sequential cohesion.
7. Functional cohesion - It is considered to be the highest degree of cohesion, and it is highly expected. Elements of module in functional cohesion
are grouped because they all contribute to a single well-defined function. It can also be reused.
 Coupling

Coupling is a measure that defines the level of inter-

dependability among modules of a program. It tells at
what level the modules interfere and interact with each
other. The lower the coupling, the better the program.
There are five levels of coupling, namely -

1. Content coupling - When a module can directly access or modify or refer to the content of
another module, it is called content level coupling.
2. Common coupling- When multiple modules have read and write access to some global data, it
is called common or global coupling.
3. Control coupling- Two modules are called control-coupled if one of them decides the function
of the other module or changes its flow of execution.
4. Stamp coupling- When multiple modules share common data structure and work on different
part of it, it is called stamp coupling.
5. Data coupling- Data coupling is when two modules interact with each other by means of
passing data (as parameter). If a module passes data structure as parameter, then the receiving
module should use all its components.
Ideally, no coupling is considered to be the best.
Design Verification

The output of software design process is design documentation, pseudo codes, detailed logic
diagrams, process diagrams, and detailed description of all functional or non-functional
requirements.

The next phase, which is the implementation of software, depends on all outputs mentioned above.

It is then becomes necessary to verify the output before proceeding to the next phase. The early any
mistake is detected, the better it is or it might not be detected until testing of the product. If the
outputs of design phase are in formal notation form, then their associated tools for verification
should be used otherwise a thorough design review can be used for verification and validation.
 SOFTWARE DESIGN STRATEGIES

Software design is a process to conceptualize the software requirements into software implementation.
Software design takes the user requirements as challenges and tries to find optimum solution. While the
software is being conceptualized, a plan is chalked out to find the best possible design for implementing
the intended solution. There are multiple variants of software design. Let us study them briefly:
 Structured Design

Structured design is a conceptualization of problem into several well-organized elements of solution. It is

basically concerned with the solution design. Benefit of structured design is, it gives better understanding of
how the problem is being solved. Structured design also makes it simpler for designer to concentrate on the
problem more accurately.
 Function Oriented Design

In function-oriented design, the system is comprised of many smaller sub-systems known as functions.
These functions are capable of performing significant task in the system. The system is considered as top
view of all functions. Function oriented design inherits some properties of structured design where divide and
conquer methodology is used.
 Object Oriented Design
Object oriented design works around the entities and their characteristics instead of functions
involved in the software system. This design strategy focuses on entities and its characteristics.
The whole concept of software solution revolves around the engaged entities.
Let us see the important concepts of Object Oriented Design:

 Objects - All entities involved in the solution design are known as objects. For example, person,
banks, company and customers are treated as objects. Every entity has some attributes associated
to it and has some methods to perform on the attributes.
 Classes - A class is a generalized description of an object. An object is an instance of a class.
Class defines all the attributes, which an object can have and methods, which defines the
functionality of the object.
 Object Oriented Design continue
In the solution design, attributes are stored as variables
and functionalities are defined by means of methods or
procedures

 Encapsulation - In OOD, the attributes (data variables) and methods (operation on the data) are
bundled together is called encapsulation. Encapsulation not only bundles important information of an
object together, but also restricts access of the data and methods from the outside world. This is
called information hiding.
 Inheritance - OOD allows similar classes to stack up in hierarchical manner where the lower or sub-
classes can import, implement and re-use allowed variables and methods from their immediate super
classes. This property of OOD is known as inheritance. This makes it easier to define specific class
and to create generalized classes from specific ones.
 Polymorphism - OOD languages provide a mechanism where methods performing similar tasks but
vary in arguments, can be assigned same name. This is called polymorphism, which allows a single
interface performing tasks for different types. Depending upon how the function is invoked, respective
portion of the code gets executed.
 Design Process

Software design process can be perceived as series of well-defined steps. Though it varies according to design
approach (function oriented or object oriented, yet It may have the following steps involved:

 A solution design is created from requirement or previous used system and/or system sequence diagram.
 Objects are identified and grouped into classes on behalf of similarity in attribute characteristics.
 Class hierarchy and relation among them are defined.
 Application framework is defined.
THANK YOU
Insert the Subtitle of Your Presentation