Shulou(Shulou.com)05/31 Report--

This article mainly introduces the relevant knowledge of what the java software development life cycle is, the content is detailed and easy to understand, the operation is simple and fast, and has a certain reference value. I believe you will gain something after reading this java software development life cycle article. Let's take a look at it.

Waterfall model

The waterfall model, also known as the life cycle method, is the most commonly used development model in the life cycle method. it divides the process of software development into six stages: software planning, requirement analysis, software design, program coding, software testing and operation and maintenance. it stipulates that they are in a fixed order from top to bottom and link up with each other, like waterfalls and falling step by step.

Software plan: mainly determine the development goal and feasibility of the software.

Requirements analysis: in the case of determining that the software development is feasible, the various functions that the software needs to achieve are analyzed in detail. The requirements analysis phase is a very important stage, which is done well and will lay a good foundation for the success of the whole software development project.

Software design: according to the results of requirement analysis, the whole software system is designed, such as system framework design, database design and so on. Software design is generally divided into overall design (summary design) and detailed design.

Program coding: converts the results of software design into program code that can be run by a computer. In order to ensure the readability and maintainability of the program and improve the running efficiency of the program, unified and standard writing norms must be established in the programming.

Software testing: after the completion of the software design, it is necessary to go through rigorous testing to find the problems existing in the whole design process and correct them. In the testing process, it is necessary to establish a detailed test plan and test strictly according to the test plan, in order to reduce the arbitrariness of the test.

Software maintenance: software maintenance is the longest lasting phase in the software life cycle. After the software development is completed and put into use, due to various reasons, the software can not continue to meet the requirements of users. In order to extend the service life of the software, it is necessary to maintain the software.

Transformation model

The transformation model (evolution model) is based on the rapid development of a prototype, according to the feedback and suggestions put forward by users in the process of calling the prototype, improve the prototype, obtain a new version of the prototype, and repeat this process until it evolves into the final software product.

Spiral model

The spiral model combines the waterfall model and the transformation model, which combines the advantages of both and increases the risk analysis. It is based on the prototype and rotates from the inside to the outside along the spiral. Each turn has to go through planning, risk analysis, implementation of engineering, customer evaluation and other activities, and develop a new version of the prototype. After several spirals, the final system is obtained.

Fountain model

The fountain model supports software reuse and the integration of multiple development activities in the life cycle, mainly supporting object-oriented development methods. the word "fountain" itself embodies the characteristics of iteration and non-gap. A part of the system is often repeated many times, and the related functions are added to the evolved system in each iteration. The so-called no gap means that there is no obvious boundary between analysis, design and coding in development activities.

V model

In the development model, testing is often used as an ex post facto behavior, but there is also a test-centered development model, which is the V model. V model is only vaguely recognized by the software industry. The V model claims that testing is not an ex post facto behavior, but a process that is as important as the development process.

The V model describes some different test levels and describes the different stages of the lifecycle corresponding to these levels. In the figure, what falls on the left is the stages of the development process, corresponding to the rising part on the right, that is, the stages of the testing process. Note that the naming of the test phase may vary from organization to organization. The value of the V model is that it clearly indicates the different levels that exist in the testing process and clearly describes the correspondence between these testing phases and the various stages of the development process:

The main purpose of unit testing is to deal with all kinds of errors that may exist in the coding process. For example, the user enters an error in the boundary value during the validation process.

The main purpose of integration testing is to solve the problems that may exist in the detailed design, especially to check the possible errors in the interface between each unit and other program parts.

The system test is mainly aimed at the outline design to check whether the system as a whole is effectively run. For example: whether the expected high performance is achieved in the product settings.

Acceptance tests are usually conducted by business experts or users to confirm that the product can really meet the business needs of the user.

Increment model

Incremental models, like prototype implementation models and other evolutionary methods, are iterative in nature. But unlike the prototype implementation, the incremental model emphasizes that each increment publishes an operable product. The early increments were "detachable" versions of the final product, but they did provide functionality for users and a platform for users to evaluate. The incremental model is characterized by the introduction of the concept of incremental package, which can be developed without waiting for all the requirements to come out, as long as the incremental package of a requirement comes out. Although an incremental package may need to further adapt to the needs of the customer and need to be changed, as long as the incremental package is small enough, the impact is acceptable for the entire project.

RAD model

Rapid Application Development (Rapid Application Development,RAD) model is an incremental software development process model, which emphasizes a very short development cycle. RAD model is a "high-speed" variant of waterfall model, which wins rapid development by using a large number of reusable components and adopting component-based construction method. If the requirements are well understood and the scope of the project is constrained, a fully functional "information system" can be quickly created by using this model. The process starts with business modeling, followed by data modeling, process modeling, application generation, testing, and iteration. The software process using the RAD model is shown in the figure.

The tasks to be accomplished in each activity phase of the RAD model are as follows.

Business modeling: what information drives the operation of business processes? What information do you want to generate? Who generated it? Where is the flow of information going? Who will handle it? It can be supplemented by a data flow graph.

Data modeling: in order to support the data flow of the business process, find the collection of data objects, define the attributes of data objects, and the relationship with other data objects constitute the data model, which can be supplemented by Emurr diagram.

Process modeling: make the data object complete each business function in the information flow. Create a process to describe the addition, modification, deletion, and lookup of data objects, that is, to refine the processing boxes in the data flow diagram.

Application generation: use the fourth generation language (4GL) to write processing programs, reuse existing components or create new reusable components, and use the tools provided by the environment to automatically generate and construct the whole application system.

Testing and delivery, due to a large number of reuse, generally only do overall testing, but the newly created artifacts still need to be tested.

Component-based model

Component (component) is a software unit with reusable value and relatively independent function. Component-based software development (Component Based Software Development,CBSD) model is a process of using modular method to modularize the whole system, and with the support of a certain component model, reuse one or more software components in the component library, and construct the application software system with high efficiency and high quality by means of combination. The component-based development model integrates many characteristics of the spiral model, which is evolutionary in nature, and the development process is iterative. The component-based development model consists of five stages: software requirement analysis and definition, architecture design, component library establishment, application software construction, testing and release.

Prototype method

The software prototype is the partial realization of the proposed new product. the main purpose of establishing the prototype is to solve the problem of demand uncertainty in the early stage of product development. its purpose is to identify and improve the requirements, explore design options, and develop into the final product. There are many ways to classify prototypes. According to whether the prototype realizes the function or not, the software prototype can be divided into horizontal prototype and vertical prototype. The horizontal prototype, also known as the behavior prototype, is used to explore some specific behaviors of the expected system and to refine the requirements. The horizontal prototype is usually only the navigation of the function, but it does not really implement the function. Horizontal prototypes are mainly used in interfaces. Vertical prototypes, also known as structured prototypes, implement part of the function. Vertical prototypes are mainly used in the implementation of complex algorithms.

XP method

XP is a lightweight (agile), efficient, low-risk, flexible, predictable, scientific and fun way of software development. Compared with other methodologies, the biggest difference is that:

Provide specific and continuous feedback earlier in a shorter cycle.

Plan iteratively, first quickly generate an overall plan at the beginning, and then develop it throughout the project development process.

Rely on automated testing programs to monitor development progress and catch defects early.

Rely on verbal communication, testing, and source program communication.

Advocate continuous evolutionary design.

Depends on close collaboration within the development team.

Try to strike a balance between the short-term interests of programmers and the long-term interests of the project.

RUP method

RUP (Rational Unified Process) is a unified software development process and a general process framework, which can cope with a wide variety of software systems, different application fields, different organizational types, different performance levels and different project sizes. RUP is component-based, which means that the software system developed with it is composed of components, which are related to each other through well-defined interfaces. When preparing all the blueprints of the software system, RUP uses the unified modeling language UML. Compared with other software processes, RUP has three remarkable characteristics: use case-driven, basic architecture-centric, iterative and incremental. The software process in RUP is divided into four sequential phases in time, namely, the initial phase, the refinement phase, the construction phase and the delivery phase. A technical review is scheduled at the end of each phase to determine whether the objectives of this phase have been met. If the result of the review is satisfactory, the project can be allowed to move on to the next phase.

This is the end of the article on "what is the java software development life cycle?" Thank you for reading! I believe you all have a certain understanding of the knowledge of "what is the java software development life cycle". If you want to learn more, you are welcome to follow the industry information channel.

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.