Hello There! I would like to get your help on making Expanded Use case (detailed

Question

Hello There!

I would like to get your help on making Expanded Use case (detailed use case description) of the following use cases:

Use Case # 3:

Use Case Name: - Register Complaints

Scope: IESCO online system (user goal)

Type: Primary

Primary Actor: - Customer

Description: The user will authenticate through his login module and can register complaints regarding billing or personal information

Considering the following Use case diagram:

Project brief detail: (just for a little understanding of the project)

We liked to build a IESCO (Islamabad Electric Supply Company ) online system. This system should be able to store details of each customer. Also it should be able to show bills to the respective customer. Then the customer should be able to pay the bill and so on.
To add some extra functionality (incase the scope is less ) then we can add some extra system for IESCO internal workforce. Details of each employee , attendance , salary etc will be stored . Employee and his/her senior will be able to see that...The aim is to build a non error-prone automated system for the convenience of customers and employees and to make an online system for billing and so on.....

Now, I need the "expanded use case"(of the above given use case) which includes:

   1- Main success scenario

2- Alternate Scenarios( Extensions)

     

An example of an Expanded use case (from a Point-Of-Sale System):

UseCase: Process sale (A use case of NextGen POS system)

Success scenario: A customer arrives at a checkout with items to

purchase. The cashier uses the POS system to record each purchased

item. The system presents a running total and line-item

details. The customer enters payment information, which the

system validates and records. The system updates inventory.

The customer receives a receipt from the system and then leaves

with the items.

Alternate Scenarios:

1- If the customer paid by credit, and the reimbursement transaction to their credit

Account is rejected, inform the customer and pay them with cash.

2- If the item identifier is not found in the system, notify the Cashier

and suggest manual entry of the identifier code (perhaps it is

corrupted).

3- If the system detects failure to communicate with the external

tax calculator system, ... etc

THE "USE CASE" THAT WE HAVE TO EXPAND IS: Register Complaints

The use case diagram is as follows View and Print Bills Adjust Privacy and Do Online Payment Create new Predict Bill Customer View and Update Accept and Generate Transaction Employee View Job and Salary history Ability to Track Review Scores and Review Dates Send Emails and See performance and Employees Approve Increment in Employee Salary Manager

Explanation / Answer

ANSWER

USECASE: Register Complaints

Scope: IESCO online system

Type: Primary

Primary Actor: Customer
Description: The user will authenticate through his login module and can view the register complaint tab and submit the complaint.
Success scenario:

Customer can authenticate and login to IESCO online system and then he can visit the complaint tab and write the complaint and submit it.

The system successfully authenticates the user and displays home page which has links to following options:

The user selects compliant option.

When customer click on complaint tab then it show the comment box and submit option

then after writing of complaint then we can submit the complaint then it popups the succesfully registered your complaint.

Alternate Scenarios:

Thank You

Related Questions

Navigate

• Browse (All)
• Browse H
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.