SE401:Group58:Poster

From Marks Wiki
Jump to navigation Jump to search
Main Menu Work Plan Progress Research Backlog Functional Backlog
Meeting Minutes Supervisor Meeting Minutes Sprint Log Conference Poster

Poster Details

  • Bring Materials on Monday Meeting
    • Maybe sort out stuffs
  • Llyle away on Wednesday


Layout

Page Flow

  • Maybe Left-Right -> Top-Bottom
  • Maybe whole thing is a content player?
    • Boxes as Pips??
  • Not too overboard
    • Enough to attract them
  • Not too boring
  • Try find good choice of colours

Structure

  • Check Engineering Block for posters (See best ones)
  • N/A for now

Content

Llyle - Introduction

  • Brief overview of our project
    • Player in Silverlight, etc
    • Mention TANDBERG
    • Mention Project Goal
    • Why it's useful - Silverlight?
      • Why Silverlight

Body

Weng Hao - (Overview) Silverlight

  • High level stuff
    • Compare to Flash
    • Silverlight type of web-browser technology, etc
      • Internet Browser
      • Maybe image of our product in a browser
    • MICROSOFT
    • Integrates nicely with Visual Studio
      • Cross-language (Maybe mention VB and C# used in ours - MAYBE NOT?)
      • AND webservices
  • Xaml - How it's applied (Refer to how we made the navigator, video thingy)
    • Maybe Diagram of xaml vs rendered form

Weng Hao - Gui stuff silverlight can do=

  • Skim over GUI-features Silverlight provides
  • Powerful - can be created using stuff like Expression Blend for graphical designers
    • And developers, if they're created *cough*

Llyle - Silverlight can be used in OOP

  • Maybe diagram - Like Financial Markets using Machine Learning POSTER
  • Mention that it can use highlvl architectures for programming

Llyle - Webservices,etc

  • MAYBE NOT MENTION THIS (TOO COMPLEX FOR PUBLIC)
  • Maybe briefly mention about using TANDBERG Content Server
    • Where the Videos come from
  • Maybe why it's important to have webservices - Diagram?


Weng Hao - How it's useful in our project, etc

  • Enables easy extensions of TANDBERG's systems (HIGH LEVEL - TOO MUCH INFO)

Weng Hao - Conclusion

  • Useful for User Interface