Enterprise Software Development Orchestration

Ten years ago the Rational Unified Processed (RUP) was the heir apparent for organizing a systematic software development approach that would lead from early abstract diagrams (use cases) to design diagrams and finally to executable programming (classes). RUP is rarely used today. What happened? RUP failed to integrate the planning of enterprise data structures. Software developers are left scrambling to make sense out of different approaches for applying Service Oriented Architecture (SOA). The following list describes an SOA approach that integrates legacy data structures into reconstructed, modern web architecture.

(1) Create An Overall Milestone Plan

(2) Create A Semantic Model

(3) Creat An Exact Model Of Legacy Data Structures (As Is)

(4) Do An Initial Business Process Analysis

(5) Reverse Engineer Current (As Is) System Requirements (Functional & Non Functional)

(6) Develop An Appropriate Security Model

(7) Plan Your Software Development Lifecycle For Future & Changing Applications Systems

(8) Choreograph Internal & External Web Processes That Match Initial Business Model (4)

(9) Design A Messaging Infrastructure

(10) Create Necessary XML Repositories and XML Registries

(11) Create XML Applicances, Service Intermediaries, And Adjust For Network Gateways

(12) Profile Providers & Consumers & Revise Future Applications Requirements (see diagram below)

(13) Make Adjustments For B2B Transactions, Exchanges With External Web Vendors Of Services

(14) Create Mash-Ups Between Web Business Processes (8 & 12) And New And Old Data Structures

(15) Adjust For Dynamic Shared Documents, Social Networking, And Cloud Computing

(16) Revise And Finalize Minimum Documents Illustrating Business Processes & Data Structures

Copyright 2010 All Rights Reserved