Abstract
For software organizations needing ISO 9001 certification, including those that have adopted agile methodologies, it is important that their software life cycle processes be able to manage the requirements imposed by this certification standard. However, the user stories in the XP agile methodology do not provide auditors with enough evidence that certain steps and activities have been performed in compliance with ISO 9001. This paper proposes an extension to the user story, based on four sub processes related to the CMMI-DEV model: 1) identification of the source of the user story; 2) categorization of the non functional requirements; 3) identification of the user story relationships; and 4) prioritization of the user stories. These sub processes are aligned with the XP release planning phase, and enhance the ability of user stories to accumulate the information that is mandatory for achieving ISO 9001 certification.
Highlights
ISO 9001 was originally designed for the manufacturing sector; this standard is being used in many other sectors as well, including health care and software
This paper proposes an extension to the user story, based on four sub processes related to the CMMI-DEV model: 1) identification of the source of the user story; 2) categorization of the non functional requirements; 3) identification of the user story relationships; and 4) prioritization of the user stories
These sub processes are aligned with the XP release planning phase, and enhance the ability of user stories to accumulate the information that is mandatory for achieving ISO 9001 certification
Summary
ISO 9001 was originally designed for the manufacturing sector; this standard is being used in many other sectors as well, including health care and software. The authors of [5,6] have investigated the capability of XP to implement the software processes related to the requirements of ISO 9001 and to the guidelines in ISO 90003 based on the ISO 12207 terminology They observed the following: The main means for documenting user requirements in XP is the user story technique. For exam- ple, the user story technique records a high-level description of user requirements It does not record the details of face-to-face communica- tions with the user during the iterative planning process, not does it take into account the system requirements or any of the technical details need- ed during development.
Sign-in/Register to view highlights & summary 
Published Version (
Free)
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call