Docstoc

srs-final

Document Sample
srs-final Powered By Docstoc
					       The Statcard System

Software Requirements Specification

          Andrew Perhac

       Advisor: Dr. Sidbury

        November 14, 2002

  Submitted in partial fulfillment
     Of the requirements of
  CMPS 490-Computer Projects
                                                                                                                                         i


                                                      Table of Contents

1. Introduction .................................................................................................................... 1

1.1. Purpose........................................................................................................................ 1

1.2. Scope of Project .......................................................................................................... 1

1.3. Glossary ...................................................................................................................... 2

1.4. References ................................................................................................................... 3

1.5. Overview of Document ............................................................................................... 4

2. Overall Description ........................................................................................................ 6

2.1. System Environment ................................................................................................... 6

2.2. Functional Requirements Definition ........................................................................... 7

2.3. User Interface Specification ...................................................................................... 17

2.4. Non-Functional Requirements .................................................................................. 17

2.5. System Evolution ...................................................................................................... 18

3. Requirements Specification ......................................................................................... 19

3.1. External Interface Requirements............................................................................... 19

3.2. Functional Requirements .......................................................................................... 19

3.3. Detailed Non-Functional Requirements ................................................................... 24

Index ................................................................................................................................. 25
4/9/2011                           The Statcard System                                     1


1. Introduction

1.1. Purpose

   The purpose of this document is too provide a concise overall description of the

functionality and anticipated constraints of The Statcard System, developed for my senior

Computer Projects course at the University of Scranton in Pennsylvania. This document

will discuss the scope of the project at hand and will further specify the chosen system

environment as well as the anticipated user interfaces for the system. Additionally,

special considerations regarding the potential evolution of the system as well as both

functional and non-functional requirements will be identified and discussed.

   The expected audience of this document will be baseball coaches, players and fans. It

is also expected that this document will serve as a viable reference for the software

engineers and computer system specialists that are further improving and evolving The

Statcard System at the University of Scranton in Pennsylvania.



1.2. Scope of Project

       The scope of the project can be defined in terms of the documentation and

development of the Statcard System for my senior Computer Projects course at the

University of Scranton in Pennsylvania. The development of this system, The Statcard

System, encompasses using highly compatible software within the appropriate hardware

limitations. The main purpose of this system is to take a standard baseball scorecard and

create both a boxscore and season statistics output from it. The scorecard will be shown

and interacted with, in a digital format on the computer screen. Once finished the

boxscore and season statistics will be created by the system. These two outputs will be
4/9/2011                            The Statcard System                                      2


able to be saved, printed, or sent to a web page. Currently, baseball participants have no

efficient protocol for creating a box score and season statistics from a scorecard. With

more baseball coaches opting to neglect standard scoring and statistical creation

procedures, players are less likely to understand their strengths and weaknesses according

to their statistics. For those baseball coaches who do take the time to take appropriate

scoring and statistics from their baseball games, they lose about 2 hours approximately

after each game, manually creating box scores and statistics from a hand printed baseball

scorecard. The Statcard System will be responsible for the efficient collection of

statistics through the use of an electronic scorecard. This embodies the overall strategic

objectives of creating an efficient resource for baseball enthusiasts.

In addition, this system will improve a coach’s role in teaching players by giving

appropriate information on player’s statistical problems with the game of baseball. The

Statcard System will enhance the overall productivity of any baseball enthusiast.


1.3. Glossary

Terms                       Definitions
Baseball Enthusiasts        Baseball players, baseball coaches and baseball fans.
Baseball Participants       See also Baseball Enthusiasts
Boxscore                    A printed score of a baseball game giving the names and positions
                            of the players and a record of the play arranged in tabular form
Constraints                 The state of being checked, restricted, or compelled to avoid or
                            perform some action
Database                    One or more large structured sets of persistent data, usually
                            associated with software to update and query the data
Drop-Down List              A menu on a form that is used to enhance user interface by having
                            only a select number of choices allowed to be picked by the system
                            user
Electronic Scorecard        A digital template for scoring baseball games
Evolution                   The continuous furthering of a computer program through time by
                            the use of adding functionality, features and documentation while
                            deleting bugs and errors.
Execution                   The process of carrying out the instructions in a computer program
4/9/2011                          The Statcard System                                    3


                           by a computer.
File Lifetime              The time from which a file is allocated for in memory or created,
                           until the time from which a file is deallocated in memory or
                           destroyed.
Form                       Documented page where one plugs in input
Form Button                Button on a form to initialize an action
One-click Process          The automation of doing many processes within a computer
                           program using a single mouse click of the program’s user.
Scope                      The range of program or product operation
Season Statistics          A set of variables and calculations that reflect upon real life
                           situations gathered throughout an official season of the given sport.
Single-user System         A system that has only one logical user or a set of users, which have
                           the same functionality within the group, or set.
Software Package           A coherent set of software programs packaged together to be
                           installed as a single product at the same time.
Standard Baseball          A hard-copy form used for scoring baseball games.
Scorecard
Statcard System            A system that takes a digital electronic scorecard modeled from a
                           standard baseball scorecard and creates both a boxscore and updates
                           season statistics from it.
Traverse                   Processing nodes in a table or graph one at a time, usually in some
                           specified order.
Upload                     To transfer programs or data over a digital communications link
                           from a smaller or peripheral "client" system to a larger or central
                           "host" one.
User Interface             The aspects of a computer system or program which can be seen (or
                           heard or otherwise perceived) by the human user, and the
                           commands and mechanisms the user uses to control its operation
                           and input data


1.4. References

Perhac Andrew. “Software Design Description: Statcard System.” November 14, 2002.

Perhac Andrew. “Test Design Document: Statcard System.” November 14, 2002.

Perhac Andrew. “User Manual: The Statcard System.” November 14, 2002.

Martin, Dennis S. "General Format for Reports: Fall 2001 Edition." Computing

         Sciences, University of Scranton, November 14, 2002.

         <http://www.cs.scranton.edu/~dmartin/dsgenfor.htm>.

Martin, Dennis S. “Software Requirements Specification: Fall 2001 Edition." Computing
4/9/2011                            The Statcard System                                   4


       Sciences, University of Scranton, November 14, 2002.

       <http://www.cs.scranton.edu/~dmartin/dssrs.htm>.

Systran. “Free On-Line Dictionary of Computing." Imperial College Department of

       Computing, November 14, 2002. <http://foldoc.doc.ic.ac.uk/foldoc/>.



1.5. Overview of Document

       In addition to Chapter 1, there are two other chapters included within this

document. The next chapter, Chapter 2, will provide an overall description of the project,

including a complete description of the functionality of The Statcard System as well as

the context in which it will be used. Chapter 2 was developed to be understandable to the

users of the system, the baseball coaches, players, and fans.

       For readability, Chapter 2 is broken down into 5 sub-sections. The first sub-

section is System Environment, which provides an overview of all system interfaces as

well as relevant system constraints. The next sub-section is the Functional Requirements

Definition, which provides a brief, but complete description of the services that the

system will provide. The third sub-section is User Interface Specification and it describes

the various interfaces and anticipated skill levels for each user group that will be

interacting regularly with the system. The fourth sub-section is Non-Functional

Requirements, which briefly describes the requirements of the system that determines

how it performs. Lastly, the System Evolution sub-section describes both those essential

and optional requirements that may be needed or added to the system in the future.

        The final chapter, Chapter 3, will provide a complete and fully detailed

description of the system’s constraints as well as its functionality. This chapter was
4/9/2011                           The Statcard System                                        5


designed to be understandable to the system’s developers, including software engineers,

the computer systems specialists and myself that will be implementing the design and

improving its design in the future; however, it has been written in such a fashion as to be

understandable to any interested customer of my system. This chapter is counter-

