Microsoft Solution Architecture (Module 5) (2)

zhaozj2021-02-17  51

4). Define solutions

I. Define issues or opportunities

task:

l Access information through personal interviews or holding a group of investors.

l View known issues

l Curing and analyze information

l Write the problem or chance to clear the document

important:

l Establish the power of initialization projects

l How do you want to do this project and what you want?

l Will you pay attention to business value?

l may include additional information, such as market data, competitive analysis, and customer feedback

Ii. Create a shared prospect

task:

l Draft a expected in the conference of the core team

l Accept the idea submitted by the initiator and use it as one of the tasks of the project.

important:

l Make the team to adapt to the common direction

l Simplify while ensuring the consistency made

l motivation team

l Enhance the goal of the solution

l Maintaining the quality of the solution

definition:

l The expected is a solution for a solution.

III. Collect high-level needs:

task:

l Drive process (completed by product manager)

l Use the interviews, investigations, produce prototypes, observations and inspections to have documentation

l Conflict expression needs and describe "what" instead of "how"

l Pay attention to business needs

l includes acceptable standards

important:

l Provides input by all roles to create a solution concept

l Form some standard for the estimated functional range

l Evolution to detailed requirements in subsequent phases

definition:

l Demand is a condition that must be achieved.

Iv. Create user profiles

task:

l Clear user's category

l Decide what they need to do

l Estimate user skill level

l Manage users' expectations and needs

l Push design decision

definition:

l User profile: The end user is described by geography, organization, and communication structure, user functions, resource usability, and other information.

V. Concept of Solution

important:

l A series of high-rise methods that include different roles driven

l In high-level description characteristics

l Help Set the initial function range of the project

l Create a first view of a design

definition:

l Solutions Concept: How to Solution How to Solve the High Level Description

Vi. Concept of Creating a Solution: The first step

Define solutions in a goal and constraint

l Define the target

l Design goal

Objects clearly achieve

Will be used to generate or apply the assumed and constraint written documentation

Write the standard written standard

VII. Typical ways in a solution concept

way

Responsible role

Design and architecture process

Developer and program manager

Communication and marketing process

Product manager

Project or quality assurance process

Program manager

development process

Developer

Usability

user experience

Testing process

Testers

转载请注明原文地址:https://www.9cbs.com/read-28670.html

New Post(0)