Submit a knowledge article

As well as choosing a topic, you will need to choose an angle for your resource.

For knowledge articles. contributors might consider one of the following:

• What it is: explaining the topic and its relation to complex systems.
• Why educators should teach it / students should learn it.
• Why it should be integrated into engineering education.
• An angle of your own choosing.

These articles should connect the why (why must teaching about the topic be present in engineering education?) to the how (how can this be done efficiently and effectively?). Through these tools, we aim to help upskill UK engineering educators so that they feel capable of and confident in integrating complex systems concepts and intelligent robotics topics into their engineering teaching.

 

Step 1: Read the guidance for submitting a knowledge article

Research:

Knowledge articles are resources that users can access to improve their knowledge or find more information. These are intended to provide theoretical and practical background on complex systems concepts and tools such as modelling or decision-making approaches. While guidance articles focus on “how”, knowledge articles focus on “what”.

Before you begin, you should review existing Complex Systems Toolkit knowledge articles, since we hope that contributions will be fairly consistent in length, style, and tone.

Knowledge articles are meant to be overviews that a reader with no prior knowledge of the topic could refer to in order to develop a baseline understanding and learn where to look for additional information (they can reference other sources). They should be understandable to students as well: imagine that an educator might excerpt content from the article to provide their students context on a project or learning activity.

They should be approximately 500-1000 words (although they can be more in depth if necessary) and reference relevant online open-source resources.

Overview:

The articles are meant to be able to stand on their own as a piece of knowledge on a topic; they are also meant to work alongside other articles so that taken together they form a sort of complex systems in engineering handbook.

Purpose:

Each article should inform, explain, and provide knowledge on the topic. Put yourself in the perspective of an engineering educator who is new to the topic.

Content:

The content of the article should be organised and well developed. That is, it should be presented in a logical way and thoroughly explained.

References and resources:

Where additional explanation could be given, it might point to other resources, and where information is presented from another source, it needs to be properly referenced using Harvard referencing.

Format:

Knowledge articles should follow this format:

• Premise;
• Body of article, divided up into headed sections as necessary;
• Conclusion (optional);
• References: use Harvard referencing;
• Resources (online and open source).

 

Step 2: Before you submit, review this checklist

• Does the article both make sense as a single piece of content as well as fit in with the rest of the knowledge articles?
• Would someone new to this complex systems topic understand the information presented and would it help them?
• Do you need to expand on any ideas or reorganise them to make them clearer?
• What additional resources or references have you included?
• Are open resources or links to other toolkit materials included?
• Are sources cited using Harvard referencing?

 

Step 3: Submitting your knowledge article:

Knowledge articles should be submitted in Word file format (.doc or .docx).

Also submit any additional resources such as spreadsheets, handouts etc., and ensure that they are in an editable format. Please clarify where in the resource these should be embedded or linked.

Any corresponding images should be submitted in either .jpeg, .jpg or .png format. We need these to be uploaded separately from the Word file, as we will be embedding them in a web page. Please ensure that they are of high resolution and adequate size (we suggest a minimum of 800 pixels wide); that you have the right or permission to use them (bearing in mind they will be published under a Creative Commons license); and that you have added any permissions, sources, credits or other details for them in the body of the document that you are submitting.

To ensure that everyone can use and adapt the Toolkit resources in a way that best fits their teaching or purpose, this work will be licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. Under this licence users are free to share and adapt this material, under terms that they must give appropriate credit and attribution to the original material and indicate if any changes are made.

Download a copy of this guidance

Submit your knowledge article here

Submit a guidance article

As well as choosing a topic, you will need to choose an angle for your resource.

For guidance articles, contributors might consider one of the following:

• Guide to explaining the topic to students.
• How to assess for skills / competencies on this topic.
  • This could include:
    • Assessment Criteria
    • Example Rubrics
    • Reference to INCOSE Competencies
    • Reference to AHEP 4
• An angle of your own choosing.

These articles should also connect the why (why must teaching about this topic be present in engineering education?) to the how (how can this be done efficiently and effectively?). Through these tools, we aim to help upskill UK engineering educators so that they feel capable of and confident in integrating complex systems concepts and intelligent robotics topics into their engineering teaching.

 

Step 1: Read the guidance for submitting a guidance article

Research:

Guidance articles are resources that users can access to learn how to do something. These are intended to provide practical advice on subjects such as how to explain complex systems to students, or how to assess for skills and competencies in complex systems. While knowledge articles focus on “what”, guidance articles should focus on “how.”

Before you begin, you should review existing Complex Systems Toolkit guidance articles, since we hope that contributions will be fairly consistent in length, style, and tone.

Guidance articles aim to help situate our teaching resources in an educational context and to signpost to additional research and resources on complex systems theory and tools.

They should be approximately 500-1000 words (although they can be more in depth if necessary) and reference relevant online open-source resources.

Overview:

Guidance articles are meant to be able to stand on their own as a piece of guidance on a topic; they are also meant to work alongside other articles so that taken together they form a sort of complex systems in engineering handbook.

Purpose:

Each article should inform, explain, and provide guidance on the topic. Put yourself in the perspective of an engineering educator who is new to the topic.

Content:

The content of the article should be organised and well developed. That is, it should be presented in a logical way and thoroughly explained.

References and resources:

Where additional explanation could be given, it might point to other resources, and where information is presented from another source, it needs to be properly referenced using Harvard referencing.

Format:

Guidance articles should follow this format:

• Premise;
• Body of article, divided up into headed sections as necessary;
• Conclusion (optional);
• References: use Harvard referencing;
• Resources (online and open source).

 

Step 2: Before you submit, review this checklist

• Does the article both make sense as a single piece of content as well as fit in with the rest of the guidance articles?
• Would someone new to this complex systems topic understand the information presented and would it help them?
• Is the explanation clear, logically structured and technically accurate?
• Do you need to expand on any ideas or reorganise them to make them clearer?
• What additional resources or references have you included?
• Are open resources or links to other toolkit materials included?
• Are sources cited using Harvard referencing?

 

Step 3: Submitting your guidance article

Guidance articles should be submitted in Word file format (.doc or .docx).

Also submit any additional resources such as spreadsheets, handouts etc., and ensure that they are in an editable format. Please clarify where in the resource these should be embedded or linked.

Any corresponding images should be submitted in either .jpeg, .jpg or .png format. We need these to be uploaded separately from the Word file, as we will be embedding them in a web page. Please ensure that they are of high resolution and adequate size (we suggest a minimum of 800 pixels wide); that you have the right or permission to use them (bearing in mind they will be published under a Creative Commons license); and that you have added any permissions, sources, credits or other details for them in the body of the document that you are submitting.

To ensure that everyone can use and adapt the Toolkit resources in a way that best fits their teaching or purpose, this work will be licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. Under this licence users are free to share and adapt this material, under terms that they must give appropriate credit and attribution to the original material and indicate if any changes are made.

Download a copy of this guidance

Submit your guidance article here.

 

Submit a teaching activity/resource

As well as choosing a topic, you will need to choose an angle for your resource.

For activities, contributors might consider one of the following:

• Case studies that, through a real-world situation, illustrate the topic and its relation to complex systems, use cases for the tools that can be used to model / simulate this, techniques that promote development and use of systems architecture, and effects such as trade-offs, emergent properties, impacts, or unintended consequences. Case studies could also reference the implications for risk, security, ethics, sustainability, teamwork, and communication.
• Demonstrator simulations that provide examples of how systems can be modelled.
  • This could include:
    • Examples of how the topic relates complex systems
    • Interactive examples showing how well-intentioned action can lead to failure
    • Interactive examples showing the best approaches to handling complexity
• Teaching/learning activities, coursework, project briefs, lesson plans, modelling or simulation exercise/activities, technical content related to complex systems, worksheets, slides, robotics labs, swarm behaviour activities, system mapping exercises, hardware-in-the-loop demonstrations, digital twin exercises, or other teaching materials.
• An angle of your own choosing.

These resources should promote active learning pedagogies and real-world teaching methods by showing how complex systems teaching can be embedded within technical problems and engineering practice. Through these resources, we aim to help upskill UK engineering educators so that they feel capable of and confident in integrating complex systems into their engineering teaching.

 

Step 1: Read the guidance for submitting a teaching activity/resource

Research:

Teaching activities are resources that users can access to help them know what to integrate and implement. These include use cases/case studies which provide examples of complex systems topics which can be directly utilised in teaching with the suggested tools, as well as other classroom activities such as coursework, project briefs, lesson plans, simulation exercises, robotics labs, swarm behaviour activities, system mapping exercises, hardware-in-the-loop demonstrations, digital twin exercises, or other exercises.

Before you begin, you should review existing Complex Systems Toolkit teaching resources, since we hope that contributions will be fairly consistent in length, style, tone, format and approach. Remember that the audience for these resources is educators seeking to embed complex systems topics within their engineering teaching.

 

Step 1a: Guidance for submitting a case study

Case studies present real-world scenarios that can be used in teaching about complex systems topics in engineering. They provide students with opportunities to explore complex systems tools, and trade-offs, in authentic contexts, and reflect on decisions made about them.

They are usually based on a real example, although fictionalised cases are acceptable when they are grounded in realistic detail. Case studies should enable students to identify or interpret key features of complex systems topics (feedback loops, interdependence or emergent behaviour) and apply relevant tools or frameworks to make sense of the situation.

Case studies will vary in length depending on scope and resource, but many are around 1500-2000 words. They should reference relevant online open-source resources.

Please see the current research on good practice in writing case studies, which you may find helpful as you write, as well as our article about a recipe for writing a case study. This ‘recipe’ can guide you as you write to include or develop other aspects of the case. Both articles are from our Engineering Ethics Toolkit, but the guidance given can be adapted for complex systems cases.

Overview:

The case study should be presented as a narrative about a complex systems issue in engineering.

Narrative strength: the case should be clearly structured with a compelling and coherent story.

System complexity: it should explore interdependencies, multiple stakeholders and/or competing goals.

Tool integration: systems tools should be mentioned or incorporated (e.g. soft systems methodology, SysML, Agent-based modelling etc).

Activities and Resources: there should be questions, prompts or teaching activities to guide discussion or classroom use.

Authenticity:

Case studies are most effective when they feel like they are realistic, with characters that you can identify or empathise with, and with situations that do not feel fake or staged. Giving characters names and backgrounds, including emotional responses, and referencing real-life experiences help to increase authenticity.

Complexity of issue:

Many cases are either overly complicated so that they become overwhelming, or so straightforward that they can be “solved” quickly. A good strategy is to try to develop multiple dimensions of a case, but not too many that it becomes unwieldy. Additionally, complexity can be added through different parts of the case so that instructors can choose a simpler or more complicated version depending on what they need in their educational context.

Activities and resources:

You should provide a variety of suggestions for discussion points and activities to engage learners, as well as a list of reliable, authoritative open-source online resources, to both help educators prepare and to enhance students’ learning. Where information is presented from another source, it needs to be properly referenced using Harvard referencing.

Educational level and assessment:

Educational level: When writing your case study, you should consider which level it is aimed at. A Beginner level case is aimed at learners who have not had much experience in engaging with this complex systems topic or problem, and usually focuses on only one or two dimensions of a challenge. An Advanced-level case is aimed at learners who have had previous practice in engaging with this complex systems topic or problem, and often addresses multiple challenges. An Intermediate case is somewhere in between.

Assessment: If possible, suggest assessment opportunities for activities within the case, such as marking rubrics or example answers.

Format:

The case study should follow the following format:

• Teaching notes (with learning objectives, time needed, materials): This is an overview of the case and its dilemma, and how it relates to AHEP4 and INCOSE competencies.
• Learning and teaching resources: A list of reliable, authoritative, open-source online resources that relate to the case and its dilemma. These can be from a variety of sources, such as academic institutions, journals, news websites, business, and so on. We suggest a minimum of five sources that help to provide context to the case and its dilemmas.
• Summary of system or context.
• Narrative of the case (presenting the complexity).
• Questions and activities. This is where you provide suggestions for discussions and activities related to the case and the dilemma.
• Further discussion or challenge (optional). Some case studies are sufficiently complex at one dilemma, but if the case requires it you can provide further parts (up to a maximum of three).
• References: use Harvard referencing.
• If possible, suggest assessment opportunities for activities within the case, such as marking rubrics or example answers.
• Keywords: On the submission form you will be prompted to provide keywords, including educational aims, issues and situations highlighted in the case.

 

Step 2a: Before you submit, review this checklist:

• Does it follow the correct format?
• Narrative strength: is the case clearly structured with a compelling and coherent story?
• System complexity: does it explore interdependencies, multiple stakeholders and/or competing goals?
• Tool integration: are systems tools mentioned or incorporated (e.g. soft systems methodology, SysML, Agent-based modelling etc)?
• Activities and resources: are there questions, prompts or teaching activities to guide discussion or classroom use?
• Are open resources or links to other toolkit materials included?
• Are sources cited using Harvard referencing?
• What additional references have you included?

 

