System and Software Architecture Description 
Asian Film Database 
Team #3

Guang Yang -Team Leader/SSAD
Jingtao Sun -OCP
Hui Wang-SSRD
Tao Feng-Prototype
Xinhua Wei-LCP/FRD

11/2/1998
SSAD-LCO V1.0


 





































1. Introduction
    1.1 System Purpose
    1.2 Purpose of the System and Software Architecture Description Document
    1.3 Guidelines
          1.3.1 Standards (DoD, IEEE)
          1.3.2 Notation (UML)
          1.3.3 Naming Conventions
    1.4 References
2. Architectural Analysis
    2.1 Component Model
    2.2 Behavior Model
          2.2.1 Behavior list
          2.2.2 Behavior detail descriptions
    2.3 Enterprise Model
          2.3.1 Logical Component Classifications
          2.3.2 Logical Behavior Classifications
3. System Design
    3.1 Design Views
          3.1.1 Logical View
          3.1.2 System Component View
          3.1.3 Deployment View
   3.2 Object Model
          3.2.1 Detailed Component Specifications
         3.2.2 Object Specifications
    3.3 Operations Model
          3.3.1 Detailed behaviors
          3.3.2 Operation Specifications
    3.4 Class Model
    3.5 Data Model
4. Common Definition Language for System Analysis
    4.1 AFDB System
5. Common Definition Language for System Design
    5.1 Production Database
    5.2 Processing Database
    5.3 HTML Generator
    5.4 System Administrator
    5.5 Client
    5.6 Data Manager
    5.7 User
6. Appendix
    6.1 References
    6.2 Vendor documents

1. Introduction

The introduction focuses on identifying the system objective and document objective. And it will include some key reference to this document.

1.1 System Purpose

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:

1.2 Purpose of the System and Software Architecture Description Document (SSAD)

1.3 Guidelines

We utilize the following guidelines to work out this project documents:

1.3.1 Standards (DoD, IEEE)

[1] Visual Modeling With Rational ROSE and UML, Terry QUATRANI
[2] Guidelines for the LCO and LCA deliverables for MBASE (Center for Software Engineering, USC)

1.3.2 Notation (UML)

[1] Visual Modeling With Rational ROSE and UML, Terry QUATRANI

1.3.3 Naming Conventions

There will be some abbreviation for the key concept and in the document SSAD as following:

1.4 References

2. Architectural Analysis

In this section we intent to analysis and describe precisely what the system is.

2.1 Component Model

From the domain description in OCD 2.0, we identify several entities from the Entity Model (OCD 2.4). From above two documents, we summarize the possible components of the proposed system as following:
1. AFDB;
2. Film Catalog
3. Film Data
4. Glossary Context;
5. System Administrator;
6. Client;
7. Data Manager
8. User
 
 
Component: COM-01
Defining Quality: Mechanism that provide user and client access (browse, update, management) to the Asian film data
Name: AFDB
Attributes: 1. Name; 

2. Address; 

3. Staff;
Behaviors: 1. Receive user/client access; 

2. Maintain the Asian film data;
Relationships:
  1. user;
  2. Client;
  3. data manager;
  4. film catalog;
  5. film data;
  6. Glossary context;
  7. System Administrator
See figure below;
State Group:
Roles: {navigator; search engine; film data management system}
Constraints:
Dependency:
Candidate Key:
Cardinality:
Relates To: Entity E-01(AFDB) from Entity Model(OCD 2.4) 

wpe1.jpg (17976 bytes)


 
Component: COM-02
Defining Quality: Organization and relation between film list. 
Name: Film Catalog
Attributes: 1.Criteria; 

2. Number of film data record; 

3. Links to actual film data;
Behaviors: 1.Manage users' navigation path; 

2.Display Asian film data;
Relationships: 1.AFDB; 

2.Data manager; 

3.Film data; 

See figure below;
State Group:
Roles:
Constraints:
Dependency:
Candidate Key:
Cardinality:
Relates To: Part of Entity E-01(AFDB) from Entity Model(OCD 2.4)

