Selection of standards in accordance with the stages of the life cycle of information systems
Abstract
Defining a set of standards is one of the most important components of creating an information system, since standards, firstly, simplify almost all life cycle processes due to their clarity and structure, and, secondly, allow, if they are properly selected and applied, to secure the team of performers, the customer and the product itself in the regulatory sphere.
The structure of any modern information system, as a rule, includes a software tool, which, upon completion of all work, becomes a software product. The creation of a software product is a time-consuming process that is often delayed or even stopped for various reasons, which are usually associated with poor quality of work, exceeding time limits or misunderstanding between the contractor and the customer. Generally, such problems arise due to the fact that the execution team cannot correctly determine the product implementation model at the stages of its life cycle from requirements generation to testing and documentation.
Standards often act as instructions for stakeholders. However, choosing standards that are inappropriate for a particular product can complicate the task of implementing it instead of simplifying it, so it is important to be able to choose the most appropriate standards at all stages of the product life cycle.
This article demonstrates a possible course of analysis and selection of standards at all stages of the life cycle using the example of a software system for the entrance profiling of enrollees.Full Text:
PDF (Russian)References
V.V. Kholmogorov, V.V. Baranyuk. Program system for entrance profiling of applicants - help in choosing a future profession / International Journal of Open Information Technologies. 2021. - Volume 9. - No. 5. - With. 47-51.
GOST R ISO/IEC 12207-2010 “Information technology. System and software engineering. Software Life Cycle Processes”.
GOST 19.201-78 “Unified system of program documentation. Technical task. Requirements for content and design.
GOST 34.602-89 “Information technology. Set of standards for automated systems. Terms of reference for the creation of an automated system.
GOST 19.201-78 “Unified system of program documentation. Technical task. Requirements for content and design.
GOST R ISO/IEC 9294-93 “Information technology. Software Documentation Management Guide.
ISO/IEC/IEEE 42010:2011 "Addresses the creation, analysis and sustainment of architectures of systems through the use of architecture descriptions".
GOST R 57100-2016/ISO/IEC/IEEE 42010:2011 “System and software engineering. Description of architecture.
ISO/IEC 19505 "Information technology - Object Management Group Unified Modeling Language (OMG UML)".
ISO/TR 9007:1987 "Concepts and terminology for the conceptual schema and the information base".
GOST 34.320-96 “Information technologies. Database standards system. Concepts and terminology for the conceptual scheme and information base.
ISO/IEC 10032:1995 "Information technology - Reference model of data management".
GOST 34.321-96. "Information Technology. Database standards system. Reference Model for Data Management.
A.A. Bodaleva, V.V. Stolin, A.G. Shmeleva (Moscow State University), V.I. Pokhilko (I MMI), A.A. Kronika (IPAN). "Regulatory instructions for developers and users of psychodiagnostic methods", URL: http://www.voppsy.ru/issues/1987/875/875176.htm (date of access: 28.08.2021).
IEEE 1008 Software Unit Testing.
ISO/IEC/IEEE 29119-1:2013, Part 1: Concepts and definitions, published in September 2013.
GOST R 56920-2016/ISO/IEC/IEEE 29119-1:2013 “System and software engineering. Software testing. Part 1. Concepts and definitions.
ISO/IEC/IEEE 29119-2:2013, Part 2: Test processes.
GOST R 56921-2016/ISO/IEC/IEEE 29119-2:2013 “System and software engineering. Software testing. Part 2. Testing processes.
ISO/IEC/IEEE 29119-3:2013, Part 3: Test documentation.
GOST R 56922-2016/ “System and software engineering. Software testing. Part 3. Testing Documentation.
ISO/IEC/IEEE 29119-4:2015, Part 4: Test techniques.
ISO/IEC/IEEE 29119-5:2016, Part 5: Keyword-driven testing.
BS 7925-1 Vocabulary of terms in software testing.
IEEE 829-2008 - IEEE Standard for Software and System Test Documentation.
ISO/IEC 25051:2014 "Software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) - Requirements for quality of Ready to Use Software Product (RUSP) and instructions for testing", IDT.
GOST R ISO/IEC 25051-2017 “System and software engineering. Requirements and quality assessment of systems and software (SQuaRE). Quality Requirements for a Ready-to-Use Software Product (RUSP) and Testing Instructions.
GOST 34.201-89 "Types, completeness and designation of documents when creating automated systems".
GOST 19.105-78 "General requirements for program documents".
GOST R ISO/IEC 9294-93 “Information technology. Software Documentation Management Guide.
GOST 28195-89 “Assessment of the quality of software. General Provisions".
ISO/IEC 9126-93 Information technology. Evaluation of software products. Quality characteristics and guidelines for their application.
GOST R ISO/IEC 25040-2014 “Information technology (IT). System and software engineering. Requirements and quality assessment of systems and software (SQuaRE). Evaluation Process".
ISO/IEC 25040:2011 "Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) - Evaluation process".
ISO/IEC 14598-3:2000 "Software engineering - Product evaluation - Part 3: Process for developers".
Federal Law No. 184-FZ of December 27, 2002 On Technical Regulation.
Information technologies in economics and management in 2 hours. Part 2: a textbook for secondary vocational education / VV Trofimov [and others]; edited by V. V. Trofimov. - 3rd ed., revised. and additional - Moscow: Yurayt Publishing House, 2018. - 245 p. - (Professional education). - ISBN 978-5-534-09139-7.
Refbacks
- There are currently no refbacks.
Abava Кибербезопасность IT Congress 2024
ISSN: 2307-8162