Assignment Unit - 1 Vikas

You might also like

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 13

B-Tech CSE

Software Project Management


Project - 1
_Vikas Shukla
Definition of a Software Project (SP)
• A software project is a temporary endeavor
undertaken to create a unique product,
service, or result. The temporary nature of
software projects implies that they have a
defined beginning and end, and that they
are not intended to be ongoing.

2
SOFTWARE PROJECTS TYPICALLY INVOLVE THE FOLLOWING
STEPS:

REQUIREMENT GATHERING DESIGN DEVELOPMENT


This involves understanding the needs of the This involves creating a blueprint for the software, This involves coding the software, testing it, and
customer or end user, and translating those needs specifying the architecture, components, and fixing bugs.
into a set of requirements for the software. interfaces.

DEPLOYMENT MAINTENANCE
This involves fixing bugs, adding new features,
This involves making the software available to
and updating the software to keep it up-to-date.
users.

3
SOFTWARE PROJECTS VS OTHER TYPES OF PROJECTS

DEVELOPMENT INVISIBILITY COMPLEXITY


PROCESS
In software projects, the development With software, progress is not Software projects are more complex
process is iterative and involves a lot of immediately visible because the than other engineering projects. For
testing, debugging, and refinement. On work is Logical, but the others example, in a bridge, there is a clear
the other hand, other types of projects structures such as bridges, work structural relationship between parts,
follow a more linear development progress can be seen immediately. In while the relationships between
process that includes designing, software development, there is a software components are much more
prototyping, testing, and level of uncertainty. complex. We cannot compare the
manufacturing. complexity of software until we
implement it. 4
SOFTWARE PROJECTS VS OTHER TYPES OF
PROJECTS

• FLEXIBILITY
• DELIVERY
• CUSTOMIZATION
• COST
• LIFESPAN

5
CATEGORIZING (SP)

COMPULSORY VERSUS
VOLUNTARY SYSTEM Information System versus Embedded Systems

Compulsory system are those INFORMATION SYSTEMS HELPS IN OFFICE DAY TO DAY
systems which the staff of an PROCESSES AND EMBEDDED SYSTEM ARE USED TO
CONTROL MACHINES.
organization have to use if they want
to do the task. A STOCK CONTROL SYSTEM, TRANSACTION PROCESSING
SYSTEM, KNOWLEDGE MANAGEMENT SYSTEM,
Voluntary systems are the systems LEARNING MANAGEMENT SYSTEM, DATABASE SYSTEM
which are voluntarily used by the ETC. WHILE EMBEDDED SYSTEMS CONTROL MICROWAVE
OVEN, AC, MP3 PLAYER, DIGITAL CAMERA, WASHING
users eg computer gaming, school MACHINE ETC.
project etc.

6
CATEGORIZING (SP)

OBJECTIVE-BASED VERSUS OUTSOURCED PROJECT


PRODUCT-BASED SYSTEM

Project whose requirement is to Most of the companies outsource parts of its work to other

meet certain objectives which could companies. There can be several reasons to outsource
project, e.g. company does not have sufficient expertise, or
be met in a number of ways, is
project is to be completed in limited period in that case it
objective-based project.
can be outsourced to company with their development
Project whose requirement is to center.
create a product, the details of which Outsourced project fetch one time revenue in good amount
have been specified by the client, is while product based company project earn over period of
product-based project. time.

7
PROJECT AS A SYSTEM
SYSTEM, SUBSYSTEM & OPEN VERSUS CLOSED SYSTEM
ENVIRONMENT

This is where a subsystemThese are


is working those
at its which are indirect with the
A simple definition of the term system is a
optimum but is having a detrimental effect on the
set of interrelated parts, A system will environment.
overall system. An example of this might be Nearly all systems are open.
normally be part of a larger system and will where software developersOne reason
deliver that
to the users a engineered systems and the
system that is very efficient in its use of machine
itself comprise subsystem.
resources, but is also veryprojects to construct
difficult to modify. them often fail is that
Outside the system there will be system’s
the technical staff involved do not appreciate
environment. This will be made up of things
the extent to which systems are open and are
that can affect the system but over which the
liable to be affected by outside changes.
system has no direct control.

8
MANAGEMENT CONTROL

OBJECTIVES
To have a successful software project,
the manager and the project team
members must know what will
constitute success.

This will make them concentrate on


what is essential to project success.

Projects objectives should be clearly


defined.
The project control cycle

9
STEPS OF PROJECT IDENTIFICATION

• IDENTIFY & MEET • SET & PRIORITIZE • DEFINE


STAKEHOLDERS GOALS DELIVERABLES

• IDENTIFY ISSUES AND • PRESENT THE


• CREATE THE PROJECT
COMPLETE A RISK PROJECT PLAN TO
SCHEDULE
ASSESSMENT STAKEHOLDERS

Pitch deck 10
PROJECT LIFE CYCLE
Every project, from conception to completion, passes through
various phases of a life cycle synonym to life cycle of living
beings. There is no universal consensus on the number of
phases in a project cycle. An understanding of the life cycle is
important to successful completion of the project as it
facilitates to understand the logical sequence of events in the
continuum of progress from start to finish.

Pitch deck 11
Pitch deck 12
STAGES OF PROJECT LIFE CYCLE
1.Initiation
2.Planning
3.Execution
4.Monitoring & Controlling
5. Closing

Pitch deck 13

You might also like