tailieunhanh - Chương 2: Domain Understanding & Requirements Elicitation

Identifying improvement objectives; organizational & technical constraints on systemtobe; alternative options for satisfying objectives, for assigning responsibilities; scenarios of hypothetical softwareenvironment interaction. | Requirements Engineering From System Goals to UML Models to Software Specifications Axel Van Lamsweerde Fundamentals of RE Chapter 2 Domain Understanding & Requirements Elicitation start Chap. 2: Elicitation techniques alternative options agreed requirements documented requirements consolidated requirements : RE products and processes A great deal of knowledge acquisition is involved: as introduced in Chapter 1 . Studying the system-as-is Business organization: structure, dependencies, strategic objectives, policies, workflows, operational procedures, . Application domain: concepts, objectives, tasks, constraints, regulations, . Analysis of problems with system-as-is: symptoms, causes, consequences Analyzing technology opportunities, new market conditions Identifying the system stakeholders Identifying improvement objectives; organizational & technical constraints on system-to-be; alternative options for satisfying objectives, for assigning responsibilities; scenarios of hypothetical software-environment interaction; requirements on software, assumptions on environment Domain analysis & requirements elicitation: outline Identifying stakeholders & interacting with them Artefact-driven elicitation techniques Background study Data collection, questionnaires Repertory grids, card sorts for concept acquisition Scenarios, storyboards for problem world exploration Prototypes, mock-ups for early feedback Knowledge reuse: domain-independent, domain-specific Stakeholder-driven elicitation techniques Interviews Observation and ethnographic studies Group sessions Stakeholder analysis Stakeholder cooperation is essential for successful RE Elicitation = cooperative learning Representative sample must be selected to ensure adequate, comprehensive coverage of the problem world dynamic selection as new knowledge is acquired Selection based on . relevant position in the organization (ex. Sale person) role in making decisions, reaching agreement type of . | Requirements Engineering From System Goals to UML Models to Software Specifications Axel Van Lamsweerde Fundamentals of RE Chapter 2 Domain Understanding & Requirements Elicitation start Chap. 2: Elicitation techniques alternative options agreed requirements documented requirements consolidated requirements : RE products and processes A great deal of knowledge acquisition is involved: as introduced in Chapter 1 . Studying the system-as-is Business organization: structure, dependencies, strategic objectives, policies, workflows, operational procedures, . Application domain: concepts, objectives, tasks, constraints, regulations, . Analysis of problems with system-as-is: symptoms, causes, consequences Analyzing technology opportunities, new market conditions Identifying the system stakeholders Identifying improvement objectives; organizational & technical constraints on system-to-be; alternative options for satisfying objectives, for assigning responsibilities; scenarios