Professional Documents
Culture Documents
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)
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
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
Actor User/customers
End condition The system helps users/customers by giving reservation form to the users/customers
Special Requirement --
Actor User/Customers