Personal study concluded blog
| This work belongs courses | Software engineering teachers of |
| Where this requirement in the job | https://www.cnblogs.com/nwnu-daizh/p/11093584.html |
| Job learning objectives | (1) the completion of the project acceptance (2) to reflect summarize course content. |
1. "Experimental Software Engineering to prepare a" Address: https://www.cnblogs.com/runju/p/10508694.html
One problem: Through this practice involved in the project, but also the whole experience of being a difficult project development process and the problems encountered and solved, whether it is necessary for developers to understand the cultural background and development of software, I think this is necessary it can be easily later maintenance and testing, to further improve software quality, good software requirements analysis and software design documentation, software development process is very important and essential content.
Second problem: the fact that through this practice developed, feel as a senior development engineer, the most important is strict with themselves, sum up experience, not only have the most basic software development expertise, but also the courage to try, constantly improve themselves, definitely better pass the qualifying examination, but can not because the test would restrict our thinking, to continue to progress, live to old to learn.
Question three: code review on the issue, through the development, feel this is very necessary, because without it again has been very successful to complete the entire process of project development, software development, in fact, is a continuous repair, constantly looking bug the process, in strict accordance with the steps of software design step by step to complete, as long as such, will be one step closer to customer needs, will guarantee the quality of the software.
2. summed up his analysis of the feasibility of the project / needs analysis / software design / implementation / testing / project acceptance / learned what "knowledge."
About the design phase of the software, in fact, the ultimate question is to be the first to recognize the early demand for software analysis, the importance of a qualified software, good software analysis software is the first step to do, in the process the knowledge that the software design process design software, some structures, such as described in some of the design features of the system of FIG., the data flow diagram and the design drawing, FIG box, class diagram, like FIG system activity and system functions dESCRIPTION Figure designed to achieve in software, mainly coded design, development and implementation must be strictly in accordance with the program step by step software design. On software testing, in fact, he is constantly found a bug in the process, including the delineation of a number of test case design and some of the equivalence classes, followed by eight-profile white-box and black box testing, which should all be qualified as a development staff should have expertise. Finally the software acceptance process, including what should be a simple and understandable way to introduce their own developed software to allow customers to clear and understandable, there is identification of the contract, and he is really feeling a bit formal software acceptance process, benefit .
3. Personal experience
Truly recognize the importance of teamwork on a software development project, individual projects, it may determine a person's thinking on what you think of what to do, which means thinking there is a big limitation, but from the twinning programming a team project and then, realizing that a problem can also have a variety of solutions, people can expect to not think, for a lot of projects have space to play, to further ensure the quality of the software. Teamwork can improve the efficiency of development projects of good quality, each responsible for a module to improve the efficiency of project development, saving time. For individuals, so that my team had responsibility for their future integration into society has been greatly helped by the project practice, they would know a lot of good friends, with learning, thinking, friends, etc., not the same harvest.
4. Summary of the course and practice summary brings you upgrade:
(1) software engineering practice that he wrote about 2500 lines of code.
(2) how much time you are in the practice of software engineering homework
| experiment | Time (min) |
| Experimental fourteen project review team & course summary | 60min |
| Experimental thirteen Teamwork 9: Beta team sprint and project acceptance | 90min |
| Experimental twelve Teamwork 8: software testing and Alpha sprint | 60min |
| Experimental eleven Teamwork 7: Team project design & coding perfect | 200min |
| Improved system design and detailed design of the project team: 6 experiment ten teamwork | 60min |
| Experimental nine Teamwork 5- team project needs improvement and system design | 90min |
| Experiments eight Teamwork 4: demand research and analysis based on the prototype of the project team | 120min |
| Experiment 7 Team Assignment 3: prototyping and development project team | 40min |
| Experiments six team Assignment 2: Project Selection Team | 30min |
| Experiment 5 Teamwork 1: set up software R & D team </ td | 30min |
| Experiment 4 software engineering twinning projects | 60min |
| Improvement of the peer review with three operations | 40min |
| Software engineering experiment two individual events | 60min |
| Experimental Software Engineering to prepare a | 30min |
(3) integration project when it is difficult, we are the leader in each experiment the task arrangement, each person has their own module, has a different division of labor, the beginning of pairwise integration, followed by all integration, because of the different environment of each person's computer, and the contents of each module storage location, including some interface design, there is a big problem in the latter part of the integration, it takes a long time, it is more profound impact .
(4) Cumulative spending about 20 hours in software engineering, spent an average of five hours a week, late in code written when time gradually increased.
(5) in the project development process, but it re-acquainted with the java language, our main project is to write a java language, java prior knowledge of the language is too shallow, through this development, learned a lot about the java language knowledge, there are still a great harvest.
| Software development tools, project management tools | Software development methods | Modeling software |
| eclipse, Navicat (database visualization tool), GitHub, MySql | Object-oriented approach, the development of the prototype, the data structure for the | Object-Oriented |
5. What problems do you think the current curriculum, do you have any better suggestions.
Software Engineering This course is theoretical guidance for software development, which is a summary of experience in software development, I think everyone before carrying out software development practices must be read to grasp and understanding of the basics of software development technology theory, the theoretical basis for the foundation stone, we can further ensure the quality of software development. The main problem is that the software engineering process itself is a complex process, involving more knowledge, theoretical knowledge ones, boring and tedious, and most of the knowledge necessary to understand and master, which is gradually losing students the door of the interest, which is I think there is a problem.