For software engineering this course, I think it is necessary, then a lot a lot of time and energy to study, to understand, to get to know. Just eleven big learning throughout the school year, I think I was just getting started, but I visit often and even software engineers who have a personal blog, when academic forums, I feel that they know nothing about this subject. Computer language equivalent of a new foreign language. It is illogical, unreasonable, and sometimes as a punctuation makes me a very tough battle ...... I speak English as my second language, but to learn the English language than ten years of barely passing. University Software Engineering is hard to imagine just four years of study after graduation will be to what extent.
Apart from that I do not understand what the system is, what language to talk about, just talk about my views on needs analysis and testing:
On the Importance of needs analysis. In fact, I learned last semester introductory course in software engineering, has in mind. A successful software is built, and effective communication and cooperation between high-quality demand sources with the user and the developer on the success of the needs analysis. But the user has a problem can be solved by a computer system, and developers began to help users solve the problem, communication begins.
Requirements elicitation is probably the most difficult, the most critical and most error-prone and most in need of communication activities. The demand for access often have the wrong understanding: for example, the user needs to know is what we have to do is talk to them, get demand from them, just ask the target characteristics of the user's system, what is to be done, what should be made like, so basically no need to worry about the.
Followed by the understanding of the problem. Lack of user capabilities and limitations of computer systems understand that any system will have a lot of users, or different types of users, each user only knows the system they need, but do not know the overall situation of the system. In other words, we have to do is as a party, to listen, to understand the requirements of the Party dads, and give reasonable and appropriate answers.
Just last semester we had a group of college students seeking jobs website, on demand in this first hurdle got stuck, causing the back of the process irrelevant, and finally almost complete.
Software testing it a little simpler. The software itself has no form, is highly complex knowledge-intensive logic products, which can not have the slightest error. Software implementation project must be accompanied by the process of software quality assurance activities, software testing is one of the main activities. In the software development process tracking, people use a lot of software quality assurance method of analysis, design and implementation of software. For large-scale, high complexity of software is even more so. In these errors, some fatal mistake, if not removed, would result in significant damage to property.
For the purpose of software testing is to "explain the program should be able to correctly perform the function", or "does not indicate that the program error"? Based on the different positions, there are two distinct testing purposes. From the user's point of view, the software's wish to expose hidden errors and defects in software testing, to consider whether to accept the product. And from the point of view of software development, we hope to be able to test the software product does not indicate that there is an error in the process, verify that the software has been implemented correctly to user needs, establish people's confidence in the quality of software. Therefore, they will choose the path that leads to test the probability of small effect, avoid those test cases had been exposed to bugs. At the same time, not to be detected, the program may be included in the discharge side. Obviously, such a test is worthless to improve and improve software quality. Because victims often there are many unexpected problems in the program, may be missing, many hidden bugs exposed only possible under certain circumstances. If you do not look for errors as putting the focus on such a basis, these hidden errors and defects will not check out, you will be left to go to the operational phase. If a user point of view, for they suspected, they should be aligned with the goal of testing activities expose errors present in the program. When selecting test cases, you should consider a program that has found errors in the data.
Talking on this blog is just the demand for software engineering analysis and testing, I was a very little knowledge about software engineering, so on a deeper