Scribd
Upload
34 views9 pages

Software Project Management: Activities Methodologies

1) Software project management involves feasibility studies, planning, and executing projects according to plans while allowing for changes. 2) The software development life-cycle (ISO 12207) includes requirements analysis, architecture design, coding and testing individual components, integration, qualification testing, installation, and acceptance support. 3) A methodology is a set of methods that provide a way of working within a specific context according to plans that define activities, dates, staffing, tools, and materials.

Uploaded by

Unichrone Learning
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
34 views9 pages

Software Project Management: Activities Methodologies

1) Software project management involves feasibility studies, planning, and executing projects according to plans while allowing for changes. 2) The software development life-cycle (ISO 12207) includes requirements analysis, architecture design, coding and testing individual components, integration, qualification testing, installation, and acceptance support. 3) A methodology is a set of methods that provide a way of working within a specific context according to plans that define activities, dates, staffing, tools, and materials.

Uploaded by

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

Software Project Management

Activities Methodologies
Activities covered by project management

Feasibility study
Is project technically feasible and worthwhile from a business point
of view?
Planning
Only done if project is feasible
Execution
Implement plan, but plan may be changed as we go along

2
The software development life-cycle (ISO 12207)
ISO 12207 life-cycle
• Requirements analysis
– Requirements elicitation: what does the client
need?
– Analysis: converting ‘customer-facing’
requirements into equivalents that developers can
understand
– Requirements will cover
• Functions
• Quality
• Resource constraints i.e. costs

4
ISO 12207 life-cycle
• Architecture design
– Based on system requirements
– Defines components of system: hardware,
software, organizational
– Software requirements will come out of this
• Code and test
– Of individual components
• Integration
– Putting the components together

5
ISO12207 continued
• Qualification testing
– Testing the system (not just the software)
• Installation
– The process of making the system operational
– Includes setting up standing data, setting system
parameters, installing on operational hardware
platforms, user training etc
• Acceptance support
– Including maintenance and enhancement

6
Plans, methods and methodologies

Methodology = a set of methods

Context

Plan
Methods
+ start and end dates for each activity,
A way of working staffing, tools and materials etc

7
Some ways of categorizing projects

Distinguishing different types of project is important as


different types of task need different project
approaches e.g.
• Voluntary systems (such as computer games) versus
compulsory systems e.g. the order processing system
in an organization
• Information systems versus embedded systems
• Objective-based versus product-based
• Product-development versus outsourced

8
Stakeholders
These are people who have a stake or interest in the
project
In general, they could be users/clients or
developers/implementers
They could be:
• Within the project team
• Outside the project team, but within the same
organization
• Outside both the project team and the organization
Different stakeholders may have different objectives –
need to define common project objectives

You might also like