Architecture review board
Download
1 / 94

Architecture Review Board Project: Asian Film Database - PowerPoint PPT Presentation


  • 1121 Views
  • Uploaded on

Architecture Review Board. Project: Asian Film Database . Date: 11/10/98. Agenda. 1. Project Overview - Solomon Yang(3 min) 2. OCD & prototype - Jingtao Sun & Tao Feng (12 min) 3. Requirement - by Hui Wang (5 min) 4. Architecture - by Solomon Yang (5 min)

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Architecture Review Board Project: Asian Film Database' - bernad


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Architecture review board

Architecture Review Board

Project: Asian Film Database

Date: 11/10/98


Agenda
Agenda

  • 1. Project Overview - Solomon Yang(3 min)

  • 2. OCD & prototype - Jingtao Sun & Tao Feng (12 min)

  • 3. Requirement - by Hui Wang (5 min)

  • 4. Architecture - by Solomon Yang (5 min)

  • 5. Project Plan - by Tao Feng (5 min)

  • 6. Feasibility Rationale - by Xinhua Wei (5 min)

  • 7. Discussion and comments (35 min)

  • 8. Summary (5 min)


System overview
System Overview

  • The Asian Film Database (AFDB) system is to create better awareness and understanding of Asian cinema by providing comprehensive and immediate availability of relevant information about it on the internet using the latest information technology, and thereby contributing globally to deeper intercultural understanding. This would also:

    • help the growth and development of the Asian cinema industry through effective marketing of Asian cinema within the region as well as internationally

    • encourage interaction and joint ventures with and among Asian cinema industry

    • enrich educational inputs for cinema and general education institutions



Project team
Project team

  • Customer

    • Karen Howell

    • Robert Doiel

  • Development team

    • Solomon Yang Team Leader/SSAD

    • Jingtao Sun OCP

    • Hui Wang SSRD

    • Tao Feng Prototype

    • Xinhua Wei LCP/FRD


Operational concept description ocd
Operational Concept Description(OCD)

  • Introduction

  • Domain Description

  • System Analysis

  • Concept of Operation


Purpose of ocd
Purpose of OCD

  • Identify high-level objectives and scope

  • Describe domains of the proposed system

  • Identify operational scenarios and prototypes of interfaces

  • Clarify operational concepts


Organization background
Organization Background

  • Cinema cultures

    • China, India, Japan, Korea and Taiwan

  • Film industries of the cinema cultures

    • From 10 to 800 films per year

  • User of Asian Film Database Clarify

    • Producers, directors, distributors, film critics, scholars, media as well as general public


Organization goals
Organization Goals

  • AFDB contain information for each of the cinema culture

  • Texts are available in English, Chinese, Japanese and Korean

  • User friendly and graphically user interface

  • Database management interface


Current system
Current System

  • No official Asian Film Database

  • Hard to obtain information of Asian Film

  • Integrity of information is not guaranteed

  • Information is usually out of date

  • Prevents interaction among film industries

  • Prevents growth and development of Asian cinema industry


Organization activity model
Organization Activity Model

  • Film Data management

  • Browse website of Asian Film Database

  • Database Administration


Film data management
Film Data Management

  • Creating a film Data Entry

  • Management of the new Film Data

  • Modification of Film Data


Browse website of afdb
Browse Website of AFDB

  • Choose language

  • Go through catalog

  • Search the database

  • Display film data record

  • Look up glossary context


Database administration
Database Administration

  • User account management

  • Data Maintenance

  • Collect updated data

  • Checks data consistency

  • Backup/restore the Asian Film Database


Statement of purpose
Statement of Purpose

  • Help the growth and development of Asian cinema industry

  • To encourage interaction and joint venture with and among Asian cinema industry

  • To enrich educational inputs for cinema and general education institutions


Project goals
Project Goals

  • A database accommodating Film Data

    • Accommodate 10,000 film records

    • Texts are in four languages

  • Friendly user-interface

    • User may choose preferred language

    • User may browse website through catalog

    • User may search database

    • User may check context glossary


Project goals cont
Project Goals(cont’)

  • Interface for data management

    • Check data record

    • Modify data

    • Add/delete data

    • Data transmission

  • Interface for database administration

    • Update/restore database

    • Manage user accounts

    • Collect updated data


