Requirements Document Grading - Software Methodology

This document is worth 50 points (out of 500 total on the project).

Section	Max Pts	Your Pts	Comments (What I'm looking for)
Introduction / Product Overview	6		This section is judged as a whole, since it's pretty subjective as to what goes where. Does it tell me: What's being built What the purpose of it is Why your implementation is needed What you expect from the product Where to go for more information (reference docs). Don't get carried away, but really think about this. This should fit on one or two pages and you should be able to give it to your boss to tell him why what you're doing is important.
Quality of Requirements	10		Understandable, unambiguous, non-redundant, consistent, correct, testable?
Comprehensiveness	10		The requirements support all the scenarios & usages -- including error conditions
Unresolved Issues	2		Unresolved issues identified
Glossary of Terms/Jargon	2		Definitions of acronyms used
Preliminary User Interface	10		Four or 5 hand drawn displays to support key requirements: initialization, help display, etc.
Presentation	5		Correct spelling Clear sentence construction Consistent format You will lose points if all the group members names aren't on the title page.
Time Logs and Meeting Notes	5		Titles and labels, so we know what everything is Times for all team members, even while doing individual work. Total time for all team members and milestone Items to be addressed (agenda) Decisions made Action items assigned, with due date and responsible person
Total:	50		General Comments: