10. Module 7: Develop your solution
1) Module profile
Microsoft solution structure development phase
Test solution
2) The development phase of Microsoft Solutions Architecture
I. Overview of the development phase of Microsoft Solutions Architecture
the goal:
Complete the characteristics, components and other elements described in the specification
Team focus:
l Write code
l Develop the underlying structure
l Create a training document
l Develop market channels and sales support
II. Milestones and submissions of Microsoft Solutions Architecture Development Stage
Conceptual verification completion -> Internal release 1-> internal release 2-> internal release N
Submitted items:
Solution code
structure map
training material
Documentation
N deployment process
n operation method
N support and problem solving
Market material
Upgrade master plan, timetable and risk documentation
III. Executive Project Plan
Start development according to planning and timetable
Started current work
Integration creation and testing throughout the development phase
IV. Development of the underlying structure
The development of the underlying structure includes the following tasks:
l
l Create a deployment script and process
l Deploy Automation Tools and Deployment Checklist
l Developing problems to solve and fail service
l Develop backup and recovery or feedback methods as pointed out in the planned documentation
V. Concept verification
Establish baseline for the underlying structure of the solution
Determine the survival capacity of the scheme in a simulated environment
Does not include user code components
Informed development student cycle setting phase
Temporary milestones: concept of verification completion
Vi. Generate
Constructions completed by developers include:
l Confirm the normal operation of the scheme in the simulation environment
l Provide the basis for the development of iteration
Construction includes:
l Code component, directory structure, underlayer, documentation, deployment script
l For initial builds, it may be just a few components.
Generate: Stage sexual integration of all sufficiently completed elements included in the scenario
VII. Development solutions using internal release
Gradually increase characteristics
Create a detailed test case
Stabilize each internal release
Release quality indicators for each internal release to achieve temporary milestones
Internal release cycle:
Internal release version 1-> Feature development -> test and stability -> Buffer time -> internal release 2
Viii. Use the internal release cycle
To evaluate the generated quality setting standard
Try to release each internal version independently
Frequent generation and testing
True frequent code review
IX. Use the benefits of internal publishing cycles
Promote the decomposition of complex projects into manageable tasks
Provide opportunities for implementation of changes in planning
Increase the overall quality of the solution
Provide short-term motivation targets
X. Steps for daily generation processes
Each internal release cycle includes a series of daily generation
There are three steps in daily generation:
l Development: Temporary milestone arrangement for internal release
l Test: Test according to test plan
l Verification: Evaluation according to quality standards
Xi. Development of internal version through daily constructors
Each internal release version starts with a series of daily generation
Then it is test and stability
When the temporary milestone is reached
Xii. Code review
The code review can be formal, informal or third parties
Solutions benefit from the following aspects:
l Improve code quality
l Accelerate the development speed
l makes falseization clear
Projects and teams benefit from the following aspects:
l Provide training
l Reduce the cost of error decision
l Improved code maintenance
l Improve development practice and standard
Code review: Access the code to improve its quality and development team capacity
Xiii. Implementation code review
Early start code review
Clearly scheduled time
Share learned lessons
XIV. Create an entry submitted by the user experience
The entry submitted by the user experience has a user experience role drive
l Synchronization of items submitted with other plans
l iterative development
l Publish the development and designated internal release
Submitted items
l User references
l user interface interface element
l User training
l Use test plots
XV. Create an operation document Operation document creation by the release manager role
l Synchronization of items submitted with other plans
l iterative development
l Publish the development and designated internal release
Submitted entries include:
l Operation guide, standard operation method
l Help documentation and support method
l Knowledge base
l Support employee training
