Shulou(Shulou.com)06/03 Report--

Software Lifecycle:

1. Problem definition: what problems do users need to solve?

2. Feasibility analysis: is the problem that users need to solve feasible (technical feasibility, market feasibility)?

3. Requirement analysis: refine the questions raised by users.

4. System design: determine the implementation method of the refinement problem:

5. Coding: develop stably according to requirements and design to solve problems

6. Testing: verify that the problems raised by users have been solved (unit testing: developers during development, integration testing: testing the overall process, functional use case testing: testing each refined function, performance testing: stress and stability testing using professional tools)

7. Maintenance:

Development model:

1. Waterfall model: each stage of development is executed sequentially, and each stage produces cyclic feedback. if there is a problem at a certain stage, you need the previous or earlier stage to troubleshoot and solve the problem. Suitable for projects with clear requirements and clear solutions, it is often used in some small projects.

2. Prototype model: refinement step by step, and the development phase is implemented around the prototype. It is suitable for unclear requirements in the early stage, and it is convenient to collect requirements by using prototype method.

3. Incremental model: it combines the basic components of the waterfall model and the iterative characteristics of the prototype implementation. the model uses a linear sequence that staggers with the progress of the schedule time, and each linear sequence produces a publishable "increment" of the software. Suitable for large-scale projects.

Requirements Analysis:

1. Demand research: the goal is to mine the needs of users. First of all, determine the target user, then determine the problem domain, and define a system to describe the problem, users put forward requirements in this problem area and system, including: functional requirements; quality requirements, user experience requirements and so on. Finally get a "demand survey report".

2. Requirement description: analyze, identify, synthesize and model the collected data through demand research, clear the fuzziness, ambiguity and inconsistency of user requirements, analyze the data requirements of the system, and establish a logical model for the original problem and target software. Finally get a "software requirements specification" and confirm with the user. Software developers need to design and code according to the Software requirements Specification. The software requirements specification includes: system overview, running environment, functional module diagram, functional use case, performance requirements, interface requirements, other requirements and so on.

3. Requirements review: the participants are mainly architects, technical managers, requirements analysts, designers and developers. The main audit contents are: whether the requirement specification conforms to the specification, whether the requirement description is clear and detailed,

Design:

1. Outline design: according to the description of software requirements, establish the overall structure of the target system and the relationship between modules (technical architecture, functional architecture); system network deployment structure; core business process; define the external interface of the system, the interface between modules; prepare summary design documents; summary design review

2. Detailed design: the main task of detailed design is to design the class interface (parameters, interface function), local data structure, physical data model, page prototype and so on.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.