1 / 18

eRA Migration/Development Strategy

eRA Migration/Development Strategy. Kalpesh S. Patel Ekagra Software Technologies, Ltd. Strategic Enterprise Architecture. Vision Define “Where/What is There”? Functional Architecture End-to-end eRA architecture High level UseCase models Detailed blue print Migration Plan

taya
Télécharger la présentation

eRA Migration/Development Strategy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. eRA Migration/Development Strategy Kalpesh S. Patel Ekagra Software Technologies, Ltd.

  2. Strategic Enterprise Architecture • Vision • Define “Where/What is There”? • Functional Architecture • End-to-end eRA architecture • High level UseCase models • Detailed blue print • Migration Plan • Data Architecture • Database architecture • Physical & Logical partitioning of data • Data Security • Business Intelligence • Technical Architecture • Product Capabilities & Usage Guidelines • Product Integration

  3. Tactical Issues • UI Standards • UI Implementation Templates • Legacy Integration with J2EE • Portal Architecture • Security Architecture • Development Tools Guidelines • J2EE Usage guidelines • Migration Strategy & Order

  4. 9iAS J2EE Server - eRA User Authentication Info +NIH Request + NIH Response Business Apps JSP, Servlet User Authentication Info + eRA Request + eRA Response Web Services JPDK NIH SSO NIH Authentication OID LDAP eRA Authentication Portal Integration Architecture eRA NIH NIH Portal eRA Portal Security Authentication

  5. Migration StrategyObjectives • Migration of IMPAC-II applications to J2EE • Preserve intellectual capital • Unified enterprise architecture • IMPAC-II migration sequence • COMMONS migration sequence

  6. Migration of IMPAC-II Apps 8+ common modules

  7. Common Modules • Tightly integrated • Options • Maintain two copies, J2EE & Oracle Forms • Integrate J2EE apps with legacy Forms • Migrate all legacy applications to Web (JInitiator) • Call Oracle Forms from J2EE • Call J2EE from Oracle Forms

  8. Migration Order • Criteria • Dependency • Need to be web based • Complexity • Business priority • Common Modules • Migrate at the end • Exceptional case : Migrate with the business area

  9. Next Steps • Technical integration between J2EE and Oracle Forms • Migration Order & Plan

  10. COMMONS

  11. Observations • NIH communicates with Grantee through out the life cycle (Paper) • Formal communication captured by IMPAC-II • COMMONS - additional communication channel • Continue to support paper process • COMMONS functionality overlaps with IMPAC-II

  12. Overlap

  13. Approach • COMMONS – Customer facing application • COMMONS as another business area of IMPAC-II • Reuse common components

  14. Alignment • Close alignment by functional areas - IMPAC-II & COMMONS • One lead analyst per functional area - ownership • One scope document per functional area • Lead analyst to coordinate resolution of all policy issues

  15. Alignment - 2 • Requirements – Per functional area • Identify end-to-end business process (internal & external) • One set of business use cases & supplementary specs • Share Actors where possible and address security for them • Organize/categorize all artifacts by functional area • Unifying the development

  16. Advantages Build Once Resource Savings Easier maintenance Cohesiveness among IMPAC-II & COMMONS Disadvantages Slower development Resource Savings are not linear Dependency Approach assessment Issues • Coordination • Scheduling • Accountability • Security

  17. Next Steps • Business plans - Review • Define business processes (e.g. Trainee Appointment, Continuations, cGAP) • Task plan & Interdependency • Schedule • Develop Coordination plan • Resource Allocation Plan

  18. Questions?

More Related