Software Engineering(Software LifeCycle)

 

Life Cycle Of Software engineering

 

1. Feasibility(타당성 조사)

-> Determining if the proposed development is worthwhile and if there is a potential market for the product.

ex) statement of work,market analysis report 
2. Requirement

-> Requirements are elicited from user and what the system should do and its development constraints are defined.

ex) requirement specification, Preliminary User Manual, Test plan. 

3. Project Planning Reqirement

-> This phase involves deciding what tasks need to be done, in what order to do the tasks, what resources are needed to accomplish the tasks, and software cost estimation.

ex) Software Quality Asuureanc Plan, Cost estimation, Project Plan, 

4. Design Phase

-> This phase converts the "what" of the requirements to the "how"of the design. This includes architectural design, interface design, and detailed design.

ex) Architectural&Interface Design, Module Specification, Detailed Design

5. Implementation Design

-> This phase covers issues related to making code. Programming style and coding guidelines are dealt with in this phase.

ex) Source code, Final User Manual(사용자와 시스템 간의 전반적인 내용 포함. 원활한 소통을 위한 도구), Documentation(코드 주석 및 문서화)
6. Testing

-> This phase involves issues on test cases, unit testing, system testing, and acceptance testing.

ex) Test Report, Defect Report

7. Maintenance Phase

-> This phase involves issues on updating and improving the software to ensure continued usefulness.

ex) Customer Service Request, Documents related to configuration manangement

 

 

Order of Waterfall model(feasibility, requirements, design, implementation, Testing)

1. market analysis

2. project planning, cost estimation, requirement specification(may be done concurrently)

3. requirements review

4. high-level design

5. low level design

6. design review

7. implementation

8. unit testing

9. systems testing

10. acceptanance testing(최종 사용자 요구 사항 충족 여부 판단)