Online TV Music Channel

Miguel Rodrigues Student Number: 11511645

2MIN504 - Commercial Environments

Overview

• The project consists of an online TV music channel which content can be broadcasted online with a computer or a mobile device like Apple iPhone or the new phone from google Android G1

• The channel will broadcast Video clips from unsigned bands, as well as festivals and other music events from 3 capitals of Europe: London, Lisbon and Madrid. As well interviews from the artists.

• For the content to be broadcasted the user needs to install first a plug-in (i.e. Preferably our own plug-in but we can use other plug-ins such as sopcast, TVU Networks, Veetle Networks and so on)

• The artists can submit the files through a submission form in .mp4 or .mov movie file formats and they will be converted to our own video format

Stakeholders

Stakehoders

Power

Responsability

Influence

= = Authority

Budget holderSometimes can be the

budget holder but not always

Note: It is very important to understand what and how to communicate to each of the key stakeholders, making them feel confortable with the project and how it is progressing.

Stakeholders

External Analisys

Record Labels

Independent Artists

Consumers (music fans and mobile companies

Stakeholders

Internal Analisys

Programmer

Grafic Designer (in a later stage of the implementation of the project)

Lifecycle

Initiation Planning Execution

Closure

Methods for large projects (SSADM, UML)

Waterfall

SSADM

UML

Waterfall

This is the classical system development model

Concept

Requirements Design

Detailed design Development

Testing implementation

Waterfall

Strengths

• Minimizes planning overhead since it can be done up front.

• Structure minimizes wasted effort, so it works well for technically weak or inexperienced staff.

Weaknesses

• Inflexible

• Only the final phase produces a non-documentation deliverable.

• Backing up to address mistakes is difficult.

SSADM

Structured Systems Analysis and Design Method

developed in the early 1980s for systems analysis and application design widely used for government computing projects in the United Kingdom.

combination of text and diagrams throughout the whole life cycle of a system design

SSADM Tecniques

1.Logical Data Modelling

2. Data Flow Modelling

3.Entity Behaviour Modelling

SSADM

This is the classical system development model

Feasibility

Requirements Analysis

Requirements Specification

Physical Design

Logical System Specification

SSADM

Weaknesses

• Adopts a structured, rigorous, project led approach to the development of data structures and processes (fail to recognise that data structures are largely stable and many processes dynamic)

• requirements will not change during the development of a project

•Following each step of SSADM rigorously can be time consuming and there may be a considerable delay between inception and delivery (which is typically the first time the users see a working system).

UML

Unified Modeling Language

modeling syntax aimed primarily at creating models of software-based systems, but can be used in a number of areas.

UML

Syntax only - UML is just a language

Comprehensive

Language independent

Process independent

Tool independent

Well documented

It is a generic modeling language and needs to be adapted by the user to particular applications.

Features of UML Methodology:

Prototyping methods for large and small projects

RAD

DSDM

Evolutionary

Throwaway prototyping

RAD

RAD

prototypes

iterative development

structured techniques

involves

construction

merge

RAD - Stages

Planning

Implementation

Construction

Design

RAD

Pros

• Promotes strong collaborativeatmosphere and dynamic gathering of requirements

• Business owner actively participates in prototyping, writing test cases and performing unit testing

Cons

• Dependency on strong cohesive teams and individual commitment to the project

• Success depends on disciplined developers and their exceptional technical skills and ability

• Decision making relies on the functionality and less degree of centralized engineering authority.

DSDM

1. Active user involvement.

2. Empowered teams with authority to make decisions.

3. A focus on frequent delivery of products.

4. Using suitability for business purpose as the essential criteria for acceptance of deliverables.

5. Iterative and incremental development to ensure convergence on an accurate business solution.

6. Reversible changes during development.

7. Requirements that are base lined at a high level.

8. Integrated testing throughout the life cycle.

9. Collaboration and cooperation between all stakeholders.

DSDM

DSDM does not concentrate on the fundamental importance of corporate datamanagement

DSDM adopts a dynamic, project led approach to both data structures and processes

Like SSADM fails to recognize that data structures are largely stable and many processes dynamic

Weaknesses

Evolutionary

uses multiple iterations of requirements gathering and analysis, design and prototype development

iteration Analysis

Next level of requirements

Nex iteration

Costumer

design

Prototype Development

The result is analized by the costumer

Evolutionary

Strengths 

Customers can see steady progress.

This is useful when requirements are changing rapidly, when the customer is reluctant to commit to a set of requirements, or when no one fully understands the application area.

Weaknesses

It is impossible to know at the outset of the project how long it will take.

There is no way to know the number of iterations that will be required.

Throwaway Prototyping

Is a technical mechanism to reduce project risk by exploring critical factors to the project success

Main Benefits Can significantly reduce risk Commit to throwing the prototype away

When to use It can be used at any time and by any person on a project. Individual projects can realize some benefit by prototyping

risky areas within their individual areas of responsability. Main Risks

Not throwing it away Inefficient use of prototyping time

Solo project or large team?

TEAM:

2/3 Programmers

Grafic Designer

Database Manager

Accountant

Which Methodology?

Selecting the most appropriate methodology thepros and cons should be evaluated according to environment, cultural and technological development.

Evolutionary Methodology – to deliver a working system to the users RAD – because it promotes a strong collaborative atmosphere and dynamic gathering of

requirements. Business owner actively participates in prototyping, writing test cases and performing unit testing

RAD is suitable for applications which are interactive, with clear functionality at the user interface, have a clearly defined user group, are not computationally complex and have requirements which are not too detailed and fixed.

It is possible, during the implementation of the plug-in and, mainly, on the development of the new Video format, to use a different methodology such as Throwaway methodology.

TV channel

Development of the newCompressed video format

Always regarding compression/quality

issues

Development of the plug-in

Website Videos

Database

upload

EvolutionaryMethodology

Use of the ThrowawayMethodology & Testing

RADMethodology