referenced with Chapter 2 to allow for easy comparison between the extended and brief

descriptions of the system’s functions.

       Chapter 3 is broken down into 3 sub-sections. The first sub-section is External

System Interfaces, which describes software, hardware and user interface requirements

for interfaces that require resources that are stored external to the system’s source. The

second sub-section is the Functional Requirements, which gives a fully detailed

description of the system’s services. The final sub-section is the Non-Functional

Requirements, which provides a formal listing of both the hardware, and software

requirements that will affect the performance of the system.
4/9/2011                             The Statcard System                                     6


2. Overall Description

2.1. System Environment

                                            Digital Scorecard




                                           Statistical Database


            Baseball Enthusiast                                       Baseball Game




                                           User's Web Server
                                               (optional)



                                  Figure 1: System Environment



       The Statcard System is designed to operate simply as a software application. The

 system will be installed onto the user’s computer as a stand-alone single-user system.

 The system is designed to exist as a software package. This package includes the digital

 scorecard software, which is directly connected to the statistical database. The baseball

 game being played only effects the digital scorecard section of the software package.

 From the digital scorecard, a statistical database will be updated with a one-click

 process at the end of the baseball game. This process will create a box score and update

 the season statistics database for the appropriate team. Then, the software package has

 the ability to upload the database information onto the user’s web server if the user has

 the appropriate space and so chooses to do so. This is only an optional function of the

 system and is not needed for full functionality. This software package is intended for
4/9/2011                             The Statcard System                                        7


 three different users, namely the coaches, players and fans. However, all three users

 will belong to the same user group, giving each user the same functionality within the

 system. Therefore, this system is designated as a single user system.



2.2. Functional Requirements Definition


                                   2.2.1. Initialize Software

Use case: Initialize Software

Diagram:




                                                                          Digital Scorecard




                                       Initialize Software

                                                                         Statistical Database
    Baseball Enthusiast




Brief Description:

After installing the software package correctly and executing the software, the opening

page will ask the user to either load a new file or open an existing file. If the user

chooses to load a new file, the initialize software use case will be performed. This

operation will load a blank digital scorecard template and create a blank database. The

blank database will then automatically enter initialized values and formulas for all

statistics to be tracked throughout the lifetime of the file.
4/9/2011                           The Statcard System                                     8


Initial Step-By-Step Description

Before the use case can be initiated, the user must have successfully installed the

software package and executed the program executable.

   1. The user presses the new file button option from the welcome screen.

   2. The system loads the default digital scorecard template from the installation

        location.

   3. The system initializes a blank database.

   4. The system fills the database with default initial data and formulas to be tracked

        during the season.

   5. The game setup use case is initiated.

(For Full Functional Requirements Specification, see 3.2.1.)
(For Use Case Realizations, see SDD 5.1)
(For Validation Testing, see TDD 4.1.4)


                                      2.2.2. Load File

Use case: Load File

Diagram:




                                                                   Statistical Database


                                          Load File

        Baseball Enthusiast




Brief Description:
4/9/2011                           The Statcard System                                     9


The load file use case is performed when the user chooses to open a file containing

previous database information.



Initial Step-By-Step Description

Before the use case can be initiated, the user must have successfully created a previous

file on the system.

   1. The user presses the load file button option from the welcome screen.

   2. The system retrieves the file and opens it for use.

   3. The game setup use case is initiated.

(For Full Functional Requirements Specification, see 3.2.2.)
(For Use Case Realizations, see SDD 5.2)
(For Validation Testing, see TDD 4.1.1)


                                    2.2.3. Game Setup

Use case: Game Setup

Diagram:




                                                                     Digital Scorecard



                                   Game Setup
    Baseball Enthusiast




Brief Description:

The game setup use case enters miscellaneous information about the game to be played.
4/9/2011                            The Statcard System                                       10


