02 问题发现与模型驱动的毂发过程

What is a Business Problem

Examples

●1 Monsters University course registration platform crashes frequently during the course registration period.
● 2Monsters University course registration platform rejects the course retaking requests because of the randomize selection strategy.
●3 Professor Knights takes subway to work. It’s a little far away from the subway station to his office by walk but expensive to take a taxi.
● 4Monsters, Inc. wants a new human resource management platform.
● 5Professor Knight’s personal website has 10K unique visitors but no revenue收入
● 6Monsters, Inc. decides to start a e-commerce 电子商务 business.
● 7Sullivan is a console game player. He wants to play his games with his friends online.

• Source
  Defect
  Market Opportunity
  Leadership Order领导命令
• Granularity粒度
  High-level Question -->Details
• Foundation
  System Construction
  System Enhancement
• PIECES
  Performance – 1
  Information
  Economics
  Control
  Efficiency
  Service

Start Working on a Business Problem (The Scope Definition Phase)

Tasks

● Identify baseline problems and opportunities
● Negotiate baseline scope
● Assess baseline project worthiness
● Develop baseline schedule and budget
● Communicate the project plan (with skateholders)

Fully Understand a Business Problem (The Problem Analysis Phase)

• Above the Water VS Underwater

Fully Understand the Problem–HOW?

The Problem
Who did raise the problem?
Why did he/she raise it?
How difficult to solve it?
Is it worth to work on?
How urgent is it?
Is there any constraints? e.g.law
Fully Understand the Problem
Who did raise the problem?
Why did he/she raise it?
How difficult to solve it?
Is it worth to work on?
How urgent is it?
Is there any constraints?
What is the problem domain?
How this domain works?
Is it a valuable in this domain?
Is there any similar solutions?
How do they work?
Is there any uncertainties /hypothesis?

Am I understand CORRECT?

Tasks

● Understand the problem domain
● Analyze problems and opportunities
● Analyze business processes
● Establish system improvement objectives
● Update or refine the project plan
● Communicate findings and recommendations

Student Information System

Scope Definition and Problem Analysis

● Core functions
○ Class sign up
○ Class schedule
○ Grading management
● Other deliverables
○ Documents, trainings, etc.
● Core values
○ Data management capability
○ More efficient business process (class sign up, schedule, grading management)
○ More fair class schedule
○ Less incorrectness
○ Etc.
● Updated plan

Context Diagram

● The purpose of a context diagram is to analyze how the system interacts with
the world around it and to specify in general terms the system inputs and
outputs.

Resolve Business Problems

● Problem Reading -> understand the problem
● Breakdown the problem to sub problems
● Find out the key problem
● Conception -> propose a solution
● Calculation -> implement the solution
● Result Checking -> validate with the clients
● Answer Writing -> release (demo)
● Get feedback and iterate

Solution Strategies

● The Model Driven Development Strategy
● The Rapid Application Development Strategy
● The Commercial Application Package Implementation Strategy
● Hybrid Strategies

The Model Driven Development Strategy

● A system development strategy that emphasizes the drawing of system models to help visualize and analyze problems, define business requirements, and design information systems.
● Pros
○ More thorough specs
○ Better documentation
○ Help have thorough discussion before actual construction
○ Requirements and designs are easier to validate with pictures than words
● Cons
○ Time-consuming
○ Pictures are not software
○ inflexible

Modelings

● Data Modeling
○ Entity relationship diagram
● Process modeling
○ Structured analysis and design methodology
○ Data flow diagram, structure charts
● Object modeling
○ Object-oriented analysis and design
○ UML

The Rapid Application Development Strategy

● A system development strategy that emphasizes speed of development through extensive user involvement in the rapid, iterative, and incremental construction of a series of functioning prototypes of a system that eventually evolves into the final system (or a version).
● Pros
○ Friendly to uncertainties and changes
○ Higher visibility
○ Users see working, software-based solutions more rapidly than model
driven development
○ Defect errors earlier than model driven development
○ Natural testing and training
● Cons
○ “Code, implement, and repair”
○ Easily solve the wrong problem
○ Discourage considering other, worthy technical alternatives
○ More communications when it’s the best to throw a prototype away
○ The emphasis on speed can adversely impact quality

Commercial Application Package

● A software application that can be purchased and customized (with limits) to
meet the business requirements of a large number of organizations or a specific industry.
The Commercial Application Package Implementation Strategy
● Pros
○ Fast
○ No need to build in-house机构内部 technical teams
○ Cheap
○ No need to be responsible for significant system improvements and error corrections
○ No need to “reinvent the wheel” on business functions
● Cons
○ Dependent on vendors
○ Rarely reflects the ideal solutions
○ Always need to change business processes to adapt to the software