The TAME Project: Towards Improvement-Oriented Software Environments

Basili, Victor R.; Rombach, H. Dieter

doi:10.1007/3-540-27662-9_8

Cited by 161 publications

(235 citation statements)

References 26 publications

Supporting

Mentioning

219

Contrasting

Unclassified

Order By: Relevance

“…However, providing a general experiment design is demanding, as the design depends on the respective subject and context. Apart from the general experiment process, several smaller guidelines exist to direct researchers through the process, e.g., the goal template from the TAME project (Basili & Rombach, 1988), experimentation packages providing reusable designs, templates, and so forth (e.g., in the context of self-organizing project teams (Kuhrmann & Münch, 2016b), we created such a template; another example can be found in Fucci, Turhan & Oivo (2015)), and, pragmatically, case study designs, which can be derived from, e.g., Runeson & Höst (2009), who provide advice on planning and a guideline on reporting case study research.…”

Section: Formal and Semi-formal Experimentsmentioning

confidence: 99%

Guidelines for using empirical studies in software engineering education

Fagerholm

Kuhrmann

Münch

2017

PeerJ Computer Science

View full text Add to dashboard Cite

Software engineering education is under constant pressure to provide students with industry-relevant knowledge and skills. Educators must address issues beyond exercises and theories that can be directly rehearsed in small settings. Industry training has similar requirements of relevance as companies seek to keep their workforce up to date with technological advances. Real-life software development often deals with large, software-intensive systems and is influenced by the complex effects of teamwork and distributed software development, which are hard to demonstrate in an educational environment. A way to experience such effects and to increase the relevance of software engineering education is to apply empirical studies in teaching. In this paper, we show how different types of empirical studies can be used for educational purposes in software engineering. We give examples illustrating how to utilize empirical studies, discuss challenges, and derive an initial guideline that supports teachers to include empirical studies in software engineering courses. Furthermore, we give examples that show how empirical studies contribute to high-quality learning outcomes, to student motivation, and to the awareness of the advantages of applying software engineering principles. Having awareness, experience, and understanding of the actions required, students are more likely to apply such principles under real-life constraints in their working life.

show abstract

Section: Formal and Semi-formal Experimentsmentioning

confidence: 99%

Guidelines for using empirical studies in software engineering education

Fagerholm

Kuhrmann

Münch

2017

PeerJ Computer Science

View full text Add to dashboard Cite

show abstract

“…According to the Goal-Question-Metric (GQM) paradigm [3], the goal of the experiment was to analyze the WUEP operationalization for the WebML development process, for the purpose of evaluating it with regard to its effectiveness, efficiency, perceived ease of use, and the evaluators' perceived satisfaction of it in comparison to Heuristic Evaluation (HE) from the viewpoint of a group of novice usability evaluators. The context of the experiment is the evaluation of two Web applications performed by novice inspectors.…”

Section: Overview Of the Original Experiments (Exp)mentioning

confidence: 99%

Usability Inspection in Model-Driven Web Development: Empirical Validation in WebML

Fernandez

Abrahão

Insfrán

et al. 2013

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. There is a lack of empirically validated usability evaluation methods that can be applied to models in model-driven Web development. Evaluation of these models allows an early detection of usability problems perceived by the end-user. This motivated us to propose WUEP, a usability inspection method which can be integrated into different model-driven Web development processes. We previously demonstrated how WUEP can effectively be used when following the Object-Oriented Hypermedia method. In order to provide evidences about WUEP's generalizability, this paper presents the operationalization and empirical validation of WUEP into another well-known method: WebML. The effectiveness, efficiency, perceived ease of use, and satisfaction of WUEP were evaluated in comparison to Heuristic Evaluation (HE) from the viewpoint of novice inspectors. The results show that WUEP was more effective and efficient than HE when detecting usability problems on models. Also, inspectors were satisfied when applying WUEP, and found it easier to use than HE.

show abstract

“…This is based on the Goal Question Metric (GQM) approach [19][20][21][22] and is performed by creating a mapping between Goals (Business Objectives) and Questions (Process Areas) using a reverse mapping between Process Areas (Questions) and Business Objectives (Goals).…”

Section: Rosetta Stone Meta-modelmentioning

confidence: 99%

“…Each potential benefit must be capable of being monitored in order to determine if the benefit is being received by the organization or not. GQM [19][20][21][22] is a well-established methodology for defining measurable goals and has been used to establish successful measurement programs in industry. Specifically with regard to the Rosetta Stone Methodology, each Goal is the analysis of a particular Benefit from the Benefits model.…”

Section: Rosetta Stone Meta-modelmentioning

confidence: 99%

The Rosetta Stone Methodology – A Benefits-Driven Approach to SPI

McLoughlin

Richardson

2010

Communications in Computer and Information Science

View full text Add to dashboard Cite

Abstract. The Rosetta Stone Methodology (RSM) has been developed which allows organizations to undertake Software Process Improvement (SPI) based on business-and organizational-driven goals and objectives. The methodology itself is fully customizable and allows organizations to make adjustments to the model where they feel it appropriate. To demonstrate the usefulness, appropriateness and practicality of this new approach, the Rosetta Stone IGSI-ISM to CMMI Instance mapping (RS-ICMMI) is developed. To aid in understanding, the Measurement and Analysis (MA) process area is used as an example of how to apply the methodology. The Rosetta Stone Methodology and the RS-ICMMI instance have been validated by experts.

show abstract

The TAME Project: Towards Improvement-Oriented Software Environments

Cited by 161 publications

References 26 publications

Guidelines for using empirical studies in software engineering education

Guidelines for using empirical studies in software engineering education

Usability Inspection in Model-Driven Web Development: Empirical Validation in WebML

The Rosetta Stone Methodology – A Benefits-Driven Approach to SPI

Contact Info

Product

Resources

About