evaluation technique for their project. 3. The menu structure for Holiday Travel
ID: 3725835 • Letter: E
Question
evaluation technique for their project. 3. The menu structure for Holiday Travel Vehicle's existing character-based system is shown here. Develop and prototype a new interface design for the system's functions using a graphical user interface. Also, develop set of real use cases for your new interface. Assume the new system will need to include the same functions as those shown in the menus provided. Include any messages that will be produced as a user interacts with your interface (error, confirmation, status, etc.). Also, prepare a written summary that describes how your interface implements the principles of good interface design as presented in the textbook.
Explanation / Answer
Solution:
Use cases for the given interface scenario
We can develop use cases for each of the separate menu that generated from main menu as given below:
I) Sales Invoice management
Use Case Name:
Request Sales Invoice management options
Scenario:
A user needs to manage sales invoice
Triggering Event:
A user enters “1” in Main menu
Brief Description:
When a user enters 1 to manage the sales invoice the sales invoice has to be developed and need to show to the user.
Actors:
The User
The System
Related use cases:
The main menu
Stakeholders:
The user
The Holiday travels vehicles
Preconditions:
The user should have a sale record to manage.
The user should exist.
Post conditions:
The user should have generated/modified the sales invoice.
Flow of Activities:
Actor
System
1. User requests for create sales invoice
.
2.User request to change sales invoice
3.User request to cancel the sales invoice
1.1 System check the sales details and generate the invoice.
1.2 display the invoice and print it on request
2.1 Take the changing values.
2.2 perform the modification
3.1 Enter the details of invoice to be canceled
3.2 Cancel the invoice
Exception Conditions:
1. If no sales are there display the exception.
2. If user not exists display the message.
II)
Vehicle Inventory management
Use Case Name:
Request Vehicle Inventory management options
Scenario:
A user needs to manage Vehicle Inventory
Triggering Event:
A user enters “2” in Main menu
Brief Description:
When a user enters 2 to manage the vehicle inventory, various operations has to be performed to manage the vehicle inventory.
Actors:
The User
The System
Related use cases:
The main menu
Stakeholders:
The user
The Holiday travels vehicles
Preconditions:
The user should have a Vehicle Inventory record to manage.
The user should exist.
Post conditions:
The user should have generated/modified the sales invoice.
Flow of Activities:
Actor
System
1. User requests for create Vehicle Inventory
.
2.User request to change Vehicle Inventory record
3.User request to delete the Vehicle Inventory record
1.1 System check the details of vehicles to be added..
1.2 Create the Vehicle Inventory
2.1 Take the changing values.
2.2 perform the modification
3.1 Enter the details of vehicle to be deleted from Vehicle Inventory
3.2 Delete Vehicles
Exception Conditions:
1. If details are not match, then display the exception.
2. If user not exists display the message.
III)
Reports management
Use Case Name:
Request report management options
Scenario:
A user needs to manage the reports
Triggering Event:
A user enters “3” in Main menu
Brief Description:
When a user enters 3 to manage the reports various operation associated with the reports has to be performed.
Actors:
The User
The System
Related use cases:
The main menu
Stakeholders:
The user
The Holiday travels vehicles
Preconditions:
The user should have records to manage.
The user should exist.
Post conditions:
The user should have generated/modified the sales invoice.
Flow of Activities:
Actor
System
1. User requests for commission a report
.
2.User request to RV sales by make report
3.User request to generate Trailer sales by make report
4. User request to generate dealer options report
1.1 System check the details to commission the report.
1.commision the report
2.1 Take the values to create the RV sales.
2.2 Create the RV sales by make report,
3.1 Enter the details to make the trailer report
3.2 Crete the trailer report
4.1 Take values for dealer options record.
4.2 Create the dealer options record.
Exception Conditions:
1. If details are not match, then display the exception.
2. If user not exists display the message.
IV)
Sales staff record maintenance
Use Case Name:
Sales staff record maintenance
Scenario:
The staff record maintenance will happens here
Triggering Event:
A user enters “4” in Main menu
Brief Description:
When a user enters 4 to maintain the sales staff record, the operations has to be performed to maintain the staff record.
Actors:
The staff manager
The System
Related use cases:
The main menu
Stakeholders:
The staff manager r
The Holiday travels vehicles
Preconditions:
There should be valid details to be modified.
The user should exist.
Post conditions:
The modified staff record.
Flow of Activities:
Actor
System
1. Add sales man record
.
2.Change sales person record
3. Delete the salesman record
1.1 Take the sales man record
1.2 Add the staff
2.1 Take the details to be changed.
2.2 perform the modification
3.1 Take the details of sales man to be deleted
3.2 Delete the staff
Exception Conditions:
1. The staff details should be valid
2. If user not exists display the message.
Use Case Name:
Request Sales Invoice management options
Scenario:
A user needs to manage sales invoice
Triggering Event:
A user enters “1” in Main menu
Brief Description:
When a user enters 1 to manage the sales invoice the sales invoice has to be developed and need to show to the user.
Actors:
The User
The System
Related use cases:
The main menu
Stakeholders:
The user
The Holiday travels vehicles
Preconditions:
The user should have a sale record to manage.
The user should exist.
Post conditions:
The user should have generated/modified the sales invoice.
Flow of Activities:
Actor
System
1. User requests for create sales invoice
.
2.User request to change sales invoice
3.User request to cancel the sales invoice
1.1 System check the sales details and generate the invoice.
1.2 display the invoice and print it on request
2.1 Take the changing values.
2.2 perform the modification
3.1 Enter the details of invoice to be canceled
3.2 Cancel the invoice
Exception Conditions:
1. If no sales are there display the exception.
2. If user not exists display the message.
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.