Experience Report on the Adaptable Integration of Requirements Engineering Courses into Curricula for Professionals

This paper reports on the authors' experience developing three professional software engineering curricula and proposes a systematic, content-mapping-based approach with guiding principles for effectively integrating Requirements Engineering courses into these dynamic and modular programs.

The Gist

Here is an explanation of the paper, translated into everyday language with some creative analogies to make the concepts stick.

🎓 The Big Picture: Fixing the "University vs. Real World" Gap

Imagine you are learning to drive. In a traditional university, you spend months studying the history of the automobile, the physics of combustion engines, and the rules of the road in a classroom. You pass a test, get a license, and graduate.

But then you get into a real car, and suddenly, the steering wheel is on the wrong side, the GPS is broken, and there's a new type of traffic jam you've never seen. That is the problem this paper addresses.

Universities often teach software engineers (the "drivers") in a rigid, theoretical way. But the tech world changes fast. Professionals need to learn how to handle Requirements Engineering (RE)—which is basically the art of figuring out exactly what a customer wants before building it—right now, in a way that fits their messy, fast-paced jobs.

The authors of this paper are like curriculum architects who tried to build a new kind of "driving school" for working professionals. They wanted to figure out how to fit a specific class (Requirements Engineering) into these flexible, adult-focused programs without breaking the whole system.

---

🧩 The Challenge: The "Lego" vs. The "Mold"

Traditional University Curricula are like a pre-made plastic mold. Everything is cast in one piece. You can't change the shape easily. If you want to add a new wheel, you have to melt the whole thing down and start over.

Curricula for Professionals (CfP) are like a giant box of Lego bricks.

• They are modular (you can swap pieces in and out).
• They are dynamic (you can build a castle today and a spaceship tomorrow).
• The instructors (the builders) have a lot of freedom to decide how to use their bricks.

The Problem: The authors wanted to insert a specific, crucial Lego piece (the Requirements Engineering course) into these Lego sets. But because every instructor builds differently, and the "sets" change often, just dropping the piece in didn't work. It didn't fit, or it blocked other pieces.

---

🔍 What They Discovered (The "Aha!" Moments)

The authors looked at three different projects (like three different Lego clubs) and realized that to make this work, you have to change your mindset:

1. Don't Force the Mold: You can't force a professional course to look like a university degree. Professionals need to pick and choose what they need now.
2. The "Bottom-Up" Approach: In traditional schools, the Dean decides the whole plan from the top down. In these professional programs, the plan has to be built bottom-up. You start with the individual courses and see how they connect, rather than forcing them into a pre-made box.
3. Content is King: Forget about complex grading systems or rigid schedules for a moment. The most important thing is the actual content (the Lego bricks themselves). If the bricks fit together, the rest falls into place.
4. Autonomy is Good: Instructors need to feel like they own their courses. If you try to control them too much, they will resist. The goal is to get them to want to connect their course with the Requirements Engineering course.

---

🛠️ The Solution: The "Content Item" Map

So, how did they actually do it? They invented a method they call "Content Item Mapping."

Imagine you are trying to connect three different train tracks (three different courses) so a train can travel smoothly from one to the other.

Step 1: Break it down into "Stops" (Content Items)
Instead of looking at the whole train track as one giant block, they broke every course down into tiny, 10-15 minute "stops" or Content Items (CIs).

• Example: Instead of "The whole Security Course," they made a stop called "What is a Threat?" and another called "How to Model a Threat."

Step 2: The Collaborative Puzzle
The instructors from the different courses sat down (virtually) and laid out all their "stops" on a big table.

• Instructor A (Security): "Hey, I have a stop about 'Threats'."
• Instructor B (Requirements): "Oh, I have a stop about 'Threats' too! Let's put them next to each other so students learn it once, but deeply."
• Instructor C (Quality Assurance): "I have a stop about 'Testing Threats'. That should come after the first two."

Step 3: Build the "Learning Path"
Once they matched the stops, they created a Learning Path. This is like a custom itinerary.

