Introduction to Systems Design: Ryanair Mobile App Report, ICT115

This report, created for an Introduction to Systems Design course (ICT115), analyzes the design and development of a mobile application for Ryanair. The report focuses on system analysis and design requirements, including the creation of Data Flow Diagrams (DFDs) at different levels, user personas (customer and admin), and user storyboards. The context diagram illustrates the overall system, while Level 0 and lower-level diagrams detail specific processes such as airport navigation, flight schedule assistance, and flight communication. The report also emphasizes the importance of user-centered design, considering the needs of both customers and administrative staff. The conclusion highlights the application of a process-oriented strategy and the use of personas in translating system requirements into interface design. Recommendations are provided, including the use of agile methodology, object-oriented system analysis, and customer interviews for requirement gathering. The report aims to improve the functional modeling of the Ryanair application, providing insights into its development and implementation.

Introduction to Systems Design – Report Template
ICT115
Introduction to Systems Design
Assignment 2
ICT115 Page i

Introduction to Systems Design – Report Template
Executive Summary
The main objective of this exploration is to research the customer oriented mobile
application for Rynair, explicitly client profiles and personas, as methodological devices to
illuminate the structure as well as various UML diagrams that can be used to depict actual
requirement for application development. This paper helps to analyse two central
suspicions related with the system analysis as well as system design data frameworks ie the
assumed authoritative role of data frameworks, and (2) the perspective on data necessities.
This report receives a precise methodology for leading data gathering requirements,
analysis and designing UML diagrams. Here, we have considered two main users – Customer
and Admin in developing mobile application. We have given the case scenario of Ryanair.
The mobile application will help the customer to navigate airport, the gate information,
communication from admin when flight gets delayed.
ICT115 Page ii

Introduction to Systems Design – Report Template
Table of Contents
Executive Summary....................................................................................................................ii
Table of Tables...........................................................................................................................iii
Table of Figures.........................................................................................................................iii
1 Introduction.......................................................................................................................1
2 Body of Report...................................................................................................................1
2.1 Analysis and Design Requirements.............................................................................1
2.1.1 Context Diagram (DFD)........................................................................................1
2.1.2 Level 0 Diagram....................................................................................................3
2.1.3 Lower Level Diagram............................................................................................3
2.1.4 User Persona........................................................................................................4
2.1.5 User Storyboard...................................................................................................5
3 Conclusion..........................................................................................................................6
4 Recommendations.............................................................................................................7
5 References..........................................................................................................................7
Table of Tables
Table 1 – User types and their requirements............................................................................1
Table of Figures
Figure 1 – Context Diagram........................................................................................................2
Figure 2- Level 0 Diagram...........................................................................................................3
Figure 3: Lower Level Diagram – Airport Navigation.................................................................3
Figure 4: Lower Level Diagram – Flight Schedule Assistance....................................................4
Figure 5: Lower Level Diagram – Flight Communication Process..............................................4
ICT115 Page iii

Introduction to Systems Design – Report Template
1 Introduction
Developing data framework undertaking is the main IT project that has been created to
offer the best method for the organization. Procedure of framework development will
experience its very own life cycle and each procedure must be refined so as to satisfy points
and targets. Even though data framework advancement is constantly correspond with
failure however a couple of key variables will assist the frameworks with succeeding. The
main objective of the paper is to analyse various processes that are associated with the
development of data framework which emphatically contribute towards its prosperity
(Nayan and Zaman, 2009).
Here, we have given with the scenario of Ryanair which is low cost airline. Ryanair operates
in competitive environment where the organization has pre-established rival industries like
British Airways and Irish national Airways. Ryanair sought after low cost airline yet
productive system of offering intensely limited services to provincial UK and European goals.
The organization is thinking to develop RyanAssist mobile application that can help
passengers to explore to the correct air terminal, however the registration procedure, their
check in process and the gate information for that particular air carrier. Our objective in this
report is to develop DFD, User Persona and Storyboard of given scenario.
2 Body of Report
A useful methodology that can be used to develop the system is one of the most
mainstream in the functional modelling of data frameworks. Its quintessence lies in the
deterioration of the all action into automated functions: the framework divides the entire
system into functional subsystems, which are separated into sub-capacities, and after that
into undertakings, etc. This procedure proceeds until it gets the number of explicit systems.
For this reason such standards as "partition and overcome", progressive requesting,
deliberation, formalization, consistency, and information structuration are utilized. This
centralized approach to solve the issues requires change in system design. This prompts to a
move from the functional approach to deal with the strategy, which depends on the analysis
of data flow. At that point there was a change to a procedure oriented methodology as the
information solution (Shendryk and Boiko, 2015).
2.1 Analysis and Design Requirements
The mobile application must be able to make online registration. The customer then login
into the app in order make online check in. It will help to save time. By entering their flight
number, the system will ask for their PNR number, and then a comfortable seat can be
selected by passenger itself. The specific airport can also be navigated through the
application. Also, it will provide all the details of the gate where user has to check in for that
particular flight. If the flight is late by its normal time, it will send a message to the
passengers about this delay, so that passengers can reach accordingly at the airport.
ICT115 Report Template Page 1

Introduction to Systems Design – Report Template
2.1.1 Context Diagram (DFD)
The data flow diagram ie (DFD) helps to provide the progression of data for any procedure
or framework. It uses characterized symbols such as rectangles, circles and arrows to show
the direction of the data flow, and the labels which will describe about the input, output and
data storage points. Information flowcharts can be easy, simple as well as it can be describe
by in- depth multilevel DFDs (Lucid Software Inc., 2019).
Figure 1 – Context Diagram
I have taken six processes according to given scenario – Login, Enter PNR, Search PNR,
Retrieve gate information, Customer Checkin and message to customer for any delay.
Customer first register and then login into the application. He then enters PNR no in order
to check in or searching any detail related to that particular PNR no. The application will
search that PNR number from its booking database and will retrieve all the details related to
that PNR number. If the flight is delayed, a message will be sent to the customer in advance,
ICT115 Report Template Page 2

