umu.sePublications
Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Engineering Families of Software-Intensive Systems using Features, Goals and Scenarios
Umeå University, Faculty of Science and Technology, Department of Computing Science.
2007 (English)Doctoral thesis, comprehensive summary (Other academic)
Abstract [en]

Over the last decade, software has become an integral part of many products with which it is not traditionally associated (e.g., automobiles, medical equipment, home appliances, etc.). This has led to problems in many organizations, since it has proved difficult to integrate software engineering processes with other engineering processes. To address the increased complexity and to coordinate their engineering efforts, many organizations working in such domains have therefore introduced systems engineering into their business processes.

Systems engineering is an interdisciplinary approach to system development. Teamwork is essential in developing complex systems, and systems engineering orchestrates this process throughout the lifespan of a system. The focus of systems engineering is on defining customer needs and required functionality, documenting requirements, synthesizing a design and validating the system. A problem with the traditional techniques of systems engineering is, however, that they provide inadequate support for achieving high levels of reuse between different projects.

In this dissertation, methods and tools with the overall purpose of providing an improved reuse infrastructure for systems engineering artifacts and their resulting detailed design artifacts are proposed. The proposed methods and tools are based on the software product-line approach, a reuse strategy which focuses on families of related systems that address particular market segments.

Studies have shown that if an empirical study does not report experiences from that which practitioners consider a “real” situation, results are likely to be ignored. Even though case studies cannot achieve the scientific rigor of formal experiments, case studies can provide enough information to decide if a specific technology will benefit a particular organization. To ensure industry-relevant research results, case studies on real development projects were chosen as the main vehicle for performing research.

This dissertation reports experiences from four empirical studies which were performed within the Swedish defense industry. The studies indicate that the proposed methods and tools indeed provide an improved reuse infrastructure, compared to the previously used methods and tools.

Place, publisher, year, edition, pages
Umeå: Datavetenskap , 2007. , 35 p.
Series
Report / UMINF, ISSN 0348-0542 ; 07.24
Keyword [en]
systems engineering, software product lines, requirements engineering, variability management, use case modeling, feature modeling
National Category
Computer Science
Identifiers
URN: urn:nbn:se:umu:diva-1447ISBN: 978-91-7264-440-3 (print)OAI: oai:DiVA.org:umu-1447DiVA: diva2:141097
Public defence
2007-12-14, MA121, MIT-huset, Umeå univeritet, Umeå, 13:15 (English)
Opponent
Supervisors
Available from: 2007-11-22 Created: 2007-11-22 Last updated: 2009-09-08Bibliographically approved
List of papers
1. Use Cases for Systems Engineering—An Approach and Empirical Validation
Open this publication in new window or tab >>Use Cases for Systems Engineering—An Approach and Empirical Validation
2008 (English)In: Journal of Systems Engineering, ISSN 0938-7706, Vol. 11, no 1Article in journal (Refereed) Published
Keyword
Software Engineering, Software Product Lines, Requirements Engineering
Identifiers
urn:nbn:se:umu:diva-8484 (URN)
Available from: 2008-01-30 Created: 2008-01-30 Last updated: 2009-09-08Bibliographically approved
2. The PLUSS Approach: Domain Modeling with Features, Use Cases and Use Case Realizations
Open this publication in new window or tab >>The PLUSS Approach: Domain Modeling with Features, Use Cases and Use Case Realizations
2005 (English)In: Proceedings of the 9'th International Conference on Software Product Lines (SPLC'05), LNCS, Springer-Verlag, Heidelberg: Springer Berlin , 2005, 33-44 p.Chapter in book (Other academic)
Abstract [en]

This paper describes a product line use case modeling approach tailored towards organizations developing and maintaining extremely long lived software intensive systems. We refer to the approach as the PLUSS approach, Product Line Use case modeling for Systems and Software engineering . An industrial case study is presented where PLUSS is applied and evaluated in the target domain. Based on the case study data we draw the conclusion that PLUSS performs better than modeling according to the styles and guidelines specified by the IBM-Rational Unified Process (RUP) in the current industrial context.

