The software process and Model:
Software process:
Objective:
The objective of this article is to know about the process of any software development in software engineering.so these are the basic steps to design and implement a software step by step. and these are also the steps of software model and development.
so,
The software process is a set of activities that lead to software development
Product activities can include software development from scratch Adding a standard programming language, such as Java or C, however, new software has been developed by expanding and modifying existing systems and configuring and integrating shelf software or system components. Integrating G&O shelf software or system components. This is a very complex but very creative process. Rely on decisions and people making decisions. Due to the need for judgment and creativity, efforts to automate the software process are limited.
Success. Computer-Aided Software Engineering (CASE) Tools (discussed in the article)
4.5) Can support some process activities. However, at least this is unlikely
Over the next few years, more widespread automation is where software takes a creative design from engineers involved in the process.
One of the reasons that the effectiveness of CASE tools is limited is enormous
Diversity of software processes. There is no ideal process and many organizations
Developed your own approach to software development. Is the process
Ready to exploit the capabilities of people in an organization and specific people
System features that are being developed. For some systems, e.g.
The critical system requires a very organized development process. For business
The system is likely to have a flexible, agile process, with faster requirements
Be more efficient.
Although there are many software processes, some basic activities are common to all software processes.
1. Software specification Software functionality and constraints
An operation description is required.
2. Software is required to accomplish the software design and implementation
Be prepared
3. Software Validation To verify that it works, the software must be verified
Customer wants
Software. The software evolution software should be ready to meet the changing customer
Needs
One of the reasons that the effectiveness of CASE tools is limited is enormous
Diversity of software processes. There is no ideal process, and many organizations
Developed your own approach to software development. Is the process
Ready to exploit the capabilities of people in an organization and specific people
System features that are being developed. For some systems, e.g.
The critical system requires a very organized development process. For business
The system is likely to have a flexible, agile process, with faster requirements
Be more efficient.
Although there are many software processes, some basic activities are common to all software processes.
1. Software specification Software functionality and constraints
An operation description is required.
2. Software is required to accomplish the software design and implementation
Be prepared
3. Software Validation To verify that it works, the software must be verified
Customer wants
4-Software. The software evolution software should be ready to meet the changing customer
Needs
New techniques of applying for the software process are here in this article practice. as in previous articles, now it will be explained in articles will be discussed the software process and its model will be explained.
Software process models:
Each process model of a software process reflects a particular process. The point of view, and thus provides only partial information about this process. in this; article, I introduce several general process models (sometimes called process models) and present them from an architectural point of view. That is, we View process framework but not specific activity details
These common models are not an exact description of the software process. Rather,
They are a summary of processes that can be used to explain different ways
For software development. You can think of them as a framework of action that could be
Extended Expanded and synchronized to create more specialized software engineering processes.
extended and adapted to create more specialized software engineering processes.
The process models I cover are:
1. Waterfall Pattern It takes the activities of the basic process of description, development, validation and evolution and represents them separately.
Process stages such as requirements specification, software design, implementation, testing, etc.
2. Evolutionary development This approach interrupts development, development and validation activities. An initial system is developed rapidly
Component-oriented software engineering This approach is entity-based
Of a remarkable number of reusable components. The process of system development
Focuses on integrating these components into the system rather than developing them
Them from the beginning.
These three common process models are widely used in current software engineering practice. They are not mutually exclusive and are often used together as well in the last article.
so for more knowledge, you can visit www.knowlwdgehu92.info