1. Overview 1.1System overview Web Information System (WIS) aims at maintaining an online collection of information related to college.

This system is intended for providing the user a systematic platform for publishing and reading articles, for posting updates related to different domain. Also provides a provision for asking queries hence enabling the user to get the solutions or suggestions easily from other users of the system. Alerts about some important upcoming events can be provided to the user. 1.2 System context The user i.e. involving registered users and administrator form the major sink and major source of information /data. The database of WIS also acts as a source and sinks where the data is stored and retrieved when required. 1.3 Stakeholders of WIS: The main stakeholders of the system are the registered users, the administrators and the designer of the system. The main concerns: For users: The way the update, article, query information is organized. Interface of the system, Response time is the major concern. Administrator: The maintenance of the system should be easy. Should be able to make any possible privileged changes to the system. Should have access to the files not accessible for other users and having privileges to make changes to the data content in those restricted files. For designer : The system is easy to incorporate changes in the future like adding of another service. The content to be loaded when a service is requested should be minimum. Hence, the architecture is to be evaluated for features like security, access rights, modularity, scalability and reusability. 1.4 scope of this document: In this document aims at providing the details related to possible architectures for WIS, based on the quality attributes of these architectures we compare them to find the most suitable architecture for WIS. The set of architectural properties of WIS architecture includes all properties that derive from the selection and arrangement of components, connectors, and data within the System is described in the document.

adding some

details is remaining
1.5 definitions and acronyms: Definitions: Security: A method of using password and username for authentication of the user. Component: Is an abstract unit of software instructions and internal state that provides a transformation of data via its interface. A connector: Is an abstract mechanism that mediates communication, coordination, or cooperation among components. A datum (data) : is an element of information that is transferred from a component, or received by a component, via a connector. An architectural style: is a coordinated set of architectural constraints that restricts the roles/features of architectural elements and the allowed relationships among those elements within any architecture that conforms to that style. Scalability: refers to the ability of the architecture to support large numbers of components, or interactions among components, within an active configuration. Acronyms: WIS Web Information System.

2 Architecture Design:
2.1. Architecture 1: The Repository Model

This architecture consists of data repository

which contains login information of administrator and user, collection of articles , updates, queries and their solutions posted by the users. It also gives some information such as modification of data repositories by various users and administrator. If any new books are added to the library, then this is also reflected in data repository. The following table gives some important components of architecture.

# nt 1

Compone Data Repository

Componen t type e

Description

Databas This module is the database containing information such as user profile , articles, updates, library info and query. This module aims at providing the registration procedure. Also checks if similar user name exist. This module enables administrator to provide user the access rights to the services of the WIS. This module inserts article, update and query data to the data repository.

Registration

Processing (database modification, Insertion of data) Database access and modification

Add / remove user

Post updates, Processing articles, query (database and modification) suggestions

Get information

Processing (database access)

This module accesses the data repository and returns the requested data for display. Information related to articles, current updates, query info and library. This module computes the details like number of users, articles, updates using the data in data repository.

Get system Processing statistics (computation) (administrator only)

7 login

Processing(data This module deals with base access) the login process, by taking the user name and password as data from user and compares it with stored data, provides a user authentication step. Processing This is basically the (Interface Graphic User Interface Module) module which interacts with the users and makes appropriate calls to the other modules based on the requirements of the user.

control manager

Following are the connectors of the architecture:

Connect # or 1 R/W Connectors

Connector Type on

Descripti

Database This connector is access/modifica between the data tion repository and the modules 2 and 3. These represent access (R) or modification (W) of the data repository. Database access This connector is between the data repository and the modules 5, 6 and 7. This represents that the data access permission is granted i.e. reading the data is possible. This connector is between the data repository and the module 4.Data base modification is allowed i.e. insertion of data. This connector is between the control manager and modules2, 3, 4, 5 and 6.This shows invocation of these modules by the control manager to carry out certain required service requested.

2 Read only Connectors

3 Write only Connectors

Database modifications

4 Control Connectors

Module Invocation and interface control.

W only R/W Registration Data repository R/W R only Add/remove user R only Login R only

Add updates articles/query

Get information

Get system statistics

2.2. Architecture 2: The Access Layer Model (4 layered)

This architecture has 4 layers, the data repository layer, data access layer, business logic layer and user interface layer (representation layer). Data repository layer is the layer concerned with the data storage related to the WIS. For data storage and retrieval this layer should be accessed. Business logic layer is concerned with the modules of logic that are used for processing of the data related to the services provided by the WIS. Data access layer is concerned with the retrieval and modification of the data in data repository when requested by the business logic layer. Hence all the data modifications and retrieval is done via this layer. User interface layer /control layer/representation layer is concerned with the interaction with the user of WIS and invocation of the related module. Advantages of this system is that any modification to the system can be incorporated by making changes to any of the layer ,having no need to make changes to other layer.

Data repository

Core/ data Repository layer

Authentication / authorization

Store or Retrieve data

Data access layer

Login

Add/remove user

Registration

Get system statistics

Get information

Add updates articles/ query

Business logic layer

Presentation / outer user Interface layer Control manager

2.3. Comparing the Architectures

Here we compare the architectures with respect to various quality attributes.

Criteria Architecture 1 Modification in type of data repository

Architecture 2