1 / 16

Requirements, Architecture and Risks

Requirements, Architecture and Risks. Vahid Jalali. Outline. Motivations Basis for the approach DDP Standard Revised KWIC DDP Matrixes Conclusion. Motivations. Architecture plays a prominent role in large, complex software systems

Download Presentation

Requirements, Architecture and Risks

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. Requirements, Architecture and Risks Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, http://ceit.aut.ac.ir/islab, Requirement engineering course, Fall 2007 Vahid Jalali

  2. Outline • Motivations • Basis for the approach • DDP • Standard • Revised • KWIC • DDP Matrixes • Conclusion Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, http://ceit.aut.ac.ir/islab, Requirement engineering course, Fall 2007

  3. Motivations • Architecture plays a prominent role in large, complex software systems • Selection of an appropriate architecture is critically important development step • Software design for complex software system is difficult • Risk-based reasoning helps in making good architectural decisions Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, http://ceit.aut.ac.ir/islab, Requirement engineering course, Fall 2007

  4. Basis for the approach • Defect Detection and Prevention (DDP) • Requirements • Risks • Mitigations • Steps in Standard DDP • Collection and weighting of requirements • Determining the risks these requirements entail • Listing activities that can mitigate risks • DDP is a quantitative risk-based approach Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, http://ceit.aut.ac.ir/islab, Requirement engineering course, Fall 2007 Requirements Risks Mitigations

  5. Standard DDP Process Determine and weight Requirements Determine Resources List Potential Risks List & Cost Relevant Mitigations Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, http://ceit.aut.ac.ir/islab, Requirement engineering course, Fall 2007 Score Risks against Requirements Score Mitigations against Risks Select Cost-Effective Mitigations Descope/ Reprioritize Requirements Revise Budget, etc Development Plan

  6. Shortcomings of Standard DDP • Distinction between mitigation and design decision • Some mitigations induce and/or exacerbate risks • Induce • Induced risks have a range in [-1,0) • Exacerbate • Exacerbate risks have a range in [-1000000,-1) Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, http://ceit.aut.ac.ir/islab, Requirement engineering course, Fall 2007

  7. Revised DDP Process Determine Resources Determine and weight Requirements List Potential Risks List Relevant Architectures Score Risks against Requirements Score Architectures against Risks Revise selection of architecture Select Software Architecture List Potential Risks List & Cost Relevant Mitigations Score Risks against Architecture Score Mitigations against Risks Revise Budget, etc Select Cost-Effective Mitigations Descope/ Reprioritize Requirements Risk Mitigation Plan

  8. A Case Study • KWIC • The KWIC index system accepts an ordered set of lines • each line is an ordered set of words • each word is an ordered set of characters • Any line may be "circularly shifted" by repeatedly removing the first word and appending it at the end of the line • The KWIC index system outputs a listing of all circular shifts of all lines in alphabetical order Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, http://ceit.aut.ac.ir/islab, Requirement engineering course, Fall 2007

  9. Design Alternatives • Shared data architecture Master Control Input Circular Shift Alphabetizer Output Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, http://ceit.aut.ac.ir/islab, Requirement engineering course, Fall 2007 Characters Index Alphabetized index Input medium Output medium

  10. Design Alternatives (Cont.) • Abstract data type architecture Master Control Input Output Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, http://ceit.aut.ac.ir/islab, Requirement engineering course, Fall 2007 setchar char word setup setchar char word alpha i-th Characters Circular Shift Alphabetic Shifts Output Medium Input Medium

  11. Design Alternatives (Cont.) • Pipes-and-filters architecture Input medium Input Circular shift Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, http://ceit.aut.ac.ir/islab, Requirement engineering course, Fall 2007 Alphabetizer Output Output medium

  12. DDP Matrixes • Risk-Architecture Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, http://ceit.aut.ac.ir/islab, Requirement engineering course, Fall 2007

  13. DDP Matrixes (Cont.) • Risk-Mitigation Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, http://ceit.aut.ac.ir/islab, Requirement engineering course, Fall 2007

  14. Conclusion • Risk can and should be used to guide architectural decisions • Choice of architecture • Decisions flow from the choice • DDP framework is proposed for addressing these problems • Guidelines for checklist in making risks and mitigations quantitative? • Effect of complexity of project on DDP? • Nonfunctional requirements? Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, http://ceit.aut.ac.ir/islab, Requirement engineering course, Fall 2007

  15. Reference • James Kiper and Martin Feather, "Requirements, Architectures and Risks", Proceedings of the Second International Workshop “From Software Requirements to Architectures” (STRAW’03) at the International Conference on Software Engineering, May 2003, pp. 100-106 Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, http://ceit.aut.ac.ir/islab, Requirement engineering course, Fall 2007

  16. Thanks for your attention Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory, http://ceit.aut.ac.ir/islab, Requirement engineering course, Fall 2007

More Related