Welcome!

Microservices Expo Authors: Derek Weeks, Mehdi Daoudi, Pat Romanski, Liz McMillan, Elizabeth White

Related Topics: Microservices Expo

Microservices Expo: Article

Model-Driven SOA

Everything Should Start with a Model

In this article I'll cover how a model-driven design and development process can pave the way to a Service Oriented Architecture that will in turn produce accurate applications that meet business needs and increase development team productivity.

SOA is hot topic in our industry right now. One of the important aspects of SOA is that it's a business approach and methodology as much as it's a technological approach and methodology for developing distributed computing systems.

SOA is a software architecture for building applications that implement business processes or services by using a set of loosely coupled components orchestrated to deliver a well-defined package. With SOA, existing software assets already in use are packaged in such a way that they're self-contained, loosely coupled, and can be called and executed by other new applications as a service. Any new computing modules would be created as services the first time around, and so would enter into the services library to be used over and over again. Well, to call a service, we have to know how to call it, where to call it, and what to expect back as a response; that is, a service must have a callable interface that's well defined, well published, and well secured. In short, not only should a service be good quality code, it must be well understood and well documented.

How Many of You Have Done This or Seen It Happen in Your Organization?
A business analyst sketches out a system feature-by-feature, either on paper or using a flowcharting tool and hands it over to a team for development.

When the system comes back from development for testing, the analyst returns to his sketch and system tests the functionality of each feature, one feature at a time.

Whenever a feature doesn't perform as the analyst thinks he defined it, he makes a note that goes back to the developers, who make changes to the code, and the whole thing starts again...all manual, all by hand. And remember the testing team isn't always made up of analysts who wrote the "sketch"...it's a perfect world assumption that the analyst and some business users are testers along with the testing professionals. How many understandings of the "system" are in that group and how many "notes" go back to development teams? How Neanderthal!

We are no longer Neanderthals. We now have modeling tools. We now have iterative and prototyping development processes. Programming language technology has advanced such that all of our well-meaning attempts at good modular programming over the years can be expanded into bigger modules with more of a business meaning. We recognize the need to communicate and collaborate. It's taken us 40 years...but we're getting there. The idea of architecture implies a thoughtful plan using a standard set of guidelines and rules to construct a blueprint. A good software architecture will have the blueprints for how data is stored, how users interact, how blocks of functionality (services) are linked together to form programs, how programs communicate, the capacity needed of the hardware, and so forth.

The idea behind SOA is that these blocks of functionality (services) are available to be used by many programs, and that, over time, when you have more and more services those programs can be compiled and put together more quickly. And since the services are already defined, their design can be reused too. Also, if a service implements a specific business function or rule, it's simpler, more cost-effective, and less time-consuming just to change the related service code rather than search through all the independent programs for code that may have implemented that business rule and then change all the programs using it like we used to.

Of course, you still have to test it, but the actual design and development time to implement a change from the business is much less of an impact when you have models to work from, impact analysis reports to guide you, and independent services to change.

A set of loosely coupled components does the same work that used to be done inside tightly structured programs. But now the components can be combined and recombined in many ways. This makes the overall infrastructure more flexible and agile. This way SOA can make it easier and faster to build and deploy IT systems that directly service the goals of a business and we can prove it because we have our models of the SOA architectures linked directly back to the model of our business goals, business requirements, and business processes. Not only do we reuse the code, we reuse the models.

Model-Driven SOA
The whole point of SOA is to make business applications more manageable, more flexible, and more responsive to change. Businesses are constantly changing how they do things - not necessarily changing what they do. Models allow the business people to focus and change the business processes and workflows without having to focus on the technological plumbing. The IT folks can focus on designing, changing, and improving those business processes by codifying the business services. The models are their common point of communications and it documents the agreements of what needs to be done. Models can automate and drive impact analysis for better communication between IT and business and, when enough textual information has been captured, most modeling tools can generate quality code that provides a good start toward overall development.

Sybase's view of modeling (Figure 1) is that in an enterprise world your modeling environment has to be able to address the broader range of application classes and has to integrate them. You do not want a silo'd environment; a SOA environment is all about sharing and reuse. Your models have to be able to import, export, capture, forward generate, reverse engineer, and report between the common implementation techniques of service-driven, composite, event-driven, mobile, and federated systems using today's integration protocols.

To Tie It All Together
Business Process Modeling, Data Modeling (with conceptual and physical data models, data warehouse models, and data movement through the information liquidity model), Application Modeling with UML (all diagrams for UML 2.0), XML modeling and Free Models (a semantic-free diagramming and drawing facility that can be adapted to document ANY notation desired) are all used to built applications today.

