The Software Engineering Body of Knowledge (Swebok, 2004), notably a book with 200 pages mentions the word interoperability just twice, once as an example for a system requirement and the second time as the title of a standard for library data models. This stands in contrast to the challenges of globalizing economy that

Abstract. The new economy and business needs lead enterprises to be interoperable in order to be competitive and sustain new market opportunities that will result from cooperation with other enterprises. Easy ways to establish business with customers and suppliers or other enterprises are needed. Within this framework various studies on how to establish interoperability among specific enterprises, supply chains and virtual enterprises, or for specific sectors, have been successfully conducted and applied. The methodological proposal described in this paper will lead enterprises to achieve an advantage situation regarding their maturity level of interoperability. It supports enterprises to be prepared to interoperate, and this aspect can be a key issue for other enterprises to select them in new businesses or new collaborative projects.

Abstract. Some overall method characteristics, such as agility and scalability, have become increasingly important. These characteristics are different from existing method requirements which focus on the functional purposes of individual method chunks and overall methods. Characteristics like agility and scalability are often not embodied in the function of a single method chunk but are instead reflected in constraints over one or more method chunks, connections between method chunks and cross-cutting aspects of the overall method. We propose the concept of method tactics, which are techniques for achieving certain method quality attributes. We identify a list of method tactics focusing on agility and scalability by considering factors that affect these quality attributes. We validate the feasibility of using method tactics by applying them to traditional software development method chunks and deriving practices for agile development. We examine the effectiveness of the tactics by comparing our derived practices with existing practices for agile development. The comparison results show that most of the derived practices are found in existing agile methods. We also identify new practices that may have potential for use in agile methods. The results demonstrate initial support for our proposal for the use of method tactics, and for the extraction or invention of further cross-cutting primitive method tactics for more flexible situational method engineering. 1