Panel
Do We Need Requirements in COTS-Based Software Development?
Do We Need Requirements in COTS-Based Software Development?
| moderator | ||
 |
Xavier Franch | |
| panelist | ||
|
Neil Maiden | |
 |
|
|
|
Panel
Do We Need Requirements in COTS-Based Software Development? |
||||||||||||||||||||
|
COTS software products radically change the way in which software systems are developed. Existing sequential or iterative development methods and techniques are no longer relevant. One of the most important characteristics of COTS-based development is that it is solution- or feature-driven; that is, the existing features of the available or selected COTS software systems heavily influence the final application. This has major implications for how to develop software systems, and in particular for the role of requirements in this process. One extreme position is that requirements, often seen as one of the most important factors in a successful development project, are no longer important as the stakeholder typically has to work with the COTS software product as is, with little to say over customization. On the other hand, requirements still appear to be important during COTS-related activities to provide selection criteria and drivers for product change. This panel will discuss subjects such as how to integrate classical requirements activities in the COTS-based systems development processes; which are the new types of requirements particular to COTS-based systems; and others. | |||||||||||||||||||
|
|
|