Download Use Case Analysis for Tourism Management System: Customer Interactions and more Assignments Computer Science in PDF only on Docsity!
(Affiliated to Tribhuwan University)
A
Lab Report 2
On
Software Engineering
Lab Report No. 2
Submitted by: Submitted to:
Name : Sagun khadka Faculty Name: Bijaya Mishra
Batch: 2075 Subject: CACS253 Software
Year: II Semester: IV Engineering
Submission Date: 23 th^ Nov 2020 Signature of Faculty:
Customer Classes and Characteristics
1. Customer Classes:
There are four customer levels in Tourism Management system. System Admin Agents System Customer Customer
2. Characteristics of customer classes:
2.1 System Admin:
System admin monitors and authorizes all the handled by the other department of the system. System admin is the one who operates the system, modifies, add or delete the customer records in the database. The admin monitors daily, weekly, monthly report. As the main authorized persons of the company and the system, system admin has the ability to manage the other customers including their customer levels and privileges. Taking backups of the system and restoring system can also be done by the owner.
2.2 Agents:
Agents of tourism management are the various individuals and organisations that carry out or facilitates tourism developments at international, national, and local levels. There are private sector and public sector agents which facilitates the customer about the information about travel and tourism. Agents are the persons who creates tours packages, publishes tours, and checks enquiries from the customers.
2.3 System customers:
System customers are simply system managers who are responsible for managing resources available in tourism management system. The reason to customer managers is to reduce work load done by the system admin. System customers manage various tour packages, transportation, tours etc.
2.4 Customers:
Customer’s role has the least accessibility to the system functions as they are only responsible for taking services from the tourism. They choose the tourism package and sign up for the tourism. They also have the authority to cancel tour under any circumstances.
3. Use Case Diagram:
A use case diagram is a dynamic or behaviour diagram in UML. It is the core concept of Unified Modelling Language (UML). Use case diagrams model the functionality of a system using actors and use cases. Use cases are a set of actions, services, and functions that the system needs to perform. In this context, a "system" is something being developed or operated, such as a web site. The "actors" are people or entities operating under defined roles within the system. A use case diagram at its simplest is a representation of a customer's interaction
Use Case ID UC-^001
Use Case Name Login
Actors Customer, Agents, System customer, System admin, Tourism
system
Brief
Description
Allows customer to login in the system if not, signup to do actions. The use case begins when any customer tries to login into the system through the various recommendations of the agents. The customer inputs details of himself and selects packages. If the system approves the login, the customers allowed to perform required actions.
Triggers The customer wants to login in the system from one of his/her
account.
Preconditions 1.^ The system should be operational.
- The customer must be registered customer.
- The customer must have a unique password and customer name.
Normal Flow 1.^ The use case begins when the customer goes into the
system.
- Customer login in the system.
- Customer enters the details on the login/signup form.
- The system verifies the entered username and password against their registered information.
- Customer enters to the system
- Customer case ends successfully.
Alternate Flow 2A. Not a registered user.
3A. System first ask user to sign up. 4A1. Invalid username or password. 4A2. User is requested to re-enter username and password. 4A3. Customer are requested to seek help and support.
Key scenarios A.^ Successful Scenarios
- Sign up and login successful.
- Entry into the system is successful. B. Unsuccessful scenarios
- Fail due to authentication failure.
- Fail due to invalid customer detail.
- Fail due to inadequate critical resources.
- Fail due to unresponsive server/server error.
Post Conditions A.^ Successful Conditions
- User enters into the system.
- User performs the required actions. B. Failure conditions
- Non-responding System
Use case 2:
Use Case ID UC-^02
Use Case Name Update Profile
Actors Customer, system user, system admin, Tourism System
Brief
Description
Allows user to login in the system. Any registered user can update their profile anytime. All these activities are recorded by the Tourism system.
Triggers The user wants to update the profile from one of his/her account.
Preconditions The system is operational.
The user has a password and username to enter in the system.
Normal Flow 1.^ The use case begins when the customer enter into the system to change
profile.
- The tourism system provides login option to user.
- A user enters his/her username and password.
- The system verifies the user’s entered username and password against the registered information.
- The system allows the customer to view their profile.
- The system provides edit profile option.
- The user chooses edit profile.
- User updates their profile.
- User saves the changes.
- Use case ends successfully.
Special
requirements
- The user shall be registered in order to get a unique password and user name.
- The system shall keep a log including date and time, all complete history of performed actions.
Use Case Name Booking Package
Actors Customer,^ system user, Tourism System, agent
Brief
Description
Allows any registered customer to book tourism package of their choice. The use case begins when a customer gets notification from system users through the help of agents and login in the system to book tourism package. If the customer is not registered then, at first customer should register themselves with some details then can book tourism package easily. All these activities are recorded by the system users of tourism management system.
Triggers A customer wants to book a tourism package^ from one of his/her account.
Preconditions The system should be^ operational.
A customer should have a unique password and username to enter in the system. A system user shows different types of tourism packages.
Normal Flow 1.^ The use case begins when the customer login to book a tourism
package.
- The tourism management system provides sign up or login option to user.
- A customer enters his/her username and password.
- The system verifies the customer’s entered username and password against the registered information.
- The system allows the customer to view different types of tourism packages available in the system.
- The system provides book package option.
- The customer chooses book package.
- Customer pays for the booked package.
- The system sends a confirmation mail to the customer.
- Customer accepts it.
- Use case ends successfully.
Alternate Flow 3A1. If the customer is not registered in the system, send a registration form
to the customer. 4A1. Invalid username or password. 4A2. Customer is request to re-enter the username and password. 4A3. If the system doesn’t verify the customer after multiple attempts, customer is asked to seek the help and support. 7A1. The chosen type of tourism package is expired. 8 A1. Through which mode customer wants to pay for room. 10 A1. Resend mail to the customer. 11A2. Customer fails to accept the mail.
Key Scenarios A.^ Success Scenarios
- Enter username and password
- Enter into the system
- Choose and book tourism package.
- Provide identification.
- Make payment. B. Failure Scenarios
- Fail due to authentication failure
- Fail due to invalid username and password.
- Fail due to non-valid identification proof.
- Fail due to insufficient balance.
- Fail due to non-responding tourism system system
Post Conditions A.^ Successful Conditions
- User enters into the system.
- User performs the required actions.
- The tourism system has received the identification proof and amount for the chosen tourism package.
- The system has sent the package information to customer. B. Failure Conditions
- Non-responding System
Special
Requirements
- The customer shall be registered in order to get a unique password and username.
- Customer shall accept the confirmation mail.
- The system shall keep a log, including date and time, customer details, all complete history of performed actions. Use case 4:
Post Conditions C.^ Successful Conditions
- Enters into the system.
- User performs the required actions.
- User and the Tourism system save the made updates. D. Failure Conditions
- Fail due to bad network connection.
- Fail due to server error.
Special
Requirements
- The user cannot update their profile without login.
- The system shall keep a log, including date and time, user details, all complete history of performed actions. Use case 4:
Use Case ID UC-^05
Use Case Name Make Payment
Actors Customer, Tourism System, system user
Brief
Description
Allows any registered customer to make payment after booking tourism package of their choice. If the customer is not registered then at first customer should register themselves with some details then can book tourism package easily. The customer can make payments only after providing identification proof for booking purpose. All these activities are recorded by the Tourism system.
Triggers A customer wants to make payment for the booked tourism package from
one of his/her account.
Preconditions The system is operational.
A customer has a unique password and username to enter in the system. A customer book a tourism package.
Normal Flow 1.^ The use case begins when the customer enter into the system to make
payments.
- The Tourism system provides login option to user.
- A customer enters his/her username and password.
- The system verifies the customer’s entered username and password against the registered information.
- The customer chooses book tourism package option.
- Customer selects the required package.
- Customer pays for the booked package.
- The system sends a confirmation mail to the system.
- Customer accepts it.
- Use case ends successfully.
Alternate Flow 4A1. Invalid username or password.
4A2. Customer is request to re-enter the username and password. 4A3. If the system doesn’t verify the customer after multiple attempts, customer is asked to seek the advice. 7A1. Customer can book one or more tourism packages. 7A2. Through which mode customer wants to pay for package. 8A1. Customer doesn’t get confirmation mail. 8A2. Resend mail to the customer. 10A1. Customer fails to accept the mail.
Key Scenarios A.^ Success Scenarios
- Enter username and password.
- Enter into the system.
- Choose and book tourism package.
- Make payment. B. Failure Scenarios
- Fail due to authentication failure.
- Fail due to invalid username and password.
- Fail due to inadequate critical resources.
- Fail due to insufficient balance.
- Fail due to non-responding tourism system
Post Conditions A.^ Successful Conditions
- Enters into the system.
- User performs the required actions.
- The hotel system has received the identification proof and amount for the chosen tourism package.
- The system has sent the package information to customer. B. Failure Conditions
- Fail due to non-valid identification proof.
- Fail due to inadequate critical resources.
- Fail due to insufficient balance.
