Day 10 – Analysis Activities

1. Day 10 – Analysis Activities • Analysis Tasks • Inception Phase • Build Phase (A-D-C-R iterations) • Managing Client Expectations • Prototypes • Overview Graphics • Evaluation Tables • Tips for • Client Project Delivery 1 – Project Charter (10/03) • Midterm Exam (10/17)

2. Analysis tasks in Inception Phase • High level analysis: • Scope (goals, • objectives, budget, • feasibility w/in • organization) • Look & feel Analyze functional requirements one module at a time for people, data, information, software & hardware. Document functional requirements specific to each module. Task order, iteration, and collaboration with users will depend on project characteristics. Include testing every phase + review

3. Inception - Early Look & Feel • Initial (quick) resources • Existing site(s) within organization • Competing sites • Best practice sites & client favorites • Prototypes • Review with key clients • Create “template”

4. Why is determining requirements so difficult? (i.e. What are the challenges?)

5. A view of the challenge

6. Why is determining requirements so important?

8. Client communication • Prototypes • System Overview Graphics • Goal: To communicate with the client in terms they can understand

9. Wireframe Version 1.0

11. Project Example: Defining Scope & Expectations • Project • Develop a business intelligence performance management and portal solution for a charter school organization • Challenge • Deliver all the required functionality within tight timeline (school calendar) and budget (funding) parameters • Solution • Listen – clients may not have an IT background, so be careful of using IT lingo. Use graphics to help the client understand what the solution can do and how they would use the functionality. • Prioritize – help the client identify those that are of the most important business value. • Maintain scope – balance priority and feasibility and provide alternatives • Prototype – visuals are a great way to make a concept more ‘tangible’ • Confirm, confirm, confirm – confirm what the client is expecting by providing frequent touchpoints (show wireframes, prototypes, pilots, etc…) • Repeat

12. Home U V W X Y Type your search here… Search Announcements My Tasks Class Pulse • Loremipsum dolor sit amet. • Mauris sit ameterosnecenimtincidunteuismod at egetenim. Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet. Add My Links Class Pulse Events • 01/10/10 Loremipsum dolor sit amet. • 01/25/10 Mauris sit ameterosnecenimtincidunteuismod. Add

13. Logo Search Home Tab 2 Tab 3 Tab 4 Pulse of My Classes (Primary View) My Alerts for Today Events mm/dd/yy – PS Open House mm/dd/yy – HS Boy’s basketball game home game mm/dd/yy – MS Girl’s Soccer game home game View Frequently Accessed Links My Link 1 My Link 2 Announcements mm/dd/yy – Open House tonight! mm/dd/yy – 3rd grade field trip to Kimball Museum View Pulse of My Current Class: Math (Primary View) Show: Failing Uplift Announcements mm/dd/yy – Red Ribbon Week next week mm/dd/yy – Open House

14. Search: Logo Home Tab 2 Tab 3 Tab 4 My Task List Pulse of My Classes Calendar mm/dd/yy – staff meeting mm/dd/yy – PS Open House mm/dd/yy– HS Boy’s basketball game home game mm/dd/yy – MS Girl’s Soccer game home game View Frequently Accessed Links My Link 1 My Link 2 Announcements mm/dd/yy – Open House tonight! mm/dd/yy– 3rd grade field trip to Kimball Museum mm/dd/yy– 2nd grade field trip to Kimball Museum View Pulse of My Current Class: 4th period Science(View: Failing Only)

15. Iterative Design and Development 1 2 3 4

16. Timing for Prototypes

17. System Overview Graphics

18. Training Monthly Schedule Mandatory OT list Reassignments Leave Data Vacation Payroll Continuing Education Overtime Workload Rule Payroll Procedure Daily Schedule Trades Leave Leave Accrual Holdovers City Certification Reports State Certification Callbacks Sick Time Leave Cap Unfilled Positions Overtime Per Shift OJI

19. Overview of Automated Resource Management System (ARMS)

20. Overview of 3-semester plan for ARMS

21. Travis Co. Project Overview

22. Analysis Techniques • Goal: Managing Client Expectations • Prototypes • Overview Graphics • Evaluation Tables Analysis techniques included in past and future classes: DFDs risk evaluation context diagrams organizational impact UML (use cases) ROI analysis root cause analysis prototyping non-functional requirements wire frame prototypes Planning techniques also aid in communication & managing client expectations

23. Evaluation Table with Milestone list Initial scope problem: would take more than a semester

24. Evaluation Table with Milestone list

26. CHALLENGE: SCOPE CREEP Hey, I have an idea! Wouldn’t it be nice if…

27. CHALLENGE: SCOPE CREEP “Some team members feel that we can code functionality easily without thinking about testing. There are a lot of complications you have to take into account for every additional requirement.” -Ameer “I think there should have been a better balance regarding how much we can/should sign up for. Some team members were too quick to sign up for new things, while others were too slow.” -Guillermo

28. SOLUTION: SCOPE CREEP Evaluation Table Gantt Chart +

29. Analysis tasks in Build Phase • High level analysis: • Scope (goals, • objectives, budget, • feasibility w/in • organization) • Look & feel Analyze functional requirements one module at a time for people, data, information, software & hardware. Document functional requirements specific to each module. Task order, iteration, and collaboration with users will depend on project characteristics. Include testing every phase + review

30. Where do I find examples? • System Overview Graphics examples • Evaluation Tables examples Examples found on Resources page and Client Project page

31. Resource: Client Project Page Outline for 1st meeting Draft for 2nd Meeting

32. Resource: Client Project Page 3rdmeeting Draft for 2nd Meeting Version for 2nd Meeting

33. 3 keys to success • Listen well / observe well. (interviewing, survey, focus groups, frequent client review, etc.) 2. Provide maximum opportunities for feedback. The main reason for phasing is to provide maximum opportunities for feedback—it is a baby steps approach. • Gain users’ respect and trust. • All the techniques in this course are designed to help with these 3 keys to success. Use them with your clients!

34. Client Project web page How to schedule UT meeting rooms & tips for selecting a host. Grading Rubric Delivery 1 guideline & template

35. Exercises, Class & Readings Class Design Group Project 1 – case Done Group Project 2 – same case Done Client Project – real world client

36. Client Project -- Project Charter Spec • “Working to spec” – valuable experience and interview talking point • Two documents for Project Charter • Project Charter Guidelines • Project Charter Template

37. How to use the Template Create documents to show your client and use them for your Project Charter document. SystemNameSystem Overview Strategy Discussion click here to start typing; DELETE GRAY INSTRUCTIONS BEFORE PRINT: Summarize techniques, forms, and diagrams that follow, explaining their relevance to your project plan. This is similar to the executive summary, but focuses on key project issues. This is a deeper explanation of what management needs to consider from the work you have done. Root Cause Analysis click here to start typing; DELETE GRAY INSTRUCTIONS BEFORE PRINT: Insert your table here following the format provided on the web schedule for Class Day 3. Functional Requirements click here to start typing; DELETE GRAY INSTRUCTIONS BEFORE PRINT: Insert your table here following the format provided on the Client Project web page for this section of your Charter. Nonfunctional Requirements click here to start typing; DELETE GRAY INSTRUCTIONS BEFORE PRINT: Insert your table here following the format provided on the web schedule for Class Day 7. Risk Evaluation & Risk Reduction click here to start typing; DELETE GRAY INSTRUCTIONS BEFORE PRINT: Insert a Risk Evaluation table and a Risk Reduction table following the format for each table provided on the web schedule for Class Day 8. Return on Investment click here to start typing; DELETE GRAY INSTRUCTIONS BEFORE PRINT: Develop a cost/benefit similar to the one presented in class. You must collect at least three years of data for the costs and benefits. Show the development and operational costs. Calculate the ROI. Include intangible benefits. The template provided on the Forms & Examples web page and examples on the Client Project web page are strongly recommended. Non-functional Requirements for ClientName 1. Maintainability – system requirements for enhancements and fixes that require custom development * Context: 2. Portability – system requirements for cross-platform, multi-user agent access, etc Context:

38. Using the techniques DFDs risk evaluation context diagrams organizational impact non-functional req. UML (use cases) ROI analysis root cause analysis prototyping In class—Wednesday, Oct 17th Sample exam—Class schedule page In class review—Monday, Oct 15th Exam 1- prep by preparing for Client Project meetings Prepare for exam by creating a rough draft of all of these client project deliveries. Bring your drafts to a team meeting and compare as way to check your skills AND accumulate Delivery 1 docs.

39. Client Project work • You’ve met with your client last week and done exercise 9 • Overwhelmed? Don’t worry • Remember its important to communicate and fail early • Should be preparing for 2nd meeting hopefully with prototypes • Meeting Minutes • Don’t need to send to me but weekly minutes are part of Charter document • Continuing to send these to the client