1 eRA Migration/Development Strategy Kalpesh S. Patel [email protected] Ekagra Software...

26
1 eRA eRA Migration/Developmen Migration/Developmen t Strategy t Strategy Kalpesh S. Patel Kalpesh S. Patel [email protected] [email protected] Ekagra Software Technologies, Ltd. Ekagra Software Technologies, Ltd. 4/9/2002 4/9/2002
  • date post

    19-Dec-2015
  • Category

    Documents

  • view

    216
  • download

    0

Transcript of 1 eRA Migration/Development Strategy Kalpesh S. Patel [email protected] Ekagra Software...

Page 1: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

1

eRA eRA Migration/DevelopmeMigration/Developme

nt Strategynt StrategyKalpesh S. PatelKalpesh S. Patel

[email protected]@od.nih.gov

Ekagra Software Technologies, Ltd.Ekagra Software Technologies, Ltd.

4/9/20024/9/2002

Page 2: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

2

AgendaAgenda

• Migration Strategy - ReviewMigration Strategy - Review• Migration/Development OrderMigration/Development Order• Proposed ScheduleProposed Schedule• Enterprise Architecture Enterprise Architecture

Development ProcessDevelopment Process

Page 3: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

3

Strategic Enterprise Strategic Enterprise ArchitectureArchitecture

• VisionVision– Define “Where/What is There”?Define “Where/What is There”?

• Functional ArchitectureFunctional Architecture– End-to-end eRA architectureEnd-to-end eRA architecture– High level UseCase modelsHigh level UseCase models– Detailed blue printDetailed blue print

• Data ArchitectureData Architecture– Database architectureDatabase architecture– Physical & Logical partitioning of dataPhysical & Logical partitioning of data– Data SecurityData Security– Business IntelligenceBusiness Intelligence

• Technical ArchitectureTechnical Architecture– Product Capabilities & Usage GuidelinesProduct Capabilities & Usage Guidelines– Product IntegrationProduct Integration

• Migration PlanMigration Plan

Page 4: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

4

Migration StrategyMigration StrategyObjectivesObjectives

• Migration of IMPAC II applications to Migration of IMPAC II applications to J2EEJ2EE

• Develop unified enterprise architecture Develop unified enterprise architecture • Maintain enterprise natureMaintain enterprise nature• Preserve intellectual capitalPreserve intellectual capital• IMPAC II migration orderIMPAC II migration order• COMMONS migration/development COMMONS migration/development

orderorder

Page 5: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

5

AlignmentAlignmentBusiness Process IMPAC-II Application COMMONS Application

1 Non Competing continuation GMICOPopulation TrackingFSR

e-SNAPPopulation Tracking SubmissionFSR Submission

2 Trainee TA & Payback X-Train

3 Competitive Grant Applications ReceiptReferralGUMGMSubprojects

c-GAP

4 Institution Profile IPF Self Service IPF

5 Personal Profile Common Person Module Self Service PPF

6 Review Peer ReviewSummary Statements

Internet Assisted Review

7 Committee Management

8 Status Grant FolderICSTOReQuickViewIQRCRISP+

Application StatusView Summary StatementView NGACRISP-Web

9 Administrative User Administration Account Administration

10 Approval Process Needed in IMPAC-II Needed in COMMONS

11 Checklists Customization checklist COMMONS will needed it

12 ARA processing ARA processing Submit ARA

13 Email notification Internal External

External

14 Close Out GM Close OutFSR

Final Progress reportFSR Submission

Page 6: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

6

ApproachApproach

• COMMONS – Customer facing applicationCOMMONS – Customer facing application• COMMONS as another business area of eRACOMMONS as another business area of eRA• Reuse common componentsReuse common components

COMMONS Data Model

Persistence, O/R mapping Layer

Business Process/Rules Tier

Presentation Tier, JSP

IMPAC-II Data Model

Page 7: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

7

AlignmentAlignment

• Close alignment by functional areas Close alignment by functional areas – IMPAC II & COMMONS– IMPAC II & COMMONS

• One lead analyst per functional area One lead analyst per functional area – ownership– ownership

• One scope document per functional One scope document per functional areaarea

• Lead analyst to coordinate Lead analyst to coordinate resolution of all policy issuesresolution of all policy issues

Page 8: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

8

Alignment – 2Alignment – 2

• Requirements – Per functional areaRequirements – Per functional area– Identify end-to-end business process Identify end-to-end business process

(internal & external)(internal & external)– One set of business use cases & One set of business use cases &

supplementary specssupplementary specs– Share Actors where possible and address Share Actors where possible and address

security for themsecurity for them– Organize/categorize all artifacts by Organize/categorize all artifacts by

functional areafunctional area

• Unifying the developmentUnifying the development

Page 9: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

9

Migration/Development Migration/Development OrderOrder

• CriteriaCriteria– DependencyDependency– ComplexityComplexity– Business priorityBusiness priority– Need to be Web-basedNeed to be Web-based

Page 10: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

10

IMPAC II Apps – IMPAC II Apps – DependenciesDependencies

8+ common modules8+ common modulesCommon Modules

