Towards Improved Requirements Engineering with SysML and the User Requirements Notation

2016 ◽  
Author(s):  
Daniel Amyot ◽  
Amal Ahmed Anda ◽  
Malak Baslyman ◽  
Lysanne Lessard ◽  
Jean-Michel Bruel
Keyword(s):  
Requirements Engineering ◽  
User Requirements ◽  
User Requirements Notation

Separating the Wheat from the Chaff

2016 ◽  
Vol 28 (2) ◽  
pp. 124-141
Author(s):  
Adarsh Kumar Kakar
Keyword(s):  
Feature Selection ◽  
Empirical Study ◽  
Product Development ◽  
Requirements Engineering ◽  
User Satisfaction ◽  
Survey Method ◽  
User Requirements ◽  
Engineering Product ◽  
Time To Market ◽  
Software Product

When making a decision to add features to an existing software product in response to feature requests posted in user forums, it is important to pursue only those changes that deliver value to both the user and the producer. But selecting critical user requirements expressed as features requests is a challenging task. While excluding a high value requirement may mean losing customers to a competing product, including a requirement that is unneeded increases time to market and introduces unnecessary costs and complexity in the product. Keeping these issues in focus, promising methods of feature selection were first identified from a review of requirements engineering, product development and quality literatures. An empirical study was then conducted to investigate the efficacy of methods in separating the vital few user feature requests from the trivial many posted in user forums without adversely impacting user satisfaction. The result of the empirical study demonstrates that the Kano survey method has potential in separating the wheat from the chaff. The reasons for this finding is empirically investigated and discussed.

Formalizing Patterns with the User Requirements Notation

2011 ◽  
pp. 302-323 ◽  
Author(s):  
Gunter Mussbacher ◽  
Daniel Amyot ◽  
Michael Weiss
Keyword(s):  
Design Patterns ◽  
User Requirements ◽  
Trade Off ◽  
User Requirements Notation ◽  
Trade Offs ◽  
Combined Use ◽  
Particular Solution

Patterns need to be described and formalized in ways that enable the reader to determine whether the particular solution presented is useful and applicable to his or her problem in a given context. However, many pattern descriptions tend to focus on the solution to a problem, and not so much on how the various (and often conflicting) forces involved are balanced. This chapter describes the user requirements notation (URN), and demonstrates how it can be used to formalize patterns in a way that enables rigorous trade-off analysis while maintaining the genericity of the solution description. URN combines a graphical goal language, which can be used to capture forces and reason about trade-offs, and a graphical scenario language, which can be used to describe behavioral solutions in an abstract manner. Although each language can be used in isolation in pattern descriptions (and have been in the literature), the focus of this chapter is on their combined use. It includes examples of formalizing Design patterns with URN together with a process for trade-off analysis.

A Novel Approach to Change Management in Requirements Engineering Context

2015 ◽  
Vol 7 (3) ◽  
pp. 18-44 ◽  
Author(s):  
Soumia Bendakir ◽  
Nacereddine Zarour ◽  
Pierre Jean Charrel
Keyword(s):  
Change Management ◽  
Requirements Engineering ◽  
Source Code ◽  
User Requirements ◽  
Requirements Management ◽  
Multi Agent System ◽  
Novel Approach ◽  
Requirements Change ◽  
Multi Agent ◽  
The Cost

Requirements change management (RCM) is actually an inevitable task that might be considered in system development's life cycle, since user requirements are continuously evolving (some are added, others are modified or deleted). A large majority of studies have examined the issue of change, while most of them focused on the design and source code, requirements were often forgotten, even though, the cost of fixing the defect and introduced error due to the requirements is less higher compared to the cost of error in design and implementation. For this purpose, this work focuses on change issues in the requirements engineering (RE) context, which contains the complete initial specification. Properties such as adaptability, perception, and cooperation of the multi-agent system (MAS) allow managing changing requirements in a controlled manner. The main objective of this work is to develop an agent-oriented approach which will be effective in the requirements management to be adapted to changes in their environments.

Enterprise modeling with the Joint Use of User Requirements Notation and UML

2011 ◽  
pp. 45-66
Author(s):  
Anna Medve
Keyword(s):  
Process Modeling ◽  
Unified Modeling Language ◽  
Enterprise Modeling ◽  
User Requirements ◽  
Urn Model ◽  
Fully Integrated ◽  
Unified Modeling ◽  
User Requirements Notation ◽  
Design Documentation ◽  
Enterprise Models

This chapter introduces the User Requirements Notation (URN) standardized formal methods and its joint use with Unified Modeling Language (UML) in enterprise modeling. It argues that the joint use of URN and UML can enhance enterprise models and co-evolve with enterprise engineering processes. URN combines goals and scenarios to help reasoning and to capture user requirements prior to detailed design. Furthermore, URN can be integrated partially or entirely into an existing business process modeling approach, without replace current ways of creating and analyzing models in order to be useful. Modelled in the UML, a URN model may be incorporated into the rest of a system’s UML design documentation, seamlessly linking the documentation for the requirements elicitation part of a project to the whole and an be fully integrated with the rest of the design documentation for a software system.

Sign in / Sign up

Export Citation Format

Share Document