INTRODUCTION TO THE JASA SUPPLEMENT
EFFECTIVE SECTIONS
SUPPLEMENT TO SECTION 1.0 INTRODUCTION
1.3.3 OPERATIONAL ENVIRONMENT
1.5 COMPLIANCE
1.5.1 Compliant Systems
1.5.2 Noncompliant Systems
1.5.3 Migration
SUPPLEMENT TO SECTION 2.0 INPUT DEVICES
2.2 KEYBOARD INPUT
2.2.2 Variable Function Keys
SUPPLEMENT TO SECTION 7.0 SYSTEM and APPLICATION DESIGN
7.1 CDE IMPLEMENTATION
7.1.1 The Desktop in DII Systems
7.1.1.2 DII Configuration
7.1.2 Session Management
7.1.2.1 Starting and Ending a Session
SUPPLEMENT TO SECTION 9.0 IMPLEMENTATION PRESENTATION
9.1 TEXT INFORMATION
9.1.4 Formats for Date/Time and Geolocation Display
9.1.4.1 Date/Time Formats
9.1.4.2 Geolocation Formats
9.1.4.2.1 Latitude and Longitude
9.1.4.2.2 MGRS
9.1.4.2.3 UTM
9.1.4.2.4 GEOREF
9.4 INFORMATION CODING
9.4.5 Sound
SUPPLEMENT TO SECTION 10.0 WINDOW DESIGN
10.4 MAP WINDOWS
10.4.1 Map Information
This supplement to version 2.0 of the User Interface Specifications for the Defense Information Infrastructure (DII) defines the specific user interface "look and feel" of command, control, communications, computer, and intelligence (C4I) systems implemented by the Joint Airborne SIGINT Architecture (JASA) supplement. The DII style guide supersedes the User Interface Specifications for the Global Command and Control System (GCCS).
The DII will become the single C4I system to support the joint warfighter, as envisioned under the C4I for the Warrior concept. To achieve this goal, the DII specifies a software environment and common software structure based on open system standards and provides detailed specifications for the "look and feel" to be delivered by all DII-compliant software. The JASA supplement is the SIGINT component of the DII.
The DII style guide is based on the Department of Defense (DoD) Human Computer Interface (HCI) Style Guide (TAFIM Volume 8) and other user interface documents published by DoD services and organizations. The style specifications defined by DII are intended to provide sufficient flexibility so that the user environment provided by a DII-compliant system can be adapted to the specific operational setting in which it will be used. As such, the DII specifications define the general "look and feel" of C4I systems fielded by DoD organizations and can be considered to provide domain-level style guidance as defined in the DoD style guide. The specifications contained in Version 2.0 of the DII style guide as extended by this supplement define the specific "look and feel" to be provided by all JASA compliant systems.
This supplement provides JASA-specific direction in the following areas: JASA hardware and software configuration and operational environment. The JASA supplement supersedes the DII in the following areas: section 1.5 compliance, section 2.2.2 variable function keys, section 7.1.1.2 classification bar, section 7.1.2.1 system login, section 9.1.4 formats for date/time and geolocation display, section 9.4.5 sound, and section 10.4 map windows.
JASA developers should comply with the following sections of Version 2.0 of the DII style guide, as modified or extended by the contents of this supplement:
| DII Style Guide | Section 1.0 - 1.2 |
| JASA Supplement | Section 1.3 |
| DII Style Guide | Section 1.4 |
| JASA Supplement | Section 1.5 |
| DII Style Guide | Section 1.6 - 1.8 |
| DII Style Guide | Section 2.0 - 2.1 |
| JASA Supplement | Section 2.2 |
| DII Style Guide | Section 2.3 |
| DII Style Guide | Section 3.0 - 3.6 |
| DII Style Guide | Section 4.0 - 4.2 |
| DII Style Guide | Section 5.0 - 5.5 |
| DII Style Guide | Section 6.0 - 6.11 |
| JASA Supplement | Section 7.1 |
| DII Style Guide | Section 7.2 |
| DII Style Guide | Section 8.0 - 8.3 |
| JASA Supplement | Section 9.1 |
| DII Style Guide | Section 9.2 - 9.3 |
| JASA Supplement | Section 9.4 |
| DII Style Guide | Section 9.5 |
| DII Style Guide | Section 10.0 - 10.3 |
| JASA Supplement | Section 10.4 |
| DII Style Guide | Section 10.5 |
| DII Style Guide | Section 11.0 - 11.4 |
| DII Style Guide | Section 12.0 - 12.4 |
| DII Style Guide | Section 13.0 - 13.3 |
| DII Style Guide | Section 14.0 - 14.5 |
| DII Style Guide | Appendix A |
| DII Style Guide | Appendix B |
| DII Style Guide | Appendix C |
| DII Style Guide | Appendix D |
| DII Style Guide | Appendix E |
| JASA Supplement | Appendix F |
| DII Style Guide | Appendix G |
| DII Style Guide | Appendix H |
| DII Style Guide | Appendix I |
| DII Style Guide | Appendix J |
It is expected that JASA systems will be installed in a range of environments including surface, subsurface and airborne. These work areas include office-like spaces with normal ambient lighting, various platform spaces with low-level lighting where users remain dark adapted, and field units with unique environments. SIGINT variants should provide sufficient flexibility in customizing user interface features (e.g., selection of display color set and illumination) so that the system is usable in the specific environment it which it is installed.
Developers of zero baseline systems should be fully compliant with the specifications in Version 2.0 of the DII style guide and the JASA Supplement to the DII style guide.
Developers of noncompliant systems should use the specifications in Version 2.0 of the DII style guide and the JASA Supplement to the DII style guide as a guide and shall document and provide rationale for deviations from these specifications.
Given the tradeoff requirements, cost schedule and percent of legacy code invested, an evolutionary path may be desirable.
This style guide assumes that most applications will use fixed function keys (i.e., each key has only one predefined function associated with it) to execute the operations shown in table 2-2 and to define mnemonics and keyboard accelerators as indicated in sections 5.5 and 5.6 and shown in table 5-1. However, developers should provide user-defined variable function keys. If variable function keys are used, the command names for the function keys should be available for display in a separate application window in the form of soft keys, as shown in Figure 2-2. Soft keys are objects on the display screen that represent the function keys on the keyboard. As the function of a key changes, the soft key labeling also changes.
Figure 2-2. Example of Soft Function Keys
Since users are likely to be working in multiple applications simultaneously, if variable function keys are used, they should be application independent. Variable function keys should define input focus e.g., a database query command should open and focus on a new or existing application window.
The use of a classification bar on JASA compliant systems should be optional based on individual system accreditation requirements.
Developers of JASA compliant systems shall implement a login procedure that meets the accreditation requirements of the individual system. A system may make available at login only those applications to which the user is allowed access, or may require users to log in to individual applications or groups of applications. If the system is unavailable for login, a message should be displayed, whenever possible, indicating the system status and when the system will become available.
The date should be displayed as YYMMDD, where YY is the last two digits of the year, MM is the month, and DD is the day, or as DD MMM YY, where DD is the day, MMM is the month, and YY is the last two digits of the year.
Time should be displayed as HHMM[SS]Z, where HH is the hour of a 24-hour day, MM is the minute, SS (optional) is the second, and Z is the time zone (Zulu [Z] time is the default).
Date/Time Group (DTG) should be displayed as DDHHMMZ MMM YY, where DD is the day, HH is the hour, MM is the minute, Z is the time zone (Zulu is the default), MMM is the month, and YY is the year.
A JASA compliant system should have the capability to display and convert geolocation formats in latitude and longitude, Military Grid Reference System (MGRS), Universal Transverse Mercator (UTM), and the World Geographic Reference System (GEOREF). Note: The geolocation formats are presented in this document as a guide. Geolocation accuracy should be consistent with the systems capabilities.
Latitude should be displayed as D{D}H, where D (one or two characters) is the degrees of latitude and H is the hemisphere (N for North, S for South) or DD{MM{SS}}H, where DD is the degrees of latitude, MM is the minutes of latitude (optional), SS is the seconds of latitude (optional, but can only be given if minutes of latitude is given), and H is the hemisphere (N for North, S for South).
Longitude should be displayed as D{D{D}}H, where D (one, two, or three characters) is the degrees of longitude and H is the hemisphere (E for East, W for West).or DDD{MM{SS}}H, where DDD is the degrees of longitude, MM is the minutes of longitude (optional), SS is the seconds of longitude (optional, but can only be given if minutes of longitude is given), and H is the hemisphere (E for East, W for West).
MGRS formats should be displayed in accordance with system requirements and should include the reference datum.
UTM formats should be displayed in accordance with system requirements and should include the reference datum.
GEOREF formats should be displayed in accordance with system requirements and should include the reference datum.
Since SIGINT users are likely to be processing multiple auditory inputs simultaneously, auditory feedback should be used judiciously to attract the user's attention.
A map window should include the reference datum and other identifying
information about the map (e.g., map name, scale, coordinates, area, scale).
To the top