This a 4 pages paper from IBM whose highlight are:
– Aligns business and IT goals through service modeling that is designed to connect an enterprise’s business model with its technology model
- Helps ensure that business knowledge in legacy applications can be accessed in a new, integrated, SOA
- Helps increase business flexibility and reduce risks by validating several aspects of SOA design, from business goal to service realization
This post from blogs@ZDNet talks about the announcing that three SOA vendors are lauching something called “SOA Maturity Model”. According to this model, SOA has five key phases in its lifecycle: from initial projects to evolution into a full-fledged “enterprise nervous system”. The model is based on CMMI from CMU.edu.
We have the “Three SOA amigos”: AmberPoint, Sonic Software and Systinet.
The model defines five levels of maturity and sets a vision for business benefits realized at each of these levels.
- Level 1: This is the initial learning and initial project phase of SOA adoption. Projects here are typically done to simultaneously meet a specific need to implement functionality while trying out specific technologies and an approach to SOA.
- Level 2: At this level, standards are set as to the technical governance of SOA implementation, typically under leadership of the architecture organization.
- Level 3: A partnership forms between technology and business organizations in order to assure that the use of SOA provides clear business responsiveness.
- Level 4: Level 4 focuses on measuring and presenting these processes at the business level so as to provide continuous feedback on the performance and business impact of the processes implemented at Level 3.
- Level 5: The SOA information systems becomes the “enterprise nervous system” and takes action automatically according to events occurring at the business level according to rules optimizing business goals.
IBM announced on Oct 12th plans to contribute with Open source Community by “giving” a subset of the IBM Rational Unified Process (RUP). See a excerpt:
“IBM will contribute a subset of the IBM Rational Unified Process (RUP), a software process platform that has guided some 500,000 developers around the world in projects ranging from small-scale product development to large industrial-strength systems. RUP is a vast collection of methods and best practices for promoting quality and efficiency throughout software development projects. IBM’s donation will also provide a foundation architecture and Web-based tools for the industry to engineer, collaborate on, share and reuse software development best practices.“
other link related to:
This holiday (Out, 12th) I was at livraria Cultura in São Paulo and, of course, I couldn’t resist… ….I bought “The Rational Unified Process Made Easy“. It is a classic must-have book. Instead of tons of white papers about RUP that I have to carry in my backpack, I keep only this five-star book.
See a piece of Amazon’s editorial review:
The Rational Unified Process Made Easy will teach you the key points involved in planning and managing iterative projects, the fundamentals of component design and software architecture, and the proper employment of use cases. All team members–from project managers to analysts, from developers to testers–will learn how to immediately apply the RUP to their work. You will learn that the RUP is a flexible, versatile process framework that can be tailored to suit the needs of development projects of all types and sizes.
Key topics covered include:
* How to use the RUP to develop iteratively, adopt an architecture-centric approach, mitigate risk, and verify software quality
* Tasks associated with the four phases of the RUP: Inception, Elaboration, Construction, and Transition
* Roles and responsibilities of project managers, architects, analysts, developers, testers, and process engineers in a RUP project
* Incrementally adopting the RUP with minimal risk
* Common patterns for failure with the RUP–and how to avoid them
Use this book to get quickly up to speed with the RUP, so you can easily employ the significant power of this process to increase the productivity of your team
Six Sigma again. This time the Six Sigma approach is suggested in an attempt:
- to build dependable – “plug-and-play” - products;
- realiable products: “last a long time”;
- and, of course, low cost (anticipate that products will be affordable).
Six Sigma, according to this article, can help IT managers to reach these goals:
“As a breakthrough philosophy, process, and methodology, Six Sigma offers a refreshing approach to systematically implement robust designs.”
March of the ESBs by ZDNet‘s Joe McKendrick — It’s no use fighting ESBs; they’re an unstoppable wave now. First IBM announced it was offering not one, but two (count ‘em, two) enterprise service buses, and now word is out that JBoss also is getting into the ESB act. InfoWorld’s Paul Krill reports that the open-source app server company “plans to offer an open-source ESB in 2006.” Along with IBM and JBoss, a lot of infrastucture vendors have been getting on the bus lately, including BEA. And, the open-source world has another ESB-like architecture in the offing — the Apache Synapse Web services intermediary.[...]
This is one of that articles that I always carry on in my backpack:
A key part of the software architect’s job is producing an architectural description of the system that defines the architecture’s key functions, features, and characteristics for its stakeholders. Where do you start? What do you need to know? Nick Rozanski and Eóin Woods provide detailed answers to these questions, with useful suggestions on how to attack this fundamental document that underpins any development project.
Well, my wish list at Amazon.com is growing I have discovered this five-stars book this week. I beg you: wanna give me a gift? Buy any one of these books. I deeply appreciate!
This week I present you the “Software Systems Architecture”:
From the Back Cover
Software Systems Architecture is a practitioner-oriented guide to designing and implementing effective architectures for information systems. It is both a readily accessible introduction to software architecture and an invaluable handbook of well-established best practices. It shows why the role of the architect is central to any successful information-systems development project, and, by presenting a set of architectural viewpoints and perspectives, provides specific direction for improving your own and your organization’s approach to software systems architecture.
With this book you will learn how to
* Design an architecture that reflects and balances the different needs of its stakeholders
* Communicate the architecture to stakeholders and demonstrate that it has met their requirements
* Focus on architecturally significant aspects of design, including frequently overlooked areas such as performance, resilience, and location
* Use scenarios and patterns to drive the creation and validation of your architecture
* Document your architecture as a set of related views
* Use perspectives to ensure that your architecture exhibits important qualities such as performance, scalability, and security
The architectural viewpoints and perspectives presented in the book also provide a valuable long-term reference source for new and experienced architects alike.
Whether you are an aspiring or practicing software architect, you will find yourself referring repeatedly to the practical advice in this book throughout the lifecycle of your projects.
A supporting Web site containing further information can be found at www.viewpoints-and-perspectives.info
According to this link, Fusion is the answer from Oracle to “Next-Generation Enterprise Architecture”.
- This suite of next-generation enterprise applications will leverage Oracle Fusion Middleware and also give customers access to Java, composite applications built on Service-Oriented Architecture (SOA), master data consolidation, Grid Computing, and other powerful technologies. Project Fusion also includes an architecture that provides:
- Business Insight: Enterprise-wide business intelligence for improved decision making with the ability to take action immediately;
- Adaptable Business Processes: Adaptive processes that help adjust to changing market conditions and competitive threats;
- Superior Ownership Experience:Lowest total cost of ownership of all enterprise software providers
Java Server Faces + EJB 3.0 + jBPM = JBoss Seam Framework
JBoss released the Seam framework that aims to unify the component models of JSF and EJB 3.0, providing a streamlined programming model for web-based enterprise applications.
Let’s point out some promisses:
- Seam introduces the notion of declarative application state management for POJO (Plain Old Java Objects) components;
- Seam components are stateful and contextual, with a well-defined container-managed lifecycle. This approach helps solve a whole class of bugs and performance problems that plague web applications with non-linear or multi-window navigation;
- Seam makes business process management a first class construct, by fully integrating JBoss jBPM into this state management architecture. It’s never been this easy to write applications with complex workflows and complex user interactions;
- Finally, Seam makes it easy to test Java EE 5 applications in unit test frameworks by leveraging the JBoss Embeddable EJB3 container.
It looks good don’t you think?