We have got one project for which we have to do only bug fixing, change in features, or new feature enhancement.
What documents will be needed in this project. We are given one complete application so is there a need to prepare SRS, Design Document, etc where client has given all the specification & DFD. Can we follow the Service Process for Feature Enhancement for eg Problem fixing/Change/Feature Enhancement Request. please provide some document related to such kind of projects, my mailID is email@example.com
Dealing with a mature product, where as you say the work is enhancement/bug fix, is in fact more complex than for a new product.
You need the documentation for the existing product and new documentation for the enhancements.
For each enhancement, you are not only looking at the new features, you are also looking at potential impact on existing features.
No shortcuts I'm afraid.
You are asking for us to supply all documentation for a project? This sounds like asking us to do your jjob for you.
Please let me know if the following steps should be followed in the above case:
Project Planning (The scope of the project as mentioned in the Contract)
Baseline for Configuration Management
Testing(if bugs remained start from Bug Fixing)
UAT (if bugs found start from Bug Fixing)
Final Release (Implementation as per contract)
Track on Non Confirmities (if bugs found start from Bug Fixing)
Please tell if this will do or we further need to do more documentation
I would say yes, deffinitly all thos, plus I would establis an SLA, (Service Level Agreement) stating exactly what you are responsible for. What if you run across a bug in the original software, should you track it? Yes! Unless the project manager says, Oh, that's alright, no one has complained about it yet. Then what would you do with it? The SLA would say what your responsibility is in this case.
Because there is no shortcut, as Rich says, you should consider "maintenance windows" that allow you to collect change requests until you can do a bundled implementation where the testing costs can be shared across multiple products or clients as opposed to developing each change request as a new project. Typically you end up accumulating a bundle until a specific time (quarterly, semi-annual or annual) or until a critical bug is reported.