Building Content Management System using Ruby on Rails.

1. June 2, 2016 | Higher Institute of Computer Science
Content Management
System
Development of
GraduationProject
Zied ELATI
Realised By
Syrine BEN MESKINA
Academic Superviser
Brahim DAHMANI
Professional Supervisor
Jury President
Riadh ZAAFRANI
Project Supervisors

2. INTRODUCTION
Project Context
RequirementsSpecification
SoftwareDesign
ConclusionandPerspectives
Realisation
Presentation
This is the
Welcome
Planning

3. IINTRODUCTION &
PROJECT CONTEXT

4. WORKING FIELDS
Sales Partnerships Design
Marketing Growth Communications
Simple Concept
Founded in 2008

5. Problematic
- Technical staff to edit and update web
content
- Editing methods still not easy for novice
administrators
- Websites have to be maintained and
updated on a regular basis

6. Proposed
Solution
Pre-packaged
software used
to manage and
create websites

8. Deep Dive
Sprint Cycle

9. II
ANALYSIS &
REQUIREMENT
SPECIFICATION

10. Functional Requirements Non-Functional Requirements
RequirementsSpecification
Scalability
Flexibility &
Extendability
Interoperability
Security
Portability
Robustness
Multiple Content Types
Search Engine Optimized
Anthentication System
Settings
Easy Templating System
Users Management
Menu Manager
Content Auditing & Versionning
Tagging
Nested Categorization

11. ADMINISTRATOR
Author PublisherContributor
Manage everything
CMS
Roles

12. Global Use Case
Diagram

13. Content Management
Use Case Diagram

14. III
SOFTWARE
DESIGN

15. Rest
CMS
Architecture
Presentation Layer
Data Layer
Business Layer
The CMS architecture
follows a standard 3-tier
architecture as well as a
Model-View-Controller
architecture

16. MVC
Summary of the steps
/usersrequest
routingtoindexaction
pullsusersfromDB
retrieveallusers
returnuserstocontroller
capturingusers
renderpage
PassingHTMLtobrowser
Avisittotheuserindex
intermsofMVC
1
2
3
4
5
6
7
8

17. ManagePagesSequence Diagram

18. ManageUsersSequence Diagram

19. Global Class Diagram

20. Package Diagram

21. PROJECT
REALIZATION
WEBO
IV

22. UsedTechnologies

23. Project
Management

24. Best Practices used along the
development process
Convention over
configuration
Don't Repeat Yourselt
(DRY)
Fat Model Thin
Controller
Rules to ease up working
with the application
keep your code concise
and readable
speed up development.
There is a lot of code that
should be in some other
layer
Refactoring
Eliminates redundancy
Code duplication in
process is waste if it can
be automated.
There is a lot of code that
should be in some other
layer
Controller changes the
state of model layer, but it
is done by using a clear
API and without messing
with internal structures.

25. V
CONCLUSION &
PERSPECTIVES

26. Conclusion
Perspectives
- CMS marries power with simplicity,
- Concentrate on improving
performance or other attributes,
- Upgrade the efficiency
of our developed system and improve
its effectiveness.
- integrate larger and more
sophisticated templates to display
their content
- merge a pointing device gesture, such
as drag and drop.

27. Thank
YOU
For your attention
The End
つづく

28. Talk is cheap show me
the code.
Linus Torvalds
I ' M S T A R T I N G
W I T H T H I S
Q U O T E