Software Design and Development

Software Design and Development

1. DEVELOPMENT METHODOLOGIES

   • TRADITIONAL (WATERFALL)
     • * Top down/ Stepwise refinement
       • Loads of time spent completing requirements
         • Working on bigger problems then smaller
           • Then designing and coding a piece of software
   • AGILE
     • agile sprints
       • planning and analysis
         • Design
           • coding
             • Testing
               • review
     • highest priority is to satisfy the customer
       • welcome changing requirements
         • deliver work frequently
           • co-op between clients and developers daily
             • build projects around motivated individuals
               • face to face conversations on updates
                 • primary measuers
                   • sustainable development

2. SOFTWARE DEVELOPMENT PROCESS

   • Analysis
     • Design
       • Implementation
         • testing
           • Documentation
             • Evaluation
               • Maintenance

3. ANALYSIS AND DESIGN

   • purpose
     • scope
       • boundaries
         • Functional Requirements
   • Design Techniques
     • Pseudocode
       • Data flow table
         • interface design

4. PARAMETER PASSING

   • Procedurse/Subroutines
     • Functions
       • local vairables

5. FILE HANDLING IMPORT CSV

   • open/creating, reading/writing, closing
     • reading a file " readline/ read"
       • writing a file "write/writelines"

6. DATA STRUCTURES PARALLEL ARRAYS

7. STANDARD ALGORITHMS

   • Find min and Max
     • Linear Search
       • counting occurances
         • input validation

8. DATA STRUCTUERS (DATA CLASS)

9. STRING HANDLING

   • sub string
     • start index
       • end index

10. TESTING AND DEBUGGING

    • reliable
      • robust
        • portable
          • fit for purpose
    • test data
      • normal - this data that the program should be expected to use in normal operation - yes
        • extreme - this data at the edge of what is acceptable. such as high and low limits or boundaries - yes
          • exceptional - this is invalid data. robust programs should reject this - NO

11. EVALUATION