Experimental fourteen project review team & course summary
| project | content |
|---|---|
| This work belongs courses | [ Teachers blog home page link ] |
| Where this requirement in the job | [ Job link address ] |
| Job learning objectives | (1) master the software project review process will be (2) summarize the course content to reflect |
| github repository address link | [ GitHub repository link ] |
A. Of the semester course content, compared to "a test preparation software engineering," the task 5 your question (questions given blog links), try to answer the questions raised, and to clarify the discussion is how to learn / practice / make clear; whether learning creates new problems? If so, please ask.
1. How does the company develop a reasonable management measures for the project?
At first felt a rational process of project implementation management practices will be affected by business background, factors affecting the economic situation, social status, etc., after the adoption of a semester, a progressive approach to understand the project development process involved Some standard specification, design specifications. Through their own personal experience, truly understand how a project is whether, in the implementation process must follow certain norms, certain standards. The so-called norms and standards is an objective, scientific development of guidelines, it will not be affected by factors affecting the business and the project itself has.
CMII standard management measures can be divided into the initial level, management level, defined level, quantitative management level which several levels. Each project is basically to follow the true kind of level managed, if certain items of some unexpected failure occurs during the initial project team of your different treatment according to the severity of the fault. If the fault can not be eliminated in the beginning phase of the project happens, I want to give up the project team record examinations this implementation plan to seek another viable plan to ensure the smooth implementation of the project through the city. In the first project on the possibility of failure can not be eliminated will be small.
2. Open source software code in the end is good or not good open source?
As a contemporary computer science students, we learn a programming language has an inescapable responsibility, but due to time factors in all aspects of energy, we can not achieve the level of programming capability and expected. Sometimes homework or need to develop a system, if we can accurately find some functional code, which would improve the efficiency of software development, improve the quality of jobs. So in this case open source code for me it is good. Software engineering test mentioned in reuse, which also shows part of the open source code selection is good.
3. The book mentioned stress test, both on increasing load, one user to extend along the axis, the second is extended along the time axis, when it comes to the time axis extended to the program of the pressing process, many of the program "small" problem will be magnified, exposed, do not understand why there will be a memory / resource leaks?
After learning of the 80/20 original software testing, you can use their own ideas to answer this question. 80% of software defects are often 20% survival deep in the software space. This principle tells us that if you want to make software testing effectively, remember that often visit the high-risk multiple "lot." Where the possibility of software defects found will be much larger, the principle for software testers to improve test efficiency and defect discovery is of great significance, as memory / resource leaks. Software testing must have the expected results. No expected results of the test is unreasonable, software defect is the result derived out of the contrast. It is like there is no standard measure can not be the same, if we do not know or can not be sure in advance of the expected results, we can not necessarily understand test accuracy. It's easy to feel like the elephant in general, many testers are often with their own feelings to judge the occurrence of software defects, the result is often the paradoxical result of things as the right to judge.
Software testing is a need for "conscious" process, as a tester, failing to calm, holding scales and reduce errors.
II. Summarize their analysis / needs analysis / software design / implementation / testing / project acceptance / learned what "knowledge" in the feasibility of the project.
- A. Demand phases: requirements analysis is to understand the basis for a software development project, do a good job requirements analysis phase, so as to ensure the development of a project feasibility and market demand, after completion of the project in order to predict the market outlook is good or bad. To understand the needs of users, know what the user wants, we can understand what the requirements are resolved, that we can not solve, so as to ensure that the project development process smoothly.
B. software design phase: Please sort out mutual structure. Since then the next directional gradually refined. Understand graphical modeling methods used in the design process and some drawing table, and understand how to better select the graphic modeling.
- C. implementation phase: Barbara realized the importance of teamwork, the division of labor is the task of all, this project will increase the speed of implementation, the project will also feature Xu Oh achieve a more perfect home. In the realization of the process, using Github management code; learn and use existing methods to improve efficiency.
- D. testing phase: master some methods used in the testing phase, such as black box, white box, covering testing, integration testing, know the advantages and disadvantages of testing, but also realized the test put to use for important software sex.
E. acceptance phase project: Each project must undergo acceptance, when it comes to the acceptance of inspection personnel must be more experienced personnel, through inspection, the teacher will give us to help us find some unexpected problems, to give some reasonable lines the proposed measures.
III. Combined with personal items / junction personal experience of program / project team, talk about the experience.
When last did pick up the computer software industry work, still feel a modicum of success. When a soft-tasking write a blog from the first, to understand the assignments in this course will be a great job and the difficulty, when there is a state of mind just doing the task. In the first operation after the finish, he was assistant teacher pointed out some minor problems, the teachers and teaching assistants to communicate, think it is too hard to learn this course, this course for us, in employment among future It will bring us many benefits. So each had to do it seriously, doing his later get used to it, perhaps to get started. In twinning projects, to do the job is not too difficult, so the feeling is not very deep. The most difficult is the team project work, and in a team project I was responsible for the preparation and finishing some documentation to establish the connection to the database, and security connectivity and test the user login status of the post-test data, including writing code the whole process of my assignments is still relatively small. The whole process of system development, our team members work together in the process of writing code, due to our limited capacity, encountered many difficulties sometimes encountered a more difficult problem to write, and when the Internet to find information can not be resolved when we had complained, he had wanted to give up. But each time the encouragement and urging leader, we will come up again confident, calm down, discuss and solve problems. Throughout the process, we also spent a lot of time. However, when you see that they can develop a system, heart full of a sense of fulfillment and accomplishment spewing out. Greatest achievement is to understand the process of developing a project which needs to be done the preparatory work, only some of the necessary preparatory work well, the speed and quality of software development it may be higher and faster. I learned how to combine modules, a problem how to solve scientific and effective, and how to appreciate the importance of teamwork, but also deeply appreciate the importance of their responsibility to have a team. Thank each and every member of the team, also thanks to the teacher's hard work.
IV. Summarize the course of the practice of summary and bring you upgrade
Statistical software engineering practice, completed the code you how many rows;
大约完成了2000多行代码You were to spend much time in the second practice of software engineering job? (Make a list)
task Spend time (h) 1. Preparation Software Engineering 4 2. Personal Software Engineering Project 7 3. Improvement mutual evaluation operations 2 4. Software engineering twinning projects and peer assessment project 4 5. Software R & D team building 2 6. Project Selection Team 4 7. prototyping and development project team 18 8. prototype-based project team needs research and analysis 14 9. The project team needs improvement and system design 7 10. The improved system design and detailed design of the project team 10 11. The project design team to improve coding & 20 12. Software Testing and Alpha sprint 10 13.Beta team sprint and project acceptance 4 14. The project review team & classroom learning summary 4 Which one job to make you the most impressive? why?
在团对项目设计完善编码，这次作业给我的印象最深，实现阶段，由于要写代码，中途有很多代码我们都不能顺利地写出来，当时的自卑感充斥着整个大脑。但我们没有选择放弃，在组长的带领下，我们一步一步，不会的就同学或者在网上搜，最后通过我们的齐心协力，成功地写完了代码。The cumulative number of hours spent on the practice of software engineering? The average number of hours per week spent?
共110小时，平均每周6小时You learn and master a new language, a new platform;
新语言：Java语言 新平台：博客园、Github、eclipse等平台 新工具：leangoo，processon，visioComplete the form below, summarizes a semester of study, software engineering development tools, development methods and modeling methods you learn or use;
| Software development tools, project management tools | Software development methods | Modeling software |
|---|---|---|
| eclips,github,navicat | Prototyping, object-oriented development method | Object-Oriented Modeling |
Other aspects of harvesting or lifting.
1.认识到了团队合作的重要性，在一个项目开发过程中单靠一个人是不太可能实现的，人多力量大。 2.有效检索资料的能力
V. What problems do you think the current curriculum, do you have any better suggestions.
由于基础太薄弱，没有编程能力，一边又要学习语言，又要学习现有的课程，所以在时间和能力各方面都不太允许，建议老师在课堂上能够添加编程的讲解，这样可能会让学生有更大的进步。谢谢老师！