Notes Application PeopleGrant Folder GUM SubProject ICSTORe

Edit Checker

Customizable checklist

Electronic 901

Email Registration & Notification

Workflow Architecture Portal

Can be used Independently? X X X X X X

Integrated with other applications? X X X X X X X X

Volatility of Changes? Low Low High

IMPAC-II

Business CriticalReceipt R&R X X X ? ?

Council & Peer Review CM XPeer Review X X X X X X X X X X

Summary Statement GenerationInternet Assisted Review XPortal

Program, IC Support & Council ECB

ICO/DEA X X X ? X X X XPopulation Tracking

Future Program Module X X X X ? X X XD Program Portal

SITSARA

GM & Finance Grants Payment MgmtFuture Budget Portal

Grants Management X X X X X X X

Page 11: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

11

Migration/Development Migration/Development OrderOrder

• Phased ApproachPhased Approach– Phase 1 – Low dependencyPhase 1 – Low dependency– Phase 2 – Medium dependency, High Phase 2 – Medium dependency, High

business prioritybusiness priority– Phase 3 – High dependency, Medium Phase 3 – High dependency, Medium

business priority, High complexitybusiness priority, High complexity

Page 12: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

12

Internal External Criteria

Phase 1 Dependency Complexity BusinessPriority (Time line 16-18)

Need to be web based

Phase 1

Committee Management

CM Fast track Low High Timeline Attached Yes

RAE

ICSTORe, QV, CRISP+, IQR, GrantFolder, GUM – View only, QVR, ECB

CRISP-Web, Status Low Low Timeline Attached

Trainee – Supportee

Trainee X-Train Low Low Timeline Attached

Program

Program Module + Program part of ICO, Program Portal

e-SNAPFSRProgress Report

LowLowLow

MediumMediumMedium

Timeline Attached Yes

Information Management

IPF Self Service IPF Low Low Timeline Attached Yes

Type 4, 6, 7, 8 Processing Low Medium Timeline Attached

e-Notification

Common mailer e-mail notification & registration

Mailer Medium High Timeline Attached Yes

e-Request

ARA 901

ARA RequestNo Cost Extension

LowLow

LowLow

Timeline Attached

Common Modules

Persons Module Self Service Profile High High Timeline Attached Yes

Edit Checker Edit Checker High Medium Timeline Attached Yes

Other Applications

Internet Assisted Review Low Medium Timeline Attached Yes

User Admin Registration; Account administration Low Low Timeline Attached

Grants Closeout iEdison, Low Low Timeline Attached

Page 13: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

13

Internal External Criteria

Phase 2 Dependency Complexity BusinessPriority (Time line 16-18)

Need to be web based

Phase 2

Grants Management

Grants Payment Management Low Medium Timeline Attached

F&B – Budget Planning Low Medium Timeline Attached

Receipt c-GAP, e-NAP Low High Timeline Attached Yes

Referral Low Medium Timeline Attached

(Program Coding) Low Low Timeline Attached

CM Consultant File Low High Timeline Attached

Voucher entry Low Medium Timeline Attached Yes

Checklist (J2EE) High Medium Timeline Attached

GUM High High Timeline Attached

DEA (ICO) High High Timeline Attached

Trainee Payback, SITS SITS – Request Medium Medium Timeline Attached

Business Intelligence – IRDB - Medium Timeline Attached

Finance & Budget Low Medium Timeline Attached

Other Applications

Pop-Tracking Pop-Tracking Submission Low Low Timeline Attached

User Admin Low Low Timeline Attached

Batch Assignment Module Interface Low Low Timeline Attached

e-Request

Supplemental Fund Request (Administrative and SITS)Change InstitutionChange PISuccessor of Interest

MediumLowLow

MediumLowLow

Timeline Attached

CD Ordering Low Low Timeline Attached

---------------------------------------------Migrate All Common Modules -----------------------------

Page 14: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

14

Internal External Criteria

Phase 3 Dependency Complexity BusinessPriority (Time line 16-18)

Need to be web based

Phase 3

Subprojects c-GAP Subprojects Medium High Timeline Attached

GM Medium High Timeline Attached

Review High High Timeline Attached

Records Management Low Medium Timeline Attached

Page 15: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

15

Business TimelineBusiness Timeline

• Overall scheduleOverall schedule• Need to reevaluate (bi) annually Need to reevaluate (bi) annually

Page 16: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

16

1

2345

6789101112131415161718192021222324252627282930313233343536373839404142434445

A B C D E F G H I J K L M N O P Q R S T U V W X YDRAFT Analysis Design & Development Efforts ongoing

Migration Order This color represents the Architecture that need to be done for projects that will start before full eRA enterprise architecture is developed

2002 2003Application JanuaryFebruaryMarch April May June July August SeptemberOctoberNovemberDecemberJanuaryFebruaryMarch April May June July August SeptemberOctober

Phase 1

RAE InternalICSTORe, QV, IQR, CRISP+,

Grant Folder, GUM(View),QVR, Ad-hoc Reporting

External CRISP-Web, Status Reporting

Trainee Supportee Internal TA Payback, SITS

