Preface
Acknowlegement
Chapter One. Power of Visualization
1.1 A Picture is Worth A Thousands of Words
1.2 Misleading Templates
1.3 Tennis Scoring
Chapter Two. Business Analysis Leverages
- 2.1 Business Analysis in Software Development Process
- 2.2 Frequently Found Issues
- 2.3 Requiremental Debts
- 2.4 Built-In Quality
Chapter Three. Project Workflow of Day-Off
- 3.1 Basic of Workflow
- 3.2 Abstractions
- 3.3 Conditions
- 3.4 States
- 3.5 Respond to Changes
Chapter Four. Project Registration
- 4.1 Basic Requirement
- 4.2 Parallel Flow
- 4.3 Change Order
- 4.4 Multiple Records
- 4.5 User Interface
- 4.6 Save Drafts
Chapter Five. Project Promotion
- 5.1 Business Values
- 5.2 Normal Cases
- 5.3 Boundaries
- 5.4 Exceptions
- 5.5 Risks
Chapter Six. Project Lucky Draw
- 6.1 Business Logic
- 6.2 Out Of Stock
- 6.3 UI Design
- 6.4 Peak Access
- 6.5 Security
- 6.6 Technical Requirements
Chapter Seven. Project Time Card
- 7.1 Set Up Personal Schedule
- 7.2 Rules And Validations
- 7.3 Read Data
- 7.4 Export
- 7.5 Statistics
- 7.6 Data Transfer
Chapter Eight. Project Online Nurse
- 8.1 Breakdown
- 8.2 MVP
- 8.3 Regulatory Compliance
- 8.4 Verification
- 8.5 Bill And Settlement
Chapter Nine. Non-Functional Requirements
- 9.1 Efficiency
- 9.2 Security
- 9.3 Compatibility
- 9.4 Fault Tolerance
- 9.5 Internationalization/Localization
- 9.6 Compliance
- 9.7 User Experience
Chapter Ten. Principles
- 10.1 Completeness
- 10.2 Correctness
- 10.3 Accuracy
- 10.4 Consistency
- 10.5 Flexibility
- 10.6 Decouple
- 10.7 Reusability
- 10.8 Multi-Perspective
- 10.9 Visualization
- 10.10 Focus On Values
- 10.11 Limited Reliability
- 10.12 Prepared
- 10.13 Murphy’s Law
Chapter Eleven. Summary
- 11.1 Analytical Tools
- 11.2 Structural Tools
- 11.3 Descriptive Tools
- 11.4 Descriptive Tools
- 11.5 Technical Tools
- 11.6 Management Tools
Chapter Twelve. Business Analysis In Agile
- Manifesto for Agile Software Development
- 12.1 User Story
- 12.2 Acceptance Criteria
- 12.3 User Story Mapping
- 12.4 Requirement Refinement
- 12.5 Requirement Exploration
- 12.6 Sprint Planning
Chapter Thirteen. Requirement Changes.
- 13.1 The Reality
- 13.2 Why Developers Resist Requirement Changes
- 13.3 Embrace Changes
- 13.4 Convince Developers
- 13.5 Requirement Change Management
Chapter Fourteen. Collaboration
- 14.1 Collaborate with Developers
- 14.2 Collaborate with Stakeholders
- 14.3 Collaborate with Product Owners