Museum Information System-ArchitecturalDesign

Museum Information System
Architectural Design
Presented to:
Dr. Shahriar Ameri
Prepared by Team1:
Claudia ARDELEANU claudia_ardeleanu@videotron.ca

Mohamed FARES m_fares@cs.concordia.ca
Liviu ISTRATE liviuistrate@hotmail.com
Oxana KHODAKOVSCAYA roxan49@hotmail.com
Pedro Maroun EID pedromeid@hotmail.com
Vu-Loc Brandon NGUYEN BNguyen@Microids.com
Page 1
Table of Contents
1. Introduction ........................................................................................ 3
2. System Design ................................................................................... 4
2.1 System Architecture ........................................................................ 4
3. User Interface Layer........................................................................... 6
3.1 Prototype ......................................................................................... 7
4. Business Layer................................................................................... 8
4.1 Class Diagram................................................................................. 8
4.2 Sequence Diagrams..................................................................... 9
4.3 State Diagrams .......................................................................... 18
5. Persistence Layer ............................................................................ 19
5.1 Database Assumption ................................................................... 19
5.2 Class Diagram for the persistence layer ....................................... 19
5.3 Data Model Diagram ..................................................................... 19
5.3 Database Schema......................................................................... 22
Page 2
1. Introduction
The Architectural Design document provides a high-level overview of the structural and
architecture of the entire system. Also the Architectural Design document provides a
more detailed description of the components of the system. Information is provided on
interactions and relationships among various sub-components of the system as well as
a detailed description of the pages corresponding to each function and each module.
The databases design is a list of everything a designer, programmer, or tester needs to
know to set up the database and to provide the connection between each function and
the database tables.
Page 3
2. System Design
The system includes the following subsystems:
Client: The client interacts with the system through a classic Windows interface. The
users will access the system in different ways depending on their privileges.
Server: The server is represented by the database server that stores the entire
information of the Museum system.
2.1 System Architecture

The system is design as an N-tier application that is divided into discrete logical parts:
user interface, business logic and data. In this model, processing is distributed between
the client and the server, and business logic is captured in a middle tier.
Tier (layer) Description

This layer comprises the entire user experience.
User interface Not only does this layer provide a graphical interface so that
and navigation users can interact with the application, input data, and view
-View the results of requests, it also manages the manipulation and
formatting of data once the client receives it.
The GUI will be a classic Windows interface implemented in
VC.
Between the interface and data services layers, this layer is

Business logic the domain of the application developer. Business logic,
-Model which captures the rules that govern application processing,
-Controller connects the user at one end with the data at the other.
The business rules mimic everyday business tasks, and can
be a single task or a series of tasks.
The business tier allows components to be written once and
reused multiple times to serve multiple clients and purposes.
The business tier is implemented by VC classes.
Data services Data services are provided by a structured data store, which
-Persistence manages and provides access to the application data.
layer Data services are provided by MS Access database
Page 4
GUI Controller Main DB

Engine Helper
DB_Museum
Figure. System component diagram for the Museum Information System
Page 5
3. User Interface Layer
The user interface class contains the code for the user interface part of an application
and is design as a Windows based application.
Main Page
Administrator User
Login
Museums Map Museums Map

Museums Museums
Items Items
Collection Collection
Select an option Select an option
*book *book
*simulation *simulation
*audio *audio
*computer *computer
Search Page Search Page
Update Page
Result on Page Result on Page
Figure UI flow diagram
Page 6
3.1 Prototype
To design a good interface we decided to create a first prototype that implements the
main functions of the system. The prototype will help us to receive feedback from the
customers and change in right of first stages of designing the GUI classes.
Page 7
4. Business Layer
4.1 Class Diagram
Page 8
4.2 Sequence Diagrams
4.2.1 Item
Create an item
- The administrator logs into the system

- The GUI creates an administrator controller
- The admin controller creates a session
- The session creates an item object based on the information provided by the
administrator.
- This item is manipulated in this session
- At the end, the changes are committed to the DB by the session
- The item object is destroyed
Controller DBHelper :
DBHelper
Sess ion : Ses s ion
CreateItem(ID, ...)
Exists(Integer)
CheckConsistency(LocationID, Type)
RecordRequest(Type, ID, ...)
Create Item which the

Administrator accesses
through all the layers after
loging in. It enables him to
create a new item.
Edit an Item
- Same operations as Creating an item

- The created session gets the data from DB for the corresponding item
- The session creates an item object based on that data
- This item is manipulated in this session
- At the end, the changes are committed to the DB by the commit command
Page 9
User Interface Controller DBHelper :

DBHelper
Ses sion : Ses sion
Edit() EditItem(const ID, ...)
Exists(ID)
Edit Item which only the

Administrator can access
edit an item.
CheckConsistency(LocationID, Type)

Record()
Delete an item
- Same operations as Editing an item

- The created session gets the data from DB for the corresponding item
- The session creates an item object based on that data
- This item is marked as deleted in this session
- At the end, the deletion is committed to the DB by the commit command to the
corresponding item.
DBHelper
Session : Session
DeleteItem(Const ID, Cause)

Exists(Integer)
Delete Item which the

Administrator accesses
delete an existing item.
Page 10
Committing to DB
- This command is used whenever the administrator or the system sees a need to
apply the changes made to the DB.
- The command comes from the controller through the session and to the DB
interface. Then, the interface is responsible to commit those changes physically.
DBHelper
MO_CItem : Ses s ion
Commit( )
The Confirmation Command to

apply all performed changes to
the DataBase. Used by
Aministrator.
Searching DB
- It is used by all users to check or fetch items or any objects existing in the DB.
- The user asks for a search on a given string; this string could be an id, a type, a
date, a part of the description, etc...
- All possibly needed search functions will be provided.
- After this command goes to the session, the session gets the information from
the DB interface and returns a response or search results to the user through the
controller and to his GUI.
Us er : General Us er Ses s ion : Ses s ion
Search()
Response()
The Search option which the

General User/Visitor can
access to retreive items.
Page 11
4.2.2 Collection
Create a collection
- The administrator login into the system

- The session creates a collection object based on the name provided by the
admin
- This collection is manipulated in this session
- The collection object is destroyed
UI Adm in : : D B Acce s s
Adm inis trato r
C O_C Adm in is trator
Log in()
createAdm in C n tl(pas s w o rd )
createS es s ion ( )
: Ses s ion
createC olle ction(N am e)

The C olle ction :
MO_ CC ol lec tion
return(The C ollectio n)
com m it('create', The colle ction )
des troy(The C olle ction )
Figure 1. Create Collection
Page 12
Update a collection

- The session gets the data from DB for the collection to be updated
- The session creates a collection object based on the information got from the DB
UI Admin : : DBAccess
Administrator
CO_CAdministrator
Login()
createAdminCntl(password)
createSession() : Session
getCollection(Name)
return(The Collection)
createCollection('update',Name)
The Collection :
CO_CCollection
commit('update', The Collection)
destroy(The Collection)
Figure 2. Update Collection
Page 13
Delete a collection

- The session gets the data from DB for the collection to be deleted
UI Admi n : : DBAcces s
Admini strator
CO_CAdministrator
Login()
createAd mi nCntl (pass word)
createSession()
: Session
getCollection(Name)
createCol lection('delete', Name)

The Collection :
CO_CCollection
commit('delete', The Collection)
destroy(The Collection)
Figure 3. Delete Collection
Page 14
4.2.3 Exhibition
Create an exhibition

- The session creates an exhibition object based on the name provided by the
admin
- This exhibition is manipulated in this session
- The exhibition object is destroyed
UI Adm in : : DBAcces s
Adm inis trator
CO_C Adm inis trator
Login()
createAdm inCntl(pas s word)
createSes s ion()
: Ses s ion
createExhibition(Nam e)
The Exhibition :
MO_CExhibition
return(The Exhibition)
com m it('create', The Exhibition)
des troy(The Exhibition)
Figure 4. Create Exhibition
Page 15
Update an exhibition

- The session gets the data from DB for the exhibition to be updated
- This exhibition is manipulated in this session
UI Admin :
Administrator : DBAccess
CO_CAdministrator
Login()
createAdminCntl(password)
createSession() : Session
getExhibition(Name)
createExhibition('update', Name)
The Exhibition :
MO_CExhibition
commit('update', The Exhibition)
destroy(The Exhibition)
Figure 5. Update Exhibition
Page 16
Delete an exhibition

- The session gets the data from DB for the exhibition to be deleted
- The session creates an exhibition object based on the information got from the
DB
UI Ad mi n : : DBAc cess
Adm inis trator
CO_CAdm inis trator
Lo gin()
createAdm inCntl(pas s word)
createSes s ion()
: Ses s ion
getExhibition(Nam e)
create Exhibition('delete', Nam e)

The Exhibition :
MO_CExhibition
com m it('delete', The Exhibition)
des troy(The Exhibition)
Figure 6. Delete Exbition
Page 17
4.3 State Diagrams
4.3.1 Collection state
On D is play
de s tr oy( )
Start
create()
mak eOn Di spl ay( ) End
Stored
Figure. Collection
4.3.2 Item state
Deleted
delete( )
delete()
com mi t()
Norm al ed it() Edited
Start
create()
com mi t()
com m it()
Com m itted
End
des troy()
Figure. Item
Page 18
5. Persistence Layer
5.1 Database Assumption
Based on the previous requirement analysis and characteristics of the Museum

Information System, we established some assumptions and constraints in order to
develop an abstract description of the data to be stored in the database. These
assumption and constraints are listed as follows:
A collection is a set of zero or many item. Items can be added to a collection
individually or following a rule.
An item can be part of zero or many collections
A collection can have zero or many items
An exhibition is a set of collections that are on display. An exhibition can be
composed by zero or many collections.
A collection can be displayed in zero or many exhibition.
An item which is on displayed has assigned only one room.
A book can have one or many authors.
5.2 Class Diagram for the persistence layer
In the persistence layer it will be only one class: DBHelper. The object of this class will
manage the connections for a user, and it will do all the operations on the database:
retrieve, insert, delete, and update. The objects of type DBHelper will only receive
messages from the class MO_CSession, which is on the MainEngine layer.
DBHelper
m_strConnection
m_vCollectionList
m_vItemList
m_vExhibitionList The DB_Helper objects
manage the operations on
OpenConnection() : String the database.
CloseConnection() : String
FindItem()
FindCollection()
FindRoom()
Commit() : String
CheckConsistency() : String
Figure. Class Diagram for the persistence layer
5.3 Data Model Diagram

The database design is described bellow in the data model diagram in two versions.
The first diagram gives only the table name and the relations between them, while the
second diagram fully lists all the field names.
Page 19
Figure. Data Model Diagram tables and relations
T_Simulation
<<Identifying>> <<PK>> PK_T_ItemCode()

1 <<FK>> FK_T_ItemCode()
T_Item
1
PK_T_ItemCode() <<Identifying>>
1
FK_T_RoomCode()
0..* 1 T_AudioVideo
1 1
1
<<Identifying>> <<PK>> PK_T_ItemCode()
<<Non-Identifying>> <<FK>> FK_T_ItemCode()
1
<<Identifying>>
T_Computer
<<Non-Identifying>>
<<PK>> PK_T_ItemCode()
1 <<FK>> FK_T_ItemCode()
1
T_Room
T_Book
<<PK>> PK_T_RoomID()
<<FK>> FK_T_ItemCode()
0..* 1
<<Non-Identifying>>
T_ItemCollection
<<FK>> FK_T_CollectionID() 0..*

<<FK>> FK_T_ItemCollection25()
<<Unique>> TC_T_ItemCodeCollectionID()
T_BookAuthor
0..*
<<FK>> FK_T_PersonID()
1 <<Unique>> TC_T_PersonIDItemCode()
0..*
T_Collection
<<Non-Identifying>>
<<PK>> PK_T_CollectionID()
<<Non-Identifying>> 1
0..* T_Person
<<PK>> PK_T_PersonID()
T_ExhibitionCollection
<<FK>> FK_T_CollectionID()
<<FK>> FK_T_ExhibitionID()
<<Unique>> TC_T_ExhibitionIDCollectionID()
0..*
<<Non-Identifying>>
T_UserAccount
1
T_Exhibition
<<PK>> PK_T_ExhibitionCode()
Page 20
T_Simulation
T_Item COL_SimultationOS : VARCHAR(50)
COL_ItemCode : VARCHAR(20) COL_ItemCode : VARCHAR(20)
COL_ItemName : VARCHAR(50) COL_SimultationGoalDescription : VARCHAR(2000)
COL_ItemCreationData : DATETIME <<Identifying>>
1
COL_ItemEntryDate : DATETIME <<PK>> PK_T_ItemCode()
COL_ItemOwner : VARCHAR(50) 1 <<FK>> FK_T_ItemCode()
COL_ItemDescription : VARCHAR(500)
COL_ItemType : VARCHAR(2)
<<Identifying>>
COL_ItemRegion : VARCHAR(50) 1
COL_RoomCode : VARCHAR(10) T_AudioVideo
COL_AudioVideoLength : SMALLINT
<<PK>> PK_T_ItemCode() 1
COL_AudioVideoFormat : VARCHAR(50)
<<FK>> FK_T_RoomCode() 1 COL_ItemCode : VARCHAR(20)
0..* 1 COL_AudioVideoDescription : VARCHAR(2000)
1 <<Identifying>>
1
T_Computer
COL_ItemCode : VARCHAR(20)
<<Identifying>> COL_ComputerModel : VARCHAR(20)
<<Non-Identifying>> COL_ComputerCompanyName : VARCHAR(50)
1
COL_ComputerHertz : SMALLINT
COL_ComputerRAM : SMALLINT
COL_ComputerMIPS : SMALLINT
T_Room COL_ComputerDescription : VARCHAR(2000)
COL_RoomCode : VARCHAR(10)
COL_RoomName : VARCHAR(50) <<PK>> PK_T_ItemCode()
COL_RoomFloor : VARCHAR(10) <<FK>> FK_T_ItemCode()
1
COL_RoomDescription : VARCHAR(2000)
COL_RoomSize : SMALLINT
<<PK>> PK_T_RoomID()
T_Book
0..* COL_ItemCode : VARCHAR(20)
COL_BookDescription : VARCHAR(2000)
COL_BookPublisher : VARCHAR(50)
T_ItemCollection
COL_CollectionID : SMALLINT 1
COL_ItemCode : VARCHAR(20) <<Non-Identifying>>
0..*
<<FK>> FK_T_ItemCollection25()
<<Unique>> TC_T_ItemCodeCollectionID()
T_BookAuthor
0..*
COL_ItemCode : VARCHAR(20)
<<Non-Identifying>> COL_PersonID : VARCHAR(20)
1
<<FK>> FK_T_PersonID()
T_Collection <<Unique>> TC_T_PersonIDItemCode()
COL_CollectionID : SMALLINT 0..*
<<Non-Identifying>>
COL_CollectionDescription : VARCHAR(2000)
COL_CollectionName : VARCHAR(100)
1
<<PK>> PK_T_CollectionID()
1 T_Person
<<Non-Identifying>> COL_PersonID : VARCHAR(20)
COL_PersonLastName : VARCHAR(50)
0..* COL_PersonBirthDate : DATETIME
COL_PersonFirstName : VARCHAR(50)
COL_PersonCurriculum : VARCHAR(2000)
T_ExhibitionCollection
COL_CollectionID : SMALLINT <<PK>> PK_T_PersonID()
COL_ExhibitionID : SMALLINT
<<FK>> FK_T_ExhibitionID()
<<Unique>> TC_T_ExhibitionIDCollectionID()
0..*
<<Non-Identifying>>
1
T_UserAccount
T_Exhibition
COL_ExhibitionID : SMALLINT
COL_ExhibitionStartDate : DATETIME
COL_ExhibitionEndDate : DATETIME
COL_ExhibitionDescription : VARCHAR(2000)
COL_ExhibitionName : VARCHAR(100)
<<PK>> PK_T_ExhibitionCode()
Figure Data Model Diagram fully developed database design
Page 21
5.3 Database Schema
The following database schema results from applying a forward engineering process on
the above data model diagram in Rational Rose. The database specification target is
Microsoft Access.
An exhibition can display one or more collections.

A collection can be displayed in different exhibitions in different periods.
CREATE TABLE S_Museum.T_ExhibitionCollection (
COL_CollectionID SMALLINT NOT NULL,
COL_ExhibitionID SMALLINT NOT NULL,
CONSTRAINT TC_T_ExhibitionIDCollectionID UNIQUE NONCLUSTERED
(COL_ExhibitionID, COL_CollectionID)
)
CREATE TABLE S_Museum.T_Room (

COL_RoomCode VARCHAR ( 10 ) NOT NULL,
COL_RoomName VARCHAR ( 50 ),
COL_RoomFloor VARCHAR ( 10 ) NOT NULL,
COL_RoomDescription VARCHAR ( 2000 ),
COL_RoomSize SMALLINT NOT NULL,
CONSTRAINT PK_T_RoomID PRIMARY KEY NONCLUSTERED
(COL_RoomCode)
)
A collection can have one or more items.

An item can be part of one or more collections.
CREATE TABLE S_Museum.T_ItemCollection (
COL_ItemCode VARCHAR ( 20 ) NOT NULL,
CONSTRAINT TC_T_ItemCodeCollectionID UNIQUE NONCLUSTERED
(COL_ItemCode, COL_CollectionID)
)
CREATE TABLE S_Museum.T_Collection (

COL_CollectionDescription VARCHAR ( 2000 ),
COL_CollectionName VARCHAR ( 100 ) NOT NULL,
CONSTRAINT PK_T_CollectionID PRIMARY KEY NONCLUSTERED
(COL_CollectionID)
)
CREATE TABLE S_Museum.T_Exhibition (
Page 22
COL_ExhibitionID SMALLINT NOT NULL,

COL_ExhibitionStartDate DATETIME,
COL_ExhibitionEndDate DATETIME,
COL_ExhibitionDescription VARCHAR ( 2000 ),
COL_ExhibitionName VARCHAR ( 100 ) NOT NULL,
CONSTRAINT PK_T_ExhibitionCode PRIMARY KEY NONCLUSTERED
(COL_ExhibitionID)
)
A person can be:

- an author of one/more books/software programs/audiovideo records/computers,
- the owner/member of a company
- the owner of an user account
- the owner of an item
CREATE TABLE S_Museum.T_Person (

COL_PersonID VARCHAR ( 20 ) NOT NULL,
COL_PersonLastName VARCHAR ( 50 ) NOT NULL,
COL_PersonBirthDate DATETIME,
COL_PersonFirstName VARCHAR ( 50 ),
COL_PersonCurriculum VARCHAR ( 2000 ),
CONSTRAINT PK_T_PersonID PRIMARY KEY NONCLUSTERED
(COL_PersonID)
)
Specific information about items of type book. This table can only be used together with
the T_Item table.
CREATE TABLE S_Museum.T_Book (
More detailed description of the book.
COL_BookDescription VARCHAR ( 2000 ),
COL_BookPublisher VARCHAR ( 50 ),
CONSTRAINT PK_T_ItemCode PRIMARY KEY NONCLUSTERED
(COL_ItemCode)
)
Intermediate table: link a book to one or more authors (person/company)

CREATE TABLE S_Museum.T_BookAuthor (
COL_PersonID VARCHAR ( 20 ) NOT NULL,
CONSTRAINT TC_T_PersonIDItemCode UNIQUE NONCLUSTERED
(COL_PersonID, COL_ItemCode)
)
CREATE TABLE S_Museum.T_Computer (

COL_ComputerModel VARCHAR ( 20 ),
Page 23
COL_ComputerCompanyName VARCHAR ( 50 ),
COL_ComputerHertz SMALLINT,
COL_ComputerRAM SMALLINT,
COL_ComputerMIPS SMALLINT,
COL_ComputerDescription VARCHAR ( 2000 ),
CONSTRAINT PK_T_Computer20 PRIMARY KEY NONCLUSTERED
(COL_ItemCode)
)
CREATE TABLE S_Museum.T_Simulation (

Operating System name
COL_SimultationOS VARCHAR ( 50 ),
COL_SimultationGoalDescription VARCHAR ( 2000 ),
CONSTRAINT PK_T_Simulation21 PRIMARY KEY NONCLUSTERED
(COL_ItemCode)
)
CREATE TABLE S_Museum.T_AudioVideo (

Minutes/Seconds
COL_AudioVideoLength SMALLINT NOT NULL,
Name of the audio/video format.
COL_AudioVideoFormat VARCHAR ( 50 ) NOT NULL,
COL_AudioVideoDescription VARCHAR ( 2000 ),
CONSTRAINT PK_T_AudioVideo22 PRIMARY KEY NONCLUSTERED
(COL_ItemCode)
)
Table of items of the museum. This table contains common information about items,
regardless of their type. Each specific item type has a separate table, linked by
ItemCode field.
CREATE TABLE S_Museum.T_Item (
COL_ItemName VARCHAR ( 50 ) NOT NULL,
The day the item was pubblicized
COL_ItemCreationData DATETIME NOT NULL,
The day the museum acquired or received the item.
COL_ItemEntryDate DATETIME NOT NULL,
Owner name. The owner can be a person, a group of people, or a company
(including the museum itself).
There is also a separate reference field to the owner table.
COL_ItemOwner VARCHAR ( 50 ) NOT NULL,
Short description of the item. A more complete description can be found in the
specific item tables.
COL_ItemDescription VARCHAR ( 500 ) NOT NULL,
BK - Books
SW - Software
CM - Computers
Page 24
AV - Audio Video
COL_ItemType VARCHAR ( 2 ) NOT NULL,
COL_ItemRegion VARCHAR ( 50 ) NOT NULL,
COL_RoomCode VARCHAR ( 10 ) NOT NULL,
CONSTRAINT PK_T_Item23 PRIMARY KEY NONCLUSTERED
(COL_ItemCode)
)
ALTER TABLE S_Museum.T_ExhibitionCollection ADD CONSTRAINT
FK_T_CollectionID FOREIGN KEY (COL_CollectionID) REFERENCES
S_Museum.T_Collection (COL_CollectionID)
ALTER TABLE S_Museum.T_ExhibitionCollection ADD CONSTRAINT

FK_T_ExhibitionID FOREIGN KEY (COL_ExhibitionID) REFERENCES
S_Museum.T_Exhibition (COL_ExhibitionID)
ALTER TABLE S_Museum.T_ItemCollection ADD CONSTRAINT

TC_T_ItemCollection212 FOREIGN KEY (COL_CollectionID) REFERENCES
S_Museum.T_Collection (COL_CollectionID)
ALTER TABLE S_Museum.T_ItemCollection ADD CONSTRAINT

FK_T_ItemCollection25 FOREIGN KEY (COL_ItemCode) REFERENCES
S_Museum.T_Item (COL_ItemCode)
ALTER TABLE S_Museum.T_Book ADD CONSTRAINT FK_T_ItemCode FOREIGN

KEY (COL_ItemCode) REFERENCES S_Museum.T_Item (COL_ItemCode)
ALTER TABLE S_Museum.T_BookAuthor ADD CONSTRAINT TC_T_BookAuthor213

FOREIGN KEY (COL_ItemCode) REFERENCES S_Museum.T_Book (COL_ItemCode)
ALTER TABLE S_Museum.T_BookAuthor ADD CONSTRAINT FK_T_PersonID

FOREIGN KEY (COL_PersonID) REFERENCES S_Museum.T_Person
(COL_PersonID)
ALTER TABLE S_Museum.T_Computer ADD CONSTRAINT TC_T_Computer214

FOREIGN KEY (COL_ItemCode) REFERENCES S_Museum.T_Item (COL_ItemCode)
ALTER TABLE S_Museum.T_Simulation ADD CONSTRAINT TC_T_Simulation215

ALTER TABLE S_Museum.T_AudioVideo ADD CONSTRAINT TC_T_AudioVideo216

ALTER TABLE S_Museum.T_Item ADD CONSTRAINT FK_T_RoomCode FOREIGN

KEY (COL_RoomCode) REFERENCES S_Museum.T_Room (COL_RoomCode)
Page 25

Museum Information System-ArchitecturalDesign

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Museum Information System-ArchitecturalDesign

Uploaded by

Copyright:

Available Formats

Museum Information System

Museum Information System

Dr. Shahriar Ameri

Claudia ARDELEANU claudia_ardeleanu@videotron.ca

2.1 System Architecture

Tier (layer) Description

Between the interface and data services layers, this layer is

GUI Controller Main DB

Figure. System component diagram for the Museum Information System

3. User Interface Layer

Museums Map Museums Map

Select an option Select an option

Search Page Search Page

Result on Page Result on Page

Figure UI flow diagram

4.2 Sequence Diagrams

- The administrator logs into the system

RecordRequest(Type, ID, ...)

Create Item which the

- Same operations as Creating an item

User Interface Controller DBHelper :

Edit() EditItem(const ID, ...)

Edit Item which only the

RecordRequest(Type, ID, ...)

- Same operations as Editing an item

DeleteItem(Const ID, Cause)

RecordRequest(Type, ID, ...)

Delete Item which the

The Confirmation Command to

Us er : General Us er Ses s ion : Ses s ion

The Search option which the

- The administrator login into the system

createC olle ction(N am e)

com m it('create', The colle ction )

des troy(The C olle ction )

Figure 1. Create Collection

- The administrator login into the system

commit('update', The Collection)

Figure 2. Update Collection

- The administrator login into the system

createCol lection('delete', Name)

commit('delete', The Collection)

Figure 3. Delete Collection

- The administrator login into the system

com m it('create', The Exhibition)

des troy(The Exhibition)

Figure 4. Create Exhibition

- The administrator login into the system

commit('update', The Exhibition)

Figure 5. Update Exhibition

- The administrator login into the system

create Exhibition('delete', Nam e)

com m it('delete', The Exhibition)

des troy(The Exhibition)

Figure 6. Delete Exbition

4.3 State Diagrams

4.3.1 Collection state

4.3.2 Item state

Based on the previous requirement analysis and characteristics of the Museum

5.2 Class Diagram for the persistence layer

Figure . Class Diagram for the persistence layer

5.3 Data Model Diagram

Figure . Data Model Diagram  tables and relations

Museums Map Museums Map

Figure. Class Diagram for the persistence layer

Figure. Data Model Diagram tables and relations

Figure Data Model Diagram fully developed database design