SwePub
Sök i SwePub databas

  Utökad sökning

Träfflista för sökning "FÖRF:(Ulf Eliasson) "

Sökning: FÖRF:(Ulf Eliasson)

  • Resultat 1-10 av 10
Sortera/gruppera träfflistan
   
NumreringReferensOmslagsbildHitta
1.
  • Wohlrab, Rebekka, 1991, et al. (författare)
  • Improving the consistency and usefulness of architecture descriptions: Guidelines for architects
  • 2019
  • Ingår i: Proceedings - 2019 IEEE International Conference on Software Architecture, ICSA 2019. ; , s. 151-160
  • Konferensbidrag (refereegranskat)abstract
    • The need to support software architecture evolution has been well recognized, even more since the rise of agile methods. However, assuring the conformance between architecture descriptions and the implementation remains challenging. Inconsistencies emanate among multiple architecture descriptions, and between architecture descriptions and code. As a consequence, architecture descriptions are not always trusted and used to the extent that their authors wish for. In this paper, we present two surveys with 93 and 72 participants to examine architectural inconsistencies, with a focus on how they evolve over time and can be mitigated using practical guidelines. We identified the importance of capturing emerging elements to keep the architecture description consistent with the implementation, and consider the current-state and future-state architecture separately. Consequences of inconsistencies typically arise at later stages, especially if an architecture description concerns multiple teams. Our guidelines suggest to limit the upfront architecture to stable decisions, while paying attention to concerns that matter across team borders. In the ideal case, companies should aim to integrate architects into the teams to capture emerging aspects with time.
  •  
2.
  • Yang, Chen, et al. (författare)
  • An industrial case study on an Architectural Assumption Documentation Framework
  • 2017
  • Ingår i: Journal of Systems and Software. - : Elsevier BV. - 0164-1212. ; 134, s. 190-210
  • Tidskriftsartikel (refereegranskat)abstract
    • As an important type of architectural knowledge, documenting architectural assumptions (AAs) is critical to the success of projects. In this work, we proposed and validated an Architectural Assumption Documentation Framework (AADF), which is composed of four viewpoints (i.e., the Detail, Relationship, Tracing, and Evolution viewpoint), to document AAs in projects. One case study with two cases was conducted at two companies from different domains and countries. The main findings are: (1) AADF can be understood by architects in a short time (i.e., a half day workshop); (2) the AA Evolution view requires the least time to create, followed by the AA Detail view and the AA Relationship view; (3) AADF can help stakeholders to identify risks and understand AAs documented by other stakeholders; and (4) understanding and applying AADF is related to various factors, including factors regarding the framework per se (e.g., tutorial, examples, concepts, and terms), personal experience, resources (e.g., time), tool support, and project context (e.g., project size and number of AAs). Adjusting these factors in an appropriate way can facilitate the usage of AADF and further benefit the projects.
  •  
3.
  • Yang, Chen, et al. (författare)
  • Architectural assumptions and their management in industry – An exploratory study
  • 2017
  • Ingår i: Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics). - Cham : Springer International Publishing. - 1611-3349 .- 0302-9743. ; 10475 LNCS, s. 191-207
  • Konferensbidrag (refereegranskat)abstract
    • As an important type of architectural knowledge, architectural assumptions should be well managed in projects. However, little empirical research has been conducted regarding architectural assumptions and their management in software development. In this paper, we conducted an exploratory case study with twenty-four architects to analyze architectural assumptions and their management in industry. In this study, we confirmed certain findings from our previous survey on architectural assumptions (e.g., neither the term nor the concept of architectural assumption is commonly used in industry, and stakeholders may have different understandings of the architectural assumption concept). We also got five new findings: (1) architects frequently make architectural assumptions in their work; (2) the architectural assumption concept is subjective; (3) architectural assumptions are context-dependent and have a dynamic nature (e.g., turning out to be invalid or vice versa during their lifecycle); (4) there is a connection between architectural assumptions and certain types of software artifacts (e.g., requirements and design decisions); (5) twelve architectural assumptions management activities and four benefits of managing architectural assumptions were identified. © 2017, Springer International Publishing AG.
  •  
