O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Introduction to Software Project Management (SPM)

612 visualizações

Publicada em

The software projects can be broadly divided into two categories:
 Information systems versus embedded systems
The difference is that in the former case, the system interface with the organization eq. stock control system, whereas in the later case, the systems interface with a machine eq. the air conditioning equipment in a building.
 Objective versus products
A project might be to create a project, the details of which have been specified by the client. On the other hand, the project may be required to meet certain objectives.

Publicada em: Engenharia
  • Seja o primeiro a comentar

  • Seja a primeira pessoa a gostar disto

Introduction to Software Project Management (SPM)

  1. 1. For more Https://www.ThesisScientist.com Unit – 1: Introduction to Software Project Management (SPM) 1.1 Definition of Software Project Management (SPM) Software Project Management (SPM) is an activity of organizing, planning and scheduling of Software Projects. 1.2 Software Projects versus other types of project The following characteristics of software project which make them different from other projects:  Invisibility  Complexity  Conformity  Flexibility 1.3 Activities covered by software project management (SPM) The following activities are:  The feasibility study  Planning  Project execution The feasibility/Plan/execution cycle as shown in the figure: Fig: Feasibility/Plan/execution cycle Feasibility study Plan Project execution How we do it? Do it? Is it worth doing?
  2. 2. For more Https://www.ThesisScientist.com 1 The feasibility study We study that whether the project have worth or not, it mean that it has a valid business case. 1. Planning First, we formulate the outline plan for the whole project then later we will go for the detail and accurate plan. 2. Project execution The execution of a project contains the design and implementation sub-phases. 1.4 Categorizing Software Projects The software projects can be broadly divided into two categories:  Information systems versus embedded systems The difference is that in the former case, the system interface with the organization eq. stock control system, whereas in the later case, the systems interface with a machine eq. the air conditioning equipment in a building.  Objective versus products A project might be to create a project, the details of which have been specified by the client. On the other hand, the project may be required to meet certain objectives. 1.5 Requirement specification The following are:  Functional requirements These define what the end-product of the project is to do.  Quality requirements There will be other attributes of the attributes of the application to be implemented that do not relate so much to what the system is to do but how to do it, eq. response time.  Resource requirements A record of how much the organization is willing to spend on the system.
  3. 3. For more Https://www.ThesisScientist.com These are also called non-functional requirements. 1.6 What is Management? The management involves the following activities:  Planning  Organizing  Staffing  Directing  Monitoring  Controlling  Innovating  Representing 1.7 Management control It involves setting the objectives for a system and then monitoring the system. The figures explain the whole system: This will involves the local manages in data collection. Data processing will be needed to transform this raw data into useful information. The making decisions/plans will be useful to take decision whether it will be complete on time or not. It also considers other aspects. The project manager can move staff from particular branches. This is modeling the consequences of a potentials solution. Several different proposals could be modeled in this way before one was chosen for implementation. It can be seen that a project plan is dynamic and will need constant adjustment during the execution of a project.
  4. 4. For more Https://www.ThesisScientist.com Fig: The project control cycle The real world Data collection Data processing Making decisions / plans Implementation Define objective Modeling Actions Data Information Decisions
  5. 5. For more Https://www.ThesisScientist.com Requirement specification The following are:  Functional requirements These define what the end-product of the project is to do.  Quality requirements There will be other attributes of the attributes of the application to be implemented that do not relate so much to what the system is to do but how to do it, eq. response time.  Resource requirements A record of how much the organization is willing to spend on the system. These are also called non-functional requirements. Categorizing Software Projects The software projects can be broadly divided into two categories:  Information systems versus embedded systems The difference is that in the former case, the system interface with the organization eq. stock control system, whereas in the later case, the systems interface with a machine eq. the air conditioning equipment in a building.  Objective versus products A project might be to create a project, the details of which have been specified by the client. On the other hand, the project may be required to meet certain objectives.
  6. 6. For more Https://www.ThesisScientist.com

×