Task Partitioning, Sequencing and Project Planning

The tasks required for the service might be broadly partitioned into:

0.      Set up database tables and account file

1.      Form input

2.      Connect to DB

3.      Authenticate reporter

4.      Insert incident in DB

5.      Copy incident report to browser

6.      Authorize email request

7.      Make & send email summary

8.      Various optional enhancements

This list is a bird's eye view of the problem solution and with no special concern for details or the sequence of tasks has to be executed by the system.  After thinking about the acceptability of this breakout of the solution's basic steps, you might sequentially order the tasks in the order you think you will be able to most easily handle the problem, sort of their cognitive order, as opposed to the process order in which the steps are supposed to be executed to accomplish the service:

           Easier to do:

0.  Set up database tables and account file

2.  Connect to DB

1.  Form input

5.  Copy incident report to browser

4.  Insert incident in DB

7.  Make & send email summary

Harder to do:

3.  Authenticate reporter

6.  Authorize email request

8.  Various optional enhancements

The actual process order for the steps / parts would be like:

            Ultimate Order:

2  Connect to DB

1. Form input

3. Authenticate reporter

4. Insert incident in DB

5. Copy incident report to browser

6  Authorize email request