Representing variability in a family of MRI scanners

Software - Practice and Experience

Volumn 34, Issue 1, 2004, Pages 69-100

  Jaring, M ^a   Krikhaar, R L ^b   Bosch, J ^a  

^a UNIVERSITY OF GRONINGEN   (Netherlands)

^b PHILIPS HEALTHCARE   (United States)

Author keywords

Dependencies; Product derivation; Software product families; Variability modeling

Indexed keywords

COMPUTER ARCHITECTURE; COMPUTER HARDWARE; COST EFFECTIVENESS; INTRANETS; LARGE SCALE SYSTEMS; MAGNETIC RESONANCE IMAGING; PRODUCT DEVELOPMENT; PROJECT MANAGEMENT; SCANNING; SOFTWARE ENGINEERING;

PRODUCT DERIVATION; SOFTWARE PRODUCT FAMILIES; VARIABILITY MODELING;

COMPUTER SOFTWARE;

EID: 0346500444     PISSN: 00380644     EISSN: None     Source Type: Journal    
DOI: 10.1002/spe.558     Document Type: Article

References (46)

1. McIlroy MD. Mass produced software components. Software Engineering: Report on a Conference by the NATO Science Committee. NATO Scientific Affairs Division: Brussels, 1968; 138-150.
2. Parnas DL. On the design and development of program families. IEEE Transactions on Software Engineering 1976; 2(1): 1-9.
3. Jacobson I, Griss M, Jonsson P. Software Reuse - Architecture, Process and Organization for Business Success, Addison-Wesley: Reading, MA, 1997.
4. Jazayeri M, Ran A, van der Linden F. Software Architecture for Product Families: Putting Research into Practice. Addison-Wesley: Reading, MA, 2000.
5. Coplien JO, Huffman DM, Weiss DM. On commonality and variability in software engineering. IEEE Software 1998; 15(6):37-45.
6. Keepence B, Mannion M. Using patterns to model variability in product families. IEEE Software 1999; 16(4): 102-108.
7. Glass RL. The relationship between theory and practice in software engineering. Communications of the ACM 1996; 39(11);11-13.
8. Bronsword L, Clements P. A case study in successful product line development. CMU/SEI-96-TR-016, Software Engineering Institute. Carnegie Mellon University - Software Engineering Institute: Pittsburgh, PA. http://www.sei.cmu.edu/publications/documents/96.reports/96.tr.016.html [15 May 2003].
9. Svahnberg M, Bosch J. Evolution in software product lines: Two cases. Journal of Software Maintenance and Evolution: Research and Practice 1999; 11(6):391-422.
10. Bosch J. Evolution and composition of reusable assets in product-line architectures: A case study. First Working IFIP Conference on Software Architecture. Kluwer: San Antonio, TX, 1999; 321-340.
11. Macala RR, Stucky LD, Gross DC. Managing domain-specific product-line development. IEEE Software 1996; 13(3): 57-67.
12. Svahnberg M, Bosch J. Issues concerning variability in software product lines. Third International Workshop on Software Architectures for Product Families. Springer: Las Palmas de Gran Canaria, 2000: 146-157.
13. Bass L, Clements P, Cohen S, Northrop L, Withey J. Product line practice workshop report. CMU/SEI-97-TR-003. Carnegie Mellon University - Software Engineering Institute: Pittsburgh, PA. http://www.sei.cmu.edu/publications/documents/97.reports/97tr003/ 97tr003abstract.html [15 May 2003].
14. Dikel D, Kane D, Ornburn S. Loftus W, Wilson J. Applying software product line architecture. IEEE Computer 1997; 30(8):49-55.
15. Wijnstra JG. Supporting diversity with component frameworks as architectural elements. 22nd International Conference on Software Engineering. ACM Press: Limerick, 2000; 51-60.
16. van Ommering R. Building product populations with software components. 24th International Conference on Software Engineering. ACM Press: Orlando, FL, 2002; 255-265.
17. Toft P, Coleman D, Ohta J. A cooperative model for cross-divisional product development for a software product line. First Software Product Line Conference. Kluwer: Denver, CO, 2000; 111-132.
18. van Gurp J, Bosch J. Design erosion: Problems & causes. Journal of Systems & Software 2002; 61(2): 105-119.
19. Bachmann F, Bass L. Managing variability in software architectures. Symposium on Software Reusability. ACM Press: Toronto, 2001; 126-132.
20. Clements P, Northrop L. A Framework for Software Product Line Practice, version 4.1. Carnegie Mellon University - Software Engineering Institute: Pittsburgh, PA. http://www.sei.cmu.edu/plp/framework.html [15 May 2003].
21. Batory D, O'Malley S. The design and implementation of hierarchical software systems with reusable components. ACM Transactions on Software Engineering and Methodology 1992; 1(4):355-398.
22. Krikhaar RL. Software architecture reconstruction. PhD Thesis, University of Amsterdam, The Netherlands, 1999.
23. Rooijmans J, Aerts H, van Genuchten M. Software quality in consumer electronics products. IEEE Software 1996; 13(1):55-64.
24. Krikhaar RL, Feijs L, de Jong R. Medema J. Architecture comprehension tools for a PBX system. Third European Conference on Software Maintenance and Reengineering. IEEE Computer Society: Amsterdam, 1999; 31-41.
25. Jaring M, Bosch J. Representing variability in software product lines: A case study. Second Software Product Line Conference. Springer: San Diego, CA, 2002; 15-36.
26. Garlan D, Allen R, Ockerbloom J. Architectural mismatch: Why reuse is so hard. IEEE Software 1995; 12(6): 17-26.
27. van Gurp J, Bosch J, Svahnberg M. On the notion of variability in software product lines. Working IEEE/IFIP Conference on Software Architecture. IEEE Computer Society: Amsterdam, 2001; 45-54.
28. Oreizy P, Gorlick MM, Taylor RN, Heimbigner D, Johnson G, Medvidovic N, Quilici A, Rosenblum DS, Wolf AL. An architecture-based approach to self-adaptive software. IEEE Intelligent Systems 1999:14(3):54-62.
29. Gamma E, Helm R, Johnson R. Vlissides J. Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley: Reading, MA, 1995.
30. Bosch J. Design & Use of Software Architectures: Adopting and Evolving a Product-Line Approach. Addison-Wesley: Reading, MA, 2000.
31. Weiss DM, Lai CTR. Software Product-Line Engineering: A Family-Based Software Development Process. Addison-Wesley: Reading, MA, 1999.
32. Bosch J, Florijn G, Greefhorst D, Kuusela J, Obbink H, Pohl K. Variability issues in software product lines. Fourth International Workshop on Product Family Engineering. Springer: Bilbao, 2001 ; 13-21.
33. Gibson JP. Feature requirements models: Understanding interactions. Feature Interactions in Telecommunication Networks IV. IOS Press: Montreal, 1997; 46-60.
34. Griss ML, Favaro J, d'Allessandro M. Integrating feature modeling with the RSEB. Fifth International Conference on Software Reuse. IEEE Computer Society: Victoria, Canada, 1998; 76-85.
35. Svahnberg M, van Gurp J, Bosch J. A taxonomy of variability realization techniques. Research Report, Blekinge Institute of Technology, Karlskrona, Sweden, 2002; 1103-1581.
36. Software Engineering Institute. How Do You Define Software Architecture? Carnegie Mellon University - Software Engineering Institute: Pittsburgh, PA. http://www.sei.cmu.edu/architecture/definitions.html [15 May 2003].
37. Maier MW, Emery D, Hilliard R. Software architecture: Introducing IEEE standard 1471. IEEE Computer 2001; 34(4):107-109.
38. Bosch J. Maturity in evolution in software product lines: Approaches, artefacts and organization. Second Software Product Line Conference. Springer: San Diego, CA. 2002; 257-270.
39. Yin RK. Case Study Research: Design and Methods, Sage Publications: New York. 1994.
40. Tellis W. Introduction to case study. The Qualitative Report 1997; 3(2). http://www.nova.edu/ssss/QR/QR3-2/tellisl.html [15 May 2003].
41. Tellis W. Application of a case study methodology. The Qualitative Report 1997; 3(3). http://www.nova.edu/ssss/QR/QR3-3/tellis2.html [15 May 2003].
42. Philips Medical Systems. http://www.medical.philips.com/ [15 May 2003].
43. Hornak JP. The Basics of MRI. Rochester Institute of Technology: Rochester, NY. http://www.cis.rit.edu/htbooks/mri/ [15 May 2003].
44. Marvelous MRI: Bringing us Visions of the Living Brain. Montreal Neurological Institute and Hospital: Montreal, http://www.mni.mcgill.ca/nm/1998f/mri.html [ 15 May 2003].
45. van der Linden FJ. Müller JK. Creating architectures with building blocks. IEEE Software 1995; 12(6):51-60.
46. Krikhaar RL, Wijnstra JG. Product Development with the Building Block Method: A Process Perspective, version 1.0. Philips Research - Information and Software Technology: Pittsburgh, PA, 1994.