Topic 3 Inception Phase PDF

TOPIC 3 Inception Phase  2 TOPIC LEARNING OUTCOMES  Describe the processes involved in the first phase of Rational Unified Process (RUP) - Inception.  Explain the initiation of IT pr...

TOPIC 3 Inception Phase  2 TOPIC LEARNING OUTCOMES  Describe the processes involved in the first phase of Rational Unified Process (RUP) - Inception.  Explain the initiation of IT projects.  Review project’s proposal evaluation and feasibility by a project manager/analyst. Explain the initial review of systems requests and the role of the systems review committee. Discuss operational feasibility, technical feasibility, economic feasibility and schedule feasibility. Describe the steps in a preliminary investigation and the end-product of an investigation. ITD22303 - Object Oriented System Analysis & Design  3 INTRODUCTION - RUP Rational Unified Process (RUP) is a software development process for object-oriented models. It is also known as the Unified Process Model. It is created by Rational Corporation and is designed and documented using UML (Unified Modeling Language). Some characteristics of RUP: being use-case driven Iterative (repetition of the process) incremental (increase in value) by nature delivered online using web technology can be customized or tailored in modular and electronic form, etc. RUP reduces unexpected development costs and prevents the wastage of resources. RUP is an excellent choice for building high-quality software within a time and budget limit. https://www.ishir.com/blog/10130/8-fundamental-sdlc-models-every-developer- ITD22303 - Object Oriented System Analysis & Design should-know-about.htm  4 INTRODUCTION – RUP (CONT.) Rational Unified Process https://www.ishir.com/blog/10130/8-fundamental-sdlc-models-every-developer- ITD22303 - Object Oriented System Analysis & Design should-know-about.htm  5 INTRODUCTION - INCEPTION Communication and planning are the main ones. Identifies the scope of the project using a use-case model allowing managers to estimate costs and time required. Customers’ requirements are identified and then it becomes easy to make a plan for the project. The project plan, project goal, risks, use-case model, and project description, are made. The project is checked against the milestone criteria and if it couldn’t pass these criteria then the project can be either canceled or redesigned. ITD22303 - Object Oriented System Analysis & Design  6 INTRODUCTION – INCEPTION (CONT.) Determine the project's scope: The team uses use case modeling to identify the project's scope, costs, and time required to build it. Establish the business case: The team creates a business case that includes the business context, success factors, and financial forecast. Identify stakeholders: The team identifies the people, organizations, and external systems that will interact with the system. Consider customer needs: The team considers how to incorporate any specific customer needs or requests into the design plan. Assess risks: The team assesses potential risks associated with the project. Create a use-case model: The team creates a use-case model that describes the proposed functionality of the new system. Create a project plan: The team creates a project plan. Develop a prototype: The team may develop a prototype. ITD22303 - Object Oriented System Analysis & Design  7 INTRODUCTION – BUSINESS CASE The term business case refers to the reasons, or justification, for a proposal A strong business case suggests that the company should pursue the alternative, above other options, because it would be in the firm’s best interest to do so Systems development typically starts with a systems request, followed by a preliminary investigation, which includes a feasibility study ITD22303 - Object Oriented System Analysis & Design  8 WHAT IS A BUSINESS CASE? Should be comprehensive, yet easy to understand Should describe the project clearly, provide the justification to proceed, and estimate the project’s financial impact https://www.projectmanager.com/blog/how-to-write-a-business-case ITD22303 - Object Oriented System Analysis & Design  9 INFORMATION SYSTEMS PROJECTS Five component of IS Main Reasons for Systems Projects ITD22303 - Object Oriented System Analysis & Design  10 INFORMATION SYSTEMS PROJECTS (CONT.) Factors that Affect Systems Projects ITD22303 - Object Oriented System Analysis & Design  11 INTERNAL FACTORS Strategic Plan Sets the overall direction for the firm and has an important impact on IT projects. Company goals and objectives that need IT support will generate systems request and influence IT priorities. Top Managers Because significant resources are required, top management usually initiates large-scale projects. Those decisions often result from strategic business goals that require IT systems, more information for decision making, or better support for mission-critical information systems. User Request Users rely more heavily on information systems to perform their jobs, they are likely to request even more IT services and support. Eg: Sales ref request improvements to the company’s web site or, users might not be satisfied with the current system because it is difficult to learn or lacks flexibility. ITD22303 - Object Oriented System Analysis & Design  12 INTERNAL FACTORS (CONT.) Information Technology Department Many systems project requests come from the IT department. IT staff members often make recommendations based on their knowledge of business operations and technology trends. IT proposals might be strictly technical matters. Existing Systems and Data Errors or problems in existing systems can trigger request for systems projects. When dealing with older systems, analysts sometimes spend too much time reacting to day-to-day problems without looking at underlying causes. With this approach an information system turn into patchwork of corrections and changes that cannot support the company’s overall business needs ITD22303 - Object Oriented System Analysis & Design  13 EXTERNAL FACTORS Technology Changing technology is a major force affecting business and society in general. Technology dramatically reshape existing business operations. Suppliers With the growth of electronic data interchange(EDI), relationships with suppliers are critically important. Eg. an automobile company might require that suppliers code their parts in a certain manner to match the auto company’s inventory control system. Customers Customers are vitally important to any business. Information systems that interact with customers usually receive top priority. Competitors Competitors drives many information systems decision. Eg. If one cellular telephone provider offers a new type of digital service, other firms must match the plan in order to remain competitive. ITD22303 - Object Oriented System Analysis & Design  14 EXTERNAL FACTORS (CONT.) Competitors Competitors drives many information systems decision. Eg. If one cellular telephone provider offers a new type of digital service, other firms must match the plan in order to remain competitive. The Economy Economic activity has a powerful influence on corporate information management. In a period of economic expansion, firms need to be ready with scalable systems what can handle additional volume and growth. Government Federal, state, and local government regulations directly affect the design of corporate information systems. ITD22303 - Object Oriented System Analysis & Design  15 INFORMATION SYSTEMS PROJECTS Project Management If the project is approved, it can be planned, scheduled, monitored and controlled, and reported Individual analysts or IT staff members often handle small projects, but companies usually designate a project manager to coordinate the overall effort for complex projects ITD22303 - Object Oriented System Analysis & Design  16 EVALUATION OF SYSTEMS REQUESTS Systems review committee or a computer resources committee evaluate systems requests to set which part is priority in the future system. Systems Requests Forms A properly designed form streamlines the request process and ensures consistency Occasionally a situation will arise that requires an immediate response ITD22303 - Object Oriented System Analysis & Design  17 EVALUATION OF SYSTEMS REQUESTS (CONT.) Elements of the System Request Form: Project sponsor – the person who initiates the project and who serves as the primary point of contract for the project on the business side. Business need – the business-related reason for initiating the system. Business requirement – the business capabilities that the system will provide. Business value – the benefits that the system will create for the organization. Special issues or constraints – issues that are related to the implementation of the system and committee make decisions about the project. ITD22303 - Object Oriented System Analysis & Design  18 OVERVIEW OF FEASIBILITY  A systems request must pass several tests, called a feasibility study, to see whether it is worthwhile to proceed further  Factors that Affect Priority  Will the proposed system reduce costs? Where? When? How? How much?  Will the system increase revenue for the company? Where? When? How? How much? ITD22303 - Object Oriented System Analysis & Design  19 FEASIBILITY ACTIVITY 1 : DETERMINING ORGANIZATIONAL & CULTURAL FEASIBILITY  Some potential human risks impacting new system  Low level of computer competency among employees  Perceived shifting of organizational power  Fear of employment loss due to increased automation  Reversal of long-standing work procedures  Factors that Affect Priority  Will the systems project result in more information or produce better results? How? Are the results measurable?  Will the system serve customers better?  Will the system serve the organization better?  One way to counter risks: training sessions ITD22303 - Object Oriented System Analysis & Design  20 FEASIBILITY ACTIVITY 2 : EVALUATING THE TECHNOLOGICAL FEASIBILITY Staff should have technological proficiency Solutions to problem are straightforward Provide additional training Hire consultants Hire more experienced employees Possibly alter scope and approach of the project Realistic assessments speedup corrective response 20 ITD22303 - Object Oriented System Analysis & Design  21 FEASIBILITY ACTIVITY 3 : DETERMINING THE SCHEDULE FEASIBILITY Development of project schedule involves high risk Assumptions and estimates made without adequate information Adaptive projects very susceptible to schedule risks Project managers use milestones to evaluate pace and compensate for slippage Contingency plans help reduce the risk of slippage 21 ITD22303 - Object Oriented System Analysis & Design  22 FEASIBILITY ACTIVITY 4 : ASSESSING THE RESOURCE FEASIBILITY Human and other resources to assess Primary resource consists of team members Systems analysts, system technicians, users Support staff Computer resources and physical facilities Factors adversely impacting human resource Lack of required people skill sets Relocations or departures 22 ITD22303 - Object Oriented System Analysis & Design  23 FEASIBILITY ACTIVITY 5 : DETERMINING THE ECONOMIC FEASIBILITY Economic feasibility consists of two questions Does anticipated value of benefits exceed project costs? Is there adequate cash flow to fund the project? Cost/benefit analysis determines economic feasibility (comparison of the costs of development versus the anticipated financial benefits of the new system) Developing cost/benefit analysis is a three-step process Estimate anticipated development and operational costs Estimate the anticipated financial benefits Subtract costs from benefits MS Project supports cost/benefit analysis 23 ITD22303 - Object Oriented System Analysis & Design MS Project Showing example of Project Labor Costs https://www.pmvision.ca/micr osoft-project-2016-resources- with-multiple-pay-rates/ https://www.youtube.com/wa tch?v=o-_KX0yRsyg https://blog.ganttpro.com/en/ microsoft-project-ms-tutorial/ 24 ITD22303 - Object Oriented System Analysis & Design  25 EVALUATING FEASIBILITY The first step in evaluating feasibility is to identify and weed out systems requests that are not feasible Even if the request is feasible, it might not be necessary Feasibility analysis is an ongoing task that must be performed throughout the systems development process ITD22303 - Object Oriented System Analysis & Design  26 PRELIMINARY INVESTIGATION OVERVIEW Interaction with Managers and Users Let people know about the preliminary investigation and explain your role Employee attitudes and reactions are important and must be considered Be careful in your use of the word problem Question users about additional capability they would like to have ITD22303 - Object Oriented System Analysis & Design  27 PRELIMINARY INVESTIGATION OVERVIEW (CONT.) Step 1: Understand the Problem or Opportunity Develop a business profile that describes business processes and functions Understand how modifications will affect business operations and other information systems Determine which departments, users, and business processes are involved A popular technique for investigating causes and effects is called a fishbone diagram. Systems request may not reveal an underlying problem Consider using a fishbone diagram ITD22303 - Object Oriented System Analysis & Design  28 PRELIMINARY INVESTIGATION OVERVIEW (CONT.) Fishbone diagram. ITD22303 - Object Oriented System Analysis & Design  29 PRELIMINARY INVESTIGATION OVERVIEW (CONT.) Step 2: Define the Project Scope and Constraints Specific Boundaries Project scope - Must Do, Should Do, Could Do, and Won’t Do Constraint - A constraint is a requirement or condition that the system must satisfy or an outcome that the system must achieve Present versus future Internal versus external Mandatory versus desirable Regardless of the type, all constraints should be identified as early as possible to avoid future problems and surprises ITD22303 - Object Oriented System Analysis & Design  30 PRELIMINARY INVESTIGATION Constraints OVERVIEW (CONT.) ITD22303 - Object Oriented System Analysis & Design  31 PRELIMINARY INVESTIGATION OVERVIEW (CONT.) Step 3: Perform Fact-Finding Fact-finding involves various techniques Depending on what information is needed to investigate the systems request, fact- finding might consume several hours, days, or weeks Analyze Organization Charts Obtain organization charts to understand how the department functions and identify individuals you might want to interview ITD22303 - Object Oriented System Analysis & Design  32  Investigate the current system documentation PRELIMINARY INVESTIGATION OVERVIEW (CONT.)  Check with users to confirm that you are Step 3: Perform Fact-Finding (Cont.) receiving accurate Conduct interviews and complete information Review documentation Observe operations Conduct a user survey Analyze the data  See how workers carry out typical tasks  Sample inputs and outputs of the system ITD22303 - Object Oriented System Analysis & Design  33 PRELIMINARY INVESTIGATION OVERVIEW (CONT.) Conduct Interviews 1. Determine the people to interview 2. Establish objectives for the interview 3. Develop interview questions 4. Prepare for the interview 5. Conduct the interview 6. Document the interview 7. Evaluate the interview ITD22303 - Object Oriented System Analysis & Design  34 PRELIMINARY INVESTIGATION OVERVIEW (CONT.) Step 3: Perform Fact-Finding (Cont.) Conduct a User Survey A survey is not as flexible as a series of interviews, but it is less expensive, generally takes less time, and can involve a broad cross-section of people Analyze the Data Systems analyst might use a Pareto chart Analysts may use an XY chart to identify if there is a correlation of variables ITD22303 - Object Oriented System Analysis & Design  35 PRELIMINARY INVESTIGATION OVERVIEW (CONT.) Step 3: Perform Fact-Finding (Cont.) FIGURE 2-21 A Pareto chart displays the causes of a FIGURE 2-22 An XY chart shows correlation between variables, which problem, in priority order, so an analyst can tackle the most is very important in problem solving. Conversely, a lack of correlation important causes first. In this example, the part number issue suggests that the variables are independent, and that you should look would be the obvious starting point. elsewhere for the cause. ITD22303 - Object Oriented System Analysis & Design  36 PRELIMINARY INVESTIGATION OVERVIEW (CONT.) Step 4: Analyze Project Usability, Cost, Benefit, and Schedule Data What information must you obtain, and how will you gather and analyze the information? What sources of information will you use, and what difficulties will you encounter in obtaining information? Will you conduct interviews? How many people will you interview, and how much time will you need to meet with the people and summarize their responses? Will you conduct a survey? Who will be involved? How much time will it take people to complete it? How much time will it take to prepare it and tabulate the results? How much will it cost to analyze the information gathered and to prepare a report with findings and recommendations? ITD22303 - Object Oriented System Analysis & Design  37 Assessing Practicality Analyzing CB in FF 1 2 https://fastercapital.com/content/Operational-Feasibility-and-Financial-Feasibility-Analysis--How-to- Examine-the-Practicality-and-Viability-of-Your-Project.html#Leveraging-Feasibility-Analysis-for-Project- Success ITD22303 - Object Oriented System Analysis & Design  38 PRELIMINARY INVESTIGATION OVERVIEW (CONT.) Step 5: Evaluate Feasibility OPERATIONAL FEASIBILITY  Review of user needs, requirements, and expectations  Look for areas that might present problems for system users and how they might be resolved. TECHNICAL FEASIBILITY Identify the hardware, software, and network resources needed to develop, install, and operate the system Develop a checklist that will highlight technical costs and concerns. ECONOMIC FEASIBILITY  Apply the financial analysis tools  The cost-benefit data will be important SCHEDULE FEASIBILITY  Include stakeholder expectations regarding acceptable timing and completion dates ITD22303 - Object Oriented System Analysis & Design  39 PRELIMINARY INVESTIGATION OVERVIEW (CONT.) Step 5: Evaluate Feasibility (Cont.) Start by reviewing the answers to the questions you asked Operational feasibility 2 Technical feasibility Economic feasibility Schedule feasibility 1 https://www.altexsoft.com/blog/technical-feasibility/ ITD22303 - Object Oriented System Analysis & Design  40 OPERATIONAL FEASIBILITY (OF) Key Factors – OF analysis Tools & Technique - OF Assessment 1 2 ITD22303 - Object Oriented System Analysis & Design  41 ECONOMIC /FINANCIAL FEASIBILITY (FF) Key Factors for FF 1 3 2 4 ITD22303 - Object Oriented System Analysis & Design  42 PRELIMINARY INVESTIGATION OVERVIEW (CONT.) Step 6: Present Results and Recommendations to Management The final task in the preliminary investigation is to prepare a report to management The format of the preliminary investigation report varies from one company to another ITD22303 - Object Oriented System Analysis & Design  43 PRELIMINARY INVESTIGATION Step 6: Present Results and OVERVIEW (CONT.) Recommendations to Management  Introduction  Systems Request Summary  Findings  Case for Action  Project Roles  Time and Costs Estimates  Expected Benefits  Appendix ITD22303 - Object Oriented System Analysis & Design  44 TOPIC SUMMARY Strategic planning allows a company to examine its purpose, vision, and values. Develop a mission statement, which leads to goals, objectives, day-to-day operations, and business results that affect company stakeholders Systems projects are initiated to improve performance, provide more information, reduce costs, strengthen controls, or provide better service ITD22303 - Object Oriented System Analysis & Design