How agile COTS selection methods are (and can be)?

Agile methods are proposed nowadays as a way to support software systems procurement. Most of the existing proposals such as eXtreme programming or scrum seem to conceive software procurement as an exercise of software development. However, a great deal of software systems are commercial off-the-shelf (COTS)-based systems, in which the focus changes from bespoke software development to COTS selection and integration. Many proposals for COTS selection have been issued and therefore one may wonder how do they behave from the agile point of view. In this paper, we study the agile principles in the context of COTS selection and we analyze some of the most widespread existing methods. As a result, we identify some practices that would help in making COTS selection processes more agile.Peer ReviewedPostprint (published version

COTS Evaluation

This article presents an extensive literature review of the empirical studies carried out in past for evaluation and selection of components during the design phase of Component Based Software Systems (CBSS). In CBSS approach the software systems can be developed by selecting appropriate components which then are assembled to form a complete software system. These Components can be either of the two (a) COTS (Commercial-off-the-Shelf) components or (b) Inhouse built components. These components are selected based on different parameters of cost, reliability, delivery time etc. Therefore, optimal selection of the components plays a vital role in development of CBSS as it saves time and effort. Related articles appearing in the International Journals from 1992 to 2014 are gathered and are critically analyzed. Based on the review it is seen that some of the important issues have not been explored fully. Hence there is scope of improvement which paves the path for future work

Unsolved Tricky Issues on COTS Selection and Evaluation

Component Based Software Engineering (CBSE) approach is based on the idea to develop software systems by selecting appropriate components and then to assemble them with a well-defined software architecture. (CBSE) offers developers the twin benefits of reduced software life cycles, shorter development times , saving cost and less effort as compare to build own component. However the success of the component based paradigm depends on the quality of the commercial off-the-shelf (COTS) components purchased and integrated into the existing software systems. It is need of the time to present a quality model that can be used by software programmer to evaluate the quality of software components before integrating them into legacy systems. The evaluation and selection of the COTS components are the most critical process. These evaluation and selection method cannot be resolved by the IT professionals itself. In this study the author tried to compare the twenty three available systematic methods for best evaluation and selection of COTS components

Systematic construction of goal-oriented COTS taxonomies

The use of Commercial Off-The-Shelf (COTS) components is becoming a strategic need because they offer the possibility to build systems at reduced costs and within shorter development time. Having efficient and reliable COTS components selection methods is a key issue not only for exploiting the potential benefits of this technology, but also for facing the problems and risks involved. Searching COTS components requires overcoming several obstacles: the growing size and evolvability of the COTS marketplace, the dependencies from the components to be selected with others, and the type of descriptions currently available for those components. The main goal of this thesis is to provide support for a reliable and comprehensive structuring of a reuse infrastructure for the COTS components marketplace. With this aim, we propose a method for the construction and maintenance of goal-oriented COTS taxonomies based on a solid domain analysis; guiding the gathering of sources of information, modeling requirements and dependency relationship among domains, and organizing knowledge in any segment of the COTS marketplace.Peer ReviewedPostprint (author’s final draft

DESIGN AND IMPLEMENTATION OF A HIGHLY MODIFIABLE RETAIL E-COMMERCE WEBSITE

The availability, modifiability, and performance of retail e-commerce websites(RECWEB) is greatly impacted by seasonal constraints. For many RECWEB, half of the calendar year is comprised of holidays and seasons. Spikes in website traffic and transactions can lower availability, modifiability, and performance of a RECWEB. This can result in downtime, customer abandonment, and ultimately lost revenue. This research focuses the modifiability aspects of the problem. During holiday and seasonal periods, enhancements to a RECWEB are generally not feasible. Enhancements put availability and performance at risk. In addition, most human resources are dedicated managing content changes. RECWEB are less modifiable then other systems because enhancements are only feasible for half of the calendar year. Furthermore, the scope of an enhancement must fit within a six month time box. This research provides pilot project for testing, designing, and implementing a highly modifiable RECWEB. The approach is to automate seasonal content changes. The cost savings on human resources can be reallocated to enhancements work. In addition, enhancements can simulate holiday seasons further in advance. The result is enhancement deployment is more feasible throughout the calendar year

PABRE: Pattern-Based Requirements Elicitation

This paper presents our PABRE method for facilitating Requirements Elicitation on the basis of Requirement Patterns with the goal of saving time and reducing errors during this activity. The process presented applies for elicitation in Off-The-Shelf selection projects driven by call for tenders processes and uses a Requirement Patterns Catalogue. The process selects patterns from the catalogue that apply to the particular selection project, and convert them into the real requirements that finally configure the project Requirements Book. We show some benefits of the pattern approach for requirements engineers and IT consultants, as well as for customers. Finally we discuss the strengths and weaknesses of the proposal and identify some future work.Peer ReviewedPostprint (published version

A pattern-based method for building requirements documents in call-for-tender processes

This paper presents our PABRE method for facilitating Requirements Elicitation on the basis of Requirement Patterns with the goal of saving time and reducing errors during this activity. The process presented applies for elicitation in Off-The-Shelf selection projects driven by call-for-tender processes and uses a Requirement Patterns Catalogue. The process selects patterns from the catalogue that apply to the particular selection project, and convert them into the real requirements that finally configure the project Requirements Document. We show some benefits of the pattern approach for requirements engineers and IT consultants, as well as for customers. Finally we discuss the strengths and weaknesses of the proposal and identify some future work.Postprint (published version