It is very unfortunate whatever IT companies failed in all history IT enablement is still covering by polishing their product stack using any agile methodology for IT enablement of business needs created in human civilization.
What is really SOA has to do with service enabling platform such as BEA and IBM? What is the big deal some IT product vendor's people publishing these kind of document?
All I wanted to know is
1. How SOA agile methodology applied to Business Analysis to understand business needs in terms of business sub systems, business sub system functional entities, business functional entities roles and responsibilities
2. Decomposition of business needs into business functions of business sub system’s functional entities
3. Decomposition of same into business transactions
4. Decomposition of business transactions into business process.
5. Understanding and designing business transaction events and initiators
6. Design and development of business transaction business data in terms of canonical data models
7. Decomposition of business transaction processes into business process entities
8. Roles and responsibilities of business process entities
9. Mapping of point nine to same of business functional entities
10. Grouping the process entities to serve functional entities
11. Avoid duplication
12. Establish reusability at the process entity in such a way that one process entity serve multiple functional entities requirement by following their roles and responsibly to fulfill the business functional needs
13. decompose process entity into activities, task
14. decompose task and activities groups into reusable services
15. Services into different taxonomy based on their nature
16. service identification of a business process from enterprise repository and registry
17. service usage plan which lead to build, enhance, decommission or buy decision
18. service life cycle
19. Service best practices
20. Service best design
21. Service best SDLC
22. Service Quality
23. Service deployment
24. Service maintenance
25. Service policy
26. Service governance
27. roles and responsibly to do all mentioned above
28. Education
29. Mentor
30. Evaluation
31. road map
etc etc
Please stop taking cow **** and covering it with chocolate
I know personally some of the project mentioned here. I have worked with people directly or indirectly involved in that projects. Most of them, if they were not directly related to BEA, they have talked about how companies made stupids out of CTOs of these firm during our discussion in the BARs in hotels west and east and North middle corner of USA.
SOA is not building services using a vendor’s tools and showing cost reduction.
SOA is more than that and this document is not addressing it. BEA as a company has failed address business needs and eventually business alignment into IT.
Anybody can build tools based on J2EE and WS specification, it is nothing has to do with a bunch of tools and technology.
Let us talk how SOA as a design approach applied to IT enablement of an enterprise in a product independent FASHION.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.