Aip Icao Template - PDF by rmi15865

VIEWS: 75 PAGES: 56

More Info
									EUROPEAN ORGANISATION FOR THE SAFETY OF
            AIR NAVIGATION


                                                         EUROCONTROL




         Requirements for AIP
           Audit Assistant




                                     AIM/AEP/0001


                      Edition         :                  1.0
                      Edition Date    :       18 June 2004
                      Status          :      Released Issue
                      Class           :      General Public




EUROPEAN AIR TRAFFIC MANAGEMENT PROGRAMME
               DOCUMENT IDENTIFICATION SHEET

                                   DOCUMENT DESCRIPTION

                                          Document Title
                                 Requirements for AIP Audit Assistant




EWP DELIVERABLE REFERENCE NUMBER
      PROGRAMME REFERENCE INDEX                     EDITION :                           1.0
                AIM/AEP/0001                        EDITION DATE :                  18 June 2004
                                                 Abstract
This document contains the requirements for a software tool to facilitate auditing of an AIP document.
The purpose of this tool is to provide checklists against which to check each section of the AIP
document, keep track responses to these checklists and record any follow-up action resulting from
identified anomalies. The tool is intended to be used by AIS organisation staff.




                                             Keywords
AIP                      Audit                    Checklist




  CONTACT PERSON :          M. Unterreiner          TEL : 3038             UNIT :        DAS/AIM


                                 DOCUMENT STATUS AND TYPE

         STATUS                            CATEGORY                          CLASSIFICATION
Working Draft                      Executive Task                       General Public
Draft                              Specialist Task                      EATMP
Proposed Issue                     Lower Layer Task                     Restricted
Released Issue

INTERNAL REFERENCE NAME :              AHEAD Electronic Filing System
Requirements for AIP Audit Assistant                                        AIM/AEP/0001



                                       DOCUMENT APPROVAL


The following table identifies all management authorities that have successively approved
the present issue of this document.



    AUTHORITY                          NAME AND SIGNATURE                   DATE


                           Ertan Ozkan              Tarkan Sevim
    Author/Editor                                                       18 June 2004




     Programme             Conrad Cleasby                               18 June 2004
      Manager



 Quality Assurance




Edition: 1.0                                Released Issue                         Page iii
AIM/AEP/0001                                                    Requirements for AIP Audit Assistant



                            DOCUMENT CHANGE RECORD


The following table records the complete history of the successive editions of the present
document.



                                                                                     SECTIONS
EDITION          DATE                  REASON FOR CHANGE                              PAGES
                                                                                     AFFECTED
  0.1          3 Nov 2003   Creation                                                    All

  1.0      18 June 2004     Update for release of version 1.0                              All




Page iv                                Released Issue                                    Edition: 1.0
Requirements for AIP Audit Assistant                                                                                  AIM/AEP/0001



                                                TABLE OF CONTENTS


1.         INTRODUCTION ........................................................................................................ 1
     1.1           Purpose and scope ......................................................................................... 1
     1.2           References....................................................................................................... 1
     1.3           Glossary........................................................................................................... 1
     1.4           Acronyms and Abbreviations ........................................................................ 2
2.         USE-CASES .............................................................................................................. 3
     2.1           Introduction ..................................................................................................... 3
     2.2           Actors and User Roles.................................................................................... 3
           2.2.1       Auditor .......................................................................................................... 3
           2.2.2       Audit Administrator ....................................................................................... 3
     2.3           Use-Cases for each Actor .............................................................................. 4
           2.3.1       Use-Case: Login to system .......................................................................... 5
           2.3.2       Use-Case: Edit state specific information..................................................... 6
           2.3.3       Use-Case: Edit contact information .............................................................. 7
           2.3.4       Use-Case: Execute an audit......................................................................... 8
           2.3.5       Use-Case: Edit action list ............................................................................. 9
           2.3.6       Use-Case: Create audit report.................................................................... 10
           2.3.7       Use-Case: Manage user accounts ............................................................. 11
           2.3.8       Use-Case: Create state specific information .............................................. 12
           2.3.9       Use-Case: Manage audits .......................................................................... 13
     2.4           Prototype User Interfaces ............................................................................ 14
3.         USER REQUIREMENTS ......................................................................................... 14
     3.1           Context........................................................................................................... 14
     3.2           Requirements ................................................................................................ 14
4.         SOFTWARE REQUIREMENTS ............................................................................... 14
     4.1           Environment .................................................................................................. 14
     4.2           Functional Requirements ............................................................................. 14
     4.3           Reporting Requirements .............................................................................. 14
     4.4           Maintainability Requirements ...................................................................... 14
     4.5           Documentation .............................................................................................. 14
5.         CONCEPTUAL ARCHITECTURE ........................................................................... 14
APPENDIX A             AIP TEMPLATE ......................................................................................... 14
APPENDIX B             PROTOTYPE USER INTERFACES .......................................................... 14
     A.1           Software Start-up and User Authentication................................................ 14
     A.2           Initialising or Continuing an Audit .............................................................. 14
     A.3           Auditing with AAA......................................................................................... 14
     A.4           Post-Audit ...................................................................................................... 14
Edition: 1.0                                             Released Issue                                                           Page v
AIM/AEP/0001                                                                       Requirements for AIP Audit Assistant



   A.5         Post-Audit Reports ....................................................................................... 14
   A.6         Other Features............................................................................................... 14
   A.7         Administrator Actions .................................................................................. 14
   A.8         Content Maintainer........................................................................................ 14




Page vi                                            Released Issue                                                Edition: 1.0
Requirements for AIP Audit Assistant                                                  AIM/AEP/0001




1.         INTRODUCTION

1.1        Purpose and scope

           The objective of this document is to specify user and software requirements of a tool
           that facilitates auditing of an AIP document. The tool will provide a series of checklist
           items to verify, and keep track of answers to the checklist items and actions
           resulting from discovered anomalies. The tool will be named as AAA (AIP Audit
           Assistant). Basic motivating business requirement for this tool is as follows:

                    Changes to an AIP are generally checked. However, there is no periodic
                    review of the complete AIP. This utility will be used to check the structure of
                    an AIP systematically and periodically1.

           The tool will be based on series of checklist items/questions defined on a standard
           AIP template. The checklist items or the questions will be related to what type of
           information should be present in a certain section. The checklist items will be given
           in three categories:

               •   Mandatory: What type of information should be present in section?

               •   Good Practice: What type of information can be present?

               •   Exclusions: What type of information should not be present?

           The tool is expected to provide on-line explanations and supporting material for the
           checklist items. Such explanation is necessary to clarify why presence of certain
           information is considered as good practice, as each person might have his/her own
           idea about what should be included or excluded in a given section. For the
           anomalies identified during an audit, the user will be able to create follow-up actions.

           The tool will provide facilities to define the persons responsible for the maintenance
           of information within the AIP document. This is considered a good practice the
           resolution of identified problems during an audit.

           At the end of the audit, the user will be able to create an audit report and an action
           list for identified problems.

           Target users are AIS organisations. Its usage will be voluntary. However, if an
           attractive and easy to use tool is provided, it is expected to be adopted by the AIS
           community.

1.2        References

           [1] Annex 15 To The Convention of International Civil Aviation, ICAO, 10th edition,
           July 1997.

           [2] Doc 8126. The structure of an AIP is given in this document.

           [3] ICAO AIP Template Review Report, Version 8a.

1.3        Glossary

           The terms defined in this section will have the associated description within this
           document.
1
    Periodic check of AIP is recommended as a good practice from Slovaque Republic.
Edition: 1.0                                   Released Issue                                Page 1
AIM/AEP/0001                                                    Requirements for AIP Audit Assistant



         Actor:     Anyone or anything that interacts with the system.

         Auditor:   The person conducting an AIP audit.

         Audit Administrator: User role for setting up AAA and auditor user accounts.

         System:    The tool under development.

         Use Case: A model for specification of what capabilities will be provided by the
                   system.

1.4      Acronyms and Abbreviations

         AHEAD      Automation and Harmonisation of European Aeronautical Data

         AIP        Aeronautical Information Publication

         AIS        Aeronautical Information Services

         ICAO       International Civil Aviation Organisation

         AAA        AIP Audit Assistant

         SRD        Software Requirements Document

         URD        User Requirements Document




