Information Technology Reference
In-Depth Information
defining corresponding success criteria help to lay the foundation for a happy out-
come (Wiegers
2009
).
11.2 Project Termination and Release
During this phase, the product is delivered and an overall project history is col-
lected. A handful of key developers, the technical writers, and the team leaders are
involved with wrapping up the system for installation and acceptance. They are
also responsible for collecting the project history for future use (Bruegge and
Dutoit
1999
). The goal of a release is to make a work product available to other
project participants, often replacing an older version of the artifact. A release can
be as simple as a two-line electronic message or it can consist of several pieces of
information: the new version of the artifact, a list of changes made since the last
release of the artifact, a list of problems or issues yet to be addressed, and an
author. Releases are used to make a large amount of information available in a
controlled manner by batching, documenting, and reviewing many changes
together. Project and client reviews are typically preceded by a release of one or
more deliverables (Schach
2007
).
11.3 Project Wrap-Up and Result Presentation
This is the last phase of SDLC and a presentation will be given to the client by the
development team. First a brief description of the industry, company and specific
facility at which the project will be conducted is given. Then the purpose and goals
achieved will be presented. The project presentation consists of the following steps:
1. Problem description
2. Purpose and goals
3. Approach and methodologies
4. Project deliverables
5. Requirements
6. Software Project Management plan
7. Design
8. Use Cases
9. Standards used
10. Timeline
Presenting the results is the final step in the development cycle. It is an
important step as it is able to convey the projects successes and failures. The
meeting may last up to a couple days and is attended by facilitators, stakeholders
and the architecture team. In advance, the stakeholders are given a workbook
containing a summary of the process, the collection of test cases, and examples of
