-
Notifications
You must be signed in to change notification settings - Fork 0
Assignment #2: Requirements Elicitation Questions for a Community Information Management System
Burak Cosar edited this page Mar 23, 2024
·
10 revisions
For my project, I am planning to develop an information management system specifically designed for the Sports Communities, and this questions are prepared to elicit information about Ultimate Frisbee community. In my project, I aim to create a system that meets the needs of players, teams, and organizers effectively.
I will divide question sets into two categories, namely:
- Technical Requirements (Functional & Non-Functional)
- Domain Specific Needs, Regulations and Requirements
- What are the primary architectural concerns for this system? (e.g., scalability, maintainability, extensibility)
- Are there any specific architectural patterns or frameworks you recommend or prefer for this project?
- Are there preferences or requirements for programming languages, databases, or other technologies?
- What are the considerations for deployment environments? (cloud services, on-premises, hybrid solutions)
- What development methodologies do you prefer or suggest for this project? (Agile, Waterfall, etc.)
- How should the system handle data consistency and integrity, especially considering distributed or offline access scenarios?
- What are the API requirements for the system, both for internal use and potential external integrations?
- How do we plan to ensure data exchange with other community management tools or platforms?
- What security frameworks or standards should the system adhere to? (OWASP, GDPR compliance, etc.)
- How should the system manage user authentication and authorization, especially for different roles within the community?
- Are there specific data encryption, storage, or transmission security measures we need to implement?
- What are the expected performance benchmarks for the system? (response times, concurrent users, etc.)
- How will the system scale to accommodate growth in the Ultimate Frisbee community or an increase in user activity?
- Are there any anticipated peak usage periods (e.g., during major tournaments), and how should the system prepare for these?
- What testing strategies and tools do you recommend for ensuring the quality and reliability of the system?
- How will we incorporate user feedback into the development cycle for continuous improvement?
- Are there specific performance or load testing benchmarks we should aim to meet before launch?
- What are the anticipated maintenance challenges, and how can we proactively address them?
- How will we manage versioning, updates, and patches for the system?
- Can you describe the typical structure of Ultimate Frisbee events and tournaments?
- What are the common communication channels used within the Ultimate Frisbee community?
- How do players and teams currently track performance and statistics?
- Are there specific roles within teams or the community (e.g., captains, coaches, league organizers) that the system should accommodate with tailored functionalities?
- What challenges have you faced with existing systems or processes for managing Ultimate Frisbee activities?
- Are there any governing bodies for Ultimate Frisbee that set rules or standards we should be aware of?
- Do these bodies have specific requirements or guidelines for the organization of tournaments, player registration, or data management that we need to comply with?
- Are there safety protocols or guidelines that need to be communicated and enforced through the system?
- Are there inclusion and diversity initiatives within the Ultimate Frisbee community that the system should support or promote?
- How does the community handle conflict resolution or disputes, and is there a need for the system to support these processes?
- Are there specific recognition or reward systems for players, teams, or volunteers that we should incorporate?