Welcome!

Microservices Expo Authors: Anders Wallgren, Thanh Tran, Liz McMillan, Carmen Gonzalez, Elizabeth White

Related Topics: Java IoT, Industrial IoT, Microservices Expo, IBM Cloud, Weblogic, IoT User Interface

Java IoT: Article

Component Models in Java | Part 1

Component-oriented programming is a preferred solution to address the increasing complexity in developing software applications

A component is a reusable software entity. A component is a deployable piece of software that can be independently developed and maintained. In the previous article -Componentizing a Monolithic Application in Java, we discussed the need for componentizing applications to get the benefits of reusability and modularity. We also looked at how an E-Store application can be componentized using a simple component model developed by the authors using a factory whiteboard pattern and a simple repository.

In Part 1 of this article we will try to understand various component models in Java and provide a brief comparison of the features provided by them. Traditionally to explain component-based software engineering (CBSE) principles, popular component frameworks like CORBA, DCOM and JavaBeans are used. Instead of this traditional approach, this article will focus on the latest and widely adopted component models and frameworks specific to Java platform such as Enterprise JavaBeans Component Model (EJB), OSGi Component Model (OSGi), Spring Component Model (spring) and Component Model using Service Component Architecture (SCA).

In this article, first an introduction of component is given and types of components are explained and then the four component models are discussed in brief. At the end, a summary of the four component models is given.

Understanding Components
Component-oriented programming is a preferred solution to address the increasing complexity in developing software applications. Component oriented development has many advantages. Typically a component is accessed using an interface that is provided by the component. A component can also depend on other interfaces provided by other components for fulfilling the functionality. Components are developed, assembled and composed with the help of a standardized component model. Each component model has its own standards for development and composition. These component models provide are accompanied by component framework which provides the runtime environment where these components are executed.

Components can be classified into different types depending on where and how they are used. We try to classify the components into the following types based on their usage in N-tier architecture.

  • UI Components
    • Reusable components created for User Interface in applications. These components typically represent UI elements like form control - text field, radio button, data grid, table etc. used for managing the presentation tier of the application.
  • Business Components
    • Reusable components that contain the business logic of the application. The components are usually POJO based, developed and deployed according to a standardized component model. The model also provides the environment for execution of these components.
  • Persistence Components
    • Reusable components used in the persistence tier of an enterprise application. These components typically help in managing the persistence between the enterprise application and the data store.
  • Application Services Components
    • Reusable components which perform services like security, infrastructure management, transaction and validation for the application. These components are used along with the business components since they provide the application services required for the business components.

There are several models and frameworks available to develop each type of component. The focus of this article is on the business components; we will try to understand how the business components can be developed using the following standardized, matured and popularly used component models:

  • Enterprise JavaBeans (EJB)
  • Spring
  • OSGi
  • Service Component Architecture (SCA)

The objective is to give an introduction of these component models from the perspective of component principles and to understand the features provided by each of them. This article does not delve much into the details of the component models.

Enterprise JavaBeans Component Model
Enterprise JavaBeans (EJB) is a component model that is significant part of the Java Platform, Enterprise Edition. This is a standard from the JCP (Java Community Process) for representing business components in an n-tier enterprise application. Enterprise JavaBeans are distributed business components that contain the business logic of the enterprise application. The first release of the standard is EJB version 1.0. Much has changed in the EJB standard from its version 3.0. EJB has become truly lightweight, POJO based component model from EJB 3.0. This article will focus on the features of EJB with reference to EJB 3.0 specification. The classes and interfaces required for developing the components as per the model are packaged in EJB API.

An Enterprise JavaBeans component is a combination of an interface referred to as business interface and a class (POJO) containing the implementation for the interface referred to as EJB component.

Business Interface
The business interface of an EJB is a Plain Old Java Interface (POJI). The business interface for the enterprise bean contains the signature of the business methods. Business interface is the component interface which is exposed to the clients. The Enterprise JavaBeans model supports both local invocation and distributed invocation. So the component interface (business interface) can be used for local invocation and remote invocation.

EJB Component
The EJB component implements the business interface and contains the implementation of the methods in the business interface. The EJB component is used for the implementation of the business logic of the enterprise application and is available in the following types:

  • Stateless Session Bean
  • Stateful Session Bean
  • Singleton Session Bean
  • Message Driven Bean

