Mr Rogers Computer Science AB Syllabus

The major software project will be submitted in four parts as shown below on or before the milestone dates listed in the table below. Each milestone will be at least the equivalent of a test grade. In addition the final project will be submitted on or before Feb 27, 2002. The final project will be submitted in a binder. It will be typewritten, have a title page, a table of contents, and have all the pages numbered. Handwritten comments can be added to the program listing and pages can be numbered by hand where it is inconvenient to do otherwise.

Minimum standards: 1000 lines of code, 5 classes or interfaces, a GUI with a pull down menu at the top, ability to throw run-time exceptions, and Inheritance--at least 2 classes. Must include at least 10 of the following:

Items		Required Pages	IB Criterion	Additional Requirements	Due	Points
1	Table of Contents	1
2	Analysis of Problem	2-3	A1, 4pts Weight: 8%	Must contain the following sub-headings with the specified information: A research question suitable for a science fair project (see the above link) that is specific and testable.. A hypothesis which details how the research question will be answered. While The research question can be a single complete sentence, the hypothesis should be several paragraphs long and meet all of the specifications in the above link. It should include a discussion of background research and to the extent possible, how the problem has been addressed in the past. It should describe the program's output. Required input, calculations, and mathematical models stated in general terms. Although you will be the primary user of the program, input/output should be described for a hypothetical end user who could potentially duplicate or extend your work. References used for background research--minimum of 5. Note that while the Wikipedia is a great place to start, it is not itself a valid reference. In addition each student should find a research mentor with in-depth expertise of the subject, other than the teacher who is at minimum available by e-mail.
3	Criterion for Success	1-2	A2, 4pts Weight: 8%	Must have at minimum an introduction clearly stating the objectives/goals of the solution to the problem and contain an outline, bullet list, or table with the minimum performance and usability criterion so that they are easily scanned. In simulations performance and usability criterion are often defined by simplifying assumptions. For example, in a projectile motion simulation if air resistance is assumed to be negligible, the simulations solutions will only be valid for low speeds.
4	Prototype Solution	Variable	A3, 4pts Weight: 8%	This section starts by describing an initial design for some of the main objectives that were determined to be the criteria for success. it should consist of the following: a brief verbal description. a block diagram of the program with at least one block describing user input, one describing the manipulation of the input, one describing file I/O, and a 4th describing the output. Bullet statements can be used for the descriptions within each box. The prototype is based on functional decomposition. It is a top-down design that includes NO, repeat NO java code. It must include: A brief written summary of the way the program will function that references items 2-4 below. Can be in outline form. Fully annotated computer-generated drawings of the user interface and output. There should be multiple drawings showing the expected output under various conditions. A list identifying all I/O. User feedback in support of the design.. (At least part of this feedback must come from the teacher.)
Milestone 1					11-25	100
5	Data Structures	2-5	B1, 4pts Weight: 8%	Must include: A brief written summary of data structure that references items 2-3 below. A Bluej block diagram. A Javadoc printout identifying all classes and fields. Diagram of file structure which at minimum contains a help file. Sketches/illustrations of the expected screen output. Javadoc comments must include: A purpose for each class. A definition for each field. Sample data for each field, where applicable including a brief discussion of the way data objects will be changed during program execution
6	Algorithms	2-5	B2, 4pts Weight: 8%	Must include: A brief written summary of algorithms that references item 2 below. This can include a list of algorithm. Standard algorithms like search and sort need very little description but more complex ones should be reasonably detailed A Javadoc printout with information on methods (it's ok to reference the above section). Javadoc comments must include: A purpose for each method. Preconditions and post conditions for each method.
7	Modular organization	3-5	B3, 4pts Weight: 8%	A written summary of class or modular structure that references item 2 below and the above sections in the design and relates how fields and methods are interconnected with various classes. A BlueJ box diagram.
Milestone 2					12-17	200
8	Usability	1	C1, 3pts Weight: 6%	See Criterion C1. Note: the pull down menu at the top of the program and help file are part of the usability.
9	Handling errors		C3, 3pts Weight: 6%	All input must be in string form with proper protection for out of boundary data. The exceptions are GUI items like sliders
10	Code Listing Listing	500-3,000 lines of code	C1, 3pts Weight: 6%	1000 lines of code, 3 classes, a GUI, and a help file that meet all mastery needs are the minimum requirements. The program should demonstrate the use of good programming techniques including: an identification header indicating the program name author, date, school computer used, IDE used, purpose. The program should possess good internal documentation, including: constant, type and variable declarations that should have explanatory comments identifiers with meaningful names objects that are clearly separated and have comments for their parameters suitable indentation that illustrates various programming constructs.	1
Milestone 3					1-31	100
11	Annotated hard copy of tested Output	Variable	C4,D1 7pts Weight: 15%	See C4 and D1.
12	Evaluation of solutions	1	D2, 4pts Weight: 8%	See D2.
13	User Documentation	6	D3, 3pts Weight: 6%	See D3.
14	Documentation of mastery aspects	2		Note that failure to meet mastery requirements will drop scores more dramatically than any other aspect of the project.
			E, 3pts Weight: 6%
	Total	60-100	48	The Holistic approach criterion evaluates commitment, initiative and independence.
Final Project (Note: 1/2 of these points will be in 4th Quarter grade) Any item with out a due date listed will be due in the final project write up.					Tues. 2-25	200
Total Point Value ( the equivalent of six tests) These points will be distributed throughout the entire year. It will be nearly impossible to pass without turning in a project.						600