wpe2.jpg (11326 bytes)


 
Component: COM-03
Defining Quality: Actual digitized film data record, including: text(max 4 copies for different language), multi-media data(image, video, etc); 
Name: Film Data
Attributes: 1.Title; 

2.Director; 

3.Actor; 

4.Production Date; 

5.Genre 

6.Language Type; 

7.Credits; 
Behaviors: 1.Store film data; 

2.Present film data;
Relationships: 1.AFDB; 

2.Client; 

3.Data manager; 

4.Film Catalog; 

See figure below;
State Group:
Roles:
Constraints:
Dependency:
Candidate Key:
Cardinality:
Relates To: Part of Entity E-01(AFDB) from Entity Model(OCD 2.4)

wpe3.jpg (12596 bytes)


 
Component: COM-04
Defining Quality: Glossary entries provide contextual information for people from different culture.
Name: Glossary Context
Attributes: 1.Entry Word; 

2.Explanation; 

3.Links to film data word;
Behaviors: 1.Provide Glossary Explanation; 

2.Link to Film Description;
Relationships: 1.AFDB; 

2.Data manager; 

3.Film data; 

See figure below;
State Group: 
Roles:
Constraints:
Dependency:
Candidate Key:
Cardinality:
Relates To: Part of Entity E-01(AFDB) from Entity Model(OCD 2.4)

wpe4.jpg (10887 bytes)


 
Component: COM-05
Defining Quality: Person responsible for system and data maintenance to AFDB
Name: System Administrator
Attributes: 1.Name; 

2.Email; 

3.Permission; 

4.ID&Password; 

5.Operation history;
Behaviors: 1.Collect system period update data; 

2.Monitor system usage statistics; 

3.System user control and management; 

4.Data maintenance 
Relationships: 1.AFDB; 

2.Data manager; 

3.Client; 

See figure below;
StateGroup:
Roles: {Database Administrator; System administrator; User Administrator}
Constraints:
Dependency:
Candidate Key:
Cardinality:
Relates To: Part of Entity E-01(AFDB) from Entity Model(OCD 2.4)

wpe5.jpg (12684 bytes)


 
Component: COM-06
Defining Quality: Organization or individual in charge of the film data providing.
Name: Client
Attributes: 1.Name; 

2.Email; 

3.Sys. ID & password; 

4.Permission; 

5.Operation History;
Behaviors: 1.Add new film data record; 

2.Check the status of document processing;
Relationships: 1.AFDB; 

2.Film data; 

See figure below;
State Group:
Roles:
Constraints:
Dependency:
Candidate Key:
Cardinality:
Relates To: Part of Entity E-01(AFDB) from Entity Model(OCD 2.4)

wpe6.jpg (10031 bytes)


 
Component: COM-07
Defining Quality: Person in charge of the management, structuring and update the film data;
Name: Data Manager
Attributes: 1.Name; 

2.Email; 

3.Sys. ID & password; 

4.Permission; 

5.Operation History;
Behaviors: 1.Create and manage film catalog; 

2.Check the new film data record; 

3.Update the production database with the verified new data; 

4.Reject the new data; 

5.Edit the film data; 

6.Browse and search the film data;
Relationships: 1.AFDB; 

2.Client; 

3.Film data; 

4.Film Catalog; 

See figure below;
State Group:
Roles:
Constraints:
Dependency:
Candidate Key:
Cardinality:
Relates To: Part of Entity E-01(AFDB) from Entity Model(OCD 2.4)

wpe7.jpg (16121 bytes)


 
Component: COM-08
Defining Quality: Public visitor to the AFDB;
Name: User
Attributes: 1.Sys. id & password; 

2.Operation Preference;
Behaviors: 1.Navigate the film list; 

2.Search interesting film data; 

3.Lookup the unclear glossary; 

4.View the film data;
Relationships: 1.AFDB; 

2.Film data; 

3.Film Catalog; 

4.Glossary Context; 