Stateless session bean represents the business component which has no conversational state with the client. Stateless session bean components are not shared between clients. They are used for single method request/response communication between client and the component.

Stateful session bean is a business component that contains the conversational state for a single client. The conversational state of the component is maintained ONLY for a single client.

Singleton session bean is a new type of business component introduced from the recent specification of EJB. This is a business component which is shared between clients and supports concurrent access.

Message driven beans are business components that are designed to consume messages from messaging systems like Java Message Service (JMS). Message driven beans enable asynchronous communication and they get activated upon message arrival.

The types of beans are identified using metadata annotation in the source code or through the XML deployment descriptor. All the types of EJB components are POJO based and the following annotations are used:

  • @Stateless
  • @Stateful
  • @Singleton
  • @MessageDriven

EJB Container
Components are typically deployed into the container that provides runtime and services for them. The EJB component and the business interface are packaged into a JAR file and deployed in an EJB container. EJB containers manage the life cycle of the EJB components. Typically clients trying to access the component cannot create an object of the EJB directly, rather it gets a reference to the object created by the container. Containers are rich in features and provide all the services required for the components. The container acts as a registry having references of all components deployed in it.

Component Reference
Clients accessing EJB components (except Message Driven Beans) can be a remote client or local clients. A remote client is the one that accesses EJB components using remote protocol like RMI or IIOP. A local client is the one that accesses EJB components from the same JVM where the component is running.

Like any other component model, the EJB beans are not instantiated directly using the ‘new' operator. For accessing EJB components, dependency injection is used for getting a reference to the component deployed in the container. Dependency injection is based on the principles of ‘Inversion of Control.' The idea is to avoid the direct creation of objects using a ‘new' operator on the server-side Java. Dependency injection for EJB components is provided with the help of metadata annotation @EJB. The annotation @EJB specifies a reference to the business interface. When this annotation is used, the container will provide a reference of the component to the clients. A local client for EJB simply uses the @EJB to get a reference to the component.

A remote client for EJB, where injection is not possible has an alternate way of accessing EJB components. They have to use JNDI (Java Naming and Directory Interface) API for locating the components in the container with a string name usually called as JNDI name. The container will provide the reference of the component which will be used by the clients.

A Message Driven Bean can't be accessed by clients directly because they are asynchronous message listeners. This is a type of EJB component that is activated by the arrival of a message in a message destination. So clients cannot invoke any of the methods in the message driven bean.

Example to Understand EJB Component Model
The EJB component model discussed above can be understood with a simple example. Let us take the example of a Cart component used in online shopping. The Cart component has several methods like addItem, listItems, getTotalPrice and clearCart which helps to add items to the cart, list the items in the cart, get the total price of the components in the cart and clear the cart contents.

Note:  For benefit of those readers who read our earlier article on Componentizing Monolithic Application in Java, this is the same ShoppingCart component discussed in the article with little modifications. For simplicity, only a single component - Cart is used for demonstration purposes in this article.

Figure 1 - EJB Component Model - Cart Component Example

The business interface of the component in EJB model is a remote interface called ‘CartBeanRemote'.

package com.online.shopping;

import java.util.Collection;
import javax.ejb.Remote;

@Remote
public interface CartBeanRemote {
public void addItem(Product product, int quantity);
public Collection<Product> listItems();    
public double getTotalPrice();
public void clearCart();   
}

The business interface is implemented as a Stateful session EJB component ‘CartBean' because the component has to maintain the conversational state across method invocations for the client.

package com.online.shopping;

import java.util.Collection;
import java.util.HashMap;
import java.util.HashSet;
import java.util.Iterator;
import java.util.Map;
import java.util.Set;
import javax.ejb.Stateful;

@Stateful
public class CartBean implements CartBeanRemote {
Map<Product, Integer> items = new HashMap<Product, Integer>();      

@Override
public Collection<Product> listItems() {
HashSet<Product> contents = new HashSet<Product>();
Set<Product> set = items.keySet();
Iterator<Product> iterator = set.iterator();
while(iterator.hasNext()) {
contents.add(iterator.next());
}
return contents;
}  

@Override
public void addItem(Product product, int quantity) {
if(items.containsKey(product)) {
quantity +=items.get(product);
}
items.put(product, quantity);
}

@Override
public void clearCart() {
items.clear();
}

@Override
public double getTotalPrice() {
double totalPrice = 0;
for(Product product: items.keySet()) {
totalPrice+=product.getPrice()* items.get(product);           
}
return totalPrice;
}

}

The Stateful session bean is accessed by the client using a dependency injection @EJB annotation. The client need not create an object of the bean; rather the container will give the reference of the bean instance. Since this is a Stateful session bean, the bean maintains the conversational state of this client. The EJB component is stored internally in the container with a global JNDI name which by default is the name of the business interface-cartBeanRemote. Optionally the JNDI name can be specified as part of the @Stateful annotation. The container will look up internally for the bean with the global JNDI name (cartBeanRemote in this case) and a reference is injected into the business interface which is used by the client. The client is as simple as shown below.

package shoppingcartclient;

import com.online.shopping.CartBeanRemote;
import com.online.shopping.Product;
import java.util.Collection;
import javax.ejb.EJB;

public class ClientApp {

@EJB
private static CartBeanRemote cartBeanRemote;

public static void main(String[] args) {      

Product product = new Product();
product.setName("OSGi");
product.setPrice(550.00);
cartBeanRemote.addItem(product, 10);

Product newProduct = new Product();
newProduct.setName("EJB");
newProduct.setPrice(500.00);
cartBeanRemote.addItem(newProduct, 20);

Collection<Product> productItems = cartBeanRemote.listItems();
for(Product items: productItems) {
System.out.println(items.getName()+"******"+ items.getPrice());             
}            

System.out.println("Total Price of Cart Items: "+cartBeanRemote.getTotalPrice());

cartBeanRemote.clearCart();  

}
}

An alternative to the dependency injection as mentioned earlier, the JNDI API can be used to locate the business interface and the bean can be accessed using that. This is how the standardized EJB component Model simplifies the development, deployment and accessing of the components which is really a complex task without the model.

Spring Component Model
Spring is the most popular open source framework for building end-to-end enterprise applications in Java. Spring brings in greatest benefits like lightweight and modularity. This is achieved with the help of componentization of the framework. The Spring framework was initially written by Rod Johnson and was first released in the year June 2003. Spring components are POJO based and the benefit here is that the Spring components do not need heavyweight containers, only lightweight web containers (Servlet Containers...) are sufficient.

Spring is popular because of its support for Inversion of Control (IoC) features in the form of a Dependency Injection. As discussed earlier, dependency injection is the simplest form of representation of dependency between two classes without creating an object of the class using ‘new' operator. Dependency injection is the heart of the Spring framework. Apart from dependency injection, Spring framework provides support for AOP (Aspect Oriented Programming) as well. Spring framework provides the required APIs for development and deployment of the components.

