Get Instant Help From 5000+ Experts For
question

Writing: Get your essay and assignment written from scratch by PhD expert

Rewriting: Paraphrase or rewrite your friend's essay with similar meaning at reduced cost

Editing:Proofread your work by experts and improve grade at Lowest cost

And Improve Your Grades
myassignmenthelp.com
loader
Phone no. Missing!

Enter phone no. to receive critical updates and urgent messages !

Attach file

Error goes here

Files Missing!

Please upload all relevant files for quick & complete assistance.

Guaranteed Higher Grade!
Free Quote
wave

If you cannot have your problem solved right away, it is annoying not knowing when it will be solved.  How often will you, for instance, have to go to the printer to check whether it has got toner now?  In many cases the problem has been solved, but the user doesn't know.

Some support systems allow the user to look up their problem request in the support system to see what has happened, but it is inconvenient and how often should they look? On the other hand, there are cases where the user wants to add further information, or has solved the problem in some other way.  Here the user wants to open the problem request and record what is necessary.

Use Case Diagram and Descriptions

The use case modeling is used for identifying the interaction among the user and the system. The use case diagram represents the end users as actors (Wolters, Gerth & Engels, 2016). The functions of the system that the users access are represented through the use cases.

Within this report, the use case diagram of a Helpdesk Support System has been designed. The diagram has three actors, users, first line supporters and second line supporters. There are total eight use cases. The report includes full description of seven use cases. The estimated time use case has been neglected as it is completely system associated.

The proposed system a Helpdesk Support System. This system will store each of the user requests and share it with authorized end users. The user can access only those requests that he/she has filled. The system will have different user interface features for internal and external users. The system will allow first line supporters to assign priority to the requites. The system will store the results of each request evaluation.

Use Case Name:

Email Helpdesk

Scenario:

The user informs the helpdesk about the issue through sending email.

Triggering Event:

The user wants to inform the helpdesk about the issue

Brief Description:

The users want solution to their issues. Therefore, they inform the helpdesk supporters about the issue by sending email

Actors:

User

Stakeholder(s):

User, Support Staff

Precondition(s):

The user must be registered

Postcondition(s):

The request is valid and meaningful

Flow of Activities:

1. The user will face an issue

2. The description of the issue will be recorded

3. The issue will be sent to the helpdesk

Sub flow(s)

1. The first line supporter reject request

Exception Condition(s):

1. The issue is unknown to helpdesk supporters

2. The user cannot be identified as verified

Use Case Name:

Call Helpdesk

Scenario:

The user informs the helpdesk about the issue over the phone.

Triggering Event:

The user wants to inform the helpdesk about the issue over the phone

Brief Description:

The users want solution to their issues. Therefore, they inform the helpdesk supporters about the issue by calling.

Actors:

User, Support Staff

Stakeholder(s):

User, Support Staff

Precondition(s):

The user must have a valid issue

Postcondition(s):

The request is valid and meaningful

Flow of Activities:

1. The user will call the support staff

2. The user will tell all the issue related information to the support staff

Sub flow(s)

1. The first line supporter reject request

Exception Condition(s):

1. The issue is unknown to helpdesk supporters

2. The user cannot be identified as verified

Use Case Name:

Assign priority to request

Scenario:

Each of the user requests are assigned a priority number. Based on this number, the request will be resolved.

Triggering Event:

The first line supporter wants to organize their work.

Brief Description:

The support staff will access all the relevant information regarding the request and contact with the user to formulate accurate idea of the request. Based on how severe the issues is the priority is assigned

Actors:

First Line Support Staff

Stakeholder(s):

First Line Support Staff

Precondition(s):

The request must be handled by the Second Line Support Staff

Postcondition(s):

All the information regarding the request is present

Flow of Activities:

1. Support staff access information on request

2. Support staff contact user

3. Support staff assign the priority

Sub flow(s)

1. First line support staff provide solution

2. Second line support staff receive the request

Exception Condition(s):

1. The helpdesk has more request than they can handle

Use Case Name:

Look up problem request

Scenario:

The user will request the helpdesk to inform them about the status of the request

Triggering Event:

The users wants to know about what happened to their request

Brief Description:

The user will ask the first line supporter about the status of the request. The first line supporter will provide an answer to their query

Actors:

User

Stakeholder(s):

User, Supporter

Precondition(s):

The user must have submitted a request

Postcondition(s):

The request is not completed

Flow of Activities:

1. The user will call helpdesk and enquire about the request

2. The supporter will access the request log and identify the status

3. The supporter will inform user

Sub flow(s)

1. The supporter will store the status in a register

Exception Condition(s):

1. The request log must be in operating condition

Use Case Name:

Enter Request in HSS

Scenario:

The first line supporter will registrar the request into the helpdesk support system

Triggering Event:

The request is fund to be valid and is ready to be evaluated

Brief Description:

The first line supporter has all the information of the request. The request is stored in the system. The first line support staff and work on the request as per the assigned priority

Actors:

First line supporter

Stakeholder(s):

User, First line Supporter

Precondition(s):

The user must have submitted a request

Postcondition(s):

All the inputs fields in the request registration form must be filled

Flow of Activities:

1. The first lie supporter will access system

2. The supporter will enter user details

3. Then the supporter will enter request details and save the data

Sub flow(s)

1. The request will be sent to every authorized personnel

2. The priority assigning form will appear

