This document outlines the requirements for a result monitoring system using SMS for tracking scores during sports competitions. It will allow administrators and event managers to input scores via SMS and generate overall rankings. The system will be developed using Microsoft Visual Studio and Access on Windows 7 computers. It will need to interface with various mobile phones for SMS input. Functional requirements, project management plans, module descriptions, data flow diagrams, and testing plans are provided to guide the development and testing of the software.

1. RESULT MONITORING
SYSTEM USING SMS
BREDS GROUP

2. Software Requirements
Specifications

3. PURPOSE
This is to give a detailed description of the
requirements for the “Result Monitoring
system using SMS” software.

4. 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.

5. SCOPE
The software is mainly focused in
monitoring the result of each sports
category during the competition proper.

6. CONSTRAINTS
• Hardware specifications, budget
constraints, man power
• Mobile Signals
• Adding of Athletes, Coach, and
Referee

7. ASSUMPTION AND DEPENDENCIES
• Computer literate
• Finished the one day seminar regarding
“Proper Use of Result Monitoring System
using SMS”
ADMINISTRATOR

8. • 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

9. 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

10. SOFTWARE INTERFACES
• Microsoft Visual Studio 2010
• Microsoft Access 2010
• Any mobile phone regardless of its
specification and operating system

11. SOFTWARE SYSTEM ATTRIBUTES
• Portable
• Reliable
• Secure
• Fast transmission
• Storage capable

12. PRODUCT PERSPECTIVE

13. PRODUCT FUNCTION

14. FUNCTIONAL REQUIREMENTS

15. FUNCTIONAL REQUIREMENTS

16. FUNCTIONAL REQUIREMENTS

17. FUNCTIONAL REQUIREMENTS

18. SOFTWARE PROJECT
MANAGEMENT PLAN

19. 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.

20. 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.

21. ASSUMPTION AND CONSTRAINTS
• Lack of resource like laptop and
internet connection.
• Source code

22. PROJECT ORGANIZATION
EXTERNAL
INTERFACES

23. PROJECT ORGANIZATION
INTERNAL
INTERFACES

24. 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

25. 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.

26. 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.

27. SOFTWARE DESIGN
DESCRIPTION

28. 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.

29. 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.

30. 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.

31. 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

32. DATA FLOW DIAGRAM

33. Sequence Diagram

34. Activity Diagram for the Administrator

35. Activity Diagram for the Event Manager

36. Entity Relationship Diagram

37. SOFTWARE TEST
DESIGN

38. 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.

39. OUTLINE
• FEATURES TO BE TESTED
• TEST IDENTIFICATION
• FEATURES

40. 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.

41. OUTLINE
• TEST ITEMS
• INPUT SPECIFICATIONS
• OUTPUT SPECIFICATIONS

42. CASE 1: AUTHENTICATION PROCESS

43. CASE 2: AUTHENTICATION PROCESS

44. CASE 3: MENU BAR

45. CASE 4: DATA ENTRY

46. CASE 5: LOGS

47. CASE 6: DATA ENTRY

48. 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