Showing posts with label Jurnal. Show all posts
Showing posts with label Jurnal. Show all posts

Handling Obstacles in Goal-Oriented Requirements Engineering (Rekayasa Perangkat Lunak)

Wednesday, 1 December 2010



Axel van Lamsweerde, Member, IEEE, and Emmanuel Letier

Abstract 
Requirements engineering is concerned with the elicitation of high-level goals to be achieved by the envisioned system, the refinement of such goals and their operationalization into specifications of services and constraints and the assignment of responsibilities for the resulting requirements to agents such as humans, devices, and software. Requirements engineering processes often result in goals, requirements, and assumptions about agent behavior that are too ideal; some of them are likely not to be satisfied from time to time in the running system due to unexpected agent behavior. The lack of anticipation of exceptional behaviors results in unrealistic, unachievable, and/or incomplete requirements. As a consequence, the software developed from those requirements will not be robust enough and will inevitably result in poor performance or failures, sometimes with critical consequences on the environment. This paper presents formal techniques for reasoning about obstacles to the satisfaction of goals, requirements, and assumptions elaborated in the requirements engineering process. A first set of techniques allows obstacles to be generated systematically from goal formulations and domain properties. A second set of techniques allows resolutions to be generated once the obstacles have been identified thereby. Our techniques are based on a temporal logic formalization of goals and domain properties; they are integrated into an existing method for goal-oriented requirements elaboration with the aim of deriving more realistic, complete, and robust requirements specifications. A key principle in this paper is to handle exceptions at requirements engineering time and at the goal level, so that more freedom is left for resolving them in a satisfactory way. The various techniques proposed are illustrated and assessed in the context of a real safety-critical system. 

Index Terms-Goal-oriented requirements engineering, high-level exception handling, obstacle-based requirements transformation, defensive requirements specification, specification refinement, lightweight formal methods.

Download full text here





READ MORE - Handling Obstacles in Goal-Oriented Requirements Engineering (Rekayasa Perangkat Lunak)

Sebuah Replikasi Extended Percobaan untuk Menilai Metode Inspeksi Persyaratan Perangkat Lunak Inspeksi

Friday, 19 November 2010

KRISTIAN SANDAHL
ZeLab, Ericsson Radio Systems AB, Box 12 48, S-581 12 Link¨oping, Sweden
OLA BLOMKVIST
Quality Technology and Management, Department of Mechanical Engineering, Link¨oping University, S-581 83 Link¨oping, Sweden
JOACHIM KARLSSON
Focal Point AB, Teknikringen 1E, S-583 30 Link¨oping, Sweden
CHRISTIAN KRYSANDER
Department of Computer and Information Science, Link¨oping University, S-581 83 Link¨oping, Sweden
MIKAEL LINDVALL
Department of Computer and Information Science, Link¨oping University, S-581 83 Link¨oping, Sweden
NICLAS OHLSSON
Department of Computer and Information Science, Link¨oping University, S-581 83 Link¨oping, Sweden
Abstrak
Kami telah melakukan suatu replikasi diperpanjang percobaan Porter-Votta-Basili membandingkan metode Skenario dan metode Checklist untuk memeriksa persyaratan spesifikasi menggunakan instrumen identik. Penelitian telah dilakukan dalam konteks pendidikan kita diwakili oleh suatu definisi yang lebih umum dari sebuah cacat dibandingkan dengan daftar cacat asli.

READ MORE - Sebuah Replikasi Extended Percobaan untuk Menilai Metode Inspeksi Persyaratan Perangkat Lunak Inspeksi

Foundations of Sequence-Based Software Specification

Wednesday, 17 November 2010

Stacy J. Prowell, Member, IEEE Computer Society, and Jesse H. Poore, Member, IEEE
Abstract—Rigorous specification early in the software development process can greatly reduce the cost of later development and maintenance, as well as provide an explicit means to manage risk and identify and meet safety requirements. Sequence-based software specification is a collection of techniques for implementing rigorous, practical software specification. The primary result of this research is the sequence enumeration method of specification writing. Straightforward, systematic enumeration of all sequences to produce an arguably complete, consistent, and traceably correct specification is made practical by controlling the growth of the process.



READ MORE - Foundations of Sequence-Based Software Specification

Scenario-Based Assessment of Nonfunctional Requirements

Wednesday, 3 November 2010

Andreas Gregoriades and Alistair Sutcliffe, Member, IEEE

Abstract—This paper describes a method and a tool for validating nonfunctional requirements in complex socio-technical systems. The System Requirements Analyzer (SRA) tool validates system reliability and operational performance requirements using scenario- based testing. Scenarios are transformed into sequences of task steps and the reliability of human agents performing tasks with computerized technology is assessed using Bayesian Belief Network (BN) models. The tool tests system performance within an envelope of environmental variations and reports the number of tests that pass a benchmark threshold. The tool diagnoses problematic areas in scenarios representing pathways through system models, assists in the  dentification of their causes, and supports comparison of alternative requirements specifications and system designs. It is suitable for testing socio-technical systems where operational scenarios are sequential and deterministic, in domains where designs are incrementally modified so set up costs of the BNs can be defrayed over multiple tests. Index Terms—Nonfunctional requirements validation, scenario-based testing, Bayesian belief networks, systems engineering.




READ MORE - Scenario-Based Assessment of Nonfunctional Requirements

Download jurnal

Tuesday, 19 October 2010

Download Jurnal penelitian yang diambil dari IEEE transaction dan Empirical Software Engineering:


An Extended Replication of an Experiment for Assessing Methods for Software Requirements Inspections
KRISTIAN SANDAHL ZeLab, Ericsson Radio Systems AB, Box 12 48, S-581 12 Link¨oping, Sweden
OLA BLOMKVIST Quality Technology and Management, Department of Mechanical Engineering, Link¨oping University, S-581 83 Link¨oping, Sweden
JOACHIM KARLSSON Focal Point AB, Teknikringen 1E, S-583 30 Link¨oping, Sweden
CHRISTIAN KRYSANDER Department of Computer and Information Science, Link¨oping University, S-581 83 Link¨oping, Sweden
MIKAEL LINDVALL Department of Computer and Information Science, Link¨oping University, S-581 83 Link¨oping, Sweden
NICLAS OHLSSON Department of Computer and Information Science, Link¨oping University, S-581 83 Link¨oping, Sweden
Abstract. We have performed an extended replication of the Porter-Votta-Basili experiment comparing the Scenario method and the Checklist method for inspecting requirements specifications using identical instruments. The experiment has been conducted in our educational context represented by a more general definition of a defect compared to the original defect list. Our study involving 24 undergraduate students manipulated three independent variables: detection method, requirements specification, and the order of the inspections. The dependent variable measured is the defect detection rate. We found the requirements specification inspected and not the detection method to be the most probable explanation for the variance in defect detection rate. This suggests that it is important to gather knowledge of how a requirements specification can convey an understandable view of the product and to adapt inspection methods accordingly. Contrary to the original experiment, we can not significantly support the superiority of the Scenario method. This is in accordance with a replication conducted by Fusaro, Lanubile and Visaggio, and might be explained by the lack of individual defect detection skill of our less experienced subjects.
Keywords: Controlled experiments, inspections, replicated study, method evaluation
Download this Journal here
Investigating the Role of Use Cases in the Construction of Class Diagrams
BENTE ANDA bentea@simula.no
DAG I. K. SJØBERG
Simula Research Laboratory, P.O. Box 134, 1325 Lysaker, Norway
Abstack
Several approaches have been proposed for the transition from functional requirements to objectoriented design. In a use case-driven development process, the use cases are important input for the identification of classes and their methods. There is, however, no established, empirically validated technique for the transition from use cases to class diagrams. One recommended technique is to derive classes by analyzing the use cases. It has, nevertheless, been reported that this technique leads to problems, such as the developers missing requirements and mistaking requirements for design. An alternative technique is to identify classes from a textual requirements specification and subsequently apply the use case model to validate the resulting class diagram. This paper describes two controlled experiments conducted to investigate these two approaches to applying use case models in an object-oriented design process. The first experiment was conducted with 53 students as subjects. Half of the subjects used a professional modelling tool; the other half used pen and paper. The second experiment was conducted with 22 professional software developers as subjects, all of whom used one of several modelling tools. The first experiment showed that applying use cases to validate class diagrams constructed from textual requirements led to more complete class diagrams than did the derivation of classes from a use case model. In the second experiment, however, we found no such difference between the two techniques. In both experiments, deriving class diagrams from the use cases led to a better structure of the class diagrams. The results of the experiments therefore show that the technique chosen for the transition from use cases to class diagrams affects the quality of the class diagrams, but also that the effects of the techniques depend on the categories of developer applying it and on the tool with which the technique is applied.
Keywords: UML, use cases, object-oriented design, modelling tool, controlled experiment, replicated experiment.
Download this Journal here
READ MORE - Download jurnal

 
 
 

Teman