Requirements Engineering Lecturer: Peng Liang Unit 1: Office: - PowerPoint PPT Presentation

9/ 1/ 2009 | 1/ 66 9/ 1/ 2009 | 2/ 77 Course information Requirements Engineering › Lecturer: Peng Liang Unit 1: › Office: Bernoulliborg V 5161.576 Basic of requirements engineering › Phone: 050-363 7480 › E-mail: p.liang at rug.nl › Department of Computer Science / Peng Liang › Contact: by email or appointment › Course website: › Rijksuniversiteit Groningen (RUG) http:/ / www.cs.rug.nl/ ~liangp/ teaching/ courses/ RE2009Fall/ › http:/ / www.cs.rug.nl/ ~liangp/ teaching/ courses/ RE2009Fall/ ( slides, assignm ent deadlines, schedule, resources, reading list, etc. ) Peng Liang Requirements Engineering 2009 Fall Peng Liang Requirements Engineering 2009 Fall 9/ 1/ 2009 | 3/ 77 9/ 1/ 2009 | 4/ 77 Course schedule Course schedule every week Lecture session 11:15-14:00 V 5161.0253 Mon Tue Wed Thu Fri (Week 42@X 5118.-156) Tue (Week 36-43) * Tutorial session 13:15-15:00 X 5118.-149 11:15 Thu (Week 36-43) lecture 13:15 14 :0 0 tutorial 15:15-16:00 V 5161.0208 * Lab session 15:0 0 Thu (Week 36-43) 15:15 lab Course project presentation by group Sem inar days 16:0 0 (Week 43, 20.10.2009) (using lecture session) 13:00-16:00 Tennishal Exam (30.10.2009) * Tutorial sessions is used for group project discussion and meetings. 2 nd Exam (05-02-2010) 09:00-12:00 X 5113.0201 * Lab sessions are is used for requirements documentation in REWiki. Peng Liang Requirements Engineering 2009 Fall Peng Liang Requirements Engineering 2009 Fall

9/ 1/ 2009 | 5/ 77 9/ 1/ 2009 | 6/ 77 Course rules Course bibliography › No single textbook covers the field well › Team work more important than written exam • A. van Lamsweerde. Requirem ents engineering: from sy stem goa ls to UML m od els to softw a re sp ecifica tions . John Wiley & Sons, 2009 › Take a pen(cil) and paper for the course • L.A. Maciaszek. Requirem ents a na ly sis a nd sy stem d esign (3rd edition) . Pearson Addison-Wesley, 2007 › Pose questions whenever you want • D. Leffingwell and D. Widrig. Ma na ging softw a re requirem ents: A Use Ca se Ap p roa ch . Addison-Wesley, 2003. • G. Kotonya and I. Sommerville. Requirem ents Engineering: Processes a nd Techniques . John Wiley & Sons, 1998. • I. Sommerville and P. Sawyer. Requirem ents Engineering: A Good Pra ctice Guid e . John Wiley & Sons, 1997. • R.J. Wieringa. Requirem ents Engineering: Fra m ew orks for Und ersta nd ing . Wiley, 1996. › This course is practice-oriented • All papers and book links are available on the course website Peng Liang Requirements Engineering 2009 Fall Peng Liang Requirements Engineering 2009 Fall 9/ 1/ 2009 | 7/ 77 9/ 1/ 2009 | 8/ 77 Course objectives Fundamental skills › Explore the state-of-the-art practice in › Interviewing and teamwork skills for requirements Requirements Engineering elicitation and validation • Techniques, notations, methods, processes, and tools › Analysis and modelling skill for problem solving › Writing skill for requirements specification › Gain practical experience in mature Requirements Engineering techniques • Elicit, analyze, document, validate, and manage requirements Peng Liang Requirements Engineering 2009 Fall Peng Liang Requirements Engineering 2009 Fall

9/ 1/ 2009 | 9/ 77 9/ 1/ 2009 | 10/ 77 Course outline Course content explanation Requirem ents engineering › Expectations from RE course 2008 Requirem ents engineering process › Software engineering and RE course › Zooming in requirements engineering Requirem ents elicitation › Course limitations Requirem ents docum entation Requirem ent Requirem ent negotiation analysis Requirem ents m anagem ent Requirem ent validation Peng Liang Requirements Engineering 2009 Fall Peng Liang Requirements Engineering 2009 Fall 9/ 1/ 2009 | 11/ 77 9/ 1/ 2009 | 12/ 77 Expectations from RE course 2008 SE course and RE course › RE as a subset of SE › Show us the step-by-step method to examine and document the needs of use case customers; Software SE m odeling process RE › Apply the methods in practices with a FR & NFR project; project Software m anagem ent evolution RE process › New information other than content already introduced in SE, SDP courses; bug tracking Software strategy architecture patterns Peng Liang Requirements Engineering 2009 Fall Peng Liang Requirements Engineering 2009 Fall

