For a decade, I’ve utilized a method in the requirement phase to uncover hidden requirements and tackle ambiguities, guided by SEI CMU’s insights ( https://lnkd.in/gc4-crSW ) on quality attribute refinement and allocation. 📊

In scenario refinement, we analyze:

1. 𝐒𝐭𝐢𝐦𝐮𝐥𝐮𝐬 𝐒𝐨𝐮𝐫𝐜𝐞: Front collision detected by the vehicle’s system 🚗
2. 𝐒𝐭𝐢𝐦𝐮𝐥𝐮𝐬: Event sent to ECU by the collision detection system 💻
3. 𝐄𝐧𝐯𝐢𝐫𝐨𝐧𝐦𝐞𝐧𝐭: Operational ECU with functioning sensors 🌐
4. 𝐀𝐫𝐭𝐢𝐟𝐚𝐜𝐭𝐬: Details of sensors like collision detection, seatbelt status, and speedometer ⚙️
5. 𝐑𝐞𝐬𝐩𝐨𝐧𝐬𝐞: ECU processes the event and checks preconditions ✔️
6. 𝐑𝐞𝐬𝐩𝐨𝐧𝐬𝐞 𝐌𝐞𝐚𝐬𝐮𝐫𝐞: Airbag deployment system activates within 30 milliseconds ⏱️

By consistently refining scenarios, we can capture effective requirements, addressing functional and non-functional aspects for a robust system design. 🛠️

What methods do you find most effective for handling software requirements? 🤔

I would love to hear about your most favored and highly effective method for handling software requirements. Your expertise and insights in this area would be greatly appreciated!

Happy learning! 📚

By

N ASHOK KUMAR (ak@faradsystems.com)