SE401:Group58:Sprint2

From Marks Wiki
Revision as of 05:22, 3 November 2008 by Mark (Sọ̀rọ̀ | contribs) (5 revision(s))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Main Menu Work Plan Progress Research Backlog Functional Backlog
Meeting Minutes Supervisor Meeting Minutes Sprint Log Conference Poster

Sprint 2

  • Duration: 2 weeks
  • Start Date: 23 July 2008
  • End Date: 6 August 2008

Developer Hours

  • Llyle= 20h
  • Weng Hao= 20h
  • Total of 40h

Deliverables

  • Pip-enabled Video player (Picture in picture)
    • Pip will play a second stream of video
    • A better-looking video interface than places greater focus on the video content

Tasks

Task 1: Pip Logic

  • (Presenter-bound)

Task 1.1

  • Duration: 10 minutes
    • Both videos should play simultaneously on play command
    • Both videos should stop simultaneously on stop command
    • Both videos should pause simultaneously on pause command

Task 1.2

  • Duration: 5 hours (With Test under Unit Testing)
    • Smaller video should be contained in large video at all times
    • Smaller video should not be smaller than 50 pixels by 50 pixels
    • Smaller video should not be larger than 50% in width of larger video and 50% in height of larger video

Task 1.3

  • Duration: 2 hours
    • PiP Video should be movable when clicked and dragged.
    • PiP Video should remain stationary otherwise


Task 2: Pip Visuals

  • (View-bound)

Task 2.1

  • Duration: 3 Hours
    • There must be a large and a small video, both of which are rectangles and contained in the video player control
    • The large video occupies the majority of video player control real-estate (Main focus on Video Player)
    • The small video must be on top of large video

Task 2.2

  • Duration: 3 Hours
  • The small video must be drag-able and instruct presenter of change in coordinates
  • The small video must be resizeable and instruct presenter of size change
  • The small video must have a non-intrusive yet identifiable border
  • The large and small video must always be visible and opacity set to 100%

Task 3: Volume Logic

  • (Presenter-bound)

Task 3.1

  • Duration: 1.5 Hour
    • Volume is a float number than is between 0 inclusive and 100 inclusive.
    • Volume of 0 represents minimum allowed sound from video player.
    • Volume of 100 represents maximum allowed sound from video player.
    • The change in volume is linear in comparison to video volume (decibels)

Task 4: Volume Visuals

  • (View-bound)

Task 4.1

  • Duration: 4.5 hours
    • Volume is represented by a slider metaphor that is of ‘reasonable’ size. (Such that it is non-intrusive but visible and easily modifiable)
    • A visual metaphor should indicate what is ‘loud’ and what is ‘quiet’. (Perhaps a three stage image that shows a small speaker with one sound wave for quiet, two sound waves for medium and three sound waves for loud)
    • Triangular visual "Slider" (Volume Control metaphor as a cone/triangular-shaped image)
      • Current Volume as a sub-triangle in the Volume Control Template

Task 4.2

  • Duration: 1 hour
    • Volume Icon changes 'sound waves' based on percentage of volume.
    • Volume Control based on where the user clicks on the video player

Task 5: Extras Pile

  • (These are to be done after completion of all other tasks)

Task 5.1

  • Duration: 8 hours
    • The video location metaphor should be of such a nature that the video location is perceived as a property rather than a controller of the video contents.
      • Needs to be hidden by default.
      • Needs to have button at bottom control that allows it to be viewable (Show/Hide this metaphor/property)
      • Must be relatively small in comparison to rest of main control
      • Needs to convey metaphor of a property view

Task 5.2

  • Duration: 3 hours
    • Show/Hide 'rectangle' - When moused over, 'pops up' player controls (Opacity).
      • The video player controller panel (sub controls) should be hidden or dimmed if inactivity is sense. Inactivity is a measure of the lambda of movement within the video player control within a lambda of time while the control is in focus, such that the lambda of movement and lambda of time are of a value greater than established constants K and C (for arguments sake). Values of K and C are determined through rough simulation studies/experiences.

Task 5.3

  • Duration: 3 hours
    • Visual
      • Remade into separate components (Visual - Skins)
      • The size of video player controls should be reduced in size, with the exclusion of the video surface.

Task 5.4

  • Duration: 3 hours
    • Both presenter and view
      • Buffering indication required.

Task 5.5

  • Deferred (TBA - Confirm with TANDBERG first)
    • Seeker position should not be movable outside the buffered data.


Allocations

The alloctions indicate the starting tasks. The idea is that developers can pick appropriate tasks off this sprint backlog and work on it.

Llyle

  • Task 4.1

Weng Hao

  • Task 1.1 - 1.3