CIFER®-MATLAB Interfaces: Development and ... - Cal Poly
CIFER®-MATLAB Interfaces: Development and ... - Cal Poly
CIFER®-MATLAB Interfaces: Development and ... - Cal Poly
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
3.2.1 <strong>Development</strong> Process<br />
The most difficult aspect of developing the GUI was adjusting the look <strong>and</strong> feel to appeal to the<br />
widest audience of potential users. The iterative method used for the comm<strong>and</strong>-line development<br />
was employed for the GUI as well, with NASA engineers <strong>and</strong> programmers included during the<br />
design process. Several initial concepts were sketched on paper before any code was written.<br />
When ideas were put into code, the first programs were designed only around the layout of the<br />
GUI, lacking any real functionality. This allowed reviewers a clear idea of what the finished<br />
product might look like. Once the design for the layout was sufficiently refined, the functionality<br />
was written into the code. As the functionality was based on the comm<strong>and</strong>-line interface, the<br />
focus of the GUI development was the layout.<br />
The GUI was largely built up around the comm<strong>and</strong>-line code that already could interface with<br />
CIFER ® . Data entry in the GUI was largely h<strong>and</strong>led by toggles <strong>and</strong> text fields. The error checking<br />
from the comm<strong>and</strong> line was superseded by similar checks within the GUI to make its use closely<br />
resemble the old CIFER ® interface. Appendix A shows the COMPOSITE screens from both the<br />
old interface <strong>and</strong> the new GUI.<br />
3.2.2 Modern Updates to the Original Interface<br />
Perhaps the most visible change between the original interface <strong>and</strong> the new <strong>MATLAB</strong> GUI was<br />
the added navigational features. CIFER ® was originally designed to run on VAX/VMS systems<br />
<strong>and</strong> as a result, uses the keyboard function keys for navigation. There were menus that could be<br />
accessed for navigation within each program; however they are not always intuitive in use. Thus<br />
two primary navigation bars were added to the GUI interface. The left bar, found in Appendix A,<br />
29