Requirements should be attached or linked to any elements of any models, with multiple requirements documents tied to multiple models simultaneously for complete requirements traceability and visible as a document or a matrix. Models should be used to round-trip engineer to process engines (BPEL engines), databases, application servers as well as object-oriented development languages including VB, .NET, C#, and Java. By using patterns and templates, you can take a model-driven approach to development on J2EE, .NET and Web Services. By using techniques like object/relational mapping and data source mapping as well as integrated metadata management, you can link and synchronize all the models together. Changes that occur in one model can be communicated effectively and easily as change requests to any other model type to ensure a complete, cohesive, and consistent response to change throughout the project team, and throughout the enterprise. With your common metadata repository, you have a secure environment to manage, share, and collaborate on modeling projects.

SDLC
Modern software development systems are usually developed using model-driven methodologies and processes. The nice thing about comprehensive modeling tools is that all the stakeholders throughout the SDLC (Software Development Lifecycle) have their own view into the metadata or information about the system to be developed. This common detailed definition of what must be built to meet the customer's needs is how development teams can be productive and not waste time because of misunderstandings or because one expert didn't pass some information on to another (Figure 2).
• End users and business analysts have a business-centric view into the system that captures information about requirements, goal, ands conceptual business processes.
• IT management and enterprise architects have detailed functional models, more technical but not a code-level view of system components, hardware, and software deployment details, and shared application components.
• Data architects and DBAs have conceptual data models, physical data models, and the DBMS-specific artifacts necessary to implement the data structure and the services necessary to support the processes being automated or implemented.
• Application/system architects and application developers have their view into the use cases, sequences of events, and objects that have to be implemented to develop the application code and the services necessary to codify the detailed business process.


More Stories By Ian Thain

