Microsoft Solution Architecture (module VIII)

11. Module 8: Stabilize your solution <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office"/>

1) Module Overview

The stability phase of Microsoft Solution architecture

Test and trial run for stable phase

2 The Stability phase of the Microsoft solution Architecture

I. Overview of the stability phase of the Microsoft Solution Architecture

Goal:

Improve the quality of the solution to deliver acceptable standards for product release

Team Focus:

• Improve the quality of solutions

L Outstanding performance in preparation for release

• Shift from focus on structural characteristics to focus on quality

• Transfer the solution to the stabilization phase

L ready to release

Ii. Milestones in the stability phase of the Microsoft Solution architecture and the items that can be submitted

Error collection-> 0 error bounce-> user acceptable test complete-> release substitute-> product test run complete before-> trial

Items to be submitted:

L Trial Run Overview

L for release of the following entries:

N Source code and executable files

n Scripts and installation documentation

N End user Help and training documentation

N Manipulating documents

N Publishing Notes

L Test and Error Reporting

L Project Documentation

Iii. Addressing the challenges of the stabilization phase

Stabilizing a program includes predicting

L predicting the number or severity of errors

L Predictive Error resolution process

L Estimating the quality status of each point of the scheme

L Forecast Release date

Use effective technology to help make accurate predictions

L Assume a fixed date of shipment

L Use error convergence as a stable indication

L treat the 0 error rebound as a steady indication

Iv. Adoption of a fixed shipping date

Consider the item's shipping date as a fixed variable relative to the actual shipping date

Motivate creativity by removing date of change of project shipments

Use a fixed shipping date as a driver to make a decision

Motivate the team to drive the process forward

v. Using error convergence as an indication of stability

Bug Convergence: The point at which the ratio of the error is resolved beyond the error found

Trends in Bug Convergence:

L Help predict when solutions can be released

L Provide objective instructions for the process

Temporary milestones: Bug convergence

3 Test and trial in stable phase

I. User-acceptable testing

User-acceptable testing: ensuring that users agree that solutions can meet the needs of users in a lab-only environment

Test process:

L driven by user experience role

L Don't confuse customer acceptability at the end of a project

II. Designation of a release substitute

Release Candidate: already tested for creation and ready to release trial

• Includes all elements that need to be published (e.g. code, documentation, support, and training)

L suitable for release on quality standards

L Successful validation of the pre-product test

Temporary milestones: Release candidates

III. Pre-product testing:

Pre-Product testing: Validation Release candidates pass the release criteria

Executing in a lab environment

Including completion and testing of the regression plan

Synchronization occurs with other pre-trial activities:

Driven by Release Management role

Temporary milestone: Product test completed before.

Iv. testing under realistic conditions

Trial run: Test under realistic conditions, such as:

L A subset of the product server

L A subset of users in a user group

• A test period for the overall product environment, including the ability to roll back

Test run target:

• Take the next step in the ongoing stabilization process

• Reduce the risk of deployment

v. Ready for trial Operation

Before you start a pilot run:

L Team and participants identify the criteria for successful trial operation

L must have feedback process

L The trial person is notified

L use checklists to validate support processes and other aspects of trial readiness

To test the deployment process for a trial

• All elements of deployment are rehearsed

Vi. performing a pilot operation

Implementation of the trial run:

• Identify and track issues

• To solve problems through further development

Evaluation results

L Compile and evaluate test run data

• Identify errors that users often encounter

L Choose a strategy for moving forward

4) Module Summary

The purpose of the stabilization phase is to reduce the risk of a solution for releasing a product

A successful stabilization phase requires the team to move from a focus on the construction feature to a focus so that the solution reaches a known quality state

When the solution moves from release candidate to trial, the process of gradual transfer to operation occurs