Software Design Principles: "Producing The Software Blueprint"
Software Design Principles: "Producing The Software Blueprint"
Software Design Principles: "Producing The Software Blueprint"
Lecture Objectives
To understand the importance of design in developing quality software To describe the translation from the requirements analysis model to the design model To understand the principles that guide proper design of software
TCS2411 Software Engineering 2
Designing A House
If you are asked to design a house
D W Kitchen W
Room 2
D D Living Room D
TCS2411 Software Engineering
WC
Room 1 W
3
What Is Design?
Explaining the idea/concept of something Usually with graphical diagrams With the intention to build from the explanation The design is a representation of a product or a system with sufficient detail for implementation
TCS2411 Software Engineering 4
Problem
Design
Models
Development Solution
5
Testing
TCS2411 Software Engineering
Designing Software
From our understanding of the problem, we start building the software Translate the analysis model into the design model Map the information from the analysis model to the design representations - data design, architectural design, interface design, procedural design
TCS2411 Software Engineering 6
Translation Model
Procedural design
Interface design Architectural design
State-Transition Diagram
Data design
Design Principles
Design process should not suffer from tunnel vision The design should be traceable to the analysis model The design should not reinvent the wheel;
Time is short
The design should minimize intellectual distance between the software and the problem in the real world
TCS2411 Software Engineering 8
10
Design Concepts
Fundamental concepts which provide foundation to design correctly: Abstraction Structural Partitioning Refinement Data Structure Modularity Software Procedure Software Architecture Information Hiding Control Hierarchy
TCS2411 Software Engineering 11
Abstraction
Identifying important features for representation There are many levels of abstraction depending on how detailed the representation is required Data abstraction - representation of data objects Procedural abstraction - representation of instructions
TCS2411 Software Engineering 12
Refinement
Stepwise refinement - top-down design strategy by Niklaus Wirth Starting at the highest level of abstraction, every step of refinement decompose instructions into more detailed instructions Complementary to abstraction
13
Modularity
Software is divided into separately named and addressable modules Divide and conquer approach - problem is broken into manageable pieces Solutions for the separate pieces then integrated into the whole system
14
P1 S5 P5 P4
P2
P3 S3
S4
TCS2411 Software Engineering 15
Software Architecture
Modules can be integrated in many ways to produce the system Software architecture is the overall structure of the software The hierarchy of components and how they interact, and the structure of data used by the components Use of framework models, and possible reuse of architectural patterns
TCS2411 Software Engineering 16
17
18
Program structure
S1
S2
S3 S2 S4 S3 S5
TCS2411 Software Engineering 19
S4
S5
Control Hierarchy
Hierarchy of modules representing the control relationships A super-ordinate module controls another module A subordinate module is controlled by another module Measures relevant to control hierarchy: depth, width, fan-in, fan-out
TCS2411 Software Engineering 20
Structure Terminology
M
Fan-out a b c
Depth
d e Fan-in i Width
TCS2411 Software Engineering 21
Structural Partitioning
Program structure partitioned horizontally and vertically Horizontal partitioning defines separate branches for each major program function - input, process, output Vertical partitioning (aka factoring) defines control (decision-making) at the top and work at the bottom
TCS2411 Software Engineering 22
Software Procedure
Processing details of individual modules Precise specification of processing, including sequence of events, exact decision points, repetitive operations, and data organization/structure Procedure is layered - subordinate modules must be referenced in processing details
TCS2411 Software Engineering 23
Information Hiding
Information (procedure and data) contained within a module is inaccessible to other modules that have no need for such information Effective modularity is achieved by independent modules, that communicate only necessary information Ease of maintenance - testing, modification localized and less likely to propagate
TCS2411 Software Engineering 24
References
Software Engineering: A Practitioners Approach 5th Ed. by Roger S. Pressman, Mc-Graw-Hill, 2001 Software Engineering by Ian Sommerville, Addison-Wesley, 2001
25