Course Schedule - ASEC 2025

Name :

Email :

Organisation :

Phone :

Country :

Subject :

...

Message :

Human or Robot :

Six + 6 = ?

Presenter : Constantin Neacsu

Presenter Bio :

Constantin Neacsu has ten years of experience in the engineering field, during which he has acquired and developed his acumen in many industries and positions, from automotive to aerospace, in design, manufacturing, testing and systems. For the past five years, Constantin has been architecting systems and evolving the MBSE expertise with fellow engineers from leading companies in the UK. Constantin has a Bachelor & Masters in Aeronautical & Aerospace Engineering from the University of Leeds in the United Kingdom. He is an Industry Process Senior Specialist in the CATIA Magic Cyber Systems team at Dassault Systemes, based in London. He is OMG OCSMP and INCOSE ASEP certified.

Session Description :

MBSE is an essential pillar of system engineering, and it has a prominent chapter in the INCOSE SE Handbook and the Vision 2035. Since its initial release in 2006, SysML has been synonymous with MBSE, and considered by many the de-facto language. The latest official version of SysML, v1.7, has many capabilities to specify and develop a product from a conceptual and logical perspective.

Despite that, many have considered SysML v1 to be insufficient and not fully capable of addressing all the needs of a complete system architecture. To address that, the OMG and system engineering community have come together to bring about a better language to address the limitations of SysML v1.

Introduce SysML v2. Despite the name, it is meant to be a revolution, rather than an evolution. SysML v2 is developed to address the issues of v1 and introduce new ways of developing system architectures and to connect stakeholders with themselves and their models.

The aim of this tutorial is to introduce the audience to the SysML v2 language and standard, and develop a simple product architecture model in a compatible and compliant modelling tool, capable of modelling the necessary features of any architectural model such a requirements, structure and behaviour. The modelling will be done in both the graphical and textual notation of SysML v2, to show the benefits of the new language. During the tutorial, differences between SYSML v1 and v2 languages will also be highlighted and clearly specified, enhancing the participants knowledge on where and how the two languages can be used.

At the end of the tutorial, the participants should have knowledge which will allow them to create a simple architectural model in SysML v2 to describe their product, as well as knowing when and how to use SysML v2 compared to v1.

Floor Plan :

Presenter : Constantin Neacsu

Presenter Bio :

Constantin Neacsu has ten years of experience in the engineering field, during which he has acquired and developed his acumen in many industries and positions, from automotive to aerospace, in design, manufacturing, testing and systems. For the past five years, Constantin has been architecting systems and evolving the MBSE expertise with fellow engineers from leading companies in the UK. Constantin has a Bachelor & Masters in Aeronautical & Aerospace Engineering from the University of Leeds in the United Kingdom. He is an Industry Process Senior Specialist in the CATIA Magic Cyber Systems team at Dassault Systemes, based in London. He is OMG OCSMP and INCOSE ASEP certified.

Session Description :

MBSE is an essential pillar of system engineering, and it has a prominent chapter in the INCOSE SE Handbook and the Vision 2035. Since its initial release in 2006, SysML has been synonymous with MBSE, and considered by many the de-facto language. The latest official version of SysML, v1.7, has many capabilities to specify and develop a product from a conceptual and logical perspective.

Despite that, many have considered SysML v1 to be insufficient and not fully capable of addressing all the needs of a complete system architecture. To address that, the OMG and system engineering community have come together to bring about a better language to address the limitations of SysML v1.

Introduce SysML v2. Despite the name, it is meant to be a revolution, rather than an evolution. SysML v2 is developed to address the issues of v1 and introduce new ways of developing system architectures and to connect stakeholders with themselves and their models.

The aim of this tutorial is to introduce the audience to the SysML v2 language and standard, and develop a simple product architecture model in a compatible and compliant modelling tool, capable of modelling the necessary features of any architectural model such a requirements, structure and behaviour. The modelling will be done in both the graphical and textual notation of SysML v2, to show the benefits of the new language. During the tutorial, differences between SYSML v1 and v2 languages will also be highlighted and clearly specified, enhancing the participants knowledge on where and how the two languages can be used.

At the end of the tutorial, the participants should have knowledge which will allow them to create a simple architectural model in SysML v2 to describe their product, as well as knowing when and how to use SysML v2 compared to v1.