Initial Step-By-Step Description

   1. The user enters in the appropriate data into the game setup form.

   2. The digital scorecard is updated to reflect the game setup.

   3. The user is prompted to click “back” or “next”.

            a. If the user clicks “back”, the game setup use case repeats.

            b. If the user clicks “next”, the edit lineup use case is initiated.

(For Full Functional Requirements Specification, see 3.2.3.)
(For Use Case Realizations, see SDD 5.3)
(For Validation Testing, see TDD 4.1.5)


                                      2.2.4. Edit Lineup

Use case: Edit Lineup

Diagram:




                                                                         Digital Scorecard



                                     Edit Lineup
    Baseball Enthusiast




Brief Description:

The edit lineup use case is designed to initialize the digital scorecard for the particular

game to be played. This includes batting order and fielding positions. This use case also

allows for changes to the lineup at any point throughout the baseball game.
4/9/2011                               The Statcard System                                  11


Initial Step-By-Step Description

Before this use case can be initiated, the user must have initialized the digital scorecard.

   1. The user clicks on the appropriate fields in the digital scorecard template and

       enters the appropriate information into these fields.

   2. Once satisfied, the user the “continue” button and the digital scorecard is ready

       for the first batter’s input.

   3. The keep score use case is automatically initiated.

(For Full Functional Requirements Specification, see 3.2.4.)
(For Use Case Realizations, see SDD 5.4)
(For Validation Testing, see TDD 4.1.6)


                                        2.2.5. Keep Score

Diagram:




                                                                       Digital Scorecard



                                       Keep Score
     Baseball Enthusiast




Brief Description:

The keep score use case takes the input of the user depending on the real life happenings

of the baseball game. The user will be shown one enlarged standard cube of the digital

scorecard for each batter to be faced. After the user inputs the appropriate information

for each hitter, the digital scorecard will be updated and the next cube will be enlarged
4/9/2011                           The Statcard System                                      12


for input. This will occur until the user inputs the “end of inning” marker on the

scorecard. This process will continue until the “end of game” marker is inputted.



Initial Step-By-Step Description

Before this use case can be initiated the user must have the digital scorecard and lineup

ready for use.

   1. The first batter on the away team has his digital scorecard cube enlarged for input.

   2. The user selects the appropriate buttons that correspond to the real life situations

       occurring within the baseball game being viewed.

   3. The user selects the next batter in the lineup and step two is repeated.

   4. Steps two and three repeat until user selects the “end of inning” button.

   5. The digital scorecard updates the scorecard to tally up the current totals as of the

       last inning played.

   6. Steps two through five repeat until the “end of game” button is selected.

   7. The create boxscore use case is initiated.

(For Full Functional Requirements Specification, see 3.2.5.)
(For Use Case Realizations, see SDD 5.5)
(For Validation Testing, see TDD 4.1.7)


                                   2.2.6. Create Boxscore

Use Case: Create Boxscore

Diagram:
4/9/2011                           The Statcard System                                    13




                                                                      Digital Scorecard



                                  Create Boxscore
     Baseball Enthusiast




Brief Description:

The create boxscore use case automatically creates a standard boxscore from the inputted

information on the digital scorecard.



Initial Step-By-Step Description

Before this use case can be initiated, the digital scorecard must be completed according to

the real life situations that occurred in the baseball game previously played.

   1. The software traverses the digital scorecard and tallies up the information

       gathered from the scorecard.

   2. The boxscore formulas are calculated and all results are processed and shown.

   3. The boxscore is shown to allow saving, printing, or uploading.

   4. The Update Season Statistics use case is initiated.

(For Full Functional Requirements Specification, see 3.2.6.)
(For Use Case Realizations, see SDD 5.6)
(For Validation Testing, see TDD 4.1.8)


                              2.2.7. Update Season Statistics

Use case: Update Season Statistics

Diagram:
4/9/2011                           The Statcard System                                      14




                                                                      Digital Scorecard




                               Update Season Statistics
    Baseball Enthusiast                                              Statistical Database




Brief Description:

The update season statistics use case is initiated by the “one click processing” of the user.

