ServiceTechMag.com > Archive > Issue LXVIII, November 2012
Download Issue
Download Full Service Technology Magazine PDF




From the Big Bang to Service Component Architecture -
Mass Customization in the Context of Universe and Life

Jeff Zhong

Jeff Zhong

In my recent trip to London to present at the 5th International SOA Symposium and 4th International Cloud Symposium, I observed more than 100 organizations participated with keynotes speakers from the US National Aeronautics and Space Administration (NASA) and European Space Agency. Service design principles have been applied successfully in many industries including Life Sciences and Astronomy. After the meetings, I visited University of Cambridge where Charles Darwin hypothesized biological evolution by natural selection and Stephen Hawking evangelized the Big Bang theory about the origin of the Universe. The trip prompted me to believe the Universe and life on earth were created and evolved by mass customization - a process to transform from singular, basic and generic to diversified, complex and more specific forms. I will first explore component architecture of the Universe and life, and then discuss the concept of Service Component Architecture, major vendors and business applications. After reading the article, the readers should have a holistic view about the Universe, life and Service Orientation. According to the Big Bang Theory, the Universe was created from a singularity of nothingness about 15 billion years ago. Initially the Universe was homogenous and then relatively basic particles such as bosons, quarks, leptons, neutrons, protons and electrons were created with smaller particles as the components for larger composites. The present Universe is composed of about...


Functional Size, Effort and Cost of the SOA Projects
with Function Points

Yuri Marx Pereira Gomes

Yuri Marx Pereira Gomes

For many years traditional software has been your size, effort and cost estimated using Function Point Analysis (FPA). It's the most clear and easier method because is based in the user perceived functionalities of a defined scope. Other techniques are based in mathematical formulas or in the technical factors like lines of code. User perceived functionalities are identified using requirements description, application GUIs and data models in traditional project, but when we initiate a project we have a business vision of the project only. In this case, we can use the estimated count method, so when the other artifacts are created, we will use detailed count in a new count of the project. SOA projects in your initial phase use the same documents of the traditional projects to estimate the size, but in the after phases, the artifacts are different. Many SOA projects don't have GUIs or traditional data models, but they have schema files (the data model) and WSDL files (the functionalities perceived by the user of the services). In this article we will see how we can estimate and count SOA projects using SOA artifacts, like Service Candidate descriptions, WSDL and XSD artifacts. The International Function Points Group (IFPUG) defines functions points as a "measure software size by quantifying the functionality provided to the user based solely on logical design and functional specifications". The Wikipedia defines a function point as...


Complex Method Design with HTTP and REST

Thomas Erl and Benjamin Carlyle

Thomas Erl

Benjamin Carlyle

The uniform contract establishes a set of base methods used to perform basic data communication functions. As we've explained, this high-level of functional abstraction is what makes the uniform contract reusable to the extent that we can position it as the sole, over-arching data exchange mechanism for an entire inventory of services. Besides its inherent simplicity, this part of a service inventory architecture automatically results in the baseline standardization of service contract elements and message exchange. The standardization of HTTP on the World Wide Web results in a protocol specification that describes the things that services and consumers "may", "should", or "must" do to be compliant with the protocol. The resulting level of standardization is intentionally only as high as it needs to be to ensure the basic functioning of the Web. It leaves a number of decisions as to how to respond to different conditions up to the logic within individual services and consumers. This "primitive" level of standardization is important to the Web where we can have numerous foreign service consumers interacting with third-party services at any given time. A service inventory, however, often represents an environment that is private and controlled within an IT enterprise. This gives us the opportunity to customize this standardization beyond the use of common and primitive methods. This form of customization can be justified when we have requirements for increasing the levels of predictability and quality-of-service beyond what the World Wide Web can...


Modeling and Analyzing Enterprise
Cloud Service Architecture - Part I

Longji Tang

Longji Tang

Enterprise Cloud Computing (ECC) is a new paradigm of distributed computing. ECC enables a new business model for enterprise computing and provides a new enterprise architectural style which brings new patterns and design principles into Enterprise Architecture (EA). The enterprise service-oriented architecture (ESOA) is an enterprise architectural style which is an abstraction of concrete enterprise service-oriented architectures. The ESOA includes SOA architectural elements, service design patterns as well as principles, and SOA quality attributes. Both styles share several common goals as well as conceptual foundations and they can connect and refine each other. This paper first presents a framework for modeling architectural styles and then defines a new hybrid architectural style, Enterprise Cloud Service Architecture (ECSA), by combining and refining the ESOA and ECC. The paper also specifies the ECSA formally and informally. We further analyze the consistency, instantiation, and extension of ECSA. Several case studies are also presented. With the globalization of the economic environment, the increasing complexity of business processes makes the enterprise information systems complicated. Enterprise service-oriented architecture (ESOA) is designed to tackle the complexity and build better architectures and solutions for enterprises. Conceptually, the ESOA is an architectural style which defines the concrete...


2017 2016 2015 2014 2013 2012 2011 2010 2009 2008 2007 2006