Step 1b: Read the guidance for submitting a different teaching activity

 Purpose & outcomes:

Teaching activities/tools are intended to support educators’ ability to apply and embed complex systems concepts and topics within their engineering teaching.

Educators need to quickly and easily find help with:

• Adapting and integrating existing complex systems resources to their disciplinary context.
• Implementing new and different pedagogies that support complex systems learning.
• Structuring lessons, modules, and programmes so that complex systems skills and outcomes are central themes.

Thus, these teaching activities/tools will provide crucial guidance for those who may be teaching complex systems related material for the first time, or who are looking for new and different ways to integrate complex systems concepts or topics into their teaching.

Teaching activities/tools may take the form of learning activities, coursework, project briefs, lesson plans, modelling or simulation exercise/activities, technical content related to complex systems, worksheets, slides, robotics labs, swarm behaviour activities, system mapping exercises, hardware-in-the-loop demonstrations, digital twin exercises, or other similar teaching materials.

Research:

Before you begin to write, you should familiarise yourself with existing Complex Systems Toolkit teaching resources, as well as content that has been created to complement case studies in our Ethics Toolkit and teaching tools in our Sustainability Toolkit, since we want these resources to be produced in a similar style and format.

Purpose:

Imagine that you are an engineering educator who is new to teaching complex systems concepts or topics. You turn to this teaching tool to help you apply and embed these in your module.

• Does this resource help introduce or develop concepts related to complex systems or systems thinking so that learners can engage with these topics in the context of engineering?
• If not, what is needed to make this possible?

Presentation and clarity:

Depending on the resource, you may choose to provide worksheets, slides, problem sets, narrative prompts, etc.

• Is the resource explained in such a way that someone new to teaching complex systems could understand how to use it?
• Is the material clearly introduced and described?

Resources and guidance:

Depending on the topic, educators may need additional resources or guidance to support their use of the material. For instance, background information may be required or a technical topic explained.

• Have you provided sufficient material so that educators can easily employ the resource?
• Do references use Harvard referencing?

Format:

The teaching activity/tool should follow this format:

• Overview:
  • Short description of what the resource is and what it aims to do.
  • States how it is related to complex systems or systems thinking topic(s), referring to external content such as INCOSE Competencies and AHEP 4.
  • Provides an overview of the activity, suggesting how it might be implemented and in what contexts, how long it might take, and any other relevant delivery information.
• Details any specific materials or software required for the activity, as well as any modelling or simulation tools to be used.
• Lists any learning and teaching resources recommended in order to undertake the activity, including suggested pre-reading or other references.
• Explains the activity in as much detail as is required (this will vary depending on the type of material the resource addresses.)
• If relevant, provides assessment guidance–marking rubrics, sample answers, etc.

 

Step 2b: Before you submit, review this checklist:

• Does this resource help introduce or develop concepts/topics related to complex systems or systems thinking so that learners can engage with these topics in the context of engineering?
• Is the resource explained in such a way that someone new to teaching complex systems could understand how to use it?
• Is the material clearly introduced and described?
• Have you provided sufficient material so that educators can easily employ the resource?
• Do references use Harvard referencing?
• Does it follow the correct format?

 

Step 3: Submitting your teaching activity/resource

 Teaching resources should be submitted in Word file format (.doc or .docx).

Also submit any additional resources such as spreadsheets, handouts etc., and ensure that they are in an editable format. Please clarify where in the resource these should be embedded or linked.

Any corresponding images should be submitted in either .jpeg, .jpg or .png format. We need these to be uploaded separately from the Word file, as we will be embedding them in a web page. Please ensure that they are of high resolution and adequate size (we suggest a minimum of 800 pixels wide); that you have the right or permission to use them (bearing in mind they will be published under a Creative Commons license); and that you have added any permissions, sources, credits or other details for them in the body of the document that you are submitting.

To ensure that everyone can use and adapt the Toolkit resources in a way that best fits their teaching or purpose, this work will be licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. Under this licence users are free to share and adapt this material, under terms that they must give appropriate credit and attribution to the original material and indicate if any changes are made.

Download a copy of this guidance

Submit your teaching resource here