Feasibility Study - Analysis Team Notes

It's good practice to maintain a log of progress with the deliverables to date. If there's a team of analysts it should be maintained as a result of daily / weekly catchup sessions. Maintaining a percentage (or effort to) complete can help with planning.

It also forms a great tool for keeping the project manager appraised of progress - and might mean you don't need to do a separate weekly progress update report!

• Terms of Reference - Signed off, complete.
• Dataflow Model
• Dataflow Diagram - top level done. Decomposition to level 2 (and beyond?) still to be done after sessions with the business.

Notice how you've got a great basis for estimating now? You've got a good idea of the number of processes to investigate and a feel for their complexity.

You can start booking interviews with the various business reps to cover off the decomposition.

You should have a rough feel as to how long each process investigation will take.

If users can't devote the time when you need it, it is relatively easy to see whether the various milestones in the project plan are jeopardised. If so, have speaks with the project manager.

..an early warning system :)

• Elementary Process Descriptions (for top level) - done to BA notes standard at this stage. Will be removed and re-done at the lower levels as we decompose to them
• External entity descriptions
• Datastore Descriptions first cut done - to be completed (TBC)
• I/O Descrptions - first cut done (TBC)
• Logical Data Model
• Logical Data Structure Diagram - done at first draft but Purchase Order and Purchase Order Line entities to be added and described.
• Entity and Data Item (attribute) Descriptions - done at first draft (but see previous bullet)
• Relationship Descriptions - done on LDS but full descriptions TBD
• User Catalogue - TBD
• Problems / Requirements List
• Event Catalogue Some events fully documented but TBC
• Event / Entity Xref - TBD
• Reports Catalogue - TBD
• Non-functional aspects - first draft