Skip to main content
SpringerLink
Log in

Modelling mobile app requirements for semantic traceability

  • Original Article
  • Published:
Requirements Engineering Aims and scope Submit manuscript

Abstract

The paper presents a modelling method aimed to support the definition and elicitation of requirements for mobile apps through an approach that enables semantic traceability for the requirements representation. Business process-centricity is employed in order to capture requirements in a knowledge structure that retains procedural knowledge from stakeholders and can be traversed by semantic queries in order to trace domain-specific contextual information for the modelled requirements. Consequently, instead of having requirements represented as natural language items that are documented by diagrammatic models, the communication channels are switched: semantically interlinked conceptual models become the requirements representation, while free text can be used for requirements annotations/metadata. Thus, the method establishes a knowledge externalization channel between business stakeholders and app developers, also tackling the Twin Peaks bridging challenge (between requirements and early designs). The method is presented using its modelling procedure as a guiding thread, with each step illustrated by case-based samples of the modelling language and auxiliary functionality. The design work is encompassed by an existing metamodelling framework and introduces a taxonomy for modelling relations, since the metamodel is the key enabler for the goal of semantic traceability. The research was driven by the ComVantage EU research project, concerned with mobile app support for collaborative business process execution. Therefore, the project provides context for the illustrating examples; however, generalization possibilities beyond the project scope will also be discussed, with respect to both motivation and outcome.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Log in via an institution

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Fig. 1
Fig. 2
Fig. 3
Fig. 4
Fig. 5
Fig. 6
Fig. 7
Fig. 8
Fig. 9
Fig. 10
Fig. 11
Fig. 12
Fig. 13
Fig. 14
Fig. 15

Similar content being viewed by others

