1. Use-Cases Elicitation and FAST Copyright, 2003 © Jerzy R. Nawrocki Jerzy.Nawrocki@put.poznan.pl www.cs.put.poznan.pl/jnawrocki/require/ Requirements Engineering Lecture 4 Requirements Engineering Lecture 4

2. J. Nawrocki, Use-Cases Elicitation.. BibliographyBibliography IEEE Guide for Information Technology – System Definition - Concept of Operations (ConOps) Document, IEEE Std 1362-1998, March 1998. S. Adolph, P. Bramble, A. Cockburn, A. Pols, Patterns for Effective Use Cases, Addison- Wesley, Boston, 2003. 

3. J. Nawrocki, Use-Cases Elicitation.. ContentsContents Use Cases Elicitation Patterns FAST Technique Inception Steps

4. J. Nawrocki, Use-Cases Elicitation.. The Team Small Writing Team Small Writing Team: Restrict the number of people refining any one work product to just two or three people. Participating Audience Participating Audience: Actively involve your customer and internal stakeholders in the use case development process when possible. Balanced Team Balanced Team: Staff the team with people from different specialties. Make sure the team contains both developers and end users.

5. J. Nawrocki, Use-Cases Elicitation.. The Process - 1 Breadth Before Depth Breadth Before Depth: Conserve your energy by developing an overview of your use cases first, then progressively add detail. Spiral Development Spiral Development: Develop use cases in an iterative, breadth-first manner, with each iteration prograssively increasing the precision and accuracy. Multiple Forms Multiple Forms: Select the format based on the risks associated with the project and the preferences of the people involved.

6. J. Nawrocki, Use-Cases Elicitation.. Short Format Actor Administrator Use Case Set Monitor Parameters Select MonitorDescription Person monitoring and controlling job control systemDescription Allow administrator to specify boundaries and Precision of items being monitored Choose something to monitor (e.g. a process or wait queue)

7. J. Nawrocki, Use-Cases Elicitation.. Fully Dressed Format Buy Something Primary Actor Primary Actor: Requestor Goal in Context Goal in Context: Requestor buys something through the system, gets it. Does not include paying for it. Scope Scope: Business – The overall purchasing mechanism, electronic adn non-electronic, as seen by the people in the company. Level Level: Summary Stakeholders and Interests Requestor Requestor: Wants what he/she ordered. Company Company: Wants to control spending but allow needed purchases. Vendor Vendor: Wants to get paid for any goods delivered. Precondition Precondition: None

8. J. Nawrocki, Use-Cases Elicitation.. Fully Dressed Format Success Guarantees Success Guarantees: Requestor has goods, correct budet ready do be debited. Trigger Trigger: Requestor decides to buy something. Main Success Scenario 1.Requestor 1.Requestor: Initiate a request. 2.Approver 2.Approver: Check money in the budget, check price of goods, complete request for submission. 3.Buyer 3.Buyer: Check contents of storage, find best vendor for goods. 4.Authorizer 4.Authorizer: Validate Approver’s signature....Extensions 1a. Requestor does not know vendor or price: leave those parts blank and continue.

9. J. Nawrocki, Use-Cases Elicitation.. Fully Dressed Format Priority Priority: Various Response Time Response Time: Various Frequency Frequency: Three times a day Channel to Primary Actor Channel to Primary Actor: Internet browser, mail system, or equivalent Channels to Secondary Actors Channels to Secondary Actors: Fax, phone, car Open Issues Open Issues: When is a canceled request deleted from the system? What authorization is needed to cancel a request?

10. J. Nawrocki, Use-Cases Elicitation.. The Process - 2 Two Tier Review Two Tier Review: Hold two types of review: The first by a smaller, internal team, possibly repeated many times; the second by the complete group, perhaps just once. Quitting Time Quitting Time: Stop developing use cases once they are complete and satisfactorily meet audience needs. Writers Lincense Writers Lincense: Small diffrences in writing style are inevitable.

