eThens – A component-based framework for

E-governance

BITS, Pilani.

BITS C461 / IS C341Software Engineering

Project Presentation

What is E-Governance?

● Caution: Emerging concept ● Context: “fully electronified” government● Refers to a broad collection of functionalities● E-governance (interface) vs E-government

(infrastructure)

What is this framework about?

● Target Environment– Domain: E-governance – Users:

● Application (Software) Developers● (Software) Service Providers and Service

Integrators

What is this framework about?

● Functionality:– Support for Modeling and Design phases of Lifecycle

● Features:– Customizable, Fine-grained domain model– Extensible framework– Tools for Integration

Approach

● Layered framework –

– Production layer– Integration layer– Infrastructure layer

Production Layer

Integration Layer

Infrastructure Layer

Approach

● Domain Model

– Fine-grained Abstractions– Functions vs. Aspects– Hierarchy of domain elements– Extensible elements – subject to domain

constraints

Approach

● Operations on model elements

– Selection;– Instantiation;– Composition; – Extension; and– Validation

Production Layer

● Commodities – Information, Service● Modes of Provision – Exchange, Portal● Target user – Application Developer

Production Layer

● Uses – To produce

– Service Portal– Service Exchange– Information Portal– Information Exchange

Integration Layer

● Commodities – Service Elements– Information Fragments

● Target Users– Tool Developers – Service Integrators

Integration Layer

● Uses

– To compose service elements into a service (or information fragments into information)

– To extend existing service elements (or info. frags.)

– To resolve integration issues

Integration Layer

SP1 Production Layer

Integration Layer

Infrastructure Layer

Svc1 Info2

Info1Svc2

IP1

Integration Layer

● Composition Model

– Structure of Elements / Fragments– Flow / Sequencing– Interfaces and constraints– Access Control

Integration Layer

● Extension Model

– Add, Restrict, or Refine elements / fragments– Ensure integrity with existing infrastructure

Infrastructure Layer

● Commodities – Domain model (Functions and Aspects)

● Target User – Domain Expert(s)● Uses

– To support and enable E-governance framework(s).– To define Points of Service and Sources of

Information

Infrastructure Layer

● Hierarchy of functional domains – verticals● Domains provide

– Points of Service– Sources of Information

● Aspects (may be cross-domain)- Horizontals● Aspects provide

– attributes of services / info.

Infrastructure Layer

Production Layer

Integration Layer

Infrastructure Layer

Svc1Info2

Info1

Svc2

PoS2

SoI3PoS1

SoI2SoI1PoS3

Infrastructure Layer

● Top level (functional) domains (incomplete?)– Defense– Law & Order– Regulation & Controls– Welfare– Planning & Policies– Financing

Infrastructure Layer ● Domain Hierarchy: e.g. Welfare

– Infrastructure● Education● Transportation● Communication

– Ad-hoc

● Service Elements & Info. Fragments: e.g. Education

– List of Accredited Universities

– Accreditation / Evaluation

– Funding for Research projects

Infrastructure Layer

● Aspects (incomplete?)– Rules and Regulations– Authorities and Decision Making– Rights and Privileges– Hard Resources (e.g. Money)– Soft Resources (e.g. Records)– Socio-political conventions

Infrastructure Layer

Law

&

Order

Finances

Domains & Functions -->

Rules & Regulations

Rights & Privileges

Aspects

-->W

elfare

EDU.

Accreditation Evaluation List of Univ.

Trans.

PoS SoI

E-governance Framework Project Requirements

Build a vertical prototype -

1) Build a simple domain model

a) two or three functional subdomains

b) One cross-functional aspect

2) Build integration mechanisms

a. Selection of service points (functions)

b. Composition of service points

E-governance Framework Project

● Technology Requirements– UML for domain model– Java for development

● Technology Suggestions– Eclipse and plug-ins

E-governance Application Project

● Application– Emergency Tracking and Maintenance Portal

● Domain– E-governance

● (Ulterior) Motives– Useful product in an emerging domain– Feasibility Prototype for eThens– Identification of Service Integration Issues

E-governance Application Project

● Objective:– To build a single window services portal for

emergency tracking and management

● Features:– Services Portal– Single Window for a set of services– Composition of service elements into a service

E-governance Application Project

● Application Domain Description

– Emergencies (Public and large-scale) Natural Disasters (Earthquake, Floods) Epidemics (Cholera breakout, SARS) Accidents (Railway accidents, Flight Crashes) Social Volatility (Terrorist attacks, Communal

Violence)

E-governance Application Project

● Application Domain Description

– Primary Services● Tracking and Management of Emergencies

– Service Users● Citizens● Businesses and Non-profit organizations● Government agencies

E-governance Application Project

– Service Providers● Government Agencies

– Requirements● three layer approach● Web-enabled portal● Status tracking● Resource mobilization

E-governance Application Project

● Layer(s) Details– Services Layer supports single window for many

services– Integration Layer enables composition of service

elements into service.– Infrastructure Layer enables service elements

(This layer could be simulated with wrappers for data).

E-governance Application Project

● Required Technologies– Java based web tier and back end.

● Recommended Technologies– IBM WebSphere Development Environment

OR– Eclipse