Competitive Algorithm Calculation Testing in a Unified System (C.A.C.T.U.S.) Requirements Specification 11/2/2011 Presented By: ExoNET Solutions 1.

Competitive Algorithm Calculation Testing in a

Unified System

(C.A.C.T.U.S.)

Requirements Specification

11/2/2011

Presented By:ExoNET

Solutions

1

Welcome

Dr. Darren LimAssociate Professor of

Computer ScienceSiena College

2ExoNET Solutions - Requirements Specification

Agenda Introductions Problem Overview Project Status User Case Narratives UML Use Case Diagrams Data Flow Diagrams Functional and Non-Functional Requirements

Timeline What is next for ExoNET?


ExoNET SolutionsTeam Members

David PurcellTeam Leader

Stephanie Del Belso

Documents Analyst

Thomas DelaneySystems

Administrator

Marco SamaritoniWeb Master

Paul AmodeoAssistant Web

Master





Problem Overview

Current contest system is loosely structured

Inconvenient for judges and contestants

Not easily maintained

Not fully automated





Project Status

Development and

Testing

Requirements Specification





User Case Narratives

Describe the behavior of users within a system.

Aid in the discovery of requirements


User Case Narrative: System Administrator

Logs in/Logs out of C.A.C.T.U.S.Has highest level privilegesConfigures contest environmentCreates user accounts for a contest


User Case Narrative: Judge

Logs in/Logs out of C.A.C.T.U.S.Is given teams to superviseCommunicates with teamsReviews problem submissions


User Case Narrative: Contestant

Logs in/Logs out of C.A.C.T.U.S.

Familiarizes with C.A.C.T.U.S. interface

Submits problem submissions


User Case Narrative: Spectator

Logs in/Logs out of C.A.C.T.U.S.

Views scoreboard

Views contest problems





UML Use Case Diagrams

Visual representation of user behavior

Overview of User Case Narratives


UML Use Case Diagram Legend

System Boundary

Actor (Human or Non-Human)

Use Case

Participations


UML Use Case Diagram: C.A.C.T.U.S.

UML Diagram ExoNET

System Administrator

Judge

Contestant

Spectator

DatabaseManagement System

Authenticate

passwordusername

<<include>><<include>>

Configure

Upload

<<include>>

ProblemSolutionsTest Cases

ContestProblems

Select languages<<include>>

Start/stoptime

<<include>>

Add/dropteams

View

BroadcastMessage

ChatWindow

<<include>>

Useraccounts

Java

<<include>>

Scoreboard

ProcessSubmissions

Contestproblems

<<include>><<include>><<include>>

C.A.C.T.U.S Competitive Algorithm Calculations Testing in a Unified System

Compiler

ApacheServer





Data Flow Diagrams

Visual representation of data flowSystem components are drawn at various

levels of detailContext Diagram – Highest level of abstraction

and external usersLevel 0 Diagram – Major processes and dataLevel 1 Diagrams – More detailed view of a

process


Data Flow Diagrams Legend

Data Source/SinkProcess

Data StoreData Flow


Data Flow Diagram: Context Diagram


Data Flow Diagram: Level 0 Diagram


Data Flow Diagram: Process 2 (Log In), Level 1





Functional Requirements Inventory:C.A.C.T.U.S.

ResponsiveScalableRobustUsable in multiple Web BrowsersRun programming contests


Functional Requirements Inventory:System Administrator

Upload contest problemsAdd/Drop ContestantsCreate user accountsSelect contest languages


Functional Requirements Inventory:Judge

Process problem submissions from Contestants

Communicate with Contestants


Functional Requirements Inventory:Contestant

View contest problemsView scoreboardCommunicate with JudgesSubmit problem submissions


Functional Requirements Inventory:Spectator

View contest problems

View scoreboard


Non-Functional Requirements

User friendly

Stable





Timeline





What is next for ExoNET?

Preliminary Design – November 3rd – December 6th

Preliminary Design Delivered – December 6th, 2011

Preliminary Design Presentation – December 7th, 2011


Thank You.

Questions? Comments?


Competitive Algorithm Calculation Testing in a Unified System (C.A.C.T.U.S.) Requirements Specification 11/2/2011 Presented By: ExoNET Solutions 1.

Documents

discovery of requirements

user accounts

project status development

spectator logs inlogs

judge logs inlogs

contestant logs inlogs

contest environment

unified system