KF7011 Systems Analysis and Design With UML

Write a use case description for the booking campus lessons and site visits.  You should include the recording of all customer and student details and making appoitnments for the preliminary site visit.  Your description should follow the house style as taught on the module.

em and the relationship between the system and the user is illustrated graphically in this diagram. It assists the development team in understanding the system functionalities in a better manner (Secchi, Bonfe and Fantuzzi, 2007).

There are various use cases that will be involved in the PSC information system as well. These use cases include Request for Session, Sign In/Sign Up, Register new student, Make Payment, Manage Balance Payment, Manage Booking, Generate Confirmation Letter, Manage Pickup/Drop, On-Campus, Site Visit, Manage Appointment, Manage Staff, Manage Services, and Generate Report.

The users that will be involved with the information system will include customer, administrative staff, teaching staff, staff driver, and director. 

Use Case Description 

Request for Session

It is the use case in which the customer will place a request for session. The session may be on-campus or site-visit. There will be an option that will be provided to the customer to select out of the two and extension will be made to on-campus or site-visit use cases as per the option selected by the customer. This use case is also connected with manage booking use case. It is because the incorporation will be done as per the availability of the teaching staff and number of members if a site visit is requested. The actors involved in this use case are the system and the customer (Zheng, Feng and Zhao, 2014).

Sign In/Sign Up

In order to make use of the information system for PSC and access the different functions incorporated in the system, signing in to the system will be needed. The use case includes the signing in of the customer in the system in case of an existing customer. In case of a new customer, there will be an option provided to sign up. The basic details will be required to be filled for creating a new account and the credentials will be generated. The unique and valid credentials shall be used to sign in to the system. The actors involved in the use case will be the system and the customer.

Register New Student

In the case of a new customer, there will be an option provided to sign up. The basic details will be required to be filled for creating a new account and the credentials will be generated. The unique and valid credentials shall be used to sign in to the system. The actors involved in the use case will be the system and the customer (Wang, Liu and Lu, 2011).

Make Payment

There is a fee that is associated with every session that is attended by a customer. There will be payment gateways that will be integrated in the information system which would allow the customer to pay using different modes of payment, such as credit/debit cards, electronic wallets, and likewise. The use case includes the interaction between the system and customer while making payment for the session at the PSC.  There is a 20% deposit that is to be made at the time of requesting for a session for weekly or group sessions (Gemino and Parker, 2009).

Manage Balance Payment

The customer pays 20% deposit at the time of booking a session. The rest 80% may be paid afterwards at any time before attending the session and the management of the balance payment would be done by the administrator. The administrator will keep a record of the balance payment for each of the customer and the payment request will be automatically made after the deposit is paid. The use case describes the interaction between the administrative staff member and the system while tracking the balance payment and the management of the same.

Manage Booking

Use Case	Manage Booking
Description	The booking for a session is confirmed only when a deposit of 20% is made by the customer in advance. In case there is no deposit fee paid, the booking is automatically cancelled. The system will check for the availability of the teaching staff when a new booking request is received. Also, in the case of site-visits, the availability of staff drivers will also be validated before the booking is confirmed to the customer (Jakimi and Koutbi, 2009).
Pre-Condition	The management of the booking is related and connected with the two other use cases as manage balance payment and request for session.
Actors	System, Customer, Administrative staff member
Procedure	1. Request for session (A1) 2. Selection of option 3. Availability check 4. Get customer details (A2) 5. Payment for session (A3)
Fail Condition	A1: Session not available A2: New customer is asked to register in the system. A3: Non-payment of the session fee
Success Condition	Payment of session fee and availability of the staff

Generate Confirmation Letter

The customer pays 20% deposit at the time of booking a session. The rest 80% may be paid afterwards at any time before attending the session and the management of the balance payment would be done by the administrator. The administrator will keep a record of the balance payment for each of the customer and the payment request will be automatically made after the deposit is paid. The booking for a session is confirmed only when a deposit of 20% is made by the customer in advance. In case there is no deposit fee paid, the booking is automatically cancelled. The system will check for the availability of the teaching staff when a new booking request is received. Also, in the case of site-visits, the availability of staff drivers will also be validated before the booking is confirmed to the customer. Once the availability is validated and complete payment is received, the administrative staff will generate a confirmation letter for the customer. The actors involved in the use case are the administrative staff and the system (Almendros-Jimenez and Iribarne, 2006).

