Academia.edu no longer supports Internet Explorer.
To browse Academia.edu and the wider internet faster and more securely, please take a few seconds to upgrade your browser.
2004, IEEE Software
…
12 pages
1 file
COTS-based development (CBD) raises a spectrum of issues, from requirements negotiation to product selection and product integration. The studies on this topic are often in disagreement, lack details about products and projects, and are based on uncritically-accepted assumptions. This was confirmed by an analysis of the literature from which we derived a list of characterizing features for CBD. In order to explore these issues from an empirical perspective, we conducted an exploratory study, based on structured interviews to projects in small and medium-enterprises in Europe. From them we derive two results: key points in COTS based development as it happens in companies; and a definition of COTS product capable of capturing these key points.
IEEE Software, 2004
0 7 4 0 -7 4 5 9 / 0 4 / $ 2 0 . 0 0 © 2 0 0 4 I E E E cots software Studies on commercial-off-the-shelf-based development often disagree, lack product and project details, and are founded on uncritically accepted assumptions. This empirical study establishes key features of industrial COTS-based development and creates a definition of "COTS products" that captures these features.
2000
This paper summarizes the results of a study on fifteen projects that used a COTS-based approach. The process they followed is evaluated to identify essential differences in comparison to traditional software development. The main differences, and the activities for which projects require more guidance, are requirements definition and COTS selection, high level design, integration and testing.
IEEE Software, 2005
0 7 4 0 -7 4 5 9 / 0 5 / $ 2 0 . 0 0 © 2 0 0 5 I E E E focus Integrating COTS into the Development Process B uilding and evolving software systems is an arduous, costly, lengthy, and complex task. The resulting systems are similarly complex. We're thus constantly searching for ways to reduce such costs, time, and complexity while increasing system functionality and quality. Not surprisingly, our quest for "silver bullets," as described by Frederick Brooks back in 1987, 1 hasn't produced significant
Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium, 2000
The work described in this paper is an investigation of COTS-based software development within a particular NASA environment, with an emphasis on the processes used. Fifteen projects using a COTS-based approach were studied and their actual process was documented. This process is evaluated to identify essential differences in comparison to traditional software development. The main differences, and the activities for which projects require more guidance, are requirements definition and COTS selection, high level design, integration and testing.
Journal of Systems and …, 2002
The work described in this paper is an investigation of the COTS-based software development within a particular NASA environment, with an emphasis on the processes used. Fifteen projects using a COTS-based approach were studied and their actual process was documented. ...
2000
CITATIONS 65 READS 168 4 authors, including:
Proceedings of the 28th Annual ACM Symposium on Applied Computing - SAC '13, 2013
We present a descriptive and exploratory study of factors that can affect the success of COTS-based systems. Based on a review of the literature and industrial experience, the choice of life cycle model and the amount of glueware required were hypothesized as the main factors in predicting project success. In this study we examined the relationship between different life cycle models and COTS integration project success. Two life cycle models were studied: the sequential model and the iterative model. Seven subjects from six industrial organizations responded to a survey providing data on 23 COTS integration projects. While there was variability between iterative and sequential projects on a variety of organizational and product factors, little difference was found between the life cycle models on the success criteria of projects (i.e. being on time, meeting requirements and being within budget). We found that projects that met two or three of the success criteria had significantly higher scores on project characteristics (organizational plus product) than those meeting none or just one.
2002
Selecting COTS products is a process that inherently involves tradeoffs. In this position paper, we highlight the challenges of the requirements process for COTS-based system where the negotiation of requirements plays a critical task. In particular, it is necessary to perform a careful balancing between stakeholders requirements and COTS features. We analyse the processes of COTS matching and balancing using a goal-driven approach.
Empirical Software Engineering, 2007
... Department of Computer and Information Science, Norwegian University of Science and Technology, NO-7491 Trondheim, Norway e-mail: [email protected] FO Bjørnson email:[email protected] R. Conradi e-mail: [email protected] R. Conradi & VB Kampenes ...
"International Workshop on Models and Processes for the Evaluation of COTS Components (MPEC 2004)" W7S Workshop - 26th International Conference on Software Engineering, 2004
The use of Commercial-Off-The-Shelf (COTS) software has become more and more important in software development. In COTS-based development, COTS component selection is the most crucial phase. Although some selection processes have been proposed, empirical studies are necessary to assess these processes. This paper describes an exploratory study by structured interviews of 16 COTS-based development projects in Norwegian IT companies. The results indicate that successful COTS component selection can be implemented without using formal processes, and projects with different contexts may use different selection processes. If members in new project has enough practical experience with actual COTS components, such experience can be the dominant factor in selection. In the case of using a new COTS component in the project, hands-on experimentation is needed as an effective way of evaluating the component.
Loading Preview
Sorry, preview is currently unavailable. You can download the paper by clicking the button above.
2013
European Journal of Information Systems, 2000
COTS workshop. Continuing Collaborations for …, 2000
2007
Requirements Engineering, 2006
11th Asia-Pacific Software Engineering Conference, 2004
Communications of the ACM, 1997