Guidelines for Project Part 1
Note: Use the following guidelines in
conjunction with the handout for Team Project Part#1 available in section
Homework of the course website.
·
In
the Table of Contents provide the
titles of sections and subsections of your SRS, with corresponding page
numbers. Number the sections and subsections for easier referencing.
·
The
Introduction should provide an
overview of your project. What is the project about, what are
its main goals, what sport is considered, and what are the main
functions of the software that you will develop (500 to 1000 words).
·
In
Specific Requirements include the
core parts of Project Part#1, as mentioned in parts C1 and C2
of the handout.
·
For
part C1, Requirements analysis and completion,
you can use any structured, well organized format that helps you answer adequately
C1 requests. Natural
language, point form statements, the format “<Req. ID> The <system> shall <function>” (for examples, see Verity paper, section 2, on the
course website), the format shown in Fig. 5.10 of the textbook, or a combination
of the above can all be used. If you find useful, you can include supporting
pictures, diagrams, and tables in this section (but this is not required).
·
For
part C2a, Use cases and scenarios, take into
consideration the following:
o
The
use case diagram should have beetwen 7 and 15 use cases.
o
Each
use case should be described using one of the following: (i) natural language,
three to six lines description for each use case, (ii) the format shown in Fig.
12. 9 of the textbook, or (iii) the template shown in the handout “Use case
modeling” (based on Chapter 4 of Arlow and Neustadt’s book) distributed in the class
on Wednesday, October 22. Use just one type of description (i, ii, or iii) for all
use cases.
o
Each
scenario should be detailed using either (i) the step-like format (“sequence of
actions”) shown in Fig.
5.11 of the textbook, or (ii) the template shown in the handout “Use case
modeling” (based on Ch. 4, Arlow and Neustadt). The latter format is strongly
recommended.
o
The
Class diagram for C2b should be drawn using
the UML notations for classes, relationships, and cardinalities. The class
diagram is expected to contain at least 7 classes.
o
The
two State machines in C2c should be drawn using
the UML notations for states and transitions. Both state machines should be
fairly complex; it is recommended that one state machine describes the entire
system and the other describes the simulation part of the system (that is, the
simulation of an individual game, trial, or competition round).
·
The
Glossary of Terms should include at
least ten terms specific to the problem’s domain (the sport considered). For
each term provide a brief description (one to four lines) and, whenever appropriate,
alternate terms (equivalent terms). Note that there is no upper limit to the
number of terms you can include in the glossary to help non-expert readers
understand the problem domain.
·
The
section Contributions of Team Members
should detail on an individual basis the work of each team member on this part
of the project.
·
Finally,
the References section of the SRS should
contain at least three additional references (books, articles, websites) that you have consulted in relation to your
project.