Please use this identifier to cite or link to this item:
https://doi.org/10.1007/978-3-642-15579-6_51
DC Field | Value | |
---|---|---|
dc.title | Pragmatic strategies for variability management in product lines in small- to medium-size companies | |
dc.contributor.author | Jarzabek, S. | |
dc.date.accessioned | 2013-07-04T08:21:39Z | |
dc.date.available | 2013-07-04T08:21:39Z | |
dc.date.issued | 2010 | |
dc.identifier.citation | Jarzabek, S. (2010). Pragmatic strategies for variability management in product lines in small- to medium-size companies. Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) 6287 LNCS : 503-504. ScholarBank@NUS Repository. <a href="https://doi.org/10.1007/978-3-642-15579-6_51" target="_blank">https://doi.org/10.1007/978-3-642-15579-6_51</a> | |
dc.identifier.isbn | 3642155782 | |
dc.identifier.issn | 03029743 | |
dc.identifier.uri | http://scholarbank.nus.edu.sg/handle/10635/41188 | |
dc.description.abstract | Most SPLs in small- to medium-size companies evolve from a single successful product. Initially, each new product variant is often developed by ad hoc reuse - copy and modify - of source code files implementing existing products. Versions of source files pertinent to different products are stored under a Software Configuration Management (SCM) tool such as CVS or SVN. As the number of customers and relevant product variants increases, such ad hoc reuse shows its limits: The product size grows as we implement new features in response to customer requests. At the same time, we need maintain all the released product variants, so we have more and more code to maintain. Also with a growing customer base (good for our business!), increasing product variability becomes a challenge for ad hoc reuse: How do we know which versions of source files should be selected from SCM repository for reuse in development of a new product? How should we customize them and then integrate to build a new product? These problems may become taxing on company resources. © 2010 Springer-Verlag Berlin Heidelberg. | |
dc.description.uri | http://libproxy1.nus.edu.sg/login?url=http://dx.doi.org/10.1007/978-3-642-15579-6_51 | |
dc.source | Scopus | |
dc.type | Conference Paper | |
dc.contributor.department | COMPUTER SCIENCE | |
dc.description.doi | 10.1007/978-3-642-15579-6_51 | |
dc.description.sourcetitle | Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) | |
dc.description.volume | 6287 LNCS | |
dc.description.page | 503-504 | |
dc.identifier.isiut | NOT_IN_WOS | |
Appears in Collections: | Staff Publications |
Show simple item record
Files in This Item:
There are no files associated with this item.
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.