[Langzixue programming] [Reading Notes]-Demand Analysis of the TAO nature

Nature of the Tao-object-oriented Practice Guide

• Demand Analysis: pursuing perfection vs. Tolerating Defects
  • Design Scheme
    • fish and bear's paw
      • ainemo
        • advantages
          • low development and maintenance costs
          • simple structure
        • disadvantages
          • lack of flexibility
      • bear's paw
        • advantages
          • Flexible
          • scalability
        • disadvantages
          • complicated structure
          • high development and maintenance costs
    • Sword in my heart
      • 1. If you want to meet your needs, try to select "Xiaoyu" and discard "bear's paw"
      • 2. There are unquestionable reasons for choosing "bear's paw"
    • Go Astray
      • New technology syndrome
      • Silver bullet Universal Theory
      • Transition Design
    • Prodigal Son's post-reading experience
      • Understanding
        • All requirements-oriented design solutions at minimal cost
      • Doubt
        • How can we ensure the scalability and maintainability of the project by taking "Xiaoyu" as the "bear's paw?
  • Target & Scope
    • Project objectives
      • Concise and clear
      • Views of all project owners on Project prospects and Product Development
      • Play a guiding role in the project process
    • Project Scope
  • Requirement Analysis
    • What is demand?
      • Users have clear expectations and requirements for software products to solve their business problems
      • It should not include design details, implementation details, project plan information or test information.
      • A constraint between the customer and the project team
    • Functional requirements
    • Non-functional requirements
    • Project Stakeholders
      • Customer
        • The person who pays for software products, such as the boss
      • User
        • Persons who directly use software, such as operators
      • Other stakeholders
      • Note: Not includingProgramEmployee
  • Demand change
    • Effective Management & control of demand changes
    • Iterative development and feedback
  • actual operation
    • Procedure
      • 1. Determine the target and scope
      • 2. analyze all stakeholders based on the target and scope
      • 3. Extract non-functional requirements
      • 4. Extract functional requirements
        • Use Case Analysis
      • 5. Write the project requirement statement
    • Tips
      • What you really need is not what you want
      • Use prototype to communicate with users and explore requirements

Figure: