Methodical recommendation to the laboratory work "Planning of System Activities" for the course "Basics of Software Engineering"

Abstract

Software engineering is an engineering discipline that is concerned with all aspects of software production [1]. Software engineering can be divided into sub-disciplines [2]. Some of them are: 1 Software engineering management: The application of management activities – planning, coordinating, measuring, monitoring, controlling, and reporting – to ensure that the development and maintenance of software is systematic, disciplined, and quantified. 2 Requirements engineering: The elicitation, analysis, specification, and validation of requirements for software. 3 Software design: The process of defining the architecture, components, interfaces, and other characteristics of a system or component. 4 Software construction: The detailed creation of working, meaningful software through a combination of programming, verification, unit testing, integration testing, and debugging. 5 Software testing: An empirical, technical investigation conducted to provide stakeholders with information about the quality of the product or service under test. 6 Software maintenance: The totality of activities required to provide cost effective support to software. 7 Software quality. The outcome of software engineering is an efficient and reliable software product. Software product is a computer programs with all associated documentation and configuration data that is required to make these programs operate correctly [1]. Essential attributes of good software product: maintainability, dependability and security, efficiency, acceptability. A software process is a sequence of activities that leads to the production of a software product. Four fundamental activities are common to all software processes. These activities are: 1 Software specification, where customers and engineers define the software that is to be produced and the constraints on its operation. 2 Software development, where the software is designed and programmed. 3 Software validation, where the software is checked to ensure that it is what the customer requires. 4 Software evolution, where the software is modified to reflect changing customer and market requirements. The methodical recommendation is about modelling (or designing) and creating a software that will help to calculate some system of expressions with unknown variables. The values of variables can be obtained from different sources: from file or from keyboard.