9. Module 6: Plan your project
1) Module profile
Planning stage of Microsoft Solutions Architecture
What is planning to generate?
How to generate
When is the plan to generate?
Ready to develop and test the environment
2) Planning stage of Microsoft Solutions Architecture
I. Overview of the test phase of the Microsoft Solution Architecture
the goal:
l Create a solution architecture, design, project plan, and schedule
Team focus:
l Find as soon as possible as possible
l Knowing when you have information that is enough to move forward
II. Milestones and submissions of the planning stage of the Microsoft Solutions Architecture
Technical verification completion / set the baseline of the specification / set the baseline of the primary project plan to set the baseline / establishment of the main project schedule / established development and test environment
Delivered product:
l Specification
l master project plan
l primary evolution table
Iii. Effective plan
Program can reduce risk
l early detection defect
l control fee
l Improve quality
Plan to work hard
n pre-plan
n treat the plan
IV. Microsoft Solution Architecture
Plan is an iterative process
Effective plan to answer key questions
L What we have to generate?
l How do we generate it?
l When will it generate it?
l We are ready to generate it?
3) What is planning to generate?
I. Verification Technology
Start assessment of techniques for assessing the performance of technology and operation of each performance
l Manual installation or configuration new technology
l Write what environment and what environment is required to write
l Provides input for the design process
l Clear entries and technical risks
l Reflecting these entries and risks in project plans and schedules
Temporary milestone: technical verification
Ii. Design solution
Concept Design
Logical design
Physics design
Iii. Concept design
Propose business needs and user needs
l Place demand and feature into business logic
l Create an input as an input as a preliminary specification
Duplication of minimization efforts
Clear demand
l security
l availability
l Reliability
l Manageability
L scaling
l support sex
IV. Tips for data collection
Talk
Ask for users
Existing documentation or chart
Prototype
group discussion
User investigation
Help group
Play a user
V. Logic design
Describe solutions with solutions, structures, and interactions
Create a series of objects, services, and properties, a logical database and a user interface for your application
Clearly logical binding of underlying architecture and components
Open in concept design errors and contradictions
Foundation for physical design
Physical design
Specific implementation of logical design
l Clear physical underlying architecture and layout
l Create a series of physical design models for applications, including component design, user interface design, and physical database design.
l Provides flexible design based on components
Find compatibility with corporate architecture
Estimation implementation option
Become a basis for fees, schedules and resource estimates
VII. Design Target Type
safety
Sustainability
Scalability
Operability
Usability
Easy to develop and deploy
Scalability
Reuse
Manageability
reliability
Integration with existing systems
VIII. Specifications
Specifications Describe the functionality of the upcoming solution and the product generated in the design phase
This important submission item:
l Curing general understanding of business and user needs
l As a team and customer a contract for the final
l clearly understand the problem of decomposition in logic and modularize it.
l Provide a path and structure for the plan, schedule schedule and build solution
Temporary milestone: determine baseline for specifications
IX. Creating Specifications
Understand the needs of the audience
Map feature to users and business processes
Concise designation to a certain level of detail
Limit the necessary places
Includes input as a constraint
Iteration to encourage feedback
As early as baseline, freezing late
X. Specifications
Summary of functional
Information background
Design goals
User use scene
Characteristics and service
Details of components (products and configuration)
annex:
l Enterprise architecture documentation
l Abstract, logical and physical design products
