Software Requirements
Software requirements documents provide an important map of the product being built, the features that will be included and much more.
This roadmap helps to keep the technical and non-technical team on the same wavelength as to what the expectations are. It helps to ensure that the product is built meeting the needs whether it’s for internal purposes, for users or clients. 1
1. Introduction
1.1 Purpose: Set the expectations for the outcome of the product.
1.2 Intended Audience: Who is the software for? Who is the end-user? Will the software be used internally at a company or externally?
1.3 Intended Use: What is the software for? What problem is it solving?
This application should be serving several roles:
-
teaching tool for people interested in creating a complex distributed app with Strapi
-
model to help Strapi core team to test and verify the new plugins (Identity Management being one of them - but not the only one)
1.4 Scope: Explain the scope of the software. What are the main goals and objectives? How do they relate to the company’s goals?
1.5 Definitions and Acronyms: Provide an overview of any definitions the reader should understand before reading on.
2. Overall Description: Describe what you are building and for who.
2.1 User Needs: Explain the user needs for this software.
2.2 Assumptions and Dependencies: What assumptions are you making that could cause an error in your approach? Is the project reliant on any other factors that could affect the development of the software?
3. System Features and Requirements
3.1 Functional Requirements: Take time to define the functional requirements that are essential for the software to build.
3.2 External Interface Requirements: Are there any UX and UI requirements that you must keep in mind as you build?
3.3 System Features: What features are required for the software to even work.
3.4 Nonfunctional Requirements: Are there any non-functional requirements that you need to address (i.e. budget, team, etc.)