ProductsDesktop Server Red Hat Enterprise Linux OpenStack Platform For IBM POWER For IBM System z For SAP Business Applications Red Hat Satellite Management For Scientific ComputingExtended Update Support High Availability High Performance Network Load Balancer Resilient Storage Scalable File System Smart Management Extended Lifecycle SupportAccelerate Automate Integrate Red Hat JBoss Developer Studio Portfolio Edition Web Framework Kit Application Platform Web Server Data Grid Portal Fuse Red Hat JBoss A-MQ SOA Platform BRMS Data Services Platform JBoss Operations Network JBoss Community or JBoss enterprise
SolutionsWhy Red Hat Why open hybrid cloud? The new IT Public cloud Cloud resource library Private cloud Infrastructure-as-a-Service (IaaS) Platform-as-a-Service (PaaS) Cloud applications and workloadsSolaris to Red Hat Enterprise Linux Migration overview Migrate from your UNIX platform How to migrate to Red Hat Enterprise Linux Upgrade to the latest Red Hat Enterprise Linux release JBoss Enterprise Middleware Benefits of migrating to Red Hat Enterprise Linux Migration services Start a conversation with Red Hat
TrainingClassroom training Red Hat Online Learning Virtual training Remote classroom training On-site team training Online Learning LabsPopular and new courses Red Hat JBoss Administration curriculum Core System Administration curriculum Red Hat JBoss Middleware Development curriculum Advanced System Administration curriculum Linux Development curriculum Cloud Computing, Virtualization, and Storage curriculum
ConsultingSOA and integration Business process management Cloud and Virtualization Custom Software Development Enterprise Data and Storage Systems management Migrations
JBoss Community Launches Savara Project
September 3, 2009
by JBoss Team
Software development has never been a precise science, hence the large number of projects that either fail to deliver or overrun on cost and timescales.
In most SOA development projects, business analysts’ typically write requirements using basic desktop productivity tools. Architects and developers then try to deliver on those requirements, but often find that what they create is not what the business expected. The process requires several iterations back and forth between the business and IT to finally deliver what was expected, wasting valuable time and resources.
A typical software development lifecycle involves multiple phases, including the gathering of business requirements, the creation of an architectural model, the design of services, and the actual writing of code. Each phase depends on the accuracy of the others. When one phase is out of alignment with the ultimate goal, the other phases are pulled out of alignment as well, resulting is a system that does not meet the original business requirements.
That’s why we are announcing a new JBoss Community project called Savara that is aimed at solving this problem by building upon the SOA Process Governance work that is going on within the JBoss Community.
The Savara project aims to apply engineering rigor to the software development process in an effort to improve productivity and quality, while reducing the cost and time to build systems.
At it’s core, the Savara project will employ a concept called “Testable Architecture.” This involves providing the business analyst with modeling tools that can be used to define business requirements. Then, at each phase of the software development lifecycle, the artifacts created in that phase can be tested to make sure they conform with artifacts created in other phases, and ultimately with the original business requirements.
For example, architectural models can be verified against business requirements, paving the way for the creation of service designs. Once created, those service designs can, in turn, be verified against the architectural models, paving the way for code to be written. That code can then be verified against the services designs. Verification at each phase of the software development lifecycle ultimately yields deployed systems that are guaranteed to meet the original business requirements.