LECTURE 1

LECTURE 1

1. INTRODUCTION

   • Start by learning some sort of code
     • Small, hypothetical and fairly well defined problem
     • usually the code is within one module
   • We then learn it may not work the first time
     • Testing
     • re-thinking requirments
       • find we may not have all the answers
     • Tracing and debugging

2. A "SIMPLE" SET OF STEPS

   • 1. Understand the Problem
     • Functionalities
     • Non-functionalities(constraints)
       • Performance, security, modifiability, marketability, etc
   • 2. Perform Some Design
     • Based on requirements
       • Organising functionalities
         • diagrams?
       • focus on input/output data
         • data, formats, organisation
       • constraints
   • 3. Code/Impliment
     • Turning the design into actual code
       • depends on how much design has been done
         • either go straight into coding
           • or do some more design
   • 4. Validate/Test
     • check the program results with some predetermined set of inputs
       • test cases
       • results don't match what is expected?
         • debug, fix, retest
   • what actually happens...
     • never really works that well ^^^^

3. BUILDING A SYSTEM

   • huge increase in complexity
     • problem
     • effort
     • solution
     • breadth
       • more functionalities
         • more features
           • MORE DATA
       • more interfaces
       • more users
     • depth
       • more linkages/connections
         • data sharing
         • control passing

4. HANDLING COMPLEXITIES

   • simplification
     • decomposition of the problem
       • modularisation of solution
         • separation of concerns
   • improving technology and tools
     • database to handle information
     • programming & Dev. Platforms
     • Computing network
     • multi-developer configuration management
     • automated testing
   • improving process methodologies
     • coordinate different people performing different tasks
     • guidance for overlapping incremental tasks
       • and for measuring separate artifacts and outcomes