You are required to develop a series of design models for a software-based system that assists in
the management of air traffic control information. The system is to be called Flight Management
System (FMS). The remit for FMS is described informally below:
FMS shall assist with the management of flight plans and flight strips. A flight plan is
created whenever a pilot wishes to fly within controlled airspace. A flight strip contains
the information that an air traffic controller requires in order to manage aircraft within the
sector of controlled air space that they are responsible for. Within the FMS both flight
plans and flight strips will be digital. A pilot shall interact with the FMS in order to create
a flight plan while an air traffic services assistant (ATSA) shall interact with the FMS in
order to create flight strips. Each time a pilot wishes to create a flight plan they shall
be required to provide a six digit PIN. Only the pilot that intends to make a flight can
create the associated flight plan. The FMS shall manage a collection of pilot records
which record: a pilot’s unique identifier, known as a PID; the PIN associated with the
PID; the pilot’s name; contact phone number; a list of airports that the pilot is certified

to take-off from and land at – using the International Air Transport Association’s (IATA)

location identifier format, i.e. a unique 3-letter code, e.g. EDI (Edinburgh), DXB (Dubai
International), KUL (Kuala Lumpur International). A flight plan shall require the following
information: a unique identifier for the flight plan, known as the FPID; the pilot’s PID;
the codes (IATA format) for the planned departure and destination airports; an expected
departure time (EDT). The FMS shall record the following information for each airport:
its IATA code; its full name; the name of the nearest city to the airport; its location,
i.e. latitude/longitude coordinates. Once a flight plan has been successfully created a
corresponding flight strip must be created before the flight can depart. The role of an
ATSA is to interact with the FMS in order to create a flight strip for each flight plan. The
FMS is required to allow an ATSA to process multiple flight plans in a single session.
Before a session starts a ATSA is required to log into the FMS using a six digit PIN.
Each ATSA has a unique identifier, known as an AID. FMS shall manage a collection
of ATSA records which record a ATSA’s AID and PIN. To end a session, an ATSA is
required to logout of the FMS. During a session, when an ATSA requests a flight plan
to process, the FMS presents both the flight plan details along with the available routes.
The FMS shall use external software called the Route Finder System (RFS) to find a
list of available routes between the departure and destination airports. As inputs from
the FMS, the RFS requires the IATA codes for the departure and destination airports
along with the EDT. It is the responsibility of the ATSA to decide which of the available
routes, supplied by through the FMS from the RFS, is allocated to the flight, i.e. added
to the flight strip. Note that it is possible that no routes are available for the given flight
plan. A flight strip shall contain the following information: a unique identifier for the flight
strip, known as the FSID; the departure airport (IATA code); the destination airport (IATA
code); the allocated route; the EDT; a status flag that indicates if a flight strip is active
or inactive. On creation, a flight strip is active. Note that the FMS is part of a larger
system-of-systems. At the end of a flight another system will set the flight strip to be
inactive. Daily at 23:59 (GMT), the FMS shall send a list of the inactive flights strips (i.e.
their FSID along with departure and destination airports (IATA codes)) to an external
Flight Archive System (FAS). The FMS shall then delete the inactive flight strips and
their associated flight plan records.
Based upon the informal description above, you are first required to define and model a set of
requirements for the FMS. Secondly, you are required to developed a set of design models that
achieve your requirements. Thirdly, you are required to derive a set of test case scenarios using
aspects of your design models. Guidance: the FMS needs to robust, e.g. it needs to be able to
deal with erroneous or inconsistent inputs. Your requirements and design models should reflect this. Develop a Use Case model for the FMS that includes at least base use cases for:
• Create Flight Plan.
• Create Flight Strip.
• Archive Flight Strip.
Guidance: you may require additional base use cases and auxiliary use cases (i.e. inclu-
sion/extension use cases). Your Use Case model should include ONE Use Case Diagram
and Use Case Specifications (textual descriptions) for all your use cases. Guidance: don’t
forget to specify alternative flows. Any auxiliary use case(s) that you choose to introduce
should appear within the Use Case Diagram and their Use Case Specifications should also
be defined.

Question