Exception Condition(s):

1. The system will reject the request

2. Some of the input fields does not match with the request type

Use Case Name:

Receive Request

Scenario:

The first line support will receive a request from second line supporter or vice versa

Triggering Event:

The first line supporter is not able to process the request and send it to second line supporter

Brief Description:

If the first line supporter is not able to provide solution to a request then the request will be received by second line supporter

Actors:

Second line supporter

Stakeholder(s):

Supporters

Precondition(s):

The user who submitted a request must be active

Postcondition(s):

The second line supporter is able to provide solution to the request

Flow of Activities:

1. The second line supporter will receive a request from first line supporter

2. supporter will receive the request

Sub flow(s)

1. The second line supporter will send solution to first line supporter

Exception Condition(s):

1. More request related information is required

Use Case Name:

Provide solution

Scenario:

The first line supporters will provide the solution of the request to user

Triggering Event:

The request is completed

Brief Description:

The concern mentioned in the request is solved and ready to send to user

Actors:

First line supporter

Stakeholder(s):

Supporters

Precondition(s):

The user who submitted a request must be active

Postcondition(s):

The solution is reasonable

Flow of Activities:

1. The supporters will generate the solution

2. The supporters will provide the solution to the user

Sub flow(s)

1. The user acknowledges the solution

2. The user informs if the solution is complete

Exception Condition(s):

1. The request must contain all the required information

Conclusion:

From the above study, it can be concluded that the use case has provided a good idea regarding the interaction between the users and the system. Not all the end users are authorized to access all the functions. The system allows an end user to access the system as per authorization level. The system will store all the request related data. These data will be retrieved and evaluated as per the requirements. The first line supporter will be interacting with the users. The send line supporter will be communicating with the first line supporter only. The system may include more functionality than discussed in this report. The provided use cases are the most vital use cases.

In this report, the use case diagram has been presented to visualizing the interaction between the end users and system. The Helpdesk Support System will be collecting data from user, first line supporter and second line supporter. Each of the user will have different authorization levels. The first line support will have the authority to collect request and assign priority to it.  The second line support will access the request only if first line will not be able to resolve the request.

The use case diagram can be used for designing the system interface and improving usability. The diagram has been modified based on the reviews collected. The use case descriptions have been presented within the report. The descriptions are very useful for understanding each of the use cases.

Description

Yes

No

Use Case Diagram is appropriate

The description matches the business descriptions

All the decisions made in the design process is feasible

According to the above table, the checklist provides an overview of the successful completion of collecting, evaluating and representation of user requirements. The manager accordingly plots the checklist and completes the approval procedure.

Hajri, I., Göknil, A., & Briand, L. (2017). A change management approach in product lines for use case-driven development and testing. In 23rd International Working Conference on Requirements Engineering: Foundation for software Quality (REFSQ 2017).

Hajri, I., Goknil, A., Briand, L. C., & Stephany, T. (2015, September). Applying product line use case modeling in an industrial automotive embedded system: Lessons learned and a refined approach. In Model Driven Engineering Languages and Systems (MODELS), 2015 ACM/IEEE 18th International Conference on (pp. 338-347). IEEE.

Nassif, A. B., Capretz, L. F., & Ho, D. (2016). Enhancing use case points estimation method using soft computing techniques. arXiv preprint arXiv:1612.01078.

Wolters, D., Gerth, C., & Engels, G. (2016). Modeling Cross-Device Systems with Use Case Diagrams. In CAiSE Forum (pp. 89-96).

Yue, T., Briand, L. C., & Labiche, Y. (2015). aToucan: an automated framework to derive UML analysis models from use case models. ACM Transactions on Software Engineering and Methodology (TOSEM), 24(3), 13.

Cite This Work

To export a reference to this article please select a referencing stye below:

My Assignment Help. (2020). Use Case Modeling For Helpdesk Support System. Retrieved from https://myassignmenthelp.com/free-samples/itsc-2439-helpdesk-support-system.

"Use Case Modeling For Helpdesk Support System." My Assignment Help, 2020, https://myassignmenthelp.com/free-samples/itsc-2439-helpdesk-support-system.

My Assignment Help (2020) Use Case Modeling For Helpdesk Support System [Online]. Available from: https://myassignmenthelp.com/free-samples/itsc-2439-helpdesk-support-system
[Accessed 22 February 2024].

My Assignment Help. 'Use Case Modeling For Helpdesk Support System' (My Assignment Help, 2020) <https://myassignmenthelp.com/free-samples/itsc-2439-helpdesk-support-system> accessed 22 February 2024.

My Assignment Help. Use Case Modeling For Helpdesk Support System [Internet]. My Assignment Help. 2020 [cited 22 February 2024]. Available from: https://myassignmenthelp.com/free-samples/itsc-2439-helpdesk-support-system.

Get instant help from 5000+ experts for
question

Writing: Get your essay and assignment written from scratch by PhD expert

Rewriting: Paraphrase or rewrite your friend's essay with similar meaning at reduced cost

Editing: Proofread your work by experts and improve grade at Lowest cost

loader
250 words
Phone no. Missing!

Enter phone no. to receive critical updates and urgent messages !

Attach file

Error goes here

Files Missing!

Please upload all relevant files for quick & complete assistance.

Other Similar Samples

support
Whatsapp
callback
sales
sales chat
Whatsapp
callback
sales chat
close