Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống
1
/ 46 trang
THÔNG TIN TÀI LIỆU
Thông tin cơ bản
Định dạng
Số trang
46
Dung lượng
1,59 MB
Nội dung
Requirement Engineering Lesson 02: The Roles, Skills and Characteritics of the RA It’s not just a simple matter of writing down what the customer says he wants !!! Lecturer: Nguyễn Ngọc Tú Email: Tu.NN79@gmail.com Tu.NguyenNgoc@hoasen.edu.vn Web: sites.google.com/site/kythuatthuthapyeucauphanmem/ Outline Suggested Roles of the RA Skills of the RA Characteristics of an Effective RA 2012.08 Requirement Engineering 2 [1] chapter 02, 03 Learning Outcomes Understand the roles and characteristics of RA 2012.08 Requirement Engineering 3 Issues 2012.08 Requirement Engineering 4 [1] chapter 02, p030 2012.08 Requirement Engineering 5 Suggested Roles of the RA 2012.08 Requirement Engineering 6 [1] chapter 02, p001 Roles 2012.08 Requirement Engineering 7 RA Roles System Initiation System Analysis & Design System Component Design System Inplementation System Integration , Test & Evaluation System Operations & Supports Work collaboratively to identify the real requirements … X X A A A A Work effectively … to manage new and changed requirements … X X X X Be alert to new technologies that may help. X X X reusing artifacts and achieving repeatability. X X X X Assist the project and its customers in envisioning a growth path … X X X X X X Advise the project (and customer) of methods, techniques, and automated tools … X X X Use metrics to measure, track, and control … B X X X X X Be able to facilitate discussions and to mediate conflicts. X X X X X X Study the domain of the area … X X X A—Continue to identify real requirements for subsequent releases and revisions, maintaining configuration control. B—System initiation or “project or task startup” is a confusing time. The experienced RA will be able to lend assistance. For example, the RA should provide a briefing to the project team that includes thetopics noted in Table 5.4. Roles: 1. collaboratively Work collaboratively with customers, users, and system architects and designers to identify the real requirements for a planned system or software development effort to define the problem that needs to be solved. 2012.08 Requirement Engineering 8 Roles: 1. collaboratively Activities involved in performing this work Identifying the stated needs of customers and users. This involves reviewing things previously written about the proposed system, inter -viewing customers and users, studying relevant legislation, and so forth. Studying the business objectives for the proposed effort. Collaborating with customers and users in a joint or cooperative environment to analyze the stated requirements, evolve better requirements, and prioritize them (see the suggested techniques that follow). 2012.08 Requirement Engineering 9 Roles: 1. collaboratively Activities involved in performing this work Involving system architects in requirements development. Iterating the draft or proposed requirements will result in a candidate architecture with better requirements and a more robust architecture. For example, systems need to be able to accommodate changing business needs. The architecture should be designed and developed accordingly, or else the delivered system soon will be outdated. Utilizing an industry strength automated requirements tool to support this work. 2012.08 Requirement Engineering 10 [...]... X X X X K X X Technical writing of requirements deliverables (RTM, SRS, IRS) K X X K X K K X X 18 19 20 21 22 Development, implementation, and use of requirements processes Familiarity with Microsoft Project QA of requirements Requirement Engineering 30 Skills: Num 23 24 25 26 27 28 29 30 31 32 20 12. 08 RA’s Skills Matrix Skills Matrix Requirements allocation (to components, applications, packages)... and provide a resource to the organization Requirement Engineering 25 20 12. 08 Skills of the RA Requirement Engineering 26 20 12. 08 Requirement Engineering 27 20 12. 08 Skills Three levels of Ras Entry/junior-level analyst; Mid-level analyst; Senior-level analyst Requirement Engineering 28 Skills: Num 1 2 3 4 5 6 7 8 9 10 11 20 12. 08 RA’s Skills Matrix Skills Matrix Types of requirements Criteria... system Requirement Engineering 12 Roles: 20 12. 08 2 effectively Requirement Engineering 13 Roles: 20 12. 08 2 effectively – actions must be explained to customers, users, and developers the partnership commitment to project success is maintained must be trained not requirements changes to accept unauthorized should be a joint team Requirement Engineering 14 Roles: 20 12. 08 2 effectively – actions Partnering... Management Requirement Engineering 22 Roles: 20 12. 08 8 facilitate & mediate http://sunset.usc.edu/research/WINWIN/winwin_main.html Requirement Engineering 23 Roles: 20 12. 08 9 Study the domain Be able to grasp, abstract, and express ideas quickly in the users’ language “If not” : he risks limiting his role to that of an order taker Requirement Engineering 24 20 12. 08 Main points ensuring that experienced... baselines in support of specific business objectives Requirement Engineering 20 Roles: 20 12. 08 8 facilitate & mediate people skills (soft skills) negotiating skills, team building, communications, relationships, and leading Two heads are better than one we get even better ideas and approaches! Requirement Engineering 21 Roles: 20 12. 08 8 facilitate & mediate Requirements Elicitation Requirements Verification... Engineering 15 Roles: 20 12. 08 3 Be alert to new technologies Be alert to new technologies that may help advising our customers concerning evolving technology would be well advised to spend additional time and effort learning about new technologies Decision Analysis Resolution (DAR) CMMi Keep the customer involved in these activities Requirement Engineering 16 Roles: 20 12. 08 4 reuse 2 meanings to... cycles, risk management) Requirements justification/rationale Junior K K K K K X Mid X X X X X X Senior X X X X X X K X X K K X X X X K X X K X X Requirement Engineering 29 Skills: 20 12. 08 RA’s Skills Matrix Num Skills Matrix Junior Mid Senior 12 Requirements management tools (e.g., DOORS, RequisitePro) K X X 13 14 15 16 17 Requirements peer review/inspection/walk-through Requirements syntax Requirements... developed work product Requirement Engineering 17 Roles: 20 12. 08 5 growth path helping customers to envision and evolve a series of releases or versions of products is particularly appropriate in the situation in which requirements are not well understood at the outset or the requirements are changing rapidly Requirement Engineering 18 Roles: 20 12. 08 6 to best support is an important role methods... requirements processes Requirements impact estimation (IE) table Junior Mid X X X X Senior X X X X X X X X X X X X X Requirement Engineering 32 Skills: • • • • • • • 20 12. 08 Has a good understanding of the roles of the RA; Is familiar with all roles described in Chapter 2; Experienced in full life cycle activities; Well-developed interpersonal skills and characteristics; Has a through understanding of CM... based on cumulative experiences (Adapted from: Michael Davis.) Requirement Engineering 33 20 12. 08 RA Job Description has the primary responsibility to elicit, analyze, validate, specify, verify, and manage the real needs of the project stakeholders, including customers and end users Requirement Engineering 34 20 12. 08 RA Job Description – Skills Needed Interviewing skills (right questions) . characteristics of RA 20 12. 08 Requirement Engineering 3 Issues 20 12. 08 Requirement Engineering 4 [1] chapter 02, p030 20 12. 08 Requirement Engineering 5 Suggested Roles of the RA 20 12. 08 Requirement. sites.google.com/site/kythuatthuthapyeucauphanmem/ Outline Suggested Roles of the RA Skills of the RA Characteristics of an Effective RA 20 12. 08 Requirement Engineering 2 [1] chapter 02, 03 Learning. functionality 20 12. 08 Requirement Engineering 11 All stakeholders should welcome a “no-impact” requirement that further clarifies the system. 20 12. 08 Requirement Engineering 12 Roles: 2. effectively