Andere Kunden interessierten sich auch für
![Managing Requirements Knowledge]( "Managing Requirements Knowledge")
Managing Requirements Knowledge74,99 €![User requirements for Internet Of Things (IoT) applications]( "User requirements for Internet Of Things (IoT) applications")
User requirements for Internet Of Things (IoT) applications23,99 €![Domain Driven Requirements]( "Domain Driven Requirements")
Domain Driven Requirements32,99 €![Building and Evaluating a SOA-Based Model]( "Building and Evaluating a SOA-Based Model")
Building and Evaluating a SOA-Based Model38,99 €![ML based expert system for evaluating student performances]( "ML based expert system for evaluating student performances")
ML based expert system for evaluating student performances26,99 €![Requirements Engineering for Service and Cloud Computing]( "Requirements Engineering for Service and Cloud Computing")
Requirements Engineering for Service and Cloud Computing74,99 €![Evaluating eGovernment Portal Functionality in KM Perspective]( "Evaluating eGovernment Portal Functionality in KM Perspective")
Evaluating eGovernment Portal Functionality in KM Perspective40,99 €
Software reuse can be defined as the process of using preexisting software artifacts rather than building them from scratch. Global Software Engineering (GSE) implies a paradigm shift towards globally distributed development teams. Requirements specifications are generally managed in industry by means of unstructured natural language (NL) requirements. However, NL is inherently ambiguous and can lead to different interpretations depending on the context. This thesis primarily focuses on a reuse-based Requirements Engineering (RE) method for GSE that specifies knowledge in the form of NL requirements. The use of a repository is proposed to arrange sets of interrelated reusable requirements into catalogues, with the purpose of managing requirements knowledge. To the best of my knowledge, there are no other proposals which tackle both issues, GSE and NL requirements reuse, jointly. My key contribution in the context of the previously mentioned method lies in: (1) devising the requirements specification techniques; (2) developing the prototypical automated tool support, based on an extensive study of the RE tools market; and (3) performing the empirical validation of the proposal.