DSTR

TP032057 BSc(Hons)Software Engineering CT077-3-2-DSTR
Contents
List of Figures .......................................................................................................................................... 2
1.0 Introduction ...................................................................................................................................... 3
2.0 Objectives.......................................................................................................................................... 4
3.0 Aims................................................................................................................................................... 4
4.0 Diagrams ........................................................................................................................................... 5
4.1 Use case diagram .......................................................................................................................... 5
4.1 Use case description ..................................................................................................................... 6
4.2 Sequence Diagram ...................................................................................................................... 10
4.2.1 Login (For Staff) .................................................................................................................... 10
4.2.1 View Call History .................................................................................................................. 11
4.2.2 View Report.......................................................................................................................... 12
4.2.3 Submit report ....................................................................................................................... 13
4.2.3 Delete report........................................................................................................................ 14
4.3 Activity Diagram .......................................................................................................................... 15
5.0 Functionality ................................................................................................................................... 18
6.0 Interface .......................................................................................................................................... 19
7.0 References ...................................................................................................................................... 28
1
List of Figures
Figure 1: Use Case Diagram .................................................................................................................... 5
Figure 2: Sequence Diagram (Login) ..................................................................................................... 10
Figure 3: Sequence Diagram (Calls History) .......................................................................................... 11
Figure 4: Sequence Diagram ( View Report) ......................................................................................... 12
Figure 5: Sequence Diagram (Submit Report) ...................................................................................... 13
Figure 6: Sequence Diagram (Delete Reports) ...................................................................................... 14
Figure 7: Activity Diagram ( Login ) ....................................................................................................... 15
Figure 8: Sequence Diagram (Calls History) .......................................................................................... 16
Figure 9: Activity Diagram (View Report).............................................................................................. 17
Figure 10: Login Page ............................................................................................................................ 19
Figure 11: Wrong username and password .......................................................................................... 19
Figure 12: Code snippet for login .......................................................................................................... 20
Figure 13: Staff Menu ........................................................................................................................... 20
Figure 14: Staff Menu (View Calls) ........................................................................................................ 21
Figure 15: Staff Menu (View Report) .................................................................................................... 21
Figure 16: Example code for Viewing.................................................................................................... 22
Figure 17: Report Submission ............................................................................................................... 22
Figure 18: Sample code for saving to database .................................................................................... 23
Figure 19: Creating a link list node........................................................................................................ 23
Figure 20: Creating Class Stack ............................................................................................................. 23
Figure 21: Push Operation .................................................................................................................... 24
Figure 22: Pop Operation ...................................................................................................................... 24
Figure 23: Sample Output - Displaying data in the linked list ............................................................... 24
Figure 24: Pop Operation ...................................................................................................................... 25
Figure 25: Push Operation .................................................................................................................... 25
Figure 26:Queue Struct ......................................................................................................................... 25
Figure 27: Dequeue Operation ............................................................................................................. 26
Figure 28: Enqueue Operation .............................................................................................................. 26
Figure 29: Sample output for Queue .................................................................................................... 27
2
1.0 Introduction
Data structures has often been about the practice of finding the most efficient and fastest
way of storing and managing data. Different data structures are used in almost every
professional application out there to maximise efficiency and accuracy of the application
carrying out its duties. A data structure is basically a logical interpretation of the blueprint of
ways that data can be arranged to. Common data structures are like arrays, linked list, queues,
stacks, binary trees, and graphs. Algorithms are the mechanism in which is used to manipulate
and control these structures thru searching and arranging. Data structures are vital, for the needs
of an application that require good memory management so carry out its functions well
Donut Customer Service system is created for users with problems with their gadgets
to call to their hotline and lodge a report. The customers will call and report about their
problems while the users of this system will use this system to serve the customer better. The
users of this system need to log in with their credentials which will be provided by the HR
department. The users then can view the reports, view their call history etc. The users of the
system will also have the advantage of deleting their database to avoid clusters of already
attended reports.
3
2.0 Objectives
1. To create a system for a call centre implementing data structures for pushing and
popping reports submitted by customers.
2. To create a system for customer service staff to help them view their data needed from
the system using a user friendly Graphical User Interface.
3. To create a system for the call centre to receive reports of the customers and allowing
users to put queue and stacks on priority.
3.0 Aims
Donut Customer Service is developed for the customer service to enhance and quicken their
services and avoid keeping customers on hold for too long. This helps the staff to utilize their
time, and helps them prioritize their customer reports. This system also is aimed to help users
to submit report easily as well as help them view all data easily without having a hassle to go
through many pages. The system is also designed in a user friendly which helps users to
navigate smoothly through the pages.
4
4.0 Diagrams
4.1 Use case diagram
Submit Reports
View Customer calls

