Results 1 -
8 of
8
A metamodeling approach for reasoning about requirements
- In Proc. 4th European Conf. Model Driven Architecture: Foundations and Applications, volume 5095 of LNCS
, 2008
"... Abstract. In requirements engineering, there are several approaches for requirements modeling such as goal-oriented, aspect-driven, and system requirements modeling. In practice, companies often customize a given approach to their specific needs. Thus, we seek a solution that allows customization in ..."
Abstract
-
Cited by 8 (2 self)
- Add to MetaCart
(Show Context)
Abstract. In requirements engineering, there are several approaches for requirements modeling such as goal-oriented, aspect-driven, and system requirements modeling. In practice, companies often customize a given approach to their specific needs. Thus, we seek a solution that allows customization in a systematic way. In this paper, we propose a metamodel for requirements models (called core metamodel) and an approach for customizing this metamodel in order to support various requirements modeling approaches. The core metamodel represents the common concepts extracted from some prevalent approaches. We define the semantics of the concepts and the relations in the core metamodel. Based on this formalization, we can perform reasoning on requirements that may detect implicit relations and inconsistencies. Our approach for customization keeps the semantics of the core concepts intact and thus allows reuse of tools and reasoning over the customized metamodel. We illustrate the customization of our core metamodel with SysML concepts. As a case study, we apply the reasoning on requirements of an industrial mobile service application based on this customized core requirements metamodel.
Change Impact Analysis based on Formalization of Trace Relations for Requirements
"... Abstract. Evolving customer needs is one of the driving factors in software development. There is a need to analyze the impact of requirement changes in order to determine possible conflicts and design alternatives influenced by these changes. The analysis of the impact of requirement changes on rel ..."
Abstract
-
Cited by 2 (1 self)
- Add to MetaCart
(Show Context)
Abstract. Evolving customer needs is one of the driving factors in software development. There is a need to analyze the impact of requirement changes in order to determine possible conflicts and design alternatives influenced by these changes. The analysis of the impact of requirement changes on related requirements can be based on requirements traceability. In this paper, we propose a requirements metamodel with well defined types of requirements relations. This metamodel represents the common concepts extracted from some prevalent requirements engineering approaches. The requirements relations in the metamodel are used to trace related requirements for change impact analysis. We formalize the relations. Based on this formalization, we define change impact rules for requirements. As a case study, we apply these rules to changes in the requirements specification for Course Management System.
Toward Component Non-functional Interoperability Analysis: A UML-based and Goal-Oriented Approach
"... Component interoperability is the ability of two or more components to cooperate despite their differences in functional and non-functional aspects such as security or performance. However, the non-functional interoperability, for the lack of adequate methods, is often handled informally. This paper ..."
Abstract
-
Cited by 1 (0 self)
- Add to MetaCart
(Show Context)
Component interoperability is the ability of two or more components to cooperate despite their differences in functional and non-functional aspects such as security or performance. However, the non-functional interoperability, for the lack of adequate methods, is often handled informally. This paper presents a work-in-progress for analyzing and achieving component non-functional interoperability. The approach introduces the concept of nonfunctional required and provided interfaces (called NRI and NPI). The NRI specifies the NFRs the client component expects to be fulfilled while the NPI specifies the NFRs promised or currently supported by the supplier component. NRI and NRI are compared to determine interoperability at the NFR definition and implementation levels. The paper presents three tactics for resolving non-interoperability, including exploring for an alternate component that provides a more desirable interoperability, negotiating for more attainable NFRs that are currently supported, and adding a non-functional adapter to bridge the interoperability differences. The preliminary framework is demonstrated using an empirical study that integrates a student registration and a class scheduling systems to build a new conference management system to illustrate how to determine and adapt them for integration. 1
Enabling Trade-off Analysis of NFRs on Models of Embedded Systems
"... is a key factor in successful design of embedded systems. This is mainly due to the constraints and resource limitations in these systems. A design that cannot achieve functionality of the system under these limitations is actually a failure. Therefore, NFRs in design of embedded systems deserve spe ..."
Abstract
- Add to MetaCart
(Show Context)
is a key factor in successful design of embedded systems. This is mainly due to the constraints and resource limitations in these systems. A design that cannot achieve functionality of the system under these limitations is actually a failure. Therefore, NFRs in design of embedded systems deserve special attention. However, one big issue is that NFRs are interconnected and cannot be considered in isolation; especially that they can have direct impacts on each other such as security and performance. This means that a careful balance and trade-off analysis among NFRs is necessary. In this paper, we focus on this need and identify what information about NFRs is required in order to perform trade-off analysis. We propose and explain our in-progress approach to incorporate this information into system models in order to enable trade-off analysis. Our approach is based on UML profiling method to annotate model elements with necessary information.
Incorporating Non-Functional Requirements with UML Models
"... I hereby declare that I am the sole author of this thesis. I authorize the University of Waterloo to lend this thesis to other institutions or individuals for the purpose of scholarly research. ..."
Abstract
- Add to MetaCart
(Show Context)
I hereby declare that I am the sole author of this thesis. I authorize the University of Waterloo to lend this thesis to other institutions or individuals for the purpose of scholarly research.
Dependency based Process Model for Impact Analysis: A Requirement Engineering Perspective
"... Changing requirements of customer needs establishes the need to analyze impact of requirement changes. For success of any software requirement analysis is very essential. In this paper, we propose a four stage method engineering process which aims at estimating impact of change. The process model de ..."
Abstract
- Add to MetaCart
(Show Context)
Changing requirements of customer needs establishes the need to analyze impact of requirement changes. For success of any software requirement analysis is very essential. In this paper, we propose a four stage method engineering process which aims at estimating impact of change. The process model described is a linear layered model. Impact sets are computed by analyzing dependency tractability relations with other connected method components. The results produced provide two type of information (a) added, deleted, modified methods (b) depth (extent) of impact on the system.
A Survey of Non-Functional Requirements in Software Development Process
, 2008
"... Due to the enormous pressure towards deploying software as fast as possible, functional requirements have been the main focus of software development process at the expense of implementing non-functional requirements (NFRs) such as performance and security. Thus, in practice, NFRs have been observed ..."
Abstract
- Add to MetaCart
Due to the enormous pressure towards deploying software as fast as possible, functional requirements have been the main focus of software development process at the expense of implementing non-functional requirements (NFRs) such as performance and security. Thus, in practice, NFRs have been observed to be frequently neglected or forgotten in the software development process. However, NFRs is an important concept in requirements engineering which plays an essential role in the success or the failure of systems. NFRs introduce quality characteristics, but they also represent constraints under which the system must operate. So, the chances of success for the software system are maximized when NFRs are modeled since the initial phases of the development process. This article reviews the NFR concepts, relates them to the overall software development process and identifies new areas of further work. Keywords. Requirements engineering, Non-functional requirements, Software development process.
Integrating Non-Functional Requirement Modeling into Model Driven Development Method
"... Abstract-Model Driven Development views application development as a continuous transformation of models of the target system. However, non-functional requirements which are important for building user-satisfied software systems and have impacts on the software design, are not sufficiently considere ..."
Abstract
- Add to MetaCart
(Show Context)
Abstract-Model Driven Development views application development as a continuous transformation of models of the target system. However, non-functional requirements which are important for building user-satisfied software systems and have impacts on the software design, are not sufficiently considered in current MDD methods. This paper proposes an approach to modeling non-functional requirements, analyzing their impacts to the design and making a complement to the original design models for the MDD methods. First, existing UML models of the application's functional properties are taken as an input of the NFR modeling process, and with a NFR repository, the NFRs are refined and operationalized. Then based on the analysis result, modeling constructs are created to implement them, and the original UML models are reversely augmented by the result of NFR modeling. In particular, a metamodel is proposed to model the new constructs and facilitate the integration process. With this approach, we can finally get an integrated design model considering both functional requirements and non-functional requirements. The feasibility of the proposed approach is illustrated with an example of the design of a simplified credit card system. Keywords-MDD, Non-Functional Requirement, UML models, NFR Modeling, Model Integratioll I.