System responsibilities
System Responsibilities

  • Film Data Management

    • Create Film Data entry

    • Management of new film data

    • Modify existing film data

  • Website navigation

    • Data in multiple languages

    • Catalog for web browse

    • Search by key words

    • Glossary context

    • Display multimedia data


System responsibilities cont
System Responsibilities(cont’)

  • Database Administration

    • User account management

    • Data maintenance


Users:

Language: Chinese/Japanese/Korean/Chinese;

Query:

keywords;

Browser:

Cinema culture, Title, Director, Actors….

Korean

English

Chinese

Japanese

Film Navigation

Search Engine

Glossary Context

Query: Keywords;

Catalog update

Result: Links

Multimedia Archive

Manager:

Client:

Data

Data

Data Edit;

Provides

Entry

Edit

Update;

data;

Data Edit:

Film Data:

text correction

title;

different language.

director;

Data viewing

actor….

update confirm

Video clip

film still...

Backup

Restore

System

Administration

Administrator

Block Diagram


Other Countries

USA

China India

Taiwan Japan Korea

Users

USC

Users

Clients

Users

UCS

USC Library

USC Students

Administrator

Asian Film Database

CSCI577a

Manager

Developer (Team3)

Stakeholders Hierarchy



  • System Requirement

  • Quality Attribute Requirements

  • System Interface Requirements

  • Environment and Data Requirements

  • Evolution Requirements


System requirement
System Requirement

AFDB consists of three subsystems:

  • Film Data Management

  • Film Data Navigation

  • Asian Film Database Administration


Film data management1
Film Data Management

  • Film Data Entry: clients to upload film data

  • Film Data Management: data managers to manage film data.



Film data navigation
Film Data Navigation

  • Users choose language to view the film data

  • Users utilize categories to browse the database website


Film data navigation continue
Film Data Navigation(continue)

  • Users use key words to search the film information of their interests

  • Users can access multimedia film data

  • Users gets help from contextual glossary to understand film information



Film database administration
Film Database Administration

  • Administrators manages Clients and Data managers

  • Film Database Maintenance



Quality attribute requirements
Quality Attribute Requirements

  • Usability

  • Performance

  • Dependability/Fault-Tolerance

  • Security

  • Compatibility


Usability
Usability

  • Ease of learning

  • Ease of use

  • Online Help


Performance
Performance

  • Fast response time

    To load a web page within 20 seconds (33.6k bps Modem)

  • Workload

    Film data Volume: 2000 films/year, 200 films/month, …


Dependability fault tolerance
Dependability/Fault-Tolerance

  • Availability (24hrs/day)

  • Reliability (authoritative)


Security
Security

  • Privacy

    Different levels of security

  • Integrity

    Film data resources, multi-languages

  • Audit

    Keep track of film data changing, clients...


Compatibility
Compatibility

  • Political Correctness

    Clients be responsible for data entry

  • Legality

    copyrights...


System interface requirements
System Interface Requirements

  • User Interfaces (GUI)


Environment and data requirements
Environment and Data Requirements

  • Operating Assumptions

    • Basic World Wide Web knowledge

    • Film Data Entry

    • WWW access

    • GUI Interface


Environment and data requirements continue
Environment and Data Requirements (continue)

  • Workload Characterization

    • 200 concurrent users

  • Data Storage Characteristics

    • Text + Images /per record = 500 KB

    • Total of 10k film records for 5 years

    • 500K x 10K =5G KB

    • Estimated Storage = 200% x 5G = 10G


Environment and data requirements continue1
Environment and Data Requirements (continue)

  • Design and Construction Constraints

    • Hardware Requirements /Limitation

      • AFDB shall be able to run with satisfactory performance on a Unix server

      • User may use PC, Mac, Unix,etc. with Internet connectivity.

    • Software Requirements

      • Server: Unix operating system

      • Users: Unix, Win95/98, Machitosh, Window NT 4.0

      • Standard World Wide Web browser (e.g., Netscape Communicator 4.0 or Microsoft Internet Explorer 4.0 or later)

      • DBMS (IBM DB2)


Environment and data requirements continue2
Environment and Data Requirements (continue)

  • Packaging Requirements

    • Installed on USC Unix server.

    • Maintained by ISD


