The specifications (or specs) are components of a document from which a developer can develop the system. It should be complete enough that it could be used as a bid request out to a third party.
In general, the system specifications will be developed from discussions with your client.
The specifications include:
- user stories
- requirements (functional, non-functional, interfaces, other)
User Stories
As a student, I want a central menu on the screen in order to see my tasks and be able to navigate easily within the app.
As a student, I want to unlock new modules as I complete different cyberbulling awareness tasks so that I can see my progress.
As a student, I want to be able to customize my avatar and have it displayed in my menu. This requires the development of an avatar customization system.
As a student, I want to be able to navigate to Cyberland from the homepage so that I can see the development of my city.
Requirements
Functional
Definite
- Users must be able to see all the widgets containing the tasks that they have unlocked
- Users must be able to open each task widget to view all lesson material
Perhaps
- Users must be able to access the files and videos from completed lesson materials in a separate location of the mobile app
Improbable
- Users must be able to navigate Cyberland map
- Users see updates on Cyberland map as they complete tasks
Non-Functional
Definite
- The mobile app has a simple interface that everyone can navigate
- Users should be able to easily access files from completed lessons
Perhaps
- Users have an avatar they can customize
Improbable
- The mobile app has an interactive map of Cyberland