C202 - Introduction to Software Systems

gmanwani@ius.edu

(812) 941- 2678

Procedure for turning in the Lab Assignments:

Following items, in that orders are required while turning-in your lab assignments:

1 - Complete Specification of the given problem. Usually the problem description given to you will be the first part of this step. You must try to elaborate and consider all the cases that can exist surrounding the problem. Specific details of each one of these cases must be studied and cited.

2 - Complete design consistent with your analysis. This part involves in writing an algorithm or flowchart (stepwise description) that solves the problem, and design of the abstract data type used in the solution. You must avoid using the C++ language constructs and reserved words in this part; but instead uses Unified Modeling Language (UML). It means that your algorithm should be language independent.

3 - Source code listing (hard copy). It must be consistent with your algorithm. It must have three distinct sections: namely input, processing and output. In some complex or long listings these sections might need to be divided in sub-sections. You must use appropriate variables names and types. Must explain how the C++ language constructs are solving that particular step in your algorithm. In other words, you must have sufficient comments in your program to make it understandable.

4 - Source code (soft copy). Name the program as your first name followed by the assignment #. For example, if Robin were turning in assignment #2, then she would name her program as Robin_driver_2.cpp, Robin_impl_2.cpp and Robin_head_2.h. She would save these files in a folder named Robin-2. You might be asked to turn-in this folder on the LAN or on a diskette.

Once you have the folder named as your first name, copy all the files to this folder. You might be asked to move this folder to the IUS-LAN. I will explain in class how to move. Make sure that the program runs before you move. Please, do not copy the executable version of your lab project to this folder.

5 - As part of the documentation, you must also design a test plan and test your program as planed. Write down the outcome of the testing, record different runs, evaluating the performance of your lab project.

6 - The final sample output of the lab project.