Requirements Document Comments

Team: NO (aka Cyberguide, but that is already taken. you could do CyberBuzz, but I'm afraid GaTech wouldn't allow it to continue with that name. :)

Grade: (79 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: You'll get 10 points instantly for just showing me the storyboard. Overall, you did a good job on this and I think you can address all of the criticisms.

Project Description of Target System (10 out of 10)

Comments: freeze it

Scenario descriptions (10 out of 10)

3 scenarios provided - OK
level of description - good
clarity - good

Comments: Scenario 1 last line "being" -> "begin"

Hmm, sounds like you guys are prepared to commercialize the idea. I say go for it, as long as you give me some credit for the original idea. :)

Storyboarding (0 out of 10)

Evidence of storyboarding - I believe you have done it, but until I see evidence of the storyboard (scanned or not), I'll hold back the points.
Connection with scenarios - not really, you are basically going with minimal changes to the existing Cyberguide.

Comments

Functional Requirements (20 out of 25)

Number of requirements - 5 major categories with further subdivision - good
Clarity of description - brief, but I get the idea
Decomposition - OK
Prioritization - not done. What comes first. I know you think you are going to get all of this completed, so you should just indicate to me what will come at the end of Week 6, Week 7, ...

Comments: It is a non-trivial task to Enter project information. There are a couple of ways to make your life easier, however. First, Don Allison prepares all of the information for the Demo Day (project descriptions and locations) in a Frame Document that you could grab and work with. Also, you could consider extracting information automatically from the GVU Web pages that describe most of the projects and using an HTML renderer to display information.

How are you guys going to integrate with the positioning system. If you want more information on how that work, let me know. Also, your scenarios suggest that you will do outdoor as well as indoor positioning. Have you thought about how to build the system to achieve both? We have a GPS receiver for use with Cyberguide.

Non-Functional Requirements (14 out of 15)

Clarity - good
Measurability - good for some, not so good for fault tolerance.
Variety - good

Comments: The 5 second access time is too long. Earlier versions of the Newton Cyberguide probably had about 2-3 seconds access time and we were getting lots of complaints. Fortunately, we seem to have found another way of accessing the info base to drastically reduce the latency and we now get around 1 sec access.

Platform and Network Environment (5 out of 10)

Vehicle platform - palmtop, but it's running Pen for Windows 1.0 built on top of 3.1.
Development platform - you don't mention this. It will be different from the palmtop and you need to mention that you will be developing using Delphi.

Comments:

I have a palmtop 486 that I can loan you to test out. It is a somewhat fragile platform, I'll warn you.

Risk Analysis (15 out of 15)

Risks identified - yes
Alternate strategies identified - yes, but I think you are still a bit too optimistic. For instance, you will have to be careful about the object design of the network. How are you going to integrate a non-Delphi network service cleanly into your system? I don't think you are going to have much problems on the storage front, but I do like you thinking about moving the storage off the Cyberguide.

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.