Requirements Analysis
- 1. Software Engineering WEEK 3 Requirements Analysis Sibel Kuzgun Akın
- 2. Requirements Analysis ● Every project starts with requirements analysis. ● Determining the needs or conditions to meet for a new or altered product or project. ● Requirements analysis is critical to the success or failure of a systems or software project.
- 3. What are requirements? (1) A condition or a capability needed by a user to solve a problem or achieve an objective. (2) A condition or capability that must be met or processed by a system or system component to satisfy a contract, standard, specification or other formally imposed document. (3) A documented representation of a condition or capability as in (1) or (2). IEEE Standard 610.12 (1990)
- 5. Definition of Requirement According to Weagers & Beatty: “A requirement is a statement of a customer need or objective, or of a condition or capability that a product must possess to satisfy such a need or objective. A property that a product must have to provide value to a stakeholder.” https://www.amazon.com/Software-Requirements-Developer-Best-Practices/dp/0735679665
- 7. Levels of Software Requirements ● Business requirements ● User requirements ● Functional requirements
- 8. Business Requirements A set of information that describes a business need that leads to one or more projects to deliver a solution and the desired ultimate business outcomes. Example: “The work hours will be tracked in our company.” Business requirements create business rules. Example: “If a person works with a machine, only work hours of the machine will be counted."
- 9. User Requirements A goal or task that a user or a user group must be able to perform with a system or a desired product attribute. Use cases, user stories, and scenarios are common ways to represent user requirements. Example: “I want a matrix report that shows all the staff and all tasks they work on in a week.”
- 10. Functional Requirements A description of a behaviour that a software system will exhibit under specific conditions. Example: “The weekly work hours report should be ordered by task id.”
- 11. Requirements Engineering Requirements engineering is the subdiscipline of systems engineering and software engineering that encompasses all project activities associated with understanding a product's necessary capabilities and attributes. ● Requirements development ● Requirements management Reference: Weagers & Beatty
- 12. Requirements Development ● Elicitation: Discover the requirements via interviews, workshops, observations, documents analysis ● Analysis ● Specification ● Validation
- 13. Elicitation ● Who will use this program? ● How many users will there be? ● Are there any user groups, i.e. users that do the same things using the program? ● Which tasks will the program perform? ● Where will you use this program? – Single computer, LAN, web, mobile devices
- 15. Stakeholders A stakeholder is an individual, group, or organization that ● is actively involved in a project, ● is affected by its process or outcome, ● or can influence its process or outcome.
- 18. A structured approach to requirements development (1) Define stakeholders: WHO? – Who is interested in the system? – Who makes decisions? – Who are the users, managers, developers? (2) Define goals: WHAT? – Stakeholders have goals – These goals can be divided into more specific goals
- 19. A structured approach to requirements development (3) Define requirements: HOW? – Goals can be derived into concrete requirements. – How to get to the requirments? – Model those requirements using diagrams, templates, etc.
- 21. Requirements Management ● Tracking ● Managing ● Controlling ● Tracing In modern days, software is used for requirements management. http://www.softwaretestinghelp.com/requirements-management-tools/
- 22. How are requirements documented? ● Meeting reports ● Emails ● Example Excel sheets ● Printed materials ● ISO 9001 procedures May be used to gather requirements from the users.
- 23. User Stories ● Extreme programming ● In software development and product management, a user story is an informal, natural language description of one or more features of a software system. ● From the perspective of an end user or user of a system. ● Post-it notes or project management software. e.g. Trello, Kanban like
- 24. Opening Questions ● Who will use the program? ● How many users will there be? – Ask further questions to understand the education level, computer using abilities of users; try to find out user groups. ● On which computers / devices will you use the program? – e.g.: PC, iPhone, Android, Web Browser
- 25. Opening Questions (2) ● How do you make these tasks now? – By hand, Excel, paper and pen... ● Could you please show me printed material, example email, Excel sheets, etc.? ● May I have a look at your working place, office, factory, etc.? – Try to understand the context. ● What is you main target? Why do you want this software?
- 26. Opening Questions (3) ● How often will you use the program? ● Which kinds of data will be stored? – Try to identify the size of database. ● Which reports to you want to get from this information system? ● Do you want the system informs you when something happens? – e.g. When the production band halts.
- 27. Continues... Requirements engineering techniques for eliciting requirements https://www.slideshare.net/dmonett/requirements-engineering-techniques-for-eliciting-requirements?next_slide A structured approach to requirements analysis https://www.slideshare.net/dmonett/a-structured-approach-to-requirements-analysis-lecture-slides
- 28. Exercise 1 ● We want a program that reads the weight of the truck from the serial port and saves it inside a file named truck.txt
- 29. Exercise 2 ● “We want to make cost analysis of the projects.” ● “We will compare the man hours and materials budget we have written in the offer, with the real man hours and money spent for the material at the end of the project.” ● “The cost analysis report's currency will be €”
- 30. Exercise 3 ● You should develop a system that keeps track of allowances given to the staff.
- 31. Exercise 4 ● “I want to have a web site that I can update myself. I want to enter new stories and upload my photos.”