liu.seSearch for publications in DiVA
Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • oxford
  • 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
Integrating an Improvement Model of Handling Capacity Requirements with OpenUP/Basic Process
Linköping University, Department of Computer and Information Science, PELAB - Programming Environment Laboratory. Linköping University, The Institute of Technology.
Ericsson AB, Linköping, Sweden.
Linköping University, Department of Computer and Information Science, PELAB - Programming Environment Laboratory. Linköping University, The Institute of Technology.
2007 (English)In: 13th International working conference on Requirements Engineering: Foundations for Software Quality (REFSQ'07), Trondheim, Norway, Berlin Heidelberg: Springer , 2007, 341-354 p.Conference paper, Published paper (Refereed)
Abstract [en]

Contemporary software processes and modeling languages have a strong focus on Functional Requirements (FRs), whereas information of Non-Functional Requirements (NFRs) are managed with text-based documentation and individual skills of the personnel. In order to get a better understanding of how capacity requirements are handled, we carried out an interview series with various branches of Ericsson. The analysis of this material revealed 18 Capacity Sub-Processes (CSPs) that need to be attended to create a capacity-oriented development. In this paper we describe all these sub-processes and their mapping into an extension of the OpenUP/Basic software process. Such an extension will support a process engineer in realizing the sub-processes, and has at the same time shown that there are no internal inconsistencies of the CSPs. The extension provides a context for continued research in using UML to support negotiation between requirements and existing design.

Place, publisher, year, edition, pages
Berlin Heidelberg: Springer , 2007. 341-354 p.
Series
Lecture Notes in Computer Science, ISSN 0302-9743 ; 4542
Keyword [en]
Capacity requirements, OpenUP/Basic, method plug-in, Eclipse Process Framework, process improvement
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:liu:diva-16792DOI: 10.1007/978-3-540-73031-6_26ISBN: 978-3-540-73030-9 (print)OAI: oai:DiVA.org:liu-16792DiVA: diva2:174090
Available from: 2009-02-19 Created: 2009-02-19 Last updated: 2009-04-23Bibliographically approved
In thesis
1. Processes and Models for Capacity Requirements in Telecommunication Systems
Open this publication in new window or tab >>Processes and Models for Capacity Requirements in Telecommunication Systems
2009 (English)Doctoral thesis, comprehensive summary (Other academic)
Abstract [en]

Capacity is an essential quality factor in telecommunication systems. The ability to develop systems with the lowest cost per subscriber and transaction, that also meet the highest availability requirements and at the same time allow for scalability, is a true challenge for a telecommunication systems provider. This thesis describes a research collaboration between Linköping University and Ericsson AB aimed at improving the management, representation, and implementation of capacity requirements in large-scale software engineering.

An industrial case study on non-functional requirements in general was conducted to provide the explorative research background, and a richer understanding of identified difficulties was gained by dedicating subsequent investigations to capacity. A best practice inventory within Ericsson regarding the management of capacity requirements and their refinement into design and implementation was carried out. It revealed that capacity requirements crosscut most of the development process and the system lifecycle, thus widening the research context considerably. The interview series resulted in the specification of 19 capacity sub-processes; these were represented as a method plug-in to the OpenUP software development process in order to construct a coherent package of knowledge as well as to communicate the results. They also provide the basis of an empirically grounded anatomy which has been validated in a focus group. The anatomy enables the assessment and stepwise improvement of an organization’s ability to develop for capacity, thus keeping the initial cost low. Moreover, the notion of capacity is discussed and a pragmatic approach for how to support model-based, function-oriented development with capacity information by its annotation in UML models is presented. The results combine into a method for how to improve the treatment of capacity requirements in large-scale software systems.

Place, publisher, year, edition, pages
Linköping: Linköping University Electronic Press, 2009. 62 p.
Series
Linköping Studies in Science and Technology. Dissertations, ISSN 0345-7524 ; 1238
National Category
Computer Science
Identifiers
urn:nbn:se:liu:diva-16932 (URN)978-91-7393-700-9 (ISBN)
Public defence
2009-03-26, Visionen, hus B, Campus Valla, Linköpings universitet, Linköping, 10:15 (English)
Opponent
Supervisors
Available from: 2009-02-25 Created: 2009-02-25 Last updated: 2009-04-23Bibliographically approved

Open Access in DiVA

No full text

Other links

Publisher's full textLink to Ph.D. Thesis

Authority records BETA

Borg, AndreasSandahl, Kristian

Search in DiVA

By author/editor
Borg, AndreasSandahl, Kristian
By organisation
PELAB - Programming Environment LaboratoryThe Institute of Technology
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar

doi
isbn
urn-nbn

Altmetric score

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

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • oxford
  • 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