Get documents about "Presentation Business Data Layer
Description
Presentation Business Data Layer document sample
Document Sample
Incremental Development Work Breakdown Structure Dictionary
# WBS Dictionary Del Name & # Dur. Est. Critically Skill
Depend
1.0 Phase Initiate – Obtaining agreement on the business N/A
requirement and charting the project.
1.1 Activity Develop the Business Requirement – Establish a common N/A
understanding of the base requirements that are to be addressed by
the project.
1.1.1 Task Create the Product Description – define, scope, and give context to the product & Product Description PM
services that the project will be chartered to develop, deliver, and support.
1.1.2 Task Prepare and Review the Product Description – depending on audience Project Proposal, Document Approval
preference, summarizes the content of the product description into an executive
summary and deliver it or prepare and conduct a review of the product description.
Obtain approval to charter a project that will assign initial planning resources to
develop the project plan.
1.2 Activity Charter the Project – Obtain the commitment and agreement N/A
between the sponsor and project team indicating how the project will
be conducted and who needs to be involved.
1.2.1 Task Create the Project Charter – define the mission, authority, and level of project Project Charter PM
planning and controls necessary for the project, and indicate the personnel or
groups expected to be involved in the project. Assign the project manager,
sponsor, and any required resources to complete the overall project planning.
Project Proposal Approved by
1.2.1.1 Milestone N/A PM
2. Phase Plan – Creation and approval of the core work plan and N/A
facilitating plans which will guide project execution and
control.
2.1 Activity Develop the Core Work Plan (CWP) – The development of the N/A
work scope, supporting schedule, budget, and project organization
that focuses and guides the project work effort.
2.1.1 Task Develop the Scope Statement – Develop the scope statement with the customer CWP – Scope Statement PM
that indicates an agreement on work scope, project objectives and measurements,
hi-level deliverables, assumptions, and completion criteria.
89b2d78a-e6c4-4d91-aa00-c0b81894b597.xls 1
Incremental Development Work Breakdown Structure Dictionary
# WBS Dictionary Del Name & # Dur. Est. Critically Skill
Depend
2.1.2 Task Develop the WBS – Define the work Activities, sequencing, effort estimates, and CWP – WBS PM
deliverables. Indicate the type of resource (people, equipment, materials, facilities)
needed to complete the work activities. Review and obtain agreement of the WBS
work activities with the customer, sponsor, and management of other groups
expected to support the project.
2.1.3 Task Develop the Project Schedule – Develop approximate cost estimates of all the CWP – Schedule and Budget Projection PM
types of resources. Build a project schedule from the WBS and cost estimates.
Produce a time-phased cost budget from the schedule.
2.1.4 Task (Note) On large projects a feasibility study maybe a major phase prior to detailed CWP – Feasibility and Recommendations
planning. On very small or maintenance project the feasibility may be limited to
cost/benefit assumption and recommendations. This project is considered a small
project.
Determine the Project Feasibility and Recommendation – Approximate and
define the life span of the product or service being delivered. Approximate and
2.1.5 Task define a dollar value for soft and hard benefits and any cost framework to describe
Organize Project & Staff Acquisition – provide an overall reduction or avoidance CWP – Organization PM
the roles, responsibilities and membership of the Project. Obtain the staff needed
for the core team and staff need from other groups in the organization that will be
cross-committed to the project. Obtain from management commitment of all non-
contracted personnel. (Note– any contracted staff is acquired via the contract
activity, however none are planned for this project.)
2.2 Activity Develop the Facilitating Plans for Controls (FPC) – The plans for N/A
ongoing work required to ensure that the project can anticipate
possible problems, solve, and make coordinated work plan
adjustments.
2.2.1 Task Risk Management – Determine which risks are likely to affect the project, FPC – Risk Id and Mgmt
evaluate potential risk outcomes and indicators, define plan to respond to key risks
indicators.
2.2.2 Task Change Management – Outline a simple change management process to FPC – Chg Mgmt
coordinate approved changes in the project plan.
2.2.3 Task Project Standards, Approval, And Document Controls – Define and setup the FPC – Stds, Apvls, Cntls
documentation standards, document storage locations, project notebook, document
approval and promotion process, and securities.
89b2d78a-e6c4-4d91-aa00-c0b81894b597.xls 2
Incremental Development Work Breakdown Structure Dictionary
# WBS Dictionary Del Name & # Dur. Est. Critically Skill
Depend
2.2.4 Task Communication Plan and Management – Outline a plan that identifies “who” FPC – Comm. Plan & Mgmt
needs “what” communications, in “what” media, “how” often and by “whom”.
2.2.5 Task Status Reporting – Define how status will be reported, by whom, how often, and in FPC – Status Rptg
what formats and media.
2.2.6 Task Procurements & Contracting – Determine what to procure and when, document FPC – Proc. & Cntrkg
requirements and identify potential sources.
2.2.7 Task Quality Assurance – Identify the project’s relevant quality standards and determine FPC- QA
how to satisfy them.
2.2.8 Task Time Tracking – Determine what level to track time at, how time will be tracked, FPC – Time Tracking
how frequently, and administer the time tracking activities.
2.2.9 Task Issue and Decision Management – Determine process for raising and resolving FPC – Iss. & Decision Mgmt
project issues that impact the scope, schedule, cost or quality of the project.
2.3 Activity Develop the Project Plan – Integrating the results of the other N/A
planning activities into a coherent document to guide the project
execution and control.
2.3.1 Task Plan Integration – Summarize and incorporate the outputs of the planning Project Plan
activities into a single reference document – the <project name> Project Plan. The
plan is the reference document for work to be performed by all involved in the
project and must be made easily accessible to all in electronic format.
2.3.2 Task Plan Presentation and Review – Distribute, review and obtain approval of the Presentation, & Document Approval
project plan from the project directing authoritie(s) and managers who have staff
assigned to the project.
2.3.2.1 Milestone and Schedule Approved by
Plan N/A 0 PM
3.0 Phase Execution N/A
This version of an Incremental Release Lifecycle Model is a combination of
Traditional Waterfall and Spiral Development. The Business Requirements and
Conceptual Design are established for the entire system. Based on the
Implementation Strategy each System Function (Product Component) is cycled
through Functional Design, Construction, and Implementation. When all Functions
for a Release are complete, the system is assembled and following successful
Acceptance Tests by the customers is moved into Production. Implementation
Cycles overlap and the process is improved through each iteration.
89b2d78a-e6c4-4d91-aa00-c0b81894b597.xls 3
Incremental Development Work Breakdown Structure Dictionary
# WBS Dictionary Del Name & # Dur. Est. Critically Skill
Depend
This model was intentionally created to be consistent with the other DHS OIS
lifecycle models.
The following activities, tasks and deliverables should be reviewed for each project
on a case-by-case basis. Projects may utilize this model and adapt or tailor to the
specific needs of the project. This means that not all activities and tasks are
necessary for every project, and that additional activities and tasks may need to be
included.
Specific deliverables depend on the tools and techniques used by the development
staff and on the existing documentation. The deliverables listed are examples of
possible deliverables.
3.1 Activity Feasibility Study N/A
Note: Requirements definition is an extension of the process started in the
Feasibility Study. Please see the Feasibility Lifecycle model to determine if all or
some of the steps are necessary.
3.2 Activity Define Requirements N/A
The purpose of this phase is to establish a common understanding between the
customers and the software project of the customers’ requirements that will be
addressed by the software project. All system development work should be
traceable to the various levels of requirements, i.e. product description, project
objectives, hi-level requirements. Changes to the Requirements should be
managed according to their impact on the project’s cost, schedule, and quality
(scope). Note: Requirements definition is an extension of the process started in
the feasibility study, if one was performed.
3.2.1 Task Identify and describe the business area(s) to be affected by the new system Updates Feasibility Study
3.2.1.1 Subtask Refine the Feasibility Study with increasing detail to: Updated Requirements Traceability Matrix or
Stakeholder List
3.2.1.2 Subtask Identify additional Stakeholders - groups impacted by the system development. Context Diagram
3.2.1.3 Subtask Define the current business processes Procedure flow diagrams
3.2.1.4 Subtask Define the current technology – infrastructure, applications and databases Descriptions of existing reports and documents
3.2.1.5 Subtask Define the external system interfaces and primary data exchanges. Candidates for procedural change
3.2.1.6 Subtask Identify the sources and destinations of each primary data exchange. Business Rules
3.2.1.7 Subtask Identify and prioritize candidates for procedural change and automation. Business Use Cases
89b2d78a-e6c4-4d91-aa00-c0b81894b597.xls 4
Incremental Development Work Breakdown Structure Dictionary
# WBS Dictionary Del Name & # Dur. Est. Critically Skill
Depend
Business Actors
3.2.2 Task Develop Business Requirements N/A
3.2.2.1 Subtask Follow the project’s requirement management plan to:
3.2.2.2 Subtask Gather stakeholder needs from all stakeholders. Synthesize and Prioritize. Glossary
3.2.2.3 Subtask Define Requirements – transform stakeholder needs into well-defined high-level Use Cases
requirements.
3.2.2.4 Subtask Validate Requirements – evaluate each requirement and determine relative Requirements Document
priority.
3.2.2.5 Subtask Analyze Requirements – refine and categorize high-level requirements with Requirements Baseline
greater precision and detail. Categories include: functional, data, use,
performance, security, business and technical standards, operational, legal.
3.2.3 Task N/A
Reevaluate initial development approach, impact analysis, costs and benefits
3.2.3.1 Subtask The following bullets must be done in collaboration with NCS, CSS, P&P, SA,
SSI, and AMS. Refine the Feasibility Study with increasing detail to:
3.2.3.1.1 Subtask Ensure that the development approach recommended in the Feasibility Study is Updated Cost Benefit Analysis (feasibility study)
still valid.
3.2.3.1.2 Subtask Ensure that OIS cross-sections agree and can support the technical solution and Detailed plan for the next phase(s)
development.
3.2.3.1.3 Subtask Ensure that cost benefits assumptions are still valid. OIS Approved Exception Request
3.2.3.1.4 Subtask Ensure that external interfaces (projects and systems) are accurately stated. N/A
3.2.4 Task Conduct walkthrough N/A
3.2.4.1 Subtask Ensure that requirements are clear, complete, and comprehensive Issues, resolutions, changes, etc…
3.2.4.2 Subtask OIS Sections and Business Sign-off(s) indicating
Collect concurrence agreements from Major OIS Sections and Business concurrence
3.2.5 Task Obtain formal user and sponsor concurrence N/A
3.2.5.1 Subtask Decision point for the Steering Committee: Formal acceptance of the Project Plan &
Requirements
3.2.5.2 Subtask For approval of the work completed N/A
3.2.5.3 Subtask To authorize continued work on the project. N/A
3.3 Activity Conceptual Design N/A
89b2d78a-e6c4-4d91-aa00-c0b81894b597.xls 5
Incremental Development Work Breakdown Structure Dictionary
# WBS Dictionary Del Name & # Dur. Est. Critically Skill
Depend
The purpose of this phase is to develop the high-level Conceptual Design and
Implementation Strategy. The Conceptual Design is developed based on
applicable standards and best practices and is used to incorporate the business
requirements into the system design. The Implementation Strategy identifies the
potential release strategies for the Steering Committee decision on how to deliver
the system.
3.3.1 Task Develop the Conceptual Design. Conceptual Data Model
3.3.1.1 Subtask Identify best practices for the system being developed. Conceptual Process Model
3.3.1.2 Subtask Define the system’s basic functionality and information exchanges. Technology Architecture
3.3.1.3 Subtask Identify the inputs, outputs, and triggers for each system function. Use Cases (refined)
3.3.1.4 Subtask Work with NCS, P&P, CSS, SA, SSI, and AMS identify the hardware and Storyboards
software to develop and operate the new system.
3.3.1.5 Subtask Work with NCS to determine the network(s) that will support the application. N/A
3.3.2 Task Define application standards (i.e., determine how functions and data will be Description of distribution strategy
distributed, screen formats, common software functions, etc…).
3.3.2.1 Subtask Identify how system functions will be distributed geographically and technically Description of alternatives considered
(across platforms).
3.3.2.2 Subtask Define the application tiers (i.e, presentation, business logic, database) in terms Application Design Standards
of technology and function.
3.3.2.3 Subtask Describe standards for each application tier (i.e., Presentation tier will use Secure N/A
Sockets Layer (SSL), Cascading Style Sheets, error handling, naming
conventions, ODBC vs. JDBC, etc…).
3.3.3 Task Define environmental controls (e.g., security, contingency planning, restart Specifications for security, contingency and back-
recovery). up/restart requirements.
3.3.3.1 Subtask Identify the security features of the system. Use Case definition
89b2d78a-e6c4-4d91-aa00-c0b81894b597.xls 6
Incremental Development Work Breakdown Structure Dictionary
# WBS Dictionary Del Name & # Dur. Est. Critically Skill
Depend
3.3.3.2 Subtask Create contingency plan and/or revise existing contingency plans. N/A
3.3.3.3 Subtask Plan back-up and recovery processes. N/A
3.3.4 Task Define audit and control functions (error control, control totals, etc.). Audit and control specifications
3.3.4.1 Subtask Identify and describe the controls to be built into the system and used to ensure *Audit trail capture and reporting requirements
that data integrity is maintained.
*Use Case definition
3.3.5 Task Define common software functions Common routine/ software tool specifications
3.3.5.1 Subtask Identify the requirements to be automated Identification of existing reusable code to use
3.3.5.2 Subtask Identify the software functions that will be developed as common routines or N/A
software tools.
3.3.6 Task Create product delivery plan (for phased delivery) Product delivery plan
3.3.6.1 Subtask Identify the functions to be delivered in the planned versions of the system. *Implementation Strategy
Note: This activity is included for use in large development efforts in which there is *Release Strategy
need to deliver the product in phases or versions instead of as the result of a single
project.
3.3.7 Task Estimate storage, telecommunications and/or processor impacts *Hardware and communications resource
acquisition requirements. .
Note: If the system requires the acquisition of new hardware and network *Updates to Technology Architecture
resources (as opposed to increased capacity) see the Hardware and LAN
Acquisition/Installation project type.
3.3.7.1 Subtask Determine the impact of processing and storage volumes on the hardware (data N/A
storage, processor capacity) and on communications resources.
3.3.8 Task Reevaluate development approach, impact analysis, costs and benefits. Updates to previous deliverables (i.e., Plan,
Schedule, Cost/Benefit, etc…).
3.3.8.1 Subtask Ensure that the approach recommended in the Feasibility Study is still valid, N/A
given the design results.
3.3.8.2 Subtask Ensure that cost benefits assumptions are still valid. N/A
3.3.8.3 Subtask Ensure that impacts on other projects and systems are accurately stated. N/A
3.3.8.4 Subtask Revise approach and cost benefits statements as appropriate. N/A
3.3.9 Task Prepare a Conceptual Design Report Conceptual Design Report
89b2d78a-e6c4-4d91-aa00-c0b81894b597.xls 7
Incremental Development Work Breakdown Structure Dictionary
# WBS Dictionary Del Name & # Dur. Est. Critically Skill
Depend
3.3.9.1 Subtask Compile and summarize the previous deliverables into a comprehensive report. N/A
3.3.10 Subtask Conduct walkthrough Issues, resolutions, changes, etc…
3.3.10.1 Subtask Ensure that the various aspects of the design fulfill the requirements and comply Sign-off(s) indicating concurrence.
with standards.
3.3.11 Subtask Obtain formal user, technical and sponsor concurrence Formal approval of Conceptual Design Report and
Implementation Strategy.
3.3.11.1 Subtask Decision point for the Steering Committee: OIS Sections and Business Sign-off(s) indicating
concurrence.
3.3.11.2 Subtask For approval of the work completed – Conceptual Design Report & N/A
Implementation Strategy
3.3.11.3 Subtask Collect concurrence agreements from Major OIS Sections and Business. N/A
3.3.11.4 Subtask To authorize continued work on the project. N/A
3.4 Activity Functional Design N/A
The purpose of this phase is to define the detailed functional and technical design
aspects of a release. The work completed in this phase should be sufficiently
detailed to provide the construction team with specific information for how the
application should work. It is essential that business customers define the
necessary detail Analysis & Design Tasks & Deliverables are used technical team’s
Object Oriented for system functionality rather than relying on the in the rest of this
model. Structured Analysis & Design techniques can be used in place of these,
with minor changes to descriptions.
Note: The use of prototyping and Joint Application Design (JAD) are
recommended for the design of reports, screens and documents. See the RAD
template to use activities related to prototyping.
3.4.1 Task Plan for Implementation Business Reengineering Plan
3.4.1.1 Subtask Develop Business Reengineering Plan to plan for and guide the changes in Implementation Plan
business processes that are necessary to implement the system/release.
3.4.1.2 Subtask Define the Implementation Plan that specifically describe how the system/release Security Model
will be transitioned into Production (i.e., training, data conversion, switchover).
3.4.1.3 Subtask Define the post production user support (Help Desk, etc.). Support Plan
89b2d78a-e6c4-4d91-aa00-c0b81894b597.xls 8
Incremental Development Work Breakdown Structure Dictionary
# WBS Dictionary Del Name & # Dur. Est. Critically Skill
Depend
3.4.1.4 Subtask Develop the Security Model – compile all security information into a N/A
comprehensive plan over the life of the development project.
3.4.2 Task Build/acquire/ prepare the development environment (hardware and software). Installed hardware and software ready for use in
the development process.
3.4.2.1 Subtask Acquire hardware and system software resources. N/A
3.4.2.2 Subtask Ensure that the development environment is ready for use. N/A
Note: Hardware/software acquisition may require long lead times; therefore,
initiate the acquisition process as early as possible.
If there is a need to acquire hardware, system software, and/or network software,
use the Development with Hardware and LAN Acquisition/Installation lifecycle
activity list to identify those activities that are relevant to this project.
3.4.3 Task Develop test strategy
Test objectives
3.4.3.1 Subtask Define the process for validation and verification for the system/release. *Levels of testing(conceptual, functional, unit,
system, integration acceptance…).
*Roles and responsibilities for testing
3.4.4 Task Identify subsystems, their data requirements and interfaces Systems flow diagrams
3.4.4.1 Subtask Package the new system's functions into subsystems and map the flow of data Updates to Use Cases
between them.
3.4.4.2 Subtask Identify files and/or databases. N/A
3.4.4.3 Subtask Identify the media (screen, paper, electronic file, document, etc.) for each data N/A
flow.
3.4.5 Task Design User Interfaces. System prototypes
3.4.5.1 Subtask Storyboard Interfaces to describe basic flow of the screens and scenarios Screen designs
3.4.5.2 Subtask Create Prototypes with sample screens and basic functionality for customer input. *Form designs
*Report designs
3.4.6 Task Design Application Logic Design Model (that describes the realization of the
Use Cases)
3.4.6.1 Subtask Identify Candidate Classes with attributes, operations, methods, relationships, UML Diagrams, Class Diagrams, Activity
and semantics. Diagrams,…
89b2d78a-e6c4-4d91-aa00-c0b81894b597.xls 9
Incremental Development Work Breakdown Structure Dictionary
# WBS Dictionary Del Name & # Dur. Est. Critically Skill
Depend
3.4.6.2 Subtask Create Design Classes to refine the Candidate Classes with additional detail. N/A
3.4.6.3 Subtask Refactor Design Classes to identify commonality in the system to achieve N/A
maximum reuse and a consistent design.
3.4.7 Task Design External Interfaces N/A
3.4.7.1 Subtask Design the Functions of the External Interfaces N/A
3.4.8 Task Develop System Test Plan Test Cases
3.4.8.1 Subtask Define test cases (started early so that during the development of the use case Installed hardware and software ready for use in
the each test case is being defined). the test process.
3.4.8.2 Subtask Ensure that the test environment is ready for use N/A
3.4.9 Task Refine the Conceptual Data Model into a logical, application data model Logical Data Model fully attributed with
relationships, roles, cardinality, and optionality.
3.4.9.1 Subtask Identify the data required to support the system functionality. N/A
3.4.9.2 Subtask Normalize the data model. N/A
3.4.9.3 Subtask Identify data segments or records based on the way data will be used in the N/A
system.
3.4.10 Task Design physical data base and/or files Physical data base design
3.4.10.1 Subtask Map the logical data base design to the specific data base or file management N/A
system(s) to be used.
3.4.10.2 Subtask Describe the data as it will be stored on the physical media. N/A
3.4.11 Task Update previous work Documented Changes, Issues, Risks
3.4.11.1 Task Update Conceptual Design – data, process, and technology Updates to Requirements Traceability Matrix
3.4.11.2 Task Update Project Plan, Schedule, Budget N/A
89b2d78a-e6c4-4d91-aa00-c0b81894b597.xls 10
Incremental Development Work Breakdown Structure Dictionary
# WBS Dictionary Del Name & # Dur. Est. Critically Skill
Depend
3.4.11.3 Task Reevaluate technical infrastructure – storage utilization, capacity estimates, N/A
hardware acquisition
3.4.12 Task Prepare for Implementation Updates to Implementation Plan - data conversion
plan and schedule, training plan and schedule
3.4.12.1 Subtask Plan for file/database conversions – identify conversion requirements and the N/A
programs and controls required for conversion.
3.4.12.2 Subtask Identify required user, support staff and/or operator documentation and training. N/A
3.4.13 Task Conduct walkthrough Issues, Risks, Defects, Change Requests
3.4.13.1 Subtask Validate the designs (logical and physical) to ensure that they adequately fulfill N/A
requirements.
3.4.13.2 Subtask Validate that all requirements have been addressed N/A
3.4.14 Task Obtain formal user, technical, and sponsor concurrence Formal acceptance of the System Design and
Implementation Plan
3.4.14.1 Subtask Decision point for the Steering Committee: N/A
3.4.14.2 Subtask For approval of the work completed. N/A
3.4.14.3 Subtask To authorize continued work on the project. N/A
3.4.14.4 Subtask To confirm commitment of the implementation plan by all effected groups. N/A
3.5 Activity System Construction N/A
The purpose of this phase is to build and unit test the system components –
application code, database definition language (DDL), user procedures, and test
plans.
3.5.1 Task Build Test Environment System Test Plans
3.5.1.1 Subtask Define test cases, create test data, identify test criteria – include platforms and N/A
data validation.
3.5.2 Task Write System Documentation Operator Manual
3.5.2.1 Subtask Write on-line help files Administrator Manual
89b2d78a-e6c4-4d91-aa00-c0b81894b597.xls 11
Incremental Development Work Breakdown Structure Dictionary
# WBS Dictionary Del Name & # Dur. Est. Critically Skill
Depend
3.5.2.2 Subtask Write user procedures, compile into user manual N/A
3.5.2.3 Subtask Create the training material, curriculum N/A
3.5.3 Task Build Application Application Module
3.5.3.1 Subtask Develop program code and perform unit tests. Physical Database
3.5.3.2 Subtask Build user interfaces N/A
3.5.3.3 Subtask Create database to implement the schema, triggers, and stored procedures N/A
3.5.4 Task Conduct walkthrough Issues, Risks, Change Requests
3.5.4.1 Subtask Code Review N/A
3.5.4.2 Subtask Test Plan Review N/A
3.6 <Activity Title, i.e Test> – <activity description> N/A
Activity
3.6.1 Task <Task title> – Task Description N/A
3.6.1.1 <Milestone Title> N/A
Milestone
3.7 Activity Implementation N/A
The purpose of this phase is to validate the system, train the users, and transition
the system/release into production.
3.7.1 Task Validate the System Test Report
3.7.1.1 Subtask Conduct Functional Tests (black box) to ensure system performs desired Change Requests, Issues, Risks
functionality.
3.7.1.2 Subtask Once each Function is tested then assemble into a build. N/A
3.7.1.3 Subtask Conduct System Tests to ensure the system performs as expected under volume N/A
and exception conditions
3.7.1.4 Subtask Conduct Acceptance Tests to validate the system meets the customers’ Trained users, operators, and support staff
expectations.
89b2d78a-e6c4-4d91-aa00-c0b81894b597.xls 12
Incremental Development Work Breakdown Structure Dictionary
# WBS Dictionary Del Name & # Dur. Est. Critically Skill
Depend
Note: Testing may include parallel test, usability test, Beta Test, or other tests. It
may be performed in a special test environment.
3.7.2 Task Train users, operators, and support staff Formal acceptance of the system release
3.7.2.1 Subtask Ensure that all users, operators and support staff are able to use the system. N/A
3.7.3 Task Obtain formal user and sponsor concurrence N/A
3.7.3.1 Subtask Decision point for the Steering Committee: N/A
3.7.3.2 Subtask For approval of the work completed N/A
3.7.3.3 Subtask To authorize continued work on the project. N/A
3.7.4 Task Prepare for transition to production Operations schedules (batch schedule and on-line
availability)
3.7.4.1 Subtask Ensure that the production environment (including users, operations personnel, Programs transferred to production libraries
and support staff) is prepared for the start of production.
3.7.4.2 Subtask Install required new hardware, system software, and communications systems. Production job control or command lists available
3.7.4.3 Subtask Perform data conversions New or changed security data (passwords, etc.) in
the proper tables
3.7.4.4 Subtask Perform environment tests Users and support staff of systems that may be
effected by the new system advised of the
transition
Note: For applications to be run by computer operations all forms must be filled
out and submitted, as required by current procedures.
3.7.5 Task Deploy System System in Production
3.7.5.1 Subtask Move system into production use N/A
3.7.5.2 Subtask Performance tune application/database as necessary. N/A
3.7.6 Task Evaluate System/Release Updates to Project Plan, Schedule, and all
previous work
3.7.6.1 Subtask Evaluate project performance Lessons Learned
3.7.6.2 Subtask Evaluate system performance to measure how well it meets user expectations. N/A
89b2d78a-e6c4-4d91-aa00-c0b81894b597.xls 13
Incremental Development Work Breakdown Structure Dictionary
# WBS Dictionary Del Name & # Dur. Est. Critically Skill
Depend
4.0 Phase Controls – Administer and manage work controls to N/A
ensure project performance.
89b2d78a-e6c4-4d91-aa00-c0b81894b597.xls 14