Page 2                                    Released Issue                                 Edition: 1.0
Requirements for AIP Audit Assistant                                             AIM/AEP/0001




2.         USE-CASES

2.1        Introduction

           For the description of the AAA user requirements, a use case model will be used.
           The behaviour of the system, that is what functionality must be provided by the
           system, is documented in a use case model. Use case model illustrates the
           system’s intended functions (use cases), its surroundings (actors) and the
           relationships between the use cases and actors. Actors are not part of the system;
           they represent anyone or anything that must interact with the system. Use cases are
           documented with a flow of events. The flow of events for a use case is a description
           of the events needed to accomplish the required behaviour of the use case.

2.2        Actors and User Roles

           AAA is a software tool that will be used by a human operator and will not interface
           any other systems (except the computer on which it is running, but this is not
           considered an actor). Considering different usage of the system, three types of
           users or user roles are identified:

           •   Auditor,

           •   Audit Administrator.




                                       Figure 1. Types of users for AAA

2.2.1      Auditor

           Auditor is the person who executes an AIP audit. Auditor can be a single person or a
           member of an AIP audit team. Auditor is located within the AIS organization of each
           civil aviation administration.

2.2.2      Audit Administrator

           Audit Administrator is the person who sets up AAA for AIP audits. Typically, this
           includes setting up user accounts for Auditor(s), changing AAA parameters and
           initialising the AIP audit. This role can be executed by the same person as the
           Auditor for a small organisation. Audit Administrator is located within the AIS
           organization of each civil aviation administration.




Edition: 1.0                                       Released Issue                        Page 3
AIM/AEP/0001                                                      Requirements for AIP Audit Assistant




2.3      Use-Cases for each Actor

         The following use-cases are identified for these actors:

               Actor                   Use-Cases

               All                     Login to system

               Auditor                 Edit state specific information

                                       Edit contact information

                                       Execute an audit

                                       Edit action list

                                       Create audit report

               Audit Administrator     Manage user accounts

                                       Create state specific information

                                       Manage audits




                                Figure 2. Use case diagrams for Auditor




                       Figure 3. Use case diagram for Audit Administrator


Page 4                                   Released Issue                                    Edition: 1.0
Requirements for AIP Audit Assistant                                                       AIM/AEP/0001



2.3.1       Use-Case: Login to system

Creation date:          08/09/2003                  Modification date:

Version:                0.1                         Responsible:                   Tarkan Sevim

Use Case Name:          Login to the system

Description             The user starts AAA software and provides his user name and password. This use
                        case is prerequisite to the other use cases and provides entry point to the system.

Actors                  All

Pre-Conditions:         The AAA software must be installed on a PC with Microsoft Excel 97 and a user
                        account exists for the current user.

Actor Action                                          System Response

1-Nominal Scenario

1           The user starts the AAA software.         1.1         The system requests the user to enter a
                                                                  user name and password.

            The user enters his/her user name and     1.2         The system verifies the user name and
            password.                                             password. [Exception 1]

                                                      1.3         The system identifies the type of user as
                                                                  one of Auditor or Audit Administrator:

                                                      1.3.1       [Case Auditor]

                                                                  The system displays the options for the
                                                                  Auditor and continues with one of Auditor
                                                                  use cases.

                                                      1.3.2       [Case Audit Administrator]

                                                                  The system displays the options for the
                                                                  Audit Administrator and continues with
                                                                  one of Audit Administrator use cases.



Exceptions

[Exception 1]     Wrong user name or password                     The system re-requests the user name
                                                                  and password for up to three times. After
                                                                  three attempts, terminates the session
                                                                  and exits.



Post Conditions:        Application started successfully and user logged in.

Priority:               High

Performance:            None

Design                  None
Constraint:

Reference               Kick-off meeting
Documents:


Edition: 1.0                                     Released Issue                                   Page 5
AIM/AEP/0001                                                             Requirements for AIP Audit Assistant




Comments:

Open Issue:              None



2.3.2       Use-Case: Edit state specific information

Creation date:           08/09/2003                     Modification date:

Version:                 0.1                            Responsible:               Tarkan Sevim

Use Case Name:           Edit state specific information

Description              The auditor provides the names for state specific data like aerodromes and
                         heliports. The information will be saved as part of the audit.

Actors                   Auditor

Pre-Conditions:          “Login to system” use case has been executed and user identified as Auditor.

Actor (Auditor) Action                                     System Response

1-Nominal Scenario

1           The auditor requests to enter state            1.1    The system provides a form for entering
            specific information.                                 section numbers and aerodrome/heliport
                                                                  names.

2           The auditor fills in the section numbers,      2.1    The system reads the section numbers
            specific item names and accepts the                   and item names, and saves the new
            form. The user repeats this for all the               sections as part of audit. [Exception 1]
            available aerodromes and heliports.

3           The auditor continues with the audit.

Exceptions

[Exception 1]     Incomplete data                                 If section number or the name is not
                                                                  present for an entry an error is displayed
                                                                  and the user is requested to correct.

Post Conditions:         None

Priority:                High

Performance:             None

Design                   None
Constraint:

Reference                Kick-off meeting
Documents:

Comments:

Open Issue:              None




Page 6                                          Released Issue                                    Edition: 1.0
Requirements for AIP Audit Assistant                                                                 AIM/AEP/0001



2.3.3       Use-Case: Edit contact information

Creation date:          08/09/2003                     Modification date:

Version:                0.1                            Responsible:                       Tarkan Sevim

Use Case Name:          Edit contact information

Description             The auditor provides the contact information for people responsible for maintaining
                        the AIP data. The contact information is maintained as a list and is referred from
                        an AIP section as responsible for this information.

Actors                  Auditor

Pre-Conditions:         “Login to system” use case has been executed and user identified as Auditor.

Actor (Auditor) Action                                    System Response

1-Nominal Scenario

1           The auditor requests to enter new            1.1          The system          displays     the    contact
            contact information.                                      information list.

2           The auditor fills in the contact
            information for new contacts or updates
            the existing ones. The auditor repeats
            this for other contact information.

3           The auditor requests to define               3.1          The system displays the AIP tree view.
            responsible person for AIP information.

4           The auditor selects the sections to          4.1          The system displays the contact
            associate to a given contact and                          information list to choose from with an
            requests to enter contact information.                    option to create a new contact

5           The auditor selects an existing contact      5.1          [Case existing contact selected]
            or requests creation of a new one.
                                                                      The system associates the selected
                                                                      contact to the section as the responsible.

                                                         5.2          [Case new contact entry]

                                                                      The system display a form for contact
                                                                      information entry

5.2.1       The auditor fills in the contact             5.2.2        The system appends the new contact
            information for the new user and                          information to the contact list and
            validates.                                                associates the new contact to the section
                                                                      as the responsible. [Exception 1]

Exceptions

[Exception 1]     Insufficient contact information                    The system reports that the provided data
                                                                      is not sufficient and requests the user to
                                                                      provide required data.

Post Conditions:        None

Priority:               High

Performance:            None

Design                  None
Constraint:

Edition: 1.0                                         Released Issue                                          Page 7
AIM/AEP/0001                                                           Requirements for AIP Audit Assistant




Reference              Kick-off meeting
Documents:

Comments:

Open Issue:            None



2.3.4      Use-Case: Execute an audit

Creation date:         08/09/2003                     Modification date:

Version:               0.1                            Responsible:               Tarkan Sevim

Use Case Name:         Execute an audit

Description            The auditor executes an audit (complete or partial) by going through each section
                       of the AIP document using the AAA software. The auditor can also create follow-
                       up actions as part of the audit process.

Actors                 Auditor

Pre-Conditions:        “Login to system” use case has been executed and user identified as Auditor.

Actor (Auditor) Action                                 System Response

1-Nominal Scenario

1          The auditor requests to perform an                   The system checks whether there are
           audit.                                               uncompleted audit sessions for this user:

                                                       1.1      [Case no audit sessions]

                                                                The system requests to create a new
                                                                audit session.

1.1.1      The auditor enters a name for the audit
           session.

                                                       1.2      [Case uncompleted audit sessions]

                                                                The system lists the available audit
                                                                sessions for this user as well as the option
                                                                to create a new audit session.

1.2.1      The auditor selects a session name from
           the list or creates a new one.

                                                       1.3      The system creates and displays the tree
                                                                view for AIP template.

2          The auditor selects a section from the      2.1      The system creates and displays a
           AIP template.                                        checklist for the selected AIP section.
                                                                [Exception 1]

3          The auditor completes the checklist by      3.1      The system records auditor’s actions
           ticking appropriate check boxes.

4          The auditor executes Use Case: Edit
           action list to create a follow-up action
           for an anomaly in that section.


Page 8                                       Released Issue                                     Edition: 1.0
Requirements for AIP Audit Assistant                                                           AIM/AEP/0001




            The auditor repeats the steps 2-4 for
            other sections.
                                                                     The system updates audit history with the
5           The auditor saves the audit data.              5.1
                                                                     completed audit.
6           The auditor executes Use Case: Create
            audit report to display the results for the
            audit.
                                                                     The system requests to save changes and
7           The auditor quits the application.             7.1
                                                                     terminates.
Exceptions

[Exception 1]     The section is not assigned to                     The system reports the error.
                  current auditor.

Post Conditions:         None

Priority:                High

Performance:             None

Design                   None
Constraint:

Reference                Kick-off meeting
Documents:

Comments:

Open Issue:              None



2.3.5       Use-Case: Edit action list

Creation date:           08/09/2003                       Modification date:

Version:                 0.1                              Responsible:               Tarkan Sevim

Use Case Name:           Edit action list

Description              The auditor reviews the list of actions identified during the audit. The auditor can
                         print out the action list or include the action list in a document or e-mail.

Actors                   Auditor

Pre-Conditions:          “Login to system” use case has been executed, user identified as Auditor and an
                         audit session selected.

Actor (Auditor) Action                                     System Response

1-Nominal Scenario

1           The auditor requests to edit the list of       1.1       The system displays the list of actions for
            actions for the current audit.                           the current audit with all data.

2           User requests sorting of the action with       2.1       The system sorts the action list and
            respect responsible person.                              displays it.


3           The auditor updates certain fields in the      3.1       The system reflects the updates.
            action list.

Edition: 1.0                                        Released Issue                                      Page 9
AIM/AEP/0001                                                                 Requirements for AIP Audit Assistant




4           The auditor copies/pastes a group of             4.1      The system transfers the copy/paste data
            actions          into        another                      to the external document.
            document/application.

            The auditor may perform any operation
            in the other application
                                                                      The system requests to save changes and
5           The auditor quits the application.               5.1
                                                                      terminates.
Exceptions



Post Conditions:         None

Priority:                High

Performance:             None

Design                   None
Constraint:

Reference                Kick-off meeting
Documents:

Comments:

Open Issue:              None



2.3.6       Use-Case: Create audit report

Creation date:           08/09/2003                         Modification date:

Version:                 0.1                                Responsible:               Tarkan Sevim

Use Case Name:           Create audit report

Description              The auditor creates a report for an audit.

Actors                   Auditor

Pre-Conditions:          “Login to system” use case has been executed and user identified as Auditor.

Actor (Auditor) Action                                       System Response

1-Nominal Scenario

1           The auditor requests to create an audit          1.1      The system lists all the audit sessions.
            report.                                                   [Exception 1]

2           The auditor     selects   an    audit     and    2.1      The system creates and displays the tree
            accepts.                                                  view for AIP template with scores for each
                                                                      section, combined scores for sections and
                                                                      overall scores. The list of actions
                                                                      corresponding to the audit is provided as
                                                                      part of the report.

3           The auditor requests print out of the            3.1      The system prints out the audit report as
            audit report.                                             displayed on screen.

4           The auditor copies/pastes the audit              4.1      The system transfers the copy/paste data

Page 10                                             Released Issue                                    Edition: 1.0
Requirements for AIP Audit Assistant                                                           AIM/AEP/0001



            report to another document/application.                to the external document.

5           The auditor quits the application.           5.1       The system requests to save changes (if
                                                                   any) and terminates.

Exceptions

[Exception 1]     There are no audits                              The system reports the error that there
                                                                   are no audits.

Post Conditions:         None

Priority:                High

Performance:             None

Design                   None
Constraint:

Reference                Kick-off meeting
Documents:

Comments:

Open Issue:              None



2.3.7       Use-Case: Manage user accounts

Creation date:           08/09/2003                     Modification date:

Version:                 0.1                            Responsible:               Tarkan Sevim

Use Case Name:           Manage user accounts

Description              The auditor creates a new auditor account or modifies an existing one.

Actors                   Audit Administrator

Pre-Conditions:          “Login to system” use case has been executed and user identified as Audit
                         Administrator.

Actor (Audit Administrator) Action                       System Response

1-Nominal Scenario

1           The audit administrator requests to          1.1       The system displays an empty user
            create a new auditor user account.                     account form.

1.2         The audit administrator fills in the user    1.3       The system creates a new auditor user
            name, password and other personal                      account. [Exception 1]
            data, and accepts the form.

2           The audit administrator requests to          2.1       The system displays the list of all auditor
            modify auditor user accounts.                          user accounts. [Exception 2]

2.2         The audit administrator selects       an     2.3       The system displays user data in user
            auditor user account from the list.                    account form.

2.4         The audit administrator modifies certain     2.5       The system modifies the user account.
            fields and accepts the form.                           [Exception 1]

Exceptions

Edition: 1.0                                      Released Issue                                     Page 11
AIM/AEP/0001                                                             Requirements for AIP Audit Assistant




[Exception 1]     User name already exists or                     The system reports the error and requests
                  missing data                                    the user to correct.

[Exception 2]     No auditor user accounts                        The system reports the error.

Post Conditions:        None

Priority:               High

Performance:            None

Design                  None
Constraint:

Reference               Kick-off meeting
Documents:

Comments:

Open Issue:             None



2.3.8       Use-Case: Create state specific information

Creation date:          08/09/2003                      Modification date:

Version:                0.1                             Responsible:               Tarkan Sevim

Use Case Name:          Create state specific information

Description             The audit administrator provides the names for state specific data like aerodromes
                        and heliports. This use case is similar to the Edit state specific information use
                        case, the difference is that the information is saved to audit template instead of the
                        audit.

Actors                  Audit Administrator

Pre-Conditions:         “Login to system” use case has been executed and user identified as Auditor.

Actor (Audit Administrator) Action                       System Response

1-Nominal Scenario

1           The audit administrator requests to          1.1      The system provides a form for entering
            create state specific information.                    section numbers and aerodrome/heliport
                                                                  names.

2           The audit administrator fills in the         2.1      The system reads the section number and
            section numbers, specific item names                  item names and saves the new sections
            and accepts the form. The user repeats                as part of the audit template. [Exception 1]
            this for all the available aerodromes and
            heliports.

3           The audit administrator continues with
            the audit administration.

Exceptions

[Exception 1]     Incomplete data                                 If section number or the name is not
                                                                  present for an entry an error is displayed
                                                                  and the user is requested to correct.


Page 12                                        Released Issue                                     Edition: 1.0
Requirements for AIP Audit Assistant                                                         AIM/AEP/0001




Post Conditions:        None

Priority:               High

Performance:            None

Design                  None
Constraint:

Reference               Kick-off meeting
Documents:

Comments:

Open Issue:             None



2.3.9       Use-Case: Manage audits

Creation date:          08/09/2003                      Modification date:

Version:                0.1                             Responsible:                Tarkan Sevim

Use Case Name:          Manage audits

Description             The auditor creates a new audit session or modifies the settings for an existing
                        one.

Actors                  Audit Administrator

Pre-Conditions:         “Login to system” use case has been executed and user identified as Audit
                        Administrator.

Actor (Audit Administrator) Action                       System Response

1-Nominal Scenario

1           The audit administrator requests to          1.1        The system initialises the auditing
            create a new audit session.                             environment and displays the tree view for
                                                                    AIP template.

1.2         The audit administrator selects a range      1.3        The system displays a list of auditor user
            of sections from the tree view and                      accounts. [Exception 1]
            requests to assign it to an auditor.

