1 / 21

Adaptation of Evolving Requirements : A Managed approach for Non-functional requirements

Adaptation of Evolving Requirements : A Managed approach for Non-functional requirements. Tanya Kudchadker Nivedita Angadi Guides: Dr. A. Serebrenik (TU/e) Martijn Klabbers, ir ( LaQuSo ). Requirements Management - Steps. Requirement Elicitation Requirement Analysis

bardia
Télécharger la présentation

Adaptation of Evolving Requirements : A Managed approach for Non-functional requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Adaptation of Evolving Requirements : A Managed approach for Non-functional requirements Tanya Kudchadker Nivedita Angadi Guides: Dr. A. Serebrenik (TU/e) Martijn Klabbers, ir(LaQuSo)

  2. Requirements Management - Steps Requirement Elicitation Requirement Analysis Requirement Specification Requirement Validation / SET Seminar

  3. Requirements Evolution • Royce 1970, “Waterfall model”. • What is requirements evolution? In which stage does requirements evolution begin? / SET Seminar

  4. Requirements Evolution Cycle / SET Seminar

  5. Driving factors for Requirements Evolution Users need change Changes in the environment Adoption of new technologies Co-operative computing / SET Seminar

  6. Is the requirement acceptable? / SET Seminar

  7. Change Management Process to implement changes in the system. Changes need to be formally introduced and approved. Request For Change(RFC) form / SET Seminar

  8. Change management / SET Seminar

  9. Non functional requirements Why are non-functional requirements(NFR) important? NFRs are often neglected or forgotten. Ineffectively dealing with NFRs can lead to a series of failures in software development. / SET Seminar

  10. The need of the hour A methodical process to assess the consequences of the requirement change. Emphasis on Non-functional requirements. Practical guidelines to accept or reject the proposed change. / SET Seminar

  11. Types of changes / SET Seminar

  12. Process Model Requirement Change Identify change Sequence of steps for handling new or changing requirements during life time of a system. / SET Seminar

  13. Environment Change Identify change in the environment Analyze the change for its effects. / SET Seminar

  14. Requirement Change Identify the possible requirement change to the existing system. / SET Seminar

  15. Impact Analysis • Impact of requirement changes on • Non-functional requirements associated with the proposed change. • Viewpoints of each stakeholder. / SET Seminar

  16. Design Change Identify implications to the existing design of the system. / SET Seminar

  17. Further tasks • Refinement of the process model. • Application of the model on a case study and identify the various non-functional requirements which led to its failure. • E.g. London Ambulance Service Computerised Despatch System(LASCDS) / SET Seminar

  18. Summary Requirements evolution is a continuous process. Various factors drive the initiation of requirements evolution. Acceptance of these changes is a critical task. Non functional requirements play a big role in system ‘well-being’. A practical method/guidelines is a necessary for decision over acceptance of such changes. / SET Seminar

  19. References • Nazim H. Madhavji Juan Fernandez-Ramil, and Dewayne Perry: Software Evolution and Feedback: Theory and Practice. John Wiley & Sons, 2006. • Lam, W., Loomes, M.: Requirements Evolution in the Midst of Environmental Change: A Managed Approach, IEEE Computer Society, 1998 • Cysneiros L.M., Leite J.C.S.P.: Nonfunctional Requirements: From Elicitation to Conceptual Models. IEEE Transaction in Software Engineering, 30(5):328–350, May 2004 / SET Seminar

  20. Questions? / SET Seminar

  21. / SET Seminar

More Related