典型瀑布模型四個階段
The different phases that are included in the classical waterfall model are:
經典瀑布模型包含的不同階段是:
Feasibility study
可行性研究
Requirement analysis and specification
需求分析和規范
Design
設計
Coding and unit testing
編碼和單元測試
Integration and system testing
集成和系統測試
Maintenance
保養
Now, let us explain the different processes that are followed in each of these phases while the entire software development process.
現在,讓我們解釋整個軟件開發過程中每個階段所遵循的不同過程。
1)可行性研究 (1) Feasibility study)
In the feasibility study, we try to study the software in terms of technical and business aspects, to determine whether it would be beneficial for the company (or the organization) to build the particular software, whether the consumers will be satisfied through it or not and how much profit the software will be able to provide us.
在可行性研究中,我們嘗試從技術和業務方面進行研究,以確定對公司(或組織)而言,構建特定軟件是否有利,消費者是否會滿意它?以及該軟件能夠為我們提供多少利潤。
The feasibility study takes place as follows:
可行性研究如下:
A rough understanding of the project by the team leaders and heads from the client-side.
團隊負責人和客戶負責人對項目有一個大概的了解。
Analyzing every aspect of the client's views and reaching a state overall understanding of the project is made.
分析客戶觀點的各個方面,并達到對項目總體狀態的理解。
Picking up the best solution.
選擇最好的解決方案。
2)分析和規格 (2) Analysis and specification)
Here, all the requirements of the software are analyzed and documented properly. This is a very important phase because, in the classical waterfall model, each requirement must be documented in this phase itself because we cannot add or modify any of them in the later phases of development. This phase mainly involves two things:
在此,將對軟件的所有要求進行適當的分析和記錄。 這是非常重要的階段,因為在經典瀑布模型中,每個需求都必須在該階段本身中記錄下來,因為我們不能在開發的后期階段添加或修改其中的任何一個。 此階段主要涉及兩件事:
Requirements gathering
需求收集
Requirements specification
要求規范
3)設計 (3) Design)
In the design phase, a blueprint of the entire software is created. How the software must appear as a final product is decided in the designing phase itself. Hence, the design of the software gives an overview of the software to the developers so that they can work on that accordingly. This is done so that all the requirements are transformed into a structural manner which now makes it easier for the developers to implement.
在設計階段,將創建整個軟件的藍圖。 在最終設計階段,將決定軟件作為最終產品的外觀。 因此,軟件的設計向開發人員提供了軟件的概述,以便他們可以相應地進行工作。 這樣做是為了將所有需求轉換為結構化方式,這現在使開發人員更容易實現。
The designing team can follow different approaches like the traditional approach, the procedural approach, the object-oriented approach, etc.
設計團隊可以遵循不同的方法,例如傳統方法,過程方法,面向對象方法等。
4)編碼和單元測試 (4) Coding and unit testing)
In the coding phase, the developers code the program in any suitable programming language. While developing any feature of the software, the developers also have to test the feature on their level to check whether it is working fine or not. Therefore, the testing involved in this phase is termed as unit testing.
在編碼階段,開發人員可以使用任何合適的編程語言對程序進行編碼。 在開發該軟件的任何功能時,開發人員還必須在其級別上測試該功能,以檢查該功能是否正常運行。 因此,此階段涉及的測試稱為單元測試。
5)集成與系統測試 (5) Integration and system testing)
Different developers work on different subprograms. Now, all these subprograms need to be integrated to get our final software. Also, when the subprograms (or modules) are integrated, then they may function in a different manner which is not expected. SO, it is the job of the tester now to check the software for each functionality. There are three testing rounds that software must undergo before the deployment of the final software. They are:
不同的開發人員從事不同的子程序。 現在,所有這些子程序都需要集成以獲得最終軟件。 同樣,當子程序(或模塊)集成在一起時,它們可能會以不同的方式起作用,這是無法預期的。 因此,現在測試人員的工作就是檢查每種功能的軟件。 在部署最終軟件之前,軟件必須經過三輪測試。 他們是:
Alpha testing
阿爾法測試
Beta testing
Beta測試
Acceptance testing
驗收測試
6)保養 (6) Maintenance)
After the final testing, the software may require some maintenance before getting deployed. Even after getting deployed, there can occur certain problems that may occur in the software with the use. All these are also handled and maintained in the maintenance phase of the software lifecycle.
在最終測試之后,該軟件可能需要進行一些維護才能部署。 即使在部署之后,使用中的軟件也可能會出現某些問題。 所有這些都在軟件生命周期的維護階段進行處理和維護。
翻譯自: https://www.includehelp.com/basics/the-different-phases-of-the-classical-waterfall-model.aspx
典型瀑布模型四個階段