Note that some use cases were named but not described! I've also
had to pick, choose, simplify (abbreviate?), and combine use case descriptions.
A student goes online and orders the books for the classes in which they have
A student provides one or more course numbers for the current period. The
system retrieves the book list from the bookstore. The system provides the list
of books to the student, grouped by course.
Also known as:
Student uses FIS to access TRACS and logs in using student Id and a PIN.
The student requests a class schedule and is shown it by the system.
This use case lets a student to get a syllabus for a registered class.
After accessing FIS the student is listed the courses in which they are
registered. The student chooses to retrieve the syllabus for a course
and the system displays the syllabus.
Also known as
The student must authenticate themselves and is then given a list of classes
they have taken. The student selects a class and sees the grade for that class.
The student can then log of or see other classes.
. . . . . . . . . ( end of section Free Interface to College Use Cases) <<Contents | End>>
. . . . . . . . . ( end of section Free Interface to College) <<Contents | End>>
- Artifact::="Anything that is created in the course of a project".
- artifact::=see above.
- DCD::diagram="Design Class Diagram", shows the classes that will be implemented in code.
- Deliverables::="A packet of artifacts that must be prepared by a deadline for review or distribution".
- Glossary::= See http://cse.csusb.edu/dick/cs375/uml.glossary.html.
- GoF::="Gang of Four",
[ patterns.html#GoF ]
- GRASP::patterns="General Responsibility Assignment Software Patterns",
a set of guidelines for designing objects and classes. They take a single
event that the system must handle and determine a good class to carry it out.
[ patterns.html#GRASP -- General Responsibility Assignment Software Patterns ]
- Grades::= See http://cse.csusb.edu/dick/cs375/grading/.
- KISS::Folk_law="Keep It Simple, Stupid", in agile processes this means never
drawing a diagram or preparing a document that doesn't provide value
to the clients and stakeholders. In all processes it means never
designing or coding what is not needed, see YAGNI.
- OOAD::="Object-Oriented Analysis and Design", See chapter 1 in text.
- patterns::="Documented families of problems and matching solutions", see
- Patterns::= See http://cse.csusb.edu/dick/cs375/patterns.html.
- Process::="How to develop software".
- RJB::=The author of this document,
RJB="Richard J Botting, Comp Sci Dept, CSUSB".
- RUP::Process="Rational UP", a proprietary version of UP.
- SSD::="System Sequence Diagrams", see chapter 10.
- TBA::="To Be Announced".
- UML::="Unified Modeling Language".
[ Unified_Modeling_Language ]
- UP::="Unified Process", an iterative, risk-driven, and evolutionary way to develop OO software.
- YAGNI::XP="You Ain't Gonna Need It", an XP slogan that stops you
planning and coding for things that are not yet needed. As
a rule the future is not predictable enough to program a feature
until the stakeholders actually need now. In this class it also means
"It won't be on the final or in quizzes".
- XP::="Extreme Programming", the ultimate iterative, code-centric, user-involved