Scribd
Upload
363 views3 pages

SPM - Assignment 1

COCOMO 2 provides three models to estimate software project costs at different phases: [1] the Application Composition model estimates costs for prototype development, [2] the Early Design model supports cost estimation at the architectural design stage, and [3] the Post-Architecture model provides cost estimation during detailed design and coding stages. Known risks can be uncovered through careful project evaluation, while predictable risks are extrapolated from past experience, such as staff turnover or poor customer communication. The main activities in software project management include project planning and tracking, scope management, estimation management, scheduling management, project resource management, project risk management, project communication management, and project configuration management.

Uploaded by

A kay
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
363 views3 pages

SPM - Assignment 1

COCOMO 2 provides three models to estimate software project costs at different phases: [1] the Application Composition model estimates costs for prototype development, [2] the Early Design model supports cost estimation at the architectural design stage, and [3] the Post-Architecture model provides cost estimation during detailed design and coding stages. Known risks can be uncovered through careful project evaluation, while predictable risks are extrapolated from past experience, such as staff turnover or poor customer communication. The main activities in software project management include project planning and tracking, scope management, estimation management, scheduling management, project resource management, project risk management, project communication management, and project configuration management.

Uploaded by

A kay
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Software project management

Assignment-1

Que 1. Explain COCOMO 2 Model.


Ans:- COCOMO-II is the revised version of the original Cocomo (Constructive Cost Model) and
is developed at University of Southern California. It is the model that allows one to estimate the
cost, effort and schedule when planning a new software development activity.

COCOMO 2 provides three models to arrive at increasingly accurate cost


estimations. These can be used to estimate project costs at different phases
of the software product. As the project progresses, these models can be
applied at the different stages of the same project.
● Application composition model: This model as the name suggests, can be
used to estimate the cost for prototype development. We know that a prototype is usually
developed to resolve user
interface issues.
● Early design model: This supports estimation of cost at the architectural
design stage.
● Post-architecture model: This provides cost estimation during detailed
design and coding stages.
The post-architectural model can be considered as an update of the original
COCOMO. The other two models help consider the following two factors. Now
a days every software is interactive and GUI-driven. GUI development
constitutes a significant part of the overall development effort. The second
factor concerns several issues that affect productivity such as the extent of
reuse.

Que 2. Differentiate between "known risks" and "predictable risks".


Ans:- Known Risk :
1) It can be uncovered after careful evaluation project plan, business and technical environment
in which the project is being developed, other reliable information resources.

2) E.g. unrealistic delivery date, lack of software poor development environment.

Predictable Risk:
1) Predictable risks are extrapolated from past project experience.

2) E.g. staff turnover, poor communication with the customer, dilution of staff effort as ongoing
maintenance requests are serviced.

Que 3. Explain the different activities in software project management.


Ans:- The list of activities are as follows:
Project planning and Tracking
Project Resource Management
Scope Management
Estimation Management
Project Risk Management
Scheduling Management
Project Communication Management
Configuration Management
Now we will discuss all these activities -

1. Project Planning: It is a set of multiple processes, or we can say that it a task that performed
before the construction of the product starts.

2. Scope Management: It describes the scope of the project. Scope management is important
because it clearly defines what would do and what would not. Scope Management create the
project to contain restricted and quantitative tasks, which may merely be documented and
successively avoids price and time overrun.

3. Estimation management: This is not only about cost estimation because whenever we start to
develop software, but we also figure out their size(line of code), efforts, time as well as cost.

4. Scheduling Management: Scheduling Management in software refers to all the activities to


complete in the specified order and within time slotted to each activity. Project managers define
multiple tasks and arrange them keeping various factors in mind.

5. Project Resource Management: In software Development, all the elements are referred to as
resources for the project. It can be a human resource, productive tools, and libraries.

6. Project Risk Management: Risk management consists of all the activities like identification,
analyzing and preparing the plan for predictable and unpredictable risk in the project.

7. Project Communication Management: Communication is an essential factor in the success of


the project. It is a bridge between client, organization, team members and as well as other
stakeholders of the project such as hardware suppliers.From the planning to closure,
communication plays a vital role. In all the phases, communication must be clear and
understood. Miscommunication can create a big blunder in the project.

8. Project Configuration Management: Configuration management is about to control the


changes in software like requirements, design, and development of the product.The Primary
goal is to increase productivity with fewer errors.
-•-

You might also like