Requirements Document Comments

Team: Instant Finance

Grade: (103 out of 100)

The following is a breakdown of the grading.

Document presentation (5 out of 5)

Important points:

Organization: OK
Document author: OK
use of English: OK

Comments:

Project Description of Target System (10 out of 10)

Comments:

Scenario descriptions (10 out of 10)

3 scenarios provided: yes
level of description: yes
clarity: good

Comments:

Storyboarding (15 out of 10)

Evidence of storyboarding: yes, and it is outstanding work. Is it really going to look like this?
Connection with scenarios: good

Comments: Seriously, I am IMPRESSED!

Functional Requirements (25 out of 25)

Number of requirements: 5 categories, further subdivided
Clarity of description: OK
Decomposition: OK
Prioritization: OK

Comments:

Non-Functional Requirements (15 out of 15)

Variety: very good
Measurability: well done

Comments:

Platform and Network Environment (8 out of 10)

Vehicle platform: this is what it will ultimately run on, the JVM/
Development platform: this is what I think you are referring to as the vehicle in your report. You are using JDK on what platform?

Comments:

Risk Analysis (15 out of 15)

Risks identified: OK. Java is not in beta any more.
Alternate strategies identified: good

Comments:

If you wish to have your Requirements Document regraded, revise it within one week of receiving comments. Be sure to maintain a link to the original version of the Requirements Document in your notebook for comparison purposes. To get a regrade, you must send e-mail to the instructor requesting the regrade.