Microservices Expo Authors: Elizabeth White, Mehdi Daoudi, Pat Romanski, Flint Brenton, Gordon Haff

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.

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 started a Master of Science in business analytics - that's the hot topic. We serve the business community around San Francisco so we educate the working professionals and this is where they all want to be," explained Judy Lee, Associate Professor and Department Chair at Golden Gate University, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
For over a decade, Application Programming Interface or APIs have been used to exchange data between multiple platforms. From social media to news and media sites, most websites depend on APIs to provide a dynamic and real-time digital experience. APIs have made its way into almost every device and service available today and it continues to spur innovations in every field of technology. There are multiple programming languages used to build and run applications in the online world. And just li...
There is a huge demand for responsive, real-time mobile and web experiences, but current architectural patterns do not easily accommodate applications that respond to events in real time. Common solutions using message queues or HTTP long-polling quickly lead to resiliency, scalability and development velocity challenges. In his session at 21st Cloud Expo, Ryland Degnan, a Senior Software Engineer on the Netflix Edge Platform team, will discuss how by leveraging a reactive stream-based protocol,...
The general concepts of DevOps have played a central role advancing the modern software delivery industry. With the library of DevOps best practices, tips and guides expanding quickly, it can be difficult to track down the best and most accurate resources and information. In order to help the software development community, and to further our own learning, we reached out to leading industry analysts and asked them about an increasingly popular tenet of a DevOps transformation: collaboration.
We call it DevOps but much of the time there’s a lot more discussion about the needs and concerns of developers than there is about other groups. There’s a focus on improved and less isolated developer workflows. There are many discussions around collaboration, continuous integration and delivery, issue tracking, source code control, code review, IDEs, and xPaaS – and all the tools that enable those things. Changes in developer practices may come up – such as developers taking ownership of code ...
The dynamic nature of the cloud means that change is a constant when it comes to modern cloud-based infrastructure. Delivering modern applications to end users, therefore, is a constantly shifting challenge. Delivery automation helps IT Ops teams ensure that apps are providing an optimal end user experience over hybrid-cloud and multi-cloud environments, no matter what the current state of the infrastructure is. To employ a delivery automation strategy that reflects your business rules, making r...
Cloud Governance means many things to many people. Heck, just the word cloud means different things depending on who you are talking to. While definitions can vary, controlling access to cloud resources is invariably a central piece of any governance program. Enterprise cloud computing has transformed IT. Cloud computing decreases time-to-market, improves agility by allowing businesses to adapt quickly to changing market demands, and, ultimately, drives down costs.
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
"CA has been doing a lot of things in the area of DevOps. Now we have a complete set of tool sets in order to enable customers to go all the way from planning to development to testing down to release into the operations," explained Aruna Ravichandran, Vice President of Global Marketing and Strategy at CA Technologies, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"We are an integrator of carrier ethernet and bandwidth to get people to connect to the cloud, to the SaaS providers, and the IaaS providers all on ethernet," explained Paul Mako, CEO & CTO of Massive Networks, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"NetApp's vision is how we help organizations manage data - delivering the right data in the right place, in the right time, to the people who need it, and doing it agnostic to what the platform is," explained Josh Atwell, Developer Advocate for NetApp, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
"Outscale was founded in 2010, is based in France, is a strategic partner to Dassault Systémes and has done quite a bit of work with divisions of Dassault," explained Jackie Funk, Digital Marketing exec at Outscale, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
"I focus on what we are calling CAST Highlight, which is our SaaS application portfolio analysis tool. It is an extremely lightweight tool that can integrate with pretty much any build process right now," explained Andrew Siegmund, Application Migration Specialist for CAST, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
Cavirin Systems has just announced C2, a SaaS offering designed to bring continuous security assessment and remediation to hybrid environments, containers, and data centers. Cavirin C2 is deployed within Amazon Web Services (AWS) and features a flexible licensing model for easy scalability and clear pay-as-you-go pricing. Although native to AWS, it also supports assessment and remediation of virtual or container instances within Microsoft Azure, Google Cloud Platform (GCP), or on-premise. By dr...
With continuous delivery (CD) almost always in the spotlight, continuous integration (CI) is often left out in the cold. Indeed, it's been in use for so long and so widely, we often take the model for granted. So what is CI and how can you make the most of it? This blog is intended to answer those questions. Before we step into examining CI, we need to look back. Software developers often work in small teams and modularity, and need to integrate their changes with the rest of the project code b...
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...