CS504 Quiz 3 Spring 2022 Set 2

CS504 QUIZ 3 WITH · MOAZ,JUNAID FILES · Final term preparation 2022

1. Dynamic process model shows the process _____ of the system.

Structure….confirm

2. Physical view in Krutchen’s 4+1 architectural view model captures ______.

Mapping of the software onto the hardware and reflects is distributed aspect…..confirm

3. A self documenting code is a code that explains itself without the need of comments and extraneous documentation like _____.

Flowcharts, UML diagrams, process-flow state diagrams…all options correct….confirm

4. Using proper paranthesis normally makes the code.

All options correct…..confirm

Lecture 23: Architectural Views .................................................................................... 122

Lecture 24: Architectural Models-I ............................................................................... 126

Lecture 25: Architectural Models-II .............................................................................. 130

Lecture 26: Introduction to Design Patterns .................................................................. 137

Lecture 27: Observer Pattern ......................................................................................... 140

Lecture 28: Good Programming Practices and Guidelines… ........................................ 146

Lecture 29: File Handling Tips for C++ and Java ......................................................... 155

Lecture 30: Layouts and Comments in Java and C++… ............................................... 162

Lecture 31: Coding Style Guidelines Continued. .......................................................... 167

Lecture 32: Clarity Trough Modularity ......................................................................... 170

Lecture 33: Common Coding Mistakes ......................................................................... 176

Lecture 34: Portability ................................................................................................... 179

Lecture 35: Exception Handling .................................................................................... 184

Lecture 36: Software Verification and Validation ......................................................... 192

Lecture 37: Testing vs. Development ............................................................................ 195

Lecture 38: Equivalence Classes or Equivalence Partitioning ...................................... 199

Lecture 39: White Box Testing ...................................................................................... 202

Lecture 40: Unit Testing ................................................................................................ 207

Lecture 41: Inspections vs. Testing ............................................................................... 210

Lecture 42: Debugging .................................................................................................. 213

Lecture 43: Bug Classes................................................................................................. 216

Lecture 44: The Holistic Approach ................................................................................ 224

Lecture 45: Summary ..................................................................................................... 227

End-

Performan ce Scalability

System

Software

e

Implementation

Use

End-user

Functionali Logical

Lecture No. 23

8.6 Architectural Views

Software architecture defines the high level structure of the software by putting together a number of architectural elements in an organized fashion. These elements are chosen to satisfy the functional as well as non-functional requirements of the system. Perry and Wolfe proposed the following formula for software architecture:

Software architecture = {Elements, Forms, Rationale}

That is, a software architecture is a set of elements which have a certain form. These elements are further divided into three categories. These are: data elements, processing elements, and connecting elements. The data elements contain the information that is used and transformed in the system; the processing elements process the data elements and specify the transformation functions, and connecting elements connect different pieces of architecture together. These can themselves be data or processing elements.

This formula was modified by Boehm as follows:

Software architecture = {Elements, Forms, Rationale/Constraints}

Krutchen proposed that the software architecture model should be composed of multiple views as a software architecture deals with abstraction, with decomposition and composition, with style and esthetics as well as requirements from different stake holders. His architectural model is known as Krutchen’s 4+1 architectural view model. As evident, this model proposes the development of 5 main views namely the logical view, the process view, the physical view, the development view, and the use case view. The logical view is the object model of the design, the process view captures the concurrency and synchronization aspects of the design, the physical view documents the mapping(s) of the software onto the hardware and reflects its distributed aspect, the development view describes the static organization of the software in its development environment, and the use case view uses selected use cases or scenarios to validate that the architecture supports the required functionality.

This model is shown in the following diagram.

Process View

System

integrators

Scalability Throughput