See figure below;
State Group: {Public user, member}
Roles:
Constraints:
Dependency:
Candidate Key:
Cardinality:
Relates To: Part of Entity E-01(AFDB) from Entity Model(OCD 2.4)

wpe8.jpg (17476 bytes)


 
 

2.2 Behavior Model

In the other project documents, they describes the system behavior in high-level. In this section, we decompose them and describe them precisely.

2.2.1 Behavior list

There are 3 subsystems in this AFDB system:
  1. Asian film data management
    2. Asian film data navigation     3. AFDB Administer

2.2.2 Behavior detail descriptions:

 
Behavior BH-01
Name: Create a new film data record
Trigger: Client click on the button "Add new film data record"
Description: Authorized client accesses the AFDB homepage, select the function "add new film data function" to create a new film data record. Client will input all the data, including text, and attach multi-media data file. Finally he can send this record to AFDB system, temporally store in the procession database, waiting for the data manager to verify and handle. 
Pre-condition(s): Client has logged in the AFDB system, and system has recorded the client's information, such as his system user id, operation time, etc.
Post-Condition(s): 1.The new data record will send to the AFDB processing database; 

2.The system will record the client's operation. And client can query his operation history and status later.
Input(s): 1.Film text data: title, director, actor, production date, etc; 

2.Multi-media data file name/path and corresponding type, including image, video, audio, etc.
Output(s): 1.A new record in AFDB processing database. 

2.A new entry of the processing record list. 
Exception(s): There should be some mandatory fields that client must input, like title, director, film type, etc. If missing, refuse client input and no further operation.
Relates to: System Responsibility 
Scenario: See figure below. 

wpeA.jpg (15667 bytes)

Behavior BH-02
Name: Verify the new data correctness
Trigger: Data manager click on the link "Verify New Data" in the new film data list
Description: Data manager can view all the input data of the new film. He can verify the text data correctness and the multi-media data type, avoid any meaningless or wrong data into the production database. 
Pre-condition(s): One of the new data records is opened or selected. 
Post-ondition(s):
Input(s):
Output(s):
Exception(s):
Relates to: System Responsibility
Scenario: See figure below. 

wpeB.jpg (17890 bytes)


 
Behavior BH-03
Name: Update the production database with the new data 
Trigger: Data manager clicks on the button "Update the AFDB" of the corresponding data record.
Description: After Data manager verify the correctness of the new film data record, he can update the production database with the new data record. System will log this operation and changing the status of the processing new data record. 
Pre-condition(s): 1.Data manager has logged in the AFDB system, and system has recorded  his information, such as system user id, operation time, etc. 

2.One processing record has been opened or selected. 
Post-Condition(s): 1.The new data record will send to the AFDB processing database; 

2.The system will record the client's operation. And client can query his operation history and status later.
Input(s):
Output(s): 1.A new record in AFDB production database. 

2.Modification on the processing new data record. 

3.Necessary modification on the HTML file film catalog
Exception(s): If the production database is not available in that time, the system will stop any operation avoid any inconsistency between the production and processing database.
Relates to: System Responsibility 
Scenario: See figure below. 

wpeC.jpg (16577 bytes)


 
Behavior BH-04
Name: Reject the wrong data with comments; 
Trigger: Client click on the button "Reject new film data record"
Description: After the data manager verify the new film data record, he can reject this processing data record if there is any errors. And he can add some comments for the reason why to reject. System will update the processing database with process status, and deleting the record. 
Pre-condition(s): 1.Data Manager has logged in the AFDB system, and system has recorded the data manager's information such as the system user id, operation time, etc. 

2.One processing record is opened and selected. 
Post-Condition(s): 1.The new data record will be deleted from the processing database. 

2.The system will log this operation and change the status of processing data record.
Input(s): Data manager should input the comments for the reason why to reject this record. 
Output(s): The "reject" status of the processing data record.
Exception(s):
Relates to: System Responsibility 
Scenario: See figure below. 

 

wpeD.jpg (19616 bytes)


 
Behavior BH-05
Name: Edit the contents of film data record
Trigger: Client click on the button "Edit film record"
Description: Authorized data manager can edit the current contents of the film data record in production data. 

1st step to locate the record through navigating or searching the record. 

2nd Step to edit the data contents, such as the text data, or add/delete the multi-media data items. 

3rd Step, system will update the corresponding HTML file, such catalog.
Pre-condition(s): Data Manager has logged in the AFDB system, and system has recorded his/her information, such as his system user id, operation time, etc.
Post-Condition(s):
  1. The corresponding data record will be changed.
  2. The relating HTML file will be modified. 
  3. Data manager's operation will be logged. 
Input(s):
  1. The new contents of the data item.
  2. The new multi-media data file. 
Output(s):
  1. A new-updated record in AFDB production database.
  2. A new entry in operation log.
Exception(s):
Relates to: System Responsibility 
Scenario: See figure below. 

wpeE.jpg (16424 bytes)


 
Behavior BH-06
Name: Add a new language translation to one film
Trigger: Client click on the button "Add new language translation"
Description: Authorized data manager can access the AFDB production database to add a new language translation record to a film data record. 
Pre-condition(s):
  1. Data manager has logged in the AFDB system, and system has recorded his/her information, such as system user id, operation time, etc.
  2. A film data record opened or selected. 
Post-Condition(s): The new language translation record will be added to the AFDB production database; 
Input(s): New language translation.
Output(s): A new translation record. 
Exception(s):
Relates to: System Responsibility 
Scenario: See figure below. 

wpeF.jpg (14893 bytes)


 
Behavior BH-07
Name: Select display language
Trigger: When users enter the AFDB homepage, system will display this page to let user select the preferred language. 
Description: Users can select their preferred language, and then system will display the corresponding language home page and text contents.
Pre-condition(s):
Post-Condition(s): System will record users' selection
Input(s): Language choice;
Output(s):
Exception(s):
Relates to: System Responsibility 
Scenario: See figure below. 

wpe10.jpg (16311 bytes)


 
Behavior BH-08
Name: Go through the film catalog
Trigger: Users click the catalog links
Description: Users can go through catalog by clicking the interesting topic. 
Pre-condition(s):
Post-Condition(s): System will go to next catalog location.
Input(s):
Output(s): The catalog list of next entry.
Exception(s):
Relates to: System Responsibility 
Scenario: See figure below. 

wpe11.jpg (15381 bytes)


 
Behavior BH-09
Name: Display the film data record
Trigger: Users click a film data entry
Description: Users can click the link of film data entry to see the detail information of this film. 
Pre-condition(s): A film data entry link be selected
Post-Condition(s):
Input(s):
Output(s):
Exception(s):
Relates to: System Responsibility 
Scenario: See figure below. 

wpe12.jpg (15675 bytes)


 
Behavior BH-10
Name: Provide Glossary Context
Trigger: User click the glossary context hyperlink
Description: Users can view the detail description of this glossary explanation by click the hyperlink, and a new navigator window will show the corresponding description.
Pre-condition(s): A film data be displayed
Post-Condition(s): A new navigator window will pop out to show the description
Input(s):
Output(s):
Exception(s):
Relates to: System Responsibility 
Scenario: See figure below. 

wpe13.jpg (10025 bytes)


 
Behavior BH-11
Name: Search film data
Trigger: User clicks the search engine icon.
Description: Users can search film data by generate a search with key words. And then system will display all the results satisfying the search criteria. 
Pre-condition(s):
Post-Condition(s): Display the results.
Input(s): 1. Key words 
2. Search type
Output(s): Satisfying results
Exception(s):
Relates to: System Responsibility 
Scenario: See figure below. 

wpe14.jpg (16426 bytes)


 
Behavior BH-12
Name: Manage system user account
Trigger: System administrator click the button "Manage System User account"
Description: System Administrator can manage system user account, including add users, defining privilege, etc. 
Pre-condition(s):
Post-Condition(s): Updated user account database.
Input(s):
  1. System user name
  2. Personal information;
  3. Privileged access;
Output(s): Updated user account record
Exception(s):
Relates to: System Responsibility 
Scenario: See figure below. 

 

