Welcome!

Microservices Expo Authors: Don MacVittie, Stackify Blog, Liz McMillan, Simon Hill, Dalibor Siroky

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
The nature of test environments is inherently temporary—you set up an environment, run through an automated test suite, and then tear down the environment. If you can reduce the cycle time for this process down to hours or minutes, then you may be able to cut your test environment budgets considerably. The impact of cloud adoption on test environments is a valuable advancement in both cost savings and agility. The on-demand model takes advantage of public cloud APIs requiring only payment for t...
"Codigm is based on the cloud and we are here to explore marketing opportunities in America. Our mission is to make an ecosystem of the SW environment that anyone can understand, learn, teach, and develop the SW on the cloud," explained Sung Tae Ryu, CEO of Codigm, 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.
High-velocity engineering teams are applying not only continuous delivery processes, but also lessons in experimentation from established leaders like Amazon, Netflix, and Facebook. These companies have made experimentation a foundation for their release processes, allowing them to try out major feature releases and redesigns within smaller groups before making them broadly available. In his session at 21st Cloud Expo, Brian Lucas, Senior Staff Engineer at Optimizely, discussed how by using ne...
Many enterprise and government IT organizations are realizing the benefits of cloud computing by extending IT delivery and management processes across private and public cloud services. But they are often challenged with balancing the need for centralized cloud governance without stifling user-driven innovation. This strategy requires an approach that fundamentally reshapes how IT is delivered today, shifting the focus from infrastructure to services aggregation, and mixing and matching the bes...
"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.
While we understand Agile as a means to accelerate innovation, manage uncertainty and cope with ambiguity, many are inclined to think that it conflicts with the objectives of traditional engineering projects, such as building a highway, skyscraper or power plant. These are plan-driven and predictive projects that seek to avoid any uncertainty. This type of thinking, however, is short-sighted. Agile approaches are valuable in controlling uncertainty because they constrain the complexity that ste...
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...
"This all sounds great. But it's just not realistic." This is what a group of five senior IT executives told me during a workshop I held not long ago. We were working through an exercise on the organizational characteristics necessary to successfully execute a digital transformation, and the group was doing their ‘readout.' The executives loved everything we discussed and agreed that if such an environment existed, it would make transformation much easier. They just didn't believe it was reali...
"We're developing a software that is based on the cloud environment and we are providing those services to corporations and the general public," explained Seungmin Kim, CEO/CTO of SM Systems Inc., 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.
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Agile has finally jumped the technology shark, expanding outside the software world. Enterprises are now increasingly adopting Agile practices across their organizations in order to successfully navigate the disruptive waters that threaten to drown them. In our quest for establishing change as a core competency in our organizations, this business-centric notion of Agile is an essential component of Agile Digital Transformation. In the years since the publication of the Agile Manifesto, the conn...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
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...
Enterprises are adopting Kubernetes to accelerate the development and the delivery of cloud-native applications. However, sharing a Kubernetes cluster between members of the same team can be challenging. And, sharing clusters across multiple teams is even harder. Kubernetes offers several constructs to help implement segmentation and isolation. However, these primitives can be complex to understand and apply. As a result, it’s becoming common for enterprises to end up with several clusters. Thi...
DevOps teams have more on their plate than ever. As infrastructure needs grow, so does the time required to ensure that everything's running smoothly. This makes automation crucial - especially in the server and network monitoring world. Server monitoring tools can save teams time by automating server management and providing real-time performance updates. As budgets reset for the New Year, there is no better time to implement a new server monitoring tool (or re-evaluate your current solution)....
We just came off of a review of a product that handles both containers and virtual machines in the same interface. Under the covers, implementation of containers defaults to LXC, though recently Docker support was added. When reading online, or searching for information, increasingly we see “Container Management” products listed as competitors to Docker, when in reality things like Rocket, LXC/LXD, and Virtualization are Dockers competitors. After doing some looking around, we have decided tha...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, 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.
The benefits of automation are well documented; it increases productivity, cuts cost and minimizes errors. It eliminates repetitive manual tasks, freeing us up to be more innovative. By that logic, surely, we should automate everything possible, right? So, is attempting to automate everything a sensible - even feasible - goal? In a word: no. Consider this your short guide as to what to automate and what not to automate.
identify the sources of event storms and performance anomalies will require automated, real-time root-cause analysis. I think Enterprise Management Associates said it well: “The data and metrics collected at instrumentation points across the application ecosystem are essential to performance monitoring and root cause analysis. However, analytics capable of transforming data and metrics into an application-focused report or dashboards are what separates actual application monitoring from relat...