Mark: 12 revision(s)

2008-11-03T05:22:48Z

12 revision(s)

New page

{{Group58:Menu}}

=Agenda=

The agenda for the April 11 Meeting cxan be found in the following URL: 
[[SE401:Group58:11ApilMeeting | April 11 Requirements Meeting Agenda]]

=Todo=

==Professor Grundy==
* Need Project Machine

==Students==
* Give Jesse link to workplan
* Create Feature Backlog
* Talk to Jesse on what they'd like
** Requirements
* Give Jesse a time
** email to Jesse
** jesse.baker@tandberg.com

=Minutes=

==General Information==

* Wiki still viable
** No confidential information for now
* R & D project
** Capture requirements
* Professor Grundy will give us internet account
** Free, unlimited internet
* Craig played around with Silverlight
** Maybe have sample code
** Play around with it
*** Build own and extend
* We have straight access to content server
* S3
** Doesn't give thumbnail via API
** Will get it later

===Content Server Tutorial===
* Tutorial information for the Content Server may be found here:
** [[http://www.tandberg.com/collateral/documentation/Application_Programmer_Interfaces/TANDBERG%20Content%20Server%20API%20(S3).pdf| Official Content Server API(S3)]]
** [[SE401:Group58:ContentServerTutorial| Content Server Tutorial]]

==Tandberg Meetings==

* Face-to-face meeting with Hamilton team
* Once a fortnight
* Can talk anytime (Via endpoints)
** Email if needed
* Give Jesse a time
** email to Jesse
** jesse.baker@tandberg.com

==Requirements==
* Looking at Silverlight as a technology
** What it can do
** Limitations
** How far can we go?
** No other options
*** Only focus on Silverlight, no alternatives
* Look at API we can offer
** Use existing API
** See if we can integrate Silverlight and API
** What Tandberg can offer that Silverlight can't

===Note===
* Focus on content only
* Don't worry about connection caps, etc
* Content Server
** API call
** Shouldn't really care about files

==Content Server Requirements==
* We have admin rights to content server
* Have to do everything via API
* Additional support needed:
** Extend API
** Only need admin access
* Security Updates
** When running, Tandberg updates as well

==Silverlight Requirements==
* Focused on the wmv and wma file format
* Thick client
* Doesn't matter what it runs on
** Microsoft is thickle..
* Show list of conferences available
* Search conferences
** Based on keywords
* Sort conferences
* Conference thumbnails
* Replicate existing Tandberg system
** Normal End-User Requirements:
*** Looking at videos
*** Browser
* Similiar to Youtube
** Can add stuff in Youtube
*** e.g. Links, etc
* Viewing
** Video most important
** GUI
*** Simple and clean as possible
*** Not fantastic
*** CONTENT ITSELF
* Must use WCF
* Must have bandwidth detection

===GUI Requirements===
* Scaling videos based on screen resolution
* 2-Videos Screen
** Must make sure layout is good
** Presentation must be good
** Audience and Presentation
** Looking at the sizing of the 2
** synchronized video
*** "What I hear is what I see"
** Synchronized
** Maybe both starting same time
*** Buffering issues: Pause until both videos ready at same time

====Notes====
* Make it simple
* Easy to use
* Clean
* Not too much time on GUI

===Video Viewer Requirements===
* MUST GET RIGHT - FOCUS ON CONTENT
* 4 Different Layouts
* Must focus on media itself
* Make content right
* Stream must be good (Not required by us)
** Done by tandberg

====Video Content====
* No recording
* Playback
* View and playback

====Video Recording====
* Just volume needed

====After Requirements====
* Finding a way of catching specific bits
** Time?
* Captioning
* Annotation
* Existing Tandberg API doesn't support this yet

===Library Requirements===
* Must be able to:
** Sort
** Search
** Use categories for Sort & Search

===Additional Features===
* Finding and sharing content
* Enhanced finding
* Example:
** If silverlight video has link
*** Pull out video and stores links
*** Share links

====Notes====
* Let users find what they want
* Audience:
** Client
*** Similiar to Youtube users
** Tandberg Engineers
*** For their learning purposes
** NO ADMINS

===Security Requirements===
* Ignore
* No password protection
* Rest of it:
** May want to think about it
*** Roles
*** Should display only users though
* Only 1 API user & password
* Can pass a user though
* Show the ones that you are allowed to see only
** (User Priviledges)

==Existing Tandberg System==
* Mixed with embedded media players
** e.g. Javascript, PHP
* Doesn't care what player
** Tandberg library deals with video format issues
** Only cares about video content
* Jesse - Author of SOAP API
** Soap:
*** Not just SOAP API
*** May have HTTP Operations
**** No need 1000's of SOAP calls
* API
** Does shield from server

== Presentation==
* Auckland
** Formal
** Followed by exhibition
* Presentation in Tandberg
** For company only

==Silverlight Information==
* Has SOAP version 1.1
** Can't speak with version 1.2
* WCF
** Silverlight goes through WCF
** Tandberg System also uses WCF
* Only streams via HTTP
* Can't do backward compatibility
* Can't configure with ports for HTTP?

==Equipment==

* Dial IP address
* Can't record meetings with Jesse from our endpoint.
** Can only do from Hamilton endpoint
* Easy to get information/content from it
* Can get download from Tandberg team
* 256K - Preferred resolution
* Data Traffic
** Hop-to-Hop
** Goes through Oslo

SE401:Group58:Tandberg Meetings - Revision history

Mark: 12 revision(s)