Evolution requirements
Evolution Requirements

  • Capability Evolution

    • Make information available in other languages

    • Introduce more cinema cultures into database

    • establish mirror site in these cinema cultures to achieve fast Internet access

    • etc...


System and software architecture definition

System and Software Architecture Definition

Project: Asian Film Database

Date: 11/10/98


Agenda ssad
Agenda (ssad)

  • Overview

  • Component Model

  • Behavior Model

  • Enterprise Model

  • System View

  • Deployment View


Overview ssad
Overview (ssad)

Entity Model

Sys. Responsibility

From OCD

1. Component Model

2. Behavior Model

4. Sys. Component view

5. Deployment View

3. Enterprise Model

LCO Focus

Object Model

Operation Model

Class Model


Component model 1 component list

Entity Model

AFDB

Client

Manager

User

System Administrator

Film Data

Component Model

AFDB

Client

Data Manager

User

System Administrator

Film Catalog

Film Data

Glossary Context;

Component Model (1) - Component List



Behavior model 1
Behavior Model (1)

  • According to the system responsibility in OCD, we can summarize the following subgroup of system responsibilities:

    • Asian Film Data Management

    • Asian Film Navigation

    • AFDB System Administration








Deployment view

Web

Browser

Web Server

Search Engine

HTML File

- catalog

- glossary

- search interface

- data m/a

- data adm.

HTML generator

Data editor

Server

Data M/A

Database

Internet

Intranet(USC)

Digtlzd.

Device

Web

Browser

Web

Browser

Web

Browser

Deployment View

User’s Computer

Client’s Computer

Digtlzd dvc

Software

Data Mgr.’s Computer

Sys. Adm.’s Computer

Asian

film data



Overall life cycle strategy
Overall Life Cycle Strategy

  • Engineering Stage(CS577a)-- formulate operational concepts, requirement spec., arch., prototypes, life cycle plans, and integrate rationale for the proposed capabilities.

  • Production Stage(CS577b)-- develop initial operational capability products based on the requirement and arch. results from CS577a.-- training customer to use and maintain the system

  • Support Stage(USC ISD responsibility)


Phases of the development of afdb
Phases of the development of AFDB

  • Navigation

  • Data Input

  • Data Management

  • Database Administration

  • Help and Support



Major stakeholders in the development
Major stakeholders in the development

  • Owner: USC - ISD

  • Developer: CS577 students

  • User-- general public(web visitor)-- client-- Data Manager-- System Administrator

  • Customer: USC - ISD


Stakeholders responsibility user
Stakeholders’ responsibility -- User

  • Engineering Stage:-- Provide system requirement, -- Define the operational concepts -- Prepare the operational plan

  • Production Stage:-- Review and test each increment in the development environment

  • Support Stage:-- Actual usage on the AFDB


Stakeholders responsibility developer
Stakeholders’ responsibility -- Developer

  • Engineering Stage:-- prepare the system requirement, operational concept, system architecture-- make a plan -- build a prototype according to the above

  • Production Stage:-- implement and integrate the product-- perform and support test

  • Support Stage:-- Provide administrative support to the product transition-- adapt the product to operate in different environment.


Stakeholders responsibility customer
Stakeholders’ responsibility -- Customer

  • Engineering stage-- monitor and evaluate the project progress-- help to supply test data and scenario for system development

  • Production stage-- review system performance

  • Support stage-- Provide administrative support to the product transition -- maintain the system usage


Risk management
Risk Management

  • Unstable requirement-- currently there has no actual system, and a large part of requirements are based on customer’s plan.-- design system incrementally and modulely.

  • User interface mismatch -- prototype may not meet the customer’s requirements-- frequently interact with customer and get their feedback


Risk management 2
Risk Management (2)

  • Schedule constraints-- the whole project should be completed by the end of spring semester in 1999, so it will be too short to design and implement all the requirement .

  • External components, COTS-- there is no such a system now. When customers select database and other softwares later, they must think about compability with current system design and arch.

  • Personal Shortfalls-- the project will be continued by the cs577b students. They need time to be familiar with cs577a students’ work.



Quality management
Quality Management

  • One dedicated team member in project team who is in charge of performing the quality control.

    • develop documentation and coding standards

    • verify the compliance between the products and the documentation and coding standards

    • prepare test cases and produce test reports

    • not involved in the coding and development avoiding having any assumption and influence


