Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Lorentz Center 21th September - Modelling Requirements

40 views

Published on

The use of models for or during requirements engineering (RE) has been suggested to increase productivity and tackle increasing complexity by means of abstraction. Existing modelling frameworks often prescribe a variety of different, formal models for RE, trying to maximise the benefit obtained from model-based engineering (MBE). As an alternative, we have in previous work described how existing requirements, be it textual or in the form of a graphical model, and the connection between these requirements and other artefacts can also be understood as a “requirements model”. We also demonstrated how such a model can be constructed from real-world data in order to support communication and coordination among diverse stakeholders, including software and systems engineers. In this talk, I will discuss this previous work and try to connect it to the workshop theme by motivating a similar approach for data analytics.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Lorentz Center 21th September - Modelling Requirements

  1. 1. Grischa Liebel grischa@chalmers.se (grischa.liebel@gmail.com) Modelling your Requirements for Communication, Coordination (and Analytics)
  2. 2. 9/21/18 Chalmers 2
  3. 3. 9/21/18 Chalmers 3
  4. 4. 9/21/18 Chalmers 4
  5. 5. 9/21/18 Chalmers 5
  6. 6. 9/21/18 Chalmers 6 Agenda • What? • Why? • Connection to the WS?
  7. 7. 9/21/18 Chalmers 7 • Lack of Interdisciplinary Understanding • Insufficient Communication and Feedback Channels • Unclear Responsibilities and Borders (Liebel et al., “Organisation and communication problems in automotive requirements engineering”, Requirements Engineering 23 (1), 145–167, 2018) RE Problems
  8. 8. 9/21/18 Chalmers 8 • Use model-based systems engineering data (traces and person information) to create and visualise coordination networks. “Use the project memory” – Herbsleb Idea Req 1 (Peter) Issue X (Lisa) HW Design (Alice) Issue Y (Alice) Peter Lisa Alice2 1 1 We are not modelling the requirements - we interpret existing requirements as a model!
  9. 9. 9/21/18 Chalmers 9 • Not restricted to Software Engineering • Clarification, no elicitation (i.e., mainly company internal) • People authoring reqs/design have the knowledge “An engineer is trying to find experts for clarification of requirements or design” Main Use Case
  10. 10. 9/21/18 Chalmers 10 • Design science, three cycles • At Volvo Trucks • Mainly with one tool (SystemWeaver) • Proposal for improvements wrt. interoperability, design • 15 interviews, several focus groups, survey • Concerns: • Possible? • Useful? • General? Method • Information management solution • Everything in a single model • Flexible meta model • Entities and relationships
  11. 11. 9/21/18 Chalmers 11
  12. 12. 9/21/18 Chalmers 12 • Yes! • Social data needs to exist and be up-to-date • (Pre-GDPR) Possible? Systems Engineering Models (e.g. Requirements, Design) Social Models
  13. 13. 9/21/18 Chalmers 13 • Practitioners see potential: • For “new” employees • For spotting isolated nodes (people) • For additional use cases (e.g., team composition) • Awareness! • Ethical issues • Blame • Performance evaluation Useful?
  14. 14. 9/21/18 Chalmers 14 • Implemented adapters to the OSLC standard • Tool interoperability for a variety of domains (e.g., requirements mgmt, change mgmt) • Evaluated based on IBM Jazz data and an industrial survey • (Customised version of Gephi) • (Open source on GitHub) Follow-up study General?
  15. 15. 9/21/18 Chalmers 15 • Early communication regarding requirements (vs. development-specific discussions) • Little data (requirements) (vs. lots of data (code, tests)) • Mirror of the actual data (there is value in "wrong" nodes) (vs. abstraction) • Multi-disciplinary approach (vs. single-discipline tool) Why?
  16. 16. 9/21/18 Chalmers 16 Connection to the Workshop? • ”Big Software” • Lots of stakeholders • Across organisations • Across interfaces/systems • Statistical methods, AI, ML, etc., are needed to handle large amounts of data • But: How about models on a high level of abstraction? • Requirements level • Interfaces between organisations • Inform human decisions
  17. 17. 9/21/18 Chalmers 17 Req 1 (Peter) Issue X (Lisa) HW Design (Alice) Issue Y (Alice) Peter Lisa Alice2 1 1 - Useful for several use cases - Data quality is an issue - Potential ethical issues Collaboration? grischa.liebel@gmail.com

×