all these topics based on concrete examples and projects. 9/ 1/ 2009 | 13/ 77 9/ 1/ 2009 | 14/ 77 Zooming in requirements engineering Example - detail topics on RE Requirem ents › How to start a RE process, and proceed step by step? triage Goals What specific information should we collect and Requirem ents decom position prioritization acquire? (handbook) › How to identify the stakeholders in a large project? RE RE tools, Resolving (experience) DOORS, IRqA, conflicting requirem ents RequisitPro › How to perform specific requirement elicitation Requirem ents methods, and use them in a real project? (practices) tractability Techniques on › How to model the requirements using different How to write Requirem ents modeling approaches? (practices) validation good requirem ents Peng Liang Requirements Engineering 2009 Fall Peng Liang Requirements Engineering 2009 Fall 9/ 1/ 2009 | 15/ 77 9/ 1/ 2009 | 16/ 77 Course limitations Course grading › We have not real industrial projects, but we can try › 50%: Group project some projects smaller • Requirement report (in English) based on a › We are not working on a real project environment, practical software project but we can simulate it • Project presentation per group › 20%: Individual assignment › We learn RE knowledge, but still you have to apply › 30%: Final written exam them into large and complex industrial projects Peng Liang Requirements Engineering 2009 Fall Peng Liang Requirements Engineering 2009 Fall

9/ 1/ 2009 | 17/ 77 9/ 1/ 2009 | 18/ 77 Group project Group project › Learning by role playing › Each team consists of 5-6 students • to simulate a real small project team › interviewing, soft skill, communication styles › Each team propose an appropriate project • to simulate a real customer › Instructor coordinates the assignment of projects • to choose the project your group likes › To complete this project by role playing • to simulate a real environment of a project Peng Liang Requirements Engineering 2009 Fall Peng Liang Requirements Engineering 2009 Fall 9/ 1/ 2009 | 19/ 77 9/ 1/ 2009 | 20/ 77 Role playing Team composition As Developer team › Roles played by team Team A • As Developer team & Customer team Requirem ents Adm inistrative Team Leader › Roles played by individual student Engineer Assistant • Developer team: team leader, administrative assistant, requirements engineer As Custom er team • Customer team: domain expert, end-user Dom ain Expert End-user Peng Liang Requirements Engineering 2009 Fall Peng Liang Requirements Engineering 2009 Fall

9/ 1/ 2009 | 21/ 77 9/ 1/ 2009 | 22/ 77 Role’s responsibility Team interaction › Team leader: allocate responsibilities, prepare the agenda for w eekly m eeting w ith custom er team Team A Team B Team C Team D › Administrative assistant: in charge of m inutes taking during Developer Developer Developer Developer m eetings › Requirements engineer: to elicit, analyze, specify, validate, and m anage requirem ents › Domain expert: person w ith special know ledge or skills in a Team B Team C Team D Team A particular area (e.g., expert on library m anagem ent ) Custom er Custom er Custom er Custom er › End-user: person w ho w ill directly use the system being developed (e.g., librarian) Peng Liang Requirements Engineering 2009 Fall Peng Liang Requirements Engineering 2009 Fall 9/ 1/ 2009 | 23/ 77 9/ 1/ 2009 | 24/ 77 Meeting schedule every week Meeting schedule every week prepare an agenda for External meeting Team A 1 1 the meeting and points between developer and Developer to be discussed, and Team Leader Team Leader customer teams should distribute it to all be short and productive 2 stakeholders (less than 45 minutes). Team B Custom er <45 min Peng Liang Requirements Engineering 2009 Fall Peng Liang Requirements Engineering 2009 Fall

Document the requirements 9/ 1/ 2009 | 25/ 77 using REWiki 9/ 1/ 2009 | 26/ 77 Meeting schedule every week Meeting schedule every week 4 3 3 Team A Team A 1 1 Developer Developer Team A Team Leader Team Leader Developer Team A Team A 2 2 Developer Developer Internal discussion to solve the issues posed Team B Team B by customer team Custom er Custom er 30~45 min 30~45 min 30~45 min <45 min <45 min Peng Liang Requirements Engineering 2009 Fall Peng Liang Requirements Engineering 2009 Fall 9/ 1/ 2009 | 27/ 77 9/ 1/ 2009 | 28/ 77 Meeting schedule every week Submissions every week 4 › Meeting agenda (by Team leader ) 3 Team A 1 Thu › Meeting minutes (by Adm inistrative assistant ) Developer Team A Team Leader › I will check your online work on REWiki based on Developer Team A 45 min * 2 these two documents 2 Developer tutorial Team B lab Custom er 45 min 30~45 min 30~45 min <45 min Peng Liang Requirements Engineering 2009 Fall Peng Liang Requirements Engineering 2009 Fall