GENERIC DISCUSSION: 
-------------------
- Discussed days in which we should meet. Of those who attended, we determined the
  following days would be good to meet:
    Tuesdays - 7-9
    Wednesday - 7-9
    Thursday - 6-8

  As long as most people can attend each meeting (and everyone can attend atleast
  one each week), then this should be ok.  For those who couldn't attend, please
  e-mail Al ([email protected]) immediately to inform him what days are good/bad.

- Ed McGillis (Coach) bought index cards for us to write user stories on!

- We discussed user stories and how they are done.
  - Ed McGillis (Coach) informed us that user stories are written by the 
    customer and that the customer will work with the developers to 
    make the user stories refined and "correct" for the project.

- We discussed what we want to accomplish for the rest of the semester
  - Software Scope
  - System Metaphor
  - User stories
  - Release (Iteration) Plan
  - If we can get to them unit tests & functional tests.

- We determined that Drew Roedersheimer will be the new customer.  Taking over for Ian. 
  Ian will now be a developer (Ian informed us earlier via e-mail that this would
  be ok).

- Al Chu will e-mail the TA to inform him that a role change has occurred.

- Al Chu informs everyone to update your timesheets online !!!

- Prashanth Ranganathan will do all entity relationship or flow-diagrms and place
  them on-line if we ever decide to do these diagrams.

- We determined that once user stories are placed online, we should make a "time-line"
  of total user stories over a number of days.  (i.e. all user stories on 11/5/00, all
  user stories on 11/7/00, etc.).  That way, we can show what changes were made to
  user stories and which ones were removed & etc.  

- Plans for next time
  - Will meet Tuesday 7-9 for next time
  - Continue to discuss days we can meet.
  - Discuss initial user stories with Drew Roedersheimer with issues we have with 
    stories.  This should be done so that Drew can begin writing user stories
    on cards and putting user stories on the web page too.
  - Write up a system metaphor
  - Edit Software Scope if necessary

USER STORIES:
-------------

Unforunately Drew Roedersheimer (Customer) was unable to make the meeting at last minute.  However,
Drew was nice enough to e-mail us a whole list of ideas he had for user stories so that we could
get an idea of what he (the customer) wanted for the system and we could begin thinking about
our project.

The e-mail:

Date: Sun, 05 Nov 2000 19:16:35 -0600
From: Drew Roedersheimer 
To: [email protected]
Subject: meeting tonight and user stories

Al,

I thought I'd be able to get back from home in time for the meeting
tonight, but it doesn't look like I will....  I've put together some
user stories and here they are.   I hope you get this in time for the
meeting and my absence doesn't screw things up too much..


User stories (some of these are probably already implemented, but I
figured they would be useful nonetheless):

Students can login and view grade distributions for each course and each
assignment / exam.

Students can login and view percentile rank for each course and each
assignment / exam.

Students are restricted to viewing only their own data.  A secure login
scheme is required to ensure that passwords don't go out in plain view.

TA's login and view data for the courses they are working on.  Access
must be restricted to only the courses they should have access to.

TA's login and update data for the courses they are working on.  Some
type of concurrent access restrictions must be implemented.

TA's should also be able to view their own course data for courses they
are currently taking.

TA's and professors can access particular students' grades by entering
the course number and the students' login / ssn.

TA's and professors can post grade cutoffs for assignments / quizzes /
exams for each course they have access to.

Certain TA's should be allowed to update student data while others
should only be allowed to view student data for the courses.

Professors can login and view data for the courses they are teaching.
Professors may be able to view data for all courses - not just the ones
they are teaching.

Professors can also login and update data for courses they are
teaching.  Professors should only be able to update data for their
courses (obviously).

Administrative staff have different levels of access priveleges.  Some
can access courses in particular majors, while others may access any and
all courses.

Administrative staff can access summaries of the courses they are
checking.  Examples include the current average of all students, grade
distributions, etc.

Administrative staff can access students' grades in particular courses
by entering the course number and the students' login / ssn.

Administrative staff can retrieve a summary of the students' standing in
all courses being taken at this time.

Administrative staff can retrieve a history of the students' standings
in all courses taken at the university.

I'm sure we can come up with more, but that's all I could think of at
the moment.  Let me know what you guys think, as well as what goes on at
the meeting.  Again, sorry I can't make it.

-Drew

USER STORY ANALYSIS:
--------------------

- We analyzed the user stories and came up with many questions.  These
  questions will be brought up at the next meeting so that the customer
  can edit his user stories and we can get a better idea of the system as a whole.

- In edition, Edward McGillis (Coach) told us that since "real" user stories
  are done during discussion between the customer and developer, that we would not
  count these as "real" user stories (atleast not at this moment).  Although many of them 
  will end up user stories.

Yun Li - Who creates the class in the gradebook program?  The Administration?

Angela Thelen - Does Administration refer to system administrators or faculty (Deans)?

Al Chu / Edward McGillis - Will graders be allowed to enter data into the gradebook?

Everyone - Will the gradebook program give a history of all classes and grades, or grades
           for just one semester?

Everyone - Who gives ability to an individaul to create/edit/etc. grades & classes?

Prashanth Ranganathan - What kind of security is expected of the system?

Prashanth Ranganathan - Can the user update entire class grades at one time?

Yun Li - Who creates entries (i.e. homework/exam/MP entires) in the gradebook, Professors
         or TAs?

Everyone - Who sets up a class in the gradebook itself?  Administration?

SOFTWARE SCOPE:
---------------
- We then wrote up a preliminary software scope to get an idea of the system.  The software
scope can be found on the webpage.

EMAILS:
-------
Date: Mon, 6 Nov 2000 00:32:52 -0600 (CST)
From: Al Chu 
To: CS327 TA 
Cc: drew alan roedersheimer , ian michael bearman 
Subject: Re: Web Based Gradebook - Questions

On Wed, 1 Nov 2000, CS327 TA wrote:

> 3. You can change roles. Just notify me.

Ian Bearman is now a developer & Drew Roedersheimer is the customer in our
group.

Thanks,
Al Chu