Place, publisher, year, edition, pages
Heidelberg: Springer Berlin, 2005
Series
Lecture Notes in Computer Science, ISSN 0302-9743 (Print) 1611-3349 (Online)
Identifiers
urn:nbn:se:umu:diva-2811 (URN)10.1007/11554844_5 (DOI)978-3-540-28936-4 (ISBN)
Available from: 2007-11-22 Created: 2007-11-22 Last updated: 2015-09-25Bibliographically approved
3. The PLUSS Toolkit: Extending Telelogic Doors and IBM-Rational Rose to Support Product Line Use Case Modeling
Open this publication in new window or tab >>The PLUSS Toolkit: Extending Telelogic Doors and IBM-Rational Rose to Support Product Line Use Case Modeling
2005 (English)In: Proceedings of the 20th IEEE/ACM International Conference on Automated Software Engineering (ASE'05), 2005, 300-304 p.Conference paper, Published paper (Refereed)
Abstract [en]

The PLUSS approach (Product Line Use case modeling for Systems and Software engineering) is a domain modeling method tailored towards the development of long lived software intensive systems. PLUSS provides means to maintain a common and complete use case model for a whole family of systems. In this paper, we describe how the commercial requirements management tool Telelogic DOORS and the UML modeling tool IBM-Rational Rose can be extended and used for managing system family models in accordance with the PLUSS approach

Keyword
Software Engineering, Software Product Lines, Requirements Engineering
Identifiers
urn:nbn:se:umu:diva-10263 (URN)10.1145/1101908.1101955 (DOI)
Available from: 2008-07-24 Created: 2008-07-24 Last updated: 2015-09-25Bibliographically approved
4. Software Product Line Modeling Made Practical: An Example from the Swedish Defense Industry
Open this publication in new window or tab >>Software Product Line Modeling Made Practical: An Example from the Swedish Defense Industry
2006 (English)In: Communications of the ACM, ISSN 0001-0782, E-ISSN 1557-7317, Vol. 49, no 12, 49-54 p.Article in journal (Refereed) Published
Keyword
Software Engineering, Software Product Lines
Identifiers
urn:nbn:se:umu:diva-10259 (URN)10.1145/1183236.1183265 (DOI)
Available from: 2008-07-24 Created: 2008-07-24 Last updated: 2015-09-25Bibliographically approved
5. Managing requirements specifications for product lines: An approach and industry case study
Open this publication in new window or tab >>Managing requirements specifications for product lines: An approach and industry case study
2009 (English)In: Journal of Systems and Software, ISSN 0164-1212, Vol. 82, no 3, 435-447 p.Article in journal (Refereed) Published
Abstract [en]

Software product line development has emerged as a leading approach for software reuse. This paper describes an approach to manage natural-language requirements specifications in a software product line context. Variability in such product line specifications is modeled and managed using a feature model. The proposed approach has been introduced in the Swedish defense industry. We present a multiple-case study covering two different product lines with in total eight product instances. These were compared to experiences from previous projects in the organization employing clone-and-own reuse. We conclude that the proposed product line approach performs better than clone-and-own reuse of requirements specifications in this particular industrial context.

Place, publisher, year, edition, pages
Elsevier, 2009
Keyword
Software Engineering, Software Product Lines, Requirements Engineering
National Category
Computer Science
Identifiers
urn:nbn:se:umu:diva-22891 (URN)10.1016/j.jss.2008.07.046 (DOI)
Available from: 2009-05-19 Created: 2009-05-19 Last updated: 2012-09-06Bibliographically approved

Open Access in DiVA

fulltext(266 kB)710 downloads
File information
File name FULLTEXT01.pdfFile size 266 kBChecksum SHA-1
682de1232586d99c5a530e8dd9d8ff2a3b573d479e823d3d664e1b497b126524b3ff2c95
Type fulltextMimetype application/pdf

By organisation
Department of Computing Science
Computer Science

Search outside of DiVA

GoogleGoogle Scholar
Total: 710 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

isbn
urn-nbn

Altmetric score

isbn
urn-nbn
Total: 470 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf