SwePub
Sök i SwePub databas

  Utökad sökning

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

Sökning: LAR1:bth > (2000-2004) > Bosch Jan

  • Resultat 1-10 av 12
Sortera/gruppera träfflistan
   
NumreringReferensOmslagsbildHitta
1.
  • Bengtsson, PerOlof, et al. (författare)
  • An experiment on creating scenario profiles for software change
  • 2000
  • Ingår i: Annals of Software Engineering. - BUSSUM : BALTZER SCI PUBL BV. - 1022-7091 .- 1573-7489. ; 9:1-4, s. 59-78
  • Tidskriftsartikel (refereegranskat)abstract
    • Scenario profiles are used increasingly often for the assessment of quality attributes during the architectural design of software systems. However, the definition of scenario profiles is subjective and no data is available on the effects of individuals on scenario profiles. In this paper we present the design, analysis and results of a controlled experiment on the effect of individuals on scenario profiles, so that others can replicate the experiments on other projects and people. Both scenario profiles created by individuals and by groups are studied. The findings from the experiment showed that groups with prepared members proved to be the best method for creating scenario profiles. Unprepared groups did not perform better than individuals when creating scenario profiles.
  •  
2.
  • Bengtsson, PerOlof, et al. (författare)
  • Analyzing Software Architectures for Modifiability
  • 2000
  • Rapport (övrigt vetenskapligt/konstnärligt)abstract
    • The software architecture plays an important role in achieving a modifiable system, but few methods for modifiability analysis exist. In this paper, we propose an analysis method for software architecture modifiability that has successfully been applied in several cases. The method consists of five main steps, i.e. goal selection, software architecture description, scenario elicitation, scenario evaluation and interpretation.
  •  
3.
  •  
4.
  •  
5.
  •  
6.
  •  
7.
  • Lassing, Nico, et al. (författare)
  • Experiences with ALMA : Architecture-level modifiability analysis
  • 2002
  • Ingår i: Journal of Systems and Software. - NEW YORK : ELSEVIER SCIENCE INC. - 0164-1212 .- 1873-1228. ; 61:1, s. 47-57
  • Tidskriftsartikel (refereegranskat)abstract
    • Modifiability is an important quality for software systems, because a large part of the costs associated with these systems is spent on modifications. The effort, and therefore cost, that is required for these modifications is largely determined by a system's software architecture. Analysis of software architectures is therefore an important technique to achieve modifiability and reduce maintenance costs. However, few techniques for software architecture analysis currently exist. Based on our experiences with software architecture analysis of modifiability, we have developed ALMA, an architecture-level modifiability analysis method consisting of five steps. In this paper we report on our experiences with ALMA. We illustrate our experiences with examples from two case studies of software architecture analysis of modifiability. These case studies concern a system for mobile positioning at Ericsson Software Technology AB and a system for freight handling at DFDS Fraktarna. Our experiences are related to each step of the analysis process. In addition, we made some observations on software architecture analysis of modifiability in general. (C) 2002 Elsevier Science Inc. All rights reserved.
  •  
8.
  • Lassing, Nico, et al. (författare)
  • Experiences with SAA of Modifiability
  • 2000
  • Rapport (övrigt vetenskapligt/konstnärligt)abstract
    • Modifiability is an important quality for software systems, because a large part of the costs associated with these systems is spent on modifications. The effort, and therefore cost, that is required for these modifications is largely determined by a system’s software architecture. Analysis of software architectures is therefore an important technique to achieve modifiability and reduce maintenance costs. However, few techniques for software architecture analysis currently exist. Based on our experiences with software architecture analysis of modifiability, we have developed an analysis method consisting of five steps. In this paper we report on our experiences with this method. We illustrate our experiences with examples from two case studies of SAA of modifiability. These case studies concern a system for mobile positioning at Ericsson Software Techology and a system for freight handling at DFDS Fraktarna. Our experiences are related to each step of the analysis process. In addition, we made some observations on SAA of modifiability in general.
  •  
9.
  • Proceedings of the Fifth International Workshop on Component-Oriented Programming (WCOP 2000)
  • 2000
  • Rapport (övrigt vetenskapligt/konstnärligt)abstract
    • WCOP 2000, held in conjunction with ECOOP 2000 in Sophia Antipolis, France, was the fifth workshop in the successful series of workshops on component-oriented programming. The previous workshops were held in conjunction with the respective ECOOP conferences in Linz, Austria, Jyväskylä, Finland, Brussels, Belgium and Lisbon, Portugal. WCOP96 had focused on the principal idea of software components and worked towards definitions of terms. In particular, a high-level definition of what a software component is was formulated. WCOP97 concentrated on compositional aspects, architecture and gluing, substitutability, interface evolution, and non-functional requirements. WCOP98 had a closer look at issues arising in industrial practice and developed a major focus on the issues of adaptation. WCOP'99 moved on to address issues of component frameworks, structured architecture, and some bigger systems built using components frameworks. The topics for WCOP 2000 focused on component composition, validation and refinement and the use of component technology in the software industry.
  •  
10.
  • Software Product Lines : Three Examples
  • 2000
  • Rapport (övrigt vetenskapligt/konstnärligt)abstract
    • This report presents the results of a course on software product lines. The assignment in the course was to develop a software product line. . During the course, the students had to develop the following artifacts in groups: product line architecture, component designs, product derivations, modifiability assessment and a prototype. The results of the course are described in this report
  •  
Skapa referenser, mejla, bekava och länka
  • Resultat 1-10 av 12

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