Software Design

Software Architecture (Architectural Design)

• Low level design

• consists sets of structures

• shows abstract representation of system structure

• Can be represented in different views/perspectives

• The earlier stage/phase in software design process

Software Architecture/Architectural Design

• shows the codes of software

• show the price of software

• shows how software elements are distributed in different server

• shows how software elements are grouped

Software Design process includes

• Architectural Design

  Abstract Specification

  Network Design

  Component Design

  Data Structure Design

  Algorithm Design

• Architectural Design

  Abstract Specification

  Interface Design

  Cable Design

  Data Structure Design

  Algorithm Design

• Code Design

  Abstract Specification

  Interface Design

  Component Design

  Data Structure Design

  Algorithm Design

• Architectural Design

  Abstract Specification

  Interface Design

  Component Design

  Data Structure Design

  Algorithm Design

The levels of software design

• High Level Design

  Detailed Design

  Architectural Design

• Low Level Design

  Detailed Design

  Architectural Design

• System Design

  Integration Design

  Unit Design

• Very High Level Design

  Not So High Level Design

  Very Low Level Design

Which of the following is TRUE?

• 1. Architectural Design

  2. The system's most abstract form is the architectural design.

  It recognizes the program as a system made up of numerous.

• All is Wrong

• Detailed Design

  The implementation of what is viewed as a system and its sub-systems from previous levels. More details description on system structure.

• High Level Design

  how sub-systems and modules interact with one another and breaks down the "single entity-multiple component"

Why Software Architecture is important?

• Inhibiting or Enabling a System’s Quality Attributes

  Reasoning About and Managing Change

  Predicting System Qualities

• Enhancing Communication among Stakeholders

• Carrying Early Design Decisions

  Defining Constraints on an Implementation

  Improving Cost and Schedule Estimates

• Carrying Early Design Decisions

  Enhancing Communication among Stakeholders

Architecture Process (which is correct?)

• Determine Functional Requirements

  Designing Architecture

  Validate Architecture

• Determine User Requirements

  Designing Architecture

  Validate Architecture

• Determine Non-Functional Requirements

  Designing Architecture

  Validate Architecture

• Determine Architectural Requirements

  Designing Architecture

  Validate Architecture

Low level design

• •Each module’s responsibilities should be specified as precisely as possible

  ed

• •Each module’s responsibilities should be specified as precisely as possible

  •internal data structures and algorithms can be suggest

• •Constraints on the use of its interface should be specified

  •module-wide invariants can be specified

  •internal data structures and algorithms can be suggest

• •pre and post conditions can be identified

  •internal data structures and algorithms can be suggest

Top Down approach

• Takes the whole software system (high level of abstraction) as one entity and then decomposes it into a more detailed level

• More suitable when the software solution needs to be designed from existing one

• Takes the whole software system as multiple entities and then join them into a more abstract level

• More suitable when the software solution needs to be designed from scratch and specific details are unknown

What is a concern?

• A collection of information that influences a program's code

• may cross cut different modules

• reflects a particular facet of the system's behavior, functionality, or accountability.

• a module name