slike môn thu thập và phân tích yêu cầu nguyễn ngọc tú chương 3 kiểu yêu cầu thu thập yêu cầu

23 345 0
slike môn thu thập và phân tích yêu cầu nguyễn ngọc tú chương 3 kiểu yêu cầu thu thập yêu cầu

Đang tải... (xem toàn văn)

Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống

Thông tin tài liệu

It’s not just a simple matter of writing down what the customer says he wants !!! Requirement Engineering Lesson 03+04: Types of Requirements Lecturer: Email: Web: Nguyễn Ngọc Tú Tu.NN79@gmail.com Tu.NguyenNgoc@hoasen.edu.vn sites.google.com/site/kythuatthuthapyeucauphanmem/ 2012.08 Learning Outcomes  Identify requirement types Requirement Engineering 2012.08 Outline  Views of Requirements Types  Definitions and Descriptions of Requirements Types  Terminologies to Avoid  Examples of Requirements Types  Case Study [1] chapter 04 Requirement Engineering 2012.08 Views of Requirements Types  Some different ways to organize requirements types Hardware requirements: Performance requirements Constraints: Interface requirements Specialty engineering requirements Environmental requirements Software requirements: Functional requirements Nonfunctional requirements Requirement Engineering 2012.08 Views of Requirements Types Requirement Engineering 2012.08 Views of Requirements Types Requirement Engineering 2012.08 Views of Requirements Types Business Why the project is being undertaken User requirements What users will be able to with the product Software requirements What developers need to build Requirement Engineering 2012.08 Definitions and Descriptions  Customer needs and expectations:      Business requirements; User requirements; Product requirements; Environmental requirements; Unknowable requirements  These are analyzed by the requirements analyst and described in different ways:    High-level (or system-level) requirements; Functional requirements (what the system must do); Nonfunctional requirements:  System properties (e.g., safety);  The “ilities/specialty engineering requirements.” Requirement Engineering 2012.08 Definitions and Descriptions     system The system requirements are allocated into:    Derived requirements and design constraints; Performance requirements (e.g., how fast?); Interface requirements (relationships between elements); Subsystems (logical groupings of functions); Components of the system (hardware, software, training, documentation) Checks are done to ensure the system does what it is supposed to do, incorporating:    Verified requirements; Validated requirements; Qualification requirements Requirement Engineering 10 2012.08 Definitions and Descriptions  Business requirements    Real requirements   are the essential activities of an enterprise are derived from business goals identifying omitted requirements is a key task Business rules  provide the basis for creating the functional requirements The policies, conditions, and constraints of the business activities supported by the system;  The decision processes, guidelines, and controls behind the functional requirements (e.g., procedures);  Definitions used by the business;  Relationships and workflows in the business;  Knowledge needed to perform actions  Requirement Engineering 11 2012.08 Definitions and Descriptions  Functional Requirements Requirement Engineering 12 2012.08 Terminologies to Avoid      Source or Customer Requirements Nonnegotiable Versus Negotiable Requirements Key Requirements Originating Requirements Others:      Avoid using vague terminology Avoid putting more than one requirement in a requirement Avoid clauses like “if that should be necessary.” Avoid wishful thinking: 100% reliability, running on all platforms, pleasing all users, handling all unexpected failures Requirement Engineering 13 2012.08 Q/A ?! Requirement Engineering It’s not just a simple matter of writing down what the customer says he wants !!! Requirement Engineering Lesson 04: Gathering Requirements Lecturer: Email: Web: Nguyễn Ngọc Tú Tu.NN79@gmail.com Tu.NguyenNgoc@hoasen.edu.vn sites.google.com/site/kythuatthuthapyeucauphanmem/ 15 2012.08 Learning Outcomes  Understand about gathering requirements Requirement Engineering 16 2012.08 Issues  A lot of time and effort is wasted in the project startup phase and in performing requirements gathering activities        The project is just getting organized and things are confused There is no road map or checklist of startup activities Not all staff are present; some are still being recruited There isn’t much pressure to meet the schedule yet The customer and users are also trying to get organized and get started The staff who will be working on end-product development may not fully understand the customer’s objectives and, consequently, may not be able to appreciate the customer’s expectations An effective proven procedure for the requirements gathering steps is not available or used [1] chapter 05, p070 Requirement Engineering 17 2012.08 Outline  Key practices  Plan the Approach  Case Study [1] chapter 05 Requirement Engineering 18 2012.08 Key practices  Develop a clear vision for the end product  Develop a well defined, shared understanding of the project scope  Involve stakeholders throughout the requirements process  Represent and discover requirements using multiple models  Document the requirements clearly and consistently  Continually validate that the requirements are the right ones to focus on  Verify the quality of the requirements early and frequently Requirement Engineering 19 2012.08 Key practices  Prioritize the requirements and remove unnecessary ones  Establish a baseline for requirements (i.e., a “snapshot in time” of the reviewed and agreed-upon requirements that will serve as a basis for  further development)  Trace the requirements’ origins and how they link to other requirement and system elements  Anticipate and manage any requirements changes Requirement Engineering 20 2012.08 Plan the Approach Step 10 Action or Activity Review related historical information Review related organizational policies Identify the stakeholders of the project Develop a strategy to involve customers and users throughout the development effort Write (and iterate) a project vision and scope document Develop a requirements plan Provide for peer reviews and inspections of all requirementsrelated work products Initiate a project glossary and a project acronyms list Decide on the life-cycle approach to be used on the project Begin tailoring of the corporate (or other) requirements process [1] chapter 05, p001 Requirement Engineering 21 2012.08 Plan the Approach Step 11 12 13 14 15 16 17 18 19 Action or Activity Establish a mechanism to evolve the real requirements from the stated requirements Provide requirements-related training for project participants, including customers and users, and for RAs Rewrite the high-level system or software requirements as you proceed through the initial steps Initiate development of the real requirements based on the stated Initiate documentation of the rationale for each requirement Establish a mechanism to control changes to requirements and new Perform the verification approach and validation planning Select the practices, methods, and techniques that will be used to Begin consideration and selection of an automated requirements tool, identification of the attributes that will be needed for each requirement, and the composition of the requirements repository [1] chapter 05, p001 Requirement Engineering 22 2012.08 Plan the Approach Step 20 21 22 23 24 25 26 27 28 Action or Activity Select and acquire the automated requirements tool Load the initial real requirements into the selected requirements tool, label each requirement uniquely, and initiate assignment of appropriate attributes information to each requirement Perform requirements gathering Involve system architects and designers in reviews of the Develop the traceability strategy to be used Identify the requirements that will be met in the first release or initial products (prioritize real requirements) Establish an approach for a proof of concept, prototype, or other approximation of the work product Incorporate requirements best practices and garner management support for effective requirements engineering (including an Complete requirements gathering for the first release [1] chapter 05, p001 Requirement Engineering 23 2012.08 Q/A ?! Requirement Engineering ... Lesson 04: Gathering Requirements Lecturer: Email: Web: Nguyễn Ngọc Tú Tu.NN79@gmail.com Tu.NguyenNgoc@hoasen.edu.vn sites.google.com/site/kythuatthuthapyeucauphanmem/ 15 2012.08 Learning Outcomes... on all platforms, pleasing all users, handling all unexpected failures Requirement Engineering 13 2012.08 Q/A ?! Requirement Engineering It’s not just a simple matter of writing down what the... requirements process [1] chapter 05, p001 Requirement Engineering 21 2012.08 Plan the Approach Step 11 12 13 14 15 16 17 18 19 Action or Activity Establish a mechanism to evolve the real requirements from

Ngày đăng: 23/10/2014, 09:05

Từ khóa liên quan

Tài liệu cùng người dùng

  • Đang cập nhật ...

Tài liệu liên quan