The season statistics database is updated to reflect the changes that occurred from the

game just played.



Initial Step-By-Step Description

Before this use case can be initiated, the digital scorecard must be completed according to

the real life situations that occurred in the baseball game previously played.

    1. The statistical database is loaded.

    2. The data is passed on from the box score to be added to the season statistics

        database.

    3. All formulas within the statistical database are recalculated with the new data

        added.

    4. The season statistics database is shown to allow for saving, printing, or

        uploading.
4/9/2011                           The Statcard System                                        15


    5. The save file use case is initiated.

(For Full Functional Requirements Specification, see 3.2.7.)
(For Use Case Realizations, see SDD 5.7)
(For Validation Testing, see TDD 4.1.9)


                                      2.2.8. Save File

Use case: Save File

Diagram:




                                                                        Digital Scorecard




                                        Save File

                                                                       Statistical Database
    Baseball Enthusiast




Brief Description:

The save file use case is initiated when the season statistics database is updated or when

the user presses the “Save Now” button anytime while the software is running.



Initial Step-By-Step Description

Before the use case can be initiated, the user must have the software executing.

   1. The user enters the file name and location for the information to be saved under.

   2. The user clicks “Save.”
4/9/2011                            The Statcard System                                      16


           a. If the file is identical to a file already on the system, the file will be

                overwritten.

           b. Else the file is created in the specified location under the specified name.

(For Full Functional Requirements Specification, see 3.2.8.)
(For Use Case Realizations, see SDD 5.8)
(For Validation Testing, see TDD 4.1.2)


                                     2.2.9. Help System

Use case: Help System

Diagram:




                                                                         Digital Scorecard



                                   Help System
   Baseball Enthusiast




Brief Description:

The Help System use case is initiated whenever the user selects the “Help” button on the

various display screens.



Initial Step-By-Step Description

Before the use case can be initiated, the user must have the software running.

   1. The appropriate topics show on the menu.

   2. The user selects a topic and the help information is displayed.

(For Full Functional Requirements Specification, see 3.2.9.)
4/9/2011                            The Statcard System                                  17


(For Use Case Realizations, see SDD 5.9)
(For Validation Testing, see TDD 4.1.3)


2.3. User Interface Specification

       The Statcard System user interfaces will all be included within the software

package. The system will utilize four main windows. One window will be used to show

the user the changes created to the digital scorecard. Another window will be used to let

the user enter input onto the digital scorecard. The third window will be the output of the

boxscore at the end of the baseball game played and the final window will be the output

of the updated season statistics. Other less used windows will be created to allow for file

management and another window to allow the user to setup the baseball game being

played. These windows will utilize simple forms with traditional input/output objects,

which include text fields, drop-down lists, check boxes, and form buttons.

       The only principle user group of the system is the baseball enthusiasts, which

include baseball players, coaches, and fans alike. It is anticipated that the baseball

enthusiasts will require minimal or no instruction in regards to interacting with the

system, since they should be used to working with windows style interfaces. An

interactive help guide will also be available to the user group in order to allow both

proper input into the system and helpful instructions on how to keep a baseball scorecard.



2.4. Non-Functional Requirements

       The following describes constraints held on the system in order for it to work

properly, but are not essentially functional themselves.
4/9/2011                           The Statcard System                                   18


       This system’s overall performance will be limited to the performance quality of

the IBM-Compatible Pentium based PCs. Any computer involved in the system, should

be mobile (laptop), have at least 96 megabytes of RAM and no less than a 300-megahertz

processor. This is primarily to ensure that the computer is capable of handling the

required operating system, Windows XP. The amount of RAM actually necessary will

depend upon other possible programs running on the computer at the time of software

execution. Each computer should also have a sufficient amount of hard drive space in

order to store the software program itself, as well as additional databases and other user

files, such as boxscore files that may be saved for printing or uploading. The necessary

speed and run-time memory may have a few dependent factors, which it must adjust to

and meet in order to prevent impedance of the function designed and set-forth within this

documentation for the Statcard System.



2.5. System Evolution

       Upon the creation of requirements of the Statcard System, some optional and less

desired requirements came to light. Due to low priority of these requirements, we opted

not to implement these requirements during the initial production of the system.

       Currently, the Statcard system will only work on faster computers and is

restrained to a mobile computer running Windows XP. In the future, we hope to allow

the software to be installed on personal Palm computer devices. These palm devices

allow for greater mobility and take up less space then would carrying around a laptop

computer to the baseball game. Also, I would like to create a more graphically intense

digital scorecard with better options available at all times. Currently, due to time
4/9/2011                           The Statcard System                                     19


restraints, I will be using the simplest graphics design possible to allow the system to

function. Finally, I would like to increase the amount of statistics that can be gathered by

the digital scorecard. To make this product more appealing to the baseball fans, I would

like to add more unusual statistics not traceable by the average baseball fan using the

paper and pencil baseball scorecard. These upgrades in the system do not need to be

implemented at this time, yet will add increased functionality and user appeal to the

system if time is available to implement such upgrades.



3. Requirements Specification

3.1. External Interface Requirements

       None, this is a stand-alone system with no external components required.

3.2. Functional Requirements


                                  3.2.1. Initialize Software

Use Case Name        Initialize Software
Priority             Essential
Trigger              Software Execution
Precondition         The software package has been installed properly.
Basic Path               1. The user presses the “new file” button option
                              from the welcome screen.
                         2. The system loads the default digital scorecard
                              template from the installation location.
                         3. The system initializes a blank database.
                         4. The system fills the database with default initial
                              data and formulas to be tracked during the season.
                         5. The game setup screen is triggered.
Alternative Paths    In step 1, if the user chooses the “load file” button
                     option, the system will perform the use case Load File.
Post Condition       The template for the season statistics database and digital
                     scorecard are opened and the game setup screen appears.
Exception Paths      None
Other                None
(For Functional Requirements Definition, see 2.2.1.)
4/9/2011                           The Statcard System                               20


(For Use Case Realizations, see SDD 5.1)
(For Validation Testing, see TDD 4.1.4)

                                     3.2.2. Load File

Use Case Name         Load File
Priority              Essential
Trigger               None
Precondition          The user must have a previous data file on the system.
Basic Path                1. The user presses the “load file” button option
                              from the welcome screen.
                          2. The system retrieves the file and opens it for use.
                          3. The game setup screen is triggered.
Alternative Paths     In step 1, if the user chooses the “new file” button option,
                      the system will perform the use case Initialize Software.
Post Condition        The appropriate season statistics database is opened and
                      the game setup screen appears.
Exception Paths       If no previous database file is found in the system, the
                      user must hit cancel to return to the welcome screen.
Other                 None
(For Functional Requirements Definition, see 2.2.2.)
(For Use Case Realizations, see SDD 5.2)
(For Validation Testing, see TDD 4.1.1)

                                     3.2.3. Game Setup

Use Case Name        Game Setup
Priority             Essential
Trigger              Either the Initialize Software or Load File use cases.
Precondition         None
Basic Path                1. The user enters in the appropriate data into the
                             game setup form.
                          2. The digital scorecard is updated to reflect the
                             game setup situations.
                          3. The user is prompted to click the “next” button.
                          4. The Edit Lineup use case is initiated.
Alternative Paths    In step 3, if the user clicks the “back” button, the game
                     setup use case will repeat itself from the beginning.
Post Condition       The digital scorecard is updated to reflect the game setup
                     and the scorecard is ready to have lineups entered.
Exception Paths      If the user enters invalid field data into the game setup
                     form, an exception will be raised and the proper data type
                     and range will be displayed.
Other                None
(For Functional Requirements Definition, see 2.2.3.)
4/9/2011                          The Statcard System                              21


