SOFTWARE DEVELOPMENT CYCLE

SOFTWARE DEVELOPMENT CYCLE

1. Time keeper

   • - makes sure deadlines are being adhered too
   • uploads the teams work before finals deadlines
   • Required skills
     • -excellent communication skills
     • -organised

2. Gantt chart

   • start and end date of each task
   • dependencies of each task
   • milestones
   • task owner( time keeper)

3. PLANNING

4. ANALYSIS

   • METHODOLOGIES
     • WATERFALLS
       • Requirements, analysis, design, implementation, testing, deployment, maintenance
         • progress can be easily measured
         • making changes can be difficult
         • requirements must be clearly defined and known before development
     • AGILE
       • Plan, Design, Develop, Test, Release, Feedback and then back to plan. This would go in a circle
         • continuous improvement at every stage
         • focus can be lost if final outcome is not clear
         • continuous collaboration
         • difficult to assess effort
         • changes to requirements is acceptable
   • IDENTIFY RISKS
     • assess risks to it successful outcome
     • CONTINGENCY PLANS = plans of action to be taken if risks arises
     • plans may change to reduce risks
     • MITIGATION PLAN
       • 1) Provide description of the risk
         • 2) likeliness of risk ( low, medium, high )
           • 3) seriousness of risk ( low, medium, high )
             • 4) estimation to how many days it could set back project
               • 5) Describe the mitigation process that will take place, to reduce the risks or effects of risks

5. Requirement Analysis

   • 1) FUNCTIONAL
     • What the system needs to do. describe a particular behaviour OR function of the system
       • EXAMPLE = system must compute the sum of remaining
   • 2) NON- FUNCTIONAL
     • How it will do it. quality attributes of a system.
       • EXAMPLE = computed in less than a second, output must be rounded to certain decimal places
   • BOTH FUNCTION/NON- FUNCTIONAL ARE BRAINSTROMED TOGETHER, EVERY DETAIL NEEDS TO BE LISTED

6. PRODUCING REQUIREMENTS

   • 1) WHO, needs to interact with the software + what way
     • 2) WHAT, does the software need to compute + output
       • 3) WHERE, does the output go
         • 4) WHEN, does the task need to be computed + before or after something needs to be computed + independent or not ?
           • 5) HOW, is the task going to be computed

7. PSEUDOCODE

   • DEFINITION = Set of clearly defined instructions that compute something
     • clear general description of a computation that can be implememented in any programming language
     • Example = LIKE CHOCOLATE, sequence of instructions. 1) Roast the cocoa beans, 2) remove the shells, 3)Grind the shells, 4) add milk and sugar , 5) put into desired shape
   • Within the pseudocode we have variables