Project scores: Undeclared 25 FOO 25 Agilis 27 GetFit 27 Final Report 10 points each for items I, II, III, IV, V. Total out of 50 points. I. Details of design change. II. Team change details III. Problems faced and solved IV. Additional relevant details V. Report overall Undeclared 50 Fairly good report covering most of the expected details. Foo 48 Initial part of report has much duplication of information from development report into this report. Rest of the report has relevant information. Agilis 50 Well return report, addressing all issues. GetFit 48 Lot of information on certain items, lacks information on certain other items. Demo 10 points each for items I, II, III, IV. Total out of 40 points. I. Organization of the presentation II. Feature completeness, working of the program III. Q & A IV. Process, tools, techniques used and their effectiveness Undeclared 30 I. Organization of the presentation 9 Well done though too many context switches II. Feature completeness, working of the program 10 Fairly complete. III. Q & A 9 Answers were prompt, though some of the reasoning not convincing. IV. Process, tools, techniques used and their effectiveness 2 Inadequate largely in this area. Foo 30 I. Organization of the presentation 9 Fairly good presentation II. Feature completeness, working of the program 9 Fairly complete, though lacked some good features. III. Q & A 10 Answers were prompt, though some of the reasoning not convincing. IV. Process, tools, techniques used and their effectiveness 2 Given the size of the team, largely disappointed at not using even a source control system. Agilis 37 I. Organization of the presentation 9 Fairly good presentation II. Feature completeness, working of the program 9 Fairly complete though a little bumpy III. Q & A 10 Answers were prompt. IV. Process, tools, techniques used and their effectiveness 9 Very good job on this: Source control system, bug and issue tracking, some unit testing. GetFit 35 I. Organization of the presentation 9 Fairly good presentation II. Feature completeness, working of the program 9 Fairly complete III. Q & A 10 Answers were prompt. IV. Process, tools, techniques used and their effectiveness 7 Good job on this: Source control system, tough lacks other areas like bug and issue tracking, unit testing. Development Report 10 points each for items I, II, III, IV, V. Total out of 50 points. I. Description of Architecture and Design (with UML) II. Development activity/process III. Problems faced and solved IV. Tools and effectiveness V. Report overall Agilis I. Description of Architecture and Design (with UML) [5] Architecture section says that you have architecture. Second diagram does not add much information either. Third diagram is too details for an architecture diagram. Poor presentation or ordering of information. II. Development activity/process [5] Significant discussion on this missing. III. Problems faced and solved [5] Significant information on this missing. Some sketchy details presented. IV. Tools and effectiveness Good details. V. Report overall Missing details. Too detailed in some areas and totally lacking in others. Total: 35 Undeclared Variables I. Description of Architecture and Design (with UML) [5] No discussions on architecture in terms of any layering, how things are organized, etc. However, good to see discussion on language choice. II. Development activity/process [5] Missing significant information III. Problems faced and solved Enough details. IV. Tools and effectiveness [5] Missing significant details. V. Report overall Missing significant details. Total: 35 GetFit I. Description of Architecture and Design (with UML) [6] Lacking some details on design and diagraming. II. Development activity/process I liked your reason not to estimate hours... wish that can be used to convince the real bosses in the industry :) III. Problems faced and solved [9] Good details. IV. Tools and effectiveness Good discussions. Glad to see the use of CVS. Nice job. Too back you lost the web server and code with it though. Should have started on CVS sooner! V. Report overall Very well written. Total: 45 Foo I. Description of Architecture and Design (with UML) Architecture diagram is sufficient. Discussions on tiers is good, though I did not expect to see, in this document, as much UI as was presented. The middle tier discussions and diagraming is good. (I like Footilities, though the UML says Utilities!) II. Development activity/process [5] Not much information on this presented outside of issues section. III. Problems faced and solved Good discussions, well organized. IV. Tools and effectiveness [5] Not much information on this presented outside of issues section. V. Report overall Good report, but lacks significant required details. Total: 40 Inital Report 10 points each for items I, II, III. Total out of 30 points. I. Description of functionality II. Discussions/presentation of interfaces III. Report overall Agilis 28 I. Description of functionality 10 Very detailed description. Good job on this. II. Discussions/presentation of interfaces 10 Well supported user interface description. Great job. You even included prototype. Very pleased. III. Report overall 8 Very good description of functionality. Expected to see a diagram of the system. Undeclared Variables 26 I. Description of functionality 10 Good details on what is expected. II. Discussions/presentation of interfaces 8 Lack snap shot of what the user will see. III. Report overall 8 Good details on functionality. No pictures! GetFit 26 I. Description of functionality 10 Fairly enough details given. II. Discussions/presentation of interfaces 8 Lacks diagrams that illustrate the system. Lacks user interface diagrams as well. III. Report overall 8 Well written. Good introduction to the system functionality. Lacks details in the area of diagrams. Foo 25 I. Description of functionality 9 Too terse, written in a way it ignores the user. Improved in the resubmission II. Discussions/presentation of interfaces 10 A snap shot of screen to show the interface along with your description would have been very useful. Improved. III. Report overall 6 Abrupt start. - Still No diagrams. - Still not relevant diagrams No user interface shots.- Improved A high level architecture diagram would be very useful to show different components and their interaction.