11. Module 8: Stabilize your solution
1) Module profile
Microsoft Solution Architecture Stability Stage
Test and trial operation for stable stages
2) Microsoft solution structure stabilization stage
I. Overview of the stability phase of the Microsoft Solution Architecture
the goal:
Improve the quality of the solution for the acceptable standards acceptable
Team focus:
l Improve the quality of the solution
l Specialty in the preparation
l Transfer from the focus of constructor to the quality of attention
l Transfer the solution to a stable phase
l Preparing to release
II. Milestones for the stable stage of Microsoft Solutions Architecture and Submitted Items
Error collection -> zero error rebound -> User acceptability test completed -> release substitute -> Pre-product test -> test run completed
Submitable items:
l Trial run margin
l The following entries are released:
n Source code and executable
n script and installation documentation
N End users' help and training documents
N operation documentation
n release considerations
l Test and error report
l project documentation
III. Challenges to stabilize stability
Stable a program includes prediction
l predict the number of errors or severity
l predict the error resolution process
l estimated the quality state of each point
l predict the date of release
Use effective technical assistance to make precise predictions
l Suppose a fixed shipping date
l Converge error as a stable indication
l Take zero error rebound as a stable instruction
IV. Adopt a fixed shipping date
See the shipping date of the project as a fixed variable relative to the real shipping date
Inspire creativity by removing the changes in the project shipping
Use a fixed shipping date as a decision
The motivation team is forwarded
V. Using error converge as a stable instruction
BUG converge: When resolving the error ratio exceeds the ratio of the discovered error ratio
BUG converges tendency:
l Help predicting when can be released
l Provides objective instructions for the process
Temporary milestone: bug convergence
3) Test and trial in the stable stage
I. User acceptability test
User Acceptability Test: Make sure the user agrees that in a non-laboratory environment, the solution can reach the user's needs.
Testing process:
l Experience role drive by user
l Do not confuse the customer acceptability with the end of the project
Ii. Specify a release of a replacement
Publishing Hou Selection: Created by testing, and preparing a trial
l includes all elements that need to be published (such as code, document, support, and training)
l Suitable for publishing on quality standards
l Successful verification of before product test
Temporary milestone: release candidate
Iii. Test before guiding products:
Pre-product test: Verify the publishing candidate passed the release standard
Execute in a laboratory environment
Including completion and test regression plan
Synchronize other activities before other trials:
Driven by the release management role
Temporary milestone: test before product test.
Iv. Test under realistic conditions
Test operation: Test under realistic conditions, such as:
l A subset of the product server
l User subset in a user group
l Make a test period during the overall product environment, including the ability to roll back
Trial operation target:
l Take the next step during the ongoing stability
l Reduce the risk of deployment
V. Prepare trial operation
Before starting a trial run:
l Team and participants have clear the standards for trial running success
l There is a feedback process
l Trial is notified
l Use the checklist to verify the preparations for other aspects of the support process and trial
Test trial deployment process
l All elements deployed must be rehearsed
Vi. Executive trial operation
Realization of trial operation:
l Clear and track problems
l Solve problems through further development
Evaluation results
l Compilation and evaluation trial operation data
l Clear the mistakes often encountered
l Select a strategy for continued advancement
4) Summary of modules
The purpose of the stable phase is to reduce the risk of reducing the solution. A successful stable phase requires a team to transfer to construct characteristics to paying solutions to reach a known quality state.
When the solution moves from the publish candidate to the trial, the process of gradually transferring to the operation occurs.