You are required to develop a series of design models for a software-based system that assists in
the management of air traffic control information. The system is to be called Flight Management
System (FMS). The remit for FMS is described informally below:
FMS shall assist with the management of flight plans and flight strips. A flight plan is
created whenever a pilot wishes to fly within controlled airspace. A flight strip contains
the information that an air traffic controller requires in order to manage aircraft within the
sector of controlled air space that they are responsible for. Within the FMS both flight
plans and flight strips will be digital. A pilot shall interact with the FMS in order to create
a flight plan while an air traffic services assistant (ATSA) shall interact with the FMS in
order to create flight strips. Each time a pilot wishes to create a flight plan they shall
be required to provide a six digit PIN. Only the pilot that intends to make a flight can
create the associated flight plan. The FMS shall manage a collection of pilot records
which record: a pilot’s unique identifier, known as a PID; the PIN associated with the
PID; the pilot’s name; contact phone number; a list of airports that the pilot is certified

to take-off from and land at – using the International Air Transport Association’s (IATA)

location identifier format, i.e. a unique 3-letter code, e.g. EDI (Edinburgh), DXB (Dubai
International), KUL (Kuala Lumpur International). A flight plan shall require the following
information: a unique identifier for the flight plan, known as the FPID; the pilot’s PID;
the codes (IATA format) for the planned departure and destination airports; an expected
departure time (EDT). The FMS shall record the following information for each airport:
its IATA code; its full name; the name of the nearest city to the airport; its location,
i.e. latitude/longitude coordinates. Once a flight plan has been successfully created a
corresponding flight strip must be created before the flight can depart. The role of an
ATSA is to interact with the FMS in order to create a flight strip for each flight plan. The
FMS is required to allow an ATSA to process multiple flight plans in a single session.
Before a session starts a ATSA is required to log into the FMS using a six digit PIN.
Each ATSA has a unique identifier, known as an AID. FMS shall manage a collection
of ATSA records which record a ATSA’s AID and PIN. To end a session, an ATSA is
required to logout of the FMS. During a session, when an ATSA requests a flight plan
to process, the FMS presents both the flight plan details along with the available routes.
The FMS shall use external software called the Route Finder System (RFS) to find a
list of available routes between the departure and destination airports. As inputs from
the FMS, the RFS requires the IATA codes for the departure and destination airports
along with the EDT. It is the responsibility of the ATSA to decide which of the available
routes, supplied by through the FMS from the RFS, is allocated to the flight, i.e. added
to the flight strip. Note that it is possible that no routes are available for the given flight
plan. A flight strip shall contain the following information: a unique identifier for the flight
strip, known as the FSID; the departure airport (IATA code); the destination airport (IATA
code); the allocated route; the EDT; a status flag that indicates if a flight strip is active
or inactive. On creation, a flight strip is active. Note that the FMS is part of a larger
system-of-systems. At the end of a flight another system will set the flight strip to be
inactive. Daily at 23:59 (GMT), the FMS shall send a list of the inactive flights strips (i.e.
their FSID along with departure and destination airports (IATA codes)) to an external
Flight Archive System (FAS). The FMS shall then delete the inactive flight strips and
their associated flight plan records.
Based upon the informal description above, you are first required to define and model a set of
requirements for the FMS. Secondly, you are required to developed a set of design models that
achieve your requirements. Thirdly, you are required to derive a set of test case scenarios using
aspects of your design models. Guidance: the FMS needs to robust, e.g. it needs to be able to
deal with erroneous or inconsistent inputs. Your requirements and design models should reflect this. Develop a Use Case model for the FMS that includes at least base use cases for:
• Create Flight Plan.
• Create Flight Strip.
• Archive Flight Strip.
Guidance: you may require additional base use cases and auxiliary use cases (i.e. inclu-
sion/extension use cases). Your Use Case model should include ONE Use Case Diagram
and Use Case Specifications (textual descriptions) for all your use cases. Guidance: don’t
forget to specify alternative flows. Any auxiliary use case(s) that you choose to introduce
should appear within the Use Case Diagram and their Use Case Specifications should also
be defined.

Accepted Answer

Introduction:
This question involves the development of design models for a software-based Flight…