IS Theories & PracticesProcess vs. Project ManagementSystem Development MethodologiesSlide 41. Scope DefinitionPIECES Framework for Systems Improvement2. Problem Analysis3. Requirement Analysis4. Logical Design5. Decision AnalysisDecision Analysis6. Physical Design7. Construction Phase8. Implementation PhaseInstallation/Conversion StrategiesInstallation/Conversion Strategies …Operation and SupportSummary: Systems Development ProcessClassic Project PhasesModel-Driven DevelopmentSlide 21Model-Driven Development …Rapid Application DevelopmentRapid Application DevelopmentRapid Application Development …Hybrid StrategiesHybrid: Multiple ImplementationHybrid: Staged ImplementationMeasures of Project SuccessPoor Expectations ManagementCauses of Project FailureInter-task DependenciesTask Splitting & DelayingPERT ChartMicrosoft Project PERT ChartCritical PathGantt ChartMicrosoft Project Gantt ChartScheduling Strategies1IS Theories & PracticesSystem Development Process & Project ManagementIS 655: Note 5CSUN Information SystemsIS 655 : Note 52Process vs. Project ManagementProcess Management is an ongoing activity that documents, manages the use of, and improves an organization’s chosen methodology (the “process”) for system development. Process management is concerned with the activities, deliverables, and quality standards to be applied to all projects. Project Management is the process of scoping, planning, staffing, organizing, directing, and controlling the development of an acceptable system at a minimum cost within a specified time frame.IS 655 : Note 53System Development MethodologiesArchitected Rapid Application Development (Architected RAD)Dynamic Systems Development Methodology (DSDM)Joint Application Development (JAD)Information Engineering (IE)Rapid Application Development (RAD)Rational Unified Process (RUP)Structured Analysis and DesigneXtreme Programming (XP)IS 655 : Note 54System Building BlocksIS 655 : Note 551. Scope Definition• Purpose: define perceived problems, opportunities, and directives (POD); assess the risk of project; establish scope, preliminary requirements and constraints, participants, budget and schedule (preliminary study)• Issues: Is the project worthwhile? (using PIECES framework) Define the scope of project• Deliverable: Project charter/plan•Feasibility check: Cancel project / Approve to continue / Reduce or expanse the scope with budget and schedule modificationIS 655 : Note 56PIECES Framework for Systems ImprovementP the need to improve performanceI the need to improve information (and data)E the need to improve economics, control costs, or increase profitsC the need to improve control or securityE the need to improve efficiency of people and processesS the need to improve service to customers, suppliers, partners, employees, etc.IS 655 : Note 572. Problem Analysis• Purpose: to study and analyze the existing system from the users’ perspectives as they see Data, Processes, and Interfaces• Issue: Cost/benefits of building new system to solve these problems• Deliverable: system improvement objectives (business criteria to evaluate the new system)• Feasibility check: Cancel project / Approve to continue / Reduce or expanse the scope with budget and schedule modificationIS 655 : Note 583. Requirement Analysis • Purpose: discover users’ needs or expectations out of the new system in terms of Data, Processes, and Interfaces• Issue: Specify requirements for the new system (WHAT TO BE DONE) without prematurely expressing technical details (HOW)• Errors and omissions in requirement analysis result in user dissatisfaction of final system and costly modifications• Deliverable: business requirements statementIS 655 : Note 594. Logical Design• Purpose: translating business user requirements into a system model that depicts only WHAT TO DO without specifying any possible technical design or implementation of those requirements (conceptual design). • Issue: using graphical model of a system to represent user requirements in terms of Data, Processes and Interfaces, and to facilitate improved communication between system stakeholders.•Caution: Analysis paralysis – excessive system modeling dramatically slows progress toward implementation of the intended system solution.•Deliverable: Logical Systems Models (DFD, ERD etc)IS 655 : Note 5105. Decision Analysis• Purpose: identify all candidate solutions, analyze the feasibility of each candidate, recommend a candidate system as the target solution• Issue: Feasibility analysis in terms of technical, operational, economic, schedule (TOES), and risk•Deliverable: approved system proposal•Feasibility check: Cancel project / Approve system proposal with budget and schedule modification / Reduce the scope of proposed solution with budget and schedule modificationIS 655 : Note 511Decision AnalysisCandidate solutions evaluated in terms of TOES and Risks:–Technical feasibility – Is the solution technically practical? Does our staff have the technical expertise to design and build this solution? –Operational feasibility – Will the solution fulfill the users’ requirements? To what degree? How will the solution change the users’ work environment? How do users feel about such a solution?–Economic feasibility – Is the solution cost-effective?–Schedule feasibility – Can the solution be designed and implemented within an acceptable time?–Risk feasibility – What is the probability of a successful implementation using the technology and approach? (Risk Management)IS 655 : Note 5126. Physical Design• Purpose: to transform business requirements into technical design specifications for construction• Issue: HOW technology will be used to build the system in terms of Data, Processes, and Interfaces• Design by Specifications vs. Design by Prototyping• Deliverable: System design specifications (blueprints)•Feasibility check: Continue/ Reduce or expanse the scope with budget and schedule modificationIS 655 : Note 5137. Construction Phase• Purpose: to build and test a system that fulfill business requirements and design specs; implement interfaces between new and existing systems• Issue: Construct database, application programs, user/system interfaces, implement purchased or leased software• Deliverable: proposed system within budget and scheduleIS 655 : Note 5148. Implementation Phase• Purpose: deliver the