ICT284: Light-As-Air Ballooning (LAA) is an Organization Which Operates Hot Air Ballooning: Systems Analysis and Design Assignment, MU, Singapore

The case study: Light-As-Air Ballooning System (LAABS)

Light-As-Air Ballooning (LAA) is an organization which operates hot air ballooning on the Malaysian peninsula across from Singapore (the Singapore air-space is too busy and tightly controlled to allow free-flying ballooning there). The company has a mixed fleet of balloons and baskets and a team of pilots 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 all information about clients and flight sessions. It must also manage the information about balloon and basket maintenance, and keep track of the 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 canceled 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 acts 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 has 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 the 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 the 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 the 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

Q1. List the main stakeholders for the new  Light-As-Air  Ballooning  System  (LAABS). For each stakeholder, write a brief description of their interest in the system and what aspects of it are of particular relevance to them.

You do not need to categorize the stakeholders. Don’t include the systems development team.

Q2. (a) List and briefly describe the main functional requirements for the LAABS. There should be around 5-10.

(b) List and briefly describe the main nonfunctional requirements for the LAABS.

Q3. (a) Use the User Goal technique to develop a list of use cases for the LAABS. Present your list in a table that includes the participating actors, use case name, and a brief use case description.

(b) Use the Event Decomposition technique to identify any additional use cases for the LAABS. These will probably be temporal and state event types. Present your list in a table that includes the event, type of event, trigger, use case name, and brief use case description. You do not need to repeat the use cases you identified in (a) here.

(Note that some use cases are already identified in Q6, 7, 10 below. Include these in your lists.)

Q4. Create a domain model class diagram for the LAABS, including all classes, attributes, associations, and multiplicity. Show association classes and generalization hierarchies where appropriate.

Q5. Create a CRUD matrix to check the consistency between your domain model class diagram and your complete list of use cases. Set this out in the form of a table with classes as the columns and use cases as the rows. If you find discrepancies between the models while you are doing this, you should go back and correct your earlier models as required so that your final set of models is consistent.

Q6. Create a fully-developed use case description for the use case Book a Flight. Follow the template provided at the end of this handout.

Q7. Draw an activity diagram to represent the flow of activities for the use case Inspect Balloon shown at the end of this handout.

Q8. Draw a system sequence diagram for the use case Inspect Balloon shown at the end of this handout that corresponds to your activity diagram in Q7.

Q9. 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 the appropriate transition name, guard condition (if appropriate), and action expression (if appropriate).

Q10. Develop a user acceptance test plan for a customer of the LAAB system. Base it on the relevant use cases you have identified. You can follow the example in the textbook (below). Present your test plan in a table including the fields: use case name, test conditions, expected outcomes. You do not need to include test data.