Architecture Review Board

Document Sample
Architecture Review Board Powered By Docstoc
					Architecture Review Board

  Project: Asian Film Database

      Date: 11/10/98

 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
    – encourage interaction and joint ventures with and among Asian cinema
    – 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

                            Hosted by
Manager                                           Administrator

          Managed by                    Maintained by

                       Asian Film

            Serves                       Receives Film Data from


                       Film Data

                         Entity 01
                              Film Data
Asian Film

      Browses               Displays


                Entity 02

 Asian Film                                             Film Data
  Database                    Employed by

         Manages                            Maintains

Obtains privilidge from   Manager            Send request to

 Administrator                                           Client

                          Entity 03
Asian Film                           Film Data

     Maintain                     Backup/rest ore

                 Adminis trator
   Aut horizes                    Authorizes


                    Entity 04
Asian Film                                 Film Data

  Send Film Data to                   Creates

Obtains privilidge from                Communicates with

  Administrator                                  Manager

                          Entity 05
                     Asian Film

                Stored in

                      Film Data

Maintained by               Created by   Managed by

Administrator                                Manager

                    Entity 06
                                Asian Film


      Employs               Hosts


                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
Communicates with Client         Updates database         Rejects wrong data

                           Verifies consistency of new data

                  Creats Film Data Entry
                                                                      Translate text   Edit Film Data



                                           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     Views Images
                                                    Plays Video

                            Diaplays Film Data

   Goes through Catalog                          Searches Key Words

                            Choose Language


                   User Browses Asian Film Database
 Database Administration

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

Assigns memberships   Checkes data consistency    Back up database   Collects updated data

   Client             Manager                    Administrator

                            Database Administration
 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
                        Language: Chinese/Japanese/Korean/Chinese;
                        Query:    keywords;
                        Browser: Cinema culture, Title, Director, Actors….

                    English            Chinese       Japanese          Korean
                                                       Film Navigation
                       Search Engine
                                                      Glossary Context

                   Query: Keywords;
                                                              Catalog update
                   Result: Links

                                         Multimedia Archive
Client:                                                                                      Manager:
           Data                                                                       Data   Data Edit;
           Entry                                                                      Edit   Update;
                                                                  Data Edit:
                     Film Data:
                                                                  • text correction
                     • title;
                                                                  • different language.
                     • director;           Backup                 • Data viewing
                     • actor….             Restore                • update confirm
                     • Video clip
                     • film still...           System
                                          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 and Software
Requirement Definition
   Asian Film Database
System Requirement
Quality Attribute Requirements
System Interface Requirements
Environment and Data
Evolution Requirements
 System Requirement
AFDB 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

                Client                                       Assistant Manager to complete

                                                        Create Film                          Complete
                                                        Data Entry                           Translation
                            with Client
                                                                        <<RQ-02>>                          <<RQ-02>>
    Reject                                            <<RQ-01>>
   Film Data                              <<RQ-02>>


                                                                                                                 Film Database

                                                Check Film
                 <<RQ-02>>                      Data Integrity

  Film Data

                         Film Data Management Use Case Model
• Film Data Navigation
 - Users choose language to view the film data
 - Users utilize categories to browse the
   database website
• Film Data Navigation
 - 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

                          Browse Film Data
                          through Catalogue
                                                                                   Check Contextual

               <<RQ-04>>           <<RQ-04>>


  Choose Languge                              Find out Film Data

                   <<RQ-05>>                                                       Play Videoclips

                         Search Film Data
                           by Keywords
                                                                                     View Still Images

                               Film Data Navigation Use Case Model
•Film Database Administration

 - Administrators manages Clients and Data
 - Film Database Maintenance
Illustration to Film Database Administration

                      Manages Memebership of
                       Clients and Managers

                                                           Check Film Data


                                                                 Backup Database

                         Maintain Film

                                                                Restore Database

            Asia Film Database Administration Use Case Model
 Quality Attribute
   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)
 – Workload
   Film 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
 System Interface

 User Interfaces (GUI)
 Environment and Data
 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 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               Component Model
   – AFDB                     – AFDB
   – Client                   – Client
   – Manager                  – Data Manager
   – User                     – User
   – System Administrator     – System Administrator
   – Film Data                – Film Catalog
                              – Film Data
                              – Glossary Context;
