This chapter introduces Object-Oriented Systems Analysis and Design with the Unified Modeling Language, Version . First, the chapter introduces the basic characteristics of object-oriented systems. Second, it introduces UML . Third, the chapter overviews Object-Oriented Systems Analysis and Design and describes the Unified Process. Finally, based on the Unified Process and the UML , the chapter provides a minimalist approach to Object-Oriented Systems Analysis and Design with UML . | Chapter 2: Project Initiation, Project Management & Requirements Determination Objectives Understand the importance of linking the information system to business needs. Be able to create a system request. Understand how to assess technical, economic, and organizational feasibility. Be able to perform a feasibility analysis. Understand how projects are selected in some organizations. Successful Projects Cost At project completion, no more money has been spent than was originally allocated Schedule The project is delivered no later than the original delivery date Performance When delivered, the project has all features and functionality that were originally required of it Why Should We Care? Would you buy a car that only had a 28% chance of driving off the lot with no problems? Source: The Standish Group 2006 Chaos Report Recent Significant IT Failures Source: Charette, Robert N., “Why Software Fails,” IEEE Spectrum Online, Sept. 2005. PROJECT IDENTIFICATION Project . | Chapter 2: Project Initiation, Project Management & Requirements Determination Objectives Understand the importance of linking the information system to business needs. Be able to create a system request. Understand how to assess technical, economic, and organizational feasibility. Be able to perform a feasibility analysis. Understand how projects are selected in some organizations. Successful Projects Cost At project completion, no more money has been spent than was originally allocated Schedule The project is delivered no later than the original delivery date Performance When delivered, the project has all features and functionality that were originally required of it Why Should We Care? Would you buy a car that only had a 28% chance of driving off the lot with no problems? Source: The Standish Group 2006 Chaos Report Recent Significant IT Failures Source: Charette, Robert N., “Why Software Fails,” IEEE Spectrum Online, Sept. 2005. PROJECT IDENTIFICATION Project Identification and Initiation Projects are driven by business needs Identified by business people Identified by IT people (better yet) identified jointly by business and IT The project sponsor believes in the system and wants to see it succeed Normally this is a business person Should have the authority to move it forward Business Value Tangible Value Can be quantified and measured easily Example: 2 percent reduction in operating costs Intangible Value Results from an intuitive belief that the system provides important, but hard-to-measure, benefits to the organization Example: improved customer service Elements of a System Request Project sponsor Primary point of contact for the project Business need Reason prompting the project Business requirements Business capabilities the system will need to have Business value Benefits the organization can expect from the project Special issues Anything else that should be considered FEASIBILITY ANALYSIS Feasibility Analysis Guides the organization in .
