The successful student will be able to:
A. Create and use screen templates to design screen output,
B. Use cout, cin, basic add and subtract operations, and the use of comments to implement user interface screens,
C. Include appropriate "header files" to implement library functions.
Basic input/output knowledge and basic arithmetic operations.
The design of software systems is often centered around the screen sequencing or presentation sequence of the software package. Most programming efforts are implemented by programming teams which need some common "rules", standards, or style by which to work. These standards attempt to ensure that the work by the various teams is compatible.
One of the standards often used in the development of the screen sequence is the screen or printer spacing chart. The standardization of screens typically results in a more user-friendly sequence and a more professional appearing product. Each screen is plotted on a separate screen spacing chart and labeled.
Figure 1 presents an example of a hypothetical "project template".
Lines 1 - 5
< Project and Screen Titles >
Lines 7 - 19
< Body of the Screen >
Lines 23 - 25
< User Prompt / Message Area >
Figure 1. An example of a "project template" for screens.
Figure 2, which is hyperlinked is a screen design chart that can be used to create the specific designs for each of the screens in the project.
Assume you are to develop three screens for the Miramar College Bookstore Order System -- a system title screen; a data input screen consisting of ISBN, Book Title, Author, Publisher, Expected enrollment, Price, Required/Not Required, New/Used; and a screen to present the results of a specified calculation sequence. Figure 3 presents a possible design for a system title screen. Note that the title screen is a bit of an exception in that the body of the screen is the title of the project. Figure 4 presents a possible design for a user input screen. Once again this is only a model, creativity is highly recommended. Figure 5 is a screen that might be used as an output model for the "calculation output screen".
Figure 3. An example of a system title screen.
Figure 4. A sample user input screen.
Figure 5. An example of a data output screen.
Other requirements and comments of the system are --
The screen sequence should be designed for a monochrome machine,
The design selected here will be the basis for the screens that will be designed for the remainder of the project, however the basic design may be modified as the understanding of the projects becomes better.
Each screen should be consistent with all other screens.
Specific Screen Requirements:
Title Screen - should include the project title, programmer, latest revision date, and user prompt to continue.
Data Input Screen - should display prompt lines alternating with user input. This screen should display user instructions to press after each entry. All data should be entered as character strings. The price and enrollment should be entered into strings which will later be converted to appropriate values using the atoi() and atof() conversion functions.
Calculation Output Screen - should display the following: ISBN, Title, Author, Price, Enrollment, New/Used, Required/Not Required, and the calculation for number of books to be ordered. The string enrollment should be converted into an integer using the atoi() function; the price should be converted into a double using the atof() function immediately preceding the use in calculations. For an example, refer to the following program segment --
#include < cstdlib > // included for the atoi()
#include < string > // included for the string class
int d;// integer variable
string day;// string variable
cout<<"Enter a date: "; // prompt
cin>>day;// data entry
d=atoi(day.data());// IMPORTANT use of atoi()
// Note that day.data() creates a character array which is used by atoi() (or atof() )
// The rest of the pgm.
Be sure to include the "cstdlib" header file for the definitions of atoi() and atof().
Data to be used for this Project
Req'd 0.45 0.376
Not_Req 0.15 0.043
III. Screen Coding
Create the code for each of the screens within the same program. The coding sequence should be commented to include the program, purpose, author, date of last revision and each operational sequence should be liberally commented as to the actions being accomplished. Keep the coding for each of the screens separate and comment the beginning and ending of each screen. Each of the separate segments will be used as the basis for the development of â€œuser-definedâ€ functions in the next project.
After each screen is displayed, use the key to print a copy of the screen.
V. Evaluation Package
The following is a checklist for the evaluation package for Project 2 -
___A. Project 2 Performance Evaluation Sheet,
___B. A "Generalized Screen or Project Template",
___C. A specific design for each screen; title, input, and output using a separate printer/screen spacing chart for each,
___D. Program Listing,
___E. Prepare 5 complete sets of data used to test your program. Complete the anticipated calculations, on paper.Attachments