INF3708 SUMMARY
V
2020
UNISA
Semester 1
1
Contents
Chapter
... [Show More] 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
3
*PERT............................................................................................................................... 23
Steps for calculating the probability of meeting/missing target date ..................... 23
Chapter 8......................................................................................................................................24
Categories of Resources [7]......................................................................................... 24
*Factors to consider when allocating individuals to tasks [5].................................... 24
Categories of cost [3]................................................................................................... 24
Chapter 9......................................................................................................................................25
Traffic-light method steps [5]........................................................................................ 25
Earned Value Analysis................................................................................................... 25
*Prioritizing Monitoring [5] ............................................................................................. 26
*Ways to shorten the critical path [5].......................................................................... 26
Bibliography..................................................................................................................................27
4
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 [Show Less]