11. J. Nawrocki, Use-Cases Elicitation.. ContentsContents Use Cases Elicitation Patterns FAST Technique Inception Steps

12. J. Nawrocki, Use-Cases Elicitation.. Developers Customers FASTFAST FAST = Facilitated Application Specification Technique JAD Joint Application Development - another approach to FAST Facilitator Recorder

13. J. Nawrocki, Use-Cases Elicitation.. FASTFAST Facilitator - runs the meeting(s) Recorder - takes notes, serves tape recorder or video recorder Developers & customer representatives - work on requirements Senior manager - knows about the meeting date & time Persons involved

14. J. Nawrocki, Use-Cases Elicitation.. FASTFAST The list of stakeholders should be ready before the project leaders start to organise the first FAST meeting. Get from the customer the initial list of requirements sources (manuals, organisation charts, technical data,..) and read it before the meeting. Conducting a FAST meeting via phone or e-mail should be avoided. Before the first meeting

15. J. Nawrocki, Use-Cases Elicitation.. FASTFAST Product request (  Project Proposal) Aim & goals of the meeting Agenda for the meeting Information about place and time Input documents

16. J. Nawrocki, Use-Cases Elicitation.. FASTFAST A worksheet to fill in Missing stakeholders Missing features and use cases Use cases description Input documents

17. J. Nawrocki, Use-Cases Elicitation.. FASTFAST Product justification (consensus) Presentation of the worksheets (one by one, no critique) Deciding (discussion) about: Stakeholders Their goals Features and use cases (at different levels) Value and cost (priority) An agenda example

18. J. Nawrocki, Use-Cases Elicitation.. ContentsContents Use Cases Elicitation Patterns FAST Technique Inception Steps

19. J. Nawrocki, Use-Cases Elicitation.. Inception – Step 1 7-8.10.2004 Discuss: Project Mandate Project Mandate Project Management Team Vision of the Product Project web page address

20. J. Nawrocki, Use-Cases Elicitation..

22. Inception – Step 1 7-8.10.2004 Discuss: Project Mandate Project Management Team Project Management Team Vision of the Product Project web page address

23. J. Nawrocki, Use-Cases Elicitation.. SDS Project Organisation Project Board Project Assurance 5 th year students Project Support 3rd year student Analyst 4th year student Senior User Customer Executive Customer Senior Supplier MJ | BW Project Supervisor Project Manager 4th year student Team 3rd year students

24. J. Nawrocki, Use-Cases Elicitation..

26. Inception – Step 1 7-8.10.2004 Discuss: Project Mandate Project Management Team Vision of the Product Vision of the Product Project web page address

27. J. Nawrocki, Use-Cases Elicitation..

29. Inception – Step 2 14-15.10.2004 Review: Project Management Team Vision of the Product Check if the project web page is ready (Mandate + PMT + Vision) Discuss: Operational Scenarios, Version1 (Use Cases) Glossary, Version 1

30. J. Nawrocki, Use-Cases Elicitation.. Inception – Step 3 21-22.10.2004 Review: Operational Scenarios, Version1 (Use Cases) Glossary, Version 1 Discuss: Operational Scenarios, Version 2 (Use Cases) Glossary, Version 2 Project Approach (outline of the Software Development Plan) Project Initiation Plan Risk Factors

31. J. Nawrocki, Use-Cases Elicitation.. Inception – Step 4 28-29.10.2004 Review: Project Brief (PMT + Vision + Operational Scenarios + Glossary + Risk factors) Project Approach (outline of the Software Development Plan) Project Initiation Plan Seek approval of the Project Initiation Plan

32. J. Nawrocki, Use-Cases Elicitation..

33. SummarySummary Use cases elicitation practices: Small Writing Team Breadth Before Depth Spiral Development Multiple Forms Two Tier Review Quitting Time FAST Inception phase details

34. J. Nawrocki, Use-Cases Elicitation.. Quality assessment 1. What is your general impression? (1 - 6) 2. Was it too slow or too fast? 3. What important did you learn during the lecture? 4. What to improve and how?