Navigating the Challenges of Novel System Development in Energy and Aviation with MBSE and Agile Methodologies

Developing new product/system in the energy, aviation and space sectors faces intense pressure. Investors demand faster returns, budgets are tight, and the technologies involved often lack proven track records or clear regulatory frameworks. These factors squeeze development timelines and limit the number of iterations teams can afford. To succeed, businesses must find ways to innovate quickly without sacrificing quality or safety and reliability.

In traditional engineering development environments, function based organisational structures like Programme , Mechanical Design , Electrical Design, Software Engineering, Production, Supply Chain, Quality etc following a linear development lifecycles like waterfall method are applied, the product design follows sequential stages where requirements are frozen before a concurrent functional design with gated reviews or ad-hoc reviews enable the product or system lifecycle to progress into production and so on. However, without an overarching Systems Engineering framework, the traditional process can lead to silos due lack of information dissemination in real time or lack of coordination of interdisciplinary design conflicts. This highlights the importance of Systems Engineering. Imagine Systems Engineering as the grand conductor of a symphony orchestra, where every instrument—be it hardware, software, teams, or timelines—plays in perfect harmony. At its core, Systems Engineering is a holistic, interdisciplinary approach that integrates people, processes, and technologies to design, build, and sustain complex systems.

However, traditional Systems Engineering emphasises on upfront planning, comprehensive architecture analysis, establishing traceability and risk mitigation in multiple stages. At each stage of development lifecycle, the process captures data in system artefacts to establish validated data as part of development assurance. This process may be perceived as resource heavy, rigid and unnecessary bureaucracy. Businesses with strict development budgets and particularly new start-up's in energy, aviation, space and medical industries face a reality of limited resources, high market uncertainty, expectation of faster turnaround times and a need for quick market validation to assure investors and other stakeholders.

Summary of Challenges in Developing Novel Systems

Businesses in energy and aviation face several hurdles when creating new system architectures:

• Limited development time: Tight budgets and investor expectations force teams to deliver results quickly, reducing opportunities for multiple design iterations.

• Unproven technologies: Emerging tech often lacks extensive testing or regulatory approval, increasing uncertainty and risk.

• Lack of regulatory frameworks: Without clear standards, teams must navigate compliance on their own, which can slow progress.

• Resource constraints: Smaller teams or startups may not have access to all necessary expertise or tools.

  
  

These challenges make traditional linear development approaches inefficient. Teams need flexible, transparent processes that allow continuous learning and adjustment.

One effective approach combines Model-Based Systems Engineering (MBSE) with agile methodologies. This blend helps teams manage complexity, assess risks early, and adapt rapidly to change. The following sections explore how this works in practice, using a neuro modulation wearable device for Parkinson’s patients as an example. We will also discuss ideal team structures and how Vishwakarma Systems supports businesses adopting these methods.

How MBSE and Agile Methodologies Address These Challenges

MBSE uses formal models to represent system requirements, design, and behaviour. This creates a shared, up-to-date understanding among stakeholders and reduces errors caused by miscommunication. MBSE inherently resolves multidisciplinary design conflicts in real time with updates to models. Agile methods focus on iterative development, frequent feedback, and adapting plans based on real-world insights.

Together, they offer several benefits:

• Clear visualization of system architecture: MBSE models help teams see dependencies and potential conflicts early.

• Early risk identification: Technical risks can be assessed alongside use cases, allowing mitigation strategies before costly mistakes.

• Faster feedback loops: Agile sprints enable rapid prototyping and testing of components.

• Improved collaboration: Cross-functional teams work closely, sharing knowledge and adjusting priorities dynamically.

A Practical Example: Neuro Modulation Wearable Device for Parkinson’s Patients

Prototype of a neuro modulation wearable device designed to assist Parkinson’s patients

Imagine a start up developing a wearable device that delivers neuro modulation therapy to ease Parkinson’s symptoms. The device must be safe, effective, and comfortable, while complying with medical regulations.

Using Use Case Models

• Patient activating therapy during tremors

• Doctor adjusting therapy parameters remotely

• Device alerting caregiver in emergencies

  
  

Use cases guide requirements and help prioritize features for early development.

Integrating Technical Risk Assessment

Alongside use case modelling, the team performs technical risk assessments. For example:

• Battery life may limit therapy duration

• Wireless communication could face interference

• Sensor accuracy affects therapy effectiveness

  
  

Each risk is linked to specific use cases and system components in the MBSE model. This connection helps the team focus on high-impact risks during agile sprints.

Combining MBSE and Agile

The MBSE model serves as a living document updated after each sprint. The team uses it to:

• Track progress against requirements

• Visualize system changes and impacts

• Communicate status with stakeholders

  
  

Agile ceremonies like sprint planning and retrospectives incorporate MBSE insights, ensuring alignment between design and implementation.

Multidisciplinary team collaborating on system design and agile planning

Multidisciplinary team collaborating on system design and agile planning

Team Configuration and Roles

Successful implementation requires a well-structured team with clear roles:

• Systems Engineer: Leads MBSE modeling, ensures requirements traceability, and manages risk assessments.

• Product Owner: Represents customer needs, prioritizes backlog items based on use cases.

• Software and Hardware Engineers: Develop components in iterative cycles, provide feedback on technical feasibility.

• Quality Assurance: Tests prototypes, verifies compliance with safety and regulatory standards.

• Regulatory Specialist: Advises on applicable regulations and documentation requirements.

• Project Manager/Scrum Master: Facilitates agile processes, removes blockers, and maintains team focus.

  
  

Close collaboration and frequent communication among these roles enable rapid problem-solving and continuous improvement.

How Vishwakarma Systems Supports Businesses

Vishwakarma Systems brings extensive experience in applying MBSE combined with agile methods across complex industries. Their expertise includes:

• Tailoring MBSE frameworks to specific project needs

• Integrating risk management into system models

• Training teams on agile practices aligned with MBSE

• Providing tools and templates for efficient modelling and documentation

• Supporting regulatory compliance through structured processes

  
  

By partnering with Vishwakarma Systems, businesses can accelerate development, reduce costly errors, and improve stakeholder confidence.