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
Good Practice and Improvement Model of Handling Capacity Requirements of Large Telecommunication Systems
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.
2006 (English)In: 14th IEEE International Requirements Engineering Conference (RE'06), Minneapolis/S:t Paul, Los Alamitos, CA: IEEE Computer Society , 2006, 245-250 p.Conference paper, Published paper (Refereed)
Abstract [en]

There is evidence to suggest that the software industry has not yet matured as regards management of nonfunctional requirements (NFRs). Consequently the cost of achieving required quality is unnecessarily high. To try and avoid this, the telecommunication systems provider Ericsson defined a research task to try and improve the management of requirements for capacity, which is one of the most critical NFRs. Linkoping University joined in the effort and conducted an interview series to investigate good practice within different parts of the company. Inspired by the interviews and an ongoing process improvement project a model for improvement was created and activities were synthesized. This paper contributes the results from the interview series, and details the subprocesses of specification that should be improved. Such improvements are about understanding the relationship between numerical entities at all system levels, augmenting UML specifications to make NFRs visible, working with time budgets, and testing the sub system level components on the same level as they are specified.

Place, publisher, year, edition, pages
Los Alamitos, CA: IEEE Computer Society , 2006. 245-250 p.
Keyword [en]
Non-functional requirements, capacity, process improvement
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:liu:diva-16791DOI: 10.1109/RE.2006.28ISBN: 0-7695-2555-5 (print)ISBN: 978-0-7695-2555-6 (print)OAI: oai:DiVA.org:liu-16791DiVA: diva2:174086
Available from: 2009-02-19 Created: 2009-02-19 Last updated: 2009-02-25Bibliographically 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: 150 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