Assignment 2

Worth: 30% of your final grade.

The assignment requires you to carry out some systems analysis and early systems design activities for the Weddings Parties Everything system described here. Read the case study on the next page and answer questions 1-6 following.

Summary of what to submit:

Question	Task	Marks
1	Use cases	8
2	Domain model class diagram	6
3	Fully-developed use case description	4
4	Activity diagram	4
5	System Sequence Diagram (SSD)	4
6	State Machine Diagram (SMD)	4
	TOTAL MARKS	30

The case study

The context is a company operatinghot air ballooning on theMalaysian peninsula across from Singapore: Light-As-Air Ballooning (LAA). The organizations has pilots and a mixed fleet of balloons and baskets to cater for both small and large groups.

The five (5) smaller baskets have the capacity to carry up to 10 passengers each; six (6) larger balloons and baskets can carry up to 20 passengers each. This is a relatively new venture for this part of Asia, and the owner of this company, TEO Hong, is keen to see LAA grow and expand.

Flights take place just before sunrise, and can be booked by individuals or groups, or can be chartered (such as for wedding ceremonies and other special occasions). The larger baskets are ideal for corporate and social group bookings.

As the business expands, Light-As-Air needs a new information system; as the current one was based on Mr TEO doing all the bookings himself. The new Light-As-Air Ballooning System (LAABS)must manage the booking system for the balloons, and maintain allinformation about clients and flight sessions. It must also manage the information about balloon and basket maintenance, and keep track of pilot and other staff certification.

Customers book online or at the LAA Singapore city office. As the flight sessions are heavily subscribed, customers are sent reminder texts about their flight the week before and the day before. Cancellation without incurring a charge is only possible up to 4 weeks before the flight (after that the full price is payable). The LAABS is not required to handle any payment information as this is done by a third party system. Customers are informed the night before the booking date if the flight is cancelled due to weather.

The flights are only booked out in lots of ten (10) (small balloons) or twenty (20) (large balloons), and each flight session must be accompanied by a senior pilot and a staff member who act as co-pilot. These staff members must have first aid training, a Commercial Balloon Pilots Licence, and have passed a medical within the last 3 months. The LAABS must ensure that the staff have current first aid certificates and pilot certificates, as well as regular medical check-ups. This will require alerts to the relevant staff members at the appropriate times.

Customers must also meet various conditions: the office will need to know the weights of the passengers in each party and if anyone has had recent injury or surgery, or is pregnant. This is confirmed when they book, along with name, address, and contact phone number, and the date of the flight required. Details of all customers in a party are required, and all customers must sign a statutory declaration that the information they provide is true. Insurance and OHS requirements mandate permanent storage of these declarations.

Each flight session is booked out for two (2) hours, of which between 45 and 60 minutes is actual flying time, with 30 minutes preparation (check-in, safety briefing and boarding and balloon inflating) and 30 minutes disembarkation time (this includes bus transport back to the launch site). Customers are expected to make their own way to/from the launch site.

Customers may book two (2) different types of experience:

• Flight- this includes flight, loan of warm jacket for the duration of the flight, Certificate of Participation and transport back to the launch site only

• Deluxe experience - as well as 'Flight' inclusions, this adds a post-flight breakfast, champagne and photo opportunities with the (inflated) balloon and pilot.

Safety and comfort of customers and staff is obviously paramount for LAA. Before each flight an inspection is made of the basket and balloon (including physical damage, integrity of equipment, balloon control systems, cleanliness, etc). There is also a thorough technical check of the equipment after each flight session. These checks are noted by the system.

There is a full mechanical check of all equipment by a service engineer at the beginning and end of every working day, and in addition each balloon inflating and control system must be fully serviced by the manufacturer at least every three months or every 50 hours of use, whichever is sooner. The mechanism is removed from the balloon structure and sent to the manufacturer for examination and possible repair/replacement. This takes 4 days, so to keep the business operating TEO Hong tries to stagger the downtime so there are always at least two balloons of each size in service.

The hours of balloon use are logged by the LAABS, by adding the number of session minutes to the usage log at the end of each session. When a balloon reaches 50 hours of use it is flagged as 'in maintenance'. On reassembly the number of usage hours is reset. LAABS also records the dates, times, and details about each service.

While the control equipment is being serviced at the manufacturers, the basket and guy-ropes are refurbished and jackets inspected for wear and cleaned.

Several reports will be required of the new system. The LAABS must be able to provide an ad-hoc status report on each balloon and basket (different baskets can be attached to various balloons as long as maximum capacity is adhered to), showing whether it is in use or being serviced, its current hours of use and date of next scheduled service. It also needs to provide all the information about mechanical checks and services in a report that TEO Hong sends to the manufacturers annually as part of the maintenance agreement. Finally, TEO Hong would like a report showing the customer usage so that he can see what are the most popular times of year and types of flights and plan for expansion.

TO DO:

Note the following points:

• You may need to make assumptions where information is incomplete: state any assumptions clearly. You can also ask questions on the forum.

• Your diagrams should be drawn using Visio (or suitable alternative that creates UML diagrams). Use the appropriate template for each diagram type. Make sure your diagrams are clear and readable.

• Your diagrams must follow correct UML notation and naming conventions, and each diagram should include a title and legend.

• Your models, diagrams and discussions should be consistent with one another throughout your analysis and design.

