Home

Welcome to your wiki!

This is the default page, edit it as you see fit. To add a new page simply reference it within brackets, e.g.: [SamplePage].

The wiki uses Markdown syntax.

Project Admins:

• matthewstitt49259

[matthewstitt49259]

Initial post to SourceForge

[matthewstitt49259]

Learning Center Sign In Case Study

The use cases considered during the design of the case study are:

1.Login Student
2.Register new Student
3.List Items to Check Out
4.Log Out Student
5.Add Items to Collection
6.Create Report

Use Case 1: Login Student

Characteristic Information
Preconditions: Student has registered
Success End Conditions: Student has logged in
Failed End Conditions: Student is not logged in(Student id or password is incorrect)
Primary Actor: Student
Triggers: Interaction with Sign in and then print report for Learning Center

Main Success Scenario
1.System Administrator asks system to display Login form
2.System displays form
3.Student enters student ID (created during the “Register New Patron” use case)
4.System verifies the Student's student id and password
5.System annotates date/time when Student logged in
6.System displays “Welcome” form with a “menu” of valid actions.
-- Extensions(alternate scenarios)
4a. Verification fails and login fails
4a1. System displays “Login failed” form to the Student.

Use Case 2: Register New Student

Characteristic Information

Preconditions: Program Administrator has been authenticated
Success End Conditions: Student is registered with the system(added to the database and begin to use the Learning Center)
Failed End Conditions: Student was not registered with the system; Student is already registered with the system.
Primary Actor: Program Administrator
Trigger: A Student arrives at the Learning Center terminal

Main Success Scenario
1.System Administrator asks system to display the “Learning Center Login Form”
2.System displays the form.
3.System Administrator enters Students student ID and password into form and submits it to the system
4.System uses the student ID to create a Student ( adds student ID, password and date of registration)
5.System adds new Student to database
6.System displays “Registration Success” form to System Administrator.
-- Extensions
5a. Student ID is already in the database
5a1. System displays “Registration Failure” form to System Administrator, indicating student ID is already in use

Use Case 3: List Items to Check Out

Characteristic Information

Precondition: Student is already logged in
Success End Conditions: System displays choices to select student activity in the Learning Center.
Failed End Conditions: Student is not logged in.
Primary Actor: Student
Trigger: Student enters activity on form

Main Success Scenario
1.Student enters activity on form
2.Student clicks on “Submit” button
3.System records Student activity
4.System returns to “Learning Center Login Form”
-- Extensions
2a. The student does not select any items.
2a1. System displays the “You have not selected an item” form
2b. System records Activity code, Description, student name and Date/Time

Use Case 4: Log Out Student

Characteristic Information

Precondition: System has returned to “Learning Center Login Form” Student needs to Log Off
Success End Conditions: Student presses Log Off button displaying “Log Off” form and Logs off.
Failed End Conditions: Student does not log off
Primary Actor: Student
Trigger: Student presses “Log Off” button which prompts “Log off” form.

Main Success Scenario
1.Student selects “Log Off” button
2.System searches for Student and if found annotates date/time when Student left
3.System returns to “Learning Center Login Form”
-- Extensions
1a. System prompts Student “Please Log Out” when Student attempts to log in again.
2a. System searches for Student but Student is not found
2a1. System prompts Student, “Login not found. Please Login.”

Use Case 5: Add Item to Collection

Characteristic Information
Precondition: Student clicked Submit button on "Signin form"
Success End Conditions: Items are added to the collection
Failed End Conditions: Item is not added to the collection
Primary Actor: System
Trigger: Student completes selection and presses Submit

Main Success Scenario

1. Student selects one Activity
2. Presses "Submit"
3. System adds to Student count
4. System adds Date/Time
5. System notes Activity code and adds count to that code
   -- Extensions
   1a. Student selects more then one item
   Use Case 6: Print Report

Characteristic Information
Precondition: All users have logged off the application. System Administrator has logged off and logged into Administration form.
Success End Conditions: System Administrator successfully prints a report detailing the activity of a requested amount of time.
Failed End Conditions: Students have not logged off completely. Does not print proper information and in proper format.
Primary Actor: System Administrator
Trigger: System Administrator logs into the Administration form

Main Success Scenario

1. System Administrator logs off Sign in form
2. System shows Administration form
3. System Administrator logs into Administration form
4. System Administrator selects date range and presses Print
5. System prints report
   -- Extensions
   1a. Log off from SQL database any Students that have not logged off manually
   5a. System sorts Activity code and Activity description
   5b. System adds Student count to report
   5c. System adds Date/Time to report

[matthewstitt49259]

Uploaded .zip version of Documentation and src folders for easier download