srss revision

[Spencer Dickson]

Here are our assignments for our srss revision

Tyler, we kinda got a bad grade so we are going to redo with a maximum score of 180/200 available (we got 154/200)

Let us know if you have questions, it is due wednesday.

Matt - Use Case regular and full descriptions

Spencer - Non-functional reqs- map hardware - packaging diagram

Mike - delivery, archive, celebration milestones in mmp

          table of contents (he wants the 1.2, 1.3, etc,)

Tyler User interface prose

[MikeBowers]

Will someone verify what is meant by “delivery” and “archive”.  I just want to make sure I interpret it correctly.

[Spencer Dickson]

Delivery is the date we "deliver" to our customer (so us).  Archive is the day we pack up our code into an archive as a backup. 

[MikeBowers]

So by archive we mean the “Code Freeze” date?

[Spencer Dickson]

probably yes

[Matt Dimond]

Who knows with Ted

Matt Dimond
Dimond & Sons LLC
Cell: 801-891-6560
Office: 435-882-5526

Spencer Dickson <oilys...@gmail.com> wrote:

>probably yes
>
>
>On Tue, Feb 1, 2011 at 11:26 AM, MikeBowers <mickb...@gmail.com> wrote:
>
>> So by archive we mean the “Code Freeze” date?
>>
>>
>>

>> *From:* cs3750-...@googlegroups.com [mailto:
>> cs3750-...@googlegroups.com] *On Behalf Of *Spencer Dickson
>> *Sent:* Tuesday, February 01, 2011 11:05 AM
>>
>> *To:* cs3750-...@googlegroups.com
>> *Subject:* Re: srss revision

>>
>>
>>
>> Delivery is the date we "deliver" to our customer (so us). Archive is the
>> day we pack up our code into an archive as a backup.
>>
>> On Tue, Feb 1, 2011 at 10:51 AM, MikeBowers <mickb...@gmail.com> wrote:
>>
>> Will someone verify what is meant by “delivery” and “archive”. I just want
>> to make sure I interpret it correctly.
>>
>>
>>

>> *From:* cs3750-...@googlegroups.com [mailto:
>> cs3750-...@googlegroups.com] *On Behalf Of *Spencer Dickson
>> *Sent:* Monday, January 31, 2011 8:25 PM
>> *To:* cs3750-...@googlegroups.com
>> *Subject:* srss revision

[Tyler Rasor]

So I just need to rewrite the user interface prose?  I remember doing something for that last semester.  Did we get docked on it for it not being complete?  This is what I've found in our current document:
"The User Interface will be set up in a way to make the user experience as straight forward as possible.  A color scheme will be used to make highlighting selections in the menus easy for the user.  All text displayed will be easy to read for an average user."
I can add to that if that is all that is needed, or can do a rewrite.  Just wondering if you guys know...

---

Date: Mon, 31 Jan 2011 20:24:54 -0700
Subject: srss revision
From: oilys...@gmail.com
To: cs3750-...@googlegroups.com

[Tyler Rasor]

How are we turning in our revisions to Mike?  Are we just copy and pasting them into an email, or just as a word doc?

[Spencer Dickson]

I think he wants a short blurb under each page actually, if only just a sentence or two.  But that other thing you wrote should probably also be in there.  

We just want all around to add a bit more content in the areas he docked us.  He said a big part of his grading was based on whether the content was just present.  

[MikeBowers]

Just send any additions however.  Unless they are too exotic, I’ll figure out how to get them in there.

 

From: cs3750-...@googlegroups.com [mailto:cs3750-...@googlegroups.com] On Behalf Of Spencer Dickson
Sent: Tuesday, February 01, 2011 7:33 PM
To: cs3750-...@googlegroups.com
Subject: Re: srss revision

 

I think he wants a short blurb under each page actually, if only just a sentence or two.  But that other thing you wrote should probably also be in there.  

[Tyler Rasor]

Here is what I have come up with to add to the UI Prose.  Honestly, I don't know what else I can add to this without sounding like I'm just trying to make it look like there is more than there is.

The User Interface will be set up in a way to make the user experience as straight forward as possible.

When forms will be used to gather information, entries will flow in a natural manner (Next field will fall be below the previous).

Entry fields on a form will all conform to the same size. 'Tabbing' will take the user to the next entry displayed on the form.

Upon submission of a form, an error message will appear if there are any crucial fields that were not entered by the user, at which point the user will

be able to make changes and resubmit the form.

A color scheme will be used to make highlighting selections in the menus easy for the user.

All text displayed will be easy to read for an average user.

The user interface is designed in a way to make it easy for an average user to navigate through the bug tracking software. The design of the interface is

meant to be very user friendly, and is designed for users with little to no technical knowledge.

If anyone has anything to add to this, or would like to take anything away from this, it will not hurt my feelings.

See you all in class,

Tyler