Developing the models of patterns in the design of requirements to an information system at the knowledge level

Authors

DOI:

https://doi.org/10.15587/1729-4061.2017.110586

Keywords:

IT-service, needs, functional requirements, reuse, requirements design pattern, frame, tuple

Abstract

Results of research into mining and processing of knowledge from IS requirements were analyzed. Modification of the frame-based model of knowledge that allows description of knowledge about structures of data and interaction processes is considered. The essence of modification is to extend the frame with descriptions of a totality of methods, associated with a frame as a whole, as well as descriptions of interfaces of a frame. This modification also makes it possible in a formalized way to describe the problem of automated synthesis of IS information and software as a set of one-to-one mappings of frame descriptions.

Theoretical-multiple models of structural IS requirements design patterns at the knowledge level were developed. These models allow describing the knowledge, derived from IS requirements descriptions in the form of a network of frames. This network consists of individual frames, interfaces of frames and relationships between them. The use of these models makes it possible to formalize the process of designing of IS architecture based on knowledge, derived from IS requirements descriptions, which significantly reduces the time spent on IS creation.

Theoretical-multiple models of behavioral IS requirements design patterns at the knowledge level were developed. These models establish the main features of operations of addition, modifications and deletion of elements of structural IS requirements design patterns. In addition, developed models describe operations on formation of knowledge-oriented descriptions of IS architecture in the form of a network of frames and interfaces. Application of these models enables us to standardize implementation of operations on the knowledge, derived from patterns, and on patterns of designing structural frames.

It was proposed to consider implementation of the developed models in the form of specialized data showcases and sets of SQL-commands that implement developed behavioral patterns.

Author Biographies

Viktor Levykin, Kharkiv National University of Radio Electronics Nauky ave., 14, Kharkiv, Ukraine, 61166

Doctor of Technical Science, Professor

Department of information control systems

Maksym Ievlanov, Kharkiv National University of Radio Electronics Nauky ave., 14, Kharkiv, Ukraine, 61166

Doctor of Technical Science, Associate Professor

Department of information control systems

Olga Neumyvakina, Kharkiv National University of Radio Electronics Nauky ave., 14, Kharkiv, Ukraine, 61166

PhD, Leading Researcher

Department of information control systems

References

  1. Mansilla, D., Pollo-Cattaneo, M., Britos, P., García-Martínez, R. (2013). A Proposal of a Process Model for Requirements Elicitation in Information Mining Projects. Enterprise Information Systems of the Future, 165–173. doi: 10.1007/978-3-642-36611-6_13
  2. Berkovich, M., Leimeister, J. M., Hoffmann, A., Krcmar, H. (2012). A requirements data model for product service systems. Requirements Engineering, 19 (2), 161–186. doi: 10.1007/s00766-012-0164-1
  3. Lucassen, G., Dalpiaz, F., van der Werf, J. M. E. M., Brinkkemper, S. (2016). Improving agile requirements: the Quality User Story framework and tool. Requirements Engineering, 21 (3), 383–403. doi: 10.1007/s00766-016-0250-x
  4. Modelirovanie trebovaniy pol'zovateley. Microsoft Developer Network. Available at: https://msdn.microsoft.com/ru-ru/library/dd409376.aspx
  5. Vilpola, I. H. (2008). A method for improving ERP implementation success by the principles and process of user-centred design. Enterprise Information Systems, 2 (1), 47–76. doi: 10.1080/17517570701793848
  6. Sutcliffe, A. (1998). Scenario-based requirements analysis. Requirements Engineering, 3 (1), 48–65. doi: 10.1007/bf02802920
  7. Lipko, Yu. (2014). Algoritm formalizacii trebovaniy pri razrabotke informacionnyh system. Izvestiya Yuzhnogo federal'nogo universiteta. Tekhnicheskie nauki, 6 (155), 153–158.
  8. Cleland-Huang, J. (2015). Mining Domain Knowledge [Requirements]. IEEE Software, 32 (3), 16–19. doi: 10.1109/ms.2015.67
  9. Tyurganov, A. G. (2007). Osobennosti formalizacii predmetnoy oblasti korporativnyh informacionnyh system. Vestnik Ufimskogo gosudarstvennogo aviacionnogo tekhnicheskogo universiteta, 9 (5), 72–76.
  10. Yue, T., Briand, L. C., Labiche, Y. (2010). A systematic review of transformation approaches between user requirements and analysis models. Requirements Engineering, 16 (2), 75–99. doi: 10.1007/s00766-010-0111-y
  11. Ralph, P. (2012). The illusion of requirements in software development. Requirements Engineering, 18 (3), 293–296. doi: 10.1007/s00766-012-0161-4
  12. Rational Requisite Pro. IBM developerWorks. Available at: https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Wbcd69e09400c_4f72_9665_66f116225986/page/Rational%20RequisitePro
  13. IBM Rational DOORS Next Generation. An efficient requirements management tool for complex systems. IBM. Available at: http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=SP&infotype=PM&appname=SWGE_RA_IR_USEN&htmlfid=RAD14128USEN&attachment=RAD14128USEN.PDF
  14. Cradle Overview. 3SL. Available at: https://www.threesl.com/en/cradle/index.php
  15. Sistema upravleniya trebovaniyami Devprom Requirements. DEVPROM. Available at: http://devprom.ru/features/Система-управления-требованиями-Devprom-Requirements
  16. Madorskaya, Yu. M. Sistemy upravleniya trebovaniyami: chto i zachem? ReqCenter.pro. Soglasovannye znaniya dlya prakticheskogo ispol'zovaniya. Available at: http://edu.reqcenter.pro/?p=2433
  17. Luckham, D. The Beginnings of IT Insight: Business Activity Monitoring. Real Time Intelligence & Complex Event Processing. Available at: http://complexevents.com/media/articles/cep-article-three.pdf
  18. Levykin, V. M., Evlanov, M. V., Kernosov, M. A. (2014). Patterny proektirovaniya trebovaniy k informacionnym sistemam: modelirovanie i primenenie. Kharkiv: OOO «Kompanіya «Smіt», 320.
  19. Lassila, O. (1990). Frames or Objects, or Both? Workshop Notes from the Eight National Conference on Artificial Intelligence (AAAI-90). Object-Oriented Programming in AI, Boston (Massachusetts, U.S.A.), 8. Available at: https://pdfs.semanticscholar.org/c357/adb27b4564751552ff490a04703b39f4620b.pdf
  20. Wu, Х. (1996). A Comparison of Objects with Frames and OODBs. Object Currents, 1 (1).
  21. Minskiy, M. (1979). Freymy dlya predstavleniya znaniy. Moscow: Energiya, 152.
  22. Pospelov, D. A. (Ed.) (1990). Iskusstvennyy intellekt. Kn. 2. Modeli i metody. Moscow: Radio i svyaz', 304.
  23. Maciaszek, L. A. (2005). Requirements Analysis and System Design. Reading: Addison Wesley, Harlow England, 504.
  24. Gavrilov, A. V. (2004). Sistemy iskusstvennogo intellekta. Novosibirsk: NGTU, 59.
  25. Savitch, W. (2001). Java: An Introduction to Computer Science and Programming. Pearson: Prentice Hall, Inc, 1039.
  26. Deitel, H. M., Deitel, P. J. (2005). C++ How to Program. Pearson: Prentice Hall, Inc, 1536.
  27. Levykin, V. M., Kernosov, M. A. (2008). Issledovanie i razrabotka freymovoy modeli struktury dokumenta. Novi tekhnolohyi, 1 (19), 149–154.
  28. Evlanov, M. V. (2014). Modeli patternov proektirovaniya trebovaniy k informacionnoy sisteme na urovne dannyh. Radioelektronni i kompiuterni systemy, 1 (65), 128–138.
  29. Levykin, V. M., Evlanov, M. V., Sugrobov, V. S. (2006). Parallel'noe proektirovanie informacionnogo i programmnogo kompleksov informacionnoy sistemy. Radiotekhnika, 146, 89–98.
  30. Yevlanov, M. V. (2014). Paterny proektuvannia vymoh do informatsiynoi systemy. Visnyk natsionalnoho universytetu «Lvivska politekhnika», 783, 429–434.

Downloads

Published

2017-10-30

How to Cite

Levykin, V., Ievlanov, M., & Neumyvakina, O. (2017). Developing the models of patterns in the design of requirements to an information system at the knowledge level. Eastern-European Journal of Enterprise Technologies, 5(2 (89), 19–26. https://doi.org/10.15587/1729-4061.2017.110586

Issue

Vol. 5 No. 2 (89) (2017): INFORMATION TECHNOLOGY. INDUSTRY CONTROL SYSTEMS

Section

Information technology

License

Copyright (c) 2017 Viktor Levykin, Maksym Ievlanov, Olga Neumyvakina

Creative Commons License

This work is licensed under a Creative Commons Attribution 4.0 International License.

The consolidation and conditions for the transfer of copyright (identification of authorship) is carried out in the License Agreement. In particular, the authors reserve the right to the authorship of their manuscript and transfer the first publication of this work to the journal under the terms of the Creative Commons CC BY license. At the same time, they have the right to conclude on their own additional agreements concerning the non-exclusive distribution of the work in the form in which it was published by this journal, but provided that the link to the first publication of the article in this journal is preserved.

A license agreement is a document in which the author warrants that he/she owns all copyright for the work (manuscript, article, etc.).
The authors, signing the License Agreement with TECHNOLOGY CENTER PC, have all rights to the further use of their work, provided that they link to our edition in which the work was published.
According to the terms of the License Agreement, the Publisher TECHNOLOGY CENTER PC does not take away your copyrights and receives permission from the authors to use and dissemination of the publication through the world's scientific resources (own electronic resources, scientometric databases, repositories, libraries, etc.).
In the absence of a signed License Agreement or in the absence of this agreement of identifiers allowing to identify the identity of the author, the editors have no right to work with the manuscript.
It is important to remember that there is another type of agreement between authors and publishers – when copyright is transferred from the authors to the publisher. In this case, the authors lose ownership of their work and may not use it in any way.