Scribd
Upload
4 views

Lecture # 1 (SDA)

The document outlines the objectives and key topics related to Software Design and Architecture (SDA), emphasizing the transformation of customer requirements into implementable designs. It distinguishes between preliminary and detailed design activities, highlighting the importance of software architecture and modeling using UML. Additionally, it provides an overview of UML diagrams, including structural and behavioral types.

Uploaded by

Aimen Saeed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
4 views

Lecture # 1 (SDA)

The document outlines the objectives and key topics related to Software Design and Architecture (SDA), emphasizing the transformation of customer requirements into implementable designs. It distinguishes between preliminary and detailed design activities, highlighting the importance of software architecture and modeling using UML. Additionally, it provides an overview of UML diagrams, including structural and behavioral types.

Uploaded by

Aimen Saeed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 15

SOFTWARE DESIGN &

ARCHITECTURE

1
Objectives

 To equip with an in-depth and thorough


understanding of SDA

 Describe key issues related to software


design and architecture

2
Text books

1. L. Bass, et al., Software Architecture in


Practice, 2nd edition. Addison Wesley, 2004.

2. R. S. Pressman, Software Engineering A


Practitioner’s Approach, seventh edition.
New York, McGraw-Hill, 2010.

3
Class Agenda

 Software design
 Software architecture
 Model
 Purpose of Model
 UML
 UML diagrams

4
Software Design
 Software design deals with transforming
the customer requirements, as described
in the SRS document, into a form (a set
of documents) that is suitable for
implementation in a programming
language.

 Design activities can be broadly


classified into two important parts:
• Preliminary (or high-level) design
and
• Detailed design.
5
Preliminary and Detailed
design activities

 High-level design means identification of


different modules and the control
relationships among them and the
definition of the interfaces among these
modules.

 The outcome of high-level design is


called the program structure or software
architecture

6
Preliminary and detailed
design activities

 During detailed design, the data


structure and the algorithms of the
different modules are designed.

 The outcome of the detailed design


stage is usually known as the module-
specification document.

7
Software
architecture
 The design process for identifying the
sub-systems making up a system and
the framework for sub-system control
and communication is architectural
design

 The output of this design process is a


description of the software architecture

8
Model

 Model is a visual representation of an


object

 It captures the important aspects of a


thing to be modeled

 It can be expressed both in pictures and


text

 Model of software system is made in


modeling language such as UML 9
Why we use model ??
To:
 Capture requirements and domain
knowledge

 Think about the design of a system

 Generate usable work products

 Explore multiple solutions economically

 Find, organize, filter, retrieve, examine and


10
edit information about large systems
UML
 Stands for Unified Modeling Language

 Not a programming language

 General-purpose visual modeling language

 Specify, visualize, construct and document the


artifacts of a software system

 Unify past experiences about modeling


techniques

 Capture static structure and dynamic behavior


11

of a system
UML Diagrams

 Structural diagrams

 Behavioral diagrams

12
Structural diagrams

 Use case diagram

 Class diagram

 Component diagram

 Deployment diagram

13
Behavioral diagrams

 State chart diagram

 Activity diagram

 Sequence diagram

 Collaboration diagram

14
THE
END

15

You might also like