Component Diagram (2)

     Client                                                        FilmCatalog

                  Services                     Manage & Uses

     User                         AFDB                              FilmData
                Provide Data                   Manage & Retrieve

                Manage Data                      Look up
  DataManager                                                        Glossary

Behavior Model (1)

 According to the system responsibility in OCD, we can
  summarize the following subgroup of system
   – Asian Film Data Management
   – Asian Film Navigation
   – AFDB System Administration
      Behavior Model (2) - Asian Film Data Management

                                                    (from Use Case View)

                       Creat a new film data
(from Use Case View)

                       Update Production DB

                                                     Verify new data correctness
                                                                                     (from Use Case View)

                          Reject new data

                                                     Add a new Lang. Translatioon

                                                           Edit Existing film data
 Behavior Model (3) - Film Navigation

                       Select Display Language

                            Search Film Data
       User                                        Display Film Data
(from Use Case View)

                             Go thru catalog

                                                 Provide Glossary Context
Behavior Model (4) - AFDB System Administration

                                    (from Use Case Vi ew)

                                   Manage Sys. User
       (from Use Case Vi ew)

                                        DB data M/A
Enterprise Model(1) Component classification

                  kind of      kind of      kind of

         Client             Data Manager              Sys. Adm           User


                            Film Material

      Film Data              Film Catalog             Glossary Context
Enterprise Model(2) - Behavior Classification

                                                   Asian Film Data Management

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

                                                    Asian Filem Data Navigation

    Select display Lang.         Go thru Catalog         Display film data   Provide glossary context        Search film data

                                                      AFDB sys. maintainence

                                                        Collect modified data
                     Manage sys. usr
                                                                                             Check DB consistency
System View

                    User Inferface

          Data      AFDB system

   Deployment View
                                                                       Web Server          Search Engine
                         User’s Computer
                                                                     HTML File
                                  Web                                - catalog            HTML generator
                                 Browser                             - glossary
                                                       Server        - search interface     Data editor
                                                                     - data m/a
                                                                     - data adm.
                                                                                             Data M/A


  Client’s Computer

 Device    Digtlzd dvc          Data Mgr.’s Computer            Sys. Adm.’s Computer
                                            Web                               Web
                                           Browser                           Browser
            film data
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
 Navigation
 Data Input
 Data Management
 Database Administration
 Help and Support
Milestones and Schedules
        Date Content
        Oct 19 W-W Negotiation; Initial
        Oct 28 LCO Drafts
        Nov 4 LCO Package
        Nov 9 LCO Package ARB
        Dec 2 LCA Drafts
        Dec 7 LCA Package ARB
        Dec 14 Individual Critiques
Major stakeholders in the
 Owner: USC - ISD
 Developer: CS577 students
 User
  -- general public(web visitor)
  -- client
  -- Data Manager
  -- System Administrator
 Customer: USC - ISD
Stakeholders’ responsibility --
 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 --
 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 --
 Engineering stage
  -- monitor and evaluate the project progress
  -- help to supply test data and scenario for system
 Production stage
  -- review system performance
 Support stage
  -- Provide administrative support to the product
  -- 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 Development System Documents           Others – Project
                    Documents                                     Management
 Operational        Software              System Conf.          Weekly Metrics
  Concept             Development Files      Description            Reports
  Description        Detail Design         User Manual           Meeting Minutes
 System and          Spec.                 System
  Software           Test plan              Administrator
  Requirement        Test Description       Manual
  Description         and Results           Application Source
 System and         Inspection plan        Code (Hardcopy or
  Software           Inspection Reports     Softcopy)
  Architecture       Version
  Description         Description
 Life Cycle Plan     Documents
 Feasibility
Quality Management
 One dedicated team member in project team
 who is in charge of performing the quality
  – 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

   – 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

 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

 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
       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
 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
   – 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,
  – Dependability/Fault-Tolerance: (reliability,
  – 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:
  – 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
  – 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

Shared By: