6437 COMPUTER SCIENCE System Analysis and Design
ltdprinwival
all_of_us_work.docx
Expanded Use Case Description
|
Actors |
Customer Register Website administrator |
|
Purpose |
Login website |
|
Type |
Abstract |
|
Importance |
Primary |
|
Technical Difficulty |
Medium |
|
Cross References |
|
|
Pre -Condition |
Custumen know our website and entered. |
|
Assumptions |
This step is the first step for client when they are enter the website. |
Use Case Interactions
|
Actor Action |
System Response |
|
01- This use case start with when clients enter our website and want to login or sign in. |
customer use login system to login account
|
|
02- the new customer need register first |
new customer use login system to register and then login |
|
03- Administrator need authorized customer to login or sign in |
admin system is focus on verify customer and record customer profile. |
Use Case Interaction Exception
|
1. forgot passwords and changed email or phone number |
|
2. can’t register because of error |
|
3. registered name repetition |
|
4.can’t login because of website maintenance |
|
|
|
|
|
|
|
|
Expanded Use Case Description
|
Actors |
Administration Manager Customer
|
|
Purpose |
System Maintenance |
|
Type |
Abstract |
|
Importance |
Primary |
|
Technical Difficulty |
High |
|
Cross References |
Maintenance |
|
Pre -Condition |
Customer is registered already
Customer has access to the system
|
|
Assumptions |
This process is to maintenance system operate smoothly |
Use Case Interactions
|
Actor Action |
System Response |
|
1. The system maintenance process start with Log In |
Log in includes both manager and customer (students) access smoothly
|
|
2. Software need to regularly update |
2.1 Software update successfully notification to Manager
2.2 Software may update unsuccessful due to lack of technology skill or not enough budget, it also notification to Manager
|
|
3. Firewall is important to protect profiles and information |
3.1 Display risk to managers during running the system 3.2 If there is risk for Profiel safety, notification to customers to change password or update firewall |
|
4. System reporting |
4. 1 Notification to both managers and customers if the system need time for updating
4.2 Notification to both managers and customers if the system shut down for a moment for fix system bug or maintenance upgrade. |
Use Case Interaction Exception
|
2.1 Overspend the budget to update the software |
|
2.2 Still have problem even update the software |
|
2.3 System can’t operate smoothly after updated |
|
3.1 Customer Profile disclosure |
|
4.1 Time manage issue for system maintenance |
|
|
|
|
Use-case Description
|
Actions: |
Customer/student(Primary), course staff, accountant |
|
Purpose: |
order the course |
|
Type: |
Abstract |
|
Importance |
Primary |
|
Technical Difficulty |
Medium |
|
Cross Reference |
Pay for the course |
|
Pre-Conditions |
Login successful |
|
Assumption: |
assume customer can order online successfully |
Use-Case interactions
|
Actor Action |
System response |
|
1. This case begins when a customer decides to order the course |
2a. System requests class is available 2b. System notifies class is not available |
|
0. Customer pays the course fee |
System sends the invoice |
Use-case interaction exceptions
Alternative exceptions
Line1: customer needs to register
Line2a: Customer cancels the order,
Line3: customer want to change their mind after paying the fee.
Line4: System send the wrong invoice.
Expanded Use Case Description
|
Actors |
Applicant Student(Primary) Course Administrator Financial Team Teaching Team |
|
Purpose |
Admission into the free training course |
|
Type |
Abstract |
|
Importance |
Secondary |
|
Technical Difficulty |
Medium |
|
Cross References |
|
|
Pre -Condition |
Registration for application is mandatory for any aspirant who wants free training |
|
Assumptions |
Aspirant is having flexible time schedule to adjust with that of teachers/trainers |
Use Case Interactions
|
Actor Action |
System Response |
|
01- The use case starts when the applicant student selects the module level that she wants to study |
System approved the admission |
|
02-Student applied in the institution |
Unique Id created by the customer |
|
|
|
Use Case Interaction Exception
|
Alternate Courses/Exceptions |
|
Notices to the applicant student to give additional details |
|
Reasonable notice to the applicant student to termination from the course |
|
More than one module can be taught to an applicant student |
Purchase system
Order course
customer
course staff
student
<<extend>>
Check course
numbers
<<includes>>
Course available
<<includes>>
Course unavailable
<<extends>>
Lost order
<<includes>>
accountant
Record order
Notify course
available
<<includes>>
<<includes>
>
Pay the course fee
Send invoice
Complete the order
Purchase system
Order
course
customer
course staff
student
<<extend>>
Check
course
numbers
<<includes>>
Course
available
<<includes>>
Course
unavailable
<<extends>>
Lost order
<<includes>>
accountant
Record
order
Notify
course
available
<<includes>>
<<includes>
>
Pay the
course fee
Send
invoice
Complete
the order
Student Free Training Selection Process
Application
Personal Details
Unique Identification Identity«uses»
Course Selection Module 01
Module 02
«extends»
«extends»
Admission Approval
Date Confirmation To Start Training
Basic
Advance
Basic
Advance
«extends»
«extends»
«extends»
«extends»
Applicant Student
*
*
* **
*
*
*
*
*
Course Administrator
Financial Team
Teaching Team
Timetable
«uses» * *
*
*
* *
Student Free Training Selection Process
Application
Personal Details
Unique
Identification Identity
«uses»
Course SelectionModule 01
Module 02
«extends»
«extends»
Admission Approval
Date Confirmation To
Start Training
Basic
Advance
Basic
Advance
«extends»
«extends»
«extends»
«extends»
Applicant Student
*
*
*
*
*
*
*
*
*
*
Course Administrator
Financial Team
Teaching Team
Timetable
«uses»
*
*
*
*
*
*
