Applying Application Lifecycle Management for the Development of Complex Systems: Experiences from the Automation Industry

Kääriäinen, Jukka; Välimäki, Antti

doi:10.1007/978-3-642-04133-4_13

Cited by 11 publications

(7 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…4). This comparison, initiated by the software CM community, leads to the conclusion that PDM should be able to manage software data if PDM allows "SCM version control operations, such as branch/merge and code comparisons" [7].…”

Section: Description Of Branching / Merging Concepts In Software Desimentioning

confidence: 99%

Towards PLM for Mechatronics System Design Using Concurrent Software Versioning Principles

Bricogne

Rivest

Troussier

et al. 2012

Product Lifecycle Management. Towards Knowledge-Rich Enterprises

View full text Add to dashboard Cite

show abstract

Section: Description Of Branching / Merging Concepts In Software Desimentioning

confidence: 99%

Towards PLM for Mechatronics System Design Using Concurrent Software Versioning Principles

Bricogne

Rivest

Troussier

et al. 2012

Product Lifecycle Management. Towards Knowledge-Rich Enterprises

View full text Add to dashboard Cite

show abstract

“…We posit that existing tools supporting the alignment are inadequate because the two roles do not share them, with product managers using business-oriented tools [28], and software architects using technical tools [29]. Additionally, the deep integration we seek goes beyond the coordination of activities and management of artifacts offered by traditional Application Lifecycle Management and its tools [32].…”

Section: Discussionmentioning

confidence: 99%

Bridging the Twin Peaks -- The Case of the Software Industry

Lucassen

Dalpiaz

Werf

et al. 2015

2015 IEEE/ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture

View full text Add to dashboard Cite

We review the relationship between software architecture and requirements in the context of software products. Based on empirical evidence from a comparative case study, we promote four positions: (1) the requirements/architecture alignment problem for software products is inherently different than the same problem for tailor-made software; (2) bridging the Twin Peaks corresponds to defining and enacting a stepwise evolution of the product architecture; (3) communication tasks are ascribed to the product manager rather than the architect; and (4) integrated and cross-disciplinary tools are key to maintain requirements/architecture alignment. We argue that these positions motivate and characterize future research in the field.

show abstract

“…Focusing on the basic functions (version control, concurrent development, configuration selection and workspace management), SCM is very similar to PDM, as the Application Lifecycle Management (ALM) can be compared to PLM. ALM "has emerged to indicate the coordination of activities and the management of artefacts (e.g., requirements, source code, test cases) during the software product's lifecycle" [11]. ALM comes from the Configuration Management (CM) domain, which traditionally provides storage, versioning and traceability between all artefacts.…”

Section: State-of-the-art Analysismentioning

confidence: 99%

Meta-Model of PLM for Design of Systems of Systems

Hehenberger

Bricogne

Duigou

et al. 2016

Product Lifecycle Management in the Era of Internet of Things

View full text Add to dashboard Cite

Mechatronic System Design involves close examination and further development of design methods, design processes, models and tools. The current trend in mechatronics involves networked mechatronic systems, or cyber physical systems (CPS), which can also be considered as a sub-part of Systems of Systems (SoS). Therefore data models for the description of the product lifecycle of SoS are necessary on the base of existing meta-models for single (mechatronic) systems. The paper shows a meta-model of PLM for the design of SoS and discusses the influence of the IT-architecture in supporting the PLM interoperability.

show abstract

Applying Application Lifecycle Management for the Development of Complex Systems: Experiences from the Automation Industry

Cited by 11 publications

References 11 publications

Towards PLM for Mechatronics System Design Using Concurrent Software Versioning Principles

Towards PLM for Mechatronics System Design Using Concurrent Software Versioning Principles

Bridging the Twin Peaks -- The Case of the Software Industry

Meta-Model of PLM for Design of Systems of Systems

Contact Info

Product

Resources

About