-------- Original-Nachricht -------- Betreff: [isworld] Contents of Requirements Engineering Journal, Vol. 13, No. 3 Datum: Sun, 31 Aug 2008 02:03:15 -0400 Von: Pericles Loucopoulos p.loucopoulos@lboro.ac.uk Antwort an: Pericles Loucopoulos p.loucopoulos@lboro.ac.uk An: AISWORLD Information Systems World Network isworld@lyris.isworld.org
Requirements Engineering Journal Volume 13, No, 3 http://springerlink.com/content/102830/ Published Quarterly in Print and Electronically ISSN: 0947-3602 Published by Springer
RESEARCH PAPER 1: A cognitive semantics for the association construct, by Joerg Evermann
ABSTRACT: The unified modelling language (UML), besides its traditional use in describing software artifacts, is increasingly being used for conceptual modelling, the activity of describing an application domain. For models to be clear and unambiguous, every construct of the modelling language must have well-defined semantics, which is its mapping to elements of the semantic domain. When used for conceptual modelling, the semantic domain of UML is the application domain, as perceived by the modeller. Modellers perceive and structure their perceptions using cognitive concepts. This paper proposes a mapping of the UML association construct to those concepts. Implications for the use of the association construct for conceptual modelling are derived, a UML profile for conceptual modelling is presented, along with the results of a case study using the semantics and profile.
RESEARCH PAPER 2: Composing requirements specifications from multiple prioritized sources, by Ana Belén Barragáns Martínez, José J. Pazos Arias, Ana Fernández Vilas, Jorge García Duque, Martín López Nores, Rebeca P. Díaz Redondo and Yolanda Blanco Fernández
ABSTRACT: The formal methodology MultiSpec supports the evolution of software specifications gathered from multiple perspectives. A viewpoint-based approach is used to explicitly separate the descriptions provided by different stakeholders, and concentrate on identifying and resolving conflicts between them. The challenge addressed in this article consists in taking into account that some views may have greater degrees of relevance and, consequently, their opinion will have more importance when either obtaining the merged model or resolving the contradictions. To this end, we propose a priority-based approach, where such priority value is twofold. On the one hand, it considers external factors to the perspectives such as the importance assigned to each view by the analyst depending on who is specifying the view or the amount of stakeholders involved in that specification. On the other hand, this priority value also considers internal factors related to the quality of the views and, in order to be able to quantify this value, MultiSpec proposes two measures: coverage and density of each perspective which will be combined in a completeness value. The contributions of this approach will be clearly illustrated through a simple example.
RESEARCH PAPER 3: Requirements for tools for ambiguity identification and measurement in natural language requirements specifications, by Nadzeya Kiyavitskaya, Nicola Zeni, Luisa Mich and Daniel M. Berry
ABSTRACT: This paper proposes a two-step approach to identifying ambiguities in natural language (NL) requirements specifications (RSs). In the first step, a tool would apply a set of ambiguity measures to a RS in order to identify potentially ambiguous sentences in the RS. In the second step, another tool would show what specifically is potentially ambiguous about each potentially ambiguous sentence. The final decision of ambiguity remains with the human users of the tools. The paper describes several requirements-identification experiments with several small NL RSs using four prototypes of the first tool based on linguistic instruments and resources of different complexity and a manual mock-up of the second tool.
RESEARCH PAPER 4: Addressing privacy requirements in system design: the PriS method, BY Christos Kalloniatis, Evangelia Kavakli and Stefanos Gritzalis
ABSTRACT: A major challenge in the field of software engineering is to make users trust the software that they use in their every day activities for professional or recreational reasons. Trusting software depends on various elements, one of which is the protection of user privacy. Protecting privacy is about complying with user�s desires when it comes to handling personal information. Users� privacy can also be defined as the right to determine when, how and to what extend information about them is communicated to others. Current research stresses the need for addressing privacy issues during the system design rather than during the system implementation phase. To this end, this paper describes PriS, a security requirements engineering method, which incorporates privacy requirements early in the system development process. PriS considers privacy requirements as organisational goals that need to be satisfied and adopts the use of privacy-process patterns as a way to: (1) describe the effect of privacy requirements on business processes; and (2) facilitate the identification of the system architecture that best supports the privacy-related business processes. In this way, PriS provides a holistic approach from �high-level� goals to �privacy-compliant� IT systems. The PriS way-of-working is formally defined thus, enabling the development of automated tools for assisting its application.
SCOPE OF THE REQUIREMENTS ENGINEERING JOURNAL --------------------------------------------- The journal provides a focus for the dissemination of new results about the elicitation, representation and validation of requirements of software intensive information systems or applications. Theoretical and applied submissions are welcome, but all papers must explicitly address:(a) the practical consequences of the ideas for the design of complex systems and (b) how the ideas should be evaluated by the reflective practitioner.
The journal is motivated by a multi-disciplinary view that considers requirements not only in terms of software components specification but also in terms of activities for their elicitation, representation and agreement, carried out within an organisational and social context. To this end, contributions are sought from fields such as software engineering, information systems, occupational sociology, cognitive and organisational psychology, human-computer interaction, computer-supported cooperative work, linguistics and philosophy for work addressing specifically requirements engineering issues.
Specific topics include, but are not restricted to: - Theories and models relevant to requirements engineering - The intersection of requirements engineering with business engineering - Elicitation techniques including ethnography and social studies, task analysis, HCI approaches, user centered approaches, participatory design, facilitation techniques, cooperative requirements engineering - Analysis and valuation of cultural, political and organisational factors that affect requirements engineering practice - Architecture and functions of computer-based tools and environments for requirements engineering - Scenarios, design rationales and argumentation-based approaches - The state of practice, including evaluations of different approaches in industrial-size projects: papers on problems in requirements - Comprehensive reviews of current research and practice that synthesize findings not customarily integrated in the same place, and reports describing the unifying vision of research underway at particular institutions or research groups.
Indexed in Current Contents/ Engineering Computing & Technology, and ISI's Sciences Citation Index Expanded
Impact Factor: 1.538 (2007)
Interested authors should consult the journal's manuscript submission system at https://www.editorialmanager.com/rej/
The AISWorld LISTSERV is a service of the Association for Information Systems (http://www.aisnet.org). To unsubscribe, redirect, or change subscription options please go to http://lyris.isworld.org/. You are subscribed to AISworld as: neumann@wu-wien.ac.at. Each Sender assumes responsibility that his or her message conforms to the AISWorld LISTSERV policy and conditions of use available at http://lyris.isworld.org/isworldlist.htm.