Generic Process Model for the Structured Analysis of Methods: A Method Engineering Approach for the Analysis of RTO Capability Methodologies

Author(s):  
S. B. Goyal

In situational method engineering (SME), there are two core intentions that method engineers look for: 1) a set method engineering goal that is the kind of method needed and 2) a method allowing him to satisfy this goal. This chapter can capture method engineering's goal using a generic process model (GPM) that guides the method engineering in the definition of his project method engineering goal and in the selection approach that best allows him to achieve it. The authors wish to move to functional method engineering so as to explore the context of method engineering/situational method engineering more fully based on functional and non-functional method situation. The implications of the approach on CAME tool design are considered and illustrated through a running example.


2014 ◽  
Vol 18 (03) ◽  
pp. 1440004 ◽  
Author(s):  
VICTORIA KAYSER ◽  
KERSTIN GOLUCHOWICZ ◽  
ANTJE BIERWISCH

Technology roadmapping is a well-established method used in strategy development to map alternative future paths, while text mining offers untapped potentials concerning early detection and environmental scanning. In this paper, the roadmapping process is split into different steps in order to analyse which text mining methods could add further value within each. This leads to a two-layered process model, which includes text mining techniques to systematically integrate external information in ongoing roadmapping processes. Textual data can be used for a structured analysis and exploration of thematic fields and an objective, quantitative summary of actual developments. To demonstrate some of the benefits, the field of "cloud computing" is used to illustrate the procedure. As this article will show, the results provided by this approach extend the existing methodology, integrates an external view and complements expert opinion.


Author(s):  
Laila Niedrite ◽  
Maris Solodovnikova Treimanis ◽  
Liga Grundmane

There are many methods in the area of data warehousing to define requirements for the development of the most appropriate conceptual model of a data warehouse. There is no universal consensus about the best method, nor are there accepted standards for the conceptual modeling of data warehouses. Only few conceptual models have formally described methods how to get these models. Therefore, problems arise when in a particular data warehousing project, an appropriate development approach, and a corresponding method for the requirements elicitation, should be chosen and applied. Sometimes it is also necessary not only to use the existing methods, but also to provide new methods that are usable in particular development situations. It is necessary to represent these new methods formally, to ensure the appropriate usage of these methods in similar situations in the future. It is also necessary to define the contingency factors, which describe the situation where the method is usable.This chapter represents the usage of method engineering approach for the development of conceptual models of data warehouses. A set of contingency factors that determine the choice between the usage of an existing method and the necessity to develop a new one is defined. Three case studies are presented. Three new methods: userdriven, data-driven, and goal-driven are developed according to the situation in the particular projects and using the method engineering approach.


Sign in / Sign up

Export Citation Format

Share Document