INFO 380 Information Systems Analysis and Management

1. INFO 380Information Systems Analysis and Management Instructor: Greg Hay TA: Yuan Lin

2. Agenda: Session 9 • Announcements • Use Cases • Personas • Team Effectiveness • Project Teams\Scrum

3. Announcements • Mid-term coming up February 3 (Thursday) • Material on exam through today • Similar to quiz | mostly short-answer • ~20 questions with 80 minutes to complete • 15% of course points • Slide-deck and study guide for review on website

4. Announcements • Homework Write-Up #5 has two alternatives: • The topic posted on class calendar or review new technology on cars presented on NPR January 31. • http://www.npr.org/2011/01/31/133374309/new-car-technology-tells-tailgaters-to-back-off • What are the competitive pressures ‘driving’ this innovation? Who are the stakeholders? Write a brief problem statement that shows the ‘impact’ behind the development of this technology. • Impress me in 500 - 650 words, cite sources

5. Announcements • Undercover Boss • Example of learning via observation • http://www.cbs.com/primetime/undercover_boss/

6. Random thoughts on Midterm • Industry is unsympathetic • ‘Can you do the job?’ • Age, education, gender, language is irrelevant • Knowledge on ‘what’ (any topic) • Assumed • If you don’t know what something is…find out

7. Random thoughts on Midterm • Industry is unsympathetic • Knowledge on ‘how’ & ‘why’ • this is your specialty and your value to employer • REQUIRED: be able advance a conversation

8. Random thoughts on Midterm • Intended to reveal what you know\don’t know • My benefit • I can better understand what is sticking • Your benefit • You can identify missing knowledge • ‘Continuous Process Improvement’ eliminate gaps

9. Random thoughts on Midterm • Intended to reveal what you know\don’t know • Very similar to a technical job interview • No multiple choice • No true\false • Whiteboard Opportunity • Succeed or fail spectacularly (no hiding) • Be comfortable with having knowledge exposed

10. Questions?

11. Brief Discussion on Egypt

12. Brief Discussion on Egypt • What are the competitive pressures? • What role does information have in this crisis?

13. User-Centered Development • A process of systems development based on understanding the needs of stakeholders • System development focus on ‘why’ vs ‘how’

14. Use Case Modeling • A process of modeling a system’s functions • business events • who initiated the events • how the system responds to those events

15. Use Case Modeling • Originated relatively recently (1986) • Dr. Ivar Jacobson • Object-Oriented Software Engineering • now considered an industry best practice

16. Use Case Modeling • Tool to facilitate communication • Creates common understanding • Project team members • Clients\customers • Describes system’s behavior • Specific scenarios or common business events

17. Use Case Modeling • Focuses on one of stakeholders • ‘primary actor’ • Interact with system to accomplish desired goal

18. Use Case Modeling • Examples • Buy jeans at Nordstrom • Register for class at UW • Buy coffee at Tully’s

19. Use Case Modeling • Benefits • Solves primary challenges in system development • elicit correct system requirements from stakeholders • specify requirements in manner understandable • can be verified and validated

20. Use Case Modeling • High-Level • Tool for capturing functional requirements • Decomposes system into manageable pieces • Provides means of identifying, assigning, tracking, controlling, and management system development activities • Helps estimate project scope and schedule

21. Use Case Modeling • Components/Terms • Primary Actor • Other Participating Actors • Stakeholders and Interests

22. Use Case Modeling • Components/Terms • Precondition • Trigger • Temporal Event: • Typical Course of Events (Scenario) • Alternate Courses

23. Questions?

24. Use Case: Actors 4 types • Primary Business Actor • Stakeholder that primarily benefits from the execution of the use case • Example: employee receiving the paycheck

25. Use Case: Actors 4 types • Primary System Actor • Stakeholder that directly interfaces with system • Initiates\triggers the business or system event • Example: bank teller entering deposit information

26. Use Case: Actors 4 types • External Server Actor • Stakeholder responding to request of use case • Example: credit bureau authorizing a credit card

27. Use Case: Actors 4 types • External Receiver Actor • Stakeholder that is not the primary actor but receives something of value from the use case • Example: warehouse receives packing slip

28. Use Case Modeling • Elicit and analyze user requirements • Communicates required from a user perspective • Free of details of how system will be implemented • Two artifacts • Use-Case Diagram • Use-Case Narrative

29. Use Case: Example

32. Use Case Modeling • Steps • Identify business actors • Identify business use cases • Construct use-case model diagram • Business requirements use-case narratives

33. Step 1: Look for Actors • Ask the following questions: • Who or what provides inputs to the system? • Who or what receives outputs from the system? • Are interfaces required to other systems? • Are there events that are automatically triggered at a predetermined time? • Who will maintain information in the system? • Should be named with noun or noun phrase

34. Step 2: Look for Use Cases • Identify Business Requirements Use Cases • Capture interactions between user and system • Free of technology and implementation details

35. Step 2: Look for Use Cases • Ask the following questions: • What are the main tasks of the actor? • What information does actor need from system? • What information does actor provide to system? • Does the system need to inform the actor of any changes or events that have occurred? • Does the actor need to inform the system of any changes or events that have occurred?

36. Step 3: Construct Diagram

37. Step 4: Document Narratives • Business Requirements Use-Case Narratives • High level at first • Allows to quickly obtain an understanding of the events and magnitude of the system

38. Step 4: Document Narratives • Business Requirements Use-Case Narratives • Expand: documented business requirement narrative • use case’s typical course of events • alternate courses or exceptions

39. Use Case for Project Management • Can drive entire development effort • Tool to estimate/schedule project build cycles • Build cycles are prioritized • Importance of the use case • Dependencies • Development time

40. Use Case for Project Management • Setting priorities includes creating: • Use-case ranking and evaluation matrix • Use-case dependency diagram

41. Questions?

42. Personas • What is a persona?

43. Personas • What does a persona represent?

44. Personas • How do we build a persona?

45. Personas • What characteristics go into a persona?

46. Personas • What are the benefits of a persona?

47. Questions?

48. Team Analysis • How is the team-thing going?

49. Team Analysis • One more single-word for simplicity: Trust

50. Team Analysis • Trust • You will follow-through on tasks • Ask for help when things go sideways • Do what you say\say what you do