System Development Description and Exercise

Project Cycle:  ("->" means a deliverable)

Planning

 ->requirements document (database questions to be answered)
  ->high level task list
  ->high level budget

Gather proposals (We aren't doing this)
 ->select vendors for hardware and software

Systems Analysis
 ->functional specification (to give for analysis and creating new business procedures)
         - high level description of what the users will get when the project is done
         - high level OOB
         - high level DFD

Systems Design
-> select exact hardware and software (we aren't doing this)
-> technical specification (to give for coding and creating training manuals)
       - form screen layouts
       - table layouts
       - query descriptions
       - report layouts
 -> detailed implementation schedule
->  present the plan to the team

Implementation
  -> program unit tested code
  -> testing using test plans (unit, function, system, regression, parallel)
  -> training using training plan
  -> live turnover plan  
  -> system operational (live date)

Maintenance
    -> track and fix problems and make changes

System development exercise:

Your accounts receivable system (the one that tracks money coming into your business), currently prints all statements at the end of the month. You want to request a change to make half the statements print after two weeks, and the rest print at the end of the month.  How would you design this change? How would you select which customers printed in the first batch and which printed in the second?

On a piece of paper, sketch the screen you will use to submit the statements.

Write a flow chart of the new program logic.

What would you have to do to test this change?

What documentation would you want to see?

How would you schedule the implementation of this change?

What meetings would you hold during the project cycle?