Description
Introduction
During re-entry, all remaining parts of the rocket are jettisoned and burn up in the atmosphere. The exception to this is the capsule, where customers and crew are located. This module will splashdown in the ocean somewhere in a pre-defined area known as the landing ellipse and will be picked-up by a specially equipped recovery ship or aircraft carrier, where customers and crew will receive a medical check, before being flown back to a conventional airport. These details, including the return airport, are specified in the booking.
The spacecraft must maintain a constant connection to mission control; the on-board system will report current status, problems, allow voice and video communication which can be recorded and relayed live to friends and family of the customers on-board, and allow mission control to override the system if required. Any use of the override feature is recorded in the audit log as well as the individual flight log. Live system data is also stored in the flight log for later analysis. All elements of the flight are tracked, from the amount of fuel in each stage of the rocket, to the flight crew on-board, as it is essential that the correct total weight of the spacecraft can be determined at any given time. For this reason, everything (including fuel) and everyone entering the spacecraft before launch must be weighed before entering, and this must be recorded by mission control.
Given the high price of space tourism, with costs reaching the millions per seat, cash payments are not accepted (counting that much money would take far too long). Instead, customers pay primarily by bank cheque, direct deposit, an approved cryptocurrency, or in some cases, credit card. All payments must be cleared before a booking can be confirmed. In the case of a group booking a 10% discount can be given per person in the group. Pricing also varies by lead time, that is, a booking a year in advance will be cheaper than booking a month in advance, with the exact cost calculated at the time of the booking.
Objective of the system
The main objective of the system is to develop a new on-line management system.
1. The business manager needs all information at their fingertips to make decisions.
2. Safety is a critical aspect of this business and must be considered in every scenario.
3. The business manager requires financial reports each month, the system should store these as well for audit purposes.
4. While the system will be online, it must also be secure, and personal information must be kept private, such that only staff with a genuine need-to-know will be able to access private records.
5. The system must operate in real-time, i.e. able to receive and report on live flight data as it comes in without delays.
Tasks
(Assume that customers interact only with staff and are therefore not considered as an actor).
The system definition above will be used for the two assignments for this course. For this assignment, you will elicit and document the requirements for the on-line management system. You should identify system processes and user requirements. In this assignment you will gather and document system requirements, business rules and construct initial model of the system in UML. Specially, you develop use case diagrams, activity diagrams and map out a class diagram for the domain.
There are no limits to how far the requirements and analysis might go. However, complexity, coverage and correctness of the elements will be taken into account in the assessment of the submitted work.
The main deliverable of this assignment is a report and MS Gantt Chart to be submitted via Canvas,
For the report, you need to submit a Word or PDF document and a MS Gantt file in one compressed (zip) file containing the following:
1. Report cover sheet containing the
a. Default is 5 Team members (first and last name and student numbers)
b. Lab Day
c. Lab Room,
d. Lab Time and
e. Lab academic (first name only)
2. Introduction to the report (2.5 Marks)
a. What is in the report?
b. Who is the intended audience of this report?
c. What are the objectives of this report?
d. How does each element of this report contribute to achieving the report objectives?
e. https://www.monash.edu/rlo/assignment-samples/engineering/eng-writing-technicalreports/introduction
3. Business Rules (5 Marks)
c. Use the following table format for this process
Business Rule System Mapping Organisational Mapping
B1: Customer contact details Data collected in the customer class and the interface Manager notified if data is not complete by the system
4. Class Diagram (30 Marks)
a. All classes to be implemented (including the Boundary classes, Controller classes and Entity classes) and appropriate relationships between them.
d. Your class diagram should follow principles of good system and object design as discussed in lectures and the videos provided.
e. At least one design pattern eg observer pattern
5. Use Case Mapping to Sequence Diagram (30 Marks)
b. Each team member will create a subset of the class diagram (section 4) that maps to the required data to required of the Use Case description.
c. Each team member will create a sequence diagram (for the Use Case) that shows the relevant Boundary, Controller and Entity classes from your class diagram in section 5b.
d. Give a short description for each diagram to briefly explain the interactions among the models to perform the use case.
6. User Interface (10 Marks)
a. Each team member will develop a user interfaces (i.e. screen design) using your use case description, subset of the class diagram and sequence diagram (section 5) as the basis of your interface (The logon interface is not to be modeled).
c. Each interface must be consistent in appearance and visual style for the team.
d. Consider each user of your interface, considering accessibility and ease of use.
e. The use of a navigation process between each team members interface is important
7. Deployment (5 Marks)
a. What is your team proposing for a deployment strategy? How will you address issues in data migration from the old system to the new system? How will you handle user training? How does your chosen strategy address the potential for system faults and bugs?
b. Will you use a direct, pilot, parallel, or phased deployment? Justify your choice in comparison to the alternatives. What are some potential disadvantages to your choice and how will these be mitigated?
c. Have a look at the 14-2-Deployment.mp4 video link.
d. Give an example (with references) of a real-world situation where a similar strategy was used to support your argument.
8. Team Management (15 Marks)
a. Meeting notes for at least 5 meetings and MS teams activity report
b. MS Gantt Chart
i. your team will continue to refine your existing chart and show who has done what and the percentage completed for each task
ii. This part of your assessment will be utilised if there is any issue with team management of production and team submission. Makes sure you keep copies of your individual work
c. Self and Peer-Assessment process using TeamMates (5 marks individual, after team submission) See page 6 for further details.
9. Conclusion (2.5 Marks)
a. What was completed
b. What was not completed and why
c. How did each section of the report achieve the report objectives?
d. What are your recommendations for the client?
e. https://www.monash.edu/rlo/assignment-samples/engineering/eng-writing-technicalreports/conclusions-and-recommendations
10. Reference list (including but not limited to, any references used for the introduction and business rules sections in particular)
Handing in your work
You are to hand in the assignment electronically using Canvas’s Assignment facility.
When you are ready to submit your code file, log in to Canvas, go to the site for this course, and follow these steps . . .
• Select the Modules folder.
• Click the Group Project 2 link, which will take you to the appropriate upload page.
• Click or drag file as below. Then hit Submit Assignment.
• If you wish to see if the correct file has been uploaded then just click the download icon as below.
• If you want to submit an updated version of the assignment, go back to the Assignment link and click Try Again.
submission, and if it’s submitted late it will be marked as late.
You might be required to demonstrate your program, and to explain aspects of your code, in a subsequent computer lab class. If required, your lecturer will notify you of this process.
Assessment), an indication of how you have rated yourself compared to how your teammates have rated you.
