Library Project
Use Case Specification: Cataloging Items
Version <1.0>
Revision History
|
Date |
Version |
Description |
Author |
|
10/11/2001 |
1.0 |
Initial Creation |
Mark Bondurant |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
1. Use Case Name 1
1.1 Brief
Description 1
2. Flow of Events 1
2.1 Basic
Flow – Entering A Book 1
2.2 Alternative
Flows 1
2.2.1 Entering
A Picture 1
2.2.2 Entering
Software 1
2.2.3 Entering
A Sound 1
2.2.4 Entering
A Magazine Article 1
2.2.5 Entering
A Database 1
2.2.6 Entering
A Document 1
2.2.7 Entering
Music 1
2.2.8 Entering
An Illustration 1
2.2.9 Entering
A Web Page 1
2.2.10 Entering
A MARC Record 1
3. Special
Requirements 1
3.1 <
First special requirement > 2
4. PreConditions 2
4.1 Authenticated 2
4.2 Correctly
Positioned 2
5. PostConditions 2
5.1 <
Postcondition One > 2
6. Extension Points 2
6.1 <name
of extension point> 2
Use Case Specification: Cataloging Items
This document describes the basic flow of events that must occur during the process of data entry.
Once in the data entry system, the cataloguer
OCLC Record Fields:
Author’s name
Title proper
Statement of responsibility
Edition statement
Publication, distribution, etc.
Place of publication
Publisher
Date of publication
Physical description
Series statement
Notes
Standard number (ISBN)
Subject headings
Library of Congress control (card) number
The Cataloguer logs in to the Library System to gain access to the cataloging screens
The Cataloguer logs in to the Library System to gain access to the cataloging screens
The Cataloguer logs in to the Library System to gain access to the cataloging screens
The Cataloguer logs in to the Library System to gain access to the cataloging screens
The Cataloguer logs in to the Library System to gain access to the cataloging screens
[A Special Requirement is typically a non-functional requirement that is specific to a use case but is not easily or naturally specified in the text of the use case’s event flow. Examples of special requirements include legal and regulatory requirements, application standards, and quality attributes of the system to be built, including usability, reliability, performance or supportability requirements. Additionally, other requirements such as operating systems and environments, compatibility requirements, and design constraints should be captured in this section.]
In order to enter items, the cataloger must identify himself by logging in, otherwise he will not have access to the cataloguing portion of the system.
Unless otherwise stated, the cataloger must be at the start of the data entry system. This is reached through the main menu. Once the cataloguer has been authenticated, then the option will become available.
[A postcondition (of a use case) is a list of possible states the system can be in immediately after a use case has finished.]
[Extension points of the use case.]
[Definition of the location of the extension point in the flow of events.]