Taute Software Maintenance Model
Taute Software Maintenance Model Assignment Help | Taute Software Maintenance Model Homework Help
Taute Software Maintenance Model
The model was developed by B.J. Taute in 1983 and is very easy to understand and implement. It is a typical maintenance model and has eight phases in cycle fashion.
(ii) Estimate phase: This phase is devoted to estimate the time and effort required to make the change. It is difficult to make exact estimates. but our objective is to have at least reasonable estimate of time and efforts. Impact analysis on existing system is also required to minimize the ripple effect.
(iii) Schedule phase: We may like to identify change request for the next scheduled release and may also prepare the documents that are required for planning.
(iv) Programming phase: In this phase, source code is modified to implement the requested change. All relevant documents like design document, manuals, etc. are updated accordingly. Final output is the test version of the source code.
(v) Test phase: We would like to ensure that modification is correctly implemented. Hence, we test the code. We may use already available test cases and may also design new test cases. The term used for such testing is known as regression testing.
(vi) Documentation phase: After regression testing, system and user documents are prepared and updated before releasing the system. This helps us to maintain co-relation between code and documents.
(vii) Release phase: The new software product along with updated documents are delivered to the customer. Acceptance testing is carried out by the users of the system.
(viii) Operation phase: After acceptance testing, software is placed under normal operation. During usage, when another problem is identified or new functionality requirement is felt or even the enhancement of existing capability is desired, again a ‘change request’ process is initiated. If we do so, we may go back to change request phase and repeat all phases to implement the change.
For more help in Taute Software Maintenance Model click the button below to submit your homework assignment
Taute maintenance model
(i) Change requires phase: Maintenance team gets a request in a prescribed format from the client to make a change. This change may fall in any category of maintenance activities. We identify the type of requires (i.e., corrective, adaptive, preventive or preventive) and assign a unique identification number of request.(ii) Estimate phase: This phase is devoted to estimate the time and effort required to make the change. It is difficult to make exact estimates. but our objective is to have at least reasonable estimate of time and efforts. Impact analysis on existing system is also required to minimize the ripple effect.
(iii) Schedule phase: We may like to identify change request for the next scheduled release and may also prepare the documents that are required for planning.
(iv) Programming phase: In this phase, source code is modified to implement the requested change. All relevant documents like design document, manuals, etc. are updated accordingly. Final output is the test version of the source code.
(v) Test phase: We would like to ensure that modification is correctly implemented. Hence, we test the code. We may use already available test cases and may also design new test cases. The term used for such testing is known as regression testing.
(vi) Documentation phase: After regression testing, system and user documents are prepared and updated before releasing the system. This helps us to maintain co-relation between code and documents.
(vii) Release phase: The new software product along with updated documents are delivered to the customer. Acceptance testing is carried out by the users of the system.
(viii) Operation phase: After acceptance testing, software is placed under normal operation. During usage, when another problem is identified or new functionality requirement is felt or even the enhancement of existing capability is desired, again a ‘change request’ process is initiated. If we do so, we may go back to change request phase and repeat all phases to implement the change.
For more help in Taute Software Maintenance Model click the button below to submit your homework assignment