Floor Plan :

Presenter : Paul Davies

Presenter Bio :

Paul Davies is semi-retired, and now part-time delivers training in Requirements and Interface Management, on behalf of PPI. Previously he was the Discipline Manager for Systems Engineering at Network Rail Infrastructure Projects. In that role he was responsible for promoting improvements in process and in practitioner competence in all aspects of systems engineering. Prior to this, he worked for Thales UK, with nearly thirty years’ experience in SE research, innovations management, SE functional leadership, and project engineering management. Over a succession of challenging projects with challenging customers, Paul learned many empirical lessons on integration and testing, internal and external to systems, and they are distilled here.

Paul is a Certified Systems Engineering Professional, a Past President of the UK Chapter of INCOSE, and has been a popular presenter and tutorial lead at many INCOSE events.

Session Description :

The path to acceptance of a new system is paved with pitfalls. System elements fail in integration testing, rework follows, then re-testing, and repeat as the full system is synthesised. The whole process can be difficult, time-consuming and inefficient.

But it doesn’t have to be. The good news is that principles and processes exist to cover progressive assurance of systems, backed by many decades of cross-industry practical experience. Trying to follow every recommendation can be as financially ruinous as skimping on the integration and test activities to meet milestones, and suffering the resultant rework costs.

The talk is based partly on the INCOSE Systems Engineering Handbook, and partly on the presenter’s INCOSE UK ‘Don’t Panic!’ guide to system integration and test (SIT). It will cover the following principles and techniques:

1. Establishing a common language - key concepts
2. Failure modes and effects (includes group activity)
3. Requirements and their relationship to SIT
4. Rich traceability and progressive assurance – V versus V, trust models
5. Planning and sequencing (includes group activity)
6. Assembling the evidence – a model to support the acceptance case

Floor Plan :

Presenter : Paul Davies

Presenter Bio :

Paul Davies is semi-retired, and now part-time delivers training in Requirements and Interface Management, on behalf of PPI. Previously he was the Discipline Manager for Systems Engineering at Network Rail Infrastructure Projects. In that role he was responsible for promoting improvements in process and in practitioner competence in all aspects of systems engineering. Prior to this, he worked for Thales UK, with nearly thirty years’ experience in SE research, innovations management, SE functional leadership, and project engineering management. Over a succession of challenging projects with challenging customers, Paul learned many empirical lessons on integration and testing, internal and external to systems, and they are distilled here.

Paul is a Certified Systems Engineering Professional, a Past President of the UK Chapter of INCOSE, and has been a popular presenter and tutorial lead at many INCOSE events.

Session Description :

The path to acceptance of a new system is paved with pitfalls. System elements fail in integration testing, rework follows, then re-testing, and repeat as the full system is synthesised. The whole process can be difficult, time-consuming and inefficient.

But it doesn’t have to be. The good news is that principles and processes exist to cover progressive assurance of systems, backed by many decades of cross-industry practical experience. Trying to follow every recommendation can be as financially ruinous as skimping on the integration and test activities to meet milestones, and suffering the resultant rework costs.

The talk is based partly on the INCOSE Systems Engineering Handbook, and partly on the presenter’s INCOSE UK ‘Don’t Panic!’ guide to system integration and test (SIT). It will cover the following principles and techniques:

1. Establishing a common language – key concepts
2. Failure modes and effects (includes group activity)
3. Requirements and their relationship to SIT
4. Rich traceability and progressive assurance – V versus V, trust models
5. Planning and sequencing (includes group activity)
6. Assembling the evidence – a model to support the acceptance case

Floor Plan :

Presenter : Prof. Jon Holt

Presenter Bio :

TBA

Session Description :

Jon Holt, the outgoing Technical Director of IfSE, will present an overview of the various 'review' processes that we have in place, and discuss the differences in the different variations. This will make it clearer to potential authors how the review processes work, and will enable people to create stronger submissions.

He will also talk about how Intellectual Property works in IfSE and the various permutations surrounding different publications.

Time	Title	Acc	App	Info
11:00 - 12:30	Developing an MBSE Architecture using SysML v2 (Part A)
13:30 - 15:00	Developing an MBSE Architecture using SysML v2 (Part B)

ASEC 2025 - Courses

Submit Question

Six + 6 = ?