Let’s first understand what the development of software means. The term consists of two words, software and technology.
Software is more than just a software code. The program is an executable code that performs some computational tasks. Software is considered a collection of executable software code, related libraries and documentation. Software, if it is made for a specific requirement, is called a software product.
On the other hand, engineering is the development of products using clearly defined scientific principles and methods.
Software engineering is an engineering industry related to the development of a software product using clearly defined scientific principles, methods and procedures. The result of software development is an effective and reliable software product.
Definitions
IEEE defines the development of software as:
(1) the use of a systematic, disciplined, quantitative approach to the development, operation and maintenance of software; That is, the use of technology to software.
(2) the study of approaches, as in the above statement.
(1) the use of a systematic, disciplined, quantitative approach to the development, operation and maintenance of software; That is, the use of technology to software.
(2) the study of approaches, as in the above statement.
Fritz Bauer, a German programmer, defines the development of software as:
Software engineering is the creation and use of sound engineering principles to obtain economically profitable software, which works effectively on real machines.
Software engineering is the creation and use of sound engineering principles to obtain economically profitable software, which works effectively on real machines.
Software evolution
The process of developing a software product using the principles and methods of software development is called software evolution. This includes the initial development of software, its maintenance and update until the desired software product is developed, which satisfies the expected requirements.
Evolution begins with the process of collecting requirements. After that, the developers create a prototype of the alleged software and show it to users to get their reviews at an early stage of software development. Users offer changes by which several consistent updates and maintenance also continue to change. This process changes to the source software until the desired software has been completed.
Even after the user has received the desired software, advanced technology and changing requirements force the software product to change accordingly. It is impossible to relax the software from scratch and go one on one on one. The only possible and economical solution is to update the existing software so that it meets the last requirements.
Law on the evolution of software
Lehman has given laws for software development. He divided the software into three categories:
S-type (static type) is software that works strictly in accordance with certain specifications and solutions. The solution and a way to achieve it are immediately understood before encoding. S-type software is least subject to changes, so this is the simplest of all. For example, a calculator program for mathematical calculations.
P-type (practical type) is software with a set of procedures. This is determined precisely by what the procedures can do. In this software, the specification can be described, but the solution is not obvious immediately. For example, game software.
The electronic type (built -in) – this software is closely related to the requirements of the real environment. This software has a high degree of evolution, since in real situations various changes in the laws, taxes, etc., for example, software for online trade.
E-Type software evolution
Lehman has given eight laws for the development of E-Type software-
Continuing changes. The electronic type program system should continue to adapt to changes in the real world, otherwise it becomes less and less useful.
Increasing complexity. As the system of type E develops, its complexity increases if work is not carried out on its maintenance or reduction.
Preservation of familiarity – acquaintance with the software or knowledge of how it was developed, why it was developed in this way, etc., should be maintained at any cost for the implementation of changes in the system.
Continuing growth. In order for the E-type system to be intended to solve any business problem, its size for the implementation of changes increases in accordance with changes in the lifestyle of business.
Reducing quality. The E software system of type E worsens the quality if it is not carefully supported and adapt to the changing operating room.
Feedback systems. E-type software systems are multi-circuit multi-level feedback systems and should be considered as such to successfully modify or improve.
Self-regulation-the processes of evolution of the E-type system are self-regulatory with the distribution of products and measures close to normal.
Organizational stability. The average effective global level of activity in the developing system of electronic type does not change during the service life of the product.
Software paradigms
Software paradigms belong to the methods and steps that are undertaken during the development of software. There are many methods proposed and working at present, but we must see where these paradigms are in the development of software. They can be combined into various categories, although each of them is contained in one:
Software evolution
The programming paradigm is a subset of the software development paradigm, which is another subset of the software development paradigm.
Software development paradigm
This paradigm is known as the software development paradigm, which apply all engineering concepts related to software development. It includes various studies and collection of requirements that help build a software product. This consists of –
Collection of requirements
Development of software
programming
Software development paradigm
This paradigm is part of the software development and includes –
- Maintenance
- Programming
- design
Programming paradigm
This paradigm is closely related to the software aspect of software development. It includes –
- coding
- testing
- integration
The need to develop software
The need to develop software arises due to a higher speed of changing the requirements of the user and the environment in which the software works.