Change search
Link to record
Permanent link

Direct link
Publications (3 of 3) Show all publications
Unterkalmsteiner, M. & Gorschek, T. (2018). Process Improvement Archaeology: What led us here and what’s next?. IEEE Software, 35(4), 53-61
Open this publication in new window or tab >>Process Improvement Archaeology: What led us here and what’s next?
2018 (English)In: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 35, no 4, p. 53-61Article in journal (Refereed) Published
Abstract [en]

While in every organization corporate culture and history change over time, intentional efforts to identifyperformance problems are of particular interest when trying to understand the current state of an organization.The results of past improvement initiatives can shed light on the evolution of an organization, and represent,with the advantage of perfect hindsight, a learning opportunity for future process improvements. Weencountered the opportunity to test this premise in an applied research collaboration with the SwedishTransport Administration (STA), the government agency responsible for the planning, implementation andmaintenance of long-term rail, road, shipping and aviation infrastructure in Sweden.

Place, publisher, year, edition, pages
IEEE Computer Society, 2018
Keywords
requirerements engineering, process archaeology
National Category
Software Engineering
Research subject
FOI-portföljer, Planera
Identifiers
urn:nbn:se:trafikverket:diva-5593 (URN)10.1109/MS.2018.227110005 (DOI)000438129500008 ()
Projects
Utveckling och effektivisering av regelverk, regelverkskrav och projektkrav, genom förbättrad specifikation, analys och kommunikation (ERSAK)
Funder
Swedish Transport Administration, TRV 2015/24274
Available from: 2022-10-07 Created: 2022-10-07 Last updated: 2022-10-07
Unterkalmsteiner, M. & Gorschek, T. (2017). Requirements quality assurance in industry: Why, what and how?. In: Lecture Notes in Computer Science: . Paper presented at 23rd International Working Conference on Requirements Engineering – Foundation for Software Quality, REFSQ, Essen (pp. 77-84). Springer
Open this publication in new window or tab >>Requirements quality assurance in industry: Why, what and how?
2017 (English)In: Lecture Notes in Computer Science, Springer , 2017, p. 77-84Conference paper, Published paper (Refereed)
Abstract [en]

Context and Motivation: Natural language is the most common form to specify requirements in industry. The quality of the specification depends on the capability of the writer to formulate requirements aimed at different stakeholders: they are an expression of the customer’s needs that are used by analysts, designers and testers. Given this central role of requirements as a mean to communicate intention, assuring their quality is essential to reduce misunderstandings that lead to potential waste. Problem: Quality assurance of requirement specifications is largely a manual effort that requires expertise and domain knowledge. However, this demanding cognitive process is also congested by trivial quality issues that should not occur in the first place. Principal ideas: We propose a taxonomy of requirements quality assurance complexity that characterizes cognitive load of verifying a quality aspect from the human perspective, and automation complexity and accuracy from the machine perspective. Contribution: Once this taxonomy is realized and validated, it can serve as the basis for a decision framework of automated requirements quality assurance support.

Place, publisher, year, edition, pages
Springer, 2017
Series
Trafikverkets forskningsportföljer
Keywords
Decision support, Natural language processing, Requirements engineering, Requirements quality, Computer software selection and evaluation, Decision support systems, Natural language processing systems, Specifications, Taxonomies, Cognitive process, Decision framework, Decision supports, Domain knowledge, Human perspectives, Natural languages, Requirement specification, Quality assurance
National Category
Software Engineering
Research subject
FOI-portföljer, Planera
Identifiers
urn:nbn:se:trafikverket:diva-5513 (URN)10.1007/978-3-319-54045-0_6 (DOI)000418400900006 ()2-s2.0-85013916456 (Scopus ID)978-3-319-54044-3 (ISBN)
Conference
23rd International Working Conference on Requirements Engineering – Foundation for Software Quality, REFSQ, Essen
Projects
Utveckling och effektivisering av regelverk, regelverkskrav och projektkrav, genom förbättrad specifikation, analys och kommunikation (ERSAK)
Funder
Swedish Transport Administration, TRV 2015/24274
Available from: 2017-03-16 Created: 2022-09-29 Last updated: 2023-02-01Bibliographically approved
Femmer, H., Unterkalmsteiner, M. & Gorschek, T. (2017). Which requirements artifact quality defects are automatically detectable?: A case study. In: Proceedings - 2017 IEEE 25th International Requirements Engineering Conference Workshops, REW 2017: . Paper presented at Fourth International Workshop on Artificial Intelligence for Requirements Engineering (AIRE'17), Lisboa (pp. 400-406). IEEE, Article ID 8054884.
Open this publication in new window or tab >>Which requirements artifact quality defects are automatically detectable?: A case study
2017 (English)In: Proceedings - 2017 IEEE 25th International Requirements Engineering Conference Workshops, REW 2017, IEEE , 2017, p. 400-406, article id 8054884Conference paper, Published paper (Refereed)
Abstract [en]

[Context:] The quality of requirements engineeringartifacts, e.g. requirements specifications, is acknowledged tobe an important success factor for projects. Therefore, manycompanies spend significant amounts of money to control thequality of their RE artifacts. To reduce spending and improvethe RE artifact quality, methods were proposed that combinemanual quality control, i.e. reviews, with automated approaches.[Problem:] So far, we have seen various approaches to auto-matically detect certain aspects in RE artifacts. However, westill lack an overview what can and cannot be automaticallydetected. [Approach:] Starting from an industry guideline forRE artifacts, we classify 166 existing rules for RE artifacts alongvarious categories to discuss the share and the characteristics ofthose rules that can be automated. For those rules, that cannotbe automated, we discuss the main reasons. [Contribution:] Weestimate that 53% of the 166 rules can be checked automaticallyeither perfectly or with a good heuristic. Most rules need onlysimple techniques for checking. The main reason why some rulesresist automation is due to imprecise definition. [Impact:] Bygiving first estimates and analyses of automatically detectable andnot automatically detectable rule violations, we aim to provide anoverview of the potential of automated methods in requirementsquality control.

Place, publisher, year, edition, pages
IEEE, 2017
Series
Trafikverkets forskningsportföljer
Keywords
Artifact quality, Automated methods, Requirement engineering
National Category
Software Engineering
Research subject
FOI-portföljer, Planera
Identifiers
urn:nbn:se:trafikverket:diva-5510 (URN)10.1109/REW.2017.18 (DOI)000427148000063 ()9781538634882 (ISBN)
Conference
Fourth International Workshop on Artificial Intelligence for Requirements Engineering (AIRE'17), Lisboa
Projects
Utveckling och effektivisering av regelverk, regelverkskrav och projektkrav, genom förbättrad specifikation, analys och kommunikation (ERSAK)
Funder
Swedish Transport Administration, TRV 2015/24274
Available from: 2022-09-29 Created: 2022-09-29 Last updated: 2022-09-29
Projects
PLEng – Professional Licentiate of Engineering School [20170213]; Blekinge Institute of TechnologySERT- Software Engineering ReThought [20180010]; Blekinge Institute of TechnologyProfessional Master in Information Security (PROMIS) [20210026]; Blekinge Institute of Technology
Organisations
Identifiers
ORCID iD: ORCID iD iconorcid.org/0000-0002-3646-235x

Search in DiVA

Show all publications