Business Requirements Definition (RD)
RD.010 -
Identify Financial and Operating Structure
In this task, the project team develops a complete picture of the
organization’s financial and operating structure.
Deliverable
The deliverable for this task is the Financial and Operating Structure.
This document portrays the legal entity structure, business organizations,
financial operating environment, revenue (and/or cost) centers, and
consolidation path. It may also catalog other business entities.
RD.020 - Conduct
Current Business Baseline
In this task, the project team examines current processes and practices
to identify how the existing business system meets current business
requirements.
Deliverable
The deliverable for this task is the Current Business Baseline. It
consists of the Current Business Process model, Process Questionnaires, and the
Process Improvement and Redesign List. You may need to include other business
process documentation as well.
RD.030 - Develop
Future Process Model
This task defines the future business model in the form of integrated
process flows built upon the business processes supported by the new
applications. Identify the complete set of events to which the business
function responds in order to meet its objectives, describe the future
processes that the business performs in order to respond to each of the events,
and identify each of the steps in those processes.
Deliverable
The deliverable for this task is the Future Process Model. It consists
of the Event Catalog, Process Listing and Descriptions, and Process Flow
Diagrams. Optionally, it may include Process Step Catalogs.
RD.040 - Develop
Future Business Function Model
In this task you create a hierarchical model of the functions identified
by the Future Process Model. This classification process assists you in
checking the completeness of your future business process model You usually
conduct this task in parallel with and in support of Develop Future Process
Model (RD.030).
Deliverable
The deliverable for this task is the Future Business Function
Model. The Future Business Function
Model deliverable shows all the business functions arranged in a hierarchy
diagram. It also specifies the data usage at each function.
RD.050 -
Establish Process and Mapping Summary
During this task you create the repository for key project findings and
decisions that occur during the implementation.
Deliverable
The deliverable for this task is the Process and Mapping Summary. It
provides a single source of information on key implementation decisions for new
project members and executive management. The Project Manager can also use it
to maintain a status on the progress of deliverables in requirements definition
through build and test.
RD.060 - Gather
Business Volumes
In this task you research the current business volumes and estimate the
future projected operational processing volumes, transaction patterns, and data
storage volume requirements. This information provides the basis for
determining the size and performance of the new production system.
Deliverable
The deliverable for this task is the Business Volume Requirements.
RD.070 - Create
Business Requirements Scenarios
In this task you define detailed business requirements and perform an
initial assessment of application fit to these requirements.
Deliverable
The deliverable for this task is the Business Requirements Scenarios
(BRS). At least one BRS is created for each business process, linking
requirements to process steps.
RD.080 -
Determine Audit and Control Requirements
This task identifies the high levels and policies that affect business
and system security, control, and procedures.
Deliverable
The deliverable for this task is the Audit and Control Requirements.
RD.090 -
Identify Business Availability Requirements
This task identifies the business operating requirements that the
operating functions and information systems functions agree are necessary to
support the business processes. It also summarizes contingency situations the
company must guard against and documents the approach to managing delay,
failure, or other unexpected results that could imperil daily business
operations.
Deliverable
The deliverable for this task is the Business Availability Requirements
document.
RD.100 - Develop
Reporting Requirements
In this task you develop the reporting requirements. Reports are
typically outputs of business processes that are used as tools in support of
business process operations.
Deliverable
The deliverable for this task is the Master Report Tracking List. It is
the primary repository for all information collected about a report
requirement. It should contain system and report name, business purpose,
frequency, priority, user name and contact information.
Business Requirements Mapping (BR)
BR.010 - Prepare
Mapping Environment
During this task, you either install a new application or prepare an
existing application environment for mapping activities.
Deliverable
The deliverable for this task is a Configured Mapping Environment.
BR.020 - Map
Business Requirements
In this task you assess the fit of standard application and system
features to detailed business requirements.
Deliverable
A Business Requirements Mapping Form (BRM) is the deliverable for this
task. There is one BRM per key business requirement or gap. The BRM is an
extension of the BRS, since it shows the result of the mapping activity.
BR.030 - Map
Business Data
For this task you map the data elements from the legacy system to the
target application module(s), business objects, and attributes. The primary
purpose of this task is to discover at an early point in the project life cycle
whether any business objects or attributes in the legacy system are not being
stored in the application. This task should also determine whether the
application stores any required attributes that the legacy system does not
currently store.
Deliverable
The deliverable for this task is the Business Data Mapping Form. The
deliverable records the standard application module, business object, and
attribute. Also record the legacy system file name and fields for each business
object in the table provided in the deliverable template.
BR.040 - Conduct
Integration Fit Analysis
In this task you identify the new integration points that you require,
based on your conceptual architecture and the mapping of the new applications
onto the existing architecture. This mapping may also include distributed data
external integration points between standard applications and other third party
applications. Once you agree on the business solution for each integration
point gap, this task will result in a complete listing of all new integration
points for which you must design and build interfaces. At this stage there has
been no specification of interfaces; this task is merely a recognition that an
integration point exists and requires attention.
Deliverable
The deliverable for this task is the Integration Fit Analysis document.
BR.050 - Develop
Information Flow Model
This task specifies the future information usage and flow requirements
across business functions, business organizations, applications and data
centers. The information flow model visually depicts information flows in the
business, resulting from and driven by the business events and business
processes that form the business model. This task, together with the Develop
Information Access Model task, creates an information view of the business.
Deliverable
The deliverable for this task is an Information Flow Model for the
business.
BR.060 - Develop
Information Access Model
In this task you analyze and define the Information Access Model, which
describes information sharing and information partitioning requirements across
organizations for the key business objects and business process information.
This will assist in the definition of how information will be controlled from a
security standpoint and what information can be accessed for reporting and
consolidation. This task, together with the previous Develop Information Flow
Model task, creates an information view of the business.
Deliverable
The deliverable for this task is a model for the information access
requirements of the business. It is described in an Information Access Model
document and analyzes the business organization access and security
requirements. It is a major source document for these requirements for any of
the processes in the project.
BR.070 - Conduct
Reporting Fit Analysis
This task requires you to analyze and map every reporting requirement to
both a Future Business Process and standard application report, determine the
final disposition of every report requirement, and reduce the number of
potential reporting customizations through requirement reduction analysis.
Deliverable
The deliverable for this task is an updated Master Report Tracking List.
BR.080 - Test
Business Solutions
In this task you perform an extended test of the proposed business
solutions and validate integrated business processes based on the mapping
decisions. Demonstrate the BRSs and BRMs for each business process, and
demonstrate integration across processes to be feasible.
Deliverable
The deliverable for this task is the Mapping Scenario document.
BR.090 - Confirm
Integrated Business Solutions
In this task you secure approval for proposed business solutions. It is
a prerequisite to estimating and developing detailed designs.
Deliverable
The deliverable for this task is a signed Acceptance Certificate for
each set of related Business Requirements Scenarios.
BR.100 - Create
Process Narratives
In this task you create narrative, job-level descriptions of business process
designs.
Deliverable
The deliverable for this task is a series of Process Narratives.
BR.110 - Define
Application Setups
As you map business requirements to application features, you also begin
to define the configuration you need to support the solution. Your solution may include a number of
user-defined codes, system and application level parameters, and enabled
features. During this task, you capture the setup decisions and implement them
in the appropriate environment.
Deliverable
The deliverable for this task is an Application Setup Document.
BR.120 - Design
Security Profiles
As business requirements are established and mapped to application
features, you also begin to define the user security necessary to support the
solution in a controlled environment. During this task, you gather role and
function information and relate them to application security and
responsibilities.
Deliverable
The deliverable for this task is a Security Profiles document.
Application and Technical Architecture (TA)
TA.010 - Define
Architecture Scope, Objectives, and Approach
In this task, you outline the scope, objectives, and approach you will
use for architecture design of the system you are implementing. This task may
not require the creation of a separate deliverable for all types and sizes of
architectural processes, but you should consult with the project manager to
determine its effect on the project.
Deliverable
The deliverable for this task is Architecture Scope, Objectives, and
Approach. It is a statement of the scope and the objectives of Application and
Technical Architecture, and the approach that the architectural team will take
to perform the work.
TA.020 - Prepare
Architecture Strategy
In this task, you create the strategy for the architecture project. This
integrates the existing company information systems strategies, standards and
policies with the precise method and techniques to be employed in the present
architecture process. Application of the strategy will help to realize all or
part of the information systems vision of the company and should enable the
creation of an architecture in compliance with the high-level scope,
objectives, and approach previously defined.
Deliverable
The deliverable for this task is an Architecture Strategy that describes
the strategy to be used for the work performed in the application and technical
architecture process.
TA.030 -
Establish Architecture Requirements
In this task, you establish the major requirements that will underpin
the information systems architecture design project. The architecture team
needs to bear these requirements in mind throughout the project and ensure that
they create an architecture that is compatible with them.
Deliverable
The deliverable for this task is an Architecture Requirements document.
This contains a list of major requirements that the architecture design should
meet.
TA.040 - Develop
Conceptual Architecture
In this task, you identify possible candidate conceptual architectures
for the new information systems you are implementing, and select the preferred
architecture that best fits the overall needs of the business subject to the
project constraints.
Deliverable
The deliverable for this task is the Conceptual Architecture document.
This describes the conceptual architecture design(s) for the new
system. It may contain several designs,
if there is more than one possible conceptual architecture, but will also
indicate the conceptual architecture model that is preferred. If there is only
one possible conceptual architecture model, it will only describe this one
model.
TA.050 - Conduct
Technical Architecture Baseline
In this task you determine the current application and technical
architecture for existing systems. This includes identifying existing
applications, interfaces, databases, networks, and hardware. The information
gathered in this task can be used both in the subsequent architecture analysis
and design tasks and also in other project processes. You can also use this
task as an opportunity to identify improvements to existing maintenance and
operations procedures, and to identify which system components you can reuse in
the future architecture configuration.
Deliverable
The deliverable for this task is the Technical Architecture Baseline
document, an inventory of the systems, applications, hardware, and networks
that constitute the existing technical infrastructure for the business.
TA.060 - Develop
System Availability Strategy
In this task, you develop a strategy to provide the minimum level of
systems availability that the business demands.
Deliverable
The deliverable for this task is the System Availability Strategy
document, a study of the systems and approaches that will be incorporated into
the technical architecture of the new system to provide the required level of
system availability.
TA.070 - Define
Future Application Deployment
In this task you determine the details of the future deployment of
applications across data centers within the scope of the new architecture.
Deliverable
The deliverable for this task is the Future Application Deployment
document, which is a map for the future deployment of the applications.
TA.080 - Develop
Reporting Strategy
In this task, you analyze the reporting requirements for the new
business and specify at a high level how you will meet these in the new
architecture. This is a systems view of how the reporting requirements will be
satisfied in the new architecture, in contrast to the approach taken in the
Business Requirements Definition and Mapping processes.
Deliverable
The deliverable for this task is a Reporting Strategy document.
TA.090 - Revise
Conceptual Architecture
In this task, you review information that you have gathered and analyzed
since you created the initial draft of the Conceptual Architecture deliverable
and incorporate any relevant new findings and decisions into the deliverable.
If you need to make drastic changes to the original conceptual architecture
model because of subsequent findings and decisions, present it again to project
management to obtain management acceptance. If the changes are relatively minor
in impact, you can present it to select members of the project team to solicit
feedback and acceptance.
After incorporation of changes suggested during the final review
procedure, the revised deliverable becomes the final, agreed upon conceptual
architecture model for the new business system. This deliverable is important
for downstream activities and marks a key milestone in the project. Notify
project management when you have completed the task, and publish the resulting
deliverable.
Deliverable
The deliverable for this task is a revised and accepted Conceptual
Architecture document.
TA.100 - Define
Architecture Subsystems
In this task you identify requirements for components or systems to
support the architecture. Examples of architecture subsystems include
enterprise-wide data distribution (interface) systems, (global) data
registries, data warehouses, and operational reporting databases. You may have
either purchased the subsystems from Oracle or from another vendor, or you may
design and built them in-house as custom development projects, but even systems
that are purchased will often require at least some degree of custom
integration work. Custom development projects will use the requirements from
this task as a starting point in their definition, analysis and design phases.
Deliverable
The deliverable for this task is the Architecture Subsystems document,
which identifies the set of architecture subsystems that need to be
incorporated into the architecture.
TA.110 - Propose
Architecture Subprojects
In this task, you formally propose subsystems of the information systems
architecture that may be suitable for organization and management as
subprojects within the overall architecture design project.
Deliverable
The deliverable for this task is an Architecture Subproject Proposal
document for each architecture subsystem, component and technical area that is
most suitably managed within a separate subproject.
TA.120 - Design
Application Security Architecture
In this task, you design the application and database security
architecture, incorporating the requirements generated by the business mapping
process and the security requirements identified during the design of the
conceptual architecture.
Deliverable
The deliverable for this task is an Application Security Architecture
document. This deliverable will be highly dependent upon the nature and
functionality of the applications being implemented.
TA.130 - Design
Application Functional Architecture
In this task, you design the functional architecture for the
applications. This involves identifying
those key setup parameters in the applications that are relevant to your
particular implementation and establishing the values for those parameters
across all applications. This task is
related to, but distinct from, normal application setups because it deals with
setup parameters that have a profound effect on the way the application
database is laid out and the basic functioning of applications. It may also
affect the technical architecture design because some types of physical
partitioning of data and processing are much easier to implement technically
than others. You may define the critical parameters as part of the Business
Requirements Mapping process, but this task is where you define the
relationships between the key architecture parameters and create the overall
architecture for the different application installation sites or data centers
in your business.
Deliverable
The deliverable for this task is the Application Functional Architecture
document. The deliverable will be very dependent upon the nature and
functionality of the applications being implemented.
TA.140 - Design
Logical Application and Database Architecture
In this task, you design the new logical application and database
architecture for the system. This task refines the conceptual architecture
using information about the future deployment of the applications and the
application functional architecture to create an implementation blueprint that
shows the specific application installations and logical database architecture
for each data center. It does not include the detailed physical layout of
databases nor the hardware and networks that are addressed in other specific
tasks.
Deliverable
The deliverable for this task is the Logical Application and Database
Architecture document. The deliverable is a blueprint for the logical
application installation and database architecture. It specifies all
installations of applications and databases incorporating the analysis and
design from functional mapping, custom application and database extensions,
security, and reporting systems.
TA.150 - Design
Physical Database Architecture
In this task, you design the physical database architecture to support
your logical application and database architecture. You design a physical
layout for the database files and map the logical database objects onto
specific system hardware devices, taking into account projected future data
volumes and the system requirements for performance, cost, and availability.
Deliverable
The deliverable for this task is the Physical Database Architecture
document. It specifies storage structures and parameters necessary for
placement and management of all identified database objects.
TA.160 - Design
Hardware and Network Architecture
In this task, you define the physical hardware and network configuration
to support your final application and database architecture. You map the
physical application and database architecture onto specific computing platforms.
Deliverable
The deliverable for this task is the Hardware and Network Architecture
document. The deliverable describes the deployment of the key hardware and
network components of the new system and their relationship to the application
and database architecture.
TA.170 - Develop
System Capacity Plan
In this task, you plan the capacity for the new information systems at
production cutover and for some prescribed period of future operations,
allowing for business growth and any other known factors that could affect the
system capacity requirements. The general term system capacity refers to the
ability of a system to support numbers of user processing sessions, transaction
rates and data volume without unacceptable detriment to the performance of the
system.
Deliverable
The deliverable for this task is a System Capacity Plan document. It
contains the system capacity requirements for database servers, networks,
client desktop machines, and application client file servers.
TA.180 - Assess
Performance Risks
In this task you identify any performance risks that are apparent based
on the proposed architecture and suggest techniques to mitigate the risks.
Deliverable
The deliverable for this task is the Performance Risk Assessment
document. This is an assessment of the performance risks associated with the
application and technical architecture.
TA.190 - Design
System Management Procedures
In this task, you design the procedures and specify the tools that the
IS operations staff will need to manage the new system. After you design the
procedures in this task, you need to test and refine them later in the project,
prior to incorporating them into the system management guide and training the
system support staff.
Deliverable
The deliverable for this task is the System Management Procedures
document. This is a list of system management procedures and tools that the IS
Operations Staff will use to manage and monitor the new system.
Module Design
and Build (MD)
MD.010 - Prepare
Customization Strategy
In this task, prepare a strategy document that describes how your
project responds to customization requests.
Deliverable
The deliverable for this task is the Customization Strategy document.
MD.020 - Define
and Estimate Custom Extensions
When the solution determined during Business Requirements Mapping
requires custom components, you must estimate the effort required to complete
them. Management must then decide whether the benefits of the customization are
worth the time and expense (now and during upgrades) to build and maintain it.
Deliverable
The deliverable for this task is a Solution Document. A Solution
Document summarizes the business need that Oracle Applications features cannot
meet and proposes a solution that includes a combination of custom components,
manual workarounds, and existing application features. It also includes work
estimates for designing, building, and testing the solution.
MD.030 - Define
Design Standards
In this task, you define the standards that designers will follow when
designing custom extensions. Clear and detailed design standards ensure that
all designs are in a consistent format and include the appropriate level of
detail. Standards enforce a high level of quality.
Deliverable
The deliverable for this task is a Design Standards document.
MD.040 - Define
Build Standards
During this task you define the standards that programmers follow to
build customizations to the applications.
Deliverable
The Build Standards document is the deliverable for this task.
MD.050 - Design
Database Extensions
When customizations require new tables, indexes, views, and sequences,
you must design the new database objects and illustrate how the extensions
integrate with the existing applications database schema.
Deliverable
The deliverable for this task is the Database Extensions Design. It
includes an Entity Relationship (ER) diagram, definitions of new database
objects, and a description of how the new modules will access these objects.
MD.060 - Produce
Module Functional Design
In this task you document the functional features, use, and behavior of
required customizations. The Functional Design confirms that you understand the
user requirements and allows users to evaluate and approve the resulting
features that the new modules will provide.
Deliverable
The deliverable for this task is a Module Functional Design document
that describes each customization in business and user terms. Users and
business analysts are the audience for this deliverable. Therefore, it must
communicate all the features provided by the customization in non-technical
terms.
MD.070 - Produce
Module Technical Design
During this task you document the technical specifications for custom
and modified forms, reports, database triggers, zooms, and other custom
components.
Deliverable
The deliverable for this task is a Module Technical Design document for
each customization that includes all the technical details for each module. The
audience for this document is a programmer. It must provide all the information
that a programmer needs to code the custom components.
MD.080 - Review
Detailed Designs
This task is a design review meeting between business analysts, key
users, module designers, and programmers. The goal is to secure final sign off
of the complete designs from all interested parties. Everyone must agree that
the designs represent solutions that will adequately satisfy the business
requirements and can be built with the available technology in the allocated
time frame.
Deliverable
The deliverable for this task is Approved Designs. Confirmation of the
approvals is an Acceptance Certificate (PJM.CR.080) for each design. The Acceptance Certificate should be signed
by at least the following individuals:
·
business analyst who identified the requirements
user (a representative of the people who will be using the new functionality)
·
programmer who will code the modules (or an
alternate representative who can confirm that the design contains adequate
technical detail)
MD.090 - Prepare
Development Environment
This task establishes a hardware and software environment supporting
custom development.
Deliverable
The deliverable for this task is a Development Environment with
supporting documentation. Document the new environment by creating an
Installation Plan and Record (PJM.RM.050) document.
MD.100 - Implement
Database Extensions
In this task you create new tables, indexes, views, grants, and synonyms
to support custom module development.
Deliverable
The deliverable for this task is a set of Custom Database Objects in the
development environment and the supporting Data Definition Language (DDL)
scripts to create the database objects in the production environment.
MD.110 - Create
Custom Modules
During this task you produce the modules to support custom extensions to
the Applications. You also perform the first round of testing as part of this
task.
Deliverable
The deliverable for this task is a completed Module Source Code with
corresponding executables.
MD.120 - Create
Installation Routines
In this task you develop automated functions and detailed instructions
to install custom extensions in a target environment.
Deliverable
The deliverable for this task is a set of Installation Routines and
documented instructions to install all of the custom modules in the production
environment. Not all customizations can be installed with an automated script,
so the instructions may include manual steps as well.
Data Conversion (CV)
CV.010 - Define Conversion Scope, Objectives, and
Approach
During this task, you define
the conversion project scope, objectives, and high-level approach for
performing the conversion. Part of defining the scope is to document your
conversion requirements at the application and business object level.
Deliverable
The deliverable for this task
is the Conversion Scope, Objectives, and Approach document It is the basis for
all other conversion project deliverables and should be signed by a designated
approver. Use this deliverable to record your conversion requirements and to
track any scope changes that may impact the conversion project.
CV.020 - Prepare Conversion Strategy
During this task, you define
the strategy for converting information from the legacy systems to the new
application environment. The Data Conversion Strategy provides a roadmap for
performing the conversion of data from the legacy system(s) to the new Oracle
system. This deliverable also covers the task steps and resources needed to
fulfill this strategy.
Deliverable
The deliverable for this task
is the Data Conversion Strategy. Use it to record the strategy for meeting the
conversion requirements defined in the Conversion Scope, Objectives, and
Approach (CV.010). The strategy includes a discussion of a recommended
conversion method, tools, tasks, and testing procedures.
CV.030 - Prepare Conversion Standards
During this task, you create
the Conversion Standards that the conversion team will follow when performing
conversion tasks. This task documents the file structure and naming conventions
for the legacy and target systems, as well as for any automated tools you are
using to facilitate the conversion process.
Deliverable
The deliverable for this task
is the Conversion Standards. It documents the legacy system, target system, and
automated tool conversion standards.
CV.040 - Prepare Conversion Environment
During this task, you create
the Conversion Environment, including the hardware and software required to
support the design and build activities of the conversion process.
Deliverable
The deliverable for this task
is the Conversion Environment. It is a working computer system with all
databases, applications, and development tools required to develop and test
conversion programs.
CV.050 - Perform Conversion Data Mapping
During this task, you map the
data elements from the legacy system to the target Oracle Applications. In addition
to identifying the data sources and target tables and columns, also identify
data defaults, validation, processing, translation, filter, and foreign key
rules. The conversion mapping and the extract file layout are prerequisites for
designing the conversion programs.
Deliverable
The deliverable for this task
is the Conversion Data Mapping. The deliverable records the detailed data
mapping and extract file layout for each legacy data element you plan to
convert to Oracle. Prepare one document for each business object you are
converting.
CV.060 - Design Manual Conversion Strategy
During this task, you define
the plan to convert the business objects that require manual conversion. This
strategy provides a plan for manually converting data to successfully meet
conversion project milestones.
Deliverable
The deliverable for this task
is the Manual Conversion Strategy. The primary purpose of this deliverable is
to define how to manually convert a business object. In addition, you will
discuss the impact if you do not successfully convert business objects in the
required timeframe. You should produce one deliverable for each manually
converted business object. Use this deliverable as a roadmap for those who will
be performing the manual conversion.
CV.070 - Design Conversion Programs
During this task, you design
and document the conversion programs.
The Conversion Program Design document provides the programmer with the
necessary information for writing an accurate conversion program.
Deliverable
The deliverable for this task
is the Conversion Program Design. It defines the key assumptions, rules, and
logic needed to create the conversion modules.
CV.080 - Prepare Conversion Test Plans
During this task, outline the
testing plans for the unit, business object, and validation testing for
conversion. The unit tests confirm that each module successfully completes the
task it is defined to perform. For example, a unit test should verify that the
download program has extracted the expected number of records from the legacy
system. The business object test verifies that the quality of the data
converted to the Oracle system is accurate and functions properly in the
individual Oracle Application to which it has been converted. Validation
testing verifies that the converted legacy data performs accurately within the
entire suite of Oracle Applications.
Deliverable
The deliverable for this task
is the Conversion Test Plans. This document provides a plan for conversion
unit, business object, and validation tests. Subsequent data conversion tasks
perform each of these three levels of testing and then record the results as
described in the deliverable guidelines.
CV.090 - Develop Conversion Programs
During this task, you create
the conversion programs that perform the following functions:
·
Download the data from the
legacy system and create an ASCII flat file that can be uploaded to Oracle
tables.
·
Create interface tables that
store the legacy data before the data is validated and inserted into the
production tables of the Oracle Application.
·
Upload legacy ASCII flat file
data to the interface tables.
·
Perform any data-required
translation, transformation, or manipulation before moving the data to the
production tables. Interface and
validate, then insert or update the data into the Oracle production tables.
Deliverable
The deliverable for this task
is the Conversion Programs. This is the actual program code for the programs
defined in the Conversion Program Design (CV.070). Record the program name,
description, purpose, location, and programmer name of each program in a
Conversion Program Log.
CV.100 - Perform Conversion Unit Test
During this task, you
actually test the conversion programs to ensure that all programs work without
errors and according to the conversion testing specifications pre-defined in
the conversion unit testing components of the Conversion Test Plans (CV.080).
Deliverable
The deliverable for this task
is the Unit Tested Conversion Programs.
To support this deliverable, provide a checklist to record that the test
was completed, the date that each conversion program was tested, the programmer
who tested each program, and the sequence in which the modules were tested.
CV.110 - Perform Conversion Business Object Tests
During this task, you test
the complete conversion of each business object by executing all conversion
modules for the business object in an end-to-end fashion and verifying that the
resulting data is correct.
Deliverable
The deliverable for this task
is the Business Object Tested Conversion Programs. To support this deliverable,
record that the test has been completed, the business object test number, the
associated Oracle target table, the test completion date, and the tester. As
with the test procedures, prepare one deliverable for each business object
being converted.
CV.120 - Perform Conversion Validation Test
During this task, you
validate that the target applications function correctly with the converted
business objects.
Deliverable
The deliverable for this task
is the Validation Tested Conversion Programs. To support this deliverable,
record the test’s completion, the Oracle target applications, the test
completion date, and the tester. As with the Conversion Test Plans, prepare one
deliverable for each business object being converted.
CV.130 - Install Conversion Software
During this task, you perform
and document the installation of the conversion programs in the production
environment. This task presumes that the conversion programs have been tested.
If you are using an automated conversion tool, this task requires that you
install the software, tested conversion templates, and conversion maps needed
for Convert and Verify Data (CV.140).
Deliverable
The deliverable for this task
is the Installed Conversion Software. This deliverable records the following
information about the installed conversion software:
·
description of the production
environment
·
directory structure for the
production environment
·
location of each conversion
program in the production environment file structure
·
location of conversion tools
in the production environment
CV.140 - Convert and Verify Data
During this task, you convert
and migrate the production data from the old system to the new Oracle
production environment. Completion of this task provides data that is ready for
production use.
Deliverable
The deliverable for this task
is Converted and Verified Data. It consists of the converted production data.
This deliverable, along with the production environment, includes everything
required to use the applications in production. This includes properly
installed and configured hardware, system software, application software,
documentation, and converted production data.
Documentation (DO)
DO.010 - Prepare Glossary
This task documents the
definitions of the project terms that may be unfamiliar or confusing. Including
these in the glossary removes questions about their meaning.
Deliverable
The deliverable for this task
is the Glossary. It contains business terms, acronyms, synonyms, and entities
that will be used in the application but may be unfamiliar or confusing. The
Glossary is a living document and will be continuously revised and supplemented
throughout the project life cycle.
DO.020 - Specify Documentation Requirements
In this task you outline the
overall requirements for creating documentation and specify the deliverables to
be produced.
Deliverable
The deliverable for this task
is the Documentation Requirements. It specifies the documentation deliverables
that will be produced, how each is to be used, and the format to be used when
document ownership is transferred to the users. It also includes the plan for
producing the documents and the required staffing.
DO.030 - Determine Documentation Standards and
Procedures
The purpose of this task is
to specify the standards for all documentation deliverables. This task
determines the look and feel of the project documentation. In this task, you
also specify the procedures that the team uses to develop documentation.
Deliverable
The deliverable for this task
is the Documentation Standards and Procedures. It specifies the textual style,
editing conventions and development procedures to be used in creating the
project’s documentation.
DO.040 - Prepare Documentation Environment
In this task you prepare a
hardware and software environment that supports documentation development. You
must procure, install, and test the environment. At the end of this task, you
are ready to begin the job of developing documentation.
Deliverable
The deliverable for this task
is the Documentation Environment. It includes all hardware, software, and
utilities needed to support documentation development.
DO.050 - Produce Documentation Prototypes and
Templates
In this task you build and
review a single prototype for each type of documentation deliverable. The
result should be agreement on the look and feel of each documentation
deliverable, as well as a clear expectation of what will be delivered. You also
create templates for later use.
Deliverable
The deliverable for this task
is the Documentation Prototypes and Templates. For each type of documentation
deliverable, a prototype document and a working, tested template will be
produced.
DO.060 - Produce Initial User Reference Manual
In this task you generate the
first draft of the User Reference Manual which supplements the standard
application user reference. Material for the Initial User Reference Manual
comes from the Module Functional Design (MD.060) which defines the custom
extensions.
Collect these documents as
input and combine them into a consolidated reference.
Deliverable
The deliverable for this task
is the Initial User Reference Manual. It contains a draft description of the
detailed functionality of each custom extension. It is a reference for more
experienced users of the application system. Later, it will be updated to
incorporate any functional modifications or details that may have been added.
DO.070 - Produce Initial User Guide
This task requires you to
produce the Initial User Guide.
Deliverable
The deliverable for this task
is the Initial User Guide. This guide describes how the application system
interrelates with manual procedures in order to adequately respond to business
events. It is an instruction manual for the business and is the basis for
training new application users.
DO.080 - Produce Initial Technical Reference
Manual
The information for the
custom modules and extensions are contained in the Technical Reference Manual.
This information is intended to supplement the standard Oracle Technical
Reference Manual and is usually consistent in format and content to Oracle
Documentation Standards.
Deliverable
The deliverable for this task
is the Initial Technical Reference Manual.
It is a precursor to the Technical Reference Manual that explains the
design and structure of the custom modules and extensions to those who maintain
them after the transition to production.
DO.090 - Produce Initial System Management Guide
In this task you create an
initial version of the System Management Guide.
Deliverable
The deliverable for this task
is the Initial System Management Guide.
It is the first draft of the System Management Guide. Although called an
initial deliverable, it should be as final as possible, given the current
information. The later update should only incorporate any changes to processes
and module functionality.
DO.100 - Complete User Reference Manual
In this task you revise the
Initial User Reference Manual and create the final version. Changes have
probably been introduced into the custom modules and extensions as an outcome
of testing and review. These must be reflected as changes or additions in the
final User Reference Manual. Also, the completed modules can be used to extract
information (for example, screen layouts) that were not previously available.
This task should be executed in parallel with module and module integration
testing.
Deliverable
The deliverable for this task
is the User Reference Manual. It contains the final description of the detailed
functionality of each custom module and extension. It is a reference for more
experienced users of the application system. Preparing this deliverable
includes generating the format to be used in transferring document ownership to
the user. Once the project team has
completed this task, the User Reference Manual becomes a highly-controlled
deliverable.
DO.110 - Complete User Guide
In this task you revise the
Initial User Guide and create the final version.
This task should be performed
in parallel with the business system test.
Deliverable
The deliverable for this task
is the User Guide. It contains the final set of procedures for using the
application system in response to business events and is a guide for new users.
It is a critical document for the business. Once the project team has completed
this task, the User Guide becomes a highly-controlled deliverable.
DO.120 - Complete Technical Reference Manual
In this task you update the
content of the Initial Technical Reference Manual. The size of this task
depends on the extent of the technical changes that were made during testing.
Deliverable
The deliverable for this task
is the Technical Reference Manual. It explains the components and the design of
the customizations and extensions. It is a reference document for application
maintenance personnel.
DO.130 - Complete System Management Guide
In this task you revise the
Initial System Management Guide and create the final version. Perform this task
in parallel with the execution of the business system test.
Deliverable
The deliverable for this task
is the System Management Guide. It contains the final set of procedures for
operating the application system. It is
a guide for system administrators and the internal support staff and becomes a
critical document for the business. Once the project team has completed this
task, the System Management Guide becomes a highly-controlled deliverable.
DO.140 - Provide Online Help Text
In this optional task you use
standard Application Object Library forms to create Online Help Text for
end-users using the User Reference Manual and User Guide as input.
Deliverable
The deliverable for this task
is the Online Help Text.
Business System Testing (TE)
TE.010 - Develop Testing Strategy
The goal of the test strategy
is to develop the high-level direction for testing the applications.
Deliverable
The deliverable for this task
is the Testing Strategy. Based on the characteristics of the system to be
built, specific testing activities may be more or less important to a
successful implementation. Specific considerations include the number of custom
modules, availability and reliability of converted data, system performance,
number of system interfaces, scope of testing, testing standards, types of
testing, and the significance, or critical nature, of the system to the
business.
TE.020 - Develop Unit Test Scripts
In this task you develop the
scripts to test individual custom modules.
Design your tests to validate that module inputs, outputs, and
processing logic function as designed with no errors.
Deliverable
The deliverable for this task
is the Unit Test Scripts. These take the form of standard checklists and
step-by-step instructions to test specific functionality.
TE.030 - Develop Link Test Scripts
In this task you develop
scripts to test custom modules as part of a business flow. This will reveal any
integration problems with other modules that provide or use the data
manipulated by the target modules.
Deliverable
The deliverable for this task
is the Link Test Scripts. The name comes from the fact that they test the
connections, or links, between modules.
TE.040 - Develop System Test Scripts
In this task you develop the
scripts to test the system’s support of business processes.
Deliverable
The deliverable for this task
is System Test Scripts.
TE.050 - Develop Systems Integration Test Scripts
In this task you develop the
scripts that validate the integration between your target application system
and other systems.
Deliverable
The deliverable for this task
is the Systems Integration Test Scripts.
TE.060 - Prepare Testing Environments
In this task you install and
configure one or more environments to support all testing activities.
Deliverable
The deliverable for this task
is the configured Testing Environments.
Your Testing Strategy (TE.010) determines the number and timing of the
environments.
TE.070 - Perform Unit Test
In this task, you test
program modules on an individual basis to ensure that the inputs, outputs, and
processing logic of each module functions as designed with no errors. The goal
is to find errors in the smallest unit of software before you logically link it
into larger units. If successful, subsequent link testing will only reveal
errors related to the integration between modules.
Deliverable
The deliverable for this task
is the Unit Tested Modules. The actual results you record in the Unit Test
Scripts (TE.020) serve as confirmation that the custom modules execute without
errors.
TE.080 - Perform Link Tests
During this task, you test
custom modules as part of a business flow.
This will reveal any integration problems with other modules that
provide or use the data manipulated by the target modules. The name comes from
the fact that you are testing the connections, or links, between modules. Link
testing should reveal all potential problems with the custom code.
The scope of each link test
typically includes the set of modules that support or are affected by a single
customization. A customization is defined for each gap identified during
requirements mapping and is described by a functional design and corresponding
technical design document.
Deliverable
The deliverable for this task
is Link Tested Modules. Once modules pass link testing, they are ready for the
system test. Document your results in the Expected Results column provided in
the Link Test Specification component of the Link Test Script (TE.030).
TE.090 - Perform Installation Test
In this task, you install
custom modules in the system test environment to test the installation routines
and refine them for the eventual production environment. This task serves as a
dry run of the installation steps in preparation for configuring the production
system. This task is not required if you
have not developed custom extensions. It
also does not cover installation of the Oracle database, tools, and
Applications. These steps took place during Prepare Testing Environments
(TE.060).
Deliverable
The deliverable for this task
is Tested Installation Routines. Another important result of this test is that
you install and configure custom modules in the system test environment.
TE.100 - Prepare Key Users for Testing
In this task you will provide
basic training to key users participating in the Business System Test.
Deliverable
The deliverable for this task
is Prepared Users, trained in specific standard and custom applications functionality.
TE.110 - Perform System Testing
In this task you will test
the integration of all business system flows within the target application
system, including all standard and custom processes and reports. This task is
equivalent to a full conference room pilot (CRP), where the environment
simulates the future production environment.
Deliverable
The deliverable for this task
is the System Tested Applications. The summarized results of the System Test
should appear in a System Test Results document for review by management.
TE.120 - Perform Regression Testing
In this task you will re-test
modules in order to validate that prior module defects have been corrected.
Deliverable
The deliverable for this task
is the Regression Tested Custom Modules.
TE.130 - Perform Systems Integration Testing
In this task you will test
the system’s integration with other application systems in a production-like
environment.
Deliverable
The deliverable for this task
is the Integration Tested System.
TE.140 - Support Acceptance Test
In this task you support the
acceptance test performed by users of the production system. The scope of
acceptance testing and specific acceptance criteria is defined in the Quality
Plan. This task also involves scheduling the acceptance test team, support
staff, and user facilities.
You may omit this task if
users are participating substantially in the System Test and the company
chooses to evaluate user acceptance upon successful completion of that task.
Deliverable
The deliverable for this task
is the Acceptance Test Results. It includes both detailed and summary results
from the acceptance test.
Performance Testing (PT)
PT.010 - Define Performance Testing Scope, Objectives, and Approach
In this task, you outline the
scope, objectives, and approach you will use for the performance testing of the
system you are implementing. This task may not require the creation of a
separate deliverable for all types and sizes of Performance Testing, but you
should consult with the project manager to determine its effect on the project.
Deliverable
The deliverable for this task
is the Performance Testing Scope, Objectives, and Approach document. It is a
statement of the scope and objectives of Performance Testing, and the approach
that the performance testing team will take to perform the work.
PT.020 - Prepare Performance Testing Strategy
In this task, you outline the
strategy that you will use to conduct the performance test to satisfy the
high-level scope, objectives, and approach you have previously defined.
Deliverable
The deliverable for this task
is the Performance Testing Strategy. It is a strategy for the work to be
performed in Performance Testing.
PT.030 - Identify Performance Test Scenarios
In this task, you define the
performance test scenarios that you wish to include in Performance Testing.
These are either scenarios that business management has dictated for inclusion
or that you identify from an analysis of the performance quality objectives for
the project, coupled with detailed input of business solutions and processing
business volumes. Performance test scenarios are point-in-time snapshots of the
processing that occurs in a real system.
Deliverable
The deliverable for this task
is the Performance Test Scenarios document. It describes the processing
situations (point-in-time processing snapshots) in the future production system
where there will be critical performance requirements. These performance test
scenarios form the basis of models of the system transactions in future tasks.
PT.040 - Identify Performance Test Transaction
Models
In this task, you define in
more detail the sets of transactions that will execute during the performance
test, and the detailed transaction rate metrics for each transaction. Each
performance test scenario will have a different collection of online and batch
processing that comprises the test transaction model of the scenario and the
transactions and rate metrics need to be identified for each. A transaction
model for a scenario is the precise mix of transactions included in the
performance test for that particular scenario. The separate test transaction
models will translate into the execution of the test scenario under differing
sets of test parameters.
The other part of this task
is to identify the specific application configuration you will need to support
the test transaction models. This is less of concern if the performance testing
process is being used for a system that is already in production operations,
but if the applications are to be reconfigured in some way, or the application
configuration of the system has not been fully defined, you will need define
how you will set up the applications to support the test models.
Deliverable
The deliverable for this task
is the Performance Test Transaction Models document. This defines the detailed
mixes of transactions in the performance tests.
PT.050 - Create Performance Test Scripts
In this task, you define the
detailed test scripts for entering the data to perform online and batch
transactions, inquiries, and reports that will model the processing occurring
during a test scenario. The test scripts define the exact manner in which each
scenario transaction model will execute during the performance test. The result
of this break down into individual transaction steps is a deliverable that can
be used by the developer of the test transaction programs, or by the users
involved in the performance test.
The other component of the
task is to define the detailed transaction response measurements you will make
as part of each scripted transaction flow. These measurements are part of the
script and will either be collected by the automated testing tool if you are
using one, or may require some recording of response by the user executing the
performance test script.
Deliverable
The deliverable for this task
is the Performance Test Scripts document.
It is a set of scripts for the transactions that will execute during the
performance tests and the lists the specific measurements made within each
script transaction flow.
PT.060 - Design Performance Test Transaction
Programs
In this task, you design the
test transaction programs that will execute the transactions, reports, and
inquiries against the performance test database. If you are using an automated
load testing tool, the programs may simulate multiple online users working
concurrently within the business system. You can bypass this task if you do not
need to build any special programs to execute transactions within the
performance test, additional to the modules that will constitute the production
system. This would be the case if you are conducting a manual system
performance test that will use standard batch scheduling and manual online
transaction entry, or if you are just testing a batch processing scenario.
Deliverable
The deliverable for this task
is the Test Transaction Program Designs document. It is a set of designs for
the special test programs needed to execute transactions during the performance
tests.
PT.070 - Develop Performance Test Transaction
Programs
In this task, you create the
special test transaction programs that will execute the transactions, reports,
and inquiries against the performance test database.
Deliverable
The deliverable for this task
are the Test Transaction Programs. At the completion of this task, these
programs will be built and tested.
PT.080 - Design Performance Test Data
This task initiates the
detailed design work on the database for performance testing. Typically, you
will not have a fully populated database available for performance testing. You
will probably need to define the data for the database and determine how to
populate it. You specify the data and volumes for the performance test
database, the source of the data, and the proposed mechanism for getting the
data into the test database.
Deliverable
The deliverable for this task
is the Performance Test Data Design document. It is a design for the data in
the performance test database that will support the transaction models of the
test.
PT.090 - Design Test Database Load Programs
In this task, you design the
programs that will load test data into the performance test database. You can
bypass this task if you do not need to build any extra test database load
programs specifically to load data into the performance test database. This
would be the case if, for example, you are conducting a performance test
against a copy of an existing production database that has the approximate
volumes of data you need, or, if you can use existing data conversion programs
to load all transaction and setup data.
Deliverable
The deliverable for this task
is the Test Database Load Program Designs document. It is a set of designs for
special programs needed to load data into the performance test database.
PT.100 - Develop Test Database Load Programs
In this task, you develop and
test the programs that you will use to populate the performance test database
with data.
Deliverable
The deliverable for this task
is the Test Database Load Programs. At the completion of the task, these
programs will be built and tested.
PT.110 - Construct Performance Test Database
In this task, you populate
the Performance Test Database up to the full desired volume in preparation for
subsequent migration of the database to the testing environment.
Deliverable
The deliverable for this task
is the fully populated Performance Test Database.
PT.120 - Prepare Performance Test Environment
In this task, you prepare and
document the separate environment where Performance Testing will take place.
This involves configuring the hardware and networks, installing the Performance
Test Database, verifying that the Test Transaction Programs execute correctly
against the database, initial tuning of the environment, installing any
monitoring tools needed, and documenting the test execution procedures. After this
task is complete, the Performance Test Environment should be ready to support
execution of performance test cycles in which measurements are made.
Deliverable
The deliverable for this task
is the fully configured and documented Performance Test Environment. The
deliverable consists of a the physical environment plus a document of the same
name which describes the initial parameter settings for the environment and the
test execution procedures.
PT.130 - Execute Performance Test
This task is the culmination
of the development and environment preparation effort. You execute the Test
Transaction Programs against the test database and measure various performance
metrics for individual transactions and system components. This task is very
interactive and may require multiple test cycles for each transaction model and
hardware configuration that you intend to test. You may decide that you need to
change certain system parameters for tuning purposes or because you wish to
study the effects of system parameters on the test results. In complex
automated tool tests, you may find that the test execution model needs rework.
Execute the test programs for
each transaction model within each test scenario and take the prescribed
measurements of system performance.
Repeat for each hardware configuration. This task yields the test
results that you document in the final Performance Test Report.
Deliverable
The deliverables for this
task are Performance Test Results. These are documented in a Performance Test
Log, which records the test date and time, specific test or configuration
parameters, as well as the individual measurements made.
PT.140 - Create Performance Test Report
In this task, you document
the results and the description of Performance Testing in a format suitable for
presentation to project managers, executive sponsors, and the wider project
team.
Deliverable
The deliverable for this task
is a Performance Test Report document. It details the approach used in the
project, tests performed, results, conclusions, and recommendations.
Training (TR)
TR.010 - Prepare Training Strategy
This task assesses the
education and training needs of the project team and user community and plans
the delivery of these classes based on common areas of responsibility,
interests, and skills.
Deliverable
The deliverable for this task
is the Education and Training Plan.
TR.020 - Prepare Project Team Training Environment
During this task, you either
install a new application environment or prepare an existing application
environment for Project Team Training.
Deliverable
The deliverable for this task
is the Project Team Training Environment.
TR.030 - Conduct General Education Classes
This task educates the team
on fundamental business concepts. It exposes the project team to new business approaches
practiced in industry and also provides each team member with a common
understanding of business issues. This task is optional, but is beneficial when
you desire business process changes or improvements.
Deliverable
The deliverable for this task
is the Trained Project Team.
TR.040 - Conduct High-Level Overview of
Application Features
This task provides overviews
that explain key application concepts and provide a general understanding of
selected features.
Deliverable
The deliverable for this task
is a Trained Project Team.
TR.050 - Prepare Project Team Training
In this task, you plan the
resources for project team training.
Deliverable
The deliverable for this task
is a completed Training Preparation Checklist.
TR.060 - Train Project Team
This task provides technical
and functional application training to the immediate project team members. It
includes specific training segments for defining and using the applications as
well as maintaining the system.
Deliverable
The deliverable for this task
is the Trained Project Team.
TR.070 - Develop User Training Materials
This task produces the
end-user training materials.
Deliverable
The deliverable for this task
is the completed User Training Materials.
TR.080 - Prepare User Training Environment
During this task, you either
install a new application or prepare an existing application environment for
end-user training. If you install a new application, you must go through the
appropriate pre- and post-installation steps. If you are converting an existing
environment for end-user training, you only need to adjust the application
setup and add training-specific data.
Deliverable
The deliverable for this task
is the User Training Environment.
TR.090 - Train Users
During this task, the project
team trains users to use the new system.
Deliverable
The deliverable for this task
is the Trained Users, who understand the features of the new system and how to
use those features on the job.
Production
Migration (PM)
PM.010 - Prepare Transition Strategy
This task outlines the
business transition approach for migrating the people, company, and system to
production status.
Deliverable
The Transition Strategy
document is the deliverable for this task.
PM.020 - Design Production Support Infrastructure
This task identifies the
operational infrastructure for managing and maintaining the application
environment, database, and network communications in production. Implement the
support infrastructure in parallel with configuring the final production
environment during production cutover.
Deliverable
The Production Support
Infrastructure document is the deliverable for this task.
PM.030 - Develop Detailed Transition and
Contingency Plan
This task develops the
detailed transition plan for moving onto the production system. It also
includes an implementation contingency plan if problems arise during
transition. Do not confuse implementation contingency with system contingency
failure.
Deliverable
The Detailed Transition and
Contingency Plan for the implementation with contingency alternatives is the
deliverable for this task.
PM.040 - Prepare Production Environment
In this task you will set up,
configure, and install the database and application software for the Production
environment. This task creates a production environment that is available to
all potential system users but cannot actually be used until production
readiness is verified.
Deliverable
The deliverable for this task
is a configured Production Environment without application setup data.
PM.050 - Set Up Applications
In this task you implement
the required setups in all the applications as part of your configuration. The
Application Setup documents prepared during the Business Requirements Mapping
process defines the correct setups for each application.
Deliverable
The deliverable for this task
is Configured Applications with all required company-specific setups and seed
data. The applications are ready for accepting converted live data.
PM.060 - Implement Support Infrastructure
In this task you will
activate the support personnel and procedures for the new business system. You
also review requirements for support-related services from any software
suppliers and contractors.
Deliverable
The deliverable for this task
is a tested support system with Documented Support Procedures for getting help,
logging problems, and resolving issues.
PM.070 - Verify Production Readiness
With this task you formally
verify that the company’s systems and people are prepared for production using
a detailed verification checklist. Although the predecessor to this task is
acceptance criteria, the true system certification occurs after Perform
Business System Test. Success with this
task means that project leadership can request approval for transition
activities. This is the final approval step before the cutover to the new
production system.
Deliverable
The deliverable for this task
is a Production-Ready System, where the system, management, and users are
prepared for production cutover. Use the
detailed transition plan task lists to evaluate production readiness with
regard to key activities that must be complete prior to cutover. You can also
use an Acceptance Certificate if the team wishes to formalize signoff
confirming that the company is ready for production.
PM.080 - Commence Production
This task signifies that
company-wide use of all aspects of the production system is in place. You must
anticipate issues and quickly remedy them. Priorities may shift during a
production state and therefore you must set expectations with users on what
types of problems to resolve first.
Deliverable
The deliverable for this task
is a fully operational Production System.
PM.090 - Audit Production System
This task provides an
assessment of how well the production system meets the business objectives set
at the beginning of the project. It lets you measure the new business, using
revised key performance indicators.
Deliverable
The Post-Implementation
Production System is the deliverable for this task.
PM.100 - Measure System Performance
This task measures the
performance of the system in the production environment. This may include
transactions processing performance, system response time, and system usage.
The purpose of this task is twofold. Firstly, by measuring the actual
production system performance, closure can be achieved on the performance
quality programs and methods employed during the implementation of the system.
It is possible to assess the effectiveness of the programs and establish where
continuing performance problems may have originated. Secondly, there may be continuing
opportunities to refine and tune the performance of the system, which can only
be identified by system metrics gathering.
Deliverable
The System Performance
Assessment is the deliverable for this task.
PM.110 - Maintain System
This task is an ongoing
system maintenance or management task. The system management procedures are put
into practice and executed by the IS Operations Staff.
Deliverable
A Maintained Production
Environment with updated documentation is the deliverable for this task.
PM.120 - Refine Production System
This task solicits end-user
feedback and acts upon any requests relative to the implementation, production
system, or support.
Deliverable
The Refined Production
Environment is the deliverable for this task.
PM.130 - Decommission Former System
This task involves the full
analysis and execution of decommissioning former business systems.
Decommissioning former systems can begin after the team has decided that the
new production environment is stable and that the Detailed Transition and
Contingency Plan is no longer needed.
Deliverable
The Decommissioned Former
System is the deliverable for this task.
PM.140 - Propose Future Business Direction
This task identifies
opportunities and challenges for the company and proposes a future business
direction for the new implementation.
Deliverable
The Business Direction
Recommendations document is the deliverable for this task.
PM.150 - Propose Future Technical Direction
In this task you will
identify innovations and advancements in software and technology that can
enhance the efficiency, functionality, distributed nature, performance, and
cost of maintaining the new production environment.
Deliverable
The Technical Direction
Recommendations document is the deliverable for this task.
No comments:
Post a Comment