Team 6 SOFTWARE REQUIREMENTS - dslab.konkuk.ac.krdslab.konkuk.ac.kr/Class/2010/10SE/Team...
Transcript of Team 6 SOFTWARE REQUIREMENTS - dslab.konkuk.ac.krdslab.konkuk.ac.kr/Class/2010/10SE/Team...
![Page 1: Team 6 SOFTWARE REQUIREMENTS - dslab.konkuk.ac.krdslab.konkuk.ac.kr/Class/2010/10SE/Team Project/A/1/Software... · Team 6. 1. Introduction Elicitation Analysis Specification Management](https://reader034.fdocuments.us/reader034/viewer/2022042317/5f05e4127e708231d4153be7/html5/thumbnails/1.jpg)
SOFTWARE REQUIREMENTS
Team 6
![Page 2: Team 6 SOFTWARE REQUIREMENTS - dslab.konkuk.ac.krdslab.konkuk.ac.kr/Class/2010/10SE/Team Project/A/1/Software... · Team 6. 1. Introduction Elicitation Analysis Specification Management](https://reader034.fdocuments.us/reader034/viewer/2022042317/5f05e4127e708231d4153be7/html5/thumbnails/2.jpg)
1. Introduction
� Elicitation
� Analysis
� Specification
� Management
� Validation
![Page 3: Team 6 SOFTWARE REQUIREMENTS - dslab.konkuk.ac.krdslab.konkuk.ac.kr/Class/2010/10SE/Team Project/A/1/Software... · Team 6. 1. Introduction Elicitation Analysis Specification Management](https://reader034.fdocuments.us/reader034/viewer/2022042317/5f05e4127e708231d4153be7/html5/thumbnails/3.jpg)
1. Introduction
![Page 4: Team 6 SOFTWARE REQUIREMENTS - dslab.konkuk.ac.krdslab.konkuk.ac.kr/Class/2010/10SE/Team Project/A/1/Software... · Team 6. 1. Introduction Elicitation Analysis Specification Management](https://reader034.fdocuments.us/reader034/viewer/2022042317/5f05e4127e708231d4153be7/html5/thumbnails/4.jpg)
2.Defining a Requirement
![Page 5: Team 6 SOFTWARE REQUIREMENTS - dslab.konkuk.ac.krdslab.konkuk.ac.kr/Class/2010/10SE/Team Project/A/1/Software... · Team 6. 1. Introduction Elicitation Analysis Specification Management](https://reader034.fdocuments.us/reader034/viewer/2022042317/5f05e4127e708231d4153be7/html5/thumbnails/5.jpg)
3.Elicitation
� Requirements elicitation focuses on
gathering knowledge about the needs of the
stakeholders.
![Page 6: Team 6 SOFTWARE REQUIREMENTS - dslab.konkuk.ac.krdslab.konkuk.ac.kr/Class/2010/10SE/Team Project/A/1/Software... · Team 6. 1. Introduction Elicitation Analysis Specification Management](https://reader034.fdocuments.us/reader034/viewer/2022042317/5f05e4127e708231d4153be7/html5/thumbnails/6.jpg)
3.1 Understanding the Problem
and Its Domain
![Page 7: Team 6 SOFTWARE REQUIREMENTS - dslab.konkuk.ac.krdslab.konkuk.ac.kr/Class/2010/10SE/Team Project/A/1/Software... · Team 6. 1. Introduction Elicitation Analysis Specification Management](https://reader034.fdocuments.us/reader034/viewer/2022042317/5f05e4127e708231d4153be7/html5/thumbnails/7.jpg)
3.2 Making the Business Case
� Understanding cost, risk, and anticipated
benefits from the project
� It determines whether the project should
proceed or notproceed or not
![Page 8: Team 6 SOFTWARE REQUIREMENTS - dslab.konkuk.ac.krdslab.konkuk.ac.kr/Class/2010/10SE/Team Project/A/1/Software... · Team 6. 1. Introduction Elicitation Analysis Specification Management](https://reader034.fdocuments.us/reader034/viewer/2022042317/5f05e4127e708231d4153be7/html5/thumbnails/8.jpg)
3.3 Elicitation Techniques
� Collaborative session
� Interviewing techniques!
� Questionnaires
� Ethnography!� Ethnography!
� Prototyping!
� Documentation
� Modeling
� Roleplaying
� Checklists of NFRs
![Page 9: Team 6 SOFTWARE REQUIREMENTS - dslab.konkuk.ac.krdslab.konkuk.ac.kr/Class/2010/10SE/Team Project/A/1/Software... · Team 6. 1. Introduction Elicitation Analysis Specification Management](https://reader034.fdocuments.us/reader034/viewer/2022042317/5f05e4127e708231d4153be7/html5/thumbnails/9.jpg)
3.4. Conflict Identification
and Negotiation� Conflict : between stakeholder and
functionality of the system
� Functional requirement
� Nonfunctional requirement� Nonfunctional requirement
� Negotiation : to reveal conflicts rapidly
![Page 10: Team 6 SOFTWARE REQUIREMENTS - dslab.konkuk.ac.krdslab.konkuk.ac.kr/Class/2010/10SE/Team Project/A/1/Software... · Team 6. 1. Introduction Elicitation Analysis Specification Management](https://reader034.fdocuments.us/reader034/viewer/2022042317/5f05e4127e708231d4153be7/html5/thumbnails/10.jpg)
4. Requirements Analysis
� 4.1 Conceptual Modeling
� Several types of model : data flows, state
models, user interaction
� Depend of many factors : engineer expertise, � Depend of many factors : engineer expertise,
customer requirements
![Page 11: Team 6 SOFTWARE REQUIREMENTS - dslab.konkuk.ac.krdslab.konkuk.ac.kr/Class/2010/10SE/Team Project/A/1/Software... · Team 6. 1. Introduction Elicitation Analysis Specification Management](https://reader034.fdocuments.us/reader034/viewer/2022042317/5f05e4127e708231d4153be7/html5/thumbnails/11.jpg)
4. Requirements Analysis
� 4.2 Architectural Design and Requirements
Allocation
� Identify requirements
� Design Architectural and fulfill the stated � Design Architectural and fulfill the stated
requirements(using ATAM)
� Requirements can be allocated to components
![Page 12: Team 6 SOFTWARE REQUIREMENTS - dslab.konkuk.ac.krdslab.konkuk.ac.kr/Class/2010/10SE/Team Project/A/1/Software... · Team 6. 1. Introduction Elicitation Analysis Specification Management](https://reader034.fdocuments.us/reader034/viewer/2022042317/5f05e4127e708231d4153be7/html5/thumbnails/12.jpg)
5.Requirements specification
� Systems definition document
� user requirements document or the concept of
operations
� Systems requirement specification� Systems requirement specification
� Systems engineering activities
� Software requirements specification
� What the software component must to do
![Page 13: Team 6 SOFTWARE REQUIREMENTS - dslab.konkuk.ac.krdslab.konkuk.ac.kr/Class/2010/10SE/Team Project/A/1/Software... · Team 6. 1. Introduction Elicitation Analysis Specification Management](https://reader034.fdocuments.us/reader034/viewer/2022042317/5f05e4127e708231d4153be7/html5/thumbnails/13.jpg)
5.Requirements specification
![Page 14: Team 6 SOFTWARE REQUIREMENTS - dslab.konkuk.ac.krdslab.konkuk.ac.kr/Class/2010/10SE/Team Project/A/1/Software... · Team 6. 1. Introduction Elicitation Analysis Specification Management](https://reader034.fdocuments.us/reader034/viewer/2022042317/5f05e4127e708231d4153be7/html5/thumbnails/14.jpg)
5.1 Qualities of an individual
requirement
� Concise, Correct, Nomambiguous, Feasible,
Verifiable
5.2 Qualities of the set of 5.2 Qualities of the set of requirements
� Realistic, Concise , Complete , Consistent
![Page 15: Team 6 SOFTWARE REQUIREMENTS - dslab.konkuk.ac.krdslab.konkuk.ac.kr/Class/2010/10SE/Team Project/A/1/Software... · Team 6. 1. Introduction Elicitation Analysis Specification Management](https://reader034.fdocuments.us/reader034/viewer/2022042317/5f05e4127e708231d4153be7/html5/thumbnails/15.jpg)
6.Validation
� “How we got the requirements right?”
� Reviews
� Prototyping
� Model validation
� Acceptance tests
![Page 16: Team 6 SOFTWARE REQUIREMENTS - dslab.konkuk.ac.krdslab.konkuk.ac.kr/Class/2010/10SE/Team Project/A/1/Software... · Team 6. 1. Introduction Elicitation Analysis Specification Management](https://reader034.fdocuments.us/reader034/viewer/2022042317/5f05e4127e708231d4153be7/html5/thumbnails/16.jpg)
7.Requirements Management
� Requirements traceability
� Change requests
� Requirements
� Attributes
![Page 17: Team 6 SOFTWARE REQUIREMENTS - dslab.konkuk.ac.krdslab.konkuk.ac.kr/Class/2010/10SE/Team Project/A/1/Software... · Team 6. 1. Introduction Elicitation Analysis Specification Management](https://reader034.fdocuments.us/reader034/viewer/2022042317/5f05e4127e708231d4153be7/html5/thumbnails/17.jpg)
8.Conclusions