(For Use Case Realizations, see SDD 5.3)
(For Validation Testing, see TDD 4.1.5)

                                     3.2.4. Edit Lineup

Use Case Name         Edit Lineup
Priority              Essential
Trigger               The Game Setup use case.
Precondition          The game setup form has been completed successfully
                      with valid information.
Basic Path                 1. The user clicks on the appropriate fields in the
                              digital scorecard template and enters the
                              appropriate information into these fields.
                           2. Once satisfied, the user will click the “continue”
                              button and the digital scorecard is ready for the
                              first batter’s input.
                           3. The Keep Score use case is automatically
                              initiated.
Alternative Paths     None
Post Condition        The digital scorecard is ready for game input and the
                      Keep Score use case is initiated.
Exception Paths       If the user enters invalid field data into the game setup
                      form, an exception will be raised and the proper data type
                      and range will be displayed.
Other                 None
(For Functional Requirements Definition, see 2.2.4.)
(For Use Case Realizations, see SDD 5.4)
(For Validation Testing, see TDD 4.1.6)

                                     3.2.5. Keep Score

Use Case Name         Keep Score
Priority              Essential
Trigger               The Edit Lineup use case.
Precondition          The appropriate fields in the digital scorecard template
                      are filled in with appropriate and meaningful
                      information.
Basic Path                1. The first batter on the away team has his digital
                               scorecard cube enlarged for input.
                          2. The user selects the appropriate buttons that
                               correspond to the real life situations occurring
                               within the baseball game being viewed.
                          3. The user selects the next batter in the lineup and
                               step two is repeated.
                          4. Steps two and three repeat until the user selects
4/9/2011                          The Statcard System                              22


                               the “end of inning” button.
                           5. The digital scorecard updates the scorecard to
                               tally up the current totals as of the last inning
                               played.
                           6. Step two through five repeat until the “end of
                               game” button is selected.
                           7. The Create Boxscore use case is automatically
                               initiated.
Alternative Paths     At any point, the user may enter the Save File use case if
                      he or she chooses the “Save Button” displayed on the
                      digital scorecard.
Post Condition        The input into the digital scorecard in finalized and the
                      Create Boxscore use case is automatically initiated.
Exception Paths       If the user tries to skip a batter by selecting an out of
                      order batter as his/her next batter, the appropriate next
                      batter will be selected and a pop up warning will be
                      issued to the user about batting out of order.
Other                 None
(For Functional Requirements Definition, see 2.2.5.)
(For Use Case Realizations, see SDD 5.5)
(For Validation Testing, see TDD 4.1.7)

                                   3.2.6. Create Boxscore

Use Case Name        Create Boxscore
Priority             Essential
Trigger              The Keep Score use case.
Precondition         The information for the digital scorecard has been
                     successfully completed with no form errors.
Basic Path               1. The software traverses the digital scorecard input
                             and tallies up the information gathered from the
                             scorecard during the game.
                         2. The boxscore formulas are calculated and all
                             results are processed and shown.
                         3. A new boxscore file is created and the boxscore
                             file is opened to show the boxscore to allow for
                             saving, printing, or uploading to a website.
                         4. The Update Season Statistics use case is
                             automatically initiated.
Alternative Paths    None
Post Condition       A boxscore file is created and opened for viewing.
Exception Paths      None
Other                None
(For Functional Requirements Definition, see 2.2.6.)
(For Use Case Realizations, see SDD 5.6)
4/9/2011                           The Statcard System                                  23


(For Validation Testing, see TDD 4.1.8)

                               3.2.7. Update Season Statistics

Use Case Name         Update Season Statistics
Priority              Essential
Trigger               The Create Boxscore use case.
Precondition          The boxscore file was successfully created.
Basic Path                 1. The statistical database is loaded.
                           2. The appropriate data is passed on from the
                               boxscore to be added to the season statistics
                               database.
                           3. All formulas within the statistical database are
                               recalculated with the new data added.
                           4. The season statistics database is saved and re-
                               opened to allow for saving, printing, or
                               uploading.
                           5. The Save File use case is initiated.
