Development of methods for the analysis of functional requirements to an information system for consistency and illogicality
DOI:
https://doi.org/10.15587/1729-4061.2018.121849Keywords:
requirements analysis, functional requirements, frame, inconsistency, illogicality, ontological pointAbstract
The order of work aimed at analyzing the requirements is considered, taking into account application of the service approach to development of IS, models and methods of development of representations of functional requirements to IS at the knowledge level. It was proposed to perform work on IS requirements analysis in parallel to the work on the requirements development. Such an organization of work makes it possible to reduce the time required to perform work on the IS macro design.
Methods of analysis of separate frames and relations between frames and between frames and interfaces of representations of functional requirements to IS at the knowledge level were developed. The essence of the methods lies in comparison of frames and relations, used for description of concepts and terms in a subject area. These methods make it possible to detect inconsistencies, caused by attempts to describe the same object in a subject area in different ways.
The indicator of illogicality of the stated functional requirement and the method of detection of illogical functional requirements was developed. The essence of this method lies in identification of separate branches of the frame hierarchy (ontological points) that are present in representation of only one functional requirement to IS. Such requirement is not related to other functional requirements to IS and is considered to be illogical. This method makes it possible to assess a degree of illogicality of each functional requirement, based on which it is possible to make a decision about the feasibility of IS development.
The research contains an example of testing the developed methods in the analysis of functional requirements to the project related to the functional labor safety module.
References
- Project Management Body of Knowledge (2013). Newton Square: Project Management Institute, Inc., 586.
- GOST ISO/МEК 15288-2005. System engineering. System life cycle processes (2006). Мoscow: Standartinform, 57.
- Maguire, M., Bevan, N. (2002). User Requirements Analysis. Usability, 133–148. doi: 10.1007/978-0-387-35610-5_9
- Stowell, F., Cooray, S. (2017). The Appreciative System, Learning And Its Impact Upon Is Design. Communications of the Association for Information Systems, 40, 93–119. doi: 10.17705/1cais.04006
- Ali, N., Lai, R. (2016). A method of requirements elicitation and analysis for Global Software Development. Journal of Software: Evolution and Process, 29 (4), e1830. doi: 10.1002/smr.1830
- Liu L., Zhou Q., Liu J., Cao Z. (2017). Requirements cybernetics: Elicitation based on user behavioral data. Journal of Systems and Software, 124, 187–194. doi: 10.1016/j.jss.2015.12.030
- Asteasuain, F., Braberman, V. (2016). Declaratively building behavior by means of scenario clauses. Requirements Engineering, 22 (2), 239–274. doi: 10.1007/s00766-015-0242-2
- Yu, Y.-J., Liu, C. (2017). Little Model in Big Data: An Algebraic Approach to Analysing Abstract Software Behaviours. Ruan Jian Xue Bao/Journal of Software, 28 (6), 1488–1497.
- Li, L., Harman, M., Wu, F., Zhang, Y. (2017). The Value of Exact Analysis in Requirements Selection. IEEE Transactions on Software Engineering, 43 (6), 580–596. doi: 10.1109/tse.2016.2615100
- Dermeval, D., Vilela, J., Bittencourt, I. I., Castro, J., Isotani, S., Brito, P., Silva, A. (2015). Applications of ontologies in requirements engineering: a systematic review of the literature. Requirements Engineering, 21 (4), 405–437. doi: 10.1007/s00766-015-0222-6
- Serna M. E., Bachiller S. O., Serna A. A. (2017). Knowledge meaning and management in requirements engineering. International Journal of Information Management, 37 (3), 155–161. doi: 10.1016/j.ijinfomgt.2017.01.005
- Nguyen, T. H., Grundy, J. C., Almorsy, M. (2015). Ontology-based automated support for goal–use case model analysis. Software Quality Journal, 24 (3), 635–673. doi: 10.1007/s11219-015-9281-7
- Lopez-Lorca, A. A., Beydoun, G., Valencia-Garcia, R., Martinez-Bejar, R. (2016). Supporting agent oriented requirement analysis with ontologies. International Journal of Human-Computer Studies, 87, 20–37. doi: 10.1016/j.ijhcs.2015.10.007
- Levykin, V. M., Ievlanov, M. V., Kernosov, M. A. (2014). Pattern planning of requirements to the informative systems: design and application. Kharkiv: The «Kompanіya «Smіt LTD», 320.
- 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. doi: 10.15587/1729-4061.2017.110586
- Ievlanov, M. (2015). Methods of presenting formulated requirements to the information system at the level of knowledge. Eastern-European Journal of Enterprise Technologies, 4 (3 (76)), 4–11. doi: 10.15587/1729-4061.2015.47535
- Ievlanov, M. (2016). Development of the model and method of selecting the description of rational architecture of information system. Eastern-European Journal of Enterprise Technologies, 1 (2 (79)), 4–12. doi: 10.15587/1729-4061.2016.60583
- Evlanov, M., Vasiltcova, N., Panfyorova, I. (2015). Modeli i metody syntezu opysu ratsionalnoi arkhitektury informatsiynoi systemy. Visnyk naukovoho universytetu «Lvivska politekhnika». Seriya: Informatsiyni systemy ta merezhi, 829, 135–152.
- Ievlanov, M., Neumyvakina, O. (2015). Metody analiza sformulirovannyh funkcional'nyh trebovaniy k informacionnoy sisteme. Informacionnye sistemy i tekhnologi: materialy 4-y Mezhdunarodnoy nauch.-tekhn. konf. Kharkiv: NTMT, 52–53.
- Ievlanov, М., Serdyuk, N. (2015). Forming and analysis of requirements to information-analytical system of management by safety of labour in enterprise. Technology audit and production reserves, 4 (3 (24)), 41–45. doi: 10.15587/2312-8372.2015.47972
- Core Concepts. Available at: http://www.togaf.org/togaf9/chap02.html#tag_03_01
- Temnenco V. TOGAF or not TOGAF: Extending Enterprise Architecture beyond RUP. IBM. Available at: https://www.ibm.com/developerworks/rational/library/jan07/temnenco/index.html?S_TACT=105AGX99&S_CMP=CP
- GOST ISO/MEK 10746-3-2001. Information technology. Open Systems Interconnection. Data control and Open Distributed Processing. Reference model. Part 3. Architecture (2002). Мoscow: IPK Izdatelstvo standartov, 57.
- GOST ISO/MEK 10746-4-2004. Information technology. Open Distributed Processing. Reference Model. Part 4. Architectural semantics (2004). Мoscow: IPK Izdatelstvo standartov, 34.
Downloads
Published
How to Cite
Issue
Section
License
Copyright (c) 2018 Maksym Ievlanov, Nataliya Vasiltcova, Iryna Panforova
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.