ebSOA Task Breakdown and Draft Deliverables Schedule.doc

557 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
557
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

ebSOA Task Breakdown and Draft Deliverables Schedule.doc

  1. 1. DISCUSSION DRAFT ebSOA Task Breakdown and Draft Deliverables Schedule The components of a framework needed to execute a complete SOA solution are: • Methodology -- enables a service-based business process modeling, deployment and execution from the high level business requirements analysis to the run-time technology • Reference Model -- defines SOA components on a conceptual level • Standards -- standard-based specifications that provide support for SOA architectural components • Reference Architecture -- high level architecture that defines main SOA architectural components and their relationships • Run-time Architecture -- detailed technical architecture based on the reference architecture with all architectural components fully integrated using the open-standard based specifications • Best Practices – employs concrete examples to illustrate best of breed processes and technology By modeling business processes with services we are able to define in business terms the underlying architecture that supports deployment and execution of business processes. What SOA enables is the semantics of the business to become the semantics for the technology, and this will be reflected in ebSOA TC specifications. The ebSOA TC SOA specification will be based on: • A business process modeling approach and ontology that uses accepted business process concepts and entities in a way that allows the enterprise to replicate in an operational programming environment using XML-driven methods the role, relationship and choreography that the enterprise has, or aspires to, with its partners in real life This includes the following functional capabilities and characteristics: • External collaboration oriented business processes (collaborations with partners, suppliers, customers, etc.) • Internal collaboration oriented processes (integration and interoperability in mid-size and large enterprises) • Enterprise information integration processes (data and meta-data management) • Infrastructural processes (IT infrastructural management based on either widely accepted models or proprietary models) • A reference architecture that defines all components and their relationships • A run-time SOA architecture that enables a complete integration of all architectural components • OASIS Web Services, ebXML, and other appropriate standards specifications that provide support for the components that make up the architecture • Best practices document • Interoperability guidelines • Gap analysis – call for standards ebsoa-task-breakdown-and-draft-deliverables-scheduledoc947.doc Page 1 of 7
  2. 2. DISCUSSION DRAFT How are existing specifications utilized and what gaps are to be filled? Many of the standards that are being used are run time standards. They do not necessarily interoperate with each other to enable composition that will achieve a higher level solution. The intent is to include in the methodology how to achieve interoperability. It is anticipated that a call for development of standards for some components will be needed. For example there does not appear to be accepted standard(s) for Business Rules and Agent Frameworks. The ebSOA TC goal is to draft a complete service oriented architecture specification that includes existing, and well developed proposed, standards to reflect federated enterprise reference architecture. The specification will enable full architectural integration of all SOA components; the intent is to provide universal support for deployment and execution of business processes without need for re-building and re-coding new SOA enterprise platforms every time new or modified processes need to be supported. The SOA Best Practices document will provide templates and guidance that can be used to illustrate the practical deployment of services. Rather than provide blueprints a call of provision of blueprints for specific domains will be made to the community. ebsoa-task-breakdown-and-draft-deliverables-scheduledoc947.doc Page 2 of 7
  3. 3. DISCUSSION DRAFT Deliverables, Milestones and Scheduling Items / Tasks to be defined / completed: • Methodology -- enables a service-based business process modeling, deployment and execution from the high level business requirements analysis to the run-time technology • Reference Model -- defines SOA components on a conceptual level • Identify Standards -- standard-based specifications that provide support for SOA architectural components • Reference Architecture -- high level architecture that defines main SOA architectural components and their relationships • Run-time Architecture -- detailed technical architecture based on the reference architecture with all architectural components fully integrated using the open-standard based specifications • Best Practices – employs concrete examples to illustrate best of breed processes and technology The ebSOA TC SOA specification will be based on: • A business process modeling approach and ontology that uses accepted business process concepts and entities in a way that allows the enterprise to replicate in an operational programming environment using XML-driven methods the role, relationship and choreography that the enterprise has, or aspires to, with its partners in real life This includes the following functional capabilities and characteristics: • External collaboration oriented business processes (collaborations with partners, suppliers, customers, etc.) • Internal collaboration oriented processes (integration and interoperability in mid-size and large enterprises) • Enterprise information integration processes (data and meta-data management) • Infrastructural processes (IT infrastructural management based on either widely accepted models or proprietary models) • A reference architecture that defines all components and their relationships • A run-time SOA architecture that enables a complete integration of all architectural components • OASIS Web Services, ebXML, and other appropriate standards specifications that provide support for the components that make up the architecture • Best practices document • Interoperability guidelines • Gap analysis – call for standards ebsoa-task-breakdown-and-draft-deliverables-scheduledoc947.doc Page 3 of 7
  4. 4. DISCUSSION DRAFT Deliverables / Milestones 1. Vision document and Charter clarification 2. Specification outline – high level – Introduction / Scope / Assumptions / Constraints / ToC / Sections / Appendix 3. Specification break-out by Section a. Methodology -- enables a service-based business process modeling, deployment and execution from the high level business requirements analysis to the run-time technology b. Reference Model -- defines SOA components on a conceptual level c. Identify Standards -- standard-based specifications that provide support for SOA architectural components d. Reference Architecture -- high level architecture that defines main SOA architectural components and their relationships e. Run-time Architecture -- detailed technical architecture based on the reference architecture with all architectural components fully integrated using the open- standard based specifications f. Appendix - Best Practices – employs concrete examples to illustrate best of breed processes and technology 4. Drafts available by section 5. Revisions and completion of first committee draft 6. Finalize Committee Draft 7. Call for Comments 8. Approval of Committee Draft 9. Public Review 10. OASIS ballot ebsoa-task-breakdown-and-draft-deliverables-scheduledoc947.doc Page 4 of 7
  5. 5. DISCUSSION DRAFT Schedule: ebsoa-task-breakdown-and-draft-deliverables-scheduledoc947.doc Page 5 of 7
  6. 6. DISCUSSION DRAFT ebSOA Schedule Task 1 Architecture STRAWMAN SCHEDULE Stuff -S01 TBD Review Draft Publish More tasks Thing -S02 -S06 TBD More Team -S03 Draf t OASI S 2007 APR MAY JUN JUL AUG SEP OCT NOV DEC JAN FEB 2006 -S09 -S10 This Review Phase 1 -S05 -S04 That -S07 -S08 DEVELOPMENT / TESTING CYCLES ebsoa-task-breakdown-and-draft-deliverables-scheduledoc947.doc Page 6 of 7
  7. 7. DISCUSSION DRAFT ebsoa-task-breakdown-and-draft-deliverables-scheduledoc947.doc Page 7 of 7

×