Major project reviews
Major Project Reviews

  • Architecture Review Board (1)

    • overall content of the LCA package

    • make sure no other changes have occurred. If new elements have come out, they must be integrated at this time in the system.

  • Architecture Review Board (2)

    • The architecture designed, the developers have to make sure that they have not forgotten any requirements or import features.

    • All the risks have resolved.

  • Architecture Review Board (3)

    • must verity that no interface design errors have been made for any module of the system.

    • The review also checks that each individual module is well architected.


Major project reviews 2
Major Project Reviews (2)

  • Reviews/Inspections

    • The team insures that each sub-module is tested and meets all associated requirements.

  • Transition Readiness Review

    • focuses mainly on the acceptability of the system. The customer will meet with the development team to discuss whether or not the current system is acceptable as it stands.

  • Release Readiness Review

    • It must verify that all stakholders are satisfied with the system acceptance test. Everything that is produced by the development team is accepted.

    • at the end of the implementation phase.


Feasibility rationale asian film database
Feasibility Rationale(Asian Film Database)

To demonstrate from the following categories:

  • Product Rationale

  • Process Rationale

  • Analysis Results


Product rationale business case analysis
Product Rationale:Business Case Analysis

  • Development Cost Analysis

    • Developed by CS577b students

  • Implementation Cost Estimate

    • Training

    • Data preparation


Product Rationale:Business Case Analysis

  • Operational Cost Estimate

    • Employee of USC

    • Clients from different countries

  • Maintenance Cost Estimate

    • Essential devices

    • System Administrators


Product rationale requirements satisfaction
Product Rationale:Requirements Satisfaction

  • Capability Requirements

    • Film data management

      • Upload data by clients

      • Manage data by data managers

    • Film data navigation

      • Choose language, Browse the website, search films, and access multimedia data by users

    • Database Administration

      • Assign account for data managers and clients

      • Database maintenance


Product rationale requirements satisfaction1
Product Rationale:Requirements Satisfaction

  • Interface Requirements

    • Well-designed, user friendly, and simple enough

    • Specific interfaces for:

      • Data management Mode

      • User Mode

      • Administrator Mode


Product Rationale:Requirements Satisfaction

  • Quality Requirements

    • Usability: (easy to learn and use, help)

    • Performance: (response time, bandwidth, workload)

    • Dependability/Fault-Tolerance: (reliability, availability)

    • Security: (privacy, integrity, audit)


Product rationale requirements satisfaction2
Product Rationale:Requirements Satisfaction

  • Evolution Requirements

    • Establish the mirror sites

    • Extend number of clients

    • Extend participation to other cinema cultures

    • Proceed more business activities


Product rationale operational concept satisfaction
Product Rationale:Operational Concept Satisfaction

  • User browse the website

    • Mainstream Scenarios: Access, Display, navigate, etc..

    • Variant Scenarios: Quick search, Super search

  • Film data management and maintenance

    • Client’s data entry: Login, create entry

    • Data management: Login, manipulate

    • Data Administration: login, maintenance


Product rationale stakeholder concurrence
Product Rationale:Stakeholder Concurrence

The main agreements are reached as follows:

  • Schedule and cost

  • AFDB operations

  • Requirements

  • Development strategy

  • USC library operation


Process rationale system priorities
Process Rationale:System Priorities

  • On database

    • a database in USC

    • Film data from five countries in Asian

  • On operation

    • User: browse/download/navigate/search

    • Data manager: check/update/communicate

    • System administrator: maintain/collect/monitor/control

    • Client: create/transmit/check


Process rationale process match to system priorities
Process Rationale:Process Match to System Priorities

Spiral model and incremental development used.

  • In CS577a:

    • Formulate operational concepts, requirements specifications, architectures, prototypes, life cycle plans, and integrating rationale for the proposed capabilities.

    • In CS577b:

    • Develop Initial Operational Capability products with several increment steps


Process rationale consistency of priorities process and resources
Process Rationale:Consistency of Priorities, Process and resources

  • Database design and construction (very high)

  • Film data collection (high)

  • Requisite software assemble and needed skill learning for CS577b (high)

  • Authorization to run on USC web sever (high)


Analysis results
Analysis Results

  • Off-the-shelf solutions

    • DBMS

    • Web page designer

    • Data digitizing software

    • Film scan software


ad