I'm looking to suggest a ideal SDLC model for a small team of small projects roughly of 3 to 6 members with minimum documentation as per ISO Procedures. When I did some research on the the net I came across Basic Unified Process. Can any one let me know any other model or suggest minimum documentation required. Saving Changes...
Sort By:
Michael WoodProject Manager / Business Analyst / Business Process Improvement Guru| Independent ContractorGig Harbor, Wa, United States
Krinshna, the minimum documentation may not be the goal. Maybe it should be the most meaningful and useful documentation. I would suggest the following documentation set.
Requirements Discovery - Change Analysis mapped to Business Goals and Objectives; Existing and Proposed workflow maps mapped to the change analysis - to validate that new workflows correct the right issues; Data Model impact analysis to understand how the database will be impacted; Change Concepts that detail changes in work processes that will be leveraged by IT and the application components affected.-------------------------
Requirements/Design - For each application component identified - Summary Page that defines the purpose, business rules, table/row update rules, etc., I/O model to validate the process at a high level, Samples (if report or screen), Process Logic (diagram detailing out the coding logic), Prototype if possible. ----------------------
Construction through Testing - Test plans, testing scenerios, Test results, approvals for implementation ------------------ Training - training guides, training objectives, training evaluations ------------ Implementation/Deployment - Implementation Plan, Backout Plan. ------------- Post Implementation Review - Survey, Evaluation of Survey results.
Of course all of this nicely wrapped in a project plan. Hope this helps Saving Changes...
I suggest to go with a basic 4 stage "waterfall" methodology Framework - Initiation, Planning, Execution and Closeout. This is the easiest SDLC framework to understand and implement.
Minimum documentation requirements would be 1) Business Case, 2) Project Charter, 3) Monthly PM reports and, 4) Close-out report which includes Lessons Learned.
What is the best model suggested for a Business Intelligence tool developing unit of a research organization? What could be the model that can be suggested and pratised around the world in common? Saving Changes...
Elyse NielsenSenior Project Manager| Ascension Health Information ServicesHaines City, Fl, United States
Hi Krishna,
Check out Agile, with the research team this may be the bet mechanism to move forward.
> I'm looking to suggest a ideal SDLC model for a small team of small
> projects roughly of 3 to 6 members with minimum documentation as
> per ISO Procedures. When I did some research on the the net I cam
> across Basic Unified Process. Can any one let me know any other
> model or suggest minimum documentation required.
> What is the best model suggested for a Business Intelligence tool
> developing unit of a research organization? What could be the
> model that can be suggested and pratised around the world in
> common?
SDLC model should be selected based on the requirements for a project!!
eg.) If you are involved in developing a product, then each version of the product release becomes a project by itself. In one release you might just do bug fix, then you can go with Waterfall model. In the next release you may have complex requirements, in that case you might go with iterative model.
