SE401:Group58:Sprint1Results
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 1 Outcome
- In terms of the software development process we have completed Sprint 1
- Shown that images can be placed in a Silverlight Application (particularly in the XAML markup) to facilitate in delivering a aesthetically pleasing user interface
- Shown that buttons, sliders, and such traditional graphical components that offer useful metaphors and functionality are available for use in Silverlight and can be used to great effect.
- Shown that video can easily be played by the use of a Silverlight MediaElement control, although the desired was expressed to explore alternative black box-type video enabled controls to curb future restrictions on buffering control which is likely to arise from user requirements. Current implementation was developed by binding a URL, but byte stream binding is another option.
- Shown that it is simple to implemented seek functionality and to introduce seeker indicator granularity. (Only allow increments of x seconds where x is an Integer less than the maximum position, which is useful for timeline snapping if the user requirements wished to look into timeline snapping and annotation)
- Shown that the different Silverlight user interface participants (the view/graphics/components, the presenter/User interface logic, the model/domain-specific data) can be loosely connected as this sprint addressed placing the Video Player under the MVP pattern which was successful.
- Shown that the presenter (user interface logic) can be placed under both unit and mock tests even though the presenter is a Silverlight Library which causes framework conflictions when adding the presenter project to the Windows Library which does the testing.
- The above was solved by referencing the presenter DLL directly instead of referencing the presenter project file which means that we have shown that it is possible to reference the DLL of a Silverlight Library in a Windows Library, even though they reference different .NET Framework API.