<<extend>>
Customer Service Staff
View Cutomer Reports
Delete Reports
Figure 1: Use Case Diagram
5
4.1 Use case description
Use Case Name Submit Reports
Summary Staff can submit the reports of the complain of the customers and the
system will save the details into the database.
Actor Call System Staff
Pre-condition Staff must already be registered for application usage by the Human
Resource Department, and has received the default username and
password.
Main Sequence 1. Staff loads up the application on the designated PC that is
addressed to them.
2. Staff must click ‘Login’ and enter the username and password
in the required fields.
3. Upon successful login, the student will be redirected to the
‘Staff Main Menu’.
4. Staff will then click on ‘Submit Report’ button. Staff will be
navigated to the Report page.
5. Staff fills in report and click ‘Submit button.
Alternative Sequence 2a. Staff must request for their username and password for first time
login; which will be emailed to the student’s registered email account.
3a. If login fails, student will be prompted to enter the username and
password again.
4a. The report fields must be all filled up in order to be saved in the
database.
Post-condition The staff will remain logged in after 30 minutes of inactivity. After
that, the staff must login again to continue using the system.
Table 1 Use case description (Submit Report)
6
Use Case Name View Calls
Summary Staff can view the call history that has been attended by the staff using
the system.
password.
Main Sequence 1. Staff must click ‘Login’ and enter the username and password
in the required fields.
3. Staff will then click on ‘View Calls’ button.
4. Call History will load on the screen
login; which will be emailed to the student’s registered email account.
password again.
4a. Calls history can’t be edited or deleted.
that, the staff must login again to continue using the system. .
Table 2 Use Case Description (View Calls)
7
Use Case Name View Reports
Summary Staff can view the reports that has been attended by the staff using
the system.
password.
Main Sequence 1. Staff must click ‘Login’ and enter the username and
password in the required fields.
3. Staff will then click on ‘View Reports’ button.
4. Call History will load on the screen
login; which will be emailed to the student’s registered email
account.
password again.
4a. Calls history can’t be edited or deleted.
Table 3 Use Case Description ( View Reports)
8
Use Case Name Delete Reports
Summary Staff can Delete the reports that has already been attended by the
staff using the system.
password.
Main Sequence 1. Staff must click ‘Login’ and enter the username and
password in the required fields.
3. Staff will then click on ‘Delete Reports’ button.
4. The database will be cleared.
login; which will be emailed to the student’s registered email
account.
password again.
9
4.2 Sequence Diagram
4.2.1 Login (For Staff)
Staff System Database
Open Login page
Loads Staff Menu
Input Credetials
Verify Credentials
Confirmation
Redirect to staff menu
Figure 2: Sequence Diagram (Login)
10
4.2.1 View Call History
Load System Staff Menu
Staff Menu
Select View Calls
Finds Call History

Sends Call History
Displays Call History
Figure 3: Sequence Diagram (Calls History)
11
4.2.2 View Report
Staff Menu
Select View Report
Finds Reports
Sends Reports
Displays Reports
Figure 4: Sequence Diagram ( View Report)
12
4.2.3 Submit report
Staff Menu
Submit Report Page
Load Page
Input data of report
Saves data
Save confirmation displays
Figure 5: Sequence Diagram (Submit Report)
13
4.2.3 Delete report
Load Staff Menu
Staff Menu
Delete Reports
Data Removal
Confirmation
View Message
Figure 6: Sequence Diagram (Delete Reports)
14
4.3 Activity Diagram
Login
Open up System on
Loads System
PC
Click Login Loads Login Page
Input Username &

Password
Capture Credentials
Validates Credential
Data
No
Yes
Redirect to Staff Correct Credentials ?

Menu
Phase
Figure 7: Activity Diagram ( Login )
15
View Calls
Load Staff Menu
Select View Call
Run Search Return Results
Display Call History
View Call History

