Fig. 1. COMS system flowchart four programs. Each program begins with an oblong user block. This means program initiation and frequency, as well as data input will be user controlled.
The program block indicates the program's objective. Program 1 projects a realistic cookie order. Program 2, used only once, initializes the GCF (Girls' Cookie File) and the CRF (Cookie Reorder File). Constant items such as girls' names, cookie names and troop numbers entered here create the files needed in Programs 3 and 4. There is no visible output to Program 2.
The second program prepares the system files for future use. Arrows pointing from the program to the file denote file updates. Arrows pointing to the programs from the file denote program retrieval of file data.
Program 3 has two purposes: to report generation which requires retrieval of file data, and to update files. Program 3's output is any combination of GCF update, CRF update or GCF, CRF and financial data reports. Program 3 Is the heart of our COMS system. Programs 1 and 2 are run only once and program 4 will be run at the end of the cookie drive to determine which scouts will receive special awards and to create a compos-
The Key Box
Basic Level II Model I 32K RAM NEW DOS 1 Disk Drive
Function: Initial order suggested quantity and cost. Trigger: COMS program initiation.
Input: User-supplied via keyboard.
Data Elements: 1. Number of girl scouts participating last year/this year.
2. Number of boxes sold last year by cookie type.
3. Cookie price last year/this year.
4. Percentage or total sales to be ordered initially.
Output: Printed report(s):
1. Summary of last year's sales.
2. Average of last year's sales.
3. Initial order forecast.
1. Totals: Boxes/cases/value sold last year.
2. Average per child last year.
3. Total cases (broken down by cookie type) and total cost for initial order.
Frequency: Processed one time. Processing:
1. Prompt user for information: Each cookie type, amount sold, boxes per case, cost per box.
2. Display information including total boxes, total cases and total value.
3. Prompt user for total children selling cookies and display averages per child.
4. Prompt user for total children this year, percent or initial order and price per case.
5. Display recommended order quantities.
Fig. 2. Functional Statement
ite CHF (Cookie History File) for future drives. The only program to run with any frequency is Program 3. A good systems analyst would choose his best programmer to write Program 3.
Next, a broad functional statement is prepared for each program in the system. Figure 2 shows a functional statement for Program 1. It defines the system, the program's functions and the trigger.
Was this article helpful?