Architecture Review Board I Presentation

transcript

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) 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

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

System Overview (conti.)

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)

Introduction Domain Description System Analysis Concept of Operation

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

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

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

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

USC Library

Asian Film Database

Film Data

Manager

Client

Administrator

MaintenanceManage

Browses

Belongs to

Provides Film Data to

Context Diagram

USC Library

Asian Film Database

Film Data

Manager

Client

Administrator

Hosted by

Maintained byManaged by

Serves

Stores

Receives Film Data from

Entity 01

Asian Film Database

Film Data

Browses Displays

Entity 02

USC Library

Asian Film Database

Film Data

Manager

ClientAdministrator

Employed by

Obtains privilidge from

Manages Maintains

Send request to

Entity 03

Asian Film Database

Film Data

ManagerClient

Adminis trator

Backup/restore Maintain

Authorizes

Entity 04

Authorizes

Asian Film Database

Film Data

Manager

Client

Administrator

Obtains privilidge from

Send Film Data to Creates

Communicates with

Entity 05

Asian Film Database

Film Data

ManagerClientAdministrator

Maintained by

Stored in

Created by Managed by

Entity 06

USC Library

Asian Film Database

Manager

HostsEmploys

Entity 07

Organization Activity Model

Film Data management Browse website of Asian Film Database Database Administration

Film Data Management

Creating a film Data Entry Management of the new Film Data Modification of Film Data

Creats Film Data Entry

Client

Updates database

Verifies consistency of new data

Translate text Edit Film Data

Rejects wrong dataCommunicates with Client

Manager

Fiml Data Management

Browse Website of AFDB

Choose language Go through catalog Search the database Display film data record Look up glossary context

Looks up Glossary Context

Diaplays Film Data

User Browses Asian Film Database

Goes through Catalog Searches Key Words

Choose Language

Views ImagesPlays Video

Database Administration

User account management Data Maintenance Collect updated data Checks data consistency Backup/restore the Asian Film Database

Database Administration

Restores databaseModify Database

Back up database Collects updated dataCheckes data consistency

AdministratorClient Manager

Assigns memberships

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

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’)

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

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’)

Database Administration– User account management

– Data maintenance

English Chinese Japanese Korean

Search EngineFilm Navigation

Glossary Context

DataEntry

DataEdit

Multimedia Archive

Film Data:• title;• director;• actor….• Video clip• film still...

Data Edit:• text correction• different language.• Data viewing• update confirm

Query: Keywords;Result: Links

Catalog update

Users:Language: Chinese/Japanese/Korean/Chinese;Query: keywords;Browser: Cinema culture, Title, Director, Actors….

Client:Providesdata;

Manager:Data Edit;Update;

System AdministrationAdministrator

BackupRestore

Block Diagram

Stakeholders Hierarchy

Other Countries

Administrator

Manager

Asian Film Database

USC Library

Developer (Team3)

CSCI577a

USC Students

USC Users

Clients Users

China IndiaTaiwan Japan Korea

System and Software Requirement Definition

Asian Film Database

System RequirementQuality Attribute RequirementsSystem Interface RequirementsEnvironment and Data

RequirementsEvolution Requirements

System Requirement

AFDB consists of three subsystemsAFDB consists of three subsystems:

Film Data Management Film Data Navigation Asian Film Database Administration

• Film Data Management

- Film Data Entry: clients to upload film data - Film Data Management: data managers to

manage film data.

Illustration to Film Data Management

<<RQ-02>>

Film Data Management Use Case Model

Film Data Manager

Update/Edit Film Database

Complete Translation

<<RQ-02>>Reject

Film Data

Communicate with Client

Client

<<RQ-02>>

Check Film Data Integrity<<RQ-02>>

<<RQ-02>>

Create Film Data Entry

<<RQ-01>>

Assistant Manager to complete Translation

<<RQ-01>>

• Film Data Navigation

- Users choose language to view the film data- Users utilize categories to browse the

database website

• 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

Illustration to Film Data Navigation

Choose Languge

<<RQ-03>>

Browse Film Data through Catalogue

<<RQ-04>>

Search Film Data by Keywords

<<RQ-05>>

Check Contextual Glossary

Play Videoclips

View Still Images

Find out Film Data

<<RQ-04>>

<<RQ-05>>

<<RQ-06>>

<<RQ-07>>

Film Data Navigation Use Case Model

•Film Database Administration

- Administrators manages Clients and Data managers

- Film Database Maintenance

Illustration to Film Database Administration

Manages Memebership of Clients and Managers

Administrator

<<RQ-08>> Check Film Data Consistency

Backup Database

Restore Database

Maintain Film Database

<<RQ-09>>

Asia Film Database Administration Use Case Model

Quality Attribute Requirements

Usability Performance Dependability/Fault-Tolerance Security Compatibility

• Usability

– Ease of learning– Ease of use– Online Help

• Performance

