SE401:Group58:SMeetingMinutes040708

Main Menu	Work Plan	Progress	Research Backlog	Functional Backlog
Meeting Minutes	Supervisor Meeting Minutes	Sprint Log	Conference	Poster

TODO

By Wednesday

• Thorough Review of Tandberg Files BY WEDNESDAY

By Next Meeting

• Research Topics
• Research Topic Prioritization
  • Research Tandberg API as proper research topic
  • Add possible research topics to research backlog
  • Raise concerns to Professor Grundy
  • Prepare questions for Friday 11

By Friday

• Ask Tandberg how their system works
  • How live their information on database is (i.e. Infrastructure)
    • If data is stored first, then nothing of our things can be dynamic..
    • If active, we can add connotations to Video, etc
• ASK ABOUT TANDBERG PRESENT TECHNOLOGIES

Agenda

• Any concerns for Friday Meeting
  • Things to discuss with Professor Grundy
• What to do this week
• Where should we put research information and documentation?
• Workplan - Flesh out information for later dates
  • Beyond Interrim Report Date
• Research
  • Stuff

Minutes

• Workplan
  • Filling in dates after Interrim
  • 2 Months planned at a time
  • After each month - Review progress, plans, dates
    • Provides progressive feedback for iterations
  • Note: When iteration starts on weekend, use time to start short stories
  • Sorted May iterations

• Friday 11
  • Meeting details and preparation
  • To get sorted:
    • Meeting times with Tandberg (Regular)
      • Possibly Monthly?
      • Professor Grundy may have something sorted?
      • Using their technology
      • Specific requirements from Tandberg
      • Requirements may change (Since it's agile)
  • Meetings must involve the above, so that we can have proper agile development
    • Possibly capture their requirements regularly
      • (In case wrong perspective, requirements)
• Ask about Tandberg architectural structure AND significance to our project
• Ask about their video housekeeping (i.e. Size limitations for cache, sector breakdowns, etc)
• Will their API shield the application programmer from the underlying implementation?

• Tandberg
  • Presentation
    • Do we get an hour of their time?
  • Their Requirements
    • Standard and minimal Requirements (Hardware requirements) for using their Tandberg software
    • If to run our app requires a significantly greater processing power, that's going to be a considerable factor
  • Servers
    • What .Net Framework
      • Upgrading for clients may be a significant factor
      • Part of research
      • MUST DO IT BEFORE TANDBERG MEETING (April 11)
  • Must ask about their database and information
    • Stored info = Not live
      • Not able to connotate on the fly
      • Can do review purposes, etc
• Tandberg architectural structure AND significance to our project

• Research
  • Applets may be another possibility
    • (Not intuitive with new IE)
  • Content Server
    • May like to do Non-web-based application?
      • Thick Client instead
  • Extending customer's viewing pleasure
    • Investigating different ways we can implement media interface via Silverlight
      • Includes streaming, caching of incoming data, and other

• Rich Media Interface
  • Correlated to GUI-side of things?
  • Maintenance of Video, administration?
  • For clients or for admins (Conference or DB admin?)?