Integrated Requirements Engineering: A Tutorial
IEEE Software
Understanding solution architecture concerns
MPEC '05 Proceedings of the second international workshop on Models and processes for the evaluation of off-the-shelf components
How Agile COTS Selection Methods are (and can be)?
EUROMICRO '05 Proceedings of the 31st EUROMICRO Conference on Software Engineering and Advanced Applications
Research Directions in Requirements Engineering
FOSE '07 2007 Future of Software Engineering
Using search theory to determine an applications selection strategy
Information and Management
REFSQ'07 Proceedings of the 13th international working conference on Requirements engineering: foundation for software quality
International Journal of Distance Education Technologies
| Hi-index | 0.00 |
When buying COTS-based software, the customer has to choose between what is available. The supplier may add some minor parts, but not everything the customer wants. This means that the customer cannot write down his requirements and expect that they can all be met. A scoring system is necessary rather than traditional mandatory requirements. Requirements for integrating the new COTS system with other systems are particularly hard because suppliers may integrate in different ways and with different other systems. A related problem is that once the new COTS system is purchased, the COTS supplier may have a de-facto monopoly. Only he can expand the system or integrate it with other systems. Experience shows that customers fail to deal with these issues adequately. As an example they may believe that asking for open interfaces is sufficient to guard them against monopoly. In this paper we analyze the problems and show ways to deal with them. We illustrate the problems and solutions with real-life examples from Electronic Patient Recording systems (EPR).