Architecture Review Board Project: Asian Film Database  Date: 11/10/98
Agenda <ul><li>1. Project Overview -  Solomon Yang(3 min) </li></ul><ul><li>2. OCD & prototype -  Jingtao Sun & Tao Feng (...
System Overview <ul><li>The Asian Film Database (AFDB) system is to create better awareness and understanding of Asian cin...
System Overview (conti.)
Project team <ul><li>Customer </li></ul><ul><ul><li>Karen Howell  </li></ul></ul><ul><ul><li>Robert Doiel  </li></ul></ul>...
Operational Concept Description(OCD) <ul><li>Introduction </li></ul><ul><li>Domain Description </li></ul><ul><li>System An...
Purpose of OCD <ul><li>Identify high-level objectives and scope </li></ul><ul><li>Describe domains of the proposed system ...
Organization Background <ul><li>Cinema cultures </li></ul><ul><ul><li>China, India, Japan, Korea and Taiwan </li></ul></ul...
Organization Goals <ul><li>AFDB contain information for each of the cinema culture </li></ul><ul><li>Texts are available i...
Current System <ul><li>No official Asian Film Database  </li></ul><ul><li>Hard to obtain information of Asian Film </li></...
 
 
 
 
 
 
 
 
Organization Activity Model <ul><li>Film Data management  </li></ul><ul><li>Browse website of Asian Film Database </li></u...
Film Data Management  <ul><li>Creating a film Data Entry </li></ul><ul><li>Management of the new Film Data </li></ul><ul><...
 
Browse Website of AFDB  <ul><li>Choose language </li></ul><ul><li>Go through catalog </li></ul><ul><li>Search the database...
 
Database Administration  <ul><li>User account management </li></ul><ul><li>Data Maintenance  </li></ul><ul><li>Collect upd...
 
Statement of Purpose  <ul><li>Help the growth and development of Asian cinema industry </li></ul><ul><li>To encourage inte...
Project Goals <ul><li>A database accommodating Film Data </li></ul><ul><ul><li>Accommodate 10,000 film records </li></ul><...
Project Goals(cont’) <ul><li>Interface for data management </li></ul><ul><ul><li>Check data record </li></ul></ul><ul><ul>...
System Responsibilities <ul><li>Film Data Management </li></ul><ul><ul><li>Create Film Data entry </li></ul></ul><ul><ul><...
System Responsibilities(cont’) <ul><li>Database Administration </li></ul><ul><ul><li>User account management </li></ul></u...
System  Administration Administrator Backup Restore Block Diagram English Chinese Japanese Korean Search Engine Film Navig...
Stakeholders Hierarchy Users Other Countries Administrator UCS Manager Asian Film Database USC Library Developer (Team3) C...
System and Software Requirement Definition Asian Film Database
<ul><li>System Requirement </li></ul><ul><li>Quality Attribute Requirements </li></ul><ul><li>System Interface Requirement...
<ul><li>System Requirement </li></ul><ul><li>AFDB consists of three subsystems :   </li></ul><ul><li>Film Data Management ...
<ul><li>Film Data Management  </li></ul><ul><li>Film Data Entry:  clients to upload film data  </li></ul><ul><li>Film Data...
Illustration to Film Data Management
<ul><li>Film Data Navigation </li></ul><ul><li>Users choose language to view the film data </li></ul><ul><li>Users utilize...
<ul><li>Film Data Navigation   (continue) </li></ul><ul><li>Users use key words to search the film information of their in...
Illustration to Film Data Navigation
<ul><li>Film Database Administration </li></ul><ul><li>Administrators manages Clients and Data managers </li></ul><ul><li>...
Illustration to Film Database Administration
<ul><li>Quality Attribute Requirements </li></ul><ul><li>Usability </li></ul><ul><li>Performance </li></ul><ul><li>Dependa...
<ul><li>Usability </li></ul><ul><ul><li>Ease of learning </li></ul></ul><ul><ul><li>Ease of use </li></ul></ul><ul><ul><li...
<ul><li>Performance </li></ul><ul><ul><li>Fast response time  </li></ul></ul><ul><ul><li>To load a web page within 20 seco...
<ul><li>Dependability/Fault-Tolerance </li></ul><ul><ul><li>Availability (24hrs/day)  </li></ul></ul><ul><ul><li>Reliabili...
<ul><li>Security </li></ul><ul><ul><li>Privacy </li></ul></ul><ul><ul><li>Different levels of  security </li></ul></ul><ul...
<ul><li>Compatibility </li></ul><ul><ul><li>Political Correctness </li></ul></ul><ul><ul><li>Clients be responsible for da...
<ul><li>System Interface   Requirements </li></ul><ul><li>User Interfaces (GUI) </li></ul>
<ul><li>Environment and Data    Requirements </li></ul><ul><li>Operating Assumptions </li></ul><ul><ul><li>Basic World Wid...
<ul><li>Environment and Data    Requirements  (continue) </li></ul><ul><li>Workload Characterization </li></ul><ul><ul><li...
<ul><li>Environment and Data    Requirements  (continue) </li></ul><ul><li>Design and Construction Constraints </li></ul><...
<ul><li>Environment and Data    Requirements  (continue) </li></ul><ul><li>Packaging Requirements </li></ul><ul><ul><li>In...
<ul><li>Evolution Requirements </li></ul><ul><li>Capability Evolution </li></ul><ul><ul><li>Make information available in ...
System and Software Architecture Definition Project: Asian Film Database Date: 11/10/98
Agenda (ssad) <ul><li>Overview  </li></ul><ul><li>Component Model </li></ul><ul><li>Behavior Model </li></ul><ul><li>Enter...
Overview (ssad) Entity Model Sys. Responsibility 1. Component Model 2. Behavior Model 3. Enterprise Model Object Model Ope...
Component Model (1) - Component List <ul><li>Entity Model </li></ul><ul><ul><li>AFDB </li></ul></ul><ul><ul><li>Client </l...
Component Diagram (2)
Behavior Model (1)  <ul><li>According to the system responsibility in OCD, we can summarize the following subgroup of syst...
Behavior Model (2) - Asian Film Data Management
Behavior Model (3) - Film Navigation
Behavior Model (4) - AFDB System Administration
Enterprise Model(1) Component classification
Enterprise Model(2) - Behavior Classification
System View
Deployment View Client’s Computer User’s Computer Data Mgr.’s Computer Asian film data Digtlzd dvc Software Sys. Adm.’s Co...
Asian Film Database — Life Cycle Plan
Overall Life Cycle Strategy <ul><li>Engineering Stage(CS577a) -- formulate operational concepts, requirement spec., arch.,...
Phases of the development of AFDB <ul><li>Navigation </li></ul><ul><li>Data Input </li></ul><ul><li>Data Management </li><...
Milestones and Schedules
Major stakeholders in the development <ul><li>Owner: USC - ISD </li></ul><ul><li>Developer: CS577 students </li></ul><ul><...
Stakeholders’ responsibility -- User <ul><li>Engineering Stage: -- Provide system requirement,  -- Define the operational ...
Stakeholders’ responsibility -- Developer <ul><li>Engineering Stage: -- prepare the system requirement, operational concep...
Stakeholders’ responsibility -- Customer <ul><li>Engineering stage -- monitor and evaluate the project progress -- help to...
Risk Management <ul><li>Unstable requirement -- c urrently there has no actual system, and a large part of requirements ar...
Risk Management (2) <ul><li>Schedule constraints -- the whole project should be completed by the end of spring semester in...
Project Communication
Quality Management <ul><li>One dedicated team member in project team who is in charge of performing the quality control. <...
Major Project Reviews  <ul><li>Architecture Review Board (1) </li></ul><ul><ul><li>overall content of the LCA package </li...
Major Project Reviews (2) <ul><li>Reviews/Inspections </li></ul><ul><ul><li>The team insures that each sub-module is teste...
Feasibility Rationale (Asian Film Database)   <ul><li>To demonstrate from the following categories: </li></ul><ul><li>Prod...
Product Rationale: Business Case Analysis <ul><li>Development Cost Analysis </li></ul><ul><ul><li>Developed by CS577b stud...
<ul><li>Operational Cost Estimate </li></ul><ul><ul><li>Employee of USC </li></ul></ul><ul><ul><li>Clients from different ...
Product Rationale: Requirements Satisfaction <ul><li>Capability Requirements </li></ul><ul><ul><li>Film data management </...
Product Rationale: Requirements Satisfaction <ul><li>Interface Requirements </li></ul><ul><ul><li>Well-designed, user frie...
<ul><li>Quality Requirements </li></ul><ul><ul><li>Usability: (easy to learn and use, help) </li></ul></ul><ul><ul><li>Per...
Product Rationale: Requirements Satisfaction <ul><li>Evolution Requirements </li></ul><ul><ul><li>Establish the mirror sit...
Product Rationale: Operational Concept Satisfaction <ul><li>User browse the website </li></ul><ul><ul><li>Mainstream Scena...
Product Rationale: Stakeholder Concurrence <ul><li>The main agreements are reached as follows:  </li></ul><ul><li>Schedule...
Process Rationale: System Priorities <ul><li>On database </li></ul><ul><ul><li>a database in USC </li></ul></ul><ul><ul><l...
Process Rationale: Process Match to System Priorities <ul><li>Spiral model and incremental development used. </li></ul><ul...
Process Rationale: Consistency of Priorities, Process  and resources <ul><li>Database design and construction (very high) ...
Analysis Results <ul><li>Off-the-shelf solutions </li></ul><ul><ul><li>DBMS </li></ul></ul><ul><ul><li>Web page designer <...
Upcoming SlideShare
Loading in …5
×

Architecture Review Board I Presentation

1,859 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,859
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Architecture Review Board I Presentation

  1. 1. Architecture Review Board Project: Asian Film Database Date: 11/10/98
  2. 2. Agenda <ul><li>1. Project Overview - Solomon Yang(3 min) </li></ul><ul><li>2. OCD & prototype - Jingtao Sun & Tao Feng (12 min) </li></ul><ul><li>3. Requirement - by Hui Wang (5 min) </li></ul><ul><li>4. Architecture - by Solomon Yang (5 min) </li></ul><ul><li>5. Project Plan - by Tao Feng (5 min) </li></ul><ul><li>6. Feasibility Rationale - by Xinhua Wei (5 min) </li></ul><ul><li>7. Discussion and comments (35 min) </li></ul><ul><li>8. Summary (5 min) </li></ul>
  3. 3. System Overview <ul><li>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: </li></ul><ul><ul><li>help the growth and development of the Asian cinema industry through effective marketing of Asian cinema within the region as well as internationally </li></ul></ul><ul><ul><li>encourage interaction and joint ventures with and among Asian cinema industry </li></ul></ul><ul><ul><li>enrich educational inputs for cinema and general education institutions </li></ul></ul>
  4. 4. System Overview (conti.)
  5. 5. Project team <ul><li>Customer </li></ul><ul><ul><li>Karen Howell </li></ul></ul><ul><ul><li>Robert Doiel </li></ul></ul><ul><li>Development team </li></ul><ul><ul><li>Solomon Yang Team Leader/SSAD </li></ul></ul><ul><ul><li>Jingtao Sun OCP </li></ul></ul><ul><ul><li>Hui Wang SSRD </li></ul></ul><ul><ul><li>Tao Feng Prototype </li></ul></ul><ul><ul><li>Xinhua Wei LCP/FRD </li></ul></ul>
  6. 6. Operational Concept Description(OCD) <ul><li>Introduction </li></ul><ul><li>Domain Description </li></ul><ul><li>System Analysis </li></ul><ul><li>Concept of Operation </li></ul>
  7. 7. Purpose of OCD <ul><li>Identify high-level objectives and scope </li></ul><ul><li>Describe domains of the proposed system </li></ul><ul><li>Identify operational scenarios and prototypes of interfaces </li></ul><ul><li>Clarify operational concepts </li></ul>
  8. 8. Organization Background <ul><li>Cinema cultures </li></ul><ul><ul><li>China, India, Japan, Korea and Taiwan </li></ul></ul><ul><li>Film industries of the cinema cultures </li></ul><ul><ul><li>From 10 to 800 films per year </li></ul></ul><ul><li>User of Asian Film Database Clarify </li></ul><ul><ul><li>Producers, directors, distributors, film critics, scholars, media as well as general public </li></ul></ul>
  9. 9. Organization Goals <ul><li>AFDB contain information for each of the cinema culture </li></ul><ul><li>Texts are available in English, Chinese, Japanese and Korean </li></ul><ul><li>User friendly and graphically user interface </li></ul><ul><li>Database management interface </li></ul>
  10. 10. Current System <ul><li>No official Asian Film Database </li></ul><ul><li>Hard to obtain information of Asian Film </li></ul><ul><li>Integrity of information is not guaranteed </li></ul><ul><li>Information is usually out of date </li></ul><ul><li>Prevents interaction among film industries </li></ul><ul><li>Prevents growth and development of Asian cinema industry </li></ul>
  11. 19. Organization Activity Model <ul><li>Film Data management </li></ul><ul><li>Browse website of Asian Film Database </li></ul><ul><li>Database Administration </li></ul>
  12. 20. Film Data Management <ul><li>Creating a film Data Entry </li></ul><ul><li>Management of the new Film Data </li></ul><ul><li>Modification of Film Data </li></ul>
  13. 22. Browse Website of AFDB <ul><li>Choose language </li></ul><ul><li>Go through catalog </li></ul><ul><li>Search the database </li></ul><ul><li>Display film data record </li></ul><ul><li>Look up glossary context </li></ul>
  14. 24. Database Administration <ul><li>User account management </li></ul><ul><li>Data Maintenance </li></ul><ul><li>Collect updated data </li></ul><ul><li>Checks data consistency </li></ul><ul><li>Backup/restore the Asian Film Database </li></ul>
  15. 26. Statement of Purpose <ul><li>Help the growth and development of Asian cinema industry </li></ul><ul><li>To encourage interaction and joint venture with and among Asian cinema industry </li></ul><ul><li>To enrich educational inputs for cinema and general education institutions </li></ul>
  16. 27. Project Goals <ul><li>A database accommodating Film Data </li></ul><ul><ul><li>Accommodate 10,000 film records </li></ul></ul><ul><ul><li>Texts are in four languages </li></ul></ul><ul><li>Friendly user-interface </li></ul><ul><ul><li>User may choose preferred language </li></ul></ul><ul><ul><li>User may browse website through catalog </li></ul></ul><ul><ul><li>User may search database </li></ul></ul><ul><ul><li>User may check context glossary </li></ul></ul>
  17. 28. Project Goals(cont’) <ul><li>Interface for data management </li></ul><ul><ul><li>Check data record </li></ul></ul><ul><ul><li>Modify data </li></ul></ul><ul><ul><li>Add/delete data </li></ul></ul><ul><ul><li>Data transmission </li></ul></ul><ul><li>Interface for database administration </li></ul><ul><ul><li>Update/restore database </li></ul></ul><ul><ul><li>Manage user accounts </li></ul></ul><ul><ul><li>Collect updated data </li></ul></ul>
  18. 29. System Responsibilities <ul><li>Film Data Management </li></ul><ul><ul><li>Create Film Data entry </li></ul></ul><ul><ul><li>Management of new film data </li></ul></ul><ul><ul><li>Modify existing film data </li></ul></ul><ul><li>Website navigation </li></ul><ul><ul><li>Data in multiple languages </li></ul></ul><ul><ul><li>Catalog for web browse </li></ul></ul><ul><ul><li>Search by key words </li></ul></ul><ul><ul><li>Glossary context </li></ul></ul><ul><ul><li>Display multimedia data </li></ul></ul>
  19. 30. System Responsibilities(cont’) <ul><li>Database Administration </li></ul><ul><ul><li>User account management </li></ul></ul><ul><ul><li>Data maintenance </li></ul></ul>
  20. 31. System Administration Administrator Backup Restore Block Diagram English Chinese Japanese Korean Search Engine Film Navigation Glossary Context Data Entry Data Edit 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: Provides data; Manager: Data Edit; Update;
  21. 32. Stakeholders Hierarchy Users Other Countries Administrator UCS Manager Asian Film Database USC Library Developer (Team3) CSCI577a USC Students USC Users USA Clients Users China India Taiwan Japan Korea
  22. 33. System and Software Requirement Definition Asian Film Database
  23. 34. <ul><li>System Requirement </li></ul><ul><li>Quality Attribute Requirements </li></ul><ul><li>System Interface Requirements </li></ul><ul><li>Environment and Data Requirements </li></ul><ul><li>Evolution Requirements </li></ul>
  24. 35. <ul><li>System Requirement </li></ul><ul><li>AFDB consists of three subsystems : </li></ul><ul><li>Film Data Management </li></ul><ul><li>Film Data Navigation </li></ul><ul><li>Asian Film Database Administration </li></ul>
  25. 36. <ul><li>Film Data Management </li></ul><ul><li>Film Data Entry: clients to upload film data </li></ul><ul><li>Film Data Management: data managers to manage film data. </li></ul>
  26. 37. Illustration to Film Data Management
  27. 38. <ul><li>Film Data Navigation </li></ul><ul><li>Users choose language to view the film data </li></ul><ul><li>Users utilize categories to browse the database website </li></ul>
  28. 39. <ul><li>Film Data Navigation (continue) </li></ul><ul><li>Users use key words to search the film information of their interests </li></ul><ul><li>Users can access multimedia film data </li></ul><ul><li>Users gets help from contextual glossary to understand film information </li></ul>
  29. 40. Illustration to Film Data Navigation
  30. 41. <ul><li>Film Database Administration </li></ul><ul><li>Administrators manages Clients and Data managers </li></ul><ul><li>Film Database Maintenance </li></ul>
  31. 42. Illustration to Film Database Administration
  32. 43. <ul><li>Quality Attribute Requirements </li></ul><ul><li>Usability </li></ul><ul><li>Performance </li></ul><ul><li>Dependability/Fault-Tolerance </li></ul><ul><li>Security </li></ul><ul><li>Compatibility </li></ul>
  33. 44. <ul><li>Usability </li></ul><ul><ul><li>Ease of learning </li></ul></ul><ul><ul><li>Ease of use </li></ul></ul><ul><ul><li>Online Help </li></ul></ul>
  34. 45. <ul><li>Performance </li></ul><ul><ul><li>Fast response time </li></ul></ul><ul><ul><li>To load a web page within 20 seconds (33.6k bps Modem) </li></ul></ul><ul><ul><li>Workload </li></ul></ul><ul><ul><li>Film data Volume: 2000 films/year, 200 films/month, … </li></ul></ul>
  35. 46. <ul><li>Dependability/Fault-Tolerance </li></ul><ul><ul><li>Availability (24hrs/day) </li></ul></ul><ul><ul><li>Reliability (authoritative) </li></ul></ul>
  36. 47. <ul><li>Security </li></ul><ul><ul><li>Privacy </li></ul></ul><ul><ul><li>Different levels of security </li></ul></ul><ul><ul><li>Integrity </li></ul></ul><ul><ul><li>Film data resources, multi-languages </li></ul></ul><ul><ul><li>Audit </li></ul></ul><ul><ul><li>Keep track of film data changing, clients... </li></ul></ul>
  37. 48. <ul><li>Compatibility </li></ul><ul><ul><li>Political Correctness </li></ul></ul><ul><ul><li>Clients be responsible for data entry </li></ul></ul><ul><ul><li>Legality </li></ul></ul><ul><ul><li>copyrights... </li></ul></ul>
  38. 49. <ul><li>System Interface Requirements </li></ul><ul><li>User Interfaces (GUI) </li></ul>
  39. 50. <ul><li>Environment and Data Requirements </li></ul><ul><li>Operating Assumptions </li></ul><ul><ul><li>Basic World Wide Web knowledge </li></ul></ul><ul><ul><li>Film Data Entry </li></ul></ul><ul><ul><li>WWW access </li></ul></ul><ul><ul><li>GUI Interface </li></ul></ul>
  40. 51. <ul><li>Environment and Data Requirements (continue) </li></ul><ul><li>Workload Characterization </li></ul><ul><ul><li>200 concurrent users </li></ul></ul><ul><li>Data Storage Characteristics </li></ul><ul><ul><li>Text + Images /per record = 500 KB </li></ul></ul><ul><ul><li>Total of 10k film records for 5 years </li></ul></ul><ul><ul><li>500K x 10K =5G KB </li></ul></ul><ul><ul><li>Estimated Storage = 200% x 5G = 10G </li></ul></ul>
  41. 52. <ul><li>Environment and Data Requirements (continue) </li></ul><ul><li>Design and Construction Constraints </li></ul><ul><ul><li>Hardware Requirements /Limitation </li></ul></ul><ul><ul><ul><li>AFDB shall be able to run with satisfactory performance on a Unix server </li></ul></ul></ul><ul><ul><ul><li>User may use PC, Mac, Unix,etc. with Internet connectivity. </li></ul></ul></ul><ul><ul><li>Software Requirements </li></ul></ul><ul><ul><ul><li>Server: Unix operating system </li></ul></ul></ul><ul><ul><ul><li>Users: Unix, Win95/98, Machitosh, Window NT 4.0 </li></ul></ul></ul><ul><ul><ul><li>Standard World Wide Web browser (e.g., Netscape Communicator 4.0 or Microsoft Internet Explorer 4.0 or later) </li></ul></ul></ul><ul><ul><ul><li>DBMS (IBM DB2) </li></ul></ul></ul>
  42. 53. <ul><li>Environment and Data Requirements (continue) </li></ul><ul><li>Packaging Requirements </li></ul><ul><ul><li>Installed on USC Unix server. </li></ul></ul><ul><ul><li>Maintained by ISD </li></ul></ul>
  43. 54. <ul><li>Evolution Requirements </li></ul><ul><li>Capability Evolution </li></ul><ul><ul><li>Make information available in other languages </li></ul></ul><ul><ul><li>Introduce more cinema cultures into database </li></ul></ul><ul><ul><li>establish mirror site in these cinema cultures to achieve fast Internet access </li></ul></ul><ul><ul><li>etc... </li></ul></ul>
  44. 55. System and Software Architecture Definition Project: Asian Film Database Date: 11/10/98
  45. 56. Agenda (ssad) <ul><li>Overview </li></ul><ul><li>Component Model </li></ul><ul><li>Behavior Model </li></ul><ul><li>Enterprise Model </li></ul><ul><li>System View </li></ul><ul><li>Deployment View </li></ul>
  46. 57. Overview (ssad) Entity Model Sys. Responsibility 1. Component Model 2. Behavior Model 3. Enterprise Model Object Model Operation Model Class Model From OCD LCO Focus 5. Deployment View 4. Sys. Component view
  47. 58. Component Model (1) - Component List <ul><li>Entity Model </li></ul><ul><ul><li>AFDB </li></ul></ul><ul><ul><li>Client </li></ul></ul><ul><ul><li>Manager </li></ul></ul><ul><ul><li>User </li></ul></ul><ul><ul><li>System Administrator </li></ul></ul><ul><ul><li>Film Data </li></ul></ul><ul><li>Component Model </li></ul><ul><ul><li>AFDB </li></ul></ul><ul><ul><li>Client </li></ul></ul><ul><ul><li>Data Manager </li></ul></ul><ul><ul><li>User </li></ul></ul><ul><ul><li>System Administrator </li></ul></ul><ul><ul><li>Film Catalog </li></ul></ul><ul><ul><li>Film Data </li></ul></ul><ul><ul><li>Glossary Context; </li></ul></ul>
  48. 59. Component Diagram (2)
  49. 60. Behavior Model (1) <ul><li>According to the system responsibility in OCD, we can summarize the following subgroup of system responsibilities: </li></ul><ul><ul><li>Asian Film Data Management </li></ul></ul><ul><ul><li>Asian Film Navigation </li></ul></ul><ul><ul><li>AFDB System Administration </li></ul></ul>
  50. 61. Behavior Model (2) - Asian Film Data Management
  51. 62. Behavior Model (3) - Film Navigation
  52. 63. Behavior Model (4) - AFDB System Administration
  53. 64. Enterprise Model(1) Component classification
  54. 65. Enterprise Model(2) - Behavior Classification
  55. 66. System View
  56. 67. Deployment View Client’s Computer User’s Computer Data Mgr.’s Computer Asian film data Digtlzd dvc Software Sys. Adm.’s Computer Internet Server Web Browser Web Browser Intranet(USC) Web Browser Web Browser Digtlzd. Device Web Server HTML File - catalog - glossary - search interface - data m/a - data adm. Database Search Engine HTML generator Data editor Data M/A
  57. 68. Asian Film Database — Life Cycle Plan
  58. 69. Overall Life Cycle Strategy <ul><li>Engineering Stage(CS577a) -- formulate operational concepts, requirement spec., arch., prototypes, life cycle plans, and integrate rationale for the proposed capabilities. </li></ul><ul><li>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 </li></ul><ul><li>Support Stage(USC ISD responsibility) </li></ul>
  59. 70. Phases of the development of AFDB <ul><li>Navigation </li></ul><ul><li>Data Input </li></ul><ul><li>Data Management </li></ul><ul><li>Database Administration </li></ul><ul><li>Help and Support </li></ul>
  60. 71. Milestones and Schedules
  61. 72. Major stakeholders in the development <ul><li>Owner: USC - ISD </li></ul><ul><li>Developer: CS577 students </li></ul><ul><li>User -- general public(web visitor) -- client -- Data Manager -- System Administrator </li></ul><ul><li>Customer: USC - ISD </li></ul>
  62. 73. Stakeholders’ responsibility -- User <ul><li>Engineering Stage: -- Provide system requirement, -- Define the operational concepts -- Prepare the operational plan </li></ul><ul><li>Production Stage: -- Review and test each increment in the development environment </li></ul><ul><li>Support Stage: -- Actual usage on the AFDB </li></ul>
  63. 74. Stakeholders’ responsibility -- Developer <ul><li>Engineering Stage: -- prepare the system requirement, operational concept, system architecture -- make a plan -- build a prototype according to the above </li></ul><ul><li>Production Stage: -- implement and integrate the product -- perform and support test </li></ul><ul><li>Support Stage: -- Provide administrative support to the product transition -- adapt the product to operate in different environment. </li></ul>
  64. 75. Stakeholders’ responsibility -- Customer <ul><li>Engineering stage -- monitor and evaluate the project progress -- help to supply test data and scenario for system development </li></ul><ul><li>Production stage -- review system performance </li></ul><ul><li>Support stage -- Provide administrative support to the product transition -- maintain the system usage </li></ul>
  65. 76. Risk Management <ul><li>Unstable requirement -- c urrently there has no actual system, and a large part of requirements are based on customer’s plan. -- design system incrementally and modulely. </li></ul><ul><li>User interface mismatch -- prototype may not meet the customer’s requirements -- frequently interact with customer and get their feedback </li></ul>
  66. 77. Risk Management (2) <ul><li>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 . </li></ul><ul><li>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. </li></ul><ul><li>Personal Shortfalls -- the project will be continued by the cs577b students. They need time to be familiar with cs577a students’ work. </li></ul>
  67. 78. Project Communication
  68. 79. Quality Management <ul><li>One dedicated team member in project team who is in charge of performing the quality control. </li></ul><ul><ul><li>develop documentation and coding standards </li></ul></ul><ul><ul><li>verify the compliance between the products and the documentation and coding standards </li></ul></ul><ul><ul><li>prepare test cases and produce test reports </li></ul></ul><ul><ul><li>not involved in the coding and development avoiding having any assumption and influence </li></ul></ul>
  69. 80. Major Project Reviews <ul><li>Architecture Review Board (1) </li></ul><ul><ul><li>overall content of the LCA package </li></ul></ul><ul><ul><li>make sure no other changes have occurred. If new elements have come out, they must be integrated at this time in the system. </li></ul></ul><ul><li>Architecture Review Board (2) </li></ul><ul><ul><li>The architecture designed, the developers have to make sure that they have not forgotten any requirements or import features. </li></ul></ul><ul><ul><li>All the risks have resolved. </li></ul></ul><ul><li>Architecture Review Board (3) </li></ul><ul><ul><li>must verity that no interface design errors have been made for any module of the system. </li></ul></ul><ul><ul><li>The review also checks that each individual module is well architected. </li></ul></ul>
  70. 81. Major Project Reviews (2) <ul><li>Reviews/Inspections </li></ul><ul><ul><li>The team insures that each sub-module is tested and meets all associated requirements. </li></ul></ul><ul><li>Transition Readiness Review </li></ul><ul><ul><li>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. </li></ul></ul><ul><li>Release Readiness Review </li></ul><ul><ul><li>It must verify that all stakholders are satisfied with the system acceptance test. Everything that is produced by the development team is accepted. </li></ul></ul><ul><ul><li>at the end of the implementation phase. </li></ul></ul>
  71. 82. Feasibility Rationale (Asian Film Database) <ul><li>To demonstrate from the following categories: </li></ul><ul><li>Product Rationale </li></ul><ul><li>Process Rationale </li></ul><ul><li>Analysis Results </li></ul>
  72. 83. Product Rationale: Business Case Analysis <ul><li>Development Cost Analysis </li></ul><ul><ul><li>Developed by CS577b students </li></ul></ul><ul><li>Implementation Cost Estimate </li></ul><ul><ul><li>Training </li></ul></ul><ul><ul><li>Data preparation </li></ul></ul>
  73. 84. <ul><li>Operational Cost Estimate </li></ul><ul><ul><li>Employee of USC </li></ul></ul><ul><ul><li>Clients from different countries </li></ul></ul><ul><li>Maintenance Cost Estimate </li></ul><ul><ul><li>Essential devices </li></ul></ul><ul><ul><li>System Administrators </li></ul></ul>Product Rationale: Business Case Analysis
  74. 85. Product Rationale: Requirements Satisfaction <ul><li>Capability Requirements </li></ul><ul><ul><li>Film data management </li></ul></ul><ul><ul><ul><li>Upload data by clients </li></ul></ul></ul><ul><ul><ul><li>Manage data by data managers </li></ul></ul></ul><ul><ul><li>Film data navigation </li></ul></ul><ul><ul><ul><li>Choose language, Browse the website, search films, and access multimedia data by users </li></ul></ul></ul><ul><ul><li>Database Administration </li></ul></ul><ul><ul><ul><li>Assign account for data managers and clients </li></ul></ul></ul><ul><ul><ul><li>Database maintenance </li></ul></ul></ul>
  75. 86. Product Rationale: Requirements Satisfaction <ul><li>Interface Requirements </li></ul><ul><ul><li>Well-designed, user friendly, and simple enough </li></ul></ul><ul><ul><li>Specific interfaces for: </li></ul></ul><ul><ul><ul><li>Data management Mode </li></ul></ul></ul><ul><ul><ul><li>User Mode </li></ul></ul></ul><ul><ul><ul><li>Administrator Mode </li></ul></ul></ul>
  76. 87. <ul><li>Quality Requirements </li></ul><ul><ul><li>Usability: (easy to learn and use, help) </li></ul></ul><ul><ul><li>Performance: (response time, bandwidth, workload) </li></ul></ul><ul><ul><li>Dependability/Fault-Tolerance: (reliability, availability) </li></ul></ul><ul><ul><li>Security: (privacy, integrity, audit) </li></ul></ul>Product Rationale: Requirements Satisfaction
  77. 88. Product Rationale: Requirements Satisfaction <ul><li>Evolution Requirements </li></ul><ul><ul><li>Establish the mirror sites </li></ul></ul><ul><ul><li>Extend number of clients </li></ul></ul><ul><ul><li>Extend participation to other cinema cultures </li></ul></ul><ul><ul><li>Proceed more business activities </li></ul></ul>
  78. 89. Product Rationale: Operational Concept Satisfaction <ul><li>User browse the website </li></ul><ul><ul><li>Mainstream Scenarios: Access, Display, navigate, etc.. </li></ul></ul><ul><ul><li>Variant Scenarios: Quick search, Super search </li></ul></ul><ul><li>Film data management and maintenance </li></ul><ul><ul><li>Client’s data entry: Login, create entry </li></ul></ul><ul><ul><li>Data management: Login, manipulate </li></ul></ul><ul><ul><li>Data Administration: login, maintenance </li></ul></ul>
  79. 90. Product Rationale: Stakeholder Concurrence <ul><li>The main agreements are reached as follows: </li></ul><ul><li>Schedule and cost </li></ul><ul><li>AFDB operations </li></ul><ul><li>Requirements </li></ul><ul><li>Development strategy </li></ul><ul><li>USC library operation </li></ul>
  80. 91. Process Rationale: System Priorities <ul><li>On database </li></ul><ul><ul><li>a database in USC </li></ul></ul><ul><ul><li>Film data from five countries in Asian </li></ul></ul><ul><li>On operation </li></ul><ul><ul><li>User: browse/download/navigate/search </li></ul></ul><ul><ul><li>Data manager: check/update/communicate </li></ul></ul><ul><ul><li>System administrator: maintain/collect/monitor/control </li></ul></ul><ul><ul><li>Client: create/transmit/check </li></ul></ul>
  81. 92. Process Rationale: Process Match to System Priorities <ul><li>Spiral model and incremental development used. </li></ul><ul><li>In CS577a: </li></ul><ul><ul><li>Formulate operational concepts, requirements specifications, architectures, prototypes, life cycle plans, and integrating rationale for the proposed capabilities. </li></ul></ul><ul><ul><li>In CS577b: </li></ul></ul><ul><ul><li>Develop Initial Operational Capability products with several increment steps </li></ul></ul>
  82. 93. Process Rationale: Consistency of Priorities, Process and resources <ul><li>Database design and construction (very high) </li></ul><ul><li>Film data collection (high) </li></ul><ul><li>Requisite software assemble and needed skill learning for CS577b (high) </li></ul><ul><li>Authorization to run on USC web sever (high) </li></ul>
  83. 94. Analysis Results <ul><li>Off-the-shelf solutions </li></ul><ul><ul><li>DBMS </li></ul></ul><ul><ul><li>Web page designer </li></ul></ul><ul><ul><li>Data digitizing software </li></ul></ul><ul><ul><li>Film scan software </li></ul></ul>

×