• Wrong document? Swap it for free
  • Written by students who passed
  • Immediately available after payment
  • Read online or as PDF
Sell
Where do you study
Your language
Document preview thumbnail
Preview 3 out of 28 pages
Summary

INF3708 - Software Project Management Summary.

Document preview thumbnail
Preview 3 out of 28 pages

INF3708 - Software Project Management Summary. CHAPTER 1 *Characteristics that distinguish projects: [10]1 Non-routine tasks are involved. Planning is required. Specific objectives are to be met or a specified product is to be created. The project has a predetermined time span. Work is carried out for someone other than yourself. Work involves several specialisms. People are formed into a temporary work group to carry out the task. Work is carried out in several phases. The resources that are available for use on the project are constrained. The project is large or complex. *Characteristics of software projects which make them particularly difficult (as identified by Fred Brooks): [4]2 Invisibility – When a physical artefact (e.g. a bridge) is constructed the progress can actually be seen. With software, progress is not immediately visible. Complexity – Software products contain more complexity than other engineered artefacts per dollar/pound/euro/rand spent. Conformity – ‘Traditional’ engineers work with physical systems and materials which are governed by consistent physical laws. Software developers have to conform to the requirements of human clients. Flexibility – Software is easy to change (which is one of its greatest strengths) and must therefore change to accommodate the physical or organizational system it interfaces with, not the other way around. Successive processes that bring a new system into being: [3]3 1. Feasibility Study (Is it worth doing?) 2. Plan (How do we do it?) 3. Project Execution (Do it!) 1 p. 3 2 pp. 4-5 3 pp. 5-6 5 ISO 12207 Software Development Life Cycle: [13]4 Requirements: o Requirements analysis. o Architecture design. o Requirements analysis. Design: o Architecture design. o Requirements analysis. Code and Test: o Detailed design. o Code and test. o Integration. o Qualification test. o Integration. o Qualification test. Installation/Acceptance Support: o Installation. o Acceptance Support. Types of Stakeholders: [3]5 A: Internal to the project team (and implicitly to the organization). B: External to the project team, but within the same organization. C: External to both the project team and the organization. 4 pp. 6-8 5 p. 11 Organization Project Team 6 Well-defined objectives are described by: [5]6 SMART: Specific Measurable Achievable Relevant Time constrained Software project objectives: [4]7 The agreed functionality is delivered To the required level of quality On time Within budget Management Activities: [8]8 Planning – Deciding what is to be done. Organizing – Making arrangements. Staffing – Selecting the right people for the job. Directing – Giving instructions. Monitoring – Checking on progress. Controlling – Taking action to remedy hold-ups. Innovating – Coming up with new solutions. Representing – Liaising with clients, users, developer, suppliers and other stakeholders. 6 p. 12 7 p. 14 8 p. 15 7 CHAPTER 2 Business case (for a feasibility study) document contains: [10]9 1. Introduction and background to the proposal 2. The proposed project 3. The market 4. Organizational and operational infrastructure 5. The benefits 6. Outline implementation plan 7. Costs 8. The financial case 9. Risks 10. Management plan Key aspects of project portfolio management: [3]10 Portfolio definition Portfolio management Portfolio optimization Categories of direct costs: [3]11 Development costs – including development staff costs Setup costs – the costs of putting the system into place (new hardware, file conversion, recruitment, staff training). Operational costs – cost of operating the system after installation. *Net Profit12:

Content preview

INF3708 SUMMARY
V




2020
UNISA
Semester 1

, 1



Contents
Chapter 1........................................................................................................................................ 4

*Characteristics that distinguish projects: [10] .............................................................. 4
*Characteristics of software projects which make them particularly difficult (as
identified by Fred Brooks): [4] ......................................................................................... 4
Successive processes that bring a new system into being: [3] ................................... 4
ISO 12207 Software Development Life Cycle: [13] ....................................................... 5
Types of Stakeholders: [3] ............................................................................................... 5
Software project objectives: [4] ..................................................................................... 6
Management Activities: [8] ............................................................................................ 6
Chapter 2........................................................................................................................................ 7

Business case (for a feasibility study) document contains: [10] .................................. 7
Key aspects of project portfolio management: [3] ..................................................... 7
Categories of direct costs: [3] ........................................................................................ 7
*Net Profit: ........................................................................................................................ 7
*Payback Period: ............................................................................................................ 7
*Return on Investment (ROI): .......................................................................................... 8
*Net Present Value (NPV): .............................................................................................. 8
Programme Management: ............................................................................................ 8
Different forms of programmes: [5]................................................................................ 8
Sections of a business case’s programme brief: [3] ..................................................... 8
Chapter 3...................................................................................................................................... 10

Step Wise: [11] ............................................................................................................... 10
Chapter 4...................................................................................................................................... 11

*Advantages of running off-the-shelf software: [3] .................................................... 11
*Disadvantages of running off-the-shelf software: [4]................................................ 11
Project characteristics: [6] ............................................................................................ 11
Types of uncertainties: [3] ............................................................................................. 11
The waterfall model: [8] ................................................................................................ 12
Types of prototypes: [2] ................................................................................................ 12
Advantages of prototypes: [9]..................................................................................... 12
Disadvantages of prototypes: [6] ................................................................................ 12
Types of changes during prototyping: [3] ................................................................... 13

, 2


Advantages of incremental delivery: [8] .................................................................... 13
Disadvantages of incremental delivery: [3] ................................................................ 13
*Agile manifesto: [4]...................................................................................................... 13
Core Atern (Agile) principles: [8] ................................................................................. 13
Atern life-cycle phases: [4] ........................................................................................... 14
Importance of requirements (MoSCoW): [4] .............................................................. 14
XP principles: [4] ............................................................................................................ 14
XP practices: [12] .......................................................................................................... 14
XP limitations: [5] (p. 98 – 99) ........................................................................................ 15
Chapter 5...................................................................................................................................... 16

Difficulties of estimating effort: [6] ............................................................................... 16
Calculating estimated effort: ....................................................................................... 16
Laws for over- and under-estimates: [3] ...................................................................... 16
Bottom-up estimation: .................................................................................................. 16
Top-down estimation: ................................................................................................... 16
Euclidian distance: ........................................................................................................ 17
COnstructive COst MOdel (COCOMO): ..................................................................... 17
Stages of COCOMO II: [3] ............................................................................................ 17
COCOMO II: .................................................................................................................. 17
Chapter 6...................................................................................................................................... 19

Objectives of activity planning [5]............................................................................... 19
Approaches to identifying activities [3] ...................................................................... 19
Network planning models [3] ....................................................................................... 19
Precedence network (activity-on-node) rules [8] ...................................................... 19
Labelling conventions ................................................................................................... 20
Activity float [2] ............................................................................................................. 20
Activity-on-arrow rules [8] ............................................................................................. 20
Labelling conventions ................................................................................................... 21
Chapter 7...................................................................................................................................... 22

Lyytinen-Mathiassen-Ropponen risk framework (STAT) [4] ......................................... 22
*Framework for dealing with risks [4] ........................................................................... 22
Risk exposure ................................................................................................................. 22
Risk planning alternatives [4] ........................................................................................ 22
Risk Reduction Leverage (RRL)..................................................................................... 22

Document information

Uploaded on
May 7, 2022
Number of pages
28
Written in
2021/2022
Type
Summary
$3.30

Wrong document? Swap it for free Within 14 days of purchase and before downloading, you can choose a different document. You can simply spend the amount again.
Written by students who passed
Immediately available after payment
Read online or as PDF

Seller avatar
Reputation scores are based on the amount of documents a seller has sold for a fee and the reviews they have received for those documents. There are three levels: Bronze, Silver and Gold. The better the reputation, the more your can rely on the quality of the sellers work.
Tutorexpert01
3.9
(161)
Sold
1039
Followers
815
Items
5501
Last sold
2 months ago




Why students choose Stuvia

Created by fellow students, verified by reviews

Quality you can trust: written by students who passed their tests and reviewed by others who've used these notes.

Didn't get what you expected? Choose another document

No worries! You can instantly pick a different document that better fits what you're looking for.

Pay as you like, start learning right away

No subscription, no commitments. Pay the way you're used to via credit card and download your PDF document instantly.

Student with book image

“Bought, downloaded, and aced it. It really can be that simple.”

Alisha Student

Working on your references?

Create accurate citations in APA, MLA and Harvard with our free citation generator.

Working on your references?

Frequently asked questions