Skip to content

Requirements Analysis Document (WIP)

Ian Pike edited this page May 28, 2022 · 1 revision

Software Requirements

Project Name: Dragon Archiver

Company: WizWorks Inc

Created By: Ian Pike and WizWorks Team

1. Introduction

1.1 Purpose

The aim of Dragon Archiver is to create a robust world creation tool that provides high levels of customization and freedom to the user while keeping the overall experience as simple and to the point as possible. The goal is to try and build a program that is agnostic to outside systems while open to changing to custom tabletop games such as Dungeons & Dragons.

1.2 Intended Audience

The primary end-user is people who want to build a custom world or better track information on people and places in a simple and concise manner. Along with having easy and quick to access information on stored data that is easily understandable and relays the overarching information in a meaningful visual way.

1.3 Intended Use

World design, story writing, relational note-taking, note tracking.

1.4 Scope

Our primary goal is to build a system that can:

  1. Keep track of NPCs and players and store information on them in a dynamic manner
  2. Track locations and locations inside of those locations
  3. Allow fast navigation through data and how it relates to other sections of data.

1.5 Definitions and Acronyms

Provide definitions the reader should understand before reading on.

2. Overall Description

Describe what you are building and for who.

2.1 User Needs

Explain why the user needs this software.

2.2 Assumptions and Dependencies

What assumptions are you making that could cause an error? 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

Define the functional requirements that are essential for the software.

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 work?

3.4 Nonfunctional Requirements

Are there any non-functional requirements that you need to address (i.e. budget, team, etc.)