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.

Goal-oriented modeling and traceability recovery for IoT Ecosystems

797 views

Published on

Hironori Washizaki, Goal-oriented modeling and traceability recovery for IoT Ecosystems, NII Shonan Meeting SENCPS, Aug 23, 2017, Shonan Village

Published in: Software
  • Be the first to comment

  • Be the first to like this

Goal-oriented modeling and traceability recovery for IoT Ecosystems

  1. 1. Goal-oriented modeling and traceability recovery for IoT Ecosystems Hironori Washizaki Waseda University / National Institute of Informatics / SYSTEM INFORMATION Twitter: @Hiro_Washi washizaki@waseda.jp http://www.washi.cs.waseda.ac.jp/ 2017 Aug 23 NII Shonan Meeting SENCPS
  2. 2. • Prof., Director, Global Software Engineering Laboratory, Waseda University • Visiting Prof., National Institute of Informatics • ISO/IEC/JTC1 SC7/WG20 Convenor • IEEE CS Japan Chapter Vice-Chair • IEEE CS Membership at Large of PEAB • IEEE ICST 2017 PC Chair • IEEE CSEE&T 2017 PC Chair • APSEC 2018 PC Chair (Nara) • IEEE COMPSAC 2018 Local Chair (Tokyo) 2 Hironori Washizaki
  3. 3. Why is traceability from goals/requirements to implementation through design important? • Key to ensure consistency among artifacts [Antoniol‘00] • E.g., case of embedded software design – Good design and poor coding in terms of maintainability 3 走破戦略 コース 終了条件 ロギング 難所攻略 走法 キャリブ レーション デバイス 外部環境UI 走破戦略 コース 終了条件 ロギング 難所攻略 走法 キャリブ レーション デバイス 外部環境UI Design ≠ “Design” recovered from code Course [Antoniol’00] G. Antoniol, B. Caprile, A. Potrich and P. Tonella, "Design-Code Traceability for Object-Oriented Systems," Annals of Software Engineering, vol. 9, no. 1-4, pp. 35-58, 2000 Condition Strategy Running Calibration Device Logging Strategy package Environ ment Course Condition Strategy Running Calibration Device Logging Strategy package Environ ment balancer->operate(0,m_direction);
  4. 4. Cross-Industry IoT Ecosystems 4 Health Sensor Maker Parts Maker A …… Parts Maker A1 Parts Maker A2 …… Conventional structure Industry structure in IoT era Health Sensor Maker Insur ance Medical Info. Provider Sensor Maker Hospita l Transpo rtation Transportation Traffic expansion Hospital Remote safety A. Modeling and alignment Traffic expansion Remote safetyReliable Low cost movement Medical support NaviElderly Health condition data streaming() { …. } int monitor() { …. } void request() { …. } A. Trace Specific dataSpecific data Aligned and comprehensi ve data Living alone comfortably Living alone comfortably Commu nication
  5. 5. Promotion to hospitals Promotion to insurance companies 5 GQM+Strategies and IoT/Data • Alignment and tracing among goal, strategy and data • How about complex IoT ecosystems? Number of customers of medical info. is increased... Strategy Strategy Insurance company can offer personalized products by having medical info… Hospital can provide appropriate service by having medical info… C / A Goal Strategy C / A G S A S Strategy G S A High-level department Low- level depar tment Measuremen M M Trace …… …… …… …… …… …… …… …… …… …… …… …… …… …… …… …… …… …… Goal Context / AssumptionContext / Assumption Measurement #Customers of medical info.
  6. 6. Context-Assumption-Matrix [IEICE’16] 6 Takanobu Kobori, Hironori Washizaki, et al., “Exhaustive and efficient identification of rationales using GQM+Strategies with stakeholder relationship analysis,” IEICE Transactions on Information and Systems, Vol.E99-D, No.9, pp.2219-2228, 2016. Target View Hospital Insurance company Health sensor maker ・・・ Hospital Insurance company Health sensor maker ・・・ Insurance company can offer personalized products by having medical info… Context / Assumption Insurance company Medical info provider Personal medical info. Customized product Resource Goal depends
  7. 7. 7 Insurance company G S A S Health sensor maker Medical info. provider Expectation from the view of insurance company Expectation from the view of health sensor maker Receive medical info. Personalized products developed Strategy Insurance product and fee can be personalized based on personal medical info. Goal Context / Assumption Sales of new products Personal fitness Confirm personal info. Management system of receiver of info. Secure management of medical info. Strategy Must ensure personal info. guideline Goal Context / Assumption Insurance company Medical info. provider Confirming management systems Pati ent Getting consent Conflict, redundancy, complement Conflict, redundancy, complement
  8. 8. 8 Towards clear dependency and alignment G S A S Insurance company Medical info. provider Personal medical info. Realizing personalized insurance Objective of medical info. use Managing personal info. Clarify objective of use of medical info. Strategy Establish personal info. management system Strategy Medical info. provider Secure management of medical info. Strategy Must ensure personal info. guideline Goal Context / Assumption Health sensor maker Insurance company Receive medical info. Personalized products developed Strategy Goal Context / Assumption Sales of new products Personal fitness Insurance product and fee can be personalized based on personal medical info.
  9. 9. S1 S2 S3 S5 S6 S4 S7 S1 S2 S3 S4 S6 S5 S7 Interpretive Structural Modeling (ISM) 9 Impact S1 S2 S3 S4 S5 S6 S7 S1 1 0 0 0 0 0 0 S2 0 1 0 0 0 0 0 S3 1 1* 1 0 1 0 0 S4 1 1* 0 1 0 0 1 S5 1* 1 1 0 1 0 0 S6 1* 1 0 1 0 1 1* S7 1* 1 0 1 0 0 1 Power. Hierarchical structuring 可到達行列 S1 S2 S3 S4 S5 S6 S7 S1 1 0 0 0 0 0 0 S2 1 1 0 0 0 0 0 S3 1 0 1 0 1 0 0 S4 1 0 0 1 0 0 1 S5 0 1 1 0 1 0 0 S6 0 1 0 1 0 1 0 S7 0 1 0 1 0 0 1 Relation matrix Reachability matrix
  10. 10. ISM-based Alignment [HICSS’16] S1 S2 S3 S4 ・ ・ S1 S2 S3 S4 ・・ 1 1 (1) Decompose into elements (2)Restru cturing (3)Analysis& alignment S5 S1 S2 S3 S4 S6 S7 Hierarchical structure S5 S1 S2 S3 S4 S6 S7 ISM 1 Elements (especially strategies) 1 1 1 1 S5 S1 S2 S3 S4 S6 S7 GQM+Strategies G GG G Reachability matrix Conflict specified • Alignment for single GQM+Strategies model • Future: alignment over areas and stakeholders Yohei Aoki, Takanobu Kobori, Hironori Washizaki, et al., “Identifying Misalignment of Goals and Strategies across Organizational Units by Interpretive Structural Modeling,” 49th Hawaii International Conference on System Sciences (HICSS), 2016
  11. 11. Cross-cuttingness and evolvability in IoT A: Misalignment in goals and strategies ⇒ Top-down modeling and alignment B: Poor traceability due to cross-cutting realization and evolution ⇒ Bottom-up traceability link recovery 11 A. Alignment and tracing B. Traceability link recovery Driving Traffic Connection GUI Safety Mgmt Health Control data streaming() { …. } int monitor() { …. } void request() { …. } Requirement Architecture design Detail design SourceGoal/Value TransportMedical Supply Environme nt change Environme nt change 11 data streaming() { …. } void request() { …. }EvolutionEvolution Traffic expansion Remote safetyReliable Low cost movement Living alone comfortably Medical support Elderly Health condition Commu nication Navi.
  12. 12. Robust Traceability Recovery [CAiSE 2015][ICSME 2015] 12 R. Tsuchiya, H. Washizaki, et al.,“Interactive Recovery of Requirements Traceability Links Using User Feedback and Configuration Management Logs,” 27th International Conference on Advanced Information Systems Engineering (CAiSE 2015) K. Nishikawa, H. Washizaki, Y. Fukazawa, K. Ohshima, R. Mibe, “Recovering Transitive Traceability Links among Software Artifacts,” 31st IEEE International Conference on Software Maintenance and Evolution (ICSME 2015) Revision: 139 Author: anilsaharan Date: 2011/8/20 22:17:53 Message: Removed unused function AutomatedAutomated XMLXML Revision: 137 Author: anilsaharan Date: 2011/8/20 9:35:13 Message: Changes for fixing XML tag issue ---- Modified : /trunk/CUnit/Sources/function.c Automated testAutomated test function.c Requirements Source code Configuration management logs Design documents Tracing based on call relationship Transitive trace
  13. 13. Industrial Experiment of Recovery [SPLC2013] • Target: Commercial Network Management Systems – 94% precision and 76% recall – Successfully recovered cross-cutting implementations • Future: application to complex IoT systems together with top- down tracing 13 Req.1 Req.2 Req.3 Req.4 Req.5 Req.6 Req.7 Req.8 Req.9 Req.10 Req.11 Req.13 Req.14 Req.15 Req.16 Req.17 Req.18 Req.19 Req.20 Req.21 Req.22 Req.23 Req.24 Req.25 Req.26 Req.27 Req.28 Req.29 Req.30 Req.31 Req.32 Req.33 Req.34 Req.35 Req.36 Req.37 Req.38 Req.39 Req.40 Req.41 Req.42 Req.43 Req.44 Req.45 Req.46 Req.47 Req.48 Req.49 Module 1 Module 2 Module 3 Module 4 Module 5 Traceability matrix Req.1 Req.2 Req.3 Req.4 Req.5 Req.6 Req.7 Req.8 Req.9 Req.10 Req.11 Req.13 Req.14 Req.15 Req.16 Req.17 Req.18 Req.19 Req.20 Req.21 Req.22 Req.23 Req.24 Req.25 Req.26 Req.27 Req.28 Req.29 Req.30 Req.31 Req.32 Req.33 Req.34 Req.35 Req.36 Req.37 Req.38 Req.39 Req.40 Req.41 Req.42 Req.43 Req.44 Req.45 Req.46 Req.47 Req.48 Req.49 Module 1 ● ● ● Module 2 ● Module 3 ● ● Module 4 ● ● ● ● ● ● Module 5 ● ● ● ● ● Req.1 Req.2 Req.3 Req.4 Req.5 Req.6 Req.7 Req.8 Req.9 Req.10 Req.11 Req.13 Req.14 Req.15 Req.16 Req.17 Req.18 Req.19 Req.20 Req.21 Req.22 Req.23 Req.24 Req.25 Req.26 Req.27 Req.28 Req.29 Req.30 Req.31 Req.32 Req.33 Req.34 Req.35 Req.36 Req.37 Req.38 Req.39 Req.40 Req.41 Req.42 Req.43 Req.44 Req.45 Req.46 Req.47 Req.48 Req.49 Module 1 ● ● ● Module 2 ● Module 3 ● ● Module 4 ● ● ● ● ● ● Module 5 ● ● ● ● ● Req.1 Req.2 Req.3 Req.4 Req.5 Req.6 Req.7 Req.8 Req.9 Req.10 Req.11 Req.13 Req.14 Req.15 Req.16 Req.17 Req.18 Req.19 Req.20 Req.21 Req.22 Req.23 Req.24 Req.25 Req.26 Req.27 Req.28 Req.29 Req.30 Req.31 Req.32 Req.33 Req.34 Req.35 Req.36 Req.37 Req.38 Req.39 Req.40 Req.41 Req.42 Req.43 Req.44 Req.45 Req.46 Req.47 Req.48 Req.49 Module 1 ● ● ● Module 2 ● Module 3 ● ● Module 4 ● ● ● ● ● ● Module 5 ● ● ● ● ● Req.1 Req.2 Req.3 Req.4 Req.5 Req.6 Req.7 Req.8 Req.9 Req.10 Req.11 Req.13 Req.14 Req.15 Req.16 Req.17 Req.18 Req.19 Req.20 Req.21 Req.22 Req.23 Req.24 Req.25 Req.26 Req.27 Req.28 Req.29 Req.30 Req.31 Req.32 Req.33 Req.34 Req.35 Req.36 Req.37 Req.38 Req.39 Req.40 Req.41 Req.42 Req.43 Req.44 Req.45 Req.46 Req.47 Req.48 Req.49 Module 1 ● ● ● Module 2 ● Module 3 ● ● Module 4 ● ● ● ● ● ● Module 5 ● ● ● ● ● Req.1 Req.2 Req.3 Req.4 Req.5 Req.6 Req.7 Req.8 Req.9 Req.10 Req.11 Req.13 Req.14 Req.15 Req.16 Req.17 Req.18 Req.19 Req.20 Req.21 Req.22 Req.23 Req.24 Req.25 Req.26 Req.27 Req.28 Req.29 Req.30 Req.31 Req.32 Req.33 Req.34 Req.35 Req.36 Req.37 Req.38 Req.39 Req.40 Req.41 Req.42 Req.43 Req.44 Req.45 Req.46 Req.47 Req.48 Req.49 Module 1 ● ● ● Module 2 ● Module 3 ● ● Module 4 ● ● ● ● ● ● Module 5 ● ● ● ● ● Ryosuke Tsuchiya, Hironori Washizaki, Yoshiaki Fukazawa, Tadahisa Kato, Masumi Kawakami, Kentaro Yoshimura, “Recovering Traceability Links between Requirements and Source Code in the Same Series of Software Products, ” Proceedings of 17th International Software Product Line Conference (SPLC 2013), pp.121-130, Tokyo, August 26-30, 2013. Req. 11 Tracing Module 1 Req. 20 Module 5 Module 4 Requirement
  14. 14. Future: Metamodel-based Comprehensive Modeling and Tracing (jointly with ChangeVision, Inc. and CATS, Inc.) • With Fraunhofer IESE, we achieved GQM+Strategies metamodel for modeling and verification [HICSS’17] • Extending the metamodel to connect from goal to implementation 14 Common metamodelCommon metamodel Goal Strategy Goal Specific metamodelSpecific metamodel …… …… …… …… …… …… …… …… …… …… …… …… …… …… …… …… …… …… IoT realization IoT domain GQM+ Strategi es Stakehold er Stakeholder Goal Strategy Relation Sensor Actuator Value Edge device Cloud Data Rational Platform Function Quality Architecture Measurement C. Shimura, H. Washizaki, et al. “Identifying Potential Problems and Risks in GQM+Strategies Models Using Metamodel and Design Principles,” HICSS 2017
  15. 15. Thank you! 15

×