wpe15.jpg (13817 bytes)


 
Behavior BH-13
Name: Collect the updated data in specified period
Trigger: System administrator click the button "Collect system data"
Description: System Administrator can find out the updated system data in a specified period, and then to make copy of all the data.
Pre-condition(s):
Post-Condition(s): System log this operation
Input(s):
  1. Start/end time;
  2. File path;
Output(s):
Exception(s):
Relates to: System Responsibility 
Scenario: See figure below. 

wpe16.jpg (14216 bytes)


 
Behavior BH-14
Name: Check data consistence
Trigger: System administrator click the button "Check data consistence"
Description: System Administrator can check the links between data record, Catalog and glossary context and find out the unmatched list of links. 
Pre-condition(s):
Post-Condition(s): System log this operation
Input(s):
  1. Start/end time;
  2. File path;
Output(s):
Exception(s):
Relates to: System Responsibility 
Scenario: See figure below. 

wpe17.jpg (17828 bytes)


 
 

2.3 Enterprise Model

With the Component Model and Behavioral Model, we can create the Enterprise Model mapping the behaviors to the different components whenever possible with some essential changes.

2.3.1 Logical Component Classifications

We can summary and create some super-component, that we can decrease the complexity of whole component model, and share some qualities and methods.

We create a component named "SysUsr", which is the super-component of the "system-user-like" classes - "Administrator", "Data Manager", "Client". Therefore, these components can be inherited from the "SysUsr" and share some deterministic qualities related to people, like name, email address, etc, and some basic methods, like new, delete, modify, log, etc.

We create a basic component "Film material", which is the super-component of all the film data related components - "Film data", "Catalog", "Glossary Context". Therefore, these components can be inherited from the "Film material" to share some basic behaviors and qualities related to the "Film Material", like create, delete, check consistency, etc.
 

wpe18.jpg (24303 bytes)


 

2.3.2 Logical Behavior Classifications

We can group the system behavior in 3 classifications:
  1. film navigation;
  2. film data management;
  3. system maintenance;
You can see the detail classifications in following diagram.

wpe19.jpg (25190 bytes)


 







3. System Design

After preceding analysis and description, we can work out the whole images of the entire system and detail implementation specification for next step coding.

3.1 Design Views

In this section, we will present the entire image for the AFDB system in logical, system component and deployment views.

3.1.1 Logical View

This view of architecture addresses the functional requirements of the system ‿what the system should provide in terms of services to users.

3.1.2 System Component View

The System Component View concerns itself with the actual software/hardware/network module organization within the development and the production environment.

wpe1A.jpg (13428 bytes)


 




Mapping of the logical packages to component packages:
 
 

Component Package
Logical Packages
Interface HTML files, including: 
  • Catalog,
  • glossary context
  • search interface
AFDB system Hardware (Unix) Server
Database Commercial database system, whose contents including: 

- Production Database, 

- processing database
Data management application Data navigation and display application; 

Data management application; 

System maintenance application;

3.1.3 Deployment View

This view of architecture involves mapping software to processing nodes - it shows the configuration of run-time processing elements and the software processes living in them.

3.2 Object Model

The object model is a refinement of the Component Model (SSAD 2.1), and more applicable for further implementation.

3.2.1 Detailed Component Specifications

With the components that come from the entity model, we still need to add some new components to make the system realizable and less complicated.
 
 
Component:
Defining Quality:
Name:
Attributes:
Behaviors:
Relationships:
State Group:
Roles:
Constraints:
Dependency:
Candidate Key:
Cardinality:
Relates To:

3.2.2 Object Specifications

According to the component model with domain description, we can identify the following objects:
 
 
Object: OBJ-01
Name: User
Defining Quality The User's presence in the AFDB system is represented by the Web interfaces that allow user to navigate and search Asian film data. 
Variables or Attributes: Preferred Language
Operations: 1. Search 
2. Navigate
Outlets:
States:
Roles:
Constraints:
Component Membership
Implementation:
Relates to:
Object Interaction Diagram:
Object: OBJ-02
Name: SysUsr
Defining Quality The SysUsr presence in the AFDB system is represented by the Web interfaces that allow SysUsr to access system and has the authority to modify data.
Variables or Attributes:
  1. Name
  2. EmailAddress;
  3. OperationHistory;
  4. Location;
  5. Institute;