• Ensure your work is clearly and professionally presented, proofread for spelling and grammar, with a title page and table of contents. Start each main question on a new page.

Q1. Develop a list of use cases(please do not include multiple tables). Present your list in a table that includes the participating actors, use case name and a brief use case description. For those identified via Event Decomposition technique,you need to includethe event and type of event. (Note that some use cases are already identified below. Include these in your lists.) (8 points)

Hint: you may use CRUD to double-check if there is any missing one.

Q2. Create a domain model class diagram, including all classes, attributes, associations, and multiplicity. Show association classes and generalisation hierarchies where appropriate. (6 points)

Q3. Create a fully-developed use case description for the use case Book a Flight.

Follow the template provided at the end. (4 points)

Q4. Draw an activity diagram to represent the flow of activities for the use case Inspect Balloonshown at the end. (4 points)

Q5. Draw a system sequence diagram for the use case Inspect Balloon that corresponds to your activity diagram in Q4. (4 points)

Q6. Draw a state machine diagram to show the possible states and transitions for a Balloon object. Label each state with the state name. Label each transition with theappropriate transition name, guard condition (if appropriate) and action expression (if appropriate). (4 points)

Marking Rubric

Criteria	HD	D	C	P	F
	6.4-8	5.6-6.3	4.8-5.5	4-4.7	0-3.9
Q1 Use case (COL2.1, 2.3) (8 points)	Almost all use cases are identified.	Most use cases are identified.	A reasonable number of use cases is identified.	Some use cases are identified.	Only a few use cases are identified.
	4.8-6	4.2-4.7	3.6-4.1	3-3.5	0-2.9
Q2 Domain model class diagram (COL2.2, 2.3) (6 points)	The diagram has few errors, and is fully consistent with the case.	The diagram has few errors, and is mostly consistent with the case.	The diagram has a few errors, and represents the case reasonably.	The diagram has some errors, and have some inconsistencies.	The diagram has many errors, and has a lot of inconsistencies.
	3.2-4	2.8-3.1	2.4-2.7	2-2.3	0-1.9
Q3 Fully-developed use case description (COL2.2, 2.3) (4 points)	The answers contain all necessary details of the use cases, and are fully consistent with the case.	The answers contain most necessary details of the use cases, and are mostly consistent with the case.	The answers contain reasonable details of the use cases, andrepresents the case reasonably.	The answers contain some details of the use cases, andhave some inconsistencies.	The answers contain few details of the use cases, and havea lot of inconsistencies.
Q4 Activity diagram (COL2.2, 2.3) (4 points)	The diagram has few errors, and is fully consistent with the case.	The diagram has few errors, and is mostly consistent with the case.	The diagram has a few errors, and represents the case reasonably.	The diagram has some errors, and have some inconsistencies.	The diagram has many errors, and has a lot of inconsistencies.
Q5 System Sequence Diagram (COL2.2, 2.3) (4 points)	The diagram has few errors, and is fully consistent with the case.	The diagram has few errors, and is mostly consistent with the case.	The diagram has a few errors, and represents the case reasonably.	The diagram has some errors, and have some inconsistencies.	The diagram has many errors, and has a lot of inconsistencies.
Q6 State Machine Diagram (COL2.2, 2.3) (4 points)	The diagram has few errors, and is fully consistent with the case.	The diagram has few errors, and is mostly consistent with the case.	The diagram has a few errors, and represents the case reasonably.	The diagram has some errors, and have some inconsistencies.	The diagram has many errors, and has a lot of inconsistencies.

Use Case Name:
Scenario:
Triggering Event:
Brief Description:
Actors:
Stakeholders:
Preconditions:
Postconditions:
Flow of Activities:	Actor	System
Exception Conditions:

Use case description Inspect Balloon

Use Case Name:	Inspect Balloon
Scenario:
Triggering Event:	A party of customers is ready to undertake a flight they have booked.
Brief Description:	Before a party of customers can commence their session, the
	accompanying staff member carries out an inspection of the balloon,
	checking forphysical damage, integrity of equipment, balloon
	control systems, cleanliness, etc. If any of the checks fails, the system
	records the nature of the failure and issues an alert that the session
	cannot proceed until it has been rectified. If the checks are all OK, the
	system records this fact and issues the go-ahead for the session.
Actors:	Staff member
Stakeholders:	Staff member, manager
Preconditions:	The balloon has been booked for a session, and this has been
	recorded in the system.
Postconditions:	The session booking record has been updated to reflect the details of the
	balloon.

Flow of Activities:	Actor	System
1. Staff member completes inspection checks 2. Staff member enters session record number for the booked session 3. Staff member enters details about physical damage, cleanliness. For the cleanliness there must be a statement to indicate that the problem is no longer an issue. 4. Staff member confirms inspection report complete.	2.1 System displays the information about the session (time, date, customers in party, etc) 2.2 System prompts for confirmation that the inspection checks have happened. 3.1 System records inspection details in session booking record. 3.2 If physical damage checks are failed, system advises session must not go ahead and balloon must be withdrawn until the problem is rectified. 3.3 If cleanliness test is failed and there isn't a statement of cleaning, system advises session must not go ahead until the balloon area is cleaned. 4.1 If all checks are OK, system confirms that session can go ahead 4.2 If any checks are failed, balloon flagged as out of use.
Exception Conditions: