| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
|
|
Objectives:
The purpose of the Determine Code Version Control Method activity in the Develop & Test phase is to identify how developed code will be managed so that integrity and security of the development effort is maintained.
This activity is a subset of Integrated Change Control, also known as Configuration Management. Reference Project Control: Integration Management.
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
Objectives:
The purpose of the Develop & Review Content activity in the Develop & Test phase is to ensure that all customer-facing output conforms to StorageTek standards and has been reviewed by the business area and approved by the StorageTek Legal department (if needed) prior to implementation so that the product aligns with the consistent and professional StorageTek branded image as well as business area strategies and direction.
This activity addresses the need to clearly understand the business requirements for content. Content includes any text, pictures, instructions, etc. contained within a user interface or a web page. Content is static in nature. Content is NOT data populated from a system.
Customer-facing content (output) is any project deliverable that could be seen by StorageTek’s external customers and/or suppliers. This includes (but is not limited to) web pages, quotes, invoices and contracts. Content on customer-facing documents with legal implications, such as a notice on a web page that indicates pricing is subject to change without prior notice, must be approved by the Legal department.
If Legal approval is required, be sure to allow plenty of time in the schedule as it can take weeks to get something through Legal.
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
|
Objectives:
The purpose of the Develop Product activity in the Develop & Test phase is to construct the identified project solution so that the product meets all requirements and project objectives.
This activity involves technical construction of the product, including data conversion, system code, releases, installations, interfaces, reports, user interfaces, and supporting documentation. The product is the sum of all that is built and delivered as part of the project. This activity also includes implementation of the architectural plan as signed off by Green Team members. See Green Team Process for more details.
Develop Product, Conduct Unit Test, Perform Code Reviews and Conduct Functional Test activities are iterative in nature and are repeated until successful functional test results are achieved. It is also important to note that projects using an iterative approach may perform these activities several times throughout the project life cycle as they work through each iteration.
If this activity leads to any design changes, the project team needs to have the baseline design re-approved.
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
|
The purpose of the Conduct Unit Testing activity in the Develop & Test phase is to ensure all work units operate as designed, without error, so that there is confidence that the individual pieces work as expected and meet the required functionality.
This activity involves the individual component testing to verify functionality and expected results. This activity includes development of unit test cases, unit test design, execution, capturing and analysis of results, rework to fix defects and retest. Components include application changes and any new functionality, interfaces and data conversion. Additional components are hardware and software installs, database setup and security access.
Develop Product, Conduct Unit Test, Perform Code Reviews and Conduct Functional Test activities are iterative in nature and are repeated until successful functional test results are achieved. It is also important to note that projects using an iterative approach may perform these activities several times throughout the project life cycle as they work through each iteration.
Execute and test every line of code or widget for the work unit
Test the work unit for all of the following
all conditional and compound conditional variations
test loop limits
error handling
file and data interaction including empty and multiple record files
all user interaction including, but not limited to, screen layout and navigation, numeric and alpha numeric fields, list boxes, drop downs, scrolls, etc
Usability test
human factors, navigation, presentation
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
|
The purpose of the Perform Code Review activity in the Develop & Test phase is to verify the accuracy, efficiency and supportability of developed components so that it aligns with GIS standards.
Develop Product, Conduct Unit Test, Perform Code Reviews and Conduct Functional Test activities are iterative in nature and are repeated until successful functional test results are achieved. It is also important to note that projects using an iterative approach may perform these activities several times throughout the project life cycle as they work through each iteration.
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
|
The purpose of the Conduct Functional & User Acceptance Tests activity in the Develop & Test phase is to ensure that the application’s functional requirements have been met and that the application works end-to-end so that the product is ready for release testing.
Focused on work unit to work unit flow and control as well as data exchange and consistency
Organized by related business processes and functions
Includes test of application security
Network impact modeling, if necessary (Network impact modeling is required if new/changed network infrastructure components or client software are introduced with the project)
Includes user negative testing at the project team’s discretion
Includes revision of Requirements Document (Acceptance Criteria and Accepted By) indicating requirement was met
TestDirector is used to track functional and release test results. The project manager contacts the test team to request a project folder be set up in Test Director for their project. TestDirector produces reports which can be used in test review and readiness review meetings.
Develop Product, Conduct Unit Test, Perform Code Reviews and Conduct Functional Test activities are iterative in nature and are repeated until successful functional test results are achieved. It is also important to note that projects using an iterative approach may perform these activities several times throughout the project life cycle as they work through each iteration.
All of the web pages used to implement order entry functions for direct sales are tested together. Each ordering function is followed from start to finish within the application.
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
|
|
Objectives:
The purpose of the Conduct Performance Tests activity in the Develop & Test phase is to test the product in the environment so that any issues can be addressed prior to moving the product to the production environment to ensure the product meets the performance requirements.
This activity should be completed, when required, as early in the Develop & Test phase as possible because a negative outcome could mean redesigning the solution. It can be performed as soon as the product is stable enough to test and an environment is available. If issues are discovered, the project team may need to work with the architecture and infrastructure teams to determine a solution.
This activity includes defining the test needs, the test scenarios and requesting the test team perform the tests.
Performance test - Simulates realistic transaction volumes, based upon projected system usage and prior project experience
Stress test - Determine the maximum throughput of transactions and data
Desktop configuration test - Test new / changed client software on existing desktop configurations
Project manager fills out the Performance Test Request.
Submit to test team.
Test team will schedule meeting with the project manager to discuss details and options.
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
|
Objectives:
The purpose of the Revise Business Processes activity in the Develop & Test phase is to update the business processes impacted by the product so that business users will know how the product interacts with their processes.
This activity can begin as soon as the solution and design are complete. The project manager should coordinate this activity with the process owner.
The tasks involved with this activity include:
Schedule a work session with the process owner and business users to identify the new or changed process activities
Facilitate the session
Document the new or changed process
Obtain the process owner’s approval
Hand off the new or changed process to the process owner
The process owner’s responsibilities include:
Identification of business users who need to assist in identification of the new or changed process activities
Provide clarification in areas of the process which may need clarification
Ensuring the process is communicated to the process users
Any training necessary for the new process
ISO document requirements ongoing (includes periodic reviews, updates, approvals, etc.)
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
Objectives:
The purpose of the Develop Training & User Documentation activity in the Develop & Test phase is to ensure that all the necessary training and reference materials are developed so that the product’s introduction into the business area is smooth.
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
|
Objectives:
The purpose of the Develop Maintenance & Support Turnover Documentation activity in the Develop & Test phase is to complete all tasks documented in the Maintenance & Support Turnover Plan so there is a smooth transition from the project team to the support team.
Per the Maintenance & Support Turnover plan, all necessary system and turnover documentation should be completed. This includes any required documentation specific for each support team, identified project documentation (e.g., configuration management, design documents, etc.), updating or creating the application disaster recovery report and updating or creating the WORP page.
The GIS PMP Checklist identifies project documentation that may be requested by the support teams.
Related Links:
Application Disaster Recovery Process
WORP Process
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
|
Objectives:
The purpose of the Develop Business Rollout Plan activity in the Develop & Test phase is to ensure that all required business-related activities have been identified, assigned and scheduled so that there is a smooth integration of the product into each of the affected business areas and that the product aligns with business area standards and procedures.
Below is a list of tasks which may need to happen (this should not be considered a complete list but rather a place to start):
Training
Training logistics (travel, room setup, etc.)
Communication
Update processes, procedures, flow charts
Update roles and responsibilities
New equipment setup
| Inputs | Outputs | Who Performs | Who Reviews | Tools |
|
|
|
|
Objectives:
The purpose of the Develop Technical Implementation Plan activity in the Develop & Test phase is to ensure that all required activities have been identified, assigned and scheduled to move the product into the production environment so that defects and scheduling problems related to turnover are minimized/eliminated.
Below is a list of tasks which may need to happen (this should not be considered a complete list but rather a place to start):
Setup production environment
Production change control
Note: All changes to the production environment as a result of project work need to be submitted at least two weeks early to change control. It is highly encouraged to submit changes even earlier, to guarantee your slot, and/or have the flexibility to rearrange schedules if conflicts are detected. Changes will be reviewed by the change review board every other week. Project managers will also be required to attend the change review board to represent their project.
Data conversions
Setup of business users environment
User access
Deployment notification
Contingency plan
Move to production (who does what and when, dependencies or a specific order in which code/modules must be migrated, etc.)
Setup war room if applicable
Identify maintenance and support team members and how the product will be turned over to them
Identify and develop production validation tests
Setup training environment