|
Software Requirements
Specification
Usage scenario
Introduction
2. Usage scenario
2.1 User profiles
2.2 Use-cases
2.2.1 Use-Case Diagram
2.2.2 Use-Case
Descriptions
2.3 Special usage
considerations
2.4 Activity Diagrams
Data Model and Description
Functional Model and
Description
Behavioral Model and Description
Restrictions, Limitations, and Constraints
Validation Criteria
Appendix A
Appendix B
2. Usage
scenario
2.1 User profiles
The following definitions describe the actors in the system.
|
Administrator |
An administrator has the
responsibility for registering new customers and billing existing
customers. They have unrestricted access to the Child Care Management
system including viewing and changing passwords. |
|
Assistant |
A teaching assistant has the responsibility for
signing the children in and out of the Day Care Center. They have
restricted access to the child management system. |
|
Employee |
An employed is the general name that refers to an
administrator, teacher, or assistant. |
|
Parent |
The parent is a customer of the Child Care Center.
They are responsible for enrolling children and paying the bills. |
|
System |
The system refers to the computer hardware and
software that controls the application. It accepts user input, displays
user output, and interfaces to the Web Server through the Internet. |
|
Teacher |
A teacher has responsibility for evaluating the
children and logging their comments about the children’s behavior. They
have the same restricted access to the child management system as their
assistants. |
|
Web Server
|
The Web server is a remote computer system that
maintains the database and serves Web pages to the System. |
2.2 Use-cases
The following use-cases are typical interactions between the external
environment and the internal software system. Each use-case is described in
section 2.2.2.
1. Log onto system
2. Enroll child
3. Enter daily reminder
4. Display daily reminder
5. View account information
6. Update account information
7. Enter parent correspondence notes
8. Enter child comments
9. View report
10. Print invoices
11. Sign in child
12. Sign out child
13. Debit accounts
14. Enter child immunization data
15. Display immunization warning
16. Assign classroom
^
TOP
2.2.1 Use-Case Diagram
The use-case diagram in
Figure 1 shows six actors that were described in section 2.1. In order to
minimize the complexity of this diagram several connections were left out. For
instance, every use-case will typically involve an interaction with the System
and Web Server, but since this is a secondary activity it is not shown in the
drawing. The Employee could be an administrator, teacher or assistant. Instead
of drawing separate connections to each of these actors, the Employee was added
to make the diagram easier to read.
^
TOP
2.2.2 Use-Case Descriptions
|
Use-case: |
Log on to System |
|
Primary actor: |
Employee |
|
Goal in context: |
To gain access to the System |
|
Preconditions: |
The employee has a valid user name and password |
|
Trigger: |
An Employee needs access to the System to perform
their job |
|
Scenario: |
1. The
System prompts the employee for their user name and password.
2. The
Employee enters their user name and password.
3. The
System sends the user name to the Web Server.
4. The
Web Server sends back the password registered to the user name.
5. The
System verifies the password and sets the user’s authorization.
6. The
Employee is given access to the System to perform their job. |
|
Exceptions: |
The user name and
password cannot be verified |
|
Use-case: |
Enroll Child |
|
Primary actor: |
Administrator |
|
Goal in context: |
To enroll a child in child care |
|
Preconditions: |
1.
Child is 3-6 years of age
2.
First child being enrolled |
|
Trigger: |
Parent decides that they need someone to watch
their child during the day |
|
Scenario: |
1. A
Parent contacts a child care facility Administrator.
2. The
Administrator logs onto the System.
3. The
Administrator selects New Account from the Main menu.
4. The
Administrator checks classroom availability.
5. If a
classroom has fewer than 20 children the child is added to that
classroom roster.
6. A
new account is created.
7.
Parent and child information is entered into the System.
8. The
System sends the account information to the Web Server for storage.
9. The
Parent receives verification that their child is enrolled. |
|
Exceptions: |
The classroom has
reached its capacity |
|
Use-case: |
Enter Daily Reminder |
|
Primary actor: |
Employee |
|
Goal in context: |
To enter a personal event into the System that will
appear on a given date |
|
Preconditions: |
The user has a valid password |
|
Trigger: |
An employee has an event that they need to be
reminded of |
|
Scenario: |
1. The
Employee logs onto the System.
2. The
Employee selects Daily Reminders from the Main menu.
3. The
Employee selects New Daily Reminder.
4. The
System prompts the Employee for the date of their reminder.
5. If
the reminder date is not already past the System prompts the Employee
for their reminder message.
6. The
Employee enters the message for their reminder
7. The
System stores the information on the Web Server.
8. The
Employee receives verification that their reminder has been recorded |
|
Exceptions: |
The reminder date
entered has already passed |
^
TOP
|
Use-case: |
Display Daily Reminder |
|
Primary actor: |
System |
|
Goal in context: |
To show an employee’s reminders |
|
Preconditions: |
A reminder has previously been entered |
|
Trigger: |
The date of a reminder is the current date |
|
Scenario: |
1. The
Employee logs onto the System.
2. The
System requests the Employee’s reminders from the Web Server.
3. The
System looks for pending reminders.
4. The
System displays any pending reminder messages.
5. The
Employee acknowledges the reminder.
6. The
System deletes the reminder from the Web Server. |
|
Exceptions: |
The user doesn’t logon
on the day of their reminder.
Multiple reminders on
the same day. |
^
TOP
|
Use-case: |
View Account Information |
|
Primary actor: |
Employee |
|
Goal in context: |
To retrieve account information |
|
Preconditions: |
The account exists |
|
Trigger: |
An employee needs information from one of their
accounts |
|
Scenario: |
1. The
Employee logs onto the System.
2. The
Employee selects View Account Information from the Main menu.
3. The
System prompts for the name or ID of the Parent or child.
4. The
System requests the record from the Web Server.
5. A
report of the record is displayed on the screen. |
|
Exceptions: |
The account does not
exist |
^
TOP
|
Use-case: |
Update Account Information |
|
Primary actor: |
Administrator |
|
Goal in context: |
To update the information contained in an account |
|
Preconditions: |
The exact spelling of the name is known |
|
Trigger: |
Account information has changed and needs to be
updated |
|
Scenario: |
1. The
Administrator logs onto the System.
2. The
Administrator selects Edit Account Information from the Main menu.
3. The
System prompts for the name or ID of the Parent or child.
4. The
System requests the record from the Web Server.
5. A
form for the report is displayed on the screen.
6. The
Administrator edits the appropriate fields.
7. The
Administrator selects Save.
8. The
System sends the updated record to the Web Server for storage.
9. The
Administrator’s employee ID number, the date, and nature of the change
are logged.
10. The
Administrator receives confirmation that the information was saved. |
|
Exceptions: |
|
^
TOP
|
Use-case: |
Enter Child Comments |
|
Primary actor: |
Teacher |
|
Goal in context: |
To add comments about a child |
|
Preconditions: |
The child is enrolled in the Day Care Center |
|
Trigger: |
A teacher needs to enter a comment about a child |
|
Scenario: |
1. The
Teacher logs onto the System.
2. The
Teacher selects Enter Child Comments from the Main menu.
3. The
System prompts for the name or ID of the Child.
4. The
System sends the information to the Web Server
5. The
Web Server verifies that the Child is currently enrolled.
6. The
system prompts the Teacher for their comments.
7. The
Teacher enters comments and selects Save from the menu of options.
8. The
System sends the comments to the Web Server for storage.
9. The
Teacher’s employee ID number, the date, and nature of the change are
logged.
10. The
Teacher receives confirmation that the information was saved. |
|
Exceptions: |
|
^
TOP
|
Use-case: |
View Report |
|
Primary actor: |
Administrator |
|
Goal in context: |
To view a report |
|
Preconditions: |
Information required for the report has previously
been entered. |
|
Trigger: |
An administrator decides to view a summary of a
Parent’s information |
|
Scenario: |
1. The
Administrator logs onto the System.
2. The
Administrator selects View Report from the Main menu.
3. The
Administrator selects the name of the Report from the Report menu.
4. The
System requests the Report from the Web Server.
5. The
Report is displayed on the screen.
6. The
Administrator is given the option to close or print the report.
7. The
report is closed or printed. |
|
Exceptions: |
|
^
TOP
|
Use-case: |
Print Invoices |
|
Primary actor: |
Administrator |
|
Goal in context: |
To print invoices that will be mailed to the
parents |
|
Preconditions: |
Parents have had a child enrolled for at least a
month |
|
Trigger: |
The end of the month |
|
Scenario: |
1. The
Administrator logs onto the System.
2. The
Administrator selects Invoices from the Main menu.
3. The
System requests the invoices from the Web Server.
4. The
invoices are displayed on the screen.
5.
Immunization alerts are included on a parents invoice.
6. The
Administrator is given the option to close or print the invoices.
7. The
invoices are closed or printed. |
|
Exceptions: |
An administrator tries
to print invoices before the end of the month |
^
TOP
|
Use-case: |
Sign Out Child |
|
Primary actor: |
Assistant |
|
Goal in context: |
To ensure that the children are picked up by an
authorized person and record the time they were released. |
|
Preconditions: |
The child has been in attendance at the Day Care
Center |
|
Trigger: |
A person arrives to pick up a child |
|
Scenario: |
1. The
Assistant logs onto the System.
2. The
Assistant selects Sign Out from the Main menu.
3. The
System prompts the Assistant for the name or ID of the child.
4. The
information is sent to the Web Server.
5. The
Web Server returns the name of any authorized pick ups.
6. The
Assistant verifies the identity of the person picking up the child.
7. If
the child is released the Assistant Selects Released from the menu.
8. The
System notifies the Web Server that the Child has been released.
9. The
Web Server records the time that the Child was released.
10. The
Assistant receives confirmation that the information was recorded. |
|
Exceptions: |
|
|
Use-case: |
Debit Accounts |
|
Primary actor: |
System |
|
Goal in context: |
Debit all parents at the end of the monthly billing
period |
|
Preconditions: |
The Parent has at least one child enrolled in the
Day Care Center |
|
Trigger: |
Last day of the month |
|
Scenario: |
1. The
System requests billing information from all active accounts
2. The
Web Server returns the amount owed for each customer.
3. The
System increases the amount owed on each account.
4. The
updated information is sent back to the Web Server for storage. |
|
Exceptions: |
|
^
TOP
|
Use-case: |
Enter Child Immunization Data |
|
Primary actor: |
Administrator |
|
Goal in context: |
To enter immunization shot data for child |
|
Preconditions: |
Child is 3-6 years old and hasn't received all
shots |
|
Trigger: |
State health department sets age when each shot is
required |
|
Scenario: |
1.
Administrator enters State requirements for shots, name of shot
and age when each shot is required ( this function is only performed
once and updated as Health department or State requirement changes).
2.
Administrator receives state stamped immunization booklet from
parent.
3.
Administrator logs into system.
4.
Administrator enters dates that were stamped by physician along
with specific shot that was given. |
|
Exceptions: |
|
^
TOP
|
Use-case: |
Display Immunization Warning |
|
Primary actor: |
System |
|
Goal in context: |
Display the Immunization needed 2 weeks prior to
State deadline |
|
Preconditions: |
Child is 3-6 years old and hasn't received all
shots |
|
Trigger: |
State health department sets age when each shot is
required; child nears age when shot is required. |
|
Scenario: |
1.
Employee logs into system
2.
The system checks child records for an upcoming required
immunization.
3.
Based on data previously entered teacher receives message on
screen indicating child is nearing birthday which could mean a shot is
needed |
|
Exceptions: |
|
^
TOP
|
Use-case: |
Assign Classroom |
|
Primary actor: |
Administrator |
|
Goal in context: |
Assign classroom to child |
|
Preconditions: |
Child is enrolled in daycare center and not on
waiting list |
|
Trigger: |
Child is enrolled in daycare center |
|
Scenario: |
1. Employee logs into system
2. See enroll child Use-Case description
3. Child is assigned a classroom based on age 3-
6 |
|
Exceptions: |
All classrooms are full |
2.3 Special usage considerations
- Billing fees cannot be changed.
2.4 Activity Diagrams
The following activity diagrams show the actions that occur during a particular
use-case.
Figure 2 shows the steps taken as an employee logs on to the computer system.
Access is only granted if the correct user ID / password combination is entered
within the first three attempts. After a third attempt the user ID will be
locked out and an administrator will need to issue a new password. Once access
is granted the employee can use the system according to their level of
authorization.
Figure 2 - Activity diagram for logging on to the system
In Figure 3 a parent has contacted an administrator to enroll their child. The
administrator will first check for an available classroom. If all classes in the
child’s age category are full the child will be placed on a waiting list. After
the size of the waiting list reaches 100, parents will be turned down and no
information about them will be retained in the system. If the child is accepted,
or even placed on the waiting list, a new account will be created and all
customer information will be entered into the system.
^ TOP
Figure 3 - Activity diagram for enrolling a child
Figure 4 shows the activity involved in entering a daily reminder. The employee
will be warned if the date they are requesting has already past. In addition,
their reminder message will need to be limited to 50 characters.
Figure 4 Activity diagram for entering a daily reminder
On the day of a Daily Reminder the process shown in Figure 5 will display the
appropriate message. After the message is acknowledged it will be permanently
removed from the system. ^
TOP
Figure 5 - Activity diagram for displaying a daily reminder
Viewing and updating account information is depicted in Figure 6. As shown in
the diagram all employees will be able to view account information but only
administrators will be allowed to edit.
^ TOP
Figure 6 - Activity Diagram to view / update account information
Figure 7 shows that only administrators have access to viewing and printing
reports. After the report is displayed on the screen it can be sent to a
printer. ^
TOP
Figure 7 - Activity diagram for viewing and printing reports
Printing invoices is another activity that is only allowed by the administrative
staff. As seen in Figure 8 if a child is in need of an immunization it will be
noted on the invoice. ^
TOP
Figure 8 - Activity diagram for printing invoices
When a child leaves the Day Care Center the assistant ensures that the person
picking up the child is either the parent or someone authorized by the parent.
The diagram in Figure 9 also shows that the assistant will record the time that
the child leaves. This information will be used to bill parents for late pick
ups. ^
TOP
Figure 9 - Activity diagram for signing out children
Figure 10 - Activity diagram for debiting customer accounts
Figure 10 shows the process of debiting customer accounts. This activity happens
on the last day of every month. Each account will be billed according to the
number of children enrolled as well as the number of late pick up hours.
^
TOP
|
Home |
Hosting | Domains
| Support |
Contacts
|
| Terms
& Condition |
Privacy Policy
|
Copyright © 2005 by
HostItWise.com Read our Copyright. All
rights reserved.
|
