COTS tenders and integration requirements

Lauesen, Søren

doi:10.1007/s00766-005-0022-5

Cited by 18 publications

(4 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“… Level (Metadata 9.1 in RML): RKs might belong to one level based on the goal level scale defined by Lauesen (2002): business, user, system, and design. Business requirements aim to justify why the customer wants to spend money on a given product.…”

Section: Component-based Approachmentioning

confidence: 99%

See 1 more Smart Citation

Component-based approach for requirements reuse

Chikh¹

2017

The Knowledge Engineering Review

View full text Add to dashboard Cite

Reusing requirements improves product quality and the productivity of the development process. This paper investigates how the development of new requirements can be made more productive through reuse of the experience gained on similar requirements. This can be facilitated using a component-based reuse approach supported by a framework. Therefore, the central challenge for this research work is double: (1) to define a new concept for the requirement component as the combination of two types of knowledge: reusable knowledge and knowledge of reuse; (2) to define AFR (Analysis For Reuse) that represents the capitalization process by opposition to Analysis By Reuse that represents the process of reuse itself. Finally, we provide a case study related to the requirements of a hotel system to explain how the first process works. Through this approach, we use a framework ‘Requirements Repository Framework (R2F)’ in order to capitalize existing requirements within a repository for future reuse. We present the results of an experiment with three second-level student sections that used R2F in their IS240 course project; as well as with four student groups that used R2F in their respective senior projects. The objective of this experiment is to measure the usability of the proposed AFR process.

show abstract

Section: Component-based Approachmentioning

confidence: 99%

“…What data should the system input and output, and what data should the system store internally? (Lauesen, 2002). NFRs might be classified according to Sommerville (2011) as follows: product, organizational, and external requirements.…”

Section: Component-based Approachmentioning

confidence: 99%

Component-based approach for requirements reuse

Chikh¹

2017

The Knowledge Engineering Review

View full text Add to dashboard Cite

show abstract

“…Considerable research and experience reports exist describing the challenges involved in evaluating and selecting TPS for use. Examples include [1,7,8]. Much of this work is centered on the TPS acquirer's perspective by focusing on requirements, analysis of "fit", and adaptation of internal processes and architectures to admit the available offerings.…”

Section: Introductionmentioning

confidence: 99%

“…The first step towards defining the impacts is finding the conflicts in the concerns and their resulting design mechanisms. As related in [7], "…it often happens that the supplier cannot fulfill his promises no matter how hard he tries. Typical trouble areas are performance (response time) and integration with other products."…”

mentioning

confidence: 97%

Understanding solution architecture concerns

Gamble

Hepner

2005

Proceedings of the Second International Workshop on Models and Processes for the Evaluation of Off-the-Shelf Components - MPEC

View full text Add to dashboard Cite

Modern software system development includes the use of offthe-shelf components in the form of third-party software (TPS). Vendors of TPS products play an increasingly important role in the systems that incorporate their offerings. Modeling these vendors' motivations, in the form of architectural concerns and viewpoints, provides an additional tool for customers evaluating TPS. Such viewpoint-based analysis of vendor-oriented solution architectures can provide valuable insights to customers at the time of TPS acquisition as well during the overall lifetime of the system incorporating TPS.

show abstract

On the Use of Requirement Patterns to Analyse Request for Proposal Documents

Costal

Franch

López

et al. 2019

Conceptual Modeling

View full text Add to dashboard Cite

Requirements reuse is still today a difficult goal to achieve. One particular context in which requirements reuse may give more benefits than costs is that of call for tenders projects, due to the similarity of the requirements documents (which take the form of requests for proposal documents, RfPs) from one project to another. In this paper, we present an approach aimed at making systematic the assessment of RfPs that technology providers need to conduct in order to decide whether they present a bid or not in a call for tenders project. The approach extends a metamodel we already defined for the former PABRE method, which has a similar goal but from the perspective of the organization that issues the call for tenders. The method is illustrated with an exploratory case study in the field of the railway systems domain.

show abstract

COTS tenders and integration requirements

Cited by 18 publications

References 20 publications

Component-based approach for requirements reuse

Component-based approach for requirements reuse

Understanding solution architecture concerns

On the Use of Requirement Patterns to Analyse Request for Proposal Documents

Contact Info

Product

Resources

About