• Instead of saying, "Take Course A, then Course B, then Course C," they said, "Here is a path to becoming an Automotive Systems Engineer. It includes these specific stops from Security, these from Requirements, and these from Quality Assurance."

The Result:
In one project (TASTE), they merged three different courses into a single, smooth journey. It wasn't three separate classes anymore; it was one cohesive story about how to build safe car software.

---

🚀 Why This Matters

This approach is like giving professionals a GPS instead of a static map.

• Old Way: "Here is the map. Follow the lines exactly, even if the road is closed."
• New Way: "Here are the destinations. Here are the road conditions. You can choose the best route, and if a road closes, we can instantly reroute you using the same building blocks."

The Takeaway:
To teach professionals effectively, we shouldn't just dump university lectures on them. We need to:

1. Break knowledge into small, reusable chunks.
2. Let instructors collaborate to see how those chunks fit together.
3. Build flexible "learning paths" that adapt to real-world needs.

By doing this, the "Requirements Engineering" course stops being an afterthought and becomes the glue that holds the whole professional education together.

Technical Summary

Here is a detailed technical summary of the experience report "Adaptable Integration of Requirements Engineering Courses into Curricula for Professionals."

1. Problem Statement

The paper addresses the growing gap between academic Requirements Engineering (RE) education and the practical needs of industry professionals. Key challenges identified include:

• Curriculum Rigidity: Traditional university curricula often prioritize breadth over depth and theoretical knowledge over industry-ready skills. RE courses are frequently treated as an "afterthought" rather than a core component.
• Dynamic Industry Needs: The rapid evolution of the technological landscape requires curricula that are modular, dynamic, and responsive to changing professional demands, which traditional top-down curriculum development struggles to accommodate.
• Lack of Frameworks: There is a scarcity of suitable frameworks to guide the integration of RE courses into Curricula for Professionals (CfP). Existing models often fail to account for the high autonomy of instructors, the loose coupling of modules, and the need for continuous alignment beyond initial development.
• The Specific Gap: Integrating RE into CfP is difficult because RE is inherently uncertain and often interwoven with other Software Engineering (SE) processes, making it hard to isolate and teach effectively within a modular, practice-oriented context.

2. Methodology

The authors employed an Experience Report methodology based on a longitudinal, multi-case study involving three distinct projects where they developed or adapted SE curricula for professionals.

• Case Studies:

  1. PROMIS (Professional Master in Information Security): A master's program at Blekinge Institute of Technology (Sweden) with 15 online courses. The RE course ("Security, Privacy, and Compliance") was developed to align with existing cybersecurity courses.
  2. Software4KMU: A project by fortiss GmbH (Germany) targeting SMEs. An RE course was developed concurrently with a Quality Assurance (QA) course within a single learning roadmap.
  3. TASTE (Transformation Hub Automotive Software Engineering): A collaborative project among five German research institutions. The authors integrated RE, Model-Based Systems Engineering (MBSE), and QA materials into a specific learning path for automotive systems engineers.

• Data Collection & Analysis:

  • Iterative Approach: The authors developed their integration approach iteratively across the three cases.
  • Methods: Included interviews with instructors, focus groups with administrators, observations, and collaborative workshops.
  • Evolution: The approach evolved from initial alignment concepts in PROMIS to a refined, content-item-based strategy in TASTE.
  • Research Questions:
    • RQ1: What characteristics of CfP must be considered for RE integration?
    • RQ2: How can RE courses be effectively integrated into CfP?

3. Key Contributions

The paper proposes two primary contributions: a set of characteristics of CfP relevant to RE integration, and a lightweight, content-item-based approach for integration.

A. Characteristics of Curricula for Professionals (CfP)

The authors identified specific traits of CfP that differ from traditional university curricula and must be addressed during RE integration:

• High Modularity & Loose Coupling: Courses are often independent, requiring a bottom-up alignment strategy rather than top-down planning.
• Practice Orientation: Development is driven by practical needs rather than abstract educational standards, making reference points for RE difficult to define.
• Content Dynamism: Curricula must adapt quickly to new industry trends, leading to faster content obsolescence and a need for continuous updates.
• Instructor Autonomy: Instructors have significant ownership; integration must be collaborative and voluntary rather than administratively mandated.
• Secondary Role of Assessment: Unlike formal degrees, CfP focuses on applicable knowledge; therefore, assessment alignment is less critical than content alignment.
• Partial Alignment: Full curriculum alignment is not always necessary; integrating courses into specific "learning paths" (focused on specific roles/skills) is more viable.

B. The Content-Item-Based Integration Approach

The authors propose a systematic, lightweight approach to integrate RE courses into CfP, centered on Content Items (CIs).

The Process Steps:

1. Identify Related Courses: Analyze existing or planned courses to find those with overlapping learning outcomes or content.
2. Map Content to Items (CIs): Break down course content into small, manageable units (CIs) estimated to take 10–15 minutes to learn.
   • Specification: Each CI is defined by a title and a description of topics/concepts.
   • Tooling: Shared documents or visual tools (e.g., UML class notation in draw.io) are used to create a common understanding.
3. Collaborative Organization:
   • Instructors collaborate to identify intersections in CI titles/topics.
   • CIs are sequenced to create a logical flow. This can be done synchronously (jointly) or asynchronously (individually).
   • Two strategies are offered:
     • Strategy A (Existing Courses): Sequence CIs within each course first, then align them.
     • Strategy B (Concurrent Development): Define CIs for all courses simultaneously and align them together.
4. Define Learning Paths & Modules:
   • Group CIs into Learning Modules (thematic clusters).
   • Arrange modules into Learning Paths (sequences leading to a professional goal).
   • Distinguish between obligatory (core flow) and optional modules.
5. Specify Materials & Outcomes:
   • Attach concrete learning materials (e.g., papers, videos) to CIs to enable reuse across the CfP.
   • Verify or define learning outcomes based on the sequenced CIs.

4. Results

• Successful Integration: The approach was successfully applied in all three cases.
  • In PROMIS, the RE course was taught for three years with positive student feedback. Students appreciated the mapping of relationships between courses.
  • In TASTE, a unified learning path was created combining RE, MBSE, and QA. It consisted of 35 CIs (4 obligatory + 7 optional from RE; 7 obligatory + 6 optional from MBSE; 8 obligatory + 3 optional from QA).
  • In Software4KMU, the project manager validated the modular structure for content management.
• Key Findings on RQ1: The "bottom-up" approach is essential. Attempting to force top-down alignment fails in CfP due to instructor autonomy. Content is the most effective pivot for alignment, more so than learning outcomes or assessments.
• Key Findings on RQ2: The CI-based approach allows for:
  • Contextualization: RE concepts (e.g., threat modeling) can be adjusted to fit specific domains (e.g., automotive or security).
  • Flexibility: The modular nature allows for easy updates when industry practices change.
  • Collaboration: It facilitates asynchronous work among remote instructors.

5. Significance and Future Work

• Bridging the Gap: The study offers a practical solution to the industry-academia gap in RE education by making RE courses more grounded in professional practice and interconnected with other SE disciplines.
• Scalability: The approach is designed to be lightweight and adaptable, making it suitable for various institutions (universities and research institutes) and countries (Sweden and Germany).
• Limitations & Future Directions:
  • The approach requires strong internal commitment and clear incentives for instructors to participate.
  • The applicability to non-RE courses is uncertain, as they may not require such deep contextualization.
  • Future work will focus on structured evaluation of the approach from the perspectives of students, instructors, and industry partners, as well as exploring its application to professional certifications.

In conclusion, the paper argues that integrating RE into professional curricula requires a shift from rigid, top-down planning to a flexible, content-driven, and collaborative model that respects the autonomy of instructors and the dynamic nature of professional practice.