1. Demand research
After obtaining the customer's project requirements, first conduct project requirements research, investigating the project's business requirements, user requirements, system requirements, performance requirements, non-functional requirements, constraints and restrictions, demand priorities, etc., as follows:
- Business Requirements: Understanding the customer's business goals and strategies is the basis of software development and can help determine the main functions and characteristics of the software.
- User needs: clarify who the software is and understand their needs and habits, which has an important impact on determining the software's operating interface, functional processes, etc.
- System requirements: Analyze the system's due functions and the detailed requirements of each function.
- Performance requirements: Evaluate the performance standards that the software should have, such as response time, processing speed, stability, etc.
- Non-functional requirements: such as the ease of use, maintainability, security of the software, etc. Although these requirements are not functional requirements, they have an important impact on the satisfaction and success of the software.
- Constraints and limitations: clarify the constraints for software development and implementation, such as technical limitations, budget limitations, etc.
- Requirement priority: determine the priority of requirements so that resources and time can be arranged reasonably during the development process.
1. Methods of demand research
- Questionnaire: By designing a questionnaire, data is distributed to target groups and collected to understand their needs and opinions. This method has a wide coverage and is suitable for large-scale research.
- One-to-one interview: Engage in-depth communication with target users to understand their needs, expectations and pain points. This method allows for more specific and personalized information.
- Focus Group Discussion: Convene a group of target users and guide them to the discussion to understand their needs and opinions. This method allows users to observe interactions and collisions of opinions.
- Competitive product analysis: Through research and analysis of similar products or services on the market, we can understand their functions, characteristics, advantages and disadvantages, etc., so as to tap potential needs and opportunities.
- Expert review: Invite industry experts or senior practitioners to evaluate and recommend the needs of products or services. This method can gain professional and in-depth views.
- User log or usage record: Analyze their behavior and needs by recording data or logs generated by users during actual use.
- Stakeholder Interview: In-depth communication with stakeholders related to a product or service to understand their expectations, concerns and suggestions for a product or service.
- Interview: Interview users face to face or phone to gain insight into their needs and expectations, as well as their perceptions of software features and interfaces.
- Field observation: Go deep into the actual work scenarios of users, observe their workflow and existing problems, so as to understand user needs more accurately.
- Document analysis: Check and analyze the business information provided by users to understand the user's business needs and system requirements.
- Prototype evaluation: Based on the preliminary demand analysis results, a software prototype is created to allow users to conduct trial and evaluation, and further understand and optimize software requirements based on user feedback.
2. Requirement research case analysis
2.1 Project background
The virtual simulation training teaching management and resource sharing platform is used to coordinate the management of virtual simulation training teaching venues, virtual simulation training facilities and equipment, and virtual simulation training resources across majors, schools and regions. It should have functions such as monitoring and analysis of the virtual simulation training teaching process and management and statistics of the aggregation and allocation of virtual simulation training resources, and is used in dual-level colleges and universities. During the system use, all data can only be modified when the user logs in.
2.2 Demand Research
2.2.1 Business demand survey
- Objective: Understand the business goals and strategies of dual-high schools in virtual simulation training.
- Methods: In-depth interviews with the school leaders, Academic Affairs Office, Training Center and other departments.
- Key questions:
What are the specific goals of your school in virtual simulation training?
What are the current virtual simulation training projects? What are the plans for the future?
What core functions do you think the platform should have to support the school’s business goals?
2.2.2 User demand survey
- Objective: Definite the user groups and their needs of using the platform.
- Methods: Questionnaire surveys and interviews were conducted on different roles such as teachers, students, and administrators.
- Key questions:
How often do you use virtual simulation training?
What are the main problems you encounter during use?
What improvements do you want the platform to make in terms of interface, operational processes, etc.?
2.2.3 System requirements survey
- Objective: Clarify the functions and detailed requirements of the system.
- Method: Analyze the functions of the existing system and discuss future needs with users.
- Key questions:
What core functions do you think the platform should have?
What are your specific needs for monitoring and analysis functions?
In terms of resource aggregation and allocation, how do you want to manage and count?
2.2.4 Performance requirements survey
- Objective: Understand users' expectations for system response time, processing speed, etc.
- Method: Collect performance data through testing and user feedback.
- Key questions:
What are your expectations for the platform’s response speed?
What do you want the platform to perform in high load situations?
2.2.5 Non-functional requirements survey
- Objective: Understand users' expectations for the ease of use, security and other aspects of the platform.
- Methods: Collect user opinions through questionnaires and interviews.
- Key questions:
How do you think the platform is ease of use? What are the improvements?
What are your expectations or concerns about the security of the platform?
2.2.6 Constraint and restriction research
- Objective: Understand the constraints on technology, budget, etc.
- Method: Communicate with technical departments, financial departments, etc.
- Key questions:
What are the technical limitations of your school? likesoftwareEnvironment, hardware requirements, etc.
What is the budget scope for your proofreading platform construction? What are the additional cost considerations?
2.2.7 Requirement priority survey
- Objective: Prioritize each requirement.
- Methods: Based on the above research results, we discussed with key stakeholders to determine.
2.2.8 Data securityResearch with privacy protection
- Objective: Clarify data modification permissions and data security protection measures.
- Methods: Discuss data security strategies with legal departments and technical teams.
- Competitive product analysis: Understand other similar virtual simulation training and resource sharing platforms on the market, analyze their advantages and disadvantages, so as to better position their products.