[計(jì)算機(jī)]bis601_20xx_1_01b_re(已修改)
2025-01-31 17:11 本頁面
【正文】 ./college/van lamsweerde : Setting the Scene 169。 2022 John Wiley and Sons 1 Requirements Engineering From System Goals to UML Models to Software Specifications Axel Van Lamsweerde ./college/van lamsweerde : Setting the Scene 169。 2022 John Wiley and Sons 2 Fundamentals of RE Chapter 1 Setting the Scene (Part 2) 3 ./college/van lamsweerde : Setting the Scene 169。 2022 John Wiley and Sons Categories of requirements ? Functional requirements: prescribe what services the softwaretobe should provide – capture intended software effects on environment – units of functionality resulting from software operations “The software shall control the acceleration of all trains” ? Nonfunctional requirements: constrain how such services should be provided – Quality requirements: safety, security, accuracy, time/space performance, usability, ... – Others: pliance, architectural, development reqs – To be made precise in systemspecific terms “Acceleration mands shall be issued every 3 seconds to every train” 4 ./college/van lamsweerde : Setting the Scene 169。 2022 John Wiley and Sons A taxonomy of nonfunctional requirements NonFunctional Requirement Quality of Service Compliance Architectural Constraint Development Constraint Confidentiality Integrity Availability Distribution Installation Safety Security Usability Performance Reliability Maintainability Cost Time Space Deadline Variability Software interoperability Convenience Interface User interaction Device interaction Subclass link Accuracy Cost ? See definitions and examples in supplement ? No clearcut boundaries, possible overlaps – Functional/nonfunctional: . functional reqs for firewall management are securityrelated – Nonfunctional overlaps: . “high frequency of train mands” is related to performance and safety 5 ./college/van lamsweerde : Setting the Scene 169。 2022 John Wiley and Sons Requirements taxonomies are helpful ... ? More specific definition of what requirements are ? More semantic characterization of requirements ... – prescribing desired behaviors . many functional reqs – ruling out unacceptable behaviors . many safety, security, accuracy reqs – indicating preferred behaviors . soft, “ility” reqs ? Elicitation/analysis can be guided by taxonomy browsing – Is there any confidentiality req on information X ? – Is there any accuracy req on information Y ? – Is there any conflict between confidentiality and accountability reqs in my system? 6 ./college/van lamsweerde : Setting the Scene 169。 2022 John Wiley and Sons Setting the scene: outline ? What is Requirements Engineering? – The problem world amp。 the machine solution – The scope of RE: the WHY, WHAT and WHO dimensions – Types of statements involved: descriptive vs. prescriptive – Categories of requirements: functional vs. nonfunctional – The requirements lifecycle: actors, processes, products – Target qualities and defects to avoid – Types of software projects – Requirements in the software lifecycle – Relationship to other disciplines 7 ./college/van lamsweerde : Setting the Scene 169。 2022 John Wiley and Sons The RE process (1) start domain understanding amp。 elicitation alternative proposals 8 ./college/van lamsweerde : Setting the Scene 169。 2022 John Wiley and Sons Domain understanding ? Studying the systemasis – Business anization: structure, dependencies, strategic objectives, policies, workflows, operational procedures, ... – Application domain: concepts, objectives, tasks, constraints, regulations, ... – Strengths amp。 weaknesses of the systemasis ? Identifying the system stakeholders: – Groups or individuals affected by the systemtobe, who may influence its elaboration and its acceptance – Decision makers, managers, domain experts, users, clients, subcontractors, analysts, developers, ... Products: Initial sections for preliminary draft proposal Glossary of terms 9 ./college/van lamsweerde : Setting the Scene 169。 2022 John Wiley and Sons Requirements elicitation Exploring the problem world ... ? Further analysis of problems with systemasis: symptoms, causes, consequences ? Analysis of technology opportunities, new market cond
教學(xué)課件相關(guān)推薦
鄂ICP備17016276號-1