Software Engineering - Topic 5

​Software Design & Engineering - Topic 5

Mark Lister V. Nalupa​

​Intended Learning Outcomes

• ​Explain the software design

• Identify the software design level

• Explain modularization, concurrency, cohesion, and coupling

• ​Explain the multiple variants of software design

  Differentiate the two approaches in software design 

 

Fill in the Blank

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

Fill in the Blank

It identifies the software as a system with many components interacting with each other.

Fill in the Blank

It 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.

Fill in the Blank

This design is more detailed towards modules and their implementations.

​Software Design Levels

1. architectural design

2. high-level design

3. detailed design​

Fill in the Blank

It 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.

Advantage of Modularization

• ​Smaller components are easier to maintain

  Program can be divided based on functional aspects

  Desired level of abstraction can be brought in the program

  Components with high cohesion can be re-used again.

  Concurrent execution can be made possible

  Desired from security aspect

Fill in the Blank

It provides capability to the software to execute more than one part of code in parallel to each other.

concurrency

Fill in the Blank

It is a measure that defines the degree of intra-dependability within elements of a module.

Seven Types of Cohesion

• ​Co-incidental cohesion

• ​Logical cohesion

• ​Temporal cohesion

• ​Procedural cohesion

• ​Communicational cohesion

• ​Sequential cohesion

• ​Functional cohesion

Fill in the Blank

It is a measure that defines the level of inter-dependability among modules of a program.

Five Levels of Coupling

• content coupling

• common coupling

• control coupling

• stamp coupling

• data coupling​

design verification

Fill in the Blank

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

structured design

Fill in the Blank

It is in this software design where the system is comprised of many smaller sub-systems known as functions

function-oriented design

Fill in the Blank

This software design works around the entities and their characteristics instead of functions involved in the software system.

Variants of Software Design

• ​structured design

• ​function-oriented design

• ​object-oriented design

Fill in the Blank

This software design approach takes the whole software system as one entity and then decomposes it to achieve more than one sub-system or component based on some characteristics.

Fill in the Blank

This software design approach proceeds with composing higher level of components by using basic or lower-level components.

Software Design Approaches

• ​top-down approach

• ​bottom-up approach