Introduction to Systems Design – Report Template
so that it saves time of the customer and can reach airport accordingly. Also, customer can
checkin to the flight using RyanAssist application.
2.1.2 Level 0 Diagram
Figure 2- Level 0 Diagram
2.1.3 Lower Level Diagram
1. Navigation to and Around airports processes
ICT115 Report Template Page 3

Introduction to Systems Design – Report Template
Figure 3: Lower Level Diagram – Airport Navigation
2. Flight Schedule Assistance
Figure 4: Lower Level Diagram – Flight Schedule Assistance
3. Flight communication processes
ICT115 Report Template Page 4

Introduction to Systems Design – Report Template
Figure 5: Lower Level Diagram – Flight Communication Process
2.1.4 User Persona
Personas is a strategy that supports planning and designing our mobile application with the
emphasis on the end-clients. The regular comprehension of the personas strategy is that a
persona is a depiction of an invented individual who are dependent on information which is
collected about the customers. Personas has been advanced as a solid strategy for giving the
developers a comprehension of the forthcoming clients of their product. This
comprehension guarantees that Product Managers, Designers, Developers and so on can
deliver the solution that really address genuine client challenges. Here, we will gather more
requirements from the customer and the admin staff who are mainly considered while
developing application. This will help to understand developers about their main
requirements and what actual information should be included in this persona.
Table 1 – User types and their requirements
User type How user relates to case study
Customers Customers book tickets for business purpose, holiday or any other
important occasion. For that they have to book air tickets online.
Now customers mainly require about all the details of flight whether
its delayed, on which gate they have to enter for boarding, airport
navigation system as sometimes it becomes difficult for the customer
to reach to the exact airport where they have to checkin. Also, their
main requirement is to check in using mobile application s it will help
in saving time. If the flight gets delayed, customers want to get
automated informative message about the delay.
Admin Admin wants an automated system that will automatically search the
flight which has to take off and if the flight is delayed they want to
ICT115 Report Template Page 5

Introduction to Systems Design – Report Template
send automated message to all the passengers by just single clicking
on an option.
2.1.5 User Storyboard
A storyboard is considered as a realistic graphic approach that can help in providing a
significant level perspective on the overall system development project. In Agile system
development methodology, a storyboard can help designers rapidly get a feeling of what
work still should be finished. For whatever length of time that the team stays up with the
latest, anybody can perceive what work has been finished, which team member is working
at what and what work is left to do. This not just provide the system proprietor with better
transparency, it likewise encourages the group to imagine the succession and
interconnectedness of client stories. Storyboards can be physical or computerized (Rouse,
2019).
Figure 3 – Storeyboard
3 Conclusion
In this report, we have conducted system analysis approach to improve the procedure of
functional modelling of RyanAssist application. The main aim was identified with the
improving of the procedure and steps that are utilized in functional modelling of the
application. The utilization of a procedure oriented strategy during the structure of data
frameworks actualized the service oriented engineering. Here, we have created data flow
diagrams, Level 0 and Lower Level diagram in order better understand the functional
requirements of the application. Also, we have developed User persona of a user customer
who is the main user and application will be developed according to his requirements only.
ICT115 Report Template Page 6

Introduction to Systems Design – Report Template
This paper has revealed from a contextual analysis of user experience with system
development and utilization of
personas in the development process.
As we have to devlop application for Ryanvir airlines,
profiles and personas were found especially valuable in
making an interpretation of framework necessities into interface plan, improvement of
progress management and preparing methodologies, also, users will be identified with
various personalization needs. In light of the discoveries in this analysis, we intend to direct
a field explore different avenues regarding experienced frameworks investigators and
engineers to expand our research model. Personas can also be risky process as if it
is developed by focusing wrong user group, this application can be developed by
considering wrong group of users. Situations and client stories are viewed as helpful in
integrating with personas. In specific, client stories have been utilized to depict client
circumstances and as a prerequisites particular. The outcomes displayed in this paper are
qualitative that depends on customers and admin user requirements.
4 Recommendations
 It is recommended that the system must be developed using agile methodology as it is
easy and takes less time in system development.
 It is recommended that object oriented system analysis methodology will be used in
developing UML diagrams.
 Customer interviews, and user observation methodology will be used for gathering
system requirements.
5 References
Nayan, N., M. and Zaman, H., B. (2009). Information System Development Model: Theories
Analysis and Guidelines. Visual Informatics: Bridging Research and Practice pp 894-904.
[Online] Available at: https://link.springer.com/chapter/10.1007/978-3-642-05036-7_85
[Accessed 28th September 2019]
Shendryk, V. and Boiko, A. (2015). Stages of information system development in the process
approach. Procedia Computer Science 77 ( 2015 ) 98 – 103. [Online] Available at:
https://www.researchgate.net/publication/290507570_Stages_of_Information_System_Dev
elopment_in_the_Process_Approach [Accessed 28th September 2019]
ICT115 Report Template Page 7

Introduction to Systems Design – Report Template
What is a data flow diagram? Lucid Software Inc. 2019. [Online] Available at:
https://www.lucidchart.com/pages/data-flow-diagram [Accessed 28th September 2019]
Rouse, M. (2019). Storyboard. [Online] Available at:
https://whatis.techtarget.com/definition/storyboard [Accessed 28th September 2019]
ICT115 Report Template Page 8

Introduction to Systems Design – Report Template
ICT115 Report Template Page 9