SwePub
Sök i SwePub databas

  Utökad sökning

Träfflista för sökning "LAR1:bth srt2:(2000-2004);pers:(Svahnberg Mikael)"

Sökning: LAR1:bth > (2000-2004) > Svahnberg Mikael

  • Resultat 1-10 av 14
Sortera/gruppera träfflistan
   
NumreringReferensOmslagsbildHitta
1.
  •  
2.
  • Gorschek, Tony, et al. (författare)
  • Introduction and Application of a Lightweight Requirements Engineering Process
  • 2003
  • Konferensbidrag (refereegranskat)abstract
    • The lack of an adequate requirements specification is often blamed for the failure of many IT investments. Naturally, the requirements specification is the product of a requirements engineering process. Methods are required to evaluate the current requirements engineering process and identify where improvements are necessary making it possible to produce requirement specifications of high quality. Existing requirements engineering evaluation methods are often large, costly and time-consuming to use. Therefore we introduce a lightweight evaluation method, which we use to evaluate four industry projects. In this paper we outline the evaluation method, describe four industrial applications of the method and present an analysis of the findings. The results suggest that the proposed evaluation method is useful and the studied cases to a large extent have adequate requirements engineering processes although many important aspects are missing from their respective processes.
  •  
3.
  •  
4.
  •  
5.
  • Svahnberg, Mikael, et al. (författare)
  • A Quality-Driven Decision Support Method for Identifying Software Architecture Candidates
  • 2003
  • Ingår i: International journal of software engineering and knowledge engineering. - Singapore : World Scientific. - 0218-1940. ; 13:5, s. 547-573
  • Tidskriftsartikel (refereegranskat)abstract
    • To sustain the qualities of a software system during evolution, and to adapt the quality attributes as the requirements evolve, it is necessary to have a clear software architecture that is understood by all developers and to which all changes to the system adheres. This software architecture can be created beforehand, but must also be updated as the domain of the software, and hence the requirements on the software system evolve. Creating a software architecture for a system or part of a system so that the architecture fulfils the desired quality requirements is often hard. We propose a decision-support method to aid in the understanding of different architecture candidates for a software system. We propose a method that is adaptable with respect to both the set of potential architecture candidates and quality attributes relevant for the system's domain to help in this task. The method creates a support framework, using a multicriteria decision method, supporting comparison of different software architecture candidates for a specific software quality attribute and vice versa, and then uses this support framework to reach a consensus on the benefits and liabilities of the different software architecture candidates and to increase the confidence in the resulting architecture decision.
  •  
6.
  • Svahnberg, Mikael, et al. (författare)
  • A Study of Evolution Impact in Software Product Lines
  • 2000
  • Rapport (övrigt vetenskapligt/konstnärligt)abstract
    • Product-line architectures, i.e. a software architecture and component set shared by a family of products, represents a promising approach to achieving reuse of software. Several companies are initiating or have recently adopted a product-line architecture. However, little experience is available with respect to the evolution of the products, the software components and the software architecture. Due to the higher level of interdependency between the various software assets, software evolution is a more complex process. In this paper, we discuss the results of two case studies concentrating on the evolution of software assets in two swedish organizations that have employed the product-line architecture approach for several years. Based on these two cases, we discuss the commonalities, presented as categorizations of the evolution of the requirements, the software architecture and the software components, and also the differences between the two cases.
  •  
7.
  • Svahnberg, Mikael (författare)
  • A Study on Agreement between Participants in an Architecture Assessment
  • 2003
  • Konferensbidrag (refereegranskat)abstract
    • When conducting an architecture evaluation it is important that the right persons participate, so that as many views and aspects as possible of the architecture candidates are examined before development begins. At the same time, it is not cost efficient to include all stakeholders that might possibly have an opinion about the system. In this paper we investigate the amount of agreement between participants in an architecture assessment. The purpose of this s to identify which participants will provide unique views during a discussion and which participants share a similar view.
  •  
8.
  • Svahnberg, Mikael (författare)
  • An Industrial Study on Building Consensus Around Software Architectures and Quality Attributes
  • 2004
  • Ingår i: Information and Software Technology. - : Elsevier. - 0950-5849. ; 46:12, s. 805-818
  • Tidskriftsartikel (refereegranskat)abstract
    • When creating an architecture for a software system it is important to consider many aspects and different sides of these aspects at an early stage, lest they are misunderstood and cause problems at later stages during development. In this paper, we report from an industry study to understand and select between different architecture candidates. The company uses a method that focuses discussions of architecture candidates to where there are disagreements between the participating domain experts. The results indicate that the used method pinpoints for the company where further investigations are necessary and that the decision concerning which architecture to use is taken with more confidence as a result of the focused discussions.
  •  
9.
  • Svahnberg, Mikael, et al. (författare)
  • Conditions and Restrictions for Product Line Generation Migration.
  • 2002
  • Konferensbidrag (refereegranskat)abstract
    • In this paper, we describe a case study of a company in the domain of automatic guided vehicles (AGVs) that is in the process of migrating from a previous generation of a software product line, which has mainly been centered around hardware, into a new product-line generation which is software-centered. We describe the issues motivating this transition and the factors that complicate it. Moreover, we present a three-stage process for migrating to a new software product line. This process is currently being initiated in collaboration with the aforementioned company.
  •  
10.
  • Svahnberg, Mikael, et al. (författare)
  • Consensus Building when Comparing Software Architectures
  • 2002
  • Konferensbidrag (refereegranskat)abstract
    • When designing a software system it is beneficial to study and use architectural styles from literature, to ensure certain quality attributes. However, as the interpretation of literature may differ depending on the background and area of expertise of the person reading the literature, we suggest that structured discussions about different architecture candidates provides more valuable insight not only in the architectures themselves, but in peoples’ opinions of the architectures’ benefits and liabilities. In this paper, we propose a method to elicit the views of individuals concerning architecture candidates for a software system and pinpoint where discussions are needed to come to a consensus view of the architectures.
  •  
Skapa referenser, mejla, bekava och länka
  • Resultat 1-10 av 14

Kungliga biblioteket hanterar dina personuppgifter i enlighet med EU:s dataskyddsförordning (2018), GDPR. Läs mer om hur det funkar här.
Så här hanterar KB dina uppgifter vid användning av denna tjänst.

 
pil uppåt Stäng

Kopiera och spara länken för att återkomma till aktuell vy