Unit 1.1 - 21HU631_Software Project Management.pptx

SPM

1. 21HU631 Software Project Management Class 1 Introduction

2. Introduction Project Evaluation & Planning Effort & Cost Estimation Activity Planning & Scheduling Risk & Resource Management Monitoring & Control People & Team Management Software Quality Management Case Study & Tools What are we going to learn in this course?

3. Why do we need Software Project Management? Software Projects v/s Other Types of Projects Activities Covered by SPM CONTENTS

4. Why is Software Project Management required? ICT projects involve very large financial investments, often more than other public works like roads. Despite this, many ICT projects fail, run late, or exceed budgets. The main reason for these failures is poor project management, lack of risk management, and insufficient skills .

5. Characteristics of a Project s Non-routine tasks Planning required Specific objectives or product Fixed time span Client-oriented work Multiple specialisms involved Temporary team formation Phased execution Limited resources Large or complex in nature

6. Software Projects v/s Other Types of Project Invisibility Complexity Conformity Flexibility

7. Activities Covered by Software Project Management Feasibility Planning Project execution

8. Feasibility Assess whether the Project has a valid Business Case Stakeholders might be unsure about the means to achieve their outcome Cost Estimation must be done including developmental, operational and value of the benefits of the new system.

9. Planning Project planning begins once the feasibility study shows the project is viable. An outline plan is created for the entire project, with detailed planning done only for the first stage. Later stages are planned closer to their start, when more accurate information becomes available.

10. Project Execution Project execution includes design and implementation. Design defines product form (UI or internal architecture), while planning defines activities to build them. Planning and design overlap since design choices influence planning decisions . The development of software will be only one part of a project. Software could be developed,

11. Typical sequence of software development activities recommended in the international standard ISO 12207.

12. Requirement Analysis Analyse what kind of House we are expected to build? Requirements analysis begins with elicitation/gathering from users and managers. Requirements may define system functions (what the system should do). quality (how well functions must work). Can include training for efficient system use. Resource requirements (application development costs)

13. Architecture Design Make the house plan System components are identified to fulfill each requirement. Some requirements may be met with existing components; others need new ones. Components can be software, hardware, or work processes. Software components must consider legacy systems for interoperability. Architecture design first maps system requirements to components, then software requirements to software components.

14. Detailed Design Detailed plan of every room/furniture Each software component is divided into smaller software units. These units can be coded and tested independently. Detailed design is done separately for each unit. Code is written for each software unit. Initial testing is done to debug individual units. Code and Test Start building the actual house

15. Integration Integration of electrical/pipes with the building Components are tested together to check if overall requirements are met. Integration may involve combining different software components. It can also involve testing software with hardware platforms and user interactions.

16. Qualification testing ( Like inspecting the finished house to ensure everything matches the plan ) The whole system is tested to ensure all requirements are met. Installation (Setting up the house to make it livable) The system is made operational by setting up data, system parameters, and software. User training (Teaching the homeowners how to use the facilities) Users are trained to operate the new system effectively.

17. Acceptance support (Fixing initial issues after moving in, such as repairing a leaking tap, adjusting door hinges, or resolving paint cracks) Problems with the installed system are resolved, and errors are corrected. Maintenance (Ongoing care and improvements) Extensions, improvements, and minor updates are carried out as ongoing software projects.

18. THANK YOU!