References

  1. Ali R, Dalpiaz F, Giorgini P (2010) A goal-based framework for contextual requirements modeling and analysis. Requir Eng 15:439–458. doi:10.1007/s00766-010-0110-z

    Article  Google Scholar 

  2. Aquino N, Vanderdonckt J, Panach JI, Pastor O (2011) Conceptual modelling of interaction. In: Embley D, Thalheim B (eds) Handbook of conceptual modeling: theory, practice and research challenges. Springer, Berlin, pp 335–355

    Chapter  Google Scholar 

  3. Apel S, Kästner C (2009) An overview of feature-oriented software development. J Object Technol 8(5):49–84. http://www.jot.fm/issues/issue_2009_07/column5.pdf

  4. Beatty J, Chen A (2012) Visual models for software requirements. Microsoft Press, Redmond, Washington

  5. Beatty J, Ferrari R, Vijayan B, Godugula S (2011) Seilevel’s evaluations of requirements management tools. http://www.seilevel.com/download/9772/. Accessed Nov 2013

  6. Berenbach B, Schneider F, Naughton H (2012) The use of a requirements modeling language for industrial applications. In: Proceedings of 20th IEEE International Conference on requirements engineering (RE 2012), IEEE, pp 285–290

  7. Bizer C, Cyganiak R (2013) The TriG syntax specification. http://wifo5-03.informatik.uni-mannheim.de/bizer/trig/. Accessed Nov 2013

  8. BOC-Group (2013) ADONIS community edition tool. http://www.adonis-community.com/. Accessed Nov 2013

  9. BOC-Group (2013) ADOxx tool. http://www.adoxx.org/live/. Accessed Nov 2013

  10. Bogdan C, Falb J, Kaindl H, Kavaldjian S, Popp R, Horacek H, Arnautovic E, Szep A (2008) Generating an abstract user interface from a discourse model inspired by human communication. In: 41st Hawaii international conference on systems sciences, IEEE, pp 36

  11. Buchmann RA (2014) Conceptual modeling for mobile maintenance: the ComVantage case. In: 47th Hawaii international conference on systems sciences, IEEE, pp 3390–3399

  12. Buchmann R, Karagiannis D, Visic N (2013) Requirements definition for domain specific modelling languages: the ComVantage case. In: Proceedings of BIR 2013, Springer, pp 19–33

  13. Calefato F, Damian D, Lanubile F (2013) Computer-mediated communication to support distributed requirements elicitations and negotiations tasks. Empir Softw Eng 17(6):640–674

    Article  Google Scholar 

  14. Calvary G, Coutaz J, Thevenin D, Limbourg Q, Bouillon L, Vanderdonckt J (2003) A unifying reference framework for multi-target user interfaces. Interact Comput 15(3):289–308

    Article  Google Scholar 

  15. Carroll J, Stickler P (2013) The TriX syntax specification. http://www.hpl.hp.com/techreports/2004/HPL-2004-56.html. Accessed Nov 2013

  16. Cohn M (2004) User stories applied: for agile software development. Addison Wesley, Boston

    Google Scholar 

  17. ComVantage Research Project Consortium (2013) Project public deliverables. http://www.comvantage.eu/results-publications/public-deriverables/. Accessed in Nov 2013

  18. Dardenne A, van Lamsweerde A, Fickas S (1993) Goal-directed requirements acquisition. Sci Comput Program 20(1–2):3–50

    Article  MATH  Google Scholar 

  19. Dijkman R, Dumas M, van Dongen B, Kaarik R, Mendling J (2011) Similarity of business process models: metrics and evaluation. Inf Syst 36(2):498–516

    Article  Google Scholar 

  20. Fuentes-Fernandez R, Gomez-Sanz JJ, Pavon J (2010) Understanding the human context in requirements elicitation. Requir Eng 15:267–283. doi:10.1007/s00766-009-0087-7

    Article  Google Scholar 

  21. FusionForge Tool (2013). https://fusionforge.org/. Accessed in Nov 2013

  22. Future Internet Enterprise Systsems cluster (2013) The FInES research roadmap 2025. http://cordis.europa.eu/fp7/ict/enet/documents/fines-research-roadmap-v30_en.pdf. Accessed Nov 2013

  23. Goal-oriented Requirements Language Resources (2013). http://www.cs.toronto.edu/km/GRL/. Accessed Nov 2013

  24. Gordijn J, Akkermans H (2001) E3-value: design and evaluation of e-business models. IEEE Intell Syst 16(4):11–17

    Article  Google Scholar 

  25. Greenspan SJ, Mylopoulos J, Borgida A (1982) Capturing more world knowledge in the requirements specification. In: Proceeding international conference on software engineering, Tokyo, 1982

  26. IBM Rational Requirements Composer Tool (2013). http://www-03.ibm.com/software/products/en/rrc. Accessed in Nov 2013

  27. I-star resources (2013). http://www.cs.toronto.edu/km/istar/. Accessed Nov 2013

  28. Jackson M (2014) Topsy-turvy requirements. Requir Eng 19:107–111. doi:10.1007/s00766-013-0179-2

    Article  Google Scholar 

  29. Kaindl H, Svetinovic D (2010) On confusion between requirements and their representations. Requir Eng 15:307–311. doi:10.1007/s00766-009-0095-7

    Article  Google Scholar 

  30. Kang K, Cohen S, Hess J, Novak W, Peterson A (1990) Feature-oriented domain analysis (FODA) feasibility study, Software Engineering Institute, technical report CMU/SEI-90-TR-021

  31. Karagiannis D, Kühn H (2002) Metamodelling platforms. In: Proceedings of the 3rd International conference EC-Web 2002—DEXA 2002. LNCS 2455, Springer, pp 451–464

  32. Krogstie J, Lyytinen K, Opdahl AL, Pernici B, Siau K, Smolander K (2004) Research areas and challenges for mobile information systems. Int J Mobile Commun 2(3):220–234

    Article  Google Scholar 

  33. Linked Open Data 2—the EU Project page (2013). http://lod2.eu. Accessed Nov 2013

  34. Loucks J, Medcalf R, Buckalew L, Faria F (2013) The financial impact of BYOD. http://www.cisco.com/web/about/ac79/docs/re/byod/BYOD-Economics_Econ_Analysis.pdf. Accessed Nov 2013

  35. Microsoft Visio, the official website. http://visio.microsoft.com/en-us/pages/default.aspx. Accessed Nov 2013

  36. Monteiro E, Araújo J, Amaral V, Goulão M, Patrício P (2013) Model-driven development for requirements engineering: the case of goal-oriented approaches. 8th International Conference on the Quality of information and communications technology (QUATIC 2012), IEEE CPS, pp 75–84

  37. Moody D (2009) The physics of notations: towards a scientific basis for constructing visual notations in software engineering. IEEE Trans Softw Eng 35(5):756–777

    Article  Google Scholar 

  38. Morgan J (2012) Guidelines for chaining iOS apps. http://usabilityetc.com/2012/05/guidelines-for-chaining-ios-apps/. Accessed Nov 2013

  39. Mylopoulos J (1992) Conceptual modeling and Telos1. In: Loucopoulos P, Zicari R (eds) Conceptual modeling, databases, and case an integrated view of information systems development. Wiley, New York, pp 49–68

    Google Scholar 

  40. Nunes NJ, Cunha JF (2000) Wisdom: a software engineering method for small software development companies. IEEE Softw 17(5):113–119

    Article  Google Scholar 

  41. Nuseibeh B (2001) Weaving together requirements and architecture. Computer 34(3):115–119

    Article  Google Scholar 

  42. Object Management Group (2011) ReqIF documentation. http://www.omg.org/spec/ReqIF/1.0.1/. Accessed Nov 2013

  43. Object Management Group (2011) XMI specification. http://www.omg.org/spec/XMI/. Accessed Nov 2013

  44. Object Management Group (2012) SysML specification. http://www.omgsysml.org/. Accessed Nov 2013

  45. Object Management Group (2013) UML resource page. http://www.uml.org/. Accessed Nov 2013

  46. Open Model Initiative Laboratory (2013) ComVantage modelling prototype and resources. http://www.omilab.org/web/comvantage/home. Accessed Nov 2013

  47. Open Requirements Management Framework (2008). http://www.eclipse.org/proposals/ormf/. Accessed Nov 2013

  48. Ralph P (2013) The illusion of requirements in software development. Requir Eng 18:293–296. doi:10.1007/s00766-012-0161-4

    Article  Google Scholar 

  49. Requirements model in ORMF (2008). http://wiki.eclipse.org/Requirements_Model. Accessed Nov 2013

  50. Seilevel (2013) Requirements modeling language templates. http://www.seilevel.com/ba-resources/rml-requirements-visual-models/. Accessed Nov 2013

  51. Sequeda J (2010) I believe linked data will enable new killer apps that are only possible thanks to linked data. http://www.semantic-web.at/news/juan-sequeda-x22-i-believe-linked-data-will-enable-new-killer-apps-that-are-only-possible. Accessed Nov 2013

  52. Shaker P, Atlee JM, Shige W (2012) A feature-oriented requirements modelling language. In: Proceedings of 20th IEEE international conference on requirements engineering (RE 2012), IEEE, pp 151–160

  53. da Silva PP, Paton NW (2003) User interface modeling in UMLi. IEEE Softw 20(4):62–69

    Article  Google Scholar 

  54. Simon K (2010) SIPOC diagram. http://www.isixsigma.com/tools-templates/sipoc-copis/sipoc-diagram/. Accessed Nov 2013

  55. Software production lines community (2013). http://www.softwareproductlines.com/. Accessed Nov 2013

  56. Sundaran SK, Hayes JH, Dekhtyar A, Holbrook EA (2010) Assessing traceability of software engineering artifacts. Requir Eng 15:313–335. doi:10.1007/s00766-009-0096-6

    Article  Google Scholar 

  57. Supply Chain Council (2013) The supply chain operations reference specification. http://supply-chain.org/scor. Accessed in Nov 2013

  58. SWIRRL official website (2013). http://www.swirrl.com/publishmydata. Accessed Nov 2013

  59. UsiXML—official page (2013). http://www.usixml.org/en/home.html?IDC=221. Accessed Nov 2013

  60. Vidgen R (2003) Requirements analysis and UML: use cases and class diagrams. Comput Control Eng 14(2):12–15

    Article  Google Scholar 

  61. W3C (2004) The RDF standard resources and specification. http://www.w3.org/RDF/. Accessed in Nov 2013

  62. W3C (2012) Concur task trees submission page. http://www.w3.org/2012/02/ctt/. Accessed Nov 2013

  63. W3C (2013) Linked data platform use cases and requirements. http://www.w3.org/TR/ldp-ucr/. Accessed Nov 2013

  64. W3C (2013) SPARQL 1.1 federated query. http://www.w3.org/TR/sparql11-federated-query/. Accessed Nov 2013

  65. W3C (2013) The SPARQL query language specification. http://www.w3.org/TR/sparql11-query/. Accessed in Nov 2013

  66. Wanderley F, da Silveira D.S, Araújo J, Lencastre M (2013) Generating feature model from creative requirements using model driven design. In: Proceedings of the 16th Int. software product line conference, vol 2. ACM, New York, pp 18–25

  67. Ziegler J, Graube M, Pfeffer J, Urbas L (2012) Beyond app-chaining—mobile app orchestration for efficient model driven software generation. Proceedings of the 17th IEEE international conference on emerging technologies and factory automation. IEEE, pp 1–8

Download references

Acknowledgments

The research leading to these results was funded by the European Community’s Seventh Framework Programme under Grant Agreement No. FP7-284928 ComVantage.

Author information

Authors and Affiliations

  1. Faculty of Economic Sciences and Business Administration, University Babes-Bolyai of Cluj Napoca, Str. Teodor Mihali 58-60, 400591, Cluj Napoca, Romania

    Robert Andrei Buchmann

  2. Faculty of Computer Science, Knowledge Engineering Research Group, University of Vienna, Waehringerstr. 29, 1090, Vienna, Austria

    Robert Andrei Buchmann & Dimitris Karagiannis

Authors
  1. Robert Andrei Buchmann
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Dimitris Karagiannis
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Robert Andrei Buchmann.

Rights and permissions

Reprints and permissions

About this article

Check for updates. Verify currency and authenticity via CrossMark

Cite this article

Buchmann, R.A., Karagiannis, D. Modelling mobile app requirements for semantic traceability. Requirements Eng 22, 41–75 (2017). https://doi.org/10.1007/s00766-015-0235-1

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s00766-015-0235-1

Keywords

Search

Navigation