You are on page 1of 4

MIDTERM

Analysis and Design of Information System


By: Salsabila Irbah (05111942000007)
Theoretical Questions
1. In your opinion, this case study can be categorized as what type of system (TPS, ES, KWS,
etc)? Explain your reason to categorize it into this type of system!

I think this case study is categorized as Transaction Processing System (TPS). TPS is
a software system, or software/hardware combination that supports transaction processing. TPS
is in operational level that possible for organization can interact with external environment.
TPS is for processing data with big quantity for daily business transaction. So, I think this case
study’s category is Transaction Processing System(TPS).

2. In your opinion, what development technique (waterfall, agile, etc) is suitable in building the
system for the case study? Explain your reason?

I think waterfall is the best development technique for building this system. It begins
eith analysis needs adapted to systems are go at wisma tamu ITS, design system and software,
Implementation, Integration and Testing, and Operation and Maintenance. So for the analysis,
the team analyses the requirements and gather information for the requirement, etc. After that
design, The software developer design a technical solution to the problem set out by the product
requirements, including scenarios, layouts, and data models. Then, Implementation, the
software making is break into small modules that will be join in the next step. In this step also
we do more checking if the the module already fulfil the requirements that we want or not.
Next, Integration and Testing, we combine the modules that we made before. And then we do
testing to know if the software design is already compatible with what we want and if whether
there still errors or not. Last is operation and Maintenance, in here the software are done and
will be operated with the user. We use waterfall method because waterfall method is is the most
reliable and used by the developers, suitable for developing system which is generic, and project
system would easily controlled and scheduled well.
3. Analyze the case study, then define its business, user, functional and non-functional
requirements!
Bussiness Requirement User/Customer Requirement Functional Requirement Non-Functional Requirement
1. The system allows customer/user to
book by inputting user data (choose wisma,
check-in date, check-out date, and user 1. The system worked in all browser
general information)

1. User/customer can book a room easily


2. The system allows user/customer freely
in each wisma tamu ITS (Flamboyan,
do reservation/book a room 2.The system can be accessed anytime
Bougenville, Jasmine)
(24/7)

3. The system allows user/customer to


choose the transaction type, including the
transaction code 3. The system can be accessed in high
speed

4. The system can always update the room


availability in each wisma

4.The system can record customer data


2. User/customer can look the room who do reservation/booking
Facilitate customer/user to 5. The System must insert wisma catalog
availability in each wisma, wisma details
book a room in wisma tamu information (profile, photos, room type,
including the photo, rules, terms &
ITS facility, room price/night, location)
conditions for booking a room

6. The system can give information about 5. The system can differentiate the
the rules, terms and conditions for booking transaction type that the customer use
in wisma tamu ITS

7. The system allows user/customer to


3. User/customer can contact the wisma
look for the phone and whatsapp number 6. The system can be accessed using PC or
ITS
and admin email wisma tamu ITS mobile device

4.User/customer can track the payment


8. The system can process, search, and
status for booking the room in wisma tamu
display data of user payment status
ITS

5.User/customer can give feedback and


9. The system can display the
complaint about the facility, services, and
user/customer's feedback and complaint
experience in wisma tamu ITS

Practical Questions
1. Create a use case diagram based on the interview result to the user of Wisma Tamu ITS. Next,
choose two of the main use cases and create the use case specifications (add the alternative
flow if needed).
Use Case Specifications
Use Case Make Reservation
No UC-001

Description User/customers book/reserve a room

Actor User/customers

Start condition Users/customers want to book a room

End condition The system helps users/customers by giving reservation form to the users/customers

1.Users/Customers open the website


2. The system will show the dashboard of the website
3.Users/Customers click the reservation form
Normal Flow
4. The system open the reservation form page
5. Users/Customers select wisma (bougenville, jasmine,flamboyan)
6. Users/Customers select room type
A1. users/customers want to change wisma
1. Enter the history
Alternative Flow
2. click the last reservation form
3. open the reservation form and fill the remaining part

Special Requirement --

Use Case Choose Transaction Type


No UC-002

Description User/customers choose how to pay

Actor User/Customers

Start condition Users/customers already book/reserve a room

End condition Users/Customers transaction is verified

1.Users/Customers already fill the reservation form


2. The system will show the payment method
3.Users/Customers choose the transaction type
Normal Flow
4. The system calculate the total price
5. Users/Customers pay according to the transaction type they picked
6. The system verify the transaction
A1. users/customers already paid but the system does not verify
1. Enter the payment
Alternative Flow 2. open the payment status
3. click report
4. The receptionist will check manually
Special Requirement --
2. Create activity diagram for the case study

You might also like