software engineering

merehan
Сообщения: 57
Зарегистрирован: 15 ноя 2022, 02:42

software engineering

Сообщение merehan »

Software Engineering
Many IT professionals have put several scientific terms for software engineering, and one of these definitions is software engineering, which is a profession that is concerned with developing and creating high-quality software, taking into account the user's interests, needs and requirements at all levels , and it is generally concerned with analyzing software, its designs and how to build it. And working to verify them, and even manage them, and in order to do proper proper engineering, we must know the approach to engineering the software

Software engineering models
In order for the software engineer to do his job well, he must develop a development strategy, which includes the approach that will be followed, the general methods and tools, and the software engineering approach is chosen according to the nature of the project and its various applications, the methods and tools that it needs, the control mechanism and the effectiveness of performance that he will arrive at. And there are a lot of procedural models - the approach to software engineering -, I'll explain some of them.

Linear sequential model
Which is known as the routine life cycle, and this model is a linear sequential systematic approach to developing software. This model starts at the system level, and runs in succession from analysis to design, coding and testing, and this model is considered one of the oldest and most used models, but it has some disadvantages, including: The person must be aware of the software requirements; Therefore, it is difficult for the customer to completely clarify all his needs, the customer must be patient, so that there will be no available software version that is usable until late in the project life schedule.

The prototype
In this model, the customer is aware of a set of general objectives for the required software most, but he does not explain in detail other requirements such as external, internal, or processing process. Here, prototyping is a good method in this type of situation. Initial modeling: You start with getting the requirements, so the professional and the customer meet to clarify the overall general purposes of the software, inspect any known needs and requirements, and in this case a quick design is developed, and this design is what leads to building a preliminary modeling. The customer processes this prototype, and does so to determine the requirements for the software.

Advanced models
And because the software has evolved over time, the requirements that the customer need change due to the progress of the different software development, so the production of the software is on an unrealistic path. The cascade model was designed for direct development cases, meaning that this model expects that the whole system will be delivered after the completion of this cascade. The prototype was designed to help the client and developer understand and understand the requirements and needs, and was not designed to deliver the system once and for all.

And here, the natural programmatic rise was not observed in these two routine models of software engineering, these evolutionary models are considered to be iterative, as the software engineer works to develop complex versions of the software, and we mention from these models for example: the incremental model: which combines components of the linear cascading model Applied frequently, the incremental model creates a scripted sequence in a sequential form in the arrangement but as production time progresses, each linear sequence produces incremental software ready for delivery. The spiral model: It is divided into several branches, namely: Effective communication between the customer and the developer.

TRANSLATED FROM:
شركات تصميم
تصميمات جرافيك ديزاين
اعلانات جوجل المجانية

Ответить