Software Design and Development

Software Design and Development

1. Development Methodologies

   • Agile
     • client is involved throughout the entire process
     • teams communicate through the whole process
     • any documentation created should focus purely on the progress of the project
     • breaks development down with short goals called sprints
     • adaptive methodology focuses on adapting quickly to changes in reality
     • testing is carried out in conjunction with development
   • Waterfall
     • client is involved at the start and the end of development
     • teams work mostly in isolation with communication between each phase
     • project specifications are created at the start of the project
     • follows a strict plan with a timescale at the start of the project
     • predicative methodology focuses on analysing and planning for the future in detail and catering for known risks
     • testing is carried out when implementation phase is complete

2. Software development process

   • Analysis
     • Design
       • Implementation
         • Testing
           • Documentation
             • Evaluation
               • Maintenance
   • Iteration
     • Phases are repeated on discovery of new information
   • Specification
     • Legal binding document
       • clearly defines the functions that the software must perform in order to meet the requirements by the user
   • Maintance
     • Perfective
       • Happens in response to requests from the user to add new functions
     • Corrective
       • Fixing errors in the software
     • Adaptive
       • adapting the software the run on windows 10 rather than windows 7

3. Analysis and Design

   • Purpose
     • general description and purpose of the software
   • Scope
     • a list of deliverables that the project will hand over to the client
   • Boundaries
     • limits to what the project can do
   • Functional requirements
     • the features and functions that must be delivered by the system
   • Pseudocode
     • text based notation with any sub program
   • Data Flow
     • shows the different information that must flow in and out of sub programs
   • Structural diagram
     • hierarchical structure showing refinements

4. Testing and Debugging

   • Reliable
     • Robust
       • Portable
   • Alpha testing
     • pre release and done by team
   • Beta testing
     • done by independent test group
   • Syntax
     • Execution
       • Logic
         • runs but not correct result
       • program doesn't run
     • program doesn't run due to typing error
   • Dry runs
     • Trace tables
       • Breakpoints
         • Watchpoints

5. Evaluation

   • Fitness for purpose
   • Efficient use of coding contrusts
   • Usability
   • Maintainability
   • Robustness

6. Standard Algorithms

   • Find min and max
   • Count occurrences
   • Linear search + found flag
   • Input validation