As one of the Sybase Technical Evangelists, Ian regularly addresses technical audiences all over the world and his sessions are always very well attended. He also writes education classes, whitepapers, demos and articles for various Sybase products and publishes regularly in Journals such as SYS-CON's PBDJ and International Developer Magazine. He is also the Sybase Unwired Platform & PocketBuilder Evangelist and works closely with the team in Dublin, CA and Concord, MA on new features and demonstrations for the products. In his customer-facing Evangelist role, Ian is very involved with the design, production and testing of Enterprise class Unwired Solutions, that have been implemented using Sybase's Unwired tools for Sybase customers around the globe. In addition, Ian is a dedicated technical expert continually working with Sybase's key partners and clients to enhance the capabilities of the Unwired solutions that Sybase can offer to its customers. Ian can also be found on Twitter @ithain

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
We have Continuous Integration and we have Continuous Deployment, but what’s continuous across all of what we do is people. Even when tasks are automated, someone wrote the automation. So, Jayne Groll evangelizes about Continuous Everyone. Jayne is the CEO of the DevOps Institute and the author of Agile Service Management Guide. She talked about Continuous Everyone at the 2016 All Day DevOps conference. She describes it as "about people, culture, and collaboration mapped into your value streams....
In our first installment of this blog series, we went over the different types of applications migrated to the cloud and the benefits IT organizations hope to achieve by moving applications to the cloud. Unfortunately, IT can’t just press a button or even whip up a few lines of code to move applications to the cloud. Like any strategic move by IT, a cloud migration requires advanced planning.
Did you know that you can develop for mainframes in Java? Or that the testing and deployment can be automated across mobile to mainframe? In his session and demo at @DevOpsSummit at 21st Cloud Expo, Dana Boudreau, a Senior Director at CA Technologies, will discuss how increasingly teams are developing with agile methodologies, using modern development environments, and automating testing and deployments, mobile to mainframe.
“Why didn’t testing catch this” must become “How did this make it to testing?” Traditional quality teams are the crutch and excuse keeping organizations from making the necessary investment in people, process, and technology to accelerate test automation. Just like societies that did not build waterways because the labor to keep carrying the water was so cheap, we have created disincentives to automate. In her session at @DevOpsSummit at 20th Cloud Expo, Anne Hungate, President of Daring System...
As DevOps methodologies expand their reach across the enterprise, organizations face the daunting challenge of adapting related cloud strategies to ensure optimal alignment, from managing complexity to ensuring proper governance. How can culture, automation, legacy apps and even budget be reexamined to enable this ongoing shift within the modern software factory?
Most companies are adopting or evaluating container technology - Docker in particular - to speed up application deployment, drive down cost, ease management and make application delivery more flexible overall. As with most new architectures, this dream takes a lot of work to become a reality. Even when you do get your application componentized enough and packaged properly, there are still challenges for DevOps teams to making the shift to continuous delivery and achieving that reduction in cost ...
@DevOpsSummit at Cloud Expo taking place Oct 31 - Nov 2, 2017, at the Santa Clara Convention Center, Santa Clara, CA, is co-located with the 21st International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is ...
Docker is on a roll. In the last few years, this container management service has become immensely popular in development, especially given the great fit with agile-based projects and continuous delivery. In this article, I want to take a brief look at how you can use Docker to accelerate and streamline the software development lifecycle (SDLC) process.
Cloud adoption is often driven by a desire to increase efficiency, boost agility and save money. All too often, however, the reality involves unpredictable cost spikes and lack of oversight due to resource limitations. In his session at 20th Cloud Expo, Joe Kinsella, CTO and Founder of CloudHealth Technologies, tackled the question: “How do you build a fully optimized cloud?” He will examine: Why TCO is critical to achieving cloud success – and why attendees should be thinking holistically ab...
DevOps is good for organizations. According to the soon to be released State of DevOps Report high-performing IT organizations are 2X more likely to exceed profitability, market share, and productivity goals. But how do they do it? How do they use DevOps to drive value and differentiate their companies? We recently sat down with Nicole Forsgren, CEO and Chief Scientist at DORA (DevOps Research and Assessment) and lead investigator for the State of DevOps Report, to discuss the role of measure...
If you are part of the cloud development community, you certainly know about “serverless computing”, almost a misnomer. Because it implies there are no servers which is untrue. However the servers are hidden from the developers. This model eliminates operational complexity and increases developer productivity. We came from monolithic computing to client-server to services to microservices to serverless model. In other words, our systems have slowly “dissolved” from monolithic to function-by-func...
While some vendors scramble to create and sell you a fancy solution for monitoring your spanking new Amazon Lambdas, hear how you can do it on the cheap using just built-in Java APIs yourself. By exploiting a little-known fact that Lambdas aren’t exactly single-threaded, you can effectively identify hot spots in your serverless code. In his session at @DevOpsSummit at 21st Cloud Expo, Dave Martin, Product owner at CA Technologies, will give a live demonstration and code walkthrough, showing how ...
In his session at 20th Cloud Expo, Scott Davis, CTO of Embotics, discussed how automation can provide the dynamic management required to cost-effectively deliver microservices and container solutions at scale. He also discussed how flexible automation is the key to effectively bridging and seamlessly coordinating both IT and developer needs for component orchestration across disparate clouds – an increasingly important requirement at today’s multi-cloud enterprise.
Many organizations are now looking to DevOps maturity models to gauge their DevOps adoption and compare their maturity to their peers. However, as enterprise organizations rush to adopt DevOps, moving past experimentation to embrace it at scale, they are in danger of falling into the trap that they have fallen into time and time again. Unfortunately, we've seen this movie before, and we know how it ends: badly.
IT organizations are moving to the cloud in hopes to approve efficiency, increase agility and save money. Migrating workloads might seem like a simple task, but what many businesses don’t realize is that application migration criteria differs across organizations, making it difficult for architects to arrive at an accurate TCO number. In his session at 21st Cloud Expo, Joe Kinsella, CTO of CloudHealth Technologies, will offer a systematic approach to understanding the TCO of a cloud application...
API Security has finally entered our security zeitgeist. OWASP Top 10 2017 - RC1 recognized API Security as a first class citizen by adding it as number 10, or A-10 on its list of web application vulnerabilities. We believe this is just the start. The attack surface area offered by API is orders or magnitude larger than any other attack surface area. Consider the fact the APIs expose cloud services, internal databases, application and even legacy mainframes over the internet. What could go wrong...
With Cloud Foundry you can easily deploy and use apps utilizing websocket technology, but not everybody realizes that scaling them out is not that trivial. In his session at 21st Cloud Expo, Roman Swoszowski, CTO and VP, Cloud Foundry Services, at Grape Up, will show you an example of how to deal with this issue. He will demonstrate a cloud-native Spring Boot app running in Cloud Foundry and communicating with clients over websocket protocol that can be easily scaled horizontally and coordinate...
In his session at 20th Cloud Expo, Chris Carter, CEO of Approyo, discussed the basic set up and solution for an SAP solution in the cloud and what it means to the viability of your company. Chris Carter is CEO of Approyo. He works with business around the globe, to assist them in their journey to the usage of Big Data in the forms of Hadoop (Cloudera and Hortonwork's) and SAP HANA. At Approyo, we support firms who are looking for knowledge to grow through current business process, where even 1%...
The goal of Continuous Testing is to shift testing left to find defects earlier and release software faster. This can be achieved by integrating a set of open source functional and performance testing tools in the early stages of your software delivery lifecycle. There is one process that binds all application delivery stages together into one well-orchestrated machine: Continuous Testing. Continuous Testing is the conveyer belt between the Software Factory and production stages. Artifacts are m...
From manual human effort the world is slowly paving its way to a new space where most process are getting replaced with tools and systems to improve efficiency and bring down operational costs. Automation is the next big thing and low code platforms are fueling it in a significant way. The Automation era is here. We are in the fast pace of replacing manual human efforts with machines and processes. In the world of Information Technology too, we are linking disparate systems, softwares and tool...