SwePub
Sök i SwePub databas

  Extended search

Träfflista för sökning "WFRF:(Ehnebom Staffan) "

Search: WFRF:(Ehnebom Staffan)

  • Result 1-3 of 3
Sort/group result
   
EnumerationReferenceCoverFind
1.
  • Pareto, Lars, 1966, et al. (author)
  • Architectural Descriptions as Boundary Objects in System and Design Work
  • 2010
  • In: Lecture Notes in Computer Science. 13th International Conference on Model Driven Engineering Languages and Systems, MODELS 2010, Oslo, 3-8 October 2010. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 0302-9743. - 9783642161285 ; 6395, s. 406-419
  • Conference paper (peer-reviewed)abstract
    • Lean and Agile processes have resolved longstanding problems in engineering communication by replacing document based communication with face-to-face collaboration, but do not yet scale to very large and heterogeneous projects. This paper proposes a compatible extension to lean and agile processes that addresses this limitation. The core idea is to adopt the view of documentation as boundary objects: shared artefacts that maintain integrity across a project’s intersecting social worlds. The paper presents a case study, in which interviews with system engineers and designers were analysed to obtain requirements on an architectural description serving as boundary objects in a telecommunications project. The main result is a list of 18 empirically grounded, elementary requirements, worth considering when implementing lean and agile processes in the large.
  •  
2.
  • Pareto, Lars, 1966, et al. (author)
  • Collaborative Prioritization of Architectural Concerns
  • 2012
  • In: Journal of Systems and Software. - : Elsevier BV. - 0164-1212. ; 85:9, s. 1971-1994
  • Journal article (peer-reviewed)abstract
    • Efficient architecture work involves balancing the degree of architectural documentation with attention to needs, costs, agility and other factors. This paper presents a method for prioritizing architectural concerns in the presence of heterogeneous stakeholder groups in large organizations that need to evolve existing architecture. The method involves enquiry, analysis, and deliberation using collaborative and analytical techniques. Method outcomes are action principles directed to managers, and assessment of user needs directed to architects, along with evidence. The method results from 4 years of action research at Ericsson AB with the purpose of adding missing views to architectural documentation and removing superfluous ones. It is illustrated on a case where 29 senior engineers and managers within Ericsson prioritized 37 architectural concerns areas to arrive at 8 action principles, 5 prioritized improvement areas, and 24 improvement suggestions. Feedback from the organization is that the method has been effective in prioritizing architectural concerns, that data collection and analysis is more extensive compared to traditional prioritization practices, but that extensive analysis seems inevitable in architecture improvement work.
  •  
3.
  • Pareto, Lars, 1966, et al. (author)
  • Prioritizing Architectural Concerns
  • 2011
  • In: Software Architecture (WICSA), 2011 9th Working IEEE/IFIP Conference on. 20-24 June 2011, Boulder, Colorado, USA.. - 9781612843995 ; , s. 22-31
  • Conference paper (peer-reviewed)abstract
    • Efficient architecture work involves balancing the degree of architectural documentation with attention to needs, costs, agility and other factors. This paper presents a method for prioritizing architectural concerns in the presence of heterogeneous stakeholder groups in large organizations that need to evolve existing architecture. The method involves enquiry, analysis, and deliberation using collaborative and analytical techniques. Method outcomes are action principles directed to managers and improvement advice directed to architects along with evidence for recommendations made. The method results from 3 years of action research at Ericsson AB with the purpose of adding missing views to architectural documentation and removing superfluous ones. It is illustrated on a case where 29 senior engineers and managers within Ericsson prioritized 37 architectural concerns areas to arrive at 8 action principles, 5 prioritized improvement areas, and 24 improvement suggestions. Feedback from the organization is that the method has been effective in prioritizing architectural concerns, that data collection and analysis is more extensive compared to traditional prioritization practices, but that extensive analysis seems inevitable in architecture improvement work.
  •  
Skapa referenser, mejla, bekava och länka
  • Result 1-3 of 3
Type of publication
conference paper (2)
journal article (1)
Type of content
peer-reviewed (3)
Author/Editor
Eriksson, Peter (3)
Pareto, Lars, 1966 (3)
Ehnebom, Staffan (3)
Sandberg, Anna (2)
University
University of Gothenburg (3)
Language
English (3)
Research subject (UKÄ/SCB)
Natural sciences (3)

Year

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 Close

Copy and save the link in order to return to this view