1.4         The audit administrator      selects   an    1.5        The system records the user account as
            auditor from the list.                                  the auditor for the selected sections.

            The audit administrator repeats the
            steps 1.2 and 1.4 to delegate audits for
            other sections

2           The audit administrator requests to          2.1        The system displays the list of all
            modify the settings for an ongoing audit.               uncompleted audits. [Exception 2]

2.2         The audit administrator selects an audit     2.3        The system displays the tree view for AIP
            from the list.                                          template for the selected audit.

2.4         The audit administrator selects a range      2.5        The system displays a list of auditor user
            of sections from the tree view and                      accounts. [Exception 1]
            requests to assign it to an (other)
            auditor.

Edition: 1.0                                       Released Issue                                   Page 13
AIM/AEP/0001                                                       Requirements for AIP Audit Assistant




2.5         The audit administrator   selects   an   2.6     The system records the user account as
            auditor from the list.                           the auditor for the selected sections.

Exceptions

[Exception 1]    No auditor user accounts                    The system reports the error.

[Exception 2]    No uncompleted audits                       The system reports the error.

Post Conditions:       None

Priority:              High

Performance:           None

Design                 None
Constraint:

Reference              Kick-off meeting
Documents:

Comments:

Open Issue:            None



2.4         Prototype User Interfaces

            Prototypes for user interfaces that were mentioned in the use cases given in Section
            2.3 are included in Appendix B.




Page 14                                     Released Issue                                   Edition: 1.0
Requirements for AIP Audit Assistant                                                  AIM/AEP/0001




3.         USER REQUIREMENTS

3.1            Context

           An AIP document is composed of several main sections, each section dedicated to
           a certain part of AIS, like routes and aerodromes. Each section in turn contains
           subsections for more specific items or instances. There will be a separate checklist
           for each subsection, and each subsection will be checked against the corresponding
           checklist.

           Although AIP document is verified with respect to modified and new information,
           there is no procedure for reviewing the entire AIP document. It has been identified
           as a good practice to review the entire AIP document periodically. The AAA software
           tool is envisaged to facilitate a complete review or an audit of the AIP document. It
           will provide a consistent set of criteria against which to conduct an audit, possibility
           to keep track of the audit results and to follow up corrective actions.

           The idea of the tool is to provide a checklist against which the auditor will check
           each section of the AIP. For each section of the AIP, the tool shall provide a set of
           checklist items corresponding to the following categories:

           •     Mandatory: What must be and must not be there? (as given in the AIP
                 reference Annex 15 [1])

           •     Good Practice: What are the recommended practices? (Nice to have/Optional)

           •     Exclusions: What should not be there? (Bad/Exclusions)

           This checklist of items will be questions related to the content of a section and the
           responses will be provided by simple checkboxes. Additional information will be
           available for each question to provide background information and references if
           available. This additional information is provided to remove any ambiguities and
           clarify the reason why it has been attributed to that category.

3.2        Requirements

           General

           UR 1.     The tool shall use the AIP template given in Annex 15 [1] as the initial AIP
                     template. This AIP template is included in this document in Appendix A

           UR 2.     The tool shall support operation for two types of users (see Section 2.2 for
                     more info):

                     •   Audit Administrator,

                     •   Auditor.

           UR 3.     The tool shall use user name and password based authentication to identify
                     a user.

           UR 4.     The tool shall allow total or partial auditing of the AIP document. Total audit
                     is the case where all AIP sections are audited and partial audit is where
                     only a subset of AIP sections is audited.

           UR 5.     The tool shall allow the audit of an AIP document to be done by one or
                     more auditors. It is expected that the AIP sections will be exclusively
Edition: 1.0                                    Released Issue                              Page 15
AIM/AEP/0001                                                      Requirements for AIP Audit Assistant



                   shared if audit is conducted by more than one auditor; that is a section will
                   not be audited by two auditors.

          UR 6.    The tool shall be able to merge partial audits conducted by multiple
                   auditors.

          UR 7.    It shall be possible to audit single volume or multi volume AIP documents.

          UR 8.    Each AIP volume in a multi-volume AIP shall be treated as a separate AIP
                   document for auditing purposes.

          UR 9.    It shall be possible to audit AIP documents published in a single language
                   or multiple languages.

          UR 10. Each language edition for an AIP published in multiple languages shall be
                 treated as a separate AIP document for auditing purposes.

          UR 11. It shall be possible to upgrade the tool by downloading updated via Internet.
                 The procedure for such an update should be provided along with the
                 update.

          UR 12. The tool shall provide on-line help facility.

          UR 13. The tool shall be provided with a User’s Manual.

          UR 14. The tool shall be developed on top of Microsoft Excel ’97.

          Audit Data

          UR 15. The tool shall store data to identify an audit. Audit identification includes the
                 following:

                   •   AIP document identification:

                           o   Name,

                           o   Reference number,

                           o   Edition date,

                           o   Single or multi volume,

                           o   Volume number (if multi volume AIP),

                           o   Language (if AIP is published in multiple languages).

                   •   Auditor identification:

                           o   Name,

                           o   Location or organizational unit.

                   •   Audit identification:

                           o   Start date,

                           o   Auditor name,


Page 16                                        Released Issue                              Edition: 1.0
Requirements for AIP Audit Assistant                                               AIM/AEP/0001



                             o   Total or partial audit,

                             o   Single or group auditor.

           UR 16. The tool shall store the responses for the audit checklist items. The
                  responses to checklist items constitute the audit results. Audit score will be
                  calculated using these responses.

           UR 17. State specific information, namely aerodromes and heliports, shall be kept
                  as part of audit template data. This audit template shall be used to initialise
                  an audit. An audit template exists for each AIP document volume; multi-
                  language AIP documents can share the same audit template.

           UR 18. It shall be possible to create and modify state specific information during an
                  audit. Such modifications will only apply to the audit, and not to the audit
                  template.

           UR 19. The tool shall store follow-up actions related to an AIP section or the AIP
                  document as part of audit data.

           UR 20. The tool shall store contact information for AIP stakeholders.

           Audit Execution

           UR 21. The audit administrator and auditor shall be able to add state specific
                  information to populate the following sections of AIP template:

                    •   AD 2 Aerodromes,

                    •   AD 3 Heliports.

           UR 22. For audit administrator, state specific information shall be saved to the audit
                  template and will be available for following audits.

           UR 23. For auditor, state specific information shall be saved to the audit being
                  conducted only.

           UR 24. The auditor shall be able to create a new audit or continue a previous audit
                  create by himself/herself.

           UR 25. The auditor shall be able to select the sections for auditing for a new audit.

           UR 26. The auditor shall be able to initialise the audit by creating the checklist
                  items. The checklist items that are created correspond to the audited AIP
                  section.

           UR 27. The auditor shall be able to enter contact information for stakeholders of
                  AIP document. Stakeholders can be persons responsible for maintaining
                  the data or people that need to be notified in case of changes.

           UR 28. The auditor shall be able to define a data originator for an AIP section. This
                  can be done by selecting from the contact list or creating a new contact.

           UR 29. The auditor shall be able to specify other stakeholders for an AIP section.
                  The stakeholders are the people to be notified in case of changes to an AIP
                  section.



Edition: 1.0                                     Released Issue                           Page 17
AIM/AEP/0001                                                    Requirements for AIP Audit Assistant



          UR 30. The auditor shall be able to specify comments for each checklist item. The
                 comments are intended to serve as remarks from the auditor that does not
                 necessarily require a follow-up.

          UR 31. The tool shall display the comments and originator information for a
                 checklist item if provided.

          UR 32. The tool shall display the originator and stakeholders for an AIP section.

          UR 33. During an audit session, the auditor shall be able to view and fill in the
                 checklist items for a sections selected for auditing. This is the actual
                 auditing process, where AIP document is checked against each checklist
                 item and a response is entered.

          UR 34. The tool shall not display nor permit an auditor to modify checklist items for
                 sections that are not assigned to him.

          UR 35. The tool shall store the responses to checklist items as part of the audit.

          UR 36. After all checklist items for a section is answered, selecting another section
                 for audit or accepting the answers shall be recorded as section being
                 audited.

          UR 37. It shall be possible to modify the responses for an audited section. This
                 facility is intended for correcting errors made during the audit.

          UR 38. The tool shall keep track of such re-audited sections.

          UR 39. The auditor shall be able to create an action to keep track of anomalies for
                 an AIP section.

          UR 40. The tool shall maintain the following information for an action:

                  •   Auditor name,

                  •   Section name and anomaly description,

                  •   Creation date and due date,

                  •   Responsible for the section.

          UR 41. The tool shall allow creation of actions with no due date or responsible.
                 This is to be allowed since it is not up to the auditor to attribute these in a
                 typical AIS organisation.

          UR 42. The tool shall keep track of completed, partially audited and untouched
                 sections.

          Audit Session Logging

          UR 43. The tool shall keep track of audit progress with audit session log. An audit
                 session starts by the selection of an audit and ends when the tool is quitted.

          UR 44. The tool shall keep track of the following information in the audit session
                 log:

                  •   Session name,

