Architecture for the Conference

Management Portal
Group 17
-Varun Varshney
-Ronak Kogta
-Anil Verma
-Veera Reddy
-Yogendra Sao
 Architectural Drivers
(Major Functional & Non Functional )
for the CMP
(Conference Management Portal)
itectural Drivers Based on Major Non Functional Requirem
chitectural Drivers Based on Major Functional Requiremen

Efficient and Stable Front-end.

Ensuring
Exhaustive and complete registration

Ensuring
Efficient and Stable Front-end.
Smooth and fair Paper submission & Review
Assumptions & Major Constraints
for CMP
ences follow the same basic pattern. For eg: usage of the same basic templates.

All Components are web based.

ser’s requirements are completely fulfilled by the information provided.

nstraints : The budget constraints keeping in mind the moolah invested by all the stakeho

rocess Constraints: Technologies used in different components should be compatible

Time Constraints : Deadlines for incremental developments should be met

Decisions related to major architectural strategies.
stated by Ajay “He even planned to later add more functionalities such as accommodation
kings, vendor database management, volunteer management etc.”.

r the achievement of these goals, the system should be modular and easily extensible.

nce the architecture should facilitate addition of new service modules with ease.

g. Addition of Volunteer Management module should not affect other functions.

resses a fundamental structural organization schema for software systems.

n implies certain system characteristics ,performance characteristics and process and distrib

hitectural style is needed.

CMP

he architecture should entail efficient and correct entries into the database.

e database schema should ensure authorized access, crash recovery and efficient linking.
e architecture should make sure that the User interface is neat ,clear and tidy.

should contain sufficient information and at the same time it should not be crowded.

should allow easy simple modifications to take care of changing themes of the conferences.

ting web-based software systems like PayPal to ensure secure Registration.

equirement-Registration entails payment of registration fee which should be confidential an

Architectural Design for the CMP
Conceptual Architecture

User Interface(Front end)

Processing

Databases/Storage(Backend)

Logical Architecture(p.t.o)
 Client(User Interface)
Presentation
(Web Browser-HTML,JavaScript,CSS)
Tier
Application Tier HTTP
Client
xx
(Web Browser-HTML/JavaScript)
Control Module
Error Handler (PHP)
HTTP
HTTP HTTP
Registration Authentication Display /View Info
HTTP HTTP
HTTP
Paper Submission
Paper Review
Calculate amount
Paper Submission
Update Info List Generation
Paper Allocation
Payment Discussion Forum Submit Decision
Printing Receipts

Forum Controller
Submit
Data
File Data Data Data Data Data
Send Email
Data

SMTP
Security Module Data Controller

JDBC/ODBC

Paypal Email Component Data Management Tier

File System Database
 Architectural Style
Hybrid Architecture consisting of Three tier and Object Oriented Model

• The three-tier Architecture :

1 : Presentation Tier - User System Interface
•Provides the User-Interface to the user .
•Built using Web Markup languages like HTML and CSS
•Is in accordance and in coordination with the Control Module of the Middle T

2 : Application Implementation Tier –Processing Tier

•Implements Object Oriented Architecture
•Processing Centre of the Complete Architecture
•Handling of Components like : ( Submit,List Generation,Paper Review etc.)
•
3 : Database Management Tier – Database /Storage
•Responsible for the management of Databases and File Storage
•
Three Tier System + Object Oriented Model –Why ?

Scalability : This system provides stability in case of increase in number of users.

d the Object Oriented model help in addition of new functionalities(i.e.extendingthe system

mponents can be used by Conferences with different themes by re-using the same Middle T

Security : All the data updates take place through the Security module.

By the three tier System :

•Database integrity more easily enforced.
•The Processing is centralized
•Access to resources based on names.
Improves performance, flexibility, maintainability – As the components
are of object type, changes can be made and seen easily.
•
By the Object Oriented Model
•Data and operations are encapsulated in objects/abstract data types.
•Maintains data-integrity and hides data representation
•The components communicate using Object instances.
•
Hence the above model :
•Provides Extensibility as the system is a set of independent agents.
•Maintainability is ensured
•Reusability :Reuse of the same components by creating new Object instances .
 Design Principles Used:

composition :
Processing tier is divided into various functional components each serving a different purpo

ur model :
stration ,Authentication , Paper Submission ,Paper review.
stration is further divided into Payment ,Evaluate and Submit .etc.

ion Hiding :
d Style ensures Information Hiding.

l:
can be revoked only by passing messages, therefore system will be very selective in passing
dependability between modules (should be low).

s in our application are independent by their nature so coupling is kept low.

ation Module possesses the coupling between User Authentication, Reviewer Authentication

f functions within a module .(should be high)

rporates cohesiveness between Admin Services & the Review Services. For e.g. Information
Modularity :
The combination of different sub functionalities to describe a major functionality.

In our model :
For e.g. Payment Calculate amount and Printing receipts.
Suitable Style Structures:
1) Three Tier Architecture:

•The Processing is centralized

•Ensures performance, flexibility , maintainability,reusability and scalability

2)Object Oriented Architecture:

•Ensures modularity leading to independent components.

•Maintains Data Integrity and hides data representation
•Maintainability & extensibility
 Unsuitable Style Structures

which has various different processes like Paper Submission & Review , Registration and Di

oes not suit the demands of CMP because there is only one information exchange point i.

r every node has some information to exchange

Thank You!