Project Scenario

greasyservantInternet and Web Development

Jul 30, 2012 (5 years and 3 months ago)

294 views

The Great Mind Challenge
-

Project Scenario




Note: Already filled information should not be changed


1.


Name of the Project


System Architect Tool

2.


Objective/ Vision


IBM Rational System Architect is a leading Enterprise
Architecture modeling product. It

helps CXO’s and Enterprise
Ar捨楴散t猠摥s楮攠慮a⁵ d敲獴慮d⁴h敩r⁣ rr敮e 獴慴攠潦
慲捨楴e捴cr攬e慮a⁰污 ⁦or th攠瑲en獦srm慴楯n ⁢ 獩湥獳⸠


py獴敭 Ar捨楴散t⁳異port猠sldAF 㤬9慮a慲捨楴散tur慬a
fr慭敷or欠摥k敬潰敤⁢y Th攠佰敮⁇roup⸠呏dAF 污y猠摯wn
愠捯
浢楮慴楯i ⁡r捨楴ectur慬a捯ct敮e⁡湤 捡p慢楬aty
fr慭敷or欬k慮a⁡r捨楴e捴ur攠摥e敬潰浥mt整hodo汯l楥i
EA䑍).


A䑍⁳畧ge獴猠sh攠e慰aur攠潦⁡ 䉡獥汩l攠Ar捨楴散tur攠
fo汬潷敤⁢y⁴h攠摥e敬潰m敮e ⁡ T慲g整⁡e捨楴散tur攠瑨慴⁷楬氠
浥整⁢ 獩湥獳 橥捴楶敳⸠.祳
t敭eAr捨楴散t 獵sport猠
d敶敬潰浥mt ⁂慳敬楮攠慮a⁔慲g整eAr捨楴e捴cr敳 楮⁤楦f敲敮e
wor欠kr敡s⁣ 汬ld⁗orksp慣敳.


TldAF A䑍⁳畧g敳t猠瑨慴⁴h攠条瀠e整e敥n⁂慳攠慮a⁔慲g整e
捨c獥n⁡r捨楴e捴cr慬a捯cpon敮e猠shou汤⁢攠ed敮e楦楥搠i數tⰠ
fo汬潷敤⁢y⁡ 浩mr慴楯n
p污港lo慤a慰⁡at敲 捯c獩s敲楮i⁴h攠
bu獩湥獳⁶慬a攠景r⁴h攠er捨楴散tur慬⁣潭pon敮e猬sr楳i猠
楮io汶敤⁡湤⁥ t業慴敤⁤ur慴楯n⸠.h攠eo慤a慰⁣潵汤⁦urth敲
b攠摲ev敮⁢y 敲a汬⁣onstr慩湴猠si步⁡汬潷慢汥⁐ea欠knnu慬a
獰敮d楮i⁣潳 Ⱐ整挮




啳敲猠潦⁴h攠e祳t敭



Ent敲
pr楳i Ar捨楴散ts



po汵l楯i Arc楴散ts



䉵獩湥s猠An慬祳t



Ad浩mi獴牡瑯r



g敮敲慬⁵獥rs




Fun捴楯n慬a
剥煵楲敭敮es

EAt汥慳t⁅楧it)

1) The primary objective of this project is to visualize a roadmap
for transitioning the architecture as mentioned above. This would
use the data from System Architect but display in a separate
interface.


2) A second (optional) objective is to allow updates to the
roadmap.


3)

The roadmap creation above would also be optionally
supported by a Gap Matrix across different workspaces. This
w
ould also be displayed in a separate interface.

4)

It should implement following
--

I.

The road
-
mapping utility should be invoked from System
Architect

II.

They should be able to view gap matrix with all the
Architecture Building Blocks (ABBs) of the Baseline
Archite
cture on the vertical axis, and all the ABBs of the
Target Architecture on the horizontal axis.

III.

In the matrix, they should be able specify if Target
Architecture is "New", ‘Included’ or ‘Eliminated’ with
respect to Baseline Architecture.

IV.

They should be ab
le to select initial Architectural roadmap
components from Work Packages in Target architecture,
for further consolidated, cross
-
discipline road
-
mapping.
This is typically done within the ADM Opportunities &
Solutions phase.

V.

They should be able to display
a roadmap for the
progression from the Baseline Architecture to the Target
Architecture along a timeline. The Architecture Roadmap
must demonstrate how the selection and timeline of
Transition Architectures and work packages realizes the
Target Architectur
e.

VI.

The roadmap should be displayed with appropriate
consideration of constraints like dependencies, costs, and
benefits.

5.


Non
-
functional
requirements (Atleast
Four)

i.

It should be built upon/driven by the System
Architect security mechanism.

ii.

Flexible archi
tecture that can be used with System
Architecture desktop or web product.


6.


Optional features


7.


User interface
priorities

A.
Professional look and feel

B. Should be in sync with System Architect UI.


8.


Reports

1.

Appropriate TOGAF Reports on Gap Analysis a
nd
Architectural Roadmap Document.

9.


Other important issues



10.


Team Size

2
-
4 members

11.


Technologies to be
used

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

12.


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



Tivoli CDP/TSM / Tivoli Directory Server



Linux will be the preferred OS.



IBM Rational System Architect, desktop and Web
products.



IBM Rational System Architect Catalog Manage
r



Windows OS.



IBM Rational Publishing Engine

13.


Final Deliverable must
include

A.

Complete Source code

B.

Demonstrable use
-
case, along with working sample
System Architect repository


C.

Help documentation