Introduction to the Acme Fashion case study (slide 1)
Case Study Notes
Whenever a point needs to be made about the method being used, about aspects of the case study or just good practice, the notes will appear in a callout box like this.
This opening slide summarizes where we are with the products in the case study, part way through the Feasibility Study. It's written for the imaginary team of analysts working on the project.
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!
Feasibility Study - Analysis Team Notes
The following products are intended for the Feasibility Study. Their completeness is indicated.
- 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, let the project manager know - an early warning system s/he'll appreciate.
- Dataflow Model cont'd
- Logical Data Model
- 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