Alternative Paths     None
Post Condition        The statistical database is updated to reflect the last game
                      played. The Save File use case is initiated to insure
                      proper saving of the system files.
Exception Paths       None
Other                 None
(For Functional Requirements Definition, see 2.2.7.)
(For Use Case Realizations, see SDD 5.7)
(For Validation Testing, see TDD 4.1.9)

                                        3.2.8. Save File

Use Case Name          Save File
Priority               Essential
Trigger                None
Precondition           The file has been modified.
Basic Path                  1. The user enters the file name and location for the
                               information to be saved under.
                            2. The user clicks the “Save”
                                   a. If the file is identical to a file already on
                                       the system, the file will be overwritten.
                                   b. Else the file is created in the specified
                                       location under the specified name.
Alternative Paths      None
Post Condition         The file is updated or stored in the specified file directory
                       under the specified name
Exception Paths        If the directory to save the file doesn’t exist, the directory
4/9/2011                             The Statcard System                                   24


                      will be created.
Other                 None
(For Functional Requirements Definition, see 2.2.8.)
(For Use Case Realizations, see SDD 5.8)
(For Validation Testing, see TDD 4.1.2)

                                     3.2.9. Help System

Use Case Name         Help System
Priority              Desired
Trigger               None
Precondition          The user must click the “Help System” button option
                      from the interactive digital scorecard form.
Basic Path                1. The appropriate topics are shown on the menu.
                          4. The user selects a topic and the help information
                              is displayed.
Alternative Paths     None
Post Condition        The user is presented with useful information on scoring
                      and inputting into the interactive digital scorecard.
Exception Paths       None
Other                 None
(For Functional Requirements Definition, see 2.2.9.)
(For Use Case Realizations, see SDD 5.9)
(For Validation Testing, see TDD 4.1.3)


3.3. Detailed Non-Functional Requirements

          This project entails a number of constraints that must exist in order for the system

to function properly. The first restriction is the hardware. This project was designed to

operate on IBM-Compatible Pentium based personal computers. Secondly, the computer

must be mobile in some way, allowing for user input at the baseball field. Finally, the

operating system must be restricted to Windows based operating systems. It is strongly

encouraged to have Windows XP running on the system in order reduce compatibility

errors.    Accordingly, all of these requirements must be met in order for the system to

function properly.
4/9/2011                            The Statcard System                                          25


                                            Index


                     B
Baseball Enthusiasts, 2, 17                         Form Button, 3, 17
Batter, 11, 12, 21, 22                              Formulas, 8, 13, 15, 19, 22, 23
Boxscore, 1, 2, 3, 13, 17, 18, 22, 23

                     C                                                  G
                                                    Game, 2, 3, 7, 9, 10, 11, 12, 13, 14, 17,
Coach, 1, 2, 4, 7, 17                               19, 20, 21, 22, 23
Constraint, 1, 2, 4 18, 24
                                                                         P
                     D
                                                    Player, 1, 2, 4, 7, 17
Database, 2, 7, 8, 9, 14, 15, 18, 19, 20,
  23                                                                     S
Digital Scorecard, 7, 8, 10, 11, 12, 13,
14, 17, 19, 20, 21, 22, 24                          Season Statistics, 1, 2, 3, 7, 13, 14, 15,
                                                      17, 20, 22, 23
                     E                              Statcard System, 1, 2, 3, 4, 7, 17, 18
                                                    Statistical Database, 7, 14, 15, 23
Electronic Scorecard, 2, 3
Evolution, 1, 2, 4, 18                                                  T
                                                    Template, 2, 8, 11, 19, 20, 21
                     F
Fan, 1, 2, 4, 7, 17, 19                                                  U
Fields, 11, 17, 21                                  Upload, 3, 7, 13, 15, 18, 22, 23
                                                    User-interface, 1, 2, 3, 4, 6, 17

				
DOCUMENT INFO