Methods of presenting formulated requirements to the information system at the level of knowledge
DOI:
https://doi.org/10.15587/1729-4061.2015.47535Keywords:
information system, functional requirements, design patterns, frame, interface, connectionAbstract
The paper presents research findings on the methods of presenting formulated functional requirements to the information system at the level of knowledge. The approaches developed in the study are as follows: a method of presenting functional requirements at the level of knowledge of an individual participant of the automated process, a method of presenting functional requirements at the level of knowledge of the Consumer of IT services, a method of presenting functional requirements at the level of knowledge of the Provider of IT services, and a method of presenting functional requirements at the level of system-wide knowledge.
The developed methods allow automation of the processes of presenting and analysing functional requirements to information systems.
With the help of these methods, the task of matching the requirements of the Consumer with those of the Provider of IT services can be viewed as the task of creating a system-wide presentation of requirements at the level of knowledge. This considerably simplifies the solution of the problem of synthesis in the descriptions of the rational architecture of the information system.
The devised methods and the thereby resulting tools of developing information systems unify and simplify the processes of pre-surveying and designing information systems. This, in turn, helps reduce the cost and time of implementing IT projects for creation and upgrading of information systems. Moreover, the use of the developed methods allows the Provider to adapt previously obtained solutions to the peculiarities of the new requirements of the Consumer.
References
- GOST ISO/МEК 15288–2005. System engineering. System life cycle processes. (2006). Introduced 01–01–2007. М.: Standartinform, 57.
- GOST ISO/МEК 12207–2010. System and software engineering – Software life cycle processes. (2011). Introduced 01–03–2012. М.: Standartinform, 100.
- An Introduction to Structured Systems Analysis & Design Methodology (SSADM). Office of Government Chief Information Officer. Available: http://www.ogcio.gov.hk/en/infrastructure/methodology/ssadm/doc/s3a_pub.pdf. Last accessed 16 June 2015.
- Levikin, V. M., Ievlanov, M. V., Kernosov, M. A. (2014). Pattern planning of requirements to the informative systems: design and application. Kharkov: The «Kompanіya «Smіt LTD», 320.
- Futrell, R. T., Shafer, D. F., Shafer, L. I. (2003). Quality Software Project Management. M.: Publishing House “Viljams”, 1136.
- Leffingwell, D., Widrig, D. (2002). Managing Software Requirements: A Unified Approach. M.: Publishing House “Viljams”,448.
- Viegers, K. E. (2004). Software requirements. M.: Russkaia redakciia, 576.
- Coebern, A. (2012). Writing Effective Use Cases. M.: Lori, 288.
- Vilpola, I. H. (2008, February). A method for improving ERP implementation success by the principles and process of user-centred design. Enterprise Information Systems, Vol. 2, № 1, 47–76. doi:10.1080/17517570701793848
- Sutcliffe, A. (1998, March). Scenario-based requirements analysis. Requirements Engineering, Vol. 3, № 1, 48–65. doi:10.1007/bf02802920
- Mansilla, D., Pollo-Cattaneo, M., Britos, P., García-Martínez, R. (2013) Proposal of a Process Model for Requirements Elicitation in Information Mining Projects. Lecture Notes in Business Information Processing, 165–173. doi:10.1007/978-3-642-36611-6_13
- Lipko, Yu. (2014). Algoritm formalizacii trebovaniy pri razrabotke informacionnyh system. Izvestiia Yuznogo federalnogo universiteta. Tehnicheskie nauki, № 6 (155), 153–158.
- Yue, T., Briand, L. C., Labiche, Y. (2010, August 26). A systematic review of transformation approaches between user requirements and analysis models. Requirements Engineering, Vol. 16, № 2, 75–99. doi:10.1007/s00766-010-0111-y
- Tiurganov, A. G. (2007). Osobennosti formalizacii predmetnoy oblasti korporativnyh informacionnyh system. Vestnik Ufimskogo gosudarstvennogo aviacionnogo universiteta, Vol. 9, № 5, 72–76.
- Cleland-Huang, J. (2015, May). Mining Domain Knowledge [Requirements]. IEEE Softw, Vol. 32, № 3, 16–19. doi:10.1109/ms.2015.67
- Ievlanov, M. V. (2014). Pattern design requirements for an information system. Bulletin of the National University "Lviv Polytechnic", № 783, 429–434.
- Ievlanov, M. V. (2014). Task of the synthesis of information system architecture description. Bulletin of the National University "Lviv Polytechnic", № 805, 114–123.
Downloads
Published
How to Cite
Issue
Section
License
Copyright (c) 2015 Максим Викторович Евланов
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.
