Systems Analysis And Design

Stakeholders

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 categorise 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 nonfunctionalrequirements 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 here.

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

Q4. Create a domain model class diagram for the LAABS, including all classes, attributes, associations, and multiplicity. Show association classes and
generalisation 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 .

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.

Stakeholders

The stakeholders finds their interest in the development of the project for increasing the efficiency of the ticket booking system for Light As Air Ballooning.  

The list if stakeholders identified for the development of the information system are listed below:

Stakeholder#1: Passenger – They finds the interest to book their ticket searching for the availability of the seats and the fares. The development of the information system would help them to book ticket from remote location and eliminate the needs to book ticket by standing in queue.

Stakeholder#2:Mr TEO – Finds interest in development of the ticket booking system such that the manual effort of the staffs can be reduced and the errors in the current business process can be eliminated.

Stakeholder#3: Maintenance Staffs – The schedule of maintenance can be loaded into the database and updated periodically that helps the maintenance staffs to work according to the schedule and increase the safety of the light as air ballooning system.   

Stakeholder#4: Pilot – The pilots can see their flight time and duration from the information system and keep track on their attendance using the information system. The certificate of the pilot can be shared for checking the qualification of the pilot and adding safety in the flight.

Stakeholder#5: Manufacturer – The records of the balloons and the technical equipment can be recorded into the database and used by the manufactured for finding the spare parts and providing service to the customers.

Registration /Login – The passenger needs to register for using the online booking system and book a flight.

Search – the passenger and the staff can use the search function for finding the flight information and the other information such as certification, maintenance etc. from the information system.

Logout – The user needs to log out from the information system after completion of their activity.

Status – the status of the booking of the flight can be get from the information system after successfully registering into the information system. The available flight and the number of seats occupied can be seen from the information system on the data selected by the customer.

Requirement Analysis

Book ticket – The passenger needs to book ticket for getting for experiencing the flight session.

Cancel ticket – the ticket can be cancelled prior 4 weeks of booking and thus the booking data is checked for cancelling the ticket without any extra charges.

Tracking – The flights can be tracked with the help of the information system and it should be updated with the latest information.

Security – The information of the balloons, staffs and the customers should be secured from illegal access such that it cannot be misused for illegal purpose.

Storage – Remote servers should be secured and cloud storage should be used for storing the data and the information.  

Availability – The data should be stored redundantly such that the availability of the data is increased and the efficiency of the information system is improved.

Reliability – Redundant link should be used for the management of the information and make it available to all the users. The servers should be configured such that there are no errors in configuration and the information’s are available to the user all the time.

Where,

C = Create

R = Read

U = Update

D = Delete

Dennis, A., Wixom, B. H., & Tegarden, D. (2015). Systems analysis and design: An object-oriented approach with UML. John Wiley & Sons.

Gorod, A., White, B. E., Ireland, V., Gandhi, S. J., & Sauser, B. (Eds.). (2014). Case studies in system of systems, enterprise systems, and complex systems engineering. CRC Press.

He, Y. Y., & Dey, S. (2014). Sum rate maximization for cognitive MISO broadcast channels: Beamforming design and large systems analysis. IEEE Transactions on Wireless Communications, 13(5), 2383-2401.

Li, Y., Lee, P. P., & Lui, J. (2013). Stochastic modeling of large-scale solid-state storage systems: analysis, design tradeoffs and optimization. ACM SIGMETRICS Performance Evaluation Review, 41(1), 179-190.

Mahmoud, M. S. (2016). Networked control systems analysis and design: An overview. Arabian Journal for Science and Engineering, 41(3), 711-758.

Rosenblatt, H. J. (2013). Systems analysis and design. Cengage Learning.

Valacich, J. S., George, J. F., & Hoffer, J. A. (2015). Essentials of systems analysis and design. Pearson Education.

Zhang, C., Duan, Z., Yu, B., Tian, C., & Ding, M. (2016). A Test Case Generation Approach Based on Sequence Diagram and Automata Models. Chinese Journal of Electronics, 25(2), 234-240.