Requirements Engineering lernen! 🎓 IREB® Certified Professional for Requirements Engineering – Foundation Level 🧑‍💻 seppmed.de/akademie/seminare… Das Training vermittelt die Grundlagen zum Umgang mit Anforderungen in Softwareentwicklungsprojekten. #requirementsengineering #seminar

📢 Newly published research in #mdpisystems 👉mdpi.com/2079-8954/14/4/364 Measuring #Complexity at the Requirements Stage: Spectral Metrics as Development Effort Predictors by authors from @FollowStevens and @ASU #SystemsEngineering #RequirementsEngineering #QuantitativeMetrics

#SoftwareEngineering #SoftwareApplications #SoftwareDevelopment #SoftwareArchitecture #SoftwareDesign #SoftwareTesting #SoftwareQualityAssurance #RequirementsEngineering #AgileSoftwareDevelopment #DevOps #ContinuousIntegration #ContinuousDelivery #SoftwareMaintenance

I published a new article about a question that looks simple, but is often surprisingly hard in real projects: Is this a bug or an enhancement? In the AI Unified Process, the answer is not based on which artifacts we touch. A bug may require changes to the spec, tests, and code. An enhancement may require the same. The real distinction is intent. A bug corrects a mistake. The mistake can be in the code, in the specification, or even in the test. An enhancement changes direction. The old specification was correct for the old intent, but the business now wants something different. This distinction matters because the numbers tell you where your process is leaking. Code bugs may point to gaps in the harness. Specification bugs may point to weak requirements work. Test bugs may point to problems in your testing strategy. Without traceability, bug and enhancement are just labels. With traceability, they become feedback for improving how you work. Article: martinelli.ch/bug-or-enhance… #SpecDrivenDevelopment #AIUnifiedProcess #AIUP #SoftwareEngineering #RequirementsEngineering

New article: Use-Case 2.0: The Forgotten Practice That Solves What User Stories Can’t Many teams rely almost entirely on user stories. But user stories often lose context once the backlog grows. In this article, I explain why Use-Case 2.0 still matters, especially today: it gives the big picture it connects related behavior under one goal it brings test cases in early and it fits surprisingly well with AI-assisted development That is also why Use-Case 2.0 is such a strong foundation for the AI Unified Process: clear specifications, structured flows, and tests that protect behavior. () If you feel that user stories alone are not enough, this might resonate with you. martinelli.ch/use-case-2-0-t… #SoftwareArchitecture #RequirementsEngineering #SpecDrivenDevelopment #AI #AIUP #UseCases #UseCase20

AI-assisted development is changing how software is built. But many teams misunderstand what “spec-driven” actually means. In my latest article I compare BMAD and Spec-Driven Development and explain why AI systems need something more fundamental than task lists or prompts: clear specifications of system behavior. AI can generate code quickly. But without precise specifications, it will simply generate incorrect behavior faster. Real specifications describe intent, domain concepts, and system behavior. They create artifacts that remain understandable for developers, stakeholders, and future teams — and they provide a stable foundation for AI-assisted implementation. In the article I explore: • why task-driven workflows are not the same as specifications • how many “spec-driven” approaches are actually task scripting • why durable specifications are essential for sustainable AI development If AI is the engine, specifications are the steering wheel. martinelli.ch/bmad-vs-spec-d… #AI #SoftwareEngineering #SpecDrivenDevelopment #RequirementsEngineering #AIUP

A central part of the discussions focused on the MoD feedback from the December workshop. Their operational insights were crucial to refining system requirements and aligning key capabilities. #RequirementsEngineering #OperationalNeeds #MoD

AI is changing software development faster than most teams realize. Writing code is no longer the hard part. AI makes coding cheap. The real challenge now is something very different: 👉 defining what should be built 👉 expressing it clearly enough so AI can execute it correctly In other words, requirements have become the bottleneck. If your inputs are vague, you don’t get better software faster you just get wrong software faster. This shift changes the role of developers and architects: less typing, more thinking less implementation, more clarity less guessing, more specification In my latest article, I explain why this is happening and what it means for modern development: 👉 martinelli.ch/ai-makes-codin… If you work with AI in software development, this is a shift you cannot ignore. #AI #SoftwareDevelopment #RequirementsEngineering #SpecDrivenDevelopment #AIUnifiedProcess

🚀 Use Cases vs User Stories — same content, different outcome Many teams believe the difference between user stories and use cases is just formatting. It’s not. In reality, they organize requirements for completely different purposes: User stories help you plan work. Use cases describe system behavior. That difference changes everything. 👉 User stories are short and flexible, but often too vague for implementation. 👉 Use cases go deeper with flows, actors, and edge cases, making them usable as real specifications. In my latest article, I explain why this leads to completely different outcomes in development, especially with AI. If you care about clarity, traceability, and building systems instead of just managing tasks, this is for you. 👉 Read more: martinelli.ch/use-cases-vs-u… #softwarearchitecture #requirementsengineering #ai #specdrivendevelopment #java #agile

📣 New on the blog: The Age of ReDevTest — Why Requirements Matter More Than Code 🧠 AI is reshaping how we build software. Gone are the days when code was the centre of our world. In the age of ReDevTest, the real value lies in clear requirements, precise system use cases, and solid acceptance tests — not in the code itself. In this article I explain how today’s development loop puts intent before implementation, letting AI generate code, tests, and behaviour from well-defined specifications. If requirements are fuzzy, AI output will be too. Real productivity now comes from how fast you go from intent to correct behaviour. 👉 Read the full piece and rethink your workflow: martinelli.ch/the-age-of-red… #ReDevTest #SoftwareDevelopment #AI #RequirementsEngineering #Productivity

New blog post ✍️ AI can generate code fast. But AI cannot guess intent. In my latest blog post, I explain why system use cases are perfect in the age of AI. I cover: • where system use cases come from • what makes a system use case executable • a good example and a bad example • why vague specs break AI-assisted development 👉 Read the blog post: martinelli.ch/why-system-use… #SoftwareArchitecture #AIinSoftware #RequirementsEngineering #SystemUseCases #SpecDrivenDevelopment

New on the blog: AI4RE Meets AIUP: Why the IREB Micro-Credential Fits Perfectly 🚀 Artificial intelligence is everywhere, but how do we use it responsibly in software development? In my latest article, I explain how the new AI4RE micro-credential from IREB (International Requirements Engineering Board) complements the AI Unified Process (AIUP). It’s not just about getting a badge — it’s about building the right mindset for using AI in requirements engineering and tying that into a process where clear specifications drive the whole development lifecycle. You’ll learn: What AI4RE really teaches about AI in RE How AIUP keeps requirements and specifications at the center Why the two together make teams more effective with AI 👉 Read the full post: martinelli.ch/ai4re-meets-ai… #AI4RE #IREB #AIUP #RequirementsEngineering #SoftwareDevelopment

Many AI tools today focus on the developer and code generation. That is useful. But development involves more roles than just engineers. Requirements engineers, testers, product owners, and other stakeholders also play a key part in success. That is why I built the AI Unified Process (AIUP) aiup.dev. It supports the entire development cycle, not just code. It helps teams work together, reduce waste, and improve quality from requirements to delivery. With the AI Unified Process you can: - Capture clear and testable requirements - Keep product owners and stakeholders aligned- - Generate and validate tests early - Create traceability across all work - Enable a shared understanding across roles AI should help the whole team, not only one role. AIUP is designed for collaboration across the full lifecycle. Learn more at aiup.dev and join the conversation on how AI can truly unify product and engineering teams. #AI #SoftwareDevelopment #ProductManagement #Testing #RequirementsEngineering #AIUP #KeepITsimple

📬 Today’s the day! REFSQ 2026 author notifications are being sent out today. A big thank you to all authors for your submissions — and congratulations in advance to those accepted! #REFSQ2026 #RequirementsEngineering #ResearchCommunity

🧪Great BSAs test assumptions before systems. Don’t let requirements go unchecked. #RequirementsEngineering @IIBA @IIBAToronto @credly #MDMarketInsights #BusinessAnalysis #CapitalMarkets #FinancialServices #TradeFloor #FinanceIndustry #InvestmentAnalysis #DataAnalytics #RiskManagement #TradingStrategies #MarketResearch #FinancialData #InvestmentManagement #AssetManagement #Fintech #RegulatoryCompliance #PortfolioManagement #Derivatives #MarketAnalysis #FinancialTechnology #TradingTools #QuantitativeAnalysis #InvestmentStrategy #BusinessIntelligence #FinancialInnovation #EconomicAnalysis #TradingSystems #DataScience #HedgeFunds #PrivateEquity #RiskAnalysis

🎥Missed Birgit Penzenstadler’s insightful keynote at #REFSQ2025? No worries — the recording is now available on YouTube!✨ Don’t miss this deep dive into sustainability in requirements engineering. 📺Watch now: youtu.be/p6kwQbKR2Mw?si=qCZh… #Sustainability #RequirementsEngineering

📢 The #REFSQ2025 proceedings are out! Explore the latest in Requirements Engineering, now available on SpringerLink. 🔗 2025.refsq.org/ 📅 Free access for registered participants until May 15, 2025. #RequirementsEngineering #SoftwareQuality #SpringerLink

#REFSQ2025 spotlights! Don't miss our industry talks: 📢 How do we tackle real-world RE challenges in healthcare applications? 📢 ¿Cómo enfrentamos los desafíos reales de Ingeniería de Requisitos en aplicaciones de salud? #HealthcareTech #RequirementsEngineering #digitalhealth

Spotlights: Yiannis Kanellopoulos​-Industry Keynote 📢 As AI evolves, how does Requirements Engineering keep up? 📢 A medida que la IA evoluciona, ¿cómo se adapta la Ingeniería de Requisitos? #REFSQ2025 #AI #RequirementsEngineering #ResponsibleAI

💫Meet our #SyMeCoCOFUND fellow Jacek Dąbrowski @LeroCentre @UL_Research. Learn more about Jacek’s @Researchirel @HorizonEU @MSCActions funded #AI #RequirementsEngineering project➡️prompt-me.lero.ie. Check out➡️symeco.lero.ie for info on SyMeCo fellowships.