On-premises implementation - design and develop
This unit is a summary of the design and develop phases of an implementation of Finance + Operations (on-premises).
Deploy a development and test environment
The dev and test environment include the core Finance + Operations functionality. The environment also includes tools, such as the Microsoft Visual Studio Agent, which assists in the management and version control of developed items within the development sprint cycles. The dev and test environment is also used during the development sprint cycle for functionality testing by developers and subject matter experts (SMEs). The daily build is deployed to the dev and test environment to ensure that the most up-to-date customizations and configurations are available for testing each day. This environment is also used for overall solution testing when all sprints are complete, and the final requirements sign-off is complete.
Define test cases and create test scripts
All requirements must be tested. Test scripts should be created whether the requirement is addressed by using a standard configuration or a customization. If any plug-in independent software vendor (ISV) solutions exist, they should be tested to ensure compatibility, as should any integration to internal or external systems, data migrations, or uploads. As test scripts are produced, if any design issues are identified, the development team should update the design as needed to better meet the requirement. This means that test scripts must be created before development is complete. As with the design process, focus should be on software delivery and test scripts should be complete with respect to what they validate. These test scripts should not be connected to performance and scalability unless stated in the requirement. If needed, performance and scalability testing will take place separately.
Sign-off functional design documents (FDDs)
A functional design document (FDD) should be created for all gaps. An FDD should include requirements, functional principles, security implications, and the planned end-user experience for the specific functionality. This step is complete when FDDs have been completed and signed off.
Sign-off technical design documents (TDDs)
When a functional design document (FDD) is completed and signed off, it then becomes a technical design document (TDD). A TDD should include the planned technical execution of a functional design. This step is complete when completed and signed off FDDs have become TDDs.
Analyze code
Customization analysis offers an automated tool to validate a customer’s model files against Microsoft’s best-practice rules for tables, classes, forms, and enums. The tool then generates reports that list all identified issues. Evaluate your customizations by using customization analysis and then file bugs for the issues that were identified.
Identify a gold build and sign-off
Identify the gold build that you want to use for your Production environment. After you have identified the build, upload it to the Lifecycle Services Asset library and tag it as a gold build.
Revise milestone dates
Same as cloud implementation.