Phase
Figure 8: Sequence Diagram (Calls History)
16
View Report
Load Staff Menu
Select View Report
Run Search Return Results
Display report
View Report
Phase
Figure 9: Activity Diagram (View Report)
17
5.0 Functionality
1. Login page – Users have to posses credentials in order to log into the system. The
credentials can only be released by the Human resource department or the system
admin.
2. Staff menu – once the staff have gained access to the system, the user can use the
system to please their customers.
3. View Calls – The user can view their call history that has been made to the company
on the short time period. The system reads the data from the database and displays in
on the system.
4. View Reports – The systems allows the user to view the reports that has been made by
the customer that has been saved in the database. The system displays the data onto the
system once it’s retrieved from the database.
5. Submit Feedback – The users can submit report of the customers who calls by using
this system. The system will then save the data into a database, which will be then
retrieved later by the user.
6. Delete History – the users can delete cluttered data in the database that takes up space
and slows down the system.
18
6.0 Interface
Figure 10: Login Page
Once the system is booted, the login page as above appears for the user to insert the credentials.
Figure 11: Wrong username and password
19
When the user enters a wrong combination of password or username, the system will display
and error message that prompts the user to input the username and password again to allow the
system to scan and verify the credentials again.
Figure 12: Code snippet for login
Figure 13: Staff Menu
20
Once the login credentials are verified, the system then brings the user to the staff main menu.
The staff menu has three function:
1. View Calls
2. View Report
3. Submit report
Figure 14: Staff Menu (View Calls)
Figure 15: Staff Menu (View Report)
21
Figure 16: Example code for Viewing
Figure 17: Report Submission
22
Figure 18: Sample code for saving to database
The system will then use stack and queue to find the report and display using push and pop.
For the stack, sample codes are as below:
Figure 19: Creating a link list node
Figure 20: Creating Class Stack
23
Figure 21: Push Operation
Figure 22: Pop Operation
Figure 23: Sample Output - Displaying data in the linked list
24
Figure 24: Pop Operation
Figure 25: Push Operation
Figure 26:Queue Struct
25
Figure 27: Dequeue Operation
Figure 28: Enqueue Operation
26
Figure 29: Sample output for Queue
27
7.0 References
c++ - Append text in richTextBox from more sources in C - Stack Overflow. 2018. c++ -
Append text in richTextBox from more sources in C - Stack Overflow. [ONLINE] Available
at: https://stackoverflow.com/questions/14604559/append-text-in-richtextbox-from-more-
sources-in-c. [Accessed 18 December 2017].
Exit() Function, Terminate Program Execution - C++ Control Structures Tutorial. 2018. Exit()
Function, Terminate Program Execution - C++ Control Structures Tutorial. [ONLINE]
Available at: https://www.hscripts.com/tutorials/cpp/exit-function.php. [Accessed 18 January
2018].
c++ - Writing linked list to txt file(Saving process) - Stack Overflow. 2018. c++ - Writing
linked list to txt file(Saving process) - Stack Overflow. [ONLINE] Available at:
https://stackoverflow.com/questions/36944070/writing-linked-list-to-txt-filesaving-process.
[Accessed 19 December 2017].
c++ - How to write a File with text from a TEdit(Textbox) - Stack Overflow. 2018. c++ - How
to write a File with text from a TEdit(Textbox) - Stack Overflow. [ONLINE] Available at:
https://stackoverflow.com/questions/21419228/how-to-write-a-file-with-text-from-a-
tedittextbox. [Accessed 27 December 2017].
c++ - How to write a File with text from a TEdit(Textbox) - Stack Overflow. 2018. c++ - How
to write a File with text from a TEdit(Textbox) - Stack Overflow. [ONLINE] Available at:
https://stackoverflow.com/questions/21419228/how-to-write-a-file-with-text-from-a-
tedittextbox. [Accessed 3 January 2018]
c++ - (MFC) CListBox -> Edit Item in List? - Stack Overflow. 2018. c++ - (MFC) CListBox -
> Edit Item in List? - Stack Overflow. [ONLINE] Available at:
https://stackoverflow.com/questions/5626147/mfc-clistbox-edit-item-in-list. [Accessed 8
January 2018].
28

DSTR

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

DSTR

Hochgeladen von

Copyright:

Verfügbare Formate

TP032057 BSc(Hons)Software Engineering CT077-3-2-DSTR

View Customer calls

Customer Service Staff

View Cutomer Reports

Figure 1: Use Case Diagram

4.1 Use case description

Use Case Name Submit Reports

Actor Call System Staff

Table 1 Use case description (Submit Report)

Use Case Name View Calls

Actor Call System Staff

Table 2 Use Case Description (View Calls)

Use Case Name View Reports

Actor Call System Staff

Table 3 Use Case Description ( View Reports)

Use Case Name Delete Reports

Actor Call System Staff

4.2 Sequence Diagram

4.2.1 Login (For Staff)

Staff System Database

Open Login page

Loads Staff Menu

Redirect to staff menu

Figure 2: Sequence Diagram (Login)

4.2.1 View Call History

Staff System Database

Load System Staff Menu

Select View Calls

Finds Call History

Displays Call History

Figure 3: Sequence Diagram (Calls History)

4.2.2 View Report

Staff System Database

Load System Staff Menu

Select View Report

Figure 4: Sequence Diagram ( View Report)

4.2.3 Submit report

Staff System Database

Load System Staff Menu

Submit Report Page

Save confirmation displays

Figure 5: Sequence Diagram (Submit Report)

4.2.3 Delete report

Staff System Database

Load Staff Menu

Figure 6: Sequence Diagram (Delete Reports)

4.3 Activity Diagram

Staff System Database

Click Login Loads Login Page

Input Username &

Redirect to Staff Correct Credentials ?

Figure 7: Activity Diagram ( Login )

Staff System Database

Load Staff Menu

Select View Call

Run Search Return Results

Display Call History

View Call History

Figure 8: Sequence Diagram (Calls History)

Staff System Database

Load Staff Menu

Select View Report

Run Search Return Results

Figure 9: Activity Diagram (View Report)