CSE360 Tutorial 13

Introduction to Software Engineering
Requirement Engineering
(202206)

Transcript

1. CSE360 Introduction to Software Engineering Lecture: Requirements Engineering Javier Gonzalez-Sanchez javiergs@asu.edu javiergs.engineering.asu.edu Office Hours: By appointment
2. Javier Gonzalez-Sanchez | CSE360 | Summer 2018 | 2 Fall 2021 | 00000001 Where we are? Process Requirements Concepts Specification Management Design Coding Testing Quality
3. Concepts
4. Javier Gonzalez-Sanchez | CSE360 | Summer 2018 | 4 Fall 2021 | 00000001 Requirements Engineering
5. Javier Gonzalez-Sanchez | CSE360 | Summer 2018 | 5 Fall 2021 | 00000001 Concepts necessities requirements
6. Javier Gonzalez-Sanchez | CSE360 | Summer 2018 | 6 Fall 2021 | 00000001 Concepts necessities requirements functional requirement non-functional requirement
7. Javier Gonzalez-Sanchez | CSE360 | Summer 2018 | 7 Fall 2021 | 00000001 Functional Requirement a) services the system should provide, b) how the system should react to particular inputs, and c) how the system should behave in particular situations. d) May state what (reactions, behaviours, or services) the system should not do.
8. Javier Gonzalez-Sanchez | CSE360 | Summer 2018 | 8 Fall 2021 | 00000001 Examples • Search option given to user to search from various invoices. • User should be able to mail any report to management. • Users can be divided into groups and groups can be given separate rights. What about • Pac-man? • Blackboard? • MyASU? • Recitation Project 1?
9. Javier Gonzalez-Sanchez | CSE360 | Summer 2018 | 9 Fall 2021 | 00000001 Non-functional Requirement Non-functional requirements a) Constraints on the services or functions offered by the system, such as Standards to apply, development platform, timing constraints, constraints on the development process, etc. a) Quality attributes, such as performance specifications, robustness, usability, etc.
10. Javier Gonzalez-Sanchez | CSE360 | Summer 2018 | 10 Fall 2021 | 00000001 Examples (Quality) Property Measure Speed • Processed transactions/second • User/event response time • Screen refresh time Size • Mbytes • Number of ROM chips Ease of use • Training time • Number of help frames Reliability • Mean time to failure • Probability of unavailability • Rate of failure occurrence • Availability Robustness • Time to restart after failure • Percentage of events causing failure • Probability of data corruption on failure Portability • Percentage of target dependent statements • Number of target systems
11. Javier Gonzalez-Sanchez | CSE360 | Summer 2018 | 11 Fall 2021 | 00000001 Types of Non-Functional Requirements
12. Javier Gonzalez-Sanchez | CSE360 | Summer 2018 | 12 Fall 2021 | 00000001 INVEST in good requirements • Independent – loosely coupled with one another • Negotiable – Stories are what and why , not how ( 99% ). • Valuable – for the customer! • Estimatable – Effort/Cost of design, build, and test. • Small (sized appropriately) • Testable – pass or fail
13. Product Backlog
14. Javier Gonzalez-Sanchez | CSE360 | Summer 2018 | 14 Fall 2021 | 00000001 Definition
15. Javier Gonzalez-Sanchez | CSE360 | Summer 2018 | 15 Fall 2021 | 00000001 Questions
16. To be continued…
17. Javier Gonzalez-Sanchez | CSE360 | Summer 2018 | 17 Fall 2021 | 00000001 References • Somerville Chapter 3 and 4 • Essential Scrum – Chapter 6.
18. CSE 563 Software Requirements and Specification Javier Gonzalez-Sanchez, Ph.D. javiergs@asu.edu Fall 2022 Copyright. These slides can only be used as study material for the class CSE563 at ASU. They cannot be distributed or used for another purpose.