and System Software Architecture Description (SSAD) `
Version 1.1
System and Software Architecture Description (SSAD)
Youthink.com Video Uploading and Conversion System
Team # 10
Sandarsh M Kumar Project Management Rajen Sarda System Analysis Peter Thompson Operational Concept Description Pius Pack Feasibility Rational Description Stephen Cathers Prototyping Tasneem Hakim System Requirements Description Robert Dean IV & V John Marshall IV & V
SSAD_LCO_F06a_T10_V.1.1
i
5/18/2009
System and Software Architecture Description (SSAD) `
Version 1.1
Version History
Date 10/11/06 Author Rajen Sarda Version 1.0 Changes made Original document Section 1 & 2 10/23/06 Rajen Sarda 1.1 Added Section 3 for System Architecture Design Added Domain Model figure in Section 2 Rationale Initial draft for use with LeanMBASE v1.4 template for SSAD , OCD& SSRD for team 10 project SSAD for LCO Package. Architecture Design
SSAD_LCO_F06a_T10_V.1.1
ii
5/18/2009
System and Software Architecture Description (SSAD) `
Version 1.1
Table of Contents
SYSTEM AND SOFTWARE ARCHITECTURE DESCRIPTION (SSAD)..................................................................I VERSION HISTORY.........................................................................................................................................................II TABLE OF CONTENTS .................................................................................................................................................III 1.1.1.Introduction........................................................................................................................................................iv
1.1.1.1.Purpose of the SSAD Document .................................................................................................................................iv 1.1.1.2.Standards and Conventions..........................................................................................................................................iv
1.2.1. System Analysis.................................................................................................................................................vi
1.2.1.1.Domain Model ............................................................................................................................................................vi 1.2.1.2.Actors .......................................................................................................................................................................vii 1.2.1.3.Process Model............................................................................................................................................................vii 1.2.1.4.Functional Areas........................................................................................................................................................vii 1.2.1.5.Behavior....................................................................................................................................................................viii 1.2.1.6.Refinements from OCD.............................................................................................................................................viii
1.2.2. Technology / Platform Specific Model............................................................................................................viii
1.2.2.1.Structure .....................................................................................................................................................................ix 1.2.2.1.1.Hardware Classifiers...........................................................................................................................................ix 1.2.2.1.2.Software Classifiers Model.................................................................................................................................ix 1.2.2.1.3.Deployment Model...............................................................................................................................................x 1.2.2.1.4.Process Model.....................................................................................................................................................xi
SSAD_LCO_F06a_T10_V.1.1
iii
5/18/2009
System and Software Architecture Description (SSAD) `
Version 1.1
1.1.1. Introduction
1.1.1.1. Purpose of the SSAD Document
The purpose of System and Software Architecture Description (SSAD) for `Youthink.com' project is to give an insight into a feasible organizational concept of operation, architecture and implementation design for the system. This document will serve as a useful bridge between the Operational Concept Designed during the Inception phase. Built with the suggested architecture for the project, this document defines a high-level domain model of the system, provided by the Operational Concept Design (OCD) and will satisfy the requirements stated in the System and Software requirements document (SSRD) which was obtained after the negotiation sessions with the client. The document will serve as a reference for the development team and will help them in building a reliable and consistent system. It will help the stakeholders to understand the basic relationships and interactions between the different system components.
1.1.1.2. Standards and Conventions
Standards Used: Lean MBASE Guidelines version 1.7 Lean MBASE Additional SSAD Guidelines version 1.4 Notations Used: UML V1.3 : Unified Modeling Language Conventions Used: Glossary of Terms section of Easy Win Win Negotiation Report Terms used in OCD and SSRD on this project
1.2.
References
iv 5/18/2009
SSAD_LCO_F06a_T10_V.1.1
System and Software Architecture Description (SSAD) `
Version 1.1
<<References are summarized in SID>>
SSAD_LCO_F06a_T10_V.1.1
v
5/18/2009
System and Software Architecture Description (SSAD) `
Version 1.1
1.2.1. System Analysis
This section will analyze the top-level domain analysis of the proposed video uploading and conversion system. It specifies the overall domain level system structure. Its operational stake holders and their domain level behavior refined from the operational concept proposed in the Operational Concept Description (OCD) for the LCO and the requirements identified in the System and Software Requirements Definition (SSRD) are modeled in Rational Architect. To avoid the redundancy between the model and SSAD draft, the description about the role and behavior of operational stakeholders are not captured in the draft.
1.2.1.1. Domain Model
Youthink.com is an online community site. The youthink.com "Video Uploading & Conversion System" is an extension to the available features of the site. It consist of a Video Upload and Conversion Manager that allows the users to upload the videos to YouThink in different formats and automatically converts the video into Flash Video (FLV) for streaming over the internet. The primary operational stake holders of the system would be a user, administrator and flash media server. The system allows the key member to upload videos. The normal user would be able to watch the uploaded videos online. The other registered and unpaid member will be allowed to access other features of the web site. Hence a User class is generalized as an Authorized_User (unpaid registered user) and a Member (paid registered user) class in the domain model. The client of site the will assume administrator's role for the system. An administrator being a registered user is a generalization of Authorized_User class. Other Functional Classes being added to the system are Video_File which is generalized into an Uploaded_Video_File and a Converted_Video_File. System_Logs and System_Statistics are included as a class in domain model for video statistics and error logs information. Figure 1: System Analysis Domain Model
SSAD_LCO_F06a_T10_V.1.1
vi
5/18/2009
System and Software Architecture Description (SSAD) `
Version 1.1
1.2.1.2. Actors
The operational actors of the system their roles, purpose and responsibilities are described in documentation section of each actor in rational software architect tool.
1.2.1.3. Process Model
The process model of proposed system analysis model has the following functional areas.
1.2.1.4.
Functional Areas
The primary purpose of the video uploading and conversion is uploading videos, automatic video conversion, allowing administrator to change the video upload and conversion parameters, reporting system statistics/error logs and streaming the video online as requested by the user. Considering these requirements the domain analysis model consists of following functional areas. (1) Access management Under this functional area the system will allow an Authorized User to access an existing account, create new account and change password for accessing the system. This functional area is already implemented with the youthink.com site. To maintain the consistency with the business work flow for the video uploading and conversion system, it is included into the system process model. (2) User Video Uploading This functional area allows the Member user to upload a video, get the feedback on video uploading, set and edit video file information as well as check the video conversion status. (3) System Administration And Reporting An administrator updates video upload and conversion parameters, view system statistics and Error logs. This functional area fulfills the `video reporting' capability identified in OCD. (4) Video Streaming User requested video will be retrieved from the video archive and streamed through a flash media server.
SSAD_LCO_F06a_T10_V.1.1
vii
5/18/2009
System and Software Architecture Description (SSAD) `
Version 1.1
1.2.1.5. Behavior
Details of the processes and their domain level behavior used for implementing the capabilities described in OCD are described in documentation field of each process in the rational software architect tool. It gives the state model of the system.
1.2.1.6. Refinements from OCD
Stakeholders Stakeholders defined in OCD Team 10 developers IV & V End Users Client/Administrator Operational Stakeholders in System Analysis Model End Users Administrator Rational: End users and administrator will be directly interacting with the system for video uploads and system administration respectively.
1.2.2. Technology / Platform Specific Model
This section will analyze the top-level design analysis of the proposed video uploading and conversion system. It specifies the overall design structure of the system. A feasible Deployment model along with the Hardware and Software Component Classifiers and their design level interaction, refined from the operational concept proposed in the Operational Concept Description (OCD) for the LCO and the requirements identified in the System and Software Requirements Definition (SSRD) are modeled in Rational Architect (Architecture Package). The proposed system would be technology specific. Given its broad user base and wide spread popularity, Flash Video format will be required as an output when videos are converted. Similarly, the popularity of Windows Media also necessitates its use as an output when videos are converted. Apart from this we have to leverage on the existing set of hardware components and software tools (ASP, Cold Fusion) available with the client for developing the system.
SSAD_LCO_F06a_T10_V.1.1
viii
5/18/2009
System and Software Architecture Description (SSAD) `
Version 1.1
1.2.2.1. Structure
1.2.2.1.1. Hardware Classifiers
Following are the Hardware Classifiers considered for the System Architect Design. (1) Web Server Interface to upload user video and request the videos to be played back. The uploaded video will be sent to the File Server through the Web Server interface. It will also send the video file request to the file server when user requests a video display. (2) File Server ...