|
Construction & transition of new enterprise applications
includes the development, test, and deployment workflows.
development
The purposes of development are to:
Define the organization of the code, in terms of
implementation subsystems organized in layers.
Implement classes and objects in terms of components
(source files, binaries, executables, and others).
Test the developed components as units.
Integrate the results produced by individual
implementers (or teams), into an executable system.
The development artifacts consist of:
Implementation Model – Defining components and
implementation subsystems.
Integration Build Plan – Defining the order in
which the components and subsystems should be implemented and specifying
builds to be created to integrate the system.
Build – Constructing components that deliver a
testable subset of the run-time functions and capabilities of the
system.
test
The purposes of testing are to:
Verify the interaction between objects.
Verify the proper integration of all components of the
system.
Verify that all requirements have been correctly
implemented.
Identify and ensure defects are addressed prior to the
deployment of the system.
The test artifacts consist of:
Test Plans – Identifying the purpose and goals of
testing, the strategies to be used to implement and execute testing, and
the resources needed.
Test Cases – Identifying the conditions which
will be implemented in test and are necessary to verify successful and
acceptable implementation of the system requirements.
Test Scripts – Automating the execution of
test procedures.
deployment
The purposes of deployment are to:
Ensure that the system is available for its end users.
Ensure that the end users can effectively utilize the
system.
The deployment artifacts consist of:
Deployment Plan - Provides a detailed schedule of
events, persons responsible, and event dependencies required to ensure
successful cutover to the new system.
Installation & Setup Guide – Step-by-step
instruction for application and database installation.
Training Manual – Supplementary material for
training including handouts and examples.
Operating Manual – Instructions for various
system processes by job functions or roles.
User Reference Manual – The source of reference
using the application.
Online Help - Context sensitive at screen and
field level with hyperlink and provides a portion of user reference
manual.
Systems Manual – Used for application maintenance
and modifications; includes data dictionary, entity-relationship
diagrams, function hierarchy diagram, application map, and interfaces.
|