Operations:
  1. LogIn;
  2. New;
Outlets:
States:
Roles:
Constraints:
Component Membership
Implementation:
Relates to:
Object Interaction Diagram:
Object: OBJ-03
Name: DataMgr
Defining Quality The DataMgr presence in the AFDB system is represented by the Web interfaces that allow user to manage the production data and processing data 
Variables or Attributes:
  1. Perimission;
  2. OperationHistory;
Operations:
  1. VerifyNewData;
  2. RejectNewData;
  3. AcceptNewData;
  4. EditFilmData;
  5. EditFilmTranslation:
Outlets:
States:
Roles:
Constraints:
Component Membership
Implementation:
Relates to:
Object Interaction Diagram:
Object: OBJ-04
Name: Client
Defining Quality
Variables or Attributes:
Operations:
Outlets:
States:
Roles:
Constraints:
Component Membership
Implementation:
Relates to:
Object Interaction Diagram:
Object: OBJ-05
Name: Film
Defining Quality
Variables or Attributes:
Operations:
Outlets:
States:
Roles:
Constraints:
Component Membership
Implementation:
Relates to:
Object Interaction Diagram:
Object: OBJ-06
Name: FilmDataRecord
Defining Quality
Variables or Attributes:
Operations:
Outlets:
States:
Roles:
Constraints:
Component Membership
Implementation:
Relates to:
Object Interaction Diagram:
Object: OBJ-07
Name: GlossaryContext
Defining Quality
Variables or Attributes:
Operations:
Outlets:
States:
Roles:
Constraints:
Component Membership
Implementation:
Relates to:
Object Interaction Diagram:
Object: OBJ-08
Name: AFDB
Defining Quality
Variables or Attributes:
Operations:
Outlets:
States:
Roles:
Constraints:
Component Membership
Implementation:
Relates to:
Object Interaction Diagram:
Object: OBJ-09
Name: SearchEngine
Defining Quality
  1. Search Type;
  2. Search Tips;
Variables or Attributes:
Operations:
  1. Valid Input;
  2. Start search;
  3. Generate Search Result HTML list
Outlets:
States:
Roles:
Constraints:
Component Membership
Implementation:
Relates to:
Object Interaction Diagram:
Object: OBJ-10
Name: Navigator
Defining Quality
Variables or Attributes:
Operations:
Outlets:
States:
Roles:
Constraints:
Component Membership
Implementation:
Relates to:
Object Interaction Diagram:
Object: OBJ-11
Name: NewFilmDataManager
Defining Quality
Variables or Attributes:
Operations:
  1. CreateNewFilmRecord;
  2. CheckNewFilmRecordStatus;
  3. CehckNewFilmRecordHistoryOperation;
Outlets:
States:
Roles:
Constraints:
Component Membership
Implementation:
Relates to:
Object Interaction Diagram:
Object: OBJ-12
Name: Log
Defining Quality
Variables or Attributes: LogType;
Operations:
  1. MakeALog;
  2. ListLogList;
  3. SearchLogHistory;
Outlets:
States:
Roles:
Constraints:
Component Membership
Implementation:
Relates to:
Object Interaction Diagram:

3.3 Operations Model

The operation model is a refinement of the Behavior Model (SSAD 2.2)

3.3.1 Detailed behaviors

