Team Meeting Notes and Agenda 4-5-2010

Lead: Denise Warzel

Moderator/Facilitator: Beate Mahious

Attendees

Semantic Infrastructure Services

Apologies

• Zoran Milosevic

Meeting Agenda

1. Introduction of three new Business Analysts Alan Blair, Zoran Milosevic, and Baris Suzek (5 minutes)
2. Updates to Requirement Gathering Template (5 min)
3. Review of Periodic Table ( Denise 10 minutes)
4. Presentation of use cases (Patrick - 15 min, Shantanu - 15 min)
5. Assignments for new business analysts (Denise 10 min)
6. Meeting schedule ( Beate 5 min)

Meeting Minutes

1. Introduction of three new Business Analysts Alan Blair and Baris Suzek

Alan and Baris share their background and experiences. Clarification of flow: Storyboard -> requirement -> use case -> sub use cases

Discussion of 5 viewpoints of RM-ODP:

1.       Business/Enterprise viewpoint
2.      Information viewpoint
3.      Computational viewpoint
4.      Engineering viewpoint
5.      Technology viewpoint

2. Updates to Requirement Gathering Template
Bea Mahious shows requested and implemented changes to the Requirement Statement template:

• additional line for revised statement
• additional line for link to use case
• added note to business analysts to keep "watch" on a requirement while writing a use case for it.
  Question about template titles clarified.
  New requests for changes are:
• delete "by reviewer"
• move the Statement up higher (right under the "Requirement #)
• move all descriptions from 2nd column over to first column

3. Review of Periodic Table
Denise presents the ppt of the periodic table and group discusses changes in layout and labeling.

4. Presentation of use cases
shortened due to time constraints.
Patrick has worked on:

• Medidata - revisit with Christo's feedback
• caIntegrator
• Automate
• No questions
  Denise brings up idea of placing requirement statement directly on master list to lessen the problem of incorrect or incomplete names for Forum Topics such as "Automate".

Shantanu has worked on:

• Content Browser
• No questions

5. Assignments for new business analysts
Alan Blair will be focusing on caDSR
Baris Suzek tbd

6. Meeting schedule
The group determines that a daily 15 minute meeting is not feasible for this group, because 3 analysts are not able to take part in these meetings. We decide to meet once or twice a week for one hour with the architect (Tom Digre) which will allow for a more in-depth review. Each analyst needs to be aware of what others are working on in order to determine inter-dependencies, conflicts and and to avoid duplications.
Bea Mahious presents a chart with the four time zones that the team works in. It becomes clear that some team members will have to work outside of regular business hours in order to get the entire group together.
We decide to set up a doodle poll to try and find one common time for everyone.

Action Items