INFO 380Information Systems Analysis and Management Instructor: Greg Hay TA: Yuan Lin
Agenda: Session 10 • Announcements • Discussion on Write-ups • Review: Use Case diagram • Feasibility Analysis • Project Teams\Scrum
Announcements • Survey on class content and delivery • Students are stakeholders • Informal, voluntary and ANONYMOUS • What is going well? • Be specific if possible • What is NOT going so well? • Opportunity to vent and throw rocks • If unhappy, make suggestions for improvements • https://catalyst.uw.edu/webq/survey/gthay/124538
Announcements • Homework topic this week is on you! • What topic did you find new or interesting? • Go beyond basic definitions; why should I care? • Impress me in 500 - 650 words(cite sources!)
Announcements • Extra Credit Write-up: Due Thursday Feb 17 • Business Intelligence (BI) is an emerging component of IT industry; what are some challenges of this segment? • Why do a higher percentage of BI projects fail over other IT projects?* • Same drill: ~700 words, cite sources • Value is .5% of final grade * Instructors opinion
Announcements • Discussion on Thursday February 24 • Dilemma on release of Pentagon Papers • Be familiar with the events outlined in podcast • http://www.bobedwards.info/ftopic980.html
Announcements • Microsoft Operations Framework (MOF): • http://technet.microsoft.com/en-us/library/cc506049.aspx • Microsoft Solutions Framework (MSF): • http://technet.microsoft.com/en-us/library/bb497060.aspx • Information Technology Infrastructure Library (ITIL): • http://www.best-management-practice.com/Knowledge-Centre/White-Papers/
Announcements • Use Case Analysis Report: Due February 22 • Describes the client business work processes • Intended to focus teams on user requirements • Identify the following: • Actors • Stakeholders • Precondition • Typical course of events
Announcements • Case Study approach next couple of weeks • Real-life organizations are examined • Will leverage processes already presented
Announcements • Quiz: Tuesday February 22 • Case study about a non-profit organization • Quiz: work systems analysis process as a team • Who are the stakeholders? • What questions need to be asked? • What are some of the constraints? • What are the development priorities? Why? • Where is the complexity?
Write-Up #5a • Compare the two executive roles of Chief Information Officer and Chief Technology Officer • What are the typical responsibilities of each? • How is the role of CIO different from CTO? • How similar are the desired skill set, education and technical experience for these positions?
Write-Up #5a • CIO • Focus: internal systems\processes for value • Employees\Partners\vendors • Output: information for strategic value\advantage • Greater efficiency\lower costs • Net income or 'profit' • Skill Set: Gifted Manager first • Background in IT-based operations • Often-times experience as project managers • Advanced business training (MBA or Masters of Science)
Write-Up #5a • CTO • Focus: external incorporation of technology • Customers • Output: new technology for strategic features • Greater usability of products and services • Increase revenue • Skill Set: Gifted engineer\programmer first • Background in product development • Advanced technical training (MS Computer Science)
Write-Up #5b • What are the competitive pressures ‘driving’ this innovation?
Write-Up #5b • What are the competitive pressures ‘driving’ this innovation? • Technology • Safety • Leads to: • Reduced accidents • Lives saved • Money made and saved
Write-Up #5b • Who are the stakeholders?
Write-Up #5b • Who are the stakeholders? • Auto manufacturers • Insurance companies • First-responders (Police/Fire) • Regular folk who drive
Write-Up #5b • What is the ‘impact’ behind the development of this technology? Opportunity cost?
Review: 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
Use Case Modeling • Focuses on one of stakeholders • ‘primary actor’ • Interact with system to accomplish desired goal
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
Use Case Modeling • High-Level • Tool for capturing functional requirements • Decomposes system into manageable pieces • Provides means of identifying, assigning, tracking and management system development activities • Helps estimate project scope and schedule
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
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
Feasibility Analysis • Why do we conduct feasibility analyses?
Feasibility Analysis • Why do we conduct feasibility analyses? • To help determine: • Does a problem ‘have legs’? • Which problem-fix is a better investment?
Feasibility Analysis • How often do we conduct feasibility analyses?
Feasibility Analysis • Why do we conduct multiple feasibility analyses?
Feasibility Analysis • Any component can change that affects results • Problem is better understood after studied closer • Business drivers change • Customer requirements change
Feasibility Analysis • What is the intent of a ‘checkpoint’?
Feasibility Analysis • What is the intent of a ‘checkpoint’? • Does this problem STILL have legs?
Feasibility Analysis • When do we schedule feasibility checkpoints?
Feasibility Analysis • When do we schedule feasibility checkpoints? • Last step of at least three different phases • Scope definition • Problem Analysis • Decision Analysis
Feasibility Analysis • Scope Definition Feasibility Checkpoint • ‘Does problem warrant cost of detailed study of systems?’ • Characteristics • Really rough estimate • Problems are rarely well-defined • First-cut requirements often understated • Estimate benefits first; then costs (fatten by 50-100%)
Feasibility Analysis • Problem Analysis Feasibility Checkpoint • ‘Does problem warrant cost of launching a full project?’ • Characteristics • Better understanding and clarity on estimates • Minimum value of solving problem must equal the cost
Feasibility Analysis • Problem Analysis Feasibility Checkpoint • Initial results show the benefits derived from fixing a problem exceed the costs of doing so: • Do we have a project?
Feasibility Analysis • Decision Analysis Feasibility Checkpoint • Most-significant feasibility study • Must answer true investment value of the project • Characteristics • Must know details of problems as well as requirements • Alternative solutions defined in terms of the following: • Input/output methods • Data storage methods • Computer hardware\software requirements • People implications
Feasibility Analysis • What are some examples of alternative solutions?
Feasibility Analysis • What are some examples of alternative solutions? • Do nothing • Re-engineer manual business processes • Purchase a packaged application • Design and construct a new computer-based system
Feasibility Analysis • What are some examples of alternative solutions? • Streamline activities • Reduce duplicated\unnecessary tasks • Re-organizing office layouts • Eliminating forms and processes • Enhance existing computer processes
Feasibility Analysis • Four Types of Feasibility Analyses • What are they?
Feasibility Analysis • Four Types of Feasibility Analyses • ‘TOES’ • Technical • Operational • Economic • Schedule
Feasibility Analysis • Operational Feasibility Analysis • What is the goal?
Feasibility Analysis • Operational Feasibility Analysis • Measure how well proposed system meets requirements
Feasibility Analysis • Technical Feasibility Analysis • What are the goals?