IT 352 Information Systems Analysis and Design 2020 PDF

IT 352: Information Systems Analysis and Design By: Haifa Alhasson 2020 9/6/20 Chapter 3 Copyright © 2011 Pearson Education, Inc. Publishing...

IT 352: Information Systems Analysis and Design By: Haifa Alhasson 2020 9/6/20 Chapter 3 Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Brief List of Topics Overview of Information System development environment Managing the Information Systems Project Identifying and Selecting Systems Development Projects Initiating and Planning Systems Development Projects Determine the system requirements Structuring System Process Requirements Designing information systems System Implementation Maintaining Information Systems 9/6/20Chapter 2 Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 2  Chapter 3 Managing the Information Systems Project  Learning Objectives ü Explain the process of managing an information systems project. ü Describe the skills required to be an effective project manager. ü List and describe the skills and activities of a project manager during project initiation, project planning, project execution, and project closedown. ü Explain what is meant by critical path scheduling and describe the process of creating Gantt charts and network diagrams. ü Explain how commercial project management software packages can be used to assist or help in representing and managing project schedules. 4  Importance of Project Management n Project management may be the most important aspect or feature of systems development. n Effective PM helps to ensure ü The meeting of customer expectations. ü The satisfying of budget and time constraints. n PM skills are difficult and important to learn. 5 Managing The Information Systems Project n Project A planned undertaking of related activities to reach an objective that has a beginning and an end. n Project manager A systems analyst with a diverse set of skills—management, leadership, technical, conflict management, and customer relationship—who is responsible for initiating, planning, executing, and closing down a project. 9/7/20Chapter 2 Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall 6  Pine Valley Application Project FIGURE 3-1 Three computer applications at Pine Valley Furniture: Order filling, invoicing, and payroll Source: Hoffer, Prescott, and Topi, 2009. 7 Managing the Information Systems Project n Project A planned undertaking of related activities to reach an objective that has a beginning and an end n Project management A controlled process of initiating, planning, executing, and closing down a project. 8  Deciding on Systems Projects n System Service Request (SSR) ü A standard form for requesting or proposing systems development work within an organization. (It is the first Deliverable of SDLC lifecycle). n Feasibility study ü A study that determines whether a requested system makes economic and operational sense for an organization. 9 FIGURE 3-2 System Service Request for purchasing a fulfillment system with name and contact information of the person requesting the system, a statement of the problem, and the name and contact information of the liaison and sponsor. 10 Managing the Information Systems Project (cont.) n summary, systems development projects are undertaken for two primary reasons: to take advantage of business opportunities and to solve business problems. n Deliverable Product The end product of an SDLC phase 11 Project Management Activities FIGURE 3-4 A project manager juggles or manage numerous activities 12 Phases of Project Management Process n Phase 1: Initiation n Phase 2: Planning n Phase 3: Execution n Phase 4: Closedown 13  PM Phase 1: Project Initiation n Assess or judge size, scope and complexity, and establish procedures. n Establish: ü Initiation team ü Relationship with customer ü Project initiation plan ü Management procedures ü Project management environment ü Project workbook 14 FIGURE 3-6 The project workbook for the Purchase Fulfillment System project contains nine key documents in both hard-copy and electronic form. 15  PM Phase 2: Project Planning n Define clear discrete or separate activities and the work needed to complete each activity n Tasks ü Define project scope, alternatives, feasibility ü Divide project into tasks ü Estimate resource requirements ü Develop preliminary schedule ü Develop communication plan ü Determine standards or principle and procedures ü Identify and assess risk ü Create preliminary budget ü Develop a statement of work ü Set baseline project plan 16 Planning Detail FIGURE 3-8 Level of project planning detail should be high in the short term, with less detail as time goes on. 17  Some Components of Project Planning n Statement of Work (SOW) ¨ “Contract” between the IS staff and the customer regarding deliverables and time estimates for a system development project n The Baseline Project Plan (BPP) ¨ Contains estimates of scope, benefits, schedules, costs, risks, and resource requirements n Preliminary Budget ¨ Cost-benefit analysis outlining planned expenses and revenues 18 Some Components of Project Planning (cont.) n Work Breakdown Structure (WBS) Division of project into manageable or convenient and logically ordered tasks and subtasks n Scheduling Diagrams ü Gantt chart: horizontal bars represent task durations ü Network diagram: boxes and links represent task dependencies 19  Scheduling Diagrams Gantt Chart FIGURE 3-10 Gantt chart showing project tasks, duration times for those tasks, and predecessors Special-purpose project management software is available for this. 20  Scheduling Diagrams Network Diagram FIGURE 3-13 A network diagram illustrating tasks with rectangles (or ovals) and the relationships and sequences of those activities with arrows Special-purpose project management software is available for this. 21 Preliminary Budget FIGURE 3-15 A financial cost and benefit analysis for a systems development project Spreadsheet software is good for this. 22  PM Phase 3: Project Execution n Plans created in prior phases are put into action. n Actions ü Execute baseline project plan ü Monitor progress against baseline plan ü Manage changes in baseline plan ü Maintain project workbook ü Communicate project status 23 Monitoring Progress with a Gantt Chart FIGURE 3-17 Gantt chart with tasks 3 and 7 completed Red bars indicate critical path; lines through bars indicate percent complete. 24  Communication Methods n High Formality or Procedure or Requirement ü Project workbook ü Newsletters or information sheet ü Status reports ü Specification or requirement documents ü Meeting minutes n Medium Formality ü Meetings ü Seminars and workshops ü Memos n Low Formality ü Bulletin boards ü Brown bag lunches ü Hallway discussions 25  PM Phase 4: Project Closedown n Bring the project to an end n Actions ü Close down the project. ü Conduct post-project reviews. ü Close the customer contract. 26 Representing and Scheduling Project Plans n Gantt Charts n Network Diagrams n PERT Calculations n Critical Path Scheduling n Project Management Software 27  Gantt Charts vs. Network Diagrams n Gantt charts ü Show task durations. ü Show time overlap. ü Show slack time in duration. n Network diagrams ü Show task dependencies. ü Do not show time overlap, but show parallelism. ü Show slack time in boxes. 28  Estimating Task Duration n PERT: Program Evaluation Review Technique n Technique that uses optimistic (o), pessimistic (p), and realistic (r) time estimates to determine expected task duration n Formula for Estimated Time: ¨ ET = (o + 4r + p)/6  Example PERT Analysis FIGURE 3-22 Estimated time calculations for the SPTS project  Critical Path Scheduling n A scheduling technique whose order and duration of a sequence of task activities directly affect the completion n Critical path: the shortest time in which a project can be completed n Slack time: the time an activity can be delayed without delaying the project  Critical Path Example (dependencies between tasks) PRECEDING ACTIVITIES indicate the activities that must be completed before the specified activity can begin. FIGURE 3-23 Sequence of Activities within the SPTS project  Critical Path Example Network diagram shows dependencies FIGURE 3-25 A network diagram that illustrates the activities (circles) and the sequence (arrows) of those activities 33  Determining the Critical Path n Calculate the earliest possible completion time for each activity by summing the activity times in the longest path to the activity. This gives total expected project time. n Calculate the latest possible completion time for each activity by subtracting the activity times in the path following the activity from the total expected time. This gives slack time for activities. n Critical path – contains no activities with slack time. 34  Critical Path Calculation FIGURE 3-26 A network diagram for the SPTS project showing estimated times for each activity and the earliest and latest expected completion time for each activity Early and late time calculations are determined and critical path established. (Note: Activity #5 can begin late without affecting project completion time). 35  Critical Path Calculation (cont.) FIGURE 3-27 Activity slack time calculations for the SPTS project; all activities except number 5 are on the critical path Note the slack time in Activity #5. 36  Using Project Management Software n Many powerful software tools exist for assisting with project management. n Example: Microsoft Project can help with ü Entering project start date. ü Establishing tasks and task dependencies. ü Viewing project information as Gantt or Network diagrams. 37  Project Start Date FIGURE 3-28 Establishing a project starting date in Microsoft Project for Windows 38  Entering Tasks FIGURE 3-29 Entering tasks and assigning task relationships in Microsoft project for Windows 39 Viewing Network Diagram FIGURE 3-30 Hexagon shape indicates a Viewing project milestone. information as a network diagram Red boxes and arrows indicate in Microsoft critical path (no slack). Project for Windows 40  Viewing Gantt Chart FIGURE 3-31 Gantt chart showing progress of activities (right frame) versus planned activities (left frame) Black line at top indicates a summary activity (composed of subtasks). Diamond shape indicates a milestone. 41  Summary n In this chapter you learned how to: ü Explain the process of managing an information systems project. ü Describe the skills required to be an effective project manager. ü List and describe the skills and activities of a project manager during project initiation, project planning, project execution, and project closedown. ü Explain what is meant by critical path scheduling and describe the process of creating Gantt charts and network diagrams. ü Explain how commercial project management software packages can be used to assist in representing and managing project schedules. 42