INF3708 EXAM PACK

1.1 Specific plan/design or planned undertaking 1.2 Project scope where outline plan is detailed Includes: Work/Product Breakdown - Standards - Risk Management 1.3 Difference between net cost and total income of project over the life of the project 1.4 Time taken to break even or pay back initial investment 1.5 Uncertain event/condition – may have positive or negative effect on project Invisibility – Progress not immediately visible - process of making the invisible visible Complexity – per R spent, software project more complex than other engineered artefacts Conformity – Traditional engineers usually work with physical systems such as cement & steel Inconsistency – developers have to conform - requirements of human clients – humans are inconsistent 2.2.1 Assesses if a project is worth starting, that it has a valid business case 2.2.2 If feasibility study indicates project = viable, then project can start Outlined plan – created – detailed on 1st stage 2.2.3 Contains design & implementation sub-phases INF3708 EXAM PACK Verified Q AND A. Project Objectives: Agreed functionality on required level of quality on time and within budget Management process – helps an org get a view of information about all projects Year Project 1 Project 2 Break-even Analysis 0 - 100,000 - 100,000 1 10,000 30,000 -90,000 -70,000 2 10,000 30,000 -80,000 -40,000 3 10,000 30,000 -70,000 -10,000 4 20,000 30,000 -50,000 20,000 5 100,000 30,000 50,000 50,000 Net Profit 50,000 50,000 Project 1 Break Even = Break even Year - (Profit in BE year/Cash flow BE year) = 5 - (50000/) 4.50 Project 2 Break Even = Break even Year - (Profit in BE year/Cash flow BE year) = 4 - (20000/20000) 3.00 Both projects have same net profit but project 2 has shorter payback period Project 2 a b a x b Year Project 1 Discount Factor NPV 0 -100,000 1.0000 -100,000 1 10,000 0.9091 9,091 2 10,000 0.8264 8,264 3 10,000 0.7513 7,513 4 20,000 0.6830 13,660 5 100,000 0.6209 62,090 618 4.1.1 Classical model of system development Also known as one-shot or once through model Sequence of activities working from top to bottom Limited scope for interaction (strength) Creates natural milestones at end of each phase 4.1.2 Another way of looking at the waterfall model Greater level of detail - considered at each stage 4.2.1 Test ideas then discarded when dev of operational system starts 4.2.2 Developed and modified until in a state where becomes operational system