MindMap Gallery Requirements analysis steps
This is a mind map about the steps of demand analysis. It tells the story about the steps of demand analysis. If you are interested in the story of the steps of demand analysis, you are welcome to collect and like this mind map~
Edited at 2023-06-30 01:16:55Avatar 3 centers on the Sully family, showcasing the internal rift caused by the sacrifice of their eldest son, and their alliance with other tribes on Pandora against the external conflict of the Ashbringers, who adhere to the philosophy of fire and are allied with humans. It explores the grand themes of family, faith, and survival.
This article discusses the Easter eggs and homages in Zootopia 2 that you may have discovered. The main content includes: character and archetype Easter eggs, cinematic universe crossover Easter eggs, animal ecology and behavior references, symbol and metaphor Easter eggs, social satire and brand allusions, and emotional storylines and sequel foreshadowing.
[Zootopia Character Relationship Chart] The idealistic rabbit police officer Judy and the cynical fox conman Nick form a charmingly contrasting duo, rising from street hustlers to become Zootopia police officers!
Avatar 3 centers on the Sully family, showcasing the internal rift caused by the sacrifice of their eldest son, and their alliance with other tribes on Pandora against the external conflict of the Ashbringers, who adhere to the philosophy of fire and are allied with humans. It explores the grand themes of family, faith, and survival.
This article discusses the Easter eggs and homages in Zootopia 2 that you may have discovered. The main content includes: character and archetype Easter eggs, cinematic universe crossover Easter eggs, animal ecology and behavior references, symbol and metaphor Easter eggs, social satire and brand allusions, and emotional storylines and sequel foreshadowing.
[Zootopia Character Relationship Chart] The idealistic rabbit police officer Judy and the cynical fox conman Nick form a charmingly contrasting duo, rising from street hustlers to become Zootopia police officers!
Requirements analysis steps
Understand the background information and goal setting of the project, including the background of the project, target audience, budget, time, etc.
Understand the historical background and background information of the project, including the origin of the project, goal setting, early success or failure experience, etc.
Determine the project's target audience, including the project's end users, key stakeholders, and other interested parties
Define the project's budget scope, including the funds, resources, and other constraints available to the project
Determine the project's timeline, including project start and end times, milestones, and key delivery times.
Collect user needs
Collect user needs, including using various methods and tools to obtain information about user needs
Conduct user interviews to communicate directly with users, ask questions, and explore their needs and expectations
Conduct questionnaire surveys to collect users’ opinions and suggestions through questionnaires to understand their needs and preferences
Analyze market research data, study competitors' products, and understand user needs and trends
Conduct user observation to directly observe users’ behaviors and reactions in specific environments to understand their needs and problems
Conduct user case analysis to study users' usage scenarios and workflows to understand their needs and challenges.
Analyze requirements
Organize, classify and analyze the collected user needs to ensure an accurate understanding of the real needs of users
Collate all collected user requirements and classify them into functional requirements, non-functional requirements and constrained requirements
Carry out demand decomposition, subdivide and dismantle large demands to form a more specific demand description.
Prioritize needs to determine which needs are the most important and urgent
Evaluate and verify each requirement to ensure its feasibility and achievability
Discuss and confirm requirements with the project team and key stakeholders to ensure that both parties have a consistent understanding.
Write requirements document
Organize and write the analyzed requirements into requirements documents to facilitate subsequent development, testing and maintenance work
Based on the analyzed requirements, write detailed requirements descriptions, including functional requirements, non-functional requirements and constraint requirements.
Use consistent templates and formats to ensure a consistent style and structure of documents
Ensure requirements documents include sufficient context and examples to help developers and testers understand the requirements
Review and validate requirements documents with the project team and key stakeholders to ensure they are accurate and complete.
Confirm requirements
Work with users and project teams to validate requirements and ensure they are accurate and comprehensive
Requirements validation with users, including discussing and validating requirements with them to ensure they meet user expectations
Confirm requirements with the project team, including discussing and validating requirements with developers, testers and other relevant personnel to ensure their achievability and testability
Carry out requirements tracking and management, record changes and evolution of requirements, and ensure they are consistent with previous versions.
Check requirements
Check and validate requirements to ensure accuracy, consistency and traceability
Use a checklist or checklist to check and verify each requirement to ensure it meets relevant quality requirements
Conduct consistency checks on requirements to ensure there are no conflicts or contradictions between requirements
Ensure the traceability of requirements, that is, the requirements can be interconnected with test cases, design documents and other related documents.