Short answer

Implement a clear, layered methodology for defining use cases to ensure all project stakeholders, regardless of their industry background, share a common understanding of project goals and functionalities.

Field
Innovation & Markets
Source
World Electric Vehicle Journal (2023)
Method
Methodology development and application
Evidence
Strong effect

A structured, two-level use case methodology (business and technical) fosters a common understanding among diverse stakeholders, streamlining the development of complex, cross-industry solutions like smart EV charging. This innovation & markets research insight is drawn from a 2023 study published in World Electric Vehicle Journal. Using Methodology development and application, researchers explored how this design variable affects real-world outcomes. The key design takeaway: Implement a clear, layered methodology for defining use cases to ensure all project stakeholders, regardless of their industry background, share a common understanding of project goals and functionalities.

Study
Innovation & MarketsRecentStrong effect

Standardized Use Case Methodology Accelerates Cross-Industry Collaboration in Electromobility

A structured, two-level use case methodology (business and technical) fosters a common understanding among diverse stakeholders, streamlining the development of complex, cross-industry solutions like smart EV charging.

World Electric Vehicle Journal · 2023

01

Key Findings

  • 01A structured, two-level use case methodology (business and technical) can be effectively applied to complex, cross-industry projects.
  • 02The methodology promotes a uniform understanding of roles, processes, and interfaces among diverse stakeholders.
  • 03Application of the methodology identified 25 higher-level business use cases, revealing similarities and differences.
02

Application

Design takeaway

Implement a clear, layered methodology for defining use cases to ensure all project stakeholders, regardless of their industry background, share a common understanding of project goals and functionalities.

How to apply

When initiating a new design project involving multiple companies or departments, develop a clear framework for documenting use cases at both a strategic (business) and functional (technical) level.

Project actions

  • 01Clearly define the scope of your design project by creating detailed use cases.
  • 02Consider separating your use cases into business objectives and technical specifications to cater to different audiences.
03

Method & Evidence

AimHow can a standardized use case methodology facilitate effective collaboration and a shared understanding among diverse stakeholders in the development of complex, cross-industry solutions?
MethodMethodology development and application
ProcedureThe researchers developed a two-level use case methodology (business and technical) based on existing methods and project experience. This methodology was then applied across various project clusters to systematically describe use cases for smart electric vehicle charging.
ContextElectromobility, smart charging, cross-industry collaboration

Variables

IVUse case methodology (structured, two-level vs. unstructured/implicit)
DVStakeholder understanding, collaboration effectiveness, project development speed
CVProject domain (electromobility), number of stakeholders, type of interfaces
04

Strengths & Limitations

Strengths

  • +Provides a concrete, structured methodology for a complex problem.
  • +Demonstrates practical application and validation within a real-world project.

Limitations

The methodology might require significant upfront effort to establish, and its effectiveness could depend on the willingness of all parties to adopt it. The specific context of electromobility might not directly translate to all design fields.

Reliability & validity

Reliability would be enhanced by having multiple researchers apply the methodology and compare results. Validity is supported by its application in a real project and the identification of specific use cases, though further quantitative measures of collaboration effectiveness would strengthen it.

Think critically

To what extent does the complexity of the use case methodology itself pose a barrier to adoption in smaller or less resourced design projects?

05

Design Principles

"Standardization of communication protocols and requirement definitions is crucial for successful cross-disciplinary innovation."

Successfully integrating new technologies, especially in rapidly evolving sectors like electromobility, hinges on effective communication and alignment between disparate industry players. A standardized approach to defining requirements and interfaces, as demonstrated by this methodology, reduces ambiguity and accelerates the innovation process.

06

What This Means for Your Design

When lots of different companies need to work together on a new product, like electric car charging, it's important to have a clear way to describe what the product should do. This study shows that using a two-step method (one for business goals, one for technical details) helps everyone understand each other and makes the project run smoother.

How to use in your project

  • 1.Reference this study when discussing the importance of clear communication and stakeholder alignment in your design process, particularly when your project involves multiple disciplines or external partners.
07

Add to My Project

08

Quick Cite

Paragraph starter

The successful integration of complex, cross-industry solutions, such as those in the electromobility sector, necessitates a standardized approach to defining project requirements and fostering stakeholder alignment. Research by Ostermann et al. (2023) highlights the efficacy of a two-level use case methodology (business and technical) in creating a uniform understanding among diverse actors, thereby accelerating development and ensuring application-oriented usability. This approach is critical for bridging communication gaps and ensuring that all parties involved share a common vision for the project's objectives and functionalities.

09

Source

World Electric Vehicle Journal

Design and Application of the unIT-e2 Project Use Case Methodology

journal · 2023

View source

Questions About This Research

What does the research say about standardized use case methodology accelerates cross-industry collaboration in electromobility?
Implement a clear, layered methodology for defining use cases to ensure all project stakeholders, regardless of their industry background, share a common understanding of project goals and functionalities. Evidence: World Electric Vehicle Journal (2023).
Why does "Standardized Use Case Methodology Accelerates Cross-Industry Collaboration in Electromobility" matter for design?
Successfully integrating new technologies, especially in rapidly evolving sectors like electromobility, hinges on effective communication and alignment between disparate industry players. A standardized approach to defining requirements and interfaces, as demonstrated by this methodology, reduces ambiguity and accelerates the innovation process.
How can designers apply this research?
Implement a clear, layered methodology for defining use cases to ensure all project stakeholders, regardless of their industry background, share a common understanding of project goals and functionalities.
What were the main findings?
A structured, two-level use case methodology (business and technical) can be effectively applied to complex, cross-industry projects.. The methodology promotes a uniform understanding of roles, processes, and interfaces among diverse stakeholders.. Application of the methodology identified 25 higher-level business use cases, revealing similarities and differences.
What research method was used?
Methodology development and application.
How strong is the evidence?
Evidence strength is rated Strong effect, based on a 2023 journal from World Electric Vehicle Journal.
What should I do differently in my next project?
When initiating a new design project involving multiple companies or departments, develop a clear framework for documenting use cases at both a strategic (business) and functional (technical) level.
What are the limitations?
The specific application was within the unIT-e2 project; generalizability to all cross-industry projects may vary. The complexity of the methodology itself could be a barrier for some teams.