Spring is slightly different component model from others in the fact that there is no concept of interface available directly to expose component methods. The component itself is used directly, without violating the component principles. Spring framework comprises of Spring Beans (the ‘Component') which is a POJO which is deployed and instantiated in a container called Spring Container which instantiates the bean components using a configuration file -XML file.

Spring Container
The Spring container is the core of the Spring framework. The container takes the responsibility of creating objects, configuring properties of objects, wiring them together and completely managing the life cycle of objects from its creation till destruction. The container completely depends on the configuration file which is XML file to perform any operations on the object.

Spring Container is built on the principles of IoC. The container uses dependency injection to manage the components deployed in them. The components are referred as Spring beans. The Spring container is of two types:

  • Spring BeanFactory Container
  • Spring ApplicationContext Container

The Spring BeanFactory container is the simplest container, an implementation of the Factory design pattern that provides the basic support for dependency injection and is defined by an interface called ‘BeanFactory' interface in the Spring API. Spring ApplicationContext container is an enhanced one which includes all the functionality provided by the BeanFactory container and provides additional features required for enterprise functionality. Hence for simple, lightweight applications, BeanFactory container is used whereas ApplicationContext container is the most preferred one.

The ApplicationContext container is advanced and is used for loading the bean definitions from the configuration file. This container provides several ways to load the configuration file. It allows loading XML file from a file system through FileSystemXmlApplicationContext, from the CLASSPATH using ClassPathXmlApplicationContext and from a web application through WebXmlApplicationContext. These contexts are crucial in instantiation of a bean.

Spring Beans
Spring Beans are the components that contain the business logic in the Spring framework. They are developed and deployed in the spring container which manages the life cycle of the beans. The instantiation of beans is managed by the container with the help of configuration file. Spring Beans are POJOs and are categorized into two types only at the time of instantiation:

  • Singleton
  • Prototype

If Singleton, only one single instance of the bean is created per Spring container. The single instance is cached and used for subsequent requests. If Prototype, instances can be created in any number based on the requests. By default, the spring bean is Singleton in nature. The type of the bean to be instantiated is decided by the entry in the configuration XML file.

Spring Configuration
Spring configuration is an XML file that is popularly known as a Bean Configuration file. This configuration file can have any name, but is usually referred to as ‘Beans.xml' and is critical in managing bean instances. Spring container loads the XML file and manages the beans referred in the file. Actually Spring provides three ways of configuration as mentioned below:

  • XML-based configuration file
  • Annotation based configuration
  • Java-based configuration

However the XML-based configuration file is commonly used. The XML file contains the configuration metadata that is used by the container for creating a bean instance, managing bean's lifecycle methods and bean's dependencies. Some of the important metadata that goes as part of the configuration file are listed below:

  • id - Id for the bean
  • class - Specified the bean class
  • name - Id for the bean by a name
  • scope - Scope of the bean objects - singleton, prototype, request, session
  • lazy-init - Bean will be initialized only during the first request
  • init-method - Method invoked after initialization of the bean
  • destroy-method - Method invoked before the destruction of the bean instance
  • constructor-arg - Used for injecting dependencies
  • properties - Used for injecting dependencies
  • autowire - Used for injecting dependencies

Example to Understand Spring Component Model
The Spring Component model can be understood with the same shopping Cart example discussed in the EJB component model.

Figure 2 - Spring Component Model - Cart Component Example

The CartBean is a POJO with the same methods discussed earlier. The spring bean need not implement any interfaces.

package com.online.shopping;

import java.util.Collection;
import java.util.HashMap;
import java.util.HashSet;
import java.util.Iterator;
import java.util.Map;
import java.util.Set;

public class CartBean {
Map<Product, Integer> items = new HashMap<Product, Integer>();

public Collection<Product> listItems() {       
return items.keySet();
}

public void addItem(Product product, int quantity) {
if (items.containsKey(product)) {
quantity += items.get(product);
}
items.put(product, quantity);
}

public void clearCart() {
items.clear();
}

public double getTotalPrice() {
double totalPrice = 0;
for (Product product : items.keySet()) {
totalPrice += product.getPrice() * items.get(product);
}
return totalPrice;
}
}

The configuration file which is an XML file for the CartBean is referred as ‘Beans.xml'.  The XML file is placed under the source folder of the project. As mentioned earlier, the XML file is used for uniquely identifying beans and creation of objects. When the Spring application is loaded in the memory, the XML file is read first and the container uses this configuration file to create all the required beans and assigns id as per the tags present the configuration file. The XML file used in this example is mentioned below. The ‘CartBean' is assigned a unique id ‘cartBean'. Every bean is loaded and identified using the <bean> tag in the XML file and this tag can have child tags like <property>.

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd">

<bean id="cartBean" class="com.online.shopping.CartBean" />

</beans>

To access the CartBean, the id of the bean and the context should be available for the client programs. First, the client tries to create an application context appropriately (File or ClassPath or Web). In this example, the client uses ClassPathXmlApplicationContext API that helps in loading the ‘Beans.xml' from the CLASSPATH (the XML file must be available in the CLASSPATH) and based on the information available in the configuration file, the container takes the responsibility of creating and initializing the beans, cartBean in this case.  The context plays an important role to get the reference of the bean since there is no interface. The bean reference is obtained using getBean() method of the context object.

package com.shopping.client;

import java.util.Collection;

import org.springframework.context.ApplicationContext;
import org.springframework.context.support.ClassPathXmlApplicationContext;

import com.online.shopping.CartBean;
import com.online.shopping.Product;

public class ClientApp {

/**
* @param args
*/
public static void main(String[] args) {
ApplicationContext context = new ClassPathXmlApplicationContext("Beans.xml");
CartBean cartBean = (CartBean) context.getBean("cartBean");

Product product = new Product();
product.setName("OSGi");
product.setPrice(550.00);
cartBean.addItem(product, 10);

Product newProduct = new Product();
newProduct.setName("Spring");
newProduct.setPrice(550.00);
cartBean.addItem(newProduct, 10);

Collection<Product> productItems = cartBean.listItems();
for(Product items: productItems) {
System.out.println(items.getName()+"******"+ items.getPrice());             
}            

System.out.println("Total Price of Cart Items: "+cartBean.getTotalPrice());

cartBean.clearCart();
}

}

Thus, Spring framework provides a simplified way to create components with the help of Spring factory, configuration XML file and the Spring container. Developing components has really become easy with the help of the Spring framework.

More Stories By Piram Manickam

Piram Manickam works at Infosys Limited. He would like to acknowledge and thank Sangeetha S, a beloved colleague and friend, for her invaluable contributions in this work.

More Stories By Subrahmanya SV

Subrahmanya SV works at Infosys Limited. He would like to acknowledge and thank Sangeetha S, a beloved colleague and friend, for her invaluable contributions in this work.

More Stories By S Sangeetha

S Sangeetha is a Senior Technical Architect at the E-Commerce Research Labs at Infosys Limited. She has over 15 years of experience in architecture, design and development of enterprise Java applications. She is also involved in enhancing the technical skills of Architects at Infosys. She has co-authored a book on ‘J2EE Architecture’ and also has written numerous articles on Java for various online Java forums like JavaWorld, java.net, DevX.com and internet.com. She can be reached at [email protected]

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
Automation is a critical component of DevOps and Continuous Delivery. This morning on #c9d9 we discussed CD Automation and how you can apply Automation to accelerate release cycles, improve quality, safety and governance? What is the difference between Automation and Orchestration? Where should you begin your journey to introduce both?
While there has been much ado about interoperability, there are still no real solutions, same as last year and the year before that. The large EHR vendors who continue to dominate the market still maintain that interoperability is all but solved, still can't connect EHRs across the continuum causing frustration by providers and a disservice to patients. The ONC pays lip service to the problem, but that is about it. It is time for the healthcare industry to consider alternatives like middleware w...
SYS-CON Events announced today the Docker Meets Kubernetes – Intro into the Kubernetes World, being held June 9, 2016, in conjunction with 18th Cloud Expo | @ThingsExpo, at the Javits Center in New York, NY. Register for 'Docker Meets Kubernetes Workshop' Here! This workshop led by Sebastian Scheele, co-founder of Loodse, introduces participants to Kubernetes (container orchestration). Through a combination of instructor-led presentations, demonstrations, and hands-on labs, participants learn ...
The pace of innovation, vendor lock-in, production sustainability, cost-effectiveness, and managing risk… In his session at 18th Cloud Expo, Dan Choquette, Founder of RackN, will discuss how CIOs are challenged finding the balance of finding the right tools, technology and operational model that serves the business the best. He will discuss how clouds, open source software and infrastructure solutions have benefits but also drawbacks and how workload and operational portability between vendors...
With major technology companies and startups seriously embracing IoT strategies, now is the perfect time to attend @ThingsExpo 2016 in New York and Silicon Valley. Learn what is going on, contribute to the discussions, and ensure that your enterprise is as "IoT-Ready" as it can be! Internet of @ThingsExpo, taking place Nov 3-5, 2015, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with 17th Cloud Expo and will feature technical sessions from a rock star conference faculty ...
The 19th International Cloud Expo has announced that its Call for Papers is open. Cloud Expo, to be held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, brings together Cloud Computing, Big Data, Internet of Things, DevOps, Containers, Microservices and WebRTC to one location. With cloud computing driving a higher percentage of enterprise IT budgets every year, it becomes increasingly important to plant your flag in this fast-expanding business opportunity. Submit y...
Our CTO, Anders Wallgren, recently sat down to take part in the “B2B Nation: IT” podcast — the series dedicated to serving the IT professional community with expert opinions and advice on the world of information technology. Listen to the great conversation, where Anders shares his thoughts on DevOps lessons from large enterprises, the growth of microservices and containers, and more.
Internet of @ThingsExpo, taking place November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with the 19th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world and ThingsExpo New York Call for Papers is now open.
@DevOpsSummit taking place June 7-9, 2016 at Javits Center, New York City, and Nov 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with the 18th International @CloudExpo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world.
A strange thing is happening along the way to the Internet of Things, namely far too many devices to work with and manage. It has become clear that we'll need much higher efficiency user experiences that can allow us to more easily and scalably work with the thousands of devices that will soon be in each of our lives. Enter the conversational interface revolution, combining bots we can literally talk with, gesture to, and even direct with our thoughts, with embedded artificial intelligence, wh...
IoT generates lots of temporal data. But how do you unlock its value? How do you coordinate the diverse moving parts that must come together when developing your IoT product? What are the key challenges addressed by Data as a Service? How does cloud computing underlie and connect the notions of Digital and DevOps What is the impact of the API economy? What is the business imperative for Cognitive Computing? Get all these questions and hundreds more like them answered at the 18th Cloud Expo...
Just last week a senior Hybris consultant shared the story of a customer engagement on which he was working. This customer had problems, serious problems. We’re talking about response times far beyond the most liberal acceptable standard. They were unable to solve the issue in their eCommerce platform – specifically Hybris. Although the eCommerce project was delivered by a system integrator / implementation partner, the vendor still gets involved when things go really wrong. After all, the vendo...
As enterprises around the world struggle with their digital transformation efforts, many are finding that innovative digital teams are moving much faster than their hidebound IT organizations. Rather than struggling to convince traditional IT to get with the digital program, executives are taking advice from IT research firm Gartner, and encouraging existing IT to continue in their desultory ways. However, many CIOs are realizing the dangers of following Gartner’s advice. The central challenge ...
The initial debate is over: Any enterprise with a serious commitment to IT is migrating to the cloud. But things are not so simple. There is a complex mix of on-premises, colocated, and public-cloud deployments. In this power panel at 18th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists will look at the present state of cloud from the C-level view, and how great companies and rock star executives can use cloud computing to meet their most ambitious and disruptive business ...
The demand for organizations to expand their infrastructure to multiple IT environments like the cloud, on-premise, mobile, bring your own device (BYOD) and the Internet of Things (IoT) continues to grow. As this hybrid infrastructure increases, the challenge to monitor the security of these systems increases in volume and complexity. In his session at 18th Cloud Expo, Stephen Coty, Chief Security Evangelist at Alert Logic, will show how properly configured and managed security architecture can...
You might already know them from theagileadmin.com, but let me introduce you to two of the leading minds in the Rugged DevOps movement: James Wickett and Ernest Mueller. Both James and Ernest are active leaders in the DevOps space, in addition to helping organize events such as DevOpsDays Austinand LASCON. Our conversation covered a lot of bases from the founding of Rugged DevOps to aligning organizational silos to lessons learned from W. Edwards Demings.
Agile teams report the lowest rate of measuring non-functional requirements. What does this mean for the evolution of quality in this era of Continuous Everything? To explore how the rise of SDLC acceleration trends such as Agile, DevOps, and Continuous Delivery are impacting software quality, Parasoft conducted a survey about measuring and monitoring non-functional requirements (NFRs). Here's a glimpse at what we discovered and what it means for the evolution of quality in this era of Continuo...
When I talk about driving innovation with self-organizing teams, I emphasize that such self-organization includes expecting the participants to organize their own teams, give themselves their own goals, and determine for themselves how to measure their success. In contrast, the definition of skunkworks points out that members of such teams are “usually specially selected.” Good thing he added the word usually – because specially selecting such teams throws a wrench in the entire works, limiting...
Korean Broadcasting System (KBS) will feature the upcoming 18th Cloud Expo | @ThingsExpo in a New York news documentary about the "New IT for the Future." The documentary will cover how big companies are transmitting or adopting the new IT for the future and will be filmed on the expo floor between June 7-June 9, 2016, at the Javits Center in New York City, New York. KBS has long been a leader in the development of the broadcasting culture of Korea. As the key public service broadcaster of Korea...
SYS-CON Events announced today TechTarget has been named “Media Sponsor” of SYS-CON's 18th International Cloud Expo, which will take place on June 7–9, 2016, at the Javits Center in New York City, NY, and the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. TechTarget is the Web’s leading destination for serious technology buyers researching and making enterprise technology decisions. Its extensive global networ...