You can see the detail transactions between the objects in the behaviors.

          Asian film data management

  1. Create a film data record;
    1. Verify Client authorization;
    2. Display the data entry;
      1. Allow user to the input the text data in multi-language.
      2. Allow user to attach multi-media files;
      3. Add a new record in processing database
    Sequence Diagram as followed:


     



  2. Manage new film data;
    1. Verify Client authorization;
    2. Verify the new data consistency
      1. Data manager check the film text correctness;
      2. Data manager check the data format of multi-media data files.
      3. System will update the processing data record's status;
    3. Update the production database with the new data
      1. Update the production database;
      2. Update the processing data status;
      3. Delete the processing data record;
    4. Reject the wrong data with comments;
      1. Data manager input the comment for reason;
      2. Delete the processing data record;
      3. Update the processing data status;
    Sequence Diagram as followed: TBD
  3. Modify film data record;
    1. Edit the contents of film data record
      1. Input the modification;
      2. Update the production database;
      3. Check if there will be modification to HTML files
      4. If yes, then start HTML generator to modify Catalog, Glossary Context HTML files;
      Sequence Diagram as followed: TBD
    2. Add a new language translation to one film;
      1. Open a film data record;
      2. Input the new translation;
      3. Update the production database
      4. Check if there will be modification to HTML files
      5. If yes, then start HTML generator to modify Catalog, Glossary Context HTML files;
          Sequence Diagram as followed: TBD

          Asian film data navigation

  1. Navigate the film data through catalog;
    1. Select display language;
    2. Go through the film catalog
    3. Display the film data record
    4. Provide Glossary Context


    Sequence Diagram as followed: TBD
     

  2. Search interesting film data;
    1. Input the key word and select search strategy;
    2. Start search;
    3. Display result;


    Sequence Diagram as followed: TBD

    AFDB Administer

  1. Manage system user account;
    1. Add a SysUser account;
    2. Delete a SysUser account;
    3. Modify a SysUser account info;


    Sequence Diagram as followed: TBD
     

  2. Data Maintenance
    1. Collect the updated data in specified period
    2. Check the data consistence
          Sequence Diagram as followed: TBD

3.3.2 Operation Specifications

From the behavior model, we can identify the operations as listed:
  1. Verify SysUser validation;
  2. Allow user to the input the text data in multi-language.
  3. Allow user to attach multi-media files;
  4. Add a new record in processing database
  5. ...
The detail specifications are as followed:
 
Event: Verify SysUser Validation
Policy:
Passed Parameters
  1. SysUser ID, 
  2. password, 
  3. FunctionAccess, 
  4. LogTime, 
  5. LogLocation;
Return Values: Validation result
Exception handling:
Guards:
Validation
Messages:

Others are still TBD;

3.4 Class Model

Class model is a refinement of the Enterprise Model (SSAD 2.3). Starting from the enterprise model, we can summarize the detail for the further implementation.

3.5 Data Model

Data Model will describe the detail information for any of the following:
  1. Database structure;
  2. Data organization;
  3. File structure (for the temporary data file or HTML file)
  4. File and data cross reference;
The detail description and model diagram are still TBD.

4. Common Definition Language for System Analysis

In this section we will refer some key terms that are used the whole system analysis process.

4.1 AFDB System

This term refer to the Asian film database, the related application and other software/hardware components.

Other Terms are still TBD

5. Common Definition Language for System Design

In this section, we will explain some key terms that we use in the system design, some of them come from the domain word directly with adjustment to be more suitable and understandable for the developer.

5.1 Production database

This term refer to the database that stores all the production data,.

5.2 Processing database

This term refer to the database stores the new film data record, then the data managers can access this process database to verify the data correctness before finally update the production database.

5.3 HTML generator

This term refer to the application that can generate or modify the HTML file on the base customer's input and update.

5.4 System Administrator

The term refers to the person in charge of system maintenance.

5.5 Client

This term refers to the outside USC persons that provide film data to AFDB.

5.6 Data Manager

This term refers to the persons in charge of the data management in AFDB.

5.7 User

This term refers to the visitors that browse the film data in AFDB.

6. Appendix

6.1 Reference

[1] Visual Modeling With Rational ROSE and UML, Terry QUATRANI

[2] Guidelines for the LCO and LCA deliverables for MBASE (Center for Software Engineering, USC)

6.2 Vendor documents

Currently, customer has not decided yet to select which one commercial database system and other products. But we suppose to attach and refer some product descriptions here.