Activities covered by S/W Project Management 3 successive processes that bring a new system: 1 . Feasibility Study 2. Planning 3. Project Execution
Is It Worth Doing? Decide Proposed project is worth starting Probable development & Operational cost Estimate the Benefits “Is project technically feasible and worth-while from a business point of view”? SMART-Rule: S-Specific M- Mesurable A-Achievable R-Relevant T-Time Constrained 1. FeasibilityStudy
2.Planning : How do we do it? Outline plan and detailed plan 3.Project Execution: By Considering the “Classic Project Life Cycle”. Do It.
A typical Project Life Cycle Requirements Analysis Specification Design Coding Verification & Validation Implementation/Installation Maintenance and support
1.Requirements Analysis: Finding out what user requires from the system Requirements elicitation: what does the client needs? Requirements gathering 2.Specification: Detailed documentation of proposed system converting ‘customer-facing’ requirements into equivalents that developers can understand. 3.Design: Specification has to be drawn up2 types: External or User design- Menus, screens, report layouts. Physical design: Describes how data and software procedures are structured – Use case diagrams, Context Diagrams, ER- diagrams, Database Schema, Class Diagrams etc.
4.Coding: Writing code using some programming language. 5.Verification & Validation: Verification: Are we building the product right? Evaluation Items: Plans, Requirement Specs, Design Specs, Code, Test Cases Validation: Are we building the right product? Evaluation Items: The actual product/software. “product passes when verified but fails when validated”. 6.Implementation/Installation: Setting up data files and system parameters, writing user manuals Training users of the new system. 7.Maintenance & Support: Extensions and improvements. Correction of any errors.