External X-Train

Program Internal Program Module

External e-SNAP (Includes Prog. Rep)FSR

Info. management Internal IPF

External Self Service IPF

e-Notification Internal Common Maileremail notification & registration

External Mailer

e-Request InfrastructureInternal ARA

901Type 4, 6, 7, 8 Processing

External ARA RequestNo Cost Extension

CM Internal Fastrack

Common Modules Internal Person ModuleExternal Self Service Person ModuleInfrastru Edit Checker

Other Applications Both Internet Assisted Review

External Registration; Account adminBoth Grants CloseoutBoth iEdison (?)

Phase 1

Page 17: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

17

Phase 2

1

2345678910111213141516171819

20212223242526

A B C D E F G H I J K L M N O P Q R S T U V W X YDRAFT Analysis Design & Development Efforts ongoing

Migration Order This color represents the Architecture that need to be done for projects that will start before full eRA enterprise architecture is developed

2003 2004Application SeptemberOctoberNovemberDecemberJanuaryFebruaryMarch April May June July August SeptemberOctoberNovemberDecemberJanuaryFebruaryMarch April May June

Phase 2GM - F&B Internal Budget Planning

CM Internal CMExternal CM-Voucher submission

Receipt Internal ReceiptExternal c-GAPInternal Referral

Other Both Checklist (J2EE)Internal GUM

Business Intelligence - IRDBDEA (ICO)

User AdminBatch Assinment Module

InterfaceCD OrderingPopTracking

External Supplemental Fund RequestChange Institution Request

Change PI RequestSuccessor of Interest

Page 18: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

18

Phase 3

1

234567891011

A B C D E F G H I J K L M N O P Q R S T U V WDRAFT Analysis Design & Development Efforts ongoing

Migration Order This color represents the Architecture that need to be done for projects that will start before full eRA enterprise architecture is developed

2004Application SeptemberOctoberNovemberDecemberJanuaryFebruaryMarch April May June July August SeptemberOctoberNovemberDecember

Phase 3External cGAP-SubprojectsInternal SubProjectsInternal GMInternal ReviewInternal Records Management

Page 19: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

19

IssuesIssues

• Need to align internal & external Need to align internal & external business plansbusiness plans

• Resource allocationResource allocation– Analysts allocation – doneAnalysts allocation – done– Development allocation - ?Development allocation - ?– Dollars - ?Dollars - ?

Page 20: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

20

Enterprise Architecture Enterprise Architecture Development ProcessDevelopment Process

Page 21: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

21

ObjectivesObjectives

• Develop end-to-end eRA enterprise Develop end-to-end eRA enterprise functional architecturefunctional architecture

• Help define projectsHelp define projects• Maintain enterprise nature of the Maintain enterprise nature of the

systemsystem• Ensure that the vision is carried out Ensure that the vision is carried out

in the implementationin the implementation

Page 22: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

22

Architect - Kalpesh

1Analyst Team

Analyst Analyst Analyst

Group Advocate Team

Advocate Advocate Advocate

All Business Areas ->

here represent Internal and external systems

GM

CM

TA

Rev Rec F&B

e-Notification

Assignment

Checklist

Grant update

Coding (Human Sub)

FunctionalArchitecture

2

Business Use Case Specifications

3

Business LevelObject Model

4

Current Efforts-Use Cases-Object Model

6

5

Development Team

Dev. Team Lead Dev. Team Lead Dev. Team Lead

Enterprise Functional Architecture

Page 23: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

23

Analyst Group Ad

1

Object Model

Scope Document

All Business Areas ->

here represent Internal and external systems

GM

CM

TA

Rev

Rec

F&B

e-Notification

Assignment

Checklist

Grant update

Coding (Human Sub)

SystemsDesign

3

Architect Team Lead

3

Refined Use Case Specifications

4

5

6

J2EE Practice

7

Refined Object Model

8

Use Case Specifications

2

Enterprise Functional Architecture

Page 24: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

24

Refined Use Case Specifications

Refined Object Model

Greenleaf, Software Apps

CM GM TA

D’Amico, J2EE Practice

EJB Dev 1 EJB Dev 2 Persistence

UI, JSPEJB, Persistence,Business Rules

Assembly

Application

Architect

Internal and external systems ->

GM

CM

TA

Rev

Rec

F&B

e-Notification

Assignment

Checklist

Grant update

Coding (Human Sub)

SystemsDevelopment

1 23

4

5 6

7

8 9

Enterprise Functional Architecture

Analyst

Group Ad

Page 25: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

25

To be doneTo be done

• OrganizationOrganization– Architect, Analysts, Group Advocate, Architect, Analysts, Group Advocate,

DevelopmentDevelopment• Process FlowProcess Flow

– Ownership of the artifactsOwnership of the artifacts• Feedback loopFeedback loop• QA process when the objects are QA process when the objects are

movedmoved• Security requirements verificationSecurity requirements verification

Page 26: 1 eRA Migration/Development Strategy Kalpesh S. Patel patelk@od.nih.gov Ekagra Software Technologies, Ltd. 4/9/2002.

26

Questions?Questions?