Welcome to our Standards pages!
Software development has become increasingly complex and challenging. Programs and applications mesh tightly with each other; extensive functionalities have to be depicted. Tools and methods are used to handle technical issues of this growing complexity. Many organizational problems can be solved with the help of various established standards, which have different objectives and are suited for different phases of software development.
What are the advantages of standards?
- Those making use of standards don’t need to reinvent the wheel.
- Products and processes can be standardized.
- You can provide for consistent processes in all departments.
- Using standards regulates (and improves) communication, division of labor, exchangeability and responsibilities.
- When the allover system development process is standardized, new projects can be calculated on a better basis. Usually, standardized processes improve the quality of the system developed.
Which can be the disadvantages of standards?
- In many cases standards are fully adopted without any adjustments necessary to serve the company’s structures and the needs of the project.
- Well-functioning processes become inflexible when they are stipulated. In many cases the amount of documentation required leads to a deluge of paperwork.
- Often, management functions have to meet too high demands.
Here we present an overview of the most common standards, as well regarding standards for quality improvement as standardized process models.
International Standards
There are several internationally recognized and used standards which help to improve the quality of development processes and of artifacts created. These tried, tested and proven standards are in many cases compulsory prerequisites. Get to know some of them here.
Standard Process Models
Managing the complexity of development processes requires a sound plan. This plan, the process model, divides the development process into phases of limited content and defined periods of time. These phases represent steps of the development process for which standard process models provide very precise specifications.
Agility
With the introduction of increasingly precise process models, the persons involved are burdened with more and more regulations. Would you define this as progress in system engineering?
See “Agility” for a lot of introducing information.
Agile Process Models
In agile process models, threats and opportunities should be constantly considered. The activity chosen as next step is always the one that minimizes identified risks and takes existent opportunities in the most effective way. Here you will learn more on several agile process models.
Object Engineering
We SOPHISTs created an agile process model we call Object Engineering (OE). It describes a systematic way to elicit, document, test and manage requirements throughout their whole life cycle. Read a short introduction on our well proven process model.