Note: Already filled information should not be changed

cavalcadehorehoundMechanics

Nov 5, 2013 (3 years and 11 months ago)

94 views

The Great Mind Challenge
-

Project Scenario Template


Note: Already filled information should not be changed


i.


Name of the Project

Automation of Civil Courts

1.


Objective/ Vision

Design a system for automating the judicial services in India

2.


Users of the S
ystem

1.

Court bureaucracy.

2.

Lawyers on both sides.

3.

Plaintiffs and defendants.

Restricted public information according to the prevailing laws


Data can be bilingual. It must be tagged accordingly. Spell
-
checks and
other data cleansing tools (to be suggested) a
re essential to ensure correct
handling by justice system


3.


Functional
Requirements

(Atleast Eight)

Court bureaucracy:

1.

File cases from plaintiffs.

2.

Schedule hearings (initial and continuing).

3.

Log proceedings.

4.

Give instructions to representing advocates. Al
l formal instructions
must be logged in the system. These instructions may be multi
-
lingual.

5.

Tag and archive proceedings after each hearing. Do “proper”
慲捨楶慬a慦a敲⁨ 慲楮i⁩猠so浰汥瑥l.


i慷y敲猺



c楬i⁣ 獥⁤整慩汳eon
-
汩l攮



䍨散欠敶楤敮捥 慮a⁣ 獥慤攠
by pos楮i⁰慲 y.



c楬i n⁥ 楤敮捥Ⱐ,楴n敳獥猠整挮



s慬ad慴攠捡獥⁰ro捥敤楮g猠snd t敳 慳⁴he礠灲潣敥d.



䍡獥 te猠浡礠扥⁦楬敤ebut pt⁳ 捵r攠end 獥cr整⁷楴h
慵ah敮e楣it楯i.



剥捥楶攠en獴牵捴楯i猠慮a v慬ad慴攠a敶敬潰浥mt献



剥灯rt⁡ t楯i⁴a步n.



剥捥楶攠e
orm慬a橵jg浥mt w楴h⁡畴h敮e楣it楯i⸠


P污lnt楦f猠snd⁤敦敮d慮a猺



乯⁥摩 楮i⁲楧it献



ln汹 敬e捴牯c楣i捯c浵ni捡t楯i⁷楴h⁲数牥s敮e楮i⁡摶o捡t攠
(without⁥浡楬).



s楥i楮i⁲楧it猠瑯⁳ 攠摥e敬潰浥mt ⁣ s敳 慮a⁩ 獴牵捴楯i猠
r散e楶敤e



剥捥楶攠捯cy 畤g敭ent献


Pub汩l⁶楥i:



An礠楮ior浡m楯i⁴h慴⁴h攠eudg攠ehoo獥s⁴o⁰ b汩lh 捡n⁢攠 on攠潮
th攠e敢獩e攠eg慩湳a⁴h攠e慳攮





䥮⁥獳敮捥㨠e敳楧i⁡⁳祳t敭†eh慴敶敲慧敳⁴ae⁡扩汩瑹f⁓t⁴o⁣潭p汥瑥ly
慵ao浡m攠瑨攠e楶楬udi捩cl⁳y獴敭⁡湤潧⁩瑳 敦e楣iency.

4.


Non
-
func
tional
requirements (Atleast
Four)

i.


Secure access of confidential data (user’s details). SSL can be
used.

ii.


24 X 7 availability

iii.

Better component design to get better performance at peak time

iv.

Flexible service based architecture will be highly desirable for
f
uture extension

5.


Optional features

None

6.


User interface
priorities

A. Professional look and feel

B. Use of AJAX atleast with all registration forms

C. Browser testing and support for IE, NN, Mozila, and Firefox.

D. Use of Graphical tool like JASPER to sh
ow strategic data to admin

E. Reports exportable in .XLS, .PDF or any other desirable format

7.


Reports

.Status reports of cases

8.


Other important issues

Detection and analysis of important data
-
elements to detect integrity of
case.


9.


Team Size

2


4 membe
rs

10.


Technologies to be
used

UML, J2EE, XML, e
-
Forms, AJAX, Web 2.0, Web
-
services, SOA

11.


Tools to be Used



ROSE/RSA / WebSphere Modeler



Eclipse/ RAD / Lotus Forms Designer / Portlet Factory



WebSphere Portal/ WAS/ WAS CE / WPS



DB2 Express


‘C’ or DB2 UDB



T
ivoli CDP/TSM / Tivoli Directory Server



Linux will be the preferred OS
.

12.


Final Deliverable must
include

A. Online or offline help to above said users, Application deployment
executive and developer

B. Application archive ( .war/.ear ) with source code

C.
Database backup and DDL Script

D. Complete Source code