This Use-Case specification is used as a sample on posts and articles on this blog.

It relates to the Use-Case specification written by Scott W. Ambler  Introduction to System Use Cases (so you can compare the styles used by Scott and by me).

Use-Case specification: Enroll in Seminar

History

Distribution

References

Table of contents

1     Enroll in Seminar. 3

1.1        Short description. 3

2     Flow of events. 3

2.1        Flow Enroll in seminar 3

2.2        Subflow <Suflow name>. 5

3     Supplementary requirements. 6

3.1        Functionality. 6

3.2        Supportability. 6

3.3        Reliability. 6

3.4        Efficiency. 6

3.5        Portability. 6

3.6        Constraints 6

4     Points of discussion. 6

4.1        Point of discussion 1. 6

5     Appendix: User Interface. 7

5.1        Screen <Screenname>. 7

1                Enroll in Seminar

1.1      Short description

Enroll an existing student in a seminar for which she is eligible.

2                Flow of events

2.1      Flow Enroll in seminar

This flow starts when a Student wants to enroll in a seminar

1.      The System displays the Security Login screen.

2.      The Student inputs her name and student number

3.      The System verifies the student is eligible to enroll in seminars at the university.

4.      The System displays the available seminars on the Seminar Selection Screen.

5.      The Student selects the seminar in which she wants to enroll.

6.      The Student acknowledges she wants to enroll in the seminar.

7.      The System validates the student is eligible to enroll in the seminar.

8.      The System validates the seminar fits into the existing schedule of the student.

9.      The System calculates the fees for the seminar

10.  The System displays the Seminar Fees Screen.

11.  The System displays the calculated fees.

12.  The Student acknowledges she wants to enroll in the seminar.

13.  The System enrolls the student in the seminar.

14.  The System displays the Seminar Enrollment Summary Screen to inform the student that the enrollment was successful.

15.  The System bills the student for the seminar.

16.  If the Student wants a printed statement of the enrollment,
the System prints the Enrollment Summary Report.

Here ends this flow.

2.1.1                       Alternative Flows

A2.1   Student is Not Eligible to Enroll in Seminars

When the Student is not eligible to enroll in seminars (See business rule BR129 Determine Eligibility to Enroll) the System  displays a message. The Use Case ends.

A6.1   Cancel enrolling in Seminar.

When the Student decides not to enroll in an available seminar, the Use Case ends.

A7.1      Student does not have the prerequisites to enroll in this Seminar
When the Student is not eligible to enroll in this seminar (See business rule BR130 Determine Student Eligibility to Enroll in a Seminar) the System  displays a message. Continue at step 4.

A8.1      Seminar does not fit into the existing schedule of the student.
When the selected seminar does not fit in the existing schedule of the student (See business rule BR143 Validate Student Seminar Schedule) the System  displays a message. Continue at step 4.

A12.1  Cancel enrolling in the selected seminar

When the Student decides not to enroll in the selected, continue at step 4.

3                Supplementary requirements

Supplementary requirements which are only applicable to this Use Case are documented in this paragraph. This paragraph is organized according to ISO 9126.

3.1      Functionality

3.1.1                   The system calculates the fees for the seminar

Based on the fee published in the course catalog, applicable student fees, and applicable taxes. Apply business rules BR 180 Calculate Student Fees and BR45 Calculate Taxes for Seminar.

3.1.2                   The system bills the student for the seminar

The system bills the student for the seminar, according to business rule BR100 Bill Student for Seminar. 

3.2      Supportability

No supplementary requirements.

3.3      Reliability

No supplementary requirements.

3.4      Efficiency

No supplementary requirements.

3.5      Portability

No supplementary requirements.

3.6      Constraints

No constraints

4                Points of discussion

4.1      Showing applicable seminars only

The list of available seminars could be restricted to the seminars for which the student is eligible to enroll.

5                Appendix: User Interface

The screens used in this Use Case are fully described in the User-Experience Model. The screenshots are included to give you an idea of the proposed look of the User Interface.

5.1      UI23 Security Login Screen

Screenshot or wireframe.

5.2      UI23 Seminar selection Screen

Screenshot or wireframe.

5.3      UI23 Security Login Screen

Screenshot or wireframe.