Software Requirements

Specification for “GAME” And

NFTy Arcade

PREPARED FOR
NFTy Arcade

PREPARED BY
Collin Snyder
1 - Introduction

Software Requirements Specification for “GAME” And NFTy Arcade 1

1 - Introduction 2
1.1 - Purpose 3
1.2 - Scope 3

2 - Specific Requirements 5
2.1 - Database 5
2.1.2 Frequency of Use 5
2.1.3 Accessing Capabilities 5
2.1.4 Data Entities and Their Relationships (EXAMPLE) 5
2.1.5 Integrity Constraints 6
2.1.6 Data Retention Requirements 6
2.2 - Functions 6
2.2.1 Users and Developers 6
2.2.1.1 Function Name 6
2.2.1.2 Function Name 6
2.3 Usability Requirements 7
2.4 Performance Requirements 7
2.4.1 Requirement Name 7
2.5 Design Constraints 7
2.5.1 Design Constraint 7
2.5.2 Design Constraint 7

3 - Verification 7
3.2.2.1 Function Name Verification (how do you know the function worked?) 7
3.2.1.2 Allow User Sign up 7

4 - Appendices 8
4.1 Assumptions and Dependencies 8
1.1 - Purpose
This document is written to convey information pertaining to “GAME”, [overview of the game for
deployment]. (Example: a project collaboration system that brings new ideas to life.)

This document contains the criteria that shall need to be met in order for this system to be considered
complete and successful.

The current requirements given by the client suggest [fill in requirements]

1.2 - Scope
[overview of the project]

In Scope
●

Out of Scope / Future Wants

●

1.3 - Product Overview

1.3.1 Product Perspective
[what separates this from other “GAMEs”]

1.3.2 Product Function

[enter description]

[possible diagram for flow of communication]

1.4 - Definitions

Term Definition

Database Collection of all the information monitored by this system.

Developer A person or thing that helps in the creation of projects and ideas
from the Acorn Nursery platform

Project A users or thought idea for development

Software A document that completely describes all of the functions of a proposed

Requirements system and the constraints under which it must operate.
Specification

User Someone visiting the site to build or post a software idea.

2 - Specific Requirements

2.1 - Database
[how is the database to be used]

2.1.1 Types of Information

[data types of information to be stored]

2.1.2 Frequency of Use

[how often will it be used with the software]

2.1.3 Accessing Capabilities

[who/how can it be accessed]

2.1.4 Data Entities and Their Relationships (EXAMPLE)

The following tables shall be created to store data. Relationships in the data shall be made with a
PRIMARY KEY and FOREIGN KEY.
● Users Table
● Projects Table
● Projects_Catagories Table
● Roles Table
● Categories Table
● Features Table
2.1.5 Integrity Constraints
[security]

2.1.6 Data Retention Requirements

[fail safe]

2.2 - Functions

2.2.1 Users and Developers

2.2.1.1 Function Name

[description]

2.2.1.2 Function Name

[description]

2.2.1.3 Function Name

[description]

2.2.1.4 Function Name

[description]
2.3 Usability Requirements
● [use cases for the project]

2.4 Performance Requirements

2.4.1 Requirement Name

[description for requirement]

2.5 Design Constraints

2.5.1 Design Constraint
Example: The software shall be compatible with the following current versions of operating
systems:
● Microsoft Windows
● Apple macOS
● Linux
● Android
● Apple's iOS

2.5.2 Design Constraint

●

3 - Verification
3.2.2.1 Function Name Verification (how do you know the function worked?)
[description]

3.2.1.2 Allow User Sign up

[description]

3.2.1.3 View Sponsored Projects

[description]

3.2.1.4 Sponsor a Project

[description]

4 - Appendices

4.1 Assumptions and Dependencies

● The user understands how to operate basic functionality of electronics.
● The user owns a device capable of accessing the web.