|
Swim Lane Diagram
The diagram below shows the deliverables that are due by each major party at the end of each development step. Note that some of the steps defined earlier actually overlap in this document because some of the steps can occur concurrently. An assumption is made here that the development team is made up of more than one person, at least one of which is a senior analyst who can design a detailed system implementation plan while the programmers do the coding.
Once a Functional System Design (FSD) is completed, the QA team should be called in (preferably upon delivery of the FSD). The QA team can use the information from the DFD and ERD diagrams to create a high-level test strategy, which is fleshed out into more detailed test plans upon the delivery of the Technical System Design (TSD). By the time the program is coded, all of the test scripts will have been prepared.
Another note on concurrency: Once the client has approved an FSD, the approval of the TSD is often a formality. Therefore, as each Module Design is completed, the work can be handed off to the programmers on the assumption that only minor changes to the design will be subsequently required, and any re-work can be quickly accomplished. This approach potentially can shave months off of a development schedule. Ideally, the completion of the actual programming will only slightly lag the approval of the TSD, the gain in time being used to provide additional unit testing or technical support to the Test Team. The bulk of the programming team may be moved to other projects at this time.
Glossary
| Home | About Us | Clients | Project Management Resources | Tools & Templates | Links |
|
The 'P' in PM is as much about 'PEOPLE' Management as it is about 'PROJECT' Management. ~ Cornelius Fichtner
Nothing is less productive than to make more efficient what should not be done at all. ~ Peter Drucker
|
