RESULT MONITORING SYSTEM USING SMS

BREDS GROUP

Software Requirements Specifications

PURPOSE

This is to give a detailed description of

the requirements for the “Result

Monitoring system using SMS” software.

PURPOSE

This document is primarily intended to

be proposed to the administrator for its

approval and a reference for developing

the system for the development team.

SCOPE

The software is mainly focused in

monitoring the result of each sports

category during the competition proper.

CONSTRAINTS

• Hardware specifications, budget

constraints, man power

• Mobile Signals

• Adding of Athletes, Coach, and

Referee

ASSUMPTION AND DEPENDENCIES

• Computer literate

• Finished the one day seminar

regarding “Proper Use of Result

Monitoring System using SMS”

ADMINISTRATOR

• Finished the one day seminar

regarding “Proper Use of Result

Monitoring System using SMS”

• Responsible enough in sending the

appropriate score with valid format

given

EVENT MANAGER

ASSUMPTION AND DEPENDENCIES

HARDWARE INTERFACE

•Windows 7 operating system

• At least dual core processor

• At least dual core processor

• Every mobile phone can be use

regardless of its version and with

operating system

SOFTWARE INTERFACES

• Microsoft Visual Studio 2010

• Microsoft Access 2010

• Any mobile phone regardless of its

specification and operating

system

SOFTWARE SYSTEM ATTRIBUTES

• Portable

• Reliable

• Secure

• Fast transmission

• Storage capable  

PRODUCT PERSPECTIVE

PRODUCT FUNCTION

FUNCTIONAL REQUIREMENTS

FUNCTIONAL REQUIREMENTS

FUNCTIONAL REQUIREMENTS

FUNCTIONAL REQUIREMENTS

SOFTWARE PROJECT MANAGEMENT PLAN

PURPOSE, SCOPE AND OBJECTIVES

This is to create a systematized

planning for the development of the

proposed software – organized a reliable

software that hopefully can bring it up

to the new system.

ASSUMPTION AND CONSTRAINTS

• Project Manager together with the

team will be responsible in every

matter discussed to them by their

adviser.

• The developers have their own

adviser

• the developers will submit all the

deliverables on time.

ASSUMPTION AND CONSTRAINTS

• Lack of resource like laptop and

internet connection.

• Source code

PROJECT ORGANIZATION

EXTERNAL INTERFACES

PROJECT ORGANIZATION

INTERNAL INTERFACES

MANAGERIAL PROCESS PLAN

This Software Project Management Plan

(SPMP) shall specify the cost and schedule for

conducting the project as well as methods,

tools, and techniques used to estimate

project cost, schedule, resource

requirements, and associated confidence

levels.

ESTIMATION PLAN

CONTROL PLAN

This section will specify the metrics,

reporting mechanisms, and control

procedures necessary to measure,

report, and control the product

requirements, the project schedule and

resources, and the quality of the work

processes and work products.

TECHNICAL PLAN

This Software Project Management Plan

(SPMP) shall specify the development

process model, the technical methods,

tools, and techniques to be used to

develop the various work products.

SOFTWARE DESIGNDESCRIPTION

PURPOSE

This document also serves as a system’s

reference manual for the running system

once it is implemented. The expected

audiences are the students, teachers and

Mrs. Janus A. Naparan.

MODULE DESCRIPTION

• Log-in Module Description - It uses the manual

way of inputting the username and password to

the computer.

• Data Entry Module Description - This module is

used in the software to input all the needed

information , only can be access by the registered

Administrator.

MODULE DESCRIPTION

• Receiving SMS Module Class Description -

This module is design for receiving SMS

from the registered event managers

• Generate Result Module Description –

It will generate the overall ranking of the

departments.

DECOMPOSITION DESCRIPTION

• Log-in Process Description

• Registration Process Description

• Data Entry Process Description

• Receive SMS Reports Process Description

• Generate Result Process Description

• Printing Process Description

DATA FLOW DIAGRAM

Sequence Diagram

Activity Diagram for the Administrator

Activity Diagram for the Event Manager

Entity Relationship Diagram

SOFTWARE TESTDESIGN

PURPOSE

The purpose of this Test Design

Specification document is to detail

improvements of the test approach

presented in the Test Plan for

interconnectivity testing of the

Result Monitoring System using

SMS.

OUTLINE

• FEATURES TO BE TESTED

• TEST IDENTIFICATION

• FEATURES

TEST CASE SPECIFICATION

THE PURPOSE OF THE TEST CASE

SPECIFICATION IS TO IDENTIFY THE

SOURCES USED IN THE SYSTEM IN ALL TEST

CONDUCTED AND WHETHER IT WILL BE

USEFUL IN THE SYSTEM.

OUTLINE

• TEST ITEMS

• INPUT SPECIFICATIONS

• OUTPUT SPECIFICATIONS

CASE 1: AUTHENTICATION PROCESS

CASE 2: AUTHENTICATION PROCESS

CASE 3: MENU BAR

CASE 4: DATA ENTRY

CASE 5: LOGS

CASE 6: DATA ENTRY

CODE FORMAT IN SENDING SCORES

CODE/GAMETYPE/SCORE/SCORE

CODE/TAF/1st/2nd/3rd

For Track and Field

GAME TYPE: TEAM/INDIVIDUAL

For Team and Individual

EX: B1/TEAM/95/89

EX: B2/TAF/CCS/CTEAS/CBE