An outline structure for the Testable Architecture Methodology has been uploaded to the wiki. This outline is intended to help refine the phases, and steps within those phases, before the methodology is encoded using Eclipse Process Framework.
For more information please see: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257011#4257011 and http://www.jboss.org/community/wiki/TestableArchitectureMethodology
Friday, 25 September 2009
Thursday, 3 September 2009
Tuesday, 1 September 2009
Announcing the SAVARA project
We are pleased to announce a new jboss community project, called Savara, established in collaboration with Cognizant (www.cognizant.com ) and Amentra (www.amentra.com ).
The purpose of this project is to develop a new methodology for Enterprise Architecture and Distributed Computing, called “Testable Architecture”, and provide appropriate tooling support.
This methodology aims to ensure that any artifacts defined during the development lifecycle can be validated against other artifacts in preceding and subsequent phases. This ensures that the final delivered system is guaranteed to meet the original business requirements. Through runtime governance, it is also possible to ensure that the running system continues to meet those requirements.
As a system evolves, through subsequent enhancements to the business requirements, having such a precise understanding of the system, from requirements, through design, implementation and deployment, enables more sophisticated change management techniques to be considered.
For more information on the project, please visit the project website.
The purpose of this project is to develop a new methodology for Enterprise Architecture and Distributed Computing, called “Testable Architecture”, and provide appropriate tooling support.
This methodology aims to ensure that any artifacts defined during the development lifecycle can be validated against other artifacts in preceding and subsequent phases. This ensures that the final delivered system is guaranteed to meet the original business requirements. Through runtime governance, it is also possible to ensure that the running system continues to meet those requirements.
As a system evolves, through subsequent enhancements to the business requirements, having such a precise understanding of the system, from requirements, through design, implementation and deployment, enables more sophisticated change management techniques to be considered.
For more information on the project, please visit the project website.
Subscribe to:
Posts (Atom)