This phase proves the validity of the design concept by prototyping the final solution in a development environment and tested within a staging environment.
The development and staging environment will need to be setup during this phase. At the beginning of the phase an acceptance plan is agreed upon by both CFI and the University which will include a subset of the requirements defined in Phase 1 as part of the prototype development. The components of the system are created or procured, installed and tested with sample legacy data approved by the University.
Prototyping is done within CFI’s development environment and migrated to the staging environment for testing.
Standard CFI test cases will be modified to align with the agreed upon functional
requirements validated in Phase 1. Test cases will be used for unit testing by CFI and user acceptance testing by the University.
Computerized Facility Integration, L.L.C.
www.gocfi.com The prototype phase may result in modifications to the design specification and the project plan, but should produce agreement from all parties to continue the project.
Phase 3 – Prototype Deliverables:
• System Installation and Configurations
o Development Environment Setup – The CFI technical team will build the development environment on CFI servers using the agreed upon standards and applications from the design documentation.
o Staging Environment Setup – The University will be expected to setup the staging environment on their servers using the agreed upon standards and applications from the design documentation. The staging server is required to mimic the production setup.
Development Environment:
• Data Mapping/Collection – The data collected at this phase varies based on the modules to be implemented and the acceptance plan for this phase, however, Portfolio and core data discussed in the Data Standards Definition would always be collected. CFI will provide TRIRIGA 9 templates with the appropriate headers. The University will be responsible for extracting the data from the existing legacy system and populate the templates provided. The University may expect to extract data again during the build phase.
• System Population -
o Data - Data collected above will be populated into the development system.
o Drawing - A subset of drawings will be linked and available for testing. • System Modification and Development – Based on the acceptance plan for
the prototype, processes and requirements will be built into the system. This will include all schema modifications, GUI changes, workflow modifications and notifications which will demonstrate the select processes.
Staging Environment:
• System Replication from Development to Staging - On completion of development, the developed product will be migrated to the staging environment
• Test Case Development– CFI will develop test cases to align with the
processes of the acceptance plan of this phase. The University may add to the test cases to meet their internal IT policies
• Systems Acceptance Testing –
o Unit Testing - Using the test cases developed, CFI will perform unit testing.
o User Acceptance testing – CFI will require the University to perform the same tests within the staging environment on their servers. Successful testing will result in a phase 3 sign off.
Computerized Facility Integration, L.L.C.
www.gocfi.com
Assumptions:
• Any change to the functionality of the legacy systems after the data migration has begun that may require CFI to modify installations and configurations will be considered out of scope.
• Asset data currently in PDF files will be extracted by the University to an excel spreadsheet format provided by CFI.
• Legacy data will be provided to CFI in a CFI specified format
• Legacy data provided to CFI is expected to be correct and consistent.
Phase 4: Build
During this phase, the system is finished, installed and configured. All application
development and modifications are completed and the whole system is installed and tested at the University’s site. This phase will result in a fully functioning system based on the
acceptance criteria. We adapt our installation and testing procedures to conform to our University’s IT standards, in a two stage testing–production server sequence. Testing is against the acceptance criteria developed earlier. The build phase ends with a fully functioning, ready-to-go-live production system.
CFI will complete the following tasks:
Phase 4 Deliverables
Development Environment:
• System Modifications and Development – All modifications and/or functionality development will happen within this phase. This will include
o Database schema changes
o Process or workflow changes
o User interface modifications
o Notification and Approval setup
o Security Setup o Report Creation o Portal Setup o Roles Setup o Visualizers o Drawing links • Testing
o Test Case Development – CFI will complete development of test cases to align with the all the processes defined in the functional and design requirements documents. The University may add to the test cases to meet their internal IT policies.
o Unit Testing – CFI will conduct complete tests in the development environment prior to migrating to the staging servers. Tasks here will include
Computerized Facility Integration, L.L.C.
www.gocfi.com
• QA/QC
Staging Environment:
• System Replication from Development to Staging – On completion of development, the developed product will be migrated to the staging environment.
o System Modifications – All system modifications and development from the development environment will be migrated to the staging environment.
o System Integration – Integrations configurations setup in development will be migrated to the staging environment.
• Data & Drawing Population – The balance of data and drawings for the entire scope of the project will now be populated into the system, linked, published and available for your teams review. CFI will request a full data dump from the existing system at this time
Assumptions:
o CFI will not migrate any differential data but will migrate the full data dump as a whole. The final data dump needs to include ALL data to be migrated
• User Acceptance Testing - Your team will be provided electronic testing scripts for the purposes of navigating through implemented modules and processes to meet your functional requirements. Communication portal will be used to log bugs which will be resolved by CFI. On successful testing the product will be ready for the Production system and will sign off on Phase 4.