Titlebook: Requirements Engineering: Foundation for Software Quality; 19th International W Joerg Doerr,Andreas L. Opdahl Conference proceedings 2013 S

緯度

The Emergence of Mutual and Shared Understanding in the System Development Process on the system they develop (shared understanding) in order to collaborate effectively. . In this paper we analyse extent and forms of (lacking) mutual understanding according to the periods in the process of conceptual change. . We analyse the communication of a multidisciplinary team while develop

公共汽車

Highlighting Stakeholder Communities to Support Requirements Decision-Makingof collaborative working tools that facilitated the participation of stakeholders (and especially end-users). These tools create new opportunities of practice regarding requirement elicitation. . Nevertheless, they result in an information overload lacking structure and semantics. Consequently, requ

auxiliary

Choosing Compliance Solutions through Stakeholder Preferences such as conditions and derogations that generate a space of possible compliance alternatives. During requirements engineering, an analyst has to select one of these compliance alternatives and ensure that the requirements specification she is putting together complies with that alternative. However

synovium

忙碌

Mapping i* within UML for Business Modelingng IT solutions at best, to produce a documentation of the company’s “savoir-faire” and to look for possible optimizations. The . discipline of the . (.) has enriched the semantic of the . (.) use case diagrams for the special purpose of representing the organization’s processes with accurate elemen

Reclaim

Risk Identification at the Interface between Business Case and Requirementscitation. Unfortunately, projects still frequently fail to achieve commercial success, responsibility is often unknown, and requirements engineers may be deemed responsible for mistakes made by others. [.] There is neither empirical evidence available from a post-mortem risk analysis for projects th

Bravado

藥物

reqT.org – Towards a Semi-Formal, Open and Scalable Requirements Modeling Tooled formalism. [.] The metamodel of reqT and its main features are presented and modeling examples are provided together with a discussion on initial experiences from student projects, limitations and directions of further research.

斜

0302-9743 y; traceability; requirements engineering and business/goals; requirements engineering and software development; requirements engineering in practice; product lines and product management.978-3-642-37421-0978-3-642-37422-7Series ISSN 0302-9743 Series E-ISSN 1611-3349

WATER

Highlighting Stakeholder Communities to Support Requirements Decision-Makingattices to identify relevant groups of stakeholders depending on their past participation. . These groups can be used to enable facilitated decision-making and handling of requirements. We detail the different steps and the possible configurations, using an example inspired by a collaborative software development environment.