Page 18                                   Released Issue                                 Edition: 1.0
Requirements for AIP Audit Assistant                                                AIM/AEP/0001




                    •    Auditor name,

                    •    Session start date and time,

                    •    Session end date and time,

                    •    List of sections audited during the session,

                    •    List of sections re-audited during the session.

           UR 45. The tool shall keep track of the last position being audited during the last
                  audit session.

           UR 46. For a new audit session, the tool shall start from the position at the end of
                  the previous audit session.

           UR 47. (Optional) The tool should keep track of date and time at which each
                  checklist item is answered. This information can be used to calculate the
                  amount of effort that went into auditing of each section and to view the
                  progress of the audit.

           Audit Reporting

           UR 48. The user shall be able to produce a report for AIP audit score.

           UR 49. AIP audit score shall be displayed as the overall audit score, and the
                  number of checklist items answered in each category and left unanswered.

           UR 50. The score shall be calculated as the number of correct answers divided by
                  the number of checklist items answered as correct or false.

           UR 51. The user shall be able produce the list of actions for an audit. This report
                  should contain all the fields defined for an action.

           UR 52. It shall be possible to include the comments created during the audit with
                  the action list.

           UR 53. It shall be possible to export the action list to other Windows applications or
                  save as a separate Excel document.

           UR 54. The user shall be able to produce the list of contacts. This report should
                  contain all the fields defined for a contact.

           UR 55. It shall be possible to export the contact list to other Windows applications
                  or save as a separate Excel document.

           UR 56. It shall be possible to produce a report containing the originator and
                  stakeholders for AIP sections.

           UR 57. It shall be possible to export the stakeholders list to other Windows
                  applications or save as a separate Excel document.

           Audit Administration

           UR 58. Audit administrator shall be able to create, remove and modify user
                  accounts.



Edition: 1.0                                   Released Issue                             Page 19
AIM/AEP/0001                                                    Requirements for AIP Audit Assistant



          UR 59. Audit administrator shall be able to create and remove audits, and to modify
                 audit settings.

          UR 60. For an audit, audit administrator shall be able to designate auditors for each
                 section of AIP template.

          Content Maintenance

          The audit is performed by responding to a set of checklist items. The checklist items
          and associated explanatory text is expected to be modified for updating or
          enhancing the audit.

          UR 61. It shall be possible to modify AIP template by adding a new section,
                 deleting a section or re-organizing the sections.

          UR 62. It shall be possible to create and modify checklists for any section of AIP
                 template.

          UR 63. Each checklist shall have items grouped in three categories:

                  •   Mandatory,

                  •   Good Practice,

                  •   Exclusions.

          UR 64. The checklist items shall be yes/no type questions where the answer can
                 be indicated by ticking the corresponding check box.

          UR 65. It shall be possible to group checklist items. This can be done in the case of
                 related questions.

          UR 66. It shall be possible to create and modify help information for checklist items.
                 This help information will provide explanation for checklist items.

          Miscellaneous

          Audit session logs can be used in several ways to assess the effort that went into to
          an audit. The audit progress can be assessed by colouring the AIP sections
          completed during different audit sessions. Audit session logs can be used to
          calculate the amount of effort spent on an audit or audit session log can be viewed
          to trace the audit process.

          UR 67. (Optional) It should be possible to colour the AIP sections according to the
                 audit session they have been audited.

          UR 68. (Optional) It should be possible to view the amount of effort spent during an
                 audit using the audit session log.

          UR 69. (Optional) It should be possible to view audit session logs including data
                 about start/end time, auditor and the sections completed.

          UR 70. The tool shall be designed with modern graphical user interface design
                 techniques and attractive to use.




Page 20                                   Released Issue                                 Edition: 1.0
Requirements for AIP Audit Assistant                                                 AIM/AEP/0001




4.         SOFTWARE REQUIREMENTS

4.1        Environment

           SR 1.    The tool shall be implemented as an add-on to Microsoft Excel 97.

           SR 2.    The tool shall run on a typical office PC with a properly functioning
                    Microsoft Excel 97 installation. A typical office PC is to be taken to have the
                    following configuration or higher: 166 MHz CPU, 64 MB RAM, 4 GB Hard
                    disk.

4.2        Functional Requirements

           SR 3.    The tool shall store the AIP template given in Annex 15 [1] within an Excel
                    sheet. Each row will contain a section of the AIP document and the section
                    hierarchy shall be maintained by heading levels.

           SR 4.    The tool shall support operation for two types of user roles:

                        •    Audit Administrator,

                        •    Auditor.

           SR 5.    The tool shall use user accounts and password based authentication to
                    determine valid users and their access rights.

           SR 6.    The tool shall maintain the following information for a user account in a
                    Excel Worksheet:

                        •    User name,

                        •    Password,

                        •    Full name,

                        •    User role.

           SR 7.    The following operations shall be available to an Audit Administrator:

                         •   Create new auditor user account,

                         •   Edit auditor user accounts,

                         •   Create state specific information,

                         •   Modify audit parameters.

           SR 8.    The following operations shall be available to an Auditor:

                         •   Audit related operations: New, Open, Save and Close,

                         •   Edit state specific information for audit,

                         •   Select sections for auditing,

                         •   Checklist related operations: Create and Fill,

Edition: 1.0                                    Released Issue                               Page 21
AIM/AEP/0001                                                      Requirements for AIP Audit Assistant




                      •    Action related operations: Create and Edit,

                      •    Contact list related operations: Create and Edit,

                      •    Audit reports generation: Audit Score, Action List, Contact List and
                           Data Originators.

          SR 9.   The tool shall store checklist items for each AIP section for the following
                  categories:

                     •     Mandatory,

                     •     Good Practice,

                     •     Exclusions.

          SR 10. The tools shall create a copy of the AIP template worksheet for a new audit
                 as a new Excel file.

          SR 11. The audit Excel file shall be protected with the password of the auditor.

          SR 12. The answers to the audit checklist items shall be stored in a column of the
                 AIP template worksheet.

          SR 13. The action list shall be maintained in an Excel worksheet.

          SR 14. The actions related to AIP sections shall contain the section number as the
                 reference. The actions general to the AIP document can be given no
                 reference or some distinctive reference.

          SR 15. The contact list shall be stored as an Excel sheet with a unique reference
                 number.

          SR 16. The data originator for AIP sections shall be stored in an Excel sheet
                 containing AIP section number and originator reference.

          SR 17. The stakeholders for AIP sections shall be stored in an Excel sheet
                 containing AIP section number and stakeholder references.

          SR 18. The comments shall be stored as an Excel sheet containing AIP section
                 number and the comments.

4.3       Reporting Requirements

          SR 19. The tool shall calculate a general score for an audit as the number of
                 correct answers divided by the total number of answered checklist items.
                 Unanswered checklist items and those answered as not applicable will not
                 be included in the total number.

          SR 20. The tool shall maintain an action list with the following information:

                          Related section,

                          Priority,

                          Creator


Page 22                                      Released Issue                                Edition: 1.0
Requirements for AIP Audit Assistant                                                 AIM/AEP/0001



                              Creation Date,

                              Responsible,

                              Due Date,

4.4        Maintainability Requirements

           SR 21. It shall be possible to add/remove/modify checklist items by accessing the
                  information via Excel worksheets.

           SR 22. New versions of the software shall be made available on the Eurocontrol
                  AIS website for download. All the modified software items (executables,
                  data files and documentation) will be made available as part of such
                  updates.

           SR 23. Each release of software and documentation shall be stored as a version
                  base with all supporting material.

           SR 24. The identified software problems shall be maintained as a list with severity
                  and priority.

           SR 25. Software updates shall be documented to provide the following information:

                       •    List of new features,

                       •    List of bug corrections,

                       •    Changes to the documentation,

                       •    Changes to third party software components.

4.5        Documentation

           SR 26. The following documentation shall be generated and maintained for this
                  project:

                   •       Requirements documents (user and software requirements with draft
                           GUIs),

                   •       User’s/Reference manual,

                   •       On-line context sensitive help,

                   •       Technical documentation – (information on how the code is organised),

                   •       Comments in the code.




Edition: 1.0                                        Released Issue                         Page 23
AIM/AEP/0001                                        Requirements for AIP Audit Assistant




5.        CONCEPTUAL ARCHITECTURE




                                      Entity                            Users




               Help Items         AIP Template                      Audit Session




                                Checklist Items                  Authors of Information




                              Justification Items




Page 24                      Released Issue                                  Edition: 1.0
Requirements for AIP Audit Assistant                                                              AIM/AEP/0001




APPENDIX A              AIP TEMPLATE
Title                  Description                                                                Comments
Part 1                 General (GEN)
   GEN 0
      GEN 0.1          Preface
      GEN 0.2          Record of AIP Amendments
      GEN 0.3          Record of AIP Supplements
      GEN 0.4          Checklist of AIP pages
      GEN 0.5          List of hand amendments to the AIP
      GEN 0.6          Table of contents to Part 1
   GEN 1               National Regulations and Requirements
      GEN 1.1          Designated authorities
      GEN 1.2          Entry, transit and departure of aircraft
        GEN 1.2.1      General
        GEN 1.2.2      Scheduled flights
        GEN 1.2.3      Non-scheduled flight
        GEN 1.2.4      Private flights
        GEN 1.2.5      Public health measures applied to aircraft
      GEN 1.3          Entry, transit and departure of passengers and crew
      GEN 1.4          Entry, transit and departure of cargo
      GEN 1.5          Aircraft instruments, equipment and flight documents
      GEN 1.6          Summary of national regulations and international agreements/conventions
      GEN 1.7          Differences from ICAO Standards, Recommended Practices and Procedures
   GEN 2               Tables and Codes
      GEN 2.1          Measuring system, aircraft markings, holidays
        GEN 2.1.1      Units of measurement
        GEN 2.1.2      Time system
        GEN 2.1.3      Geodetic reference datum
        GEN 2.1.4      Aircraft nationality and registration marks
        GEN 2.1.5      Public holidays
      GEN 2.2          Abbreviations used in AIS publications
      GEN 2.3          Chart symbols
      GEN 2.4          Location indicators
      GEN 2.5          List of Radio Navigation Aids
      GEN 2.6          Conversion tables
      GEN 2.7          Sunrise/Sunset tables
   GEN 3               Services
      GEN 3.1          Aeronautical information services
        GEN 3.1.1      Responsible service
        GEN 3.1.2      Area of responsibility
        GEN 3.1.3      Aeronautical publications
        GEN 3.1.4      AIRAC system
        GEN 3.1.5      Pre-flight information service at aerodromes/heliports
      GEN 3.2          Aeronautical charts
        GEN 3.2.1      Responsible service(s)
        GEN 3.2.2      Maintenance of charts
        GEN 3.2.3      Purchase arrangements
        GEN 3.2.4      Aeronautical chart series available
        GEN 3.2.5      List of aeronautical charts available
        GEN 3.2.6      Index to the World Aeronautical Chart (WAC) — ICAO 1:1 000 000
        GEN 3.2.7      Topographical charts
        GEN 3.2.8      Corrections to charts not contained in the AIP
      GEN 3.3          Air traffic services
Edition: 1.0                                        Released Issue                                      Page 25
AIM/AEP/0001                                                               Requirements for AIP Audit Assistant




Title               Description                                                                 Comments
        GEN 3.3.1   Responsible service
        GEN 3.3.2   Area of responsibility
        GEN 3.3.3   Types of services
        GEN 3.3.4   Co-ordination between the operator and ATS
        GEN 3.3.5   Minimum flight altitude
        GEN 3.3.6   ATS units address list
      GEN 3.4       Communication services
        GEN 3.4.1   Responsible service
        GEN 3.4.2   Area of responsibility
        GEN 3.4.3   Types of service
        GEN 3.4.4   Requirements and conditions
      GEN 3.5       Meteorological services
        GEN 3.5.1   Responsible service
        GEN 3.5.2   Area of responsibility
        GEN 3.5.3   Meteorological observations and reports
        GEN 3.5.4   Types of services
        GEN 3.5.5   Notification required from operators
        GEN 3.5.6   Aircraft reports
        GEN 3.5.7   VOLMET service
        GEN 3.5.8   SIGMET service
        GEN 3.5.9   Other automated meteorological services
      GEN 3.6       Search and rescue
        GEN 3.6.1   Responsible service(s)
        GEN 3.6.2   Area of responsibility
        GEN 3.6.3   Types of service
        GEN 3.6.4   SAR agreements
        GEN 3.6.5   Conditions of availability
        GEN 3.6.6   Procedures and signals used
  GEN 4             Charges for Aerodromes/Heliports and Air Navigation Services
      GEN 4.1       Aerodrome/heliport charges
      GEN 4.2       Air navigation services charges
Part 2              En-route (ENR)
  ENR 0
      ENR 0.1       Preface                                                                     If applicable
      ENR 0.2       Record of AIP Amendments                                                    If applicable
      ENR 0.3       Record of AIP Supplements                                                   If applicable
      ENR 0.4       Checklist of AIP pages                                                      If applicable
      ENR 0.5       List of hand amendments to the AIP                                          If applicable
      ENR 0.6       Table of Contents to Part 2
  ENR 1             General Rules and Procedures
      ENR 1.1       General rules
      ENR 1.2       Visual flight rules
      ENR 1.3       Instrument flight rules
      ENR 1.4       ATS airspace classification
      ENR 1.5       Holding, approach and departure procedures
        ENR 1.5.1   General
        ENR 1.5.2   Arriving flights
        ENR 1.5.3   Departing flights
      ENR 1.6       Radar services and procedures
        ENR 1.6.1   Primary radar
        ENR 1.6.2   Secondary surveillance radar (SSR)
      ENR 1.7       Altimeter setting procedures

Page 26                                       Released Issue                                         Edition: 1.0
Requirements for AIP Audit Assistant                                                                     AIM/AEP/0001




Title                  Description                                                                       Comments
      ENR 1.8          Regional supplementary procedures
      ENR 1.9          Air traffic flow management
      ENR 1.10         Flight planning (Restriction, limitation or advisory information)
      ENR 1.11         Addressing of flight plan messages
      ENR 1.12         Interception of civil aircraft
      ENR 1.13         Unlawful interference
      ENR 1.14         Air traffic incidents
  ENR 2                Air Traffic Services Airspace
      ENR 2.1          FIR, UIR, TMA
      ENR 2.2          Other regulated airspaces
  ENR 3                ATS Routes
      ENR 3.1          Lower ATS routes                                                                  List
      ENR 3.2          Upper ATS routes                                                                  List
      ENR 3.3          Area navigation (RNAV) routes                                                     List
      ENR 3.4          Helicopter routes                                                                 List
      ENR 3.5          Other routes
      ENR 3.6          En-route holding
  ENR 4                Radio Navigation Aids/Systems
      ENR 4.1          Radio navigation aids - en-route
      ENR 4.2          Special navigation systems
      ENR 4.3          Name-code designations for significant points
      ENR 4.4          Aeronautical ground lights - en-route
  ENR 5                Navigation Warnings
      ENR 5.1          Prohibited, restricted and danger areas
      ENR 5.2          Military exercise and training areas and air defence identification zone (ADIZ)
      ENR 5.3          Other activities of a dangerous nature
        ENR 5.3.1      Other activities of a dangerous nature
        ENR 5.3.2      Other potential hazards
      ENR 5.4          Air navigation obstacles - en-route
      ENR 5.5          Aerial sporting and recreational activities
      ENR 5.6          Bird migration and areas with sensitive fauna
  ENR 6                En-Route Charts
Part 3                 Aerodromes (AD)
  AD 0
      AD 0.1           Preface                                                                           If applicable
      AD 0.2           Record of AIP Amendments                                                          If applicable
      AD 0.3           Record of AIP Supplements                                                         If applicable
      AD 0.4           Checklist of AIP pages                                                            If applicable
      AD 0.5           List of hand amendments to the AIP                                                If applicable
      AD 0.6           Table of contents to Part 3
  AD 1                 Aerodromes/Heliports — Introduction
      AD 1.1           Aerodrome/heliport availability
      AD 1.2           Rescue and fire fighting services and snow plan
        AD 1.2.1       Rescue and fire fighting services
        AD 1.2.2       Snow plan
      AD 1.3           Index to aerodromes and heliports
      AD 1.4           Grouping of aerodromes/heliports
  AD 2                 Aerodromes                                                                        Section List
      AD 2.1           Aerodrome location indicator and name
      AD 2.2           Aerodrome geographical and administrative data
      AD 2.3           Operational hours
      AD 2.4           Handling services and facilities

Edition: 1.0                                           Released Issue                                            Page 27
AIM/AEP/0001                                                       Requirements for AIP Audit Assistant




Title          Description                                                              Comments
    AD 2.5     Passenger facilities
    AD 2.6     Rescue and fire fighting services
    AD 2.7     Seasonal availability — clearing
    AD 2.8     Aprons, taxiways and check locations/positions data
    AD 2.9     Surface movement guidance and control system and markings
    AD 2.10    Aerodrome obstacles
    AD 2.11    Meteorological information provided
    AD 2.12    Runway physical characteristics
    AD 2.13    Declared distances
    AD 2.14    Approach and runway lighting
    AD 2.15    Other lighting, secondary power supply
    AD 2.16    Helicopter landing area
    AD 2.17    Air traffic services airspace
    AD 2.18    Air traffic services communication facilities
    AD 2.19    Radio navigation and landing aids
    AD 2.20    Local traffic regulations
    AD 2.21    Noise abatement procedures
    AD 2.22    Flight procedures
    AD 2.23    Additional information
    AD 2.24    Charts related to an aerodrome
  AD 3         Heliports                                                                Section List
    AD 3.1     Heliport location indicator and name
    AD 3.2     Heliport geographical and administrative data
    AD 3.3     Operational hours
    AD 3.4     Handling services and facilities
    AD 3.5     Passenger facilities
    AD 3.6     Rescue and fire fighting services
    AD 3.7     Seasonal availability - clearing
    AD 3.8     Aprons, taxiways and check locations/positions data
    AD 3.9     Markings and markers
    AD 3.10    Heliport obstacles
    AD 3.11    Meteorological information provided
    AD 3.12    Heliport data
    AD 3.13    Declared distances
    AD 3.14    Approach and FATO lighting
    AD 3.15    Other lighting, secondary power supply
    AD 3.16    Air traffic services airspace
    AD 3.17    Air traffic services communication facilities
    AD 3.18    Radio navigation and landing aids
    AD 3.19    Local traffic regulations
    AD 3.20    Noise abatement procedures
    AD 3.21    Flight procedures
    AD 3.22    Additional information
    AD 3.23    Charts related to a heliport




Page 28                                 Released Issue                                      Edition: 1.0
Requirements for AIP Audit Assistant                                               AIM/AEP/0001




APPENDIX B              PROTOTYPE USER INTERFACES
           Prototypes for user interfaces that were mentioned in the use cases given in Section
           2.3 are included in this section. The prototype screens are given in the typical order
           the software is used.

A.1      Software Start-up and User Authentication

           When the AAA software is started the start-up screen shown in Figure 4.




                              Figure 4. AIP Audit Assistant start-up screen
           To start using the software, the user needs to be authenticated. The user can start a
           new session by pressing the Login button. When Login button is pressed, the
           existing user accounts are displayed as shown in Figure 5.




                             Figure 5. User account selection dialog for login



Edition: 1.0                                     Released Issue                           Page 29
AIM/AEP/0001                                                        Requirements for AIP Audit Assistant



           The user needs to select his/her username and to click on the Login button. When
           this is done, password entry dialog as shown in Figure 6 is displayed to get and to
           verify user password. The user needs to enter his/her password and click on OK.




                       Figure 6. Password entry dialog for user authentication

A.2       Initialising or Continuing an Audit

           After user authentication, the available options for the associated user role are
           displayed. The user can select to create a new audit or to open an existing audit
           from the Auditor->Audits menu item as shown in Figure 7




                     Figure 7. Creating a new audit or opening an existing audit
           When Open Audit menu item is selected, the user is presented with a list of existing
           audits belonging to him/her. The audit lookup dialog, shown in Figure 8, allows
           opening an existing audit, edit audit parameters, delete an audit or create a new
           audit. If no audits are available for the user, he/she is requested to create a new
           audit.




Page 30                                    Released Issue                                    Edition: 1.0
Requirements for AIP Audit Assistant                                                      AIM/AEP/0001




                    Figure 8. Audit lookup dialog showing the list of audits for a user
           The user can create a new audit via the Audit parameters form shown in Figure 9.
           This form can be accessed from either the menu bar or audit lookup dialog.




                                       Figure 9. Audit parameters form

A.3      Auditing with AAA

           When a new audit is created, the tool creates a separate Excel workbook containing
           the audit. Since state specific sections will be the same for all audits conducted at a
           site, this information is copied into the audit workbook. There is a local copy of all

Edition: 1.0                                      Released Issue                                Page 31
AIM/AEP/0001                                                        Requirements for AIP Audit Assistant



          audit information for each audit. State specific information is basically the AIP
          sections for Aerodromes (AD 2) and Heliports (AD 3).

          The user might modify state specific sections via the Auditor->Edit State Specific
          Information menu item, as shown in Figure 10.




                          Figure 10. Editing of state specific information
          When this menu item is selected, the state specific information form, shown in
          Figure 11, is displayed. The modification, creation and deletion of aerodrome and
          heliport sections can be done via this form. User can modify state specific
          information by selecting an item from the list and clicking Edit button or double
          clicking over an item. New items can be created by clicking on New button or be
          removed by selecting an item and clicking on Delete button. When a new item is
          created or an existing one in edited, the entry form shown in Figure 12 is displayed.




                             Figure 11. State specific information form




Page 32                                   Released Issue                                     Edition: 1.0
Requirements for AIP Audit Assistant                                                AIM/AEP/0001




                             Figure 12. State specific information entry form
           For a new audit, the user can select the AIP sections to be audited by the Auditor-
           >Select Sections menu item. This is shown in Figure 13.




                            Figure 13. Selecting the AIP sections for auditing
           When this menu item is selected, the AIP section selection dialog shown in Figure
           14 is displayed. A hierarchical tree view of the AIP document is shown in this dialog.
           The user can select/deselect a section by clicking the check box next to section
           name. The Update sub-sections automatically toggle is used to propagate changes
           made to a section to its sub-sections. State specific sections are also included in the
           tree view. It is possible to make complete audit by selecting all the AIP sections.




Edition: 1.0                                     Released Issue                           Page 33
AIM/AEP/0001                                                         Requirements for AIP Audit Assistant




                             Figure 14. AIP section selection for audit
          An audit can be initialised by selecting the Auditor->Checklist->Create menu item,
          as shown in Figure 15. When this menu item is selected, the tool creates the
          checklist questions by copying from the initial AIP audit template for selected
          sections. This menu item should not be selected for an ongoing audit, since it will
          create an audit from scratch.




                      Figure 15. Initialising an audit by creating the checklist
          After creating the checklist, the user can start auditing by selecting Auditor-
          >Checklist->Fill menu item, as shown in Figure 16.


