Dom introduction-website-v1.0

Editor's Notes

1. Most Enterprises recognize its strategic approach—that is, harnessing the information power between and among its disparate entities and the agility that it would imbue—requires a radical departure from conventional development practices to resolve the following challenges: [Read from Slide]Additional Talking PointsBusiness Challenges: Reuse of processes, services and data across COI. The process of translating system requirements to system design, though overseen by centralized management, often misses the mark due to time compression or granularity of design review (e.g. too high level) and/or lack of familiarity with technical environment and/or end-user needs (e.g. requirement does not adequately capture ‘real requirement’).Technology Challenges: Though system design process initially starts as iterative and incremental, schedule compression often forces propagation of immature design and/or unproven approach resulting in significant ‘holes’ in functionality or disconnects at the data and/or systems integration touch points.Designing service-oriented applications often run into “new wine into old wine skins” due to lack of experience or ability to test and/or simulate implementation prior to full scale deployment.Multiple contractors working at service/unit level invariably produce software that fails to integrate at the data and/or service interface level due to lack of cross-communication or use of incompatible “open standards based” tools and technologies. Test and evaluation is not integrated with development process