software architecture3
TRANSCRIPT
![Page 1: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/1.jpg)
1
Software Architecture & Design
By
Syed Salman Qadri
Assistant Professor (CS)
The Islamia University of Bahawalpur
![Page 2: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/2.jpg)
2
Introduction
• Requirements form the basis for all software products
• Requirements engineering is the process, which enables us to systematically determine the requirements for a software product
![Page 3: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/3.jpg)
3
Importance of Software Requirements
• The hardest single part of building a software system is deciding what to build...No other part of the work so cripples the resulting system if done wrong. No other part is difficult to rectify later– Fred Brooks
![Page 4: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/4.jpg)
4
Examples of Requirements
• The system shall maintain records of all payments made to employees on accounts of salaries, bonuses, travel/daily allowances, medical allowances, etc.
![Page 5: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/5.jpg)
5
Examples of Requirements
• The system shall interface with the central computer to send daily sales and inventory data from every retail store
![Page 6: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/6.jpg)
6
Examples of Requirements
• The system shall maintain records of all library materials including books, serials, newspapers and magazines, video and audio tapes, reports, collections of transparencies, CD-ROMs, DVDs, etc.
![Page 7: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/7.jpg)
7
Examples of Requirements
• The system shall allow users to search for an item by title, author, or by International Standard Book Number
• The system’s user interface shall be implemented using a web browser
![Page 8: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/8.jpg)
8
Examples of Requirements
• The system shall support at least twenty transactions per second
• The system facilities which are available to public users shall be demonstrable in ten minutes or less
![Page 9: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/9.jpg)
9
Kinds of Software Requirements
![Page 10: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/10.jpg)
10
Kinds of Software Requirements
• Functional requirements
• Non-functional requirements
• Domain requirements
• Inverse requirements• Design and implementation constraints
![Page 11: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/11.jpg)
11
Functional Requirements
![Page 12: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/12.jpg)
12
Functional Requirements
• Statements describing what the system does.
• Functionality of the system
![Page 13: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/13.jpg)
13
Functional Requirements
• Statements of services the system should provide– Reaction to particular inputs
– Behavior in particular situations
![Page 14: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/14.jpg)
14
Functional Requirements
• Sequencing and parallelism are also captured by functional requirements
• Abnormal behavior is also documented as functional requirements in the form of exception handling
![Page 15: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/15.jpg)
15
Functional Requirements
• Functional requirements should be complete and consistent
• Customers and developers usually focus all their attention on functional requirements
![Page 16: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/16.jpg)
16
Functional Requirements Example
• The system shall solve a quadratic equation using the following formula
x = (-b+sqrt(b2 – 4*a*c))/2*a
![Page 17: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/17.jpg)
17
Functional Requirements Example
• The user shall be able to search either the entire database of patients or select a subset from it (admitted patients, or patients with asthma, etc.)
![Page 18: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/18.jpg)
18
Functional Requirements Example
• The system shall provide appropriate viewers for the user to read documents in the document store
![Page 19: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/19.jpg)
19
Functional Requirements Example
• Every order shall be allocated a unique identifier (ORDER_ID) which the user shall use to access that order
![Page 20: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/20.jpg)
20
Functional Requirements Example
• The system shall allow customers to return non-perishable items within fifteen days of the purchase. A customer must present the original sale receipt to return an item
![Page 21: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/21.jpg)
21
Comments on Examples
• Notice the level of detail in different requirements described above. Some are very detailed compared to others
![Page 22: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/22.jpg)
22
Comments on Examples
• Notice the ambiguity in the requirement, which uses the term ‘appropriate viewers’
• This requirement does not mention the formats of documents and types of viewers, which can be used
![Page 23: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/23.jpg)
23
Comments on Examples
• Notice the ambiguity in the requirement for solving the quadratic equation. The requirement does not speak about the possibility when the value of ‘a’ is zero
x = (-b+sqrt(b2 – 4*a*c))/2*a
![Page 24: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/24.jpg)
24
Comments on Examples
• Incomplete and ambiguous requirements are open to multiple interpretations and assumptions
• This can lead to the development of poor quality, or faulty, software products
![Page 25: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/25.jpg)
25
Summary
• Requirements form the basis of all software engineering projects
• Functional requirements capture the behavioral aspects/functions of the proposed automated system
• Functional requirements are the backbone of all software products
![Page 26: Software architecture3](https://reader033.vdocument.in/reader033/viewer/2022052910/559aa5751a28abc4508b4745/html5/thumbnails/26.jpg)
26
References
• ‘Requirements Engineering: Processes and Techniques’ by G. Kotonya and I. Sommerville, John Wiley & Sons, 1998
• Software Requirements: Objects, Functions, and States by A. Davis, PH, 1993
• Software Engineering 8th Edition, by I. Sommerville, 2008
• Software Engineering 5th Edition, by R. Pressman