scholarly journals INTEGRATION OF BLOCKCHAIN TECHNOLOGIE IN CASE OF SYSTEMS ENGINEERING AND SOFTWARE ENGINEERING IN AN INDUSTRIAL CONTEXT

2021 ◽  
Vol 1 ◽  
pp. 1887-1896
Author(s):  
Vahid Salehi
Keyword(s):  
Software Engineering ◽  
Systems Engineering ◽  
Data Entry ◽  
Product Lifecycle Management ◽  
Vehicle Engineering ◽  
Blockchain Technology ◽  
Software Engineering Process ◽  
Lifecycle Management ◽  
Model Based Systems Engineering ◽  
Industrial Context

AbstractCurrently, inconsistent software versions lead to massive challenges for many car manufacturers. This is partly because within the product lifecycle management and the software engineering process, there is no correct handling of software versions for the “data entry” (installation of software on the ECU) of the vehicles. Furthermore, there are currently major challenges for many vehicle manufacturers to ensure transparency, integrity and full traceability of SW data status vis-à-vis the legislator. To counteract these challenges, new solutions in the field of vehicle engineering are to be developed based on a new platform called “CarEngChainNet” and Blockchain technology. On the basis of the “CarEngChainNet” platform, new main and sub-chain chains will be developed that allow tamper-proof SW data management (Peer to Peer and crypto technology) across the entire PLM chain with new methods such as model-based systems engineering of the requirement, function and integration of the SW components in different areas of vehicle development. The aim is to develop new transmission chains of vehicles with individually packaged software artefacts (e.g. ECU software) that can be securely transmitted from server to server into the vehicle.

scholarly journals Critical Information

2012 ◽  
Vol 134 (06) ◽  
pp. 32-35 ◽  
Author(s):  
Peter A. Bilello
Keyword(s):  
Best Practices ◽  
Systems Engineering ◽  
Product Lifecycle Management ◽  
Digital Design ◽  
Extended Enterprise ◽  
Product Lifecycle ◽  
Release Date ◽  
Product Release ◽  
Electrical Engineers ◽  
Lifecycle Management

This article discusses the shift to product lifecycle management (PLM) systems by various mechanical engineering companies. Systems engineers and information-handling experts are joining forces to get a grip on the information explosion, thanks primarily to the timely convergence of systems engineering with digital design and development. PLM supports the extended enterprise. The rationale behind using PLM is to ensure that the ideas and information driving the development of today’s products incorporate best practices and everything learned right up to the product-release date. The rapid increase in electronic controls and software that are being built into key auto components requires that mechanical engineers and electrical engineers work ever more closely together. This highlights the need to integrate the very different approaches to development that the two disciplines use. One of the key functions of PLM is to make sure all the data in those analyses are retained, not just the conclusions.

Towards a Unified Product and Project Lifecycle Model (PPLM) for Systems Engineering

2008 ◽  
Author(s):  
Valeria Perelman ◽  
Amira Sharon ◽  
Dov Dori
Keyword(s):  
Systems Engineering ◽  
Size Structure ◽  
Product Lifecycle Management ◽  
Multidisciplinary Teams ◽  
Product Lifecycle ◽  
Management Framework ◽  
Complex Products ◽  
Software And Hardware ◽  
Lifecycle Management ◽  
Project Lifecycle

Developing and sustaining complex systems requires collaboration of multidisciplinary teams, coordination of processes, methods and tools, allocation of resources and utilization of adequate facilities within enterprises. The system engineering management comprises three intertwined domains: the product, the project and the enterprise. Despite the obvious links between them, each is carried out using its distinct ontology and toolset. This conceptual separation hinders effective handling of the project and product lifecycle activities within the enterprise. Testing activities of complex products are focused on verifying the performance of increasingly large modules, from software and hardware components, through subassemblies to the entire operational system. What needs to be developed, tested, and delivered is determined by the product requirements, its functions, architecture, components, and their interactions. When each component should and can be developed and tested is determined by the project plan, which is dynamically re-estimated, re-evaluated, and re-planned depending on different parameters such as the project actual status compared with the plan, recourses availability, risks, technological breakthroughs or other impacting issues. Whether carrying out the development mission is feasible is determined by the responsible enterprise, its size, structure, management criteria, other projects running in parallel, commitments, and many other aspects. This paper introduces a unified project-product lifecycle management framework that attempts to address the problems cause by separating the product from the project that is supposed to deliver it within the executing enterprise.

Sign in / Sign up

Export Citation Format

Share Document