Page 34                                    Released Issue                                     Edition: 1.0
Requirements for AIP Audit Assistant                                                     AIM/AEP/0001




                    Figure 16. Performing the audit by responding to checklist items
           When this menu item is selected, the audit checklist items dialog, as shown in
           Figure 17, is displayed. The user can view and fill in the audit checklist for a
           particular section by clicking the section name on the left pane. The tool prepares
           and displays checklist items for the selected section. The checklist items are given
           in three tabs: Mandatory, Good Practice and Exclusions. If the checklist items
           cannot fit in a single page, additional tabs are filled in. The user has to answer all
           the questions in all the tabs for that section. When user clicks on another section
           name, the tool automatically saves the answers and displays the checklist for the
           new section. Submit button saves the answers for the current section without
           moving to another section. Next button can be used to save the current one and
           move to the next section.




                    Figure 17. Audit checklist items dialog displayed for each section
           The user can create follow-up actions for the current section by clicking the New
           Action button. Actions are used to keep track of issues identified during the audit.
           When the New Action button is clicked, the follow-up action entry form, as shown in

Edition: 1.0                                     Released Issue                                Page 35
AIM/AEP/0001                                                        Requirements for AIP Audit Assistant



          Figure 18, is displayed. A description of the issue identified should be entered in
          Description field. A due date or responsible may optionally be specified.

          Similarly, the originator of the data or the person/group maintaining the data in the
          current section can be specified by clicking on the Set Originator button. When this
          button is clicked, the data originator entry form, as shown in Figure 19, is displayed.




                           List of radio navigation aids




                                Figure 18. Follow-up action entry form




Page 36                                         Released Issue                               Edition: 1.0
Requirements for AIP Audit Assistant                                             AIM/AEP/0001




                                   Figure 19. Data originator entry form
           Both Action and Data originator entry forms allows creation of new contact info via
           Add New Contact button. When the Add New Contact button is clicked, the contact
           information form shown in Figure 20 is displayed.




Edition: 1.0                                     Released Issue                        Page 37
AIM/AEP/0001                                                       Requirements for AIP Audit Assistant




                                 Figure 20. Contact information form

A.4       Post-Audit

           It is possible to create actions that are not related to a specific section. This can be
           done via the Auditor->Actions->New Action menu item, as shown in Figure 21.
           When this menu item is selected, the action entry form shown in Figure 18 is
           displayed. The actions created during the audit can be viewed by selecting the
           Auditor->Actions->Edit Actions menu item. When this menu item is selected, action
           lookup dialog, as shown in Figure 23. From this dialog, the user can create, modify
           or delete the follow-up actions.




Page 38                                    Released Issue                                   Edition: 1.0
Requirements for AIP Audit Assistant                                        AIM/AEP/0001




                                   Figure 21. Creating a generic action




                                   Figure 22. Viewing the list of actions




Edition: 1.0                                      Released Issue                  Page 39
AIM/AEP/0001                                                            Requirements for AIP Audit Assistant



                                      Figure 23. Action lookup dialog
           The contact information can be viewed by selecting the Auditor->Address Book
           menu item. When this menu item is selected, the address book lookup dialog shown
           in Figure 24 is displayed.




                                   Figure 24. Address book lookup dialog

A.5       Post-Audit Reports

           Four types of reports can be generated in the prototype:

               •   Audit Score,

               •   Action List,

               •   Contact List,

               •   Originator List.

           Each one can be generated by selecting the corresponding menu item from the
           Auditor->Reports menu, as shown in Figure 25. The report displays for these reports
           are shown in Figure 26, Figure 27, Figure 28 and Figure 29.




Page 40                                       Released Issue                                     Edition: 1.0
Requirements for AIP Audit Assistant                                         AIM/AEP/0001




                                       Figure 25. Report generation




                                Figure 26. Audit score card report display




Edition: 1.0                                     Released Issue                    Page 41
AIM/AEP/0001                                          Requirements for AIP Audit Assistant




               Figure 27. List of actions report display




               Figure 28. List of contacts report display




Page 42                     Released Issue                                     Edition: 1.0
Requirements for AIP Audit Assistant                                              AIM/AEP/0001




                              Figure 29. List of data originator report display

A.6      Other Features

           It is possible to switch user by selecting the Settings->Change User menu item.
           When this menu item is selected, the user account selection dialog shown in Figure
           5 is displayed.




                                   Figure 30. Switching user accounts
           Certain program settings can be modified by selecting Settings->Program Settings
           menu item as shown in Figure 31. When this menu item is selected, the program
           settings dialog, as shown in Figure 32 will be displayed.




                                  Figure 31. Changing program settings




Edition: 1.0                                      Released Issue                        Page 43
AIM/AEP/0001                                                         Requirements for AIP Audit Assistant




                                Figure 32. Program settings dialog
          It is possible to restore standard Excel menu bar by selecting the Settings->Restore
          Excel Menu menu item as shown in Figure 33.




                               Figure 33. Restoring Excel menu bar
          It is possible to display the keyboard shortcuts by selecting the Help-> Hot Keys
          Legend menu item as shown in Figure 34.




                              Figure 34. Viewing keyboard shortcuts
          The location of information provided in the AIP document can be viewed as a cross
          reference between information entities and the AIP section containing those entities.
          This cross reference can be viewed by selecting Help->Cross References menu
          item as shown in Figure 35. When this menu item is selected, the AIP information
          cross reference view, as shown in Figure 36, is displayed.




Page 44                                   Released Issue                                      Edition: 1.0
Requirements for AIP Audit Assistant                                           AIM/AEP/0001




                             Figure 35. Viewing information cross references




                             Figure 36. AIP information cross reference view
           Program help can be obtained by selecting the Help->AAA Help menu item as
           shown in Figure 37. Program usage help in Windows standard help format is
           displayed as shown in Figure 38.




                                Figure 37. Obtaining help on the program




Edition: 1.0                                    Released Issue                       Page 45
AIM/AEP/0001                                                     Requirements for AIP Audit Assistant




               Figure 38. Program usage help is available as standard Windows Help
          Information about program release information can be obtained by selecting Help-
          >About AAA menu item, as shown in Figure 39. The program release information is
          displayed in Figure 40.




                        Figure 39. Obtaining program release information




Page 46                                  Released Issue                                   Edition: 1.0
Requirements for AIP Audit Assistant                                              AIM/AEP/0001




                                 Figure 40. Program release information

A.7      Administrator Actions

           Main responsibilities of the audit administrator are basically to create users and
           enter an initial set of state specific sections. Furthermore, he/she can view all the
           information about the users and the audits. This user is necessary to avoid problems
           related to forgotten or lost passwords. A new user account can be created by
           selecting Administrator->New User menu item and existing user accounts can be
           edited by selecting Administrator->Edit Users menu item, respectively as shown in
           Figure 41 and Figure 43. For creating a new user account, the user account form
           shown in Figure 42 is displayed. For editing an existing user account, the user
           accounts edit form shown in Figure 44 is displayed.




                                 Figure 41. Creating a new user account




Edition: 1.0                                    Released Issue                           Page 47
AIM/AEP/0001                                                         Requirements for AIP Audit Assistant



                                  Figure 42. User account form




                             Figure 43. Editing existing user accounts




                                Figure 44. User accounts edit form
          State specific information, namely the aerodromes and heliports, can be defined by
          selecting the Administrator->Edit State Specific Information menu item as shown in
          Figure 45. Selecting this menu item brings the state specific definition form shown in
          Figure 46. It is possible to define AIP sections either for an aerodrome or for a
          heliport. Previously defined aerodromes and heliports can be traversed using the
          Previous and Next buttons. A new entry can be created by the New button and
          needs to be inserted using the Insert button after its type and name is entered. The
          current item can be deleted using the Delete button.




Page 48                                   Released Issue                                      Edition: 1.0
Requirements for AIP Audit Assistant                                               AIM/AEP/0001



                           Figure 45. Password dialog for user authentication




                           Figure 46. State specific information definition form
           The audits and related parameters can be viewed by selecting Administrator->Audit
           Lookup menu item as shown in Figure 47. The audit parameters form is displayed in
           Figure 48.




                          Figure 47. Viewing the audits and related parameters




Edition: 1.0                                     Released Issue                          Page 49
AIM/AEP/0001                                                        Requirements for AIP Audit Assistant




                                 Figure 48. Audit parameters form

A.8       Content Maintainer

           Although in the prototype there is a menu item for content maintainer (it corresponds
           to development/maintenance team). During the demo it was decided to remove this
           role. It will not be part of the final delivery.




                                                                                - End of Document -




Page 50                                   Released Issue                                     Edition: 1.0

								
To top