3,216 research outputs found
Identifying and improving reusability based on coupling patterns
Open Source Software (OSS) communities have not yet taken full advantage of reuse mechanisms. Typically many OSS projects which share the same application domain and topic, duplicate effort and code, without fully leveraging the vast amounts of available code.
This study proposes the empirical evaluation of source code folders of OSS projects in order to determine their actual internal reuse and their potential as shareable, fine-grained and externally reusable software components by future projects.
This paper empirically analyzes four OSS systems, identifies which components (in the form of folders) are currently being reused internally and studies their coupling characteristics. Stable components (i.e., those which act as service providers rather than service consumers) are shown to be more likely to be reusable. As a means of supporting replication of these successful instances of OSS reuse, source folders with similar patterns are extracted from the studied systems, and identified as externally reusable components
Recommended from our members
Evaluating the resilience and security of boundaryless, evolving socio-technical Systems of Systems
Switch or Struggle: Risk Assessment for Late Integration of COTS Components
The domain requirements of software projects often seem so specialized to developers that their original design does not incorporate any commercial-off-the-shelf (COTS) components. However, if major implementation problems are encountered at a later stage in the project, the integration of a COTS component that promises to solve those problems may become a desirable alternative to struggling on
with the original implementation. While a number of methods and criteria have already been proposed for requirements engineering, risk assessment and candidate selection of COTS components, they were developed for application in the initial phases of a project and thus do not take into account the much tighter time and design constraints imposedin a later project stage. To spark discussion on necessary
adaptations of the established methods, this position paper uses the example of a concrete project to illustrate the characteristics of “switch or struggle” situations and proposes an initial set of risk factors to be considered at that time
Vision and Objectives
The purpose of Industry Day is to exchange information with industry to increase understanding of the Government's current vision and objectives for the xEVA Production and Services Contract. The presentation provides industry with the opportunity to provide input into the xEVAPS procurement strategy and encourage offerors to submit questions and comments. A technical overview of the xEVA System serves as the foundation for the content related to draft requirements in the SOW
- …