A reuse based approach for requirements engineering

Roudiès, Ounsa; Fredj, Mounia

doi:10.1109/aiccsa.2001.934040

Cited by 11 publications

(7 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Requirements reuse can provide an enhanced opportunity for reusing the software components. Moreover, when the reusable components are identified "at the source", the reuse is optimized [5].…”

Section: Requirements Analysismentioning

confidence: 99%

See 1 more Smart Citation

Architecture-based problem frames constructing for software reuse

Wang

Qian

Liu

2006

Proceedings of the 2006 International Workshop on Advances and Applications of Problem Frames

View full text Add to dashboard Cite

Reusability is not universal property of program codes. The problem frames can support the software component reuse effectively. The problem frames approach provides an opportunity for software developers to gain experience and expertise for problem domain. This paper proposes architecturebased problem frames constructing process that results in traceable problem patterns (business patterns and requirements patterns), and the traceability between problem space and software requirements is established as the side effect of the problem frames constructing process. The architecture-based problem frames constructing can integrate with architecture-based software design process seamlessly. The relationships between context and requirements are identified explicitly, so that the problem frames are traceable and reusable.

show abstract

Section: Requirements Analysismentioning

confidence: 99%

“…Pattern is "know-how" oriented that provides problem, solution, and engineering guidance to reuse them. Other forms of reusable components (i.e., software components) are "know" oriented [5]. The context and problem of the pattern make it easy for the developers to retrieve the right solution.…”

Section: Introductionmentioning

confidence: 99%

Architecture-based problem frames constructing for software reuse

Wang

Qian

Liu

2006

Proceedings of the 2006 International Workshop on Advances and Applications of Problem Frames

View full text Add to dashboard Cite

show abstract

“…The main ones related to requirements are: (1) Many users don't define correctly what they want. (2) Requirements are changing frequently. (3) There is no enough time to analyze user requirements.…”

Section: Introductionmentioning

confidence: 99%

“…More and more works try to integrate it throughout the whole cycle of production, from the phase of requirements expression to the phase of maintenance. In the context of Requirements Engineering (RE), reuse is effective in particular because it can help to define requirements explicitly and to anticipate requirements change [1] [2].…”

Section: Introductionmentioning

confidence: 99%

Eliciting Potential Requirements with Feature-Oriented Gap Analysis

Ahn

Chong

2006

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Software reuse has long been paid attentions as an effective way to improve software quality and productivity. In the context of Requirements Engineering (RE), a reuse approach is effective in particular because it can help to define requirements and to anticipate requirements change. We propose a feature-oriented gap analysis method to elicit potential requirements from various stakeholders. We use feature modeling, which are an important concept in software product line, to identify reusable requirements elements. To achieve our goal, we present (1) a meta-model of reusable requirements elements, (2) gap analysis between new collected requirements and reused requirements in the repository, and (3) a potential requirements elicitation process with featureoriented gap analysis. This process is a set of sequential procedures to elicit potential requirements in addition to users' Plus minus interest (PMI).

show abstract

“…The simplicity of a pattern and its "small size" make it easy to understand, integrate, and reuse. Pattern is "know-how" oriented that provides both solution and engineering guidance to reuse them [6].…”

Section: Introductionmentioning

confidence: 99%

The Reusable Software Component Development Based on Pattern-Oriented

Chengjion

2012

2012 Fourth International Conference on Computational Intelligence and Communication Networks

View full text Add to dashboard Cite

Since early days, software reuse has been thought as a key strategy for reducing development costs and improving quality. Recent years, software reuse has been promoted by component-based development method. However, software reuse does not reach its full potential due to lack of the traceability between software components and business goals. Traceability is a key factor for reusability of software components. In this paper, we propose the pattern-oriented development approach that results in a component model. Architecture is used to describe component composition, and the links between components are defined formally. Patterns are used to describe the development expertise. The traceability between different models at different abstract levels is created as the side effect of development process of the software components. The constructed component model has rigorous semantic, which is helpful for developer or maintainer to reason about the tasks performing with the linkage.

show abstract

A reuse based approach for requirements engineering

Cited by 11 publications

References 4 publications

Architecture-based problem frames constructing for software reuse

Architecture-based problem frames constructing for software reuse

Eliciting Potential Requirements with Feature-Oriented Gap Analysis

The Reusable Software Component Development Based on Pattern-Oriented

Contact Info

Product

Resources

About