Experimental fourteen project review team & course summary
| project | content |
|---|---|
| This work belongs courses | Software Engineering |
| Where this requirement in the job | Experimental fourteen |
| Job learning objectives | 1) control engineering software coding to achieve the required 2) summarize the course content to reflect |
Task One: Click to view
Task Two:
Q1: course content of the semester, compared to "a test preparation software engineering" task 5 questions (you mentioned question blog link ), to try to answer questions and clarify how through learning / practice / discussion to figure out of; whether learning creates new problems? If so, please ask.
1. Software testing is divided into several stages? What is the purpose?
A: According to the development stage division, can be divided into software testing unit testing, integration testing, system testing and acceptance testing.
Unit testing: testing for each unit to ensure that each module can work as the goal.
Integration Testing: The module has been tested for assembly, integration testing. The purpose was to examine the structure and procedures related to software design problems.
Confirmation test: to test the developed software can meet all of last resort function and performance requirements. Some division method, the test will also be incorporated into the system to confirm the test.
System testing: testing software product can coordinate work with other parts of the system (for example, hardware, database and operating personnel).
Acceptance testing: testing the final steps of software product quality. The main highlight the role of the user, as well as software developers should also have a certain degree of participation.
Acceptance testing can be divided into Alpha testing and Beta testing, Alpha testing is done by the user in the development environment, Beta, is done by the user in the user environment test.
2. P52 page book mentioned, "" premature optimization software engineer, can not be too aggressive to solve all the dependency issues ", on weekdays when writing the code, a problem solved in time it will not take much in the final effort and expense on the improvement and optimization of code, small work> routing code like this, in a larger software project in the late are we going to pay more?
a: the optimization is never enough, looking ahead, any a room has its software can be optimized, one-time can not be the best, the opposite has been entangled in local optimization will only delay the overall progress, and even deeper, so we can first look at doing software> overall, only for local only to solve the basic problem, and then complete the overall stepwise refinement be good policy.
3.P27 page that "100% code coverage is not equivalent to 100% of correctness!", Then how we can achieve 100 percent correctness?
A: Through the study, I understand why "100% code coverage rate is not equal to 100% of correctness! ", 100% code coverage for programmers is not difficult, but it needs to be done 100d% correctness will be very difficult, tests are endless, just like we completed the project in> when the basic unit testing is not fully reached 100 percent, I think sometimes there is no need to fully achieve 100% code coverage, because the cost of covering some of the code area of more harm than good.
New issues:
Even if we have gone through enough testing, or can not ensure no mistakes in the actual operation, especially when developing object-oriented web site or software when using the object because diversity will encounter many problems. So there is no bug is more suitable than the norm patch method appears in the maintenance phase?
Q2: summed up his analysis / needs analysis / software design / implementation / testing / project acceptance / learned what "knowledge" in the feasibility of the project.
1. Feasibility Analysis:
The basic purpose of the feasibility analysis is to use the smallest cost to determine whether the problem can be solved in a short period of time may be near.
After passing through learning, I personally think that is the key to a feasibility analysis of the project, because no matter how good of a project, then do it if there is no availability, then there is no meaning and its value lies. So before the project, on behalf of the teacher for all of our team we conducted a comprehensive analysis and recommendations, the comments on our project was carried out.
2. Requirements Analysis: mission requirements analysis to determine how the system is not completed its work, but only to determine which systems work to be done, which is made complete on the target system, accurate, clear, specific requirements.
At this stage, before the teacher did not speak, I think it is a combination of user needs analysis based on the idea of their ideas were simple analysis on it, but after their lessons, I found that was not the case.
- At this stage I mainly learned
- Needs analysis with NABCD
- Writing standard "software requirements specification"
3. Software Design: Before no contact software engineering, I think the design stage with the implementation phase is the same, after the discovery still learned a great difference.
Software design phase of the mission is not specifically write programs, but the design of the program "blueprint" for future programmers will write the actual program code based on this "blueprint."
4. Implementation: implementation is specific coding stage, because before this is not a professional, so weak in the coding phase, however, through this project, I have made great progress in the coding phase, at the same time, I also learn, can not blindly> is to write code, but also to consider various factors, such as when the function realization: code specifications, redundancy and so on.
5. Test: the test phase basically consistent with imagination, a little different is that I thought it was a test is arbitrary, with the test piece of, piece of test, but the test specification is sub-modules, sub-test method.
6. Acceptance of the project: the project acceptance phase is to appear in front of all pay a showcase.
In short: whether in software engineering courses or in the project have learned a lot:
- It changed my superficial understanding of software engineering
- Solve my doubts before reading through software engineering
- The most important thing a deep understanding of software engineering
Q3: combined individual event / junction personal experience of program / project team, talk about the experience.
- And shortly into the period, the recall process this semester to participate in software projects, to find topics from the team began to compose project opening report, to set up the survey to determine the project user needs, identify pilot projects, the implementation of programs and look for innovation; and to develop Details of the research program and procedures; the project-related studies and research; personnel to finalize the feasibility of the project, a walking step by step, in which the experience and growth and only experienced and will share ownership. This is a rare experience, once I get experience of growing up exercise to get. During these months, the inter-group members learn from each other, which for every one of us is undoubtedly the most worthy collection of this struggle together for the same goal of unity atmosphere especially people a feeling of belonging. Special thanks to the guidance of teachers and teaching assistants for a long time and help!
- Through this project development, I deeply appreciate the great role of software engineering, software conceived from the initial to the present project realized after a long time, our team sincere cooperation to complete the project, we have made to each process part of a detailed analysis, from the initial vision to the current software coding to achieve through a long process, which took us a long time to do the design and modeling, the process may seem unimportant, but indeed software ultimate success laid the foundation, there is no pre-coding work behind will be a big problem. There is an old saying, quicken work. Early knowledge base, document storage, material preparation, preparation method can avoid rush, full preliminary experiments can make us confident. Step by step, in the final comprehensive experiments, we are benefited. He made a complete student information management, although the feature is not too perfect. But this is the crystallization of the efforts of the whole team together.
Q4: sum up the practical summary of the course and upgrade to bring you, including the following:
1. Statistical software engineering practice, how many lines of code you have completed the
A: completed approximately 1000 lines of code
each time the job 2. Soft labor practices are and how much time? The cumulative number of hours spent on the soft labor practice? The average number of hours per week spent? (Make a list)
| Soft-tasking | Spend time (h) | Cumulative spending time (h) | The average time spent per week (h) |
|---|---|---|---|
|
|
|
|
|
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
3. Which one job to make you the most impressive? why?
A: I was most impressed by a job are: Experiment 4 software engineering twinning project, in this project, first of all, is the lack of familiarity with the technology and not enough; secondly, it is not enough time; let me in this project in pay a lot, ultimately did not achieve their desired effect, however, in this twinning project is still a lot of harvest, so I cherish and nostalgia for the cooperation projects.
4. You learn and master a new language, a new platform?
A: The term is mainly controlled by the new blog platform Park, github, the new language of JAVA.
5. form below, summarizes a semester of study, software engineering development tools, development methods and modeling methods you learn or use
| Modeling software | Software development methods | Software development tools, project management tools |
|---|---|---|
| MySql，Sublime、eclipse |
|
|
6. What problems do you think the current curriculum, do you have any better suggestions.
A: Probably because of his foundation is weak, so the entire amount of work a semester feeling a little big, but the harvest is still a lot. About the course teacher has made it very clear, the rest is their own technical problems, and I will continue to learn late.