4.
  • Heldal, Rogardt, 1964, et al. (författare)
  • Descriptive vs Prescriptive Models in Industry
  • 2016
  • Ingår i: Proceedings of the ACM/IEEE 19th International Conference on Model Driven Engineering Languages and Systems (MODELS 2016). - New York, NY, USA : ACM. - 9781450343213 ; , s. 216-226
  • Konferensbidrag (refereegranskat)abstract
    • To understand the importance, characteristics, and limitations of modeling we need to consider the context where models are used. Different organizations within the same company can use models for different purposes and modelling can involve different stakeholders and tools. Recently, several papers discussing how industries use MDE have been published and they have contradictory findings. In this paper we report lessons learned from our collaborations with three large companies. We found that it is important to distinguish between descriptive models (used for documentation) and prescriptive models (used for development) to better understand the adoption of modelling in industry. Our findings are valuable for both academia and industry. A better understanding of modeling in large companies can help academia conceiving innovative MDE solutions that can have a real impact in industry. On the other hand, industry can better understand how to properly exploit MDE and what to expect from it.
  •  
5.
  • Eliasson, Ulf, 1984, et al. (författare)
  • Architecting in the Automotive Domain: Descriptive vs Prescriptive Architecture
  • 2015
  • Ingår i: 12th Working IEEE/IFIP Conference on Software Architecture (WICSA), 2015. - : IEEE. - 9781479919222 ; , s. 115-118
  • Konferensbidrag (refereegranskat)abstract
    • To investigate the new requirements and challenges of architecting often safety critical software in the automotive domain, we have performed two case studies on Volvo Car Group and Volvo Group Truck Technology. Our findings suggest that automotive software architects produce two different architectures (or views) of the same system. The first one is a high-level descriptive architecture, mainly documenting system design decisions and describing principles and guidelines that should govern the overall system. The second architecture is the working architecture, defining the actual blueprint for the implementation teams and being used in their daily work. The working architecture is characterized by high complexity and considerably lower readability than the high-level architecture. Unfortunately, the team responsible for the high-level architecture tends to get isolated from the rest of the development organization, with few communications except regarding the working architecture. This creates tensions within the organizations, sub-optimal design of the communication matrix and limited usage of the high-level architecture in the development teams. To adapt to the current pace of software development and rapidly growing software systems new ways of working are required, both on technical and on an organizational level.
  •  
6.
  • Eliasson, Ulf, 1984, et al. (författare)
  • Identifying and Visualizing Architectural Debt and Its Efficiency Interest in the Automotive Domain: A Case Study
  • 2015
  • Ingår i: 2015 Ieee 7th International Workshop on Managing Technical Debt (Mtd) Proceedings. - : IEEE. - 9781467373784
  • Konferensbidrag (refereegranskat)abstract
    • Architectural Technical Debt has recently received the attention of the scientific community, as a suitable metaphor for describing sub-optimal architectural solutions having short-term benefits but causing a long-term negative impact. We study such phenomenon in the context of Volvo Car Group, where the development of modern cars includes complex systems with mechanical components, electronics and software working together in a complicated network to perform an increasing number of functions and meet the demands of many customers. This puts high requirements on having an architecture and design that can handle these demands. Therefore, it is of utmost importance to manage Architecture Technical Debt, in order to make sure that the advantages of sub-optimal solutions do not lead to the payment of a large interest. We conducted a case study at Volvo Car Group and we discovered that architectural violations in the detailed design had an impact on the efficiency of the communication between components, which is an essential quality in cars and other embedded systems. Such interest is not studied in literature, which usually focuses on the maintainability aspects of Technical Debt. To explore how this Architectural Technical Debt and its interest could be communicated to stakeholders, we developed a visual tool. We found that not only was the Architectural Debt highly interesting for the architects and other stakeholders at VCG, but the proposed visualization was useful in increasing the awareness of the impact that Architectural Technical Debt had on efficiency.
  •  
7.
  • Eliasson, Ulf, 1984, et al. (författare)
  • The Need of Complementing Plan-Driven Requirements Engineering with Emerging Communication: Experiences from Volvo Car Group
  • 2015
  • Ingår i: 23rd IEEE International Requirements Engineering Conference, RE 2015, Ottawa, Canada, 24-28 August. - : IEEE. - 9781467369053
  • Konferensbidrag (refereegranskat)abstract
    • The automotive industry is currently going through an enormous change, transitioning from being pure hardware and mechanical companies to becoming more software focused. Currently, software development is embedded into a V-Model process that defines how software requirements are extracted from system requirements. In recent years, OEMs have come to recognize the importance and opportunities offered by software, which include better management and shorter time-to-market of distinguishing features. Strategies to better utilize software include in-house software development and new ways to collaborate with suppliers. However, in their effort to take advantage of these opportunities, engineers struggle with the formal process imposed on software development. In this paper, we investigate the impact of this struggle on the flow of requirements, including challenges and practices. We found that new ways of working with requirements had emerged that are partly not supported, partly hindered by the old tooling and processes for requirements engineering. Requirements flow both vertical and horizontal in the organization and across the supply-chain. Support for the new way of working should allow us to refine requirements iteratively throughout their life-cycle, handle the discussion of rationales, and to manage assumptions. We found strategies of achieving this to differ not only between OEMs, but also between different divisions inside the OEMs.
  •  
8.
  • Eliasson, Ulf, 1984, et al. (författare)
  • Agile Model-Driven Engineering in Mechatronic Systems - An Industrial Case Study
  • 2014
  • Ingår i: Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics). - Cham : Springer International Publishing. - 1611-3349 .- 0302-9743. - 9783319116532 ; 8767, s. 433-449
  • Tidskriftsartikel (refereegranskat)abstract
    • Model-driven engineering focuses on structuring systems as well as permitting domain experts to be directly involved in the software development. Agile methods aim for fast feedback and providing crucial knowledge early in the project. In our study, we have seen a successful combination of MDE and agile methods to support the development of complex, software-driven mechatronic systems. We have investigated how combining MDE and agile methods can reduce the number of issues caused by erroneous assumptions in the software of these mechatronic systems. Our results show that plant models to simulate mechanical systems are needed to enable agile MDE during the mechatronic development. They enable developers to run, verify, and validate models before the mechanical systems are delivered from suppliers. While two case studies conducted at Volvo Car Group confirm that combining MDE and agile works, there are still challenges e.g. how to optimize the development of plant models.
  •  
9.
  • Eliasson, Ulf, 1984, et al. (författare)
  • Extending Agile Practices in Automotive MDE
  • 2013
  • Ingår i: XM 2013, Extreme Modeling Workshop. ; , s. 11-19
  • Konferensbidrag (refereegranskat)abstract
    • The size and functionality of the software in a modern car increases with each new generation. To stay competitive automotive manufactures must deliver new and better features to their customers at the same speed or faster than their competitors. A traditional waterfall process is not suitable for this speed challenge - a more agile way of working is desirable. By introducing MDE we have seen how individual teams at Volvo Cars adopt agile practices, resulting in tensions while the organization at large still uses a waterfall process. In an exploratory case study we interviewed 18 engineers to better understand how agile practices can be extended beyond individual teams. Where the tensions have their source in the technical specification of the software components and their interfaces, it turns out that it is company culture and mindsets that are the main hurdles to overcome.
  •  
10.
  • Eliasson, Ulf, 1965- (författare)
  • Övervakning i försvarets intresse : Säkerhetspolisens övervakning och registrering av ytterlighetspartier 1917-1945
  • 2005
  • Doktorsavhandling (övrigt vetenskapligt/konstnärligt)abstract
    • This thesis is focusing on two key questions. 1. Why and to what extent did the Swedish security service monitor and register sympathizers of the extremist political parties at the end of World War I and in the subsequent inter-war period? 2. To what extent did the Swedish government - by means of inspection, observation and management - control the surveillance and registration of the extremist political parties by the security service in 1917-1945? The study compares the development in Sweden with a trajectory of development that is formulated in the literature from observations mainly in Canada and Australia. The characteristics of this trajectory are that security agencies in the 20thcentury were autonomous in their relation with the government and expansionist in terms of their surveillance activities. This dissertation comes to two key conclusions. The first is that the surveillance and registration of Communists during the inter-war period intensified in 1930 when the military’s perception of the communist threat shifted. In 1928 the Communist movement formulated a new tactic of infiltrating the armed forces; in consequence the military introduced loyalty tests of its personnel (security vetting). The second conclusion is that the military’s and, in the winter of 1939, the government’s expansionist view of the need for surveillance and registration of the extremist political parties stands in sharp contrast to the restrictive view on this issue that was formulated by the security service. Partly as a result of this attitude of the security service, the Minister of Justice and the Minister of Social Affairs controlled the Swedish security service during World War II. I argue that the Swedish security service was restrictive rather than expansionist in its view of the surveillance and registration of the political extremist parties in 1917-1945. I also make the case that its relationship with the government on issues related to these activities was characterized by control rather than by autonomy.
  •  
Skapa referenser, mejla, bekava och länka
  • Resultat 1-10 av 10

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