8/14/2019 Architecture for the Conference Management Portal

1/24

Architecture for the ConferenceManagement PortalGroup 17-Varun Varshney-Ronak Kogta

-Anil Verma-Veera Reddy-Yogendra Sao

8/14/2019 Architecture for the Conference Management Portal

2/24

8/14/2019 Architecture for the Conference Management Portal

3/24

tectural Drivers Based on Major Non Functional Require

8/14/2019 Architecture for the Conference Management Portal

4/24

8/14/2019 Architecture for the Conference Management Portal

5/24

8/14/2019 Architecture for the Conference Management Portal

6/24

Efficient and Stable Front-end.

hitectural Drivers Based on Major Functional Requireme

EnsuringExhaustive and complete registration

Efficient and Stable Front-end.

EnsuringSmooth and fair Paper submission & Review

8/14/2019 Architecture for the Conference Management Portal

7/24

Assumptions & Major Constraintsfor CMP

8/14/2019 Architecture for the Conference Management Portal

8/24

nces follow the same basic pattern. For eg: usage of the same basic templates.

All Components are web based.

ers requirements are completely fulfilled by the information provided.

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

ocess Constraints: Technologies used in different components should be compatible

Time Constraints : Deadlines for incremental developments should be met

8/14/2019 Architecture for the Conference Management Portal

9/24

ecisions related to major architectural strategies.

8/14/2019 Architecture for the Conference Management Portal

10/24

tated by Ajay He even planned to later add more functionalities such as accommodationings, vendor database management, volunteer management etc..

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

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

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

8/14/2019 Architecture for the Conference Management Portal

11/24

esses a fundamental structural organization schema for software systems.

implies certain system characteristics ,performance characteristics and process and distri

itectural style is needed.

CMP

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

database schema should ensure authorized access, crash recovery and efficient linking.

8/14/2019 Architecture for the Conference Management Portal

12/24

architecture should make sure that the User interface is neat ,clear and tidy.

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

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

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

quirement-Registration entails payment of registration fee which should be confidential a

8/14/2019 Architecture for the Conference Management Portal

13/24

Architectural Design for the CMP

8/14/2019 Architecture for the Conference Management Portal

14/24

User Interface(Front end)

Processing

Databases/Storage(Backend)

Conceptual Architecture

Logical Architecture(p.t.o)

8/14/2019 Architecture for the Conference Management Portal

15/24

xx

Client

(Web Browser-HTML/JavaScript)

Client(User Interface)(Web Browser-HTML,JavaScript,CSS)

Control Module(PHP)

Display /View InfoAuthentication

Send Email

Registration

Submit

Calculate amount

Payment

Printing Receipts

Paper Submission

Paper SubmissionUpdate Info

Paper Review

Submit DecisionDiscussion ForumList GenerationPaper Allocation

Forum Controller

Data Controller

DatabaseFile System

Application Tier

PresentationTier

Data Management Tier

Security Module

Error Handler

Paypal Email Component

HTTP

SMTP

HTTP HTTPHTTP

Data

Data Data Data Data DataFile

HTTPHTTP

HTTP

Data

JDBC/ODBC

8/14/2019 Architecture for the Conference Management Portal

16/24

Architectural Style

The three-tier Architecture :

Hybrid Architecture consisting of Three tier and Object Oriented Model

1 : Presentation Tier - User System Interface

Provides the User-Interface to the user .Built using Web Markup languages like HTML and CSSIs in accordance and in coordination with the Control Module of the Middle

2 : Application Implementation Tier Processing TierImplements Object Oriented Architecture

Processing Centre of the Complete ArchitectureHandling of Components like : ( Submit,List Generation,Paper Review etc.)

3 : Database Management Tier Database /StorageResponsible for the management of Databases and File Storage

8/14/2019 Architecture for the Conference Management Portal

17/24

Three Tier System + Object Oriented Model Why ?

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

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

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

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

By the three tier System :Database integrity more easily enforced.The Processing is centralizedAccess to resources based on names.Improves performance, flexibility, maintainability As the components

are of object type, changes can be made and seen easily.

8/14/2019 Architecture for the Conference Management Portal

18/24

By the Object Oriented Model

Data and operations are encapsulated in objects/abstract data types.Maintains data-integrity and hides data representationThe components communicate using Object instances.

Hence the above model :Provides Extensibility as the system is a set of independent agents.

Maintainability is ensuredReusability :Reuse of the same components by creating new Object instances .

8/14/2019 Architecture for the Conference Management Portal

19/24

Design Principles Used:

omposition :rocessing tier is divided into various functional components each serving a different purp

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

on Hiding :d Style ensures Information Hiding.

:can be revoked only by passing messages, therefore system will be very selective in passing

8/14/2019 Architecture for the Conference Management Portal

20/24

ependability between modules (should be low).

in our application are independent by their nature so coupling is kept low.tion Module possesses the coupling between User Authentication, Reviewer Authenticatio

functions within a module .(should be high)

porates cohesiveness between Admin Services & the Review Services. For e.g. Information

8/14/2019 Architecture for the Conference Management Portal

21/24

Modularity :

The combination of different sub functionalities to describe a major functionality.

In our model :For e.g. Payment Calculate amount and Printing receipts.

8/14/2019 Architecture for the Conference Management Portal

22/24

Suitable Style Structures:1) Three Tier Architecture:

The Processing is centralizedEnsures performance, flexibility , maintainability,reusability and scalability

2)Object Oriented Architecture:

Ensures modularity leading to independent components.Maintains Data Integrity and hides data representationMaintainability & extensibility

8/14/2019 Architecture for the Conference Management Portal

23/24

Unsuitable Style Structures

hich has various different processes like Paper Submission & Review , Registration and D

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

every node has some information to exchange

8/14/2019 Architecture for the Conference Management Portal

24/24

Thank You!