Use Case Implementations

Use Case #[Number] [NAME]

Module #/Name	[NUMBER] / [NAME]
Custodian Dept.	[Department responsible for the use case]
Actors	[List of actors, indicating who initiated the use case]
Purpose	[Intention of the use case]
Overview	[Summary of the use case]
Type	[Primary/Secondary/Optional]
Cross reference	[Related system functions]
Business Rules	[Rules and exceptions of the use case]
Contact Persons	[Persons of the organization with whom details of the use case was discussed]
Documents Referred	[Previous forms, reports and documents referred]
Response Time	[Time to be taken by the system for execution of the use case]

[Most of this section is a repetition of what is described in chapter 3. But here a detailed course of action is given in the scenarios with reference to all the classes, forms, reports that will be involved in the successful completion of the scenario. This basically helps in building the class definitions and leads to the design of the data dictionary.]

Scenario #[Number] [(Type)] [Scenario Name]

Use case #[Number]/[NAME]

Detail Course of Action

Actor Action		System Response
	[Numbered action of the actor with reference to forms and reports]		[Numbered description of the system responses with reference to classes, forms and reports]

Alternate Course:

[Line Number] : [Description of the exception]

Forms:

[List of all forms that are involved in the successful completion of the scenario in the following format:

[F# [Serial Number]/[Name]]

For example: [F# 1/frmPaymentDetails] ]

Reports:

[List of all reports that are referred in the scenario in the following format:

[R# [Serial Number]/[Name]]

For example: [R# 1/rptPaymentDetails] ]

Classes:

[List of all classes, and details about their properties and methods that are referred to in the scenario in the following format:

[C# [Serial Number]/[Name]]

For example: [C# 1.a/clsPaymentDetails]

Three different types of classes will be used in describing the scenarios. So the numbering of classes will be as given below:

Number.a – for entity (data) classes

Number b – for entityset classes

Number.c – for manager (control) classes

For example:

[C# 1.a/clsPaymentDetails],

[C# 1.b/clsPaymentDetailsSet],

[C# 1.c/clsPaymentDetailsManager]

Class #[Number] / [Name]

Attribute	M/P	Data Type	Description/Prototype
[Name of the property or method]		[Data type of the attribute or return type of function]	[Description of the property or method. Whenever it is a method, specify its prototype]

[Since the methods of an entity set class are common for all, i.e., Add, Remove, Count and Item, it is not required to give all details about these classes. Only the implementation strategy to be followed, i.e., "Array based" or "VB collection based" should be stated. It is better to use the "array based" strategy when there will be very few deletions or insertions in the collection, e.g., for storing values to be displayed in a ComboBox. If any additional special functions are required in the entity set it must be explicitly stated.]