(If you have any question about your grade for an assignment,
please see or email the person in charge: Annie--Assignment 1,
Brian--Assignments 2,4,6,8,10, and Ting--Assignments 3,5,7,9.)

Each assignment is graded according to 10 points.
The points are converted to A-F (4-0) as follows:
A   4	 10
A-  3.7   9
B+  3.3   8
B   3     7
B-  2.7   6
C+  2.3   5
C   2     4
C-  1.7   3
D+  1.3   2
D   1	  1
F   0     0

Assignment 10:
1 starting url and downloading
1 installation and required hardware software environment
4 explain 8+ functionalities / use cases
  .5 for each
  partial credit if not complete or clear.
2 supporting screen dumps
1 overall completeness and clarity
1 "what i did"
+1 good support for trouble shooting, on line help, etc.

Assignment 9:
4 test plan: describe way to show customers that the sw works correctly 
	.5 summary of specified functions and characteristics in requirements
	.5 summary of system decomposition
	 1 summary of approach
	 1 tests: need about 8-10 minimum
	 1 schedule: which, when, who.
2.5 test descriptions for each test, multiply by 8-10
	 1 data
	 1 procedure
	.5 expected result
2 test analysis report:
	1 actual results
	1 follow up if deviations were found.
.5 cvs
1 "what i did"

Assignment 8:
2 illustration of reuse
	1 documentation of reused code
	1 characterization
1 characterization of generated code
1 characterization of reverse engineered code
1 characterization of manually written code
1 summary of lines of code and in terms of subsystems
1 interesting code
1 incremental and iterative development
1 cvs use
1 "what i did"
+1 incremental and iterative computation principle in optimization
+1 mostly complete working code (or 2K+ lines of code---not copied)

Assignment 7:
1 introduction, package
1 revised class diagram
1 spec for the revision
2 spec for the design pattern used(why, where, how)
4 interface spec
	1 missing attr, operation
	1 signatures, types, visibility
	2 OCL
	  1 complexity (between two or more classes)
	  1 completeness (inv, pre, and post if applicable)
1 "what i did"

Assignment 6:
1 pt for Introduction and software arch
1 pt current architecture
2 pt for subsystem decomposition
	1 pt for individual subsystems
	1 pt for architectural style
1 pt for hardware/software mapping
1 pt for persistent data management
1 pt for access control and security
1 pt global software control
1 pt boundary conditions
1 "what I did"

Assignment 5:
3 class diagram
    1 completeness
    (all main classes, in each class, main operations and variables)
    1 relationship
    1 specification (unless the diagram is self-explanary)
3 sequence diagram
    1 completeness
    (each use case should have a corresponding sequence diagram)
    1 correctness
    (control obj, entity obj, boundary obj are correctly sequenced)
    1 specification (unless the diagram is self-explanary)
1 statchar diagram
1 activity diagram
1 cvs
1 "what I did"

Assignment 4:
1 pt for Introduction
1 pt for current system
1 pt for Objectives/Functional/Non-functional requirements
4 pts for Scenarios/Use Case Model
	1 pt scenarios
	2 pt uml diagrams
	1 pt for use case texts
2 pts for User Interface
1 "what I did"

Assignment 3:
1 activities (phases)
2 functionalities (features)
    1 granularity
    1 completeness
1 task dependencies
1 role assignment
2 schedule
    1 based on task dependencies
    1 completeness
2 detailes (platform, language, some pending problems, etc)
1 "what I did"

Assignment 2:
3 pts for References (0 for no ref, 1 for incomplete ref)
2 pts for problem statement
1 pt for objectives
2 pt for functional/nonfunctional requirements
	1 pt functional
	1 pt nonfunctional
1pt for target environment
1 "what I did"

Assignment 1:
1 questionnaire
7 content
	2 why
	3 what
	1 clarity
	1 references
	(too short: deduct upto 3)
1 link
1 "what I did"
(late, allowed only in assignment 1: deduct upto 3)
(no hard copy, allowed only in assignment 1: deduct 1)