Manage Pickup/Drop

The customer may place request for pickup/drop at the time of request for a new session. The management of the pickup and drop will be done by the staff driver. It will be carried out on the basis of the availability as there are only two staff drivers that are currently engaged with the academy. The use case involves the staff driver and the system as the actors in this case.

On-Campus

It is the use case in which the customer selects an option while placing a request for session. The session may be on-campus or site-visit. There will be an option that will be provided to the customer to select out of the two and extension will be made to on-campus or site-visit use cases as per the option selected by the customer. The actors involved in the use case will be the customer and the system.

Site Visit

Use Case	Site Visit
Description	It is the use case in which the customer selects an option while placing a request for session. The session may be on-campus or site-visit. There will be an option that will be provided to the customer to select out of the two and extension will be made to on-campus or site-visit use cases as per the option selected by the customer (Kaur, 2011).
Pre-Condition	Request for Session
Actors	System, Customer
Procedure	Begin Request for session Selection of option as Site Visit End
Fail Condition	Unavailability of the staff
Success Condition	Payment of session fee and availability of the staff

Manage Appointment

The appointment will be managed by the administrative staff as soon as a request for session will be received. The availability of the teaching staff for site visit will be checked and the response will be given accordingly. The use case is connected with site visit and request for session use cases. The actors involved are administrative staff, teaching staff, and the system.

Manage Staff

The management of the twelve teaching staff members, two administrative staff members, and the receptionist will be done by the director. It will include the allocation of the responsibilities, management of leaves, and salary management. The use case involves the system and the director as the actors.

Manage Services

The management of the services provided by the academy will be done by the director. The addition or removal of a service or the modification of a service will be allowed to be done by the director only. The actors involved in the use case include the system and the director.

Generate Report

There will be various reports that a director may generate in terms of total sessions conducted, payment reports, performance reports, and likewise. The system will automatically generate these reports and will provide the same to the director. The actors involved in the use case are the director and the system.

Class Diagram

Class diagram is a graphical representation of the structure of the system by displaying the system’s classes along with the attributes and properties associated with each class. The relationship and dependencies between the classes is also shown.

Sequence diagram shows the flow of activities between the objects of the classes that are involved with a particular system. The interactions arranged in time sequence are displayed by the diagram with the aid of the graphical elements.

Conclusion 

The record-keeping process that is currently followed in PSC is majorly manual. There is use of word processor done; however, PSC is growing at a rapid rate. It is required that computerized system is installed in their operational architecture so that the processing and handling of the operations is automated. The report includes the description of all the use cases that will be associated with the system and includes the class diagram and sequence diagram for the system. The information will assist the development team to understand the system functionalities, dependencies, and relationships to develop the source code accordingly.

References

Almendros-Jimenez, J. and Iribarne, L. (2006). Describing Use-Case Relationships with Sequence Diagrams. The Computer Journal, 50(1), pp.116-128.

Gemino, A. and Parker, D. (2009). Use Case Diagrams in Support of Use Case Modeling. Journal of Database Management, 20(1), pp.1-24.

Jakimi, A. and Koutbi, M. (2009). An Object-Oriented Approach to UML Scenarios Engineering and Code Generation. International Journal of Computer Theory and Engineering, pp.35-41.

Kaur, A. (2012). Application Of UML In Real-Time Embedded Systems. International Journal of Software Engineering & Applications, 3(2), pp.59-70.

Secchi, C., Bonfe, M. and Fantuzzi, C. (2007). On the Use of UML for Modeling Mechatronic Systems. IEEE Transactions on Automation Science and Engineering, 4(1), pp.105-113.

Wang, L., Liu, B. and Lu, M. (2011). A Modeling Language Based on UML for Modeling Simulation Testing System of Avionic Software. Chinese Journal of Aeronautics, 24(2), pp.181-194.

Zheng, J., Feng, Y. and Zhao, Y. (2014). A Unified Modeling Language-Based Design And Application For A Library Management Information System. Cybernetics and Information Technologies, 14(5), pp.129-144.