– Fast response time

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

– WorkloadFilm data Volume: 2000 films/year, 200 films/month, …

• Dependability/Fault-Tolerance

– Availability (24hrs/day) – Reliability (authoritative)

• Security

– Privacy

Different levels of security– Integrity

Film data resources, multi-languages – Audit

Keep track of film data changing, clients...

• Compatibility

– Political Correctness

Clients be responsible for data entry– Legality

copyrights...

System Interface Requirements

User Interfaces (GUI)

Environment and Data Requirements

Operating Assumptions– Basic World Wide Web knowledge– Film Data Entry – WWW access– GUI Interface

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 (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 (continue) Packaging Requirements

– Installed on USC Unix server.

– Maintained by ISD

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

Project: Asian Film Database

Date: 11/10/98

Agenda (ssad)

Overview Component Model Behavior Model Enterprise Model System View Deployment View

Overview (ssad)

Entity ModelEntity Model Sys. ResponsibilitySys. Responsibility

1. Component Model1. Component Model 2. Behavior Model2. Behavior Model

3. Enterprise Model3. Enterprise Model

Object ModelObject Model Operation ModelOperation Model

Class ModelClass Model

From OCD

LCO Focus5. Deployment View5. Deployment View

4. Sys. Component view4. Sys. Component view

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 Diagram (2)

AFDBUser

Client

DataManager

FilmCatalog

FilmData

GlossaryContext

Manage & Retrieve

SystemAdministrator

Services

Provide Data

Manage Data

Manage & Uses

Look up

Maintain

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

Behavior Model (2) - Asian Film Data Management

Creat a new film data

Update Production DB

Verify new data correctness

Add a new Lang. Translatioon

Edit Existing film data

Reject new data

Client

(from Use Case View)

SystemUserVerification&Log

DataManager

Behavior Model (3) - Film Navigation

Select Display Language

Search Film Data

Go thru catalog

Display Film Data

Provide Glossary Context

Behavior Model (4) - AFDB System Administration

DB data M/A

SystemUserVerification&Log(from Use Case View)

Manage Sys. UserSysAdministrator

Enterprise Model(1) Component classification

SysUsr

Client Data Manager Sys. Adm

kind of kind of kind of

Film Data Film Catalog Glossary Context

Film Material

Enterprise Model(2) - Behavior Classification

Creat new data Verify new data Insert new data(Update prod. db) Reject Add Lang. Translation

Asian Film Data Management

Edit file data

Select display Lang. Display film data Provide glossary context Search film data

Asian Filem Data Navigation

Go thru Catalog

Manage sys. usrCollect modified data

AFDB sys. maintainence

Check DB consistency

System View

User Inferface

AFDB system

Database

Data management

Deployment View

Server

Web Browser

Client’s Computer

User’s Computer

Data Mgr.’s Computer

Digtlzd.Device

Asianfilm data

Digtlzd dvcSoftware

Web Server

HTML File- catalog- glossary- search interface- data m/a- data adm.

Database

Search Engine

HTML generator

Data editor

Data M/A

Sys. Adm.’s Computer

Asian Film Database — Life Cycle Plan

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 Navigation Data Input Data Management Database Administration Help and Support

Milestones and Schedules

Date ContentOct 19 W-W Negotiation; Initial

PrototypeOct 28 LCO DraftsNov 4 LCO PackageNov 9 LCO Package ARBDec 2 LCA DraftsDec 7 LCA Package ARBDec 14 Individual Critiques

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 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 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 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

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)

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.

Project Communication

Project Documents System DevelopmentDocuments

System Documents Others – ProjectManagementDocuments

OperationalConceptDescription

System andSoftwareRequirementDescription

System andSoftwareArchitectureDescription

Life Cycle Plan Feasibility

Rational

SoftwareDevelopment Files

Detail DesignSpec.

Test plan Test Description

and Results Inspection plan Inspection Reports Version

DescriptionDocuments

System Conf.Description

User Manual System

AdministratorManual

Application SourceCode (Hardcopy orSoftcopy)

Weekly MetricsReports

Meeting Minutes

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

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)

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)

To demonstrate from the following categories: Product Rationale Process Rationale Analysis Results

Product Rationale:Business Case Analysis

Development Cost Analysis– Developed by CS577b students

Implementation Cost Estimate– Training– Data preparation

Operational Cost Estimate– Employee of USC– Clients from different countries

Maintenance Cost Estimate– Essential devices– System Administrators

Product Rationale:Business Case Analysis

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 Satisfaction

Interface Requirements– Well-designed, user friendly, and simple

enough– Specific interfaces for:

• Data management Mode

• User Mode

• Administrator Mode

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 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

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

The main agreements are reached as follows: Schedule and cost AFDB operations Requirements Development strategy USC library operation

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

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

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

Off-the-shelf solutions– DBMS– Web page designer– Data digitizing software – Film scan software