220 likes | 232 Views
Chapter 10. Requirement and Specifications. Sharif University of Technology, International Branch, Kish Island Dr. Mohsen Sadighi Moshkenani www.sadighim.ir. Outline. Requirements Requirement engineering Special attention on nonfunctional requirements
E N D
Chapter 10 Requirement and Specifications Sharif University of Technology, International Branch, Kish Island Dr. MohsenSadighiMoshkenani www.sadighim.ir
Outline • Requirements • Requirement engineering • Special attention on nonfunctional requirements • Requirement specifications, and its role • Format • Related diagrams • Test and evaluation
Some questions • What the desired product should do? What are its functions • In what conditions it should work? • Is there any restriction on the development process of the product? • How we can find that the delivered product, is the desired one? What are the evaluation criteria? • How related stakeholders know that they have common approach • Why such questions are important?
Some questions; Examples • For functions • For restrictions on the products • For restrictions on the development process
Requirements • Answer to the given questions, and is the basis for any treatment on development of the project • This is the reason for its importance • Such issues should be documented (Why?) • Miss-understanding is a major problem in software development • Note that the software process is not visible
Requirements • Specifies • Functions of the product • conditions and restrictions on • operation environment and • development process • Evaluation information and criteria • Answers to the raised questions • Figure 10-2
Requirement specifications • Is the document which clearly specifies the requirements • It has important roles:
Requirement engineering • The process for achieving the requirements • Why it is process? • Is it the same as system analysis?
Why requirement engineering • The base of agreement • . . .
From usual nonfunctional requirements • Human issues; such as . . . • Hardware issues; such as . . . • Software issues; such as . . . • Data issues; such as . . . • Performance issues; such as . . . • Time issues; such as • Reliability issues; such as . . . • Security issues; such as . . . • And much more
Let us follow an example • You may consider your project
How requirement specifications should be represented • For functions • Context diagram ( Figure 10-4) • Use case diagrams (Figure 10-3) • Use case description tales (Table 10-2) • For non-functional requirements: • Text ( Figure 10-5)
Home work: • Requirement specifications of your term project; • (Deadline is …) • Search for a template, to document requirement specifications; and report the result • (Optional)
Test and evaluation of the requirement specification • Review some evaluation criteria • Who is responsible to check? • Role of consulting and experts • For different aspects; such as legal and financial