Great COIT20248 Assignment Sample
1. Introduction
Ryan Aviation’s primary goal in this study is to determine whether or not the solutions to deployment are feasible.
We also experienced many challenges that are presented by Ryan Aviation with respect to keeping reports of growth in the number of employees. We also incorporated other system development methodologies and an expense estimate review to evaluate the budgetary issues to address these problems.
They also have an innovative “structure for work breaking down,” that would lead towards a more structured working environment. The venture is designed in the sheer immensity of this mission.
All these approaches should ensure Ryan Aviation develop efficient strategic policies; uphold clear ethical standards including safe data exchange.
2. Approach to Systems Development
2.1 Developing the Information Systems of Ryan Aviation
Ryan Aviation earned numerous contracts as well as established many bases across Queensland and New South-Wales to adapt to bush fires more rapidly.
A detailed analysis of data, evaluation and record analysis by Ryan aviation requires to be completed.
By examining the field measurements, the investigators established and tested theories to identify critical linkages and conduct individual experiments. It would enable Ryan Aviation to develop a significantly more reliable and secure information network for transitioning to new installations.
The problems faced by Ryan Aviation recently are:
- Issues faced in distribution of aircrafts, staffs and spare parts to all the bases
- Chaos experienced while maintenance and establishment of effective workforce and staff distribution at new locations.
- Prevent replication in other places with manually running employee leave reports, payrolls and time sheets.
- Daily preparation of staff meetings to ensure high-quality service delivery.
Aviation industries ‘ software engineering phase is far more challenging than many carriers. This is due to the fact that a minor technology-related error could contribute to a great deal of redesign and to budget risks and overruns throughout the calendar.
Stakeholders are like administrators, technicians, consumers, ground-staff, different companies and sales agents in this scheme. We have to integrate all the stakeholders ‘ criteria and suggestions on designing a system to create a stronger program in this Aviation Company.
In JAD or Joint Application Design, administrators, consumers and program experts must work together for many days to build a new format and fully appreciate the demands of each activity. This strategy includes both formal sessions and updated structures.
2.2 JAD for Developing the Information Systems
We have used the JAD method to solve all the problems encountered by Ryan aviation. Utilizing the JAD approach would assist in the standard provision of fully operational code as well as in making changes to reduce the menace of financial reporting for costs and time constraints.
The JAD design is geared towards asynchronous productivity that offers a relatively simple and better outlook than standard individuals. According to Shelly, JAD would eventually need to be validated and implemented to build and deliver a software framework progressively.
Further advantages of JAD are mentioned below:
- System and product interface strategies by JAD involves administrators, developers and consultants for the program. One’s view and one’s machinery can be better understood.
- This approach performs a series of interviews with the applicant which allows them to do so. It is a way of reducing time and money.
- This technology allows device developers to plan and collect information with the customer groups with key people.
- An overview of system requirements is the goal, and various emerging innovations are included in the application of the framework.
- The findings of the JAD program methodology are more precise and accessible to system requirements.
3. System Requirements
3.1 The Functional Requirements
To build every information system, the system requirements are important. Ryan Aviation needs two kinds of specifications, which are practical and non-functional.
Functional specifications focus primarily about what is required in order to resolve safety and quality problems in the constructed environment and non-functional condition (Kendell, 2011).http://Great COIT20248 Assignment Sample
| Power Network | Data Network | |
| Functional Requirements
(Affected by aircraft regulation) |
Supply of electric power to all cabin as well as cargo systems including the wings, tails. | Providing the entire cabin as well as the cargo systems with network facilitated by a full Cabin Backbone for exchanging data to the other system in various new locations. |
| Shielding functions for Human and wirings services. For instance GFI security, Arc Fault Sensing tools, over current clearances and short circuiting. | Providing in-built redundancy for attaining high levels of availability as well as prevent failures at any point. | |
| Current returning support of the “CFRP-fuselage” aircrafts. | Crew-friendly operating systems for reducing workloads. | |
| Miscellaneous Functional Requirements |
Local AC to DC converting systems in order to lessen the wiring weight | Install systems which support plug and play without physical device intervention or configuration |
| Power management functions | Provision of standardized interfaces for simplification of connectivity with the other devices. | |
| Remote system control for controlling all the functions | PAX Services for supporting the crew members and passengers comfort. | |
| Galley Supplying operations | Modular Architectural design for upcoming needs | |
| Supply functions for medical equipment’s | Wirelessly acquired information for assigned applications. | |
| Customizing functions according to the prevailing conditions. | Advanced Communication technologies for future | |
| Low maintenance systems for reducing the time as well as costs. | ||
| Augmentation of equipment’s. | ||
| Avoiding manual intervention by setting up auto configuration systems for maintenance. |
3.2 Non-Functional Requirements
| Security | Introducing MILS or “Multiple Independent Levels of Security” which is a procedure-oriented architecture. |
| Maintenance | The shipping standards regulations referred to as “Minimum Equipment Lists” include simple aerodynamic product (for example, flight, view, navigation, environmental protection and the convenience and facilities of the consumer) |
| Availability and Integrity | An example of a “net safety function” is the specified range of network spectrum allocations (custodian features). |
| Temporal Functional Aspect | Introducing ARINC629 has improved the bus access approaches. |
| Testing and Diagnosis | The amount of data requires special network bandwidth for testing and diagnosis. |
| Schedule-ability | A gradual scheduling strategy would preferably be endorsed to enable the use of Networks with minimal interruption from users. |
| Obsolescence | Implementing the MAC or “Modular Aerospace Control” system for the engine regulation |
4. Project Cost Benefit Analysis
4.1 Excel Sheet Representation of Cost Benefit Analysis
4.2 Cost Benefit Analysis of Ryan Aviation
As we know,
The total Development Cost (given) = $ 200,000
The given discount rate= 9 %
Therefore the Net Present Value calculated for 5 years = $ 162, 215.
To order to calculate the return on investment, Ryan Aviation’s feasibility analysis has been conducted by market estimation, NPV (Net Present Value), ROI (Break Even Analysis) and BEA processes.
In the Excel worksheets with cost benefit review, both projections and expenditures are listed. It is the total cost of the program and its benefits. Development costs are projected at $200,000. Expenditures and income over five years are projected.
The discount number is 9%. The current value is also calculated. One-time yet recurring expenses can be functions of complex existence (Valakati, George, Hoffer, 2006).http://Great COIT20248 Assignment Sample
5. Project Schedule
5.1 Gantt chart with work breakdown structure and discussion of relationship between the both
The schedule of this method outlines activities and responsibilities in the planning time frame, and Gantt’s map defines timing expectations for the start, implementation, and conclusion of the specific event (Valakati 2006).http://Great COIT20248 Assignment Sample
The complete cycle is arranged according to the period defined by the planner.
The “work break-down structure” or WBS based on the project schedule is given below. The Work Breakdown System (WBS) lays out the operating structure of a job. The WBS concept is based on the person and his point of view.
The organization engages in a number of aircraft maintenance projects. Whereas the core competencies and practices stay the same, very few organizations precisely replicate prior research.
Reuse of documents is not feasible without a consistent archiving and storage method for project data.
Figure 1 Work Breakdown Structure
5.2 System goals, requirements, scope and verify project schedule reasonable or not
The main objective of the Ryan Aviation program is to limit manual processes, so that the pen and paper-based register can be removed. Build the new scheme, which will render each standardized payment process easy for the user, conveniently available and retain the repository.
Criterion: The most critical criterion for developing a new program such as this Aviation program is
- Consumer expectations and structure
- Approach method
- Prepare, continue, check Planning
Project scope: For addition the new design framework will not only predict project time calculation and budget allocation, but it also includes scheduling for the project. It also offers the basis for completing the project in due course and in a timely manner (Shelly 2011).http://Great COIT20248 Assignment Sample
If there is any issue with resources such as fanatical, time delays and the collection of data, the above described project timetable will be appropriate if the whole criteria is agreed.
6. System Information Requirement Investigation Techniques
6.1 List of stakeholders
The Stakeholders involved in the Ryan Aviation project are:
Internal Stakeholders:
- Employees
- Maintenance manager
- IT Staff
- Directors
- General Manager
- Crew
External Stakeholders:
- Passengers
- Government Authorities
- Local Communities
- Media and Unions
- Clients
6.2 Investigation Techniques
Interviewing
It is one of the most critical criteria for the application of information. The meeting contains discussions with partners, administrators, personnel, etc. and information on the requirements and structure of the project.
Utility: Talk with people to clarify quickly whether there are confusions.
Some of the standard problems are included in the approach and are used to extract details on the conditions of the aircraft program. This helps us to acquire the answers of the stakeholders and to collect information in little time.
Usability: Document or device conflicts that minimize and can be addressed quickly.
Observation
Unit consultants collaborate alongside clients to determine where they are facing problems. This is a consumer-friendly way, even though it is unpleasant for staff to be watched by anyone often.
7. Reflection and Conclusions
It initiative constrains choosing incorrect items such as unrelated individuals and knowledge (false individuals and difficulties). It calls for great time and effort. It is a challenge to hold meetings with different departments and insufficient contact with concept experts and customers.
Depending on consumer experiences, the major accomplishment for this approach rising development costs.
Ryan Aviation experienced many manual processes issues regarding pen and paper-based record systems. Through the JAD methodology, we put administrators and consumers together and address program specifications in an organized fashion.
The JAD architecture approach for the Ryan Aviation program is very beneficial since it has different instruments and methods to collect knowledge and assess the specifications, which prevents time and money.
References
Marks, A., Rietsema, K. and Hudson, G. (2013) Aviation Management Information Systems. Embry-Riddle Press, Daytona Beach.
Airport Cooperative Research Program (2008) Integrative Airport Information Systems—Report 13. Transportation Research Board, Washington DC.
Airport Cooperative Research Program (2010) ACRP Synthesis 21 Airport Energy Efficiency and Cost Reduction, Transportation Research Board, Washington DC
- Winston, S. Morrison (1995). “The Evolution of the Airline Industry”, Brookings
Harris, A, Lang, M, Oates, B, & Keng, S 2006, Systems Analysis & Design “An Essential Part of IS Education”, Journal Of Information Systems Education, 17, 3, pp. 241-248, Business Source Complete, , viewed 28 August 2015.
Valacich, J, Hoffer, J, & George, J 2006, Essentials Of Systems Analysis And Design, “ Upper Saddle River”, Pearson Prentice Hall, c2006., CQUniversity Library Catalogue, viewed 28 August 2015.
Shelly, G, & Rosenblatt, H 2011, Systems Analysis And Design, Boston, “Course Technology, Cengage Learning”, c2011., CQUniversity Library Catalogue, EBSCOhost, viewed 28 August 2015.
Know more about UniqueSubmission’s other writing services:
