ViewPoint oriented software development: Methods and viewpoints in requirements engineering

Finkelsteiin, Anthony; Goedicke, Michael; Kramer, Jeff; Niskier, Celso

doi:10.1007/3-540-53912-3_17

Cited by 20 publications

(25 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Model-based requirements engineering is often seen as an important part as it allows, among others, for full continuity across the entire engineering process [4]. As model-based documentation is often used from different requirements perspectives or to document the intentions of different stakeholders in different requirements models [5], inconsistencies between multiple requirements models can easily arise and need to be investigated and resolved by requirements engineers [6]. This particular challenge can often only be solved by manual validation, as automated approaches can only detect inconsistencies but not negotiate agreement between different stakeholders and thus, ensure the correctness of all requirements artifacts (cf.…”

Section: Motivation and Backgroundmentioning

confidence: 99%

On the Impact of the Model-Based Representation of Inconsistencies to Manual Reviews

Daun

Brings

Weyer

2017

Conceptual Modeling

View full text Add to dashboard Cite

To ensure fulfilling stakeholder wishes, it is crucial to validate the documented requirements. This is often complicated by the fact that the wishes and intentions of different stakeholders are somewhat contradictory, which manifests itself in inconsistent requirements. To aid requirements engineers in identifying and resolving inconsistent requirements, we investigated the usefulness for manual reviews of two different model-based representation formats for inconsistent requirements; one that represent the inconsistent requirements in separate diagrams and one that represents them integrated into one diagram using annotations. The results from a controlled experiment show that the use of such integrated review diagrams can significantly increase efficiency of manual reviews, without sacrificing effectiveness.

show abstract

Section: Motivation and Backgroundmentioning

confidence: 99%

On the Impact of the Model-Based Representation of Inconsistencies to Manual Reviews

Daun

Brings

Weyer

2017

Conceptual Modeling

View full text Add to dashboard Cite

show abstract

“…Goals are conditions to be satisfied by some aspect of a system or a system modification. Goals can be decomposed into and-or trees and can be used with respect to different viewpoints of a system [10,20]. The proposed notation allows goals to be added to the business layer of a model as boxes containing free format text.…”

Section: Extending Archimatementioning

confidence: 99%

Leap

Clark

Barn

Oussena

2011

Proceedings of the 4th India Software Engineering Conference

View full text Add to dashboard Cite

This paper proposes LEAP, a simple framework for Enterprise Architecture (EA) that views an organization as an engine that executes in terms of hierarchically decomposed communicating components. The approach allows all aspects of the architecture to be precisely defined using standard modelling notations. Given that the approach is simple and precisely defined it can form the basis for a wide range of EA analysis techniques including simulation, compliance and consistency checking. The paper defines the LEAP framework and shows that it can be used to represent the key features of ArchiMate whilst containing fewer orthogonal concepts. We also show that the precision of LEAP, achieved through the use of OCL, can be used to verify both the claims made for inter-layer relationships in EA models and for extensions to ArchiMate.

show abstract

“…Published literature shows that a number of approaches that allow requirement elicitation and analysis for data modeling have been developed; below we present only those that are widely used. Although not exhaustive, this selection is representative of both the range described in the relevant literature and of what is currently practiced in industry (Zowghi et al 2005): goal-oriented (Donzelli et al 2003;Mylopoulos et al 1999;Zhang et al 2007), function-based (Chandrasekaran et al 1996), and viewpoint-oriented (Finkelstein et al 1991a;Finkelstein et al 1991b;Kotonya 1999;Steen et al 2004). The comparison suggests that an extended approach that is informed by Activity Theory provides a more comprehensive framework to elicit and analyze the requirements for data modeling.…”

Section: Chemical Incident Response Data Model Developmentmentioning

confidence: 99%

Emergency Response Information System Interoperability: Development of Chemical Incident Response Data Model

Chen¹,

Sharman²,

Chakravarti³

et al. 2008

JAIS

View full text Add to dashboard Cite

Emergency response requires an efficient information supply chain for the smooth operations of intra-and interorganizational emergency management processes. However, the breakdown of this information supply chain due to the lack of consistent data standards presents a significant problem. In this paper, we adopt a theory-driven novel approach to develop an XML-based data model that prescribes a comprehensive set of data standards (semantics and internal structures) for emergency management to better address the challenges of information interoperability. Actual documents currently being used in mitigating chemical emergencies from a large number of incidents are used in the analysis stage. The data model development is guided by Activity Theory and is validated through a RFC-like process used in standards development. This paper applies the standards to the real case of a chemical incident scenario. Further, it complies with the national leading initiatives in emergency standards (National Information Exchange Model).The 9/11 commission reports (Kean 2004) as well as analyses of Hurricane Katrina (Townsend 2006) explicate how inadequate emergency response management is a major factor contributing to the lack of an effective response. Among the factors accountable for the observed inadequacy, the response information supply chain (ISC) that connects the response operations and stakeholders has been recognized for its critical role in supporting an effective response during critical incidents (Aylward et al. 2006;DHS et al. 2006;Frale 2005;Harrison et al. 2006; Weinshel 2006). While an efficient ISC demands smooth and seamless interoperability, the reality is that there are no standards that cater to specific types of incidents such as fire or chemical incidents. The efforts of bodies such as the Department of Homeland Security, Department of Justice, and Organization for the Advancement of Structured Information Standards (OASIS) have focused primarily on standards of a more general nature dealing with emergency management issues (e.g., call alert). These have been top-down impositions of standards. However, incidents of specific types and day-to-day operations are handled mostly at local levels (Chen et al. 2005;Chen et al. 2007a). They are typically governed by local regulations and practices and are managed through collaboration with first and second responder communities from neighboring counties and towns (Bui et al. 2001; Chen et al. 2007b;Kim et al. 2007). Therefore, there is a need to adopt a more comprehensive requirements gathering approach that takes into account the social aspects, contradictions, governance rules, division of labor, etc. This paper adopts a novel approach by adapting Activity Theory to provide a framework to develop emergency data standards. Activity Theory prompts consideration of issues and concerns such as communities and sub-communities and the contradictions that are not part of traditional approaches. We provide a more detailed discussion on the approach and the benefits of this...

show abstract

ViewPoint oriented software development: Methods and viewpoints in requirements engineering

Cited by 20 publications

References 4 publications

On the Impact of the Model-Based Representation of Inconsistencies to Manual Reviews

On the Impact of the Model-Based Representation of Inconsistencies to Manual Reviews

Leap

Emergency Response Information System Interoperability: Development of Chemical Incident Response Data Model

Contact Info

Product

Resources

About