Honeywell Displays Testing

1. Honeywell Displays Testing Mike Santa Cruz Brad Simons Ryan Hernandez Matt Lombardo Jeremy Pager

2. The Hardware • One or more display units (DU) are connected to the Advanced Graphics Module (AGM) through the Modular Avionics Unit (MAU). • The display is analogous to a monitor, the AGM to a computer, and the MAU to a computer casing with multiple slots. • The AGM uses OpenGL libraries to draw primitives to the display.

4. The Problem, Reviewed • The AGM-200 is currently in development, and uses a different graphics processor than the AGM-100. • The OpenGL libraries need to be tested to ensure they still work correctly.

5. The Problem (con’t) • The AGM already has the ability to compute Cyclical Redundancy Checksums (CRC) to detect differences between two display areas. • To test the libraries, primitives must be drawn and the CRC calculated. • The AGM needs to be controlled from a remote machine, as it does not have its own monitor.

6. Honeywell

7. Documentation • Honeywell requires extensive documentation on the requirements of the program • SRS • Before any code is written it must be described in detail • SRDD • Descriptions of all tests must be in writing • Test Plan

8. SRS • System Requirements Specification • System Overview • General System Requirements • System Safety Requirements • Quality Requirements • Functional Allocation Requirements • System Interface Requirements • Power-Up/Restart Processing Requirements • Built-In-Test Requirements

9. Example SRS Requirement The program shall sum ten consecutive numbers and output the result [SRS NUMBER OUTPUT]

10. SRDD • System Requirements and Design Document • Describes all functions to be written • Describes data formats to be used • Also includes instructions on how to install

11. Example SRDD 3.5.1 printNumbers 3.5.1.1 API void printNumbers(int a) 3.5.1.2 Requirements The program shall add the numbers starting at the parameter a, to a+9, then it shall print the result of the addition of those numbers. [SRDD PRINT NUMBERS METHOD /; SRS NUMBER OUTPUT]

12. Code Example // [SRDD PRINT NUMBERS METHOD /; SRS NUMBER OUTPUT] void printNumbers(int a){ int b = 0; for(int i = a;i<a+10;i++){ b+= i; } cout << b; }

13. Our SRS and SRDD

14. The Server • The AGM has its own operating system, called DEOS. • DEOS does not have a virtual machine, so native code (i.e. C/C++) must be used. • A small server application will be running on the AGM to accept and process requests from a TCP connection.

15. The Server (con’t) • DEOS does not have a registry. • Information about each process must be manually declared and uploaded to the AGM. • Threads • Mutexes • Time Slices • Slack

16. The Server (con’t) • The server waits for an incoming TCP request. • The server parses the request, which is either to draw an OpenGL primitive or get a CRC. • The OpenGL library or CRC is invoked, and the result is returned to the client through the TCP socket.

17. HGL • Based on OpenGL 1.4. • Stripped down functionality, no need to render cutting-edge 3D graphics. • All drawing in our application done in immediate mode, i.e. glBegin()/glEnd().

18. HGL (con’t)

19. HGL (con’t) • Primitive types

20. Server Progress • Gave a demo to Malachi before spring break • UDP Connection between client/server • Able to receive incoming data from the client • Drawing HGL Primitives • Red box drawn on screen upon starting client

21. Server Side: To Do • TCP Connection • CRC • Outgoing data transmission • Write code to parse and execute commands from the client

22. The Client • The client (written in Java) will create a request and send it to the server. • The client waits for a response from the server. • In order to support modularity and extensibility, the “client” is only a layer that is invoked by a separate Java program.

23. Client Progress • Client is 97.3% done • Able to detect success/error • Display added to applet

26. Questions?