The document is a design report for Project Okatu. It includes a Merise diagram modeling the different entities and their relationships. It also includes details of the database designed based on the Merise diagram, containing 22 entities. It then describes the classes diagram created to help design application classes. The report discusses the use of an ORM and concludes that C# and the .Net framework were chosen for implementation.

1. Project Okatu
Design Report
Client document
Project Manager: DA SILVA David
ANCIA Carole, CANIONCQ Régis, LEROY Elise, MILANI Mathias
07/02/2010

2. 7 février 2010 [DESIGN REPORT]
Table of content
Merise ............................................................................................................... 3
Database ........................................................................................................... 7
Classes Diagram ...............................................................................................11
ORM ................................................................................................................. 17
Implementation Choices ................................................................................ 18
Project Okatu | Design report 2

3. 7 février 2010 [DESIGN REPORT]
Merise
The follow diagram represents links between different entities of our
project.
It was created on the base of data dictionary and the comprehension of
subject.
This Merise diagram follows theses rules:
Project Okatu | Design report 3

4. 7 février 2010 [DESIGN REPORT]
Project Okatu | Design report 4

5. 7 février 2010 [DESIGN REPORT]
Project Okatu | Design report 5

6. 7 février 2010 [DESIGN REPORT]
Project Okatu | Design report 6

7. 7 février 2010 [DESIGN REPORT]
Project Okatu | Design report 7

8. 7 février 2010 [DESIGN REPORT]
Database
The translation of Merise has given the follow database,
composed of 22 entities and many attributes of data dictionary:
Project Okatu | Design report 8

9. 7 février 2010 [DESIGN REPORT]
Manga (manga_id, manga_title, manga_type, manga_volume_count,
manga_description, first_edition_date, first_edition_country, first_edition_editor,
editor_address, manga_lock, team_id#)
Stats (stats_id, seller_country, sale_number_country, manga_id#)
Chapter (chapter_id, chapter_name, chapter_number, chapter_description,
chapter_lock, manga_id#)
Edition (edition_id, edition_name, edition_description, first_edition_date_country,
legal_depot_month, legal_depot_year, edition_lock, manga_id#, language_id#)
Character_manga (manga_id#, character_id#)
Character (character_id, character_lastname, character_firstname,
character_gender)
Character_Caracteristic (character_id#, caracteristic_id#,
characteristic_value)
Caracteristic (characteristic_id, characteristic_name)
Character_Picture (character_id#, picture_id#)
Picture (picture_id, picture_page, picture_order, picture_color_type, picture_file,
picture_lock, picture_location, picture_origin_point, picture_mask_polygon,
resizing_factor, chapter_id#)
Page (page_id, page_mask_file, page_number, volume_id#)
Chapter_volume (chapter_id#, volume_id#)
Volume (volume_id, volume_title, volume_ISBN_number, volume_price,
volume_number, volume_description, volume_cover, volume_fly_cover, volume_lock,
sale_number_manga)
Volume_edition (volume_id#, edition_id#)
Language (language_id, language_name)
Script (script_id, script_file, script_original, script_lock, chapter_id#, language_id#)
Content_Text (script_id#, balloon_id#, text)
Project Okatu | Design report 9

10. 7 février 2010 [DESIGN REPORT]
Team (team_id, team_name)
Team_Function (person_id#, team_id#, function)
Person (person_id, person_lastname, person_firstname, person_alias,
person_password, person_nationality, person_address, person_phone_number,
person_mail)
Person_Skill (skill_id#, person_id#)
Skills (skill_id, skill_name)
Character_Baloon (character_id#, balloon_id#)
Balloon (balloon_id, balloon_type, balloon_order, balloon_origin_point,
balloon_mask_polygon, balloon_lock, picture_id#)
Project Okatu | Design report 10

11. 7 février 2010 [DESIGN REPORT]
Classes Diagram
We have continued by a design object in order to help us
creating classes for the future implementation.
We have used the classes diagram method which all steps are
detailed below.
Project Okatu | Design report 11

12. 7 février 2010 [DESIGN REPORT]
Project Okatu | Design report 12

13. 7 février 2010 [DESIGN REPORT]
Project Okatu | Design report 13

14. 7 février 2010 [DESIGN REPORT]
Project Okatu | Design report 14

15. 7 février 2010 [DESIGN REPORT]
Project Okatu | Design report 15

16. 7 février 2010 [DESIGN REPORT]
Project Okatu | Design report 16

17. 7 février 2010 [DESIGN REPORT]
ORM
Project Okatu | Design report 17

18. 7 février 2010 [DESIGN REPORT]
Implementation Choices
At the end of this design, we must now start thinking about the
implementation.
After many discussions between programmers and analysts, it seems that
the best choice is to use C# with the .Net framework.
If you have any questions or doubts, feel free to let us know before we
start the implementation.
We stay at your disposal for any further information.
Project Okatu | Design report 18