System Requirements Specification Project Odin

Kyle Erwin Joshua Cilliers Jason van Hattum Dimpho Mahoko Keegan Ferrett Note: This document is constantly under revision due to our chosen methodology, and is subject to change.

Current version: v0.1

Contents

Contents Introduction . . . . . . Overall Description . Specific Requirements Appendices . . . . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

1 3 5 7

Introduction This section describes the scope of Project Odin, as well as an overview of the contents of the SRS document. Additionally, the purpose of the document is defined as well as a list of abbreviations and definitions.

Purpose The purpose of this document is to provide a thorough description of the requirements for Project Odin. The requirements, constraints, interfaces and interactions with other systems will be described in this document. This document is intended as a point of reference for the client, as well as a means of keeping track of our decisions and the project for us as the development team.

Scope "Project Odin" is a tool for generating computational models via a simple drag-and-drop interface. The idea is that an average user with little to no programming experience will be able to build highly complex models, for a range of tasks such as machine learning, statistical analysis or image manipulation. Users will also be able to create projects which will each contain a computational model, which will then be able to be used as a component in another persons model. In this way, large, complex models can be built up from components which consist of models themselves. Project authors will be able to share their projects, including a description, and be able to view the usages and popularity of their components.

Definitions, Acronyms and Abbreviations • User - A user that is using the application. • Model - A computational model built in the application. • Project - A computational model that has been shared.

References Empty for now. 1

Overview This document includes 4 sections: 1. Introduction 2. Overall Description 3. Specific Requirements 4. Appendices The sections are laid out as follows: Section 2 - Overall Description Section 2 provides an overview of the systems functionality and it’s interaction with other systems. This chapter also outlines the users of the system and their interaction with it. Finally, the constraints and assumptions are defined. Section 3 - Specific Requirements Section 3 starts off by outlining the specific requirements for each external interface, followed by a description of the function requirements. This is followed by the performance requirements and design constraints. Section 3 then describes the attributes or non-functional requirements of the system, including it’s reliability, security, availability and interoperability. Finally, any other requirements not under the preceding categories are listed. Appendices The appendices are empty for now.

2

Overall Description This section will provide an overview of the systems functionality and it’s interaction with other systems. This chapter will also outline the users of the system and their interaction, as well as the development constraints and assumptions made.

Product Perspective Empty for now. System Interfaces Empty for now. User Interfaces Will be expanded upon The user interface primarily makes use of a drag-and-drop component based system. Each component acts as a function which can be made up of further components. Users add components in to a workspace where they can add links between components by dragging from one component’s input or output nodes to those of another component. The navbars and other sections of the interface are all stylized with Materialize, so as to have a unified theme and styling. These navbars will contain the functionality needed to handle the management of the components created using the system. This part of the interface will be expanded upon further into the project. Hardware Interfaces Empty for now. Software Interfaces Empty for now. Communications Interfaces Empty for now. 3

Memory Interfaces Empty for now. Operations Interfaces Empty for now. Site Adaptation Requirements Empty for now.

Product Functions Empty for now.

User Characteristics Empty for now.

Constraints Empty for now.

Assumptions and Dependencies Empty for now.

4

Specific Requirements This section starts off by outlining the specific requirements for each external interface, followed by a description of the function requirements. It then continues with the performance requirements and design constraints, as well as the the attributes or non-functional requirements of the system. Finally, any other requirements not under the preceding categories are listed.

External Interface Requirements Functional Requirements Empty for now.

Performance Requirements Will be expanded upon.

User Interface • The drag-and-drop system needs to render as quickly as possible, preferably in under 3 seconds. • The drag-and-drop system needs to avoid producing input lag by being too heavy on system resources.

Design Constraints Empty for now.

Software System Attributes Empty for now. Reliability Empty for now. 5

Security Empty for now. Availability Empty for now. Interoperability Empty for now.

Other Requirements Empty for now.

6

Appendices Empty for now.

7

8

9

System Requirements Specification - GitHub

System Requirements Specification. Project Odin. Kyle Erwin. Joshua Cilliers. Jason van Hattum. Dimpho Mahoko. Keegan Ferrett. Note: This document is constantly under revision due to our chosen methodology, ... This section describes the scope of Project Odin, as well as an overview of the contents of the SRS doc-.

96KB Sizes 0 Downloads 110 Views

Recommend Documents

Modern Requirements Specification
However, trends in system development have made the numerous problems ... not only enabled better requirements management; they have also enabled the ..... requirements methods, and better-standardized content for our requirements.

Orc Protocol Specification - GitHub
Aug 15, 2017 - This specification documents the Orc network protocol in its entirety for the purpose of enabling .... services and authentication is performed by the nature of Tor's routing. Each Orc node ... associated with held contracts (5. Data T

Specification on Image Data File Version - GitHub
5.4.10 ShootingRecord heap ... the JFIF file format[1], as described below), sample software shall be provided openly to player vendors. ... In the separate "Decisions Concerning Extension" section, we define how various companies.

LERUKA LERUKA UseCase Specification: View public ... - GitHub
UseCase Name. Brief Description. Mockup. Flow of Events. Basic Flow. Narration. Alternative Flows. Special Requirements. Preconditions. Postconditions.

Hypervisor Top Level Functional Specification - GitHub
100. HvSendSyntheticClusterIpiEx . ...... That is, the hypervisor is free to deliver the interrupt ..... When a message is sent, the hypervisor selects a free message buffer. ...... The Flags field included an invalid mask value in the proximity doma

Anonymous Go-Kart: Specification Report Supervisor - GitHub
May 9, 2011 - [email protected] (83238549). Wim Looman ... Department of Computer and Electrical Engineering. University of ... kart, so that it can be easily controlled by a laptop. The second is to ..... BostonDynamicsTRQ6Sep09.pdf.

HELM Web-based Editor Requirements Specification V1_0.pdf ...
HELM Web-based Editor Requirements Specification V1_0.pdf. HELM Web-based Editor Requirements Specification V1_0.pdf. Open. Extract. Open with.

Software Requirements Specification versi 2.pdf
There was a problem loading this page. Retrying... Whoops! There was a problem previewing this document. Retrying... Download. Connect more apps... Try one of the apps below to open or edit this item. Main menu. Whoops! There was a problem previewing

HELM Web-based Editor Requirements Specification V1_0.pdf ...
3.1 Web-Editor Functional Requirements. ... 3.2 Non-Functional requirements . ... Page 3 of 15. HELM Web-based Editor Requirements Specification V1_0.pdf.

CBIR System - GitHub
Final result was a Matlab built software application, with an image database, that utilized ... The main idea is to integrate the strengths of content- and keyword-based image ..... In the following we present some of the best search results.