Summary of software development training
Through a few days of training, my individual has a more comprehensive understanding of the software development, but also learns not only the knowledge of software development, and there is a method of mature thinking, the overall grasp the problem. ability.
2. Summary of knowledge
2.1. Summary of training on the Analysis section
The following is the main points of the training content:
l The method of clarifying the demand is to analyze;
l Analysis means is OOA, Use Case;
l To clarify demand, you must communicate better and more fully communicate with our customers;
l Analysis is not necessary to have more special (exception analysis when re-constructing on existing systems);
l The work of the analysis is a problem domain. Although the content in some solutions needs to be discussed with the user, this part should be very small;
l The prototype and survey is very useful, allowing users to see interfaces and functions, but prototypes cannot be the final delivery system;
l In the beginning of the analysis, we must know those should be retained, which should be discarded (original demand);
l Use Cases has two forms, describes examples and text forms;
l Use Cases is simple and effective;
l The prototype and investigation are also effective, but will increase costs and will bring risks;
looa method is only useful when rebuilding the system, otherwise it will confuse the analysis and design, bringing the design to astray, and it is not easy to understand;
l Process type analysis (transliterated as a functional design, an analysis method before the OO method) is a cumbersome analysis method (more focused on solving problems, rather than definition and analysis issues) It is often caused a lot of analysis errors), and this analysis method can only be used when the system's input output is determined, and the system can be used as the main function of data. Because we have no rooms.
2.2. New Understanding
l Must adequately communicate with customers to do a good job;
l The means of analytical means, should be careful, depending on demand;
l Turpand the combination of several means, such as use cases prototypes;
l Analysis of the work should be moderate and excessive analysis will make the design mistaken, too little analysis will lack the design;
2.3. Important
The following perspectives have explained the analysis methods, as well as their advantages and insufficient, very important:
l Use Cases is simple and effective;
l The prototypes and investigations are effective, but will increase costs and bring risks;
looa method is not very effective;
l Process analysis is a method close to being eliminated, and it is not necessary to use it.
2.4. Harvest
The following is the harvest of some training:
l has a new understanding of Use Cases;
l Since the analysis must be moderate, we must experience this extent, choose a better balance point; the following is the harvest acquisition throughout the training process:
l As a member of the development team, we must have a good attitude to treat problems encountered in development, take every problem, actively communicate and communicate;
l Software development is a team-based activity, which is based on mutual collaboration and mutual trust;
l The status of software development team leaders is very important in development activities.
The following issues are not obviously mentioned in training, but I think it is important:
l How to discover the needs of the description from the user description, maybe this is the work you have to do, but it is not a thing that is easy to complete.
