Requirements Engineering Processes
Download as PPTX, PDF0 likes954 views
This chapter discusses requirements engineering processes. It defines a process as an organized set of activities that transforms inputs to outputs. Requirements engineering is presented as a design process involving creativity and interactions between people. The key activities in most requirements engineering processes are requirements elicitation, analysis and negotiation, and validation. Process models can describe requirements engineering processes at different levels of granularity. Human factors are important influences as requirements processes involve stakeholders from varying backgrounds. Process improvement is achieved through incremental introduction of good practices and maturity models can assess organizational process capabilities.
Requirements Engineering Processes
- 1. Chapter 3 – Requirements Engineering Processes Requirements Engineering Mutah University Faculty of IT, Department of Software Engineering Dr. Ra’Fat A. AL-msie’deen https://sites.google.com/site/ralmsideen/ https://academic.mutah.edu.jo/rafatalmsiedeen/sitepages/Home.aspx https://rafat66.github.io/Al-Msie-Deen/ rafatalmsiedeen@mutah.edu.jo or rafatals3ode@gmail.com
- 3. Based on Some content from Gerald Kotonya and Ian Sommerville’s text with the same name. Requirements Engineering Processes and Techniques by G. Kotonya and I. Sommerville 1998.
- 4. Objectives To introduce the notion of processes and process models for requirements engineering. To explain the critical role of people in requirements engineering processes. To explain why process improvements is important and to suggest a process improvement model for requirements engineering.
- 5. Processes o A process is an organised set of activities which transforms inputs to outputs. o Process descriptions encapsulate knowledge and allow it to be reused. o Examples of process descriptions: Instruction manual for a dishwasher. Cookery book. Procedures manual for a bank. Quality manual for software development.
- 6. Design processes • Processes which involve creativity, interactions between a wide range of different people, engineering judgement and background knowledge and experience. • Examples of design processes: Writing a book. Organising a conference. Designing a processor chip. Requirements engineering.
- 7. RE process - inputs and outputs
- 8. Input/output description Input Description Existing system information Information about the functionality of systems to be replaced or other systems which interact with the system being specified Stakeholder needs Descriptions of what system stakeholders need from the system to support their work Organizational standards Standards used in an organisation regarding system development practice, quality management, etc. Regulations External regulations such as health and safety regulations which apply to the system. Domain information General information about the application domain of the system
- 9. Input/output description Output Description Agreed requirements A description of the system requirements which is understandable by stakeholders and which has been agreed by them. System specification This is a more detailed specification of the system functionality which may be produced in some cases System models A set of models such as a data-flow model. an object model, a process model, etc. which describes the system from different perspectives
- 10. RE process variability • RE processes vary radically from one organisation to another. • Factors contributing to this variability include: – Technical maturity. – Disciplinary involvement. – Organizational culture. – Application domain. There is therefore no ‘ideal’ requirements engineering process
- 11. Process models • A process model is a simplified description of a process presented from a particular perspective. • Types of process model include: Coarse-grain activity models Fine-grain activity models Role-action models Entity-relation models
- 12. Coarse-grain activity model of RE
- 13. RE process activities • Requirements elicitation – Requirements discovered through consultation with stakeholders. • Requirements analysis and negotiation – Requirements are analysed and conflicts resolved through negotiation. • Requirements documentation – A requirements document is produced. • Requirements validation – The requirements document is checked for consistency and completeness.
- 14. Waterfall model of the software process
- 15. Context of the RE process
- 16. Spiral model of the RE process
- 17. Actors in the RE process • Actors in a process are the people involved in the execution of that process. • Actors are normally identified by their roles rather than Individually. • Requirements engineering involves actors who are primarily interested in the problem to be solved (end-users, etc) as well actors interested in the solution (system designers, etc.). • Role-action diagrams document which actors are involved in different activities.
- 18. RAD for software prototyping Role-Action Diagram
- 19. Role descriptions Role Description Domain expert Responsible for providing information about the application domain and the specific problem in that domain which is to be solved. System end-user Responsible for using the system after delivery Requirements engineer Responsible for eliciting and specifying the system requirements Software engineer Responsible for developing the prototype software system Project manager Responsible for planning and estimating the prototyping project
- 20. Human and social factors Requirements engineering processes are dominated by human, social and organisational factors because they always involve a range of stakeholders from different backgrounds and with different individual and organisational goals. System stakeholders may come from a range of technical and non-technical background and from different disciplines.
- 21. Types of stakeholder o Software engineers responsible for system development. o System end-users who will use the system after it has been delivered. o Managers of system end-users who are responsible for their work. o External regulators who check that the system meets its legal requirements. o Domain experts who give essential background information about the system application domain.
- 22. Factors influencing requirements Personality and status of stakeholders. The personal goals of individuals within an organisation. The degree of political influence of stakeholders within an organisation.
- 23. Process support • CASE tools provide automated support for software engineering processes. • The most mature CASE tools support well-understood activities such as programming and testing and the use of structured methods. • Support for requirements engineering is still limited because of the informality and the variability of the process.
- 24. CASE tools for RE • Modelling and validation tools support the development of system models which can be used to specify the system and the checking of these models for completeness and consistency. The tool package which supports this book includes this type of tool. • Management tools help manage a database of requirements and support the management of changes to these requirements.
- 26. A requirements management system (cont.) Word Processor
- 27. Requirements management tools • Requirements browser. • Requirements query system. • Traceability support system. • Report generator. • Requirements converter and word processor linker. • Change control system.
- 28. Process improvement • Process improvement is concerned with modifying processes in order to meet some improvement objectives. • Improvement objectives: – Quality improvement. – Schedule reduction. – Resource reduction.
- 29. Planning process improvement What are the problems with current processes? What are the improvement goals? How can process improvement be introduced to achieve these goals? How should process improvements be controlled and managed?
- 30. RE process problems Lack of stakeholder involvement. Business needs not considered. Lack of requirements management. Lack of defined responsibilities. Stakeholder communication problems. Over-long schedules and poor quality requirements documents.
- 31. Process maturity • Process maturity can be thought of as the extent that an organisation has defined its processes, actively controls these processes and provides systematic human and computer- based support for them. • The SEI’s Capability Maturity Model is a framework for assessing software process maturity in development organisations Software Engineering Institute
- 33. Maturity levels • Initial level – Organisations have an undisciplined process and it is left to individuals how to manage the process and which development techniques to use. • Repeatable level – Organisations have basic cost and schedule management procedures in place. They are likely to be able to make consistent budget and schedule predictions for projects in the same application area. • Defined level – The software process for both management and engineering activities is documented, standardized and integrated into a standard software process for the organisation.
- 34. Maturity levels (cont.) • Managed level – Detailed measurements of both process and product quality are collected and used to control the process. • Optimizing level – The organisation has a continuous process improvement strategy, based on objective measurements, in place.
- 35. RE process maturity model Figure x. Requirements engineering process maturity levels.
- 36. RE process maturity levels • Initial level – No defined RE process. Suffer from requirements problems such as requirements volatility, unsatisfied stakeholders and high rework costs. Dependent on individual skills and experience. • Repeatable level – Defined standards for requirements documents and policies and procedures for requirements management. • Defined level – Defined RE process based on good practices and techniques. Active process improvement process in place.
- 37. Good practice for RE process improvement RE processes can be improved by the systematic introduction of good requirements engineering practice. Each improvement cycle identifies good practice guidelines and works to introduce them in an organisation.
- 38. Examples of good practice guidelines o Define a standard document structure. o Uniquely identify each requirement. o Define policies for requirements management. o Use checklists for requirements analysis. o Use scenarios to elicit requirements. o Specify requirements quantitatively. o Use prototyping to animate requirements. o Reuse requirements.
- 39. Key points The requirements engineering process is a structured set of activities which lead to the production of a requirements document. Inputs to the requirements engineering process are information about existing systems, stakeholder needs, organisational standards, regulations and domain information. Requirements engineering processes vary radically from one organisation to another. Most processes include requirements elicitation, requirements analysis and negotiation and requirements validation.
- 40. Key points (cont.) Requirements engineering process models are simplified process description which are presented from a particular perspective. Human, social and organisational factors are important influences on requirements engineering processes. Requirements engineering process improvement is difficult and is best tackled in an incremental way. Requirements engineering processes can be classified according to their degree of maturity.
- 41. Chapter 3 – Requirements Engineering Processes Requirements Engineering Mutah University Faculty of IT, Department of Software Engineering Dr. Ra’Fat A. AL-msie’deen https://sites.google.com/site/ralmsideen/ https://academic.mutah.edu.jo/rafatalmsiedeen/sitepages/Home.aspx https://rafat66.github.io/Al-Msie-Deen/ rafatalmsiedeen@mutah.edu.jo or rafatals3ode@gmail.com