| project | content |
|---|---|
| This work belongs courses | Classroom teachers blog home page link |
| Where this requirement in the job | Job link address |
| Job learning objectives | (1) master the software project will be assessed process; (2) to reflect summarize course content. |
Task One:
Team project approval opinion --github address table
Task Two:
1. The course content of the semester, Contrasts "Experimental Software Engineering to prepare a" task 5 you mentioned (given questions blog link), to try to answer questions and clarify how the discussion by learning / practice / make clear; whether learning creates new problems? If so, please ask.
Experiment a first reading "of the law concerns to build"
Answers Question 1
In the process of learning this semester, realize that learning is a gradual process, we should give priority to the interest, keep trying, keep correct, constantly improving, Nothing is easy, and anything with patience, diligence exercises and stick to it will give you a satisfactory result; so in the future of software engineering in the learning process, I should have positive thinking, engage in active practice, learn to fight like this course.
Question 2 Answers
Through a semester of study, I believe that when the block a smaller scale, no need to write "unit testing" because the code length is small, and compile and run through our reading-based, will be able to find the problem and resolve, this time to write "unit tests "counterproductive; carrying out large-scale project team, we can write" unit testing ", quickly find the problem, achieve a multiplier effect; but" 100% code coverage does not equal 100% correct sex ", it just helped to the greatest extent we solve some problems, but some errors, such as semantic errors we need further changes and adjustments; due to the" unit testing "the code is written according to the specific program, so for writing code specific program of "unit testing" as well as realization of the principle, we need further understanding and learning;
Question 3 Answers
Through this "case", we realize that the "effectiveness analysis" as well as the importance of skills in the preparation of the code, on the basis of achieve the desired effect, we should call it time, operational efficiency and so on into consideration, so that the program will speed improved operating efficiency of the entire system will greatly improve
2. summed up his analysis of the feasibility of the project / needs analysis / software design / implementation / testing / project acceptance / learned what "knowledge."
Feasibility Analysis
Feasibility analysis is conducted in terms of technical, economic, engineering and other projects by the main content and related conditions, such as market demand, supply of resources, the scale of construction, process routes, equipment selection and environmental impact, financing, profitability, etc. research and comparative analysis, financial, economic and social and environmental impact after completion of the project may be made to predict, which made the project worth the investment and advice on how to build and provide a comprehensive basis for decision-making project systems analysis. Feasibility analysis should have predictability, fairness, reliability, scientific characteristics.
demand analysis
Requirements analysis, also known as software requirements analysis, system analysis needs analysis or requirements engineering, is a developer of an intensive research and analysis, an accurate understanding of the specific requirements of the user and project features, performance, reliability, etc., in the form of non-users demand expressed into a complete requirements definition, to determine what the system must do the process.
software design
Software design is the SRS from the description, the overall structure of the software system function design requirements identified during the analysis, the division of functional modules, and algorithm determines to write specific code for each module, the specific form of software design. The project team can use prototyping software to form the initial prototype of the software, and then on this basis making further design, the software design stage should also explicitly software system architecture and formed a relatively complete database logic design using Visio, Rational Rose, PowerDesign and other drawing tools to complete, and finally prepared in accordance with GB GB8567--88 "software system outline design specifications."
achieve
Realize that the software coding. Software coding refers to the conversion software is designed to be acceptable computer program, that is written in "source list" expressed in a programming language. To fully understand the software development languages, tools, features and programming style, and a choice of development tools help ensure the development of quality software products. At this stage the project team should be noted that before the program code to develop a unified, standards-compliant coding standards, so you can ensure readability, maintainability, improve the efficiency of the program.
test
The purpose of software testing is a smaller price discovery as many errors. At this stage can be carried out rigorous testing after the software design is complete, we found a software problem in the entire software design process and correct the problem. Throughout the test phase is divided into unit testing, assembly and testing, the test system in three stages. Two commonly used test method is the test object is white box source method, based on the internal logical structure of the program to discover software programming errors, configuration errors and data errors. The method is based on black box function of the software or software behavior Description, Discovery interfaces, functions and structure of the software error. Finally, write a complete test documentation.
Project Acceptance
After the project is acceptance testing of software development, users of the software product into the final quality inspection activities previously conducted practical application. Whether it is to answer the development of software products meet the requirements anticipated, and the question whether users can accept. Because it's not just test the quality of some aspects of the software, but to conduct a comprehensive quality testing, and software is qualified to decide, therefore acceptance testing is a rigorous formal testing activities. According to the plan in advance of the need to develop, review the configuration software, functional testing, performance testing and other aspects of testing. Project developers should provide a "needs analysis statement", "outline design specifications," "detailed design specification", "database design specifications," "test plan", "Test Report", "Program Maintenance Manual", "User Manual" "project summary report" and a series of documentation.
3. The combination of individual project / twinning individual program / project team experience, to talk about the experience.
Individual project experience
In the individual event, the teachers required to achieve a readable English text files into any program, summed up by the previous knowledge and access to information, independent of the final completion of this project design; then the teacher scheduled a job on peer assessment, peer assessment process in I found many shortcomings of their own projects, implementation and blog publishing and other projects by drawing on other students, their projects have also been a corresponding improvement and improve.
Pair programming experience
After the completion of the personal project, carried out two forces in the project, the twinning process, we first become familiar with each other's coding style and learning, through communication and exchange after completion of the initial project team knot
Team project experience
After completion of the two twinning, twinning had four projects, the project also increased the difficulty in pairing process, we help each other, we have problems to solve together, many times there will be disagreements and conflicts, etc., by communication and consultation, we finally reached a consensus and solutions, but also realized the importance of listening in communication and teamwork process.
4. Summary of Practice on the course and upgrade to bring you, including the following:
• Statistical software engineering practice, completed the code you how many rows;
About 3000 lines of code completed
• how much time you are in the homework software engineering practices? (Make a list)
| Soft-tasking | Spend time (h) |
|---|---|
| Experimental Software Engineering to prepare a | 2 |
| Software engineering experiment two individual events | 3 |
| Third experiment software engineering twinning project | 3 |
| Experiment 4 prototype based software needs access to | 3 |
| Experiment 5 software R & D team building | 2 |
| Experiments six teams and project review team project topics report | 3 |
| Experiment 7 prototyping and development project team teamwork 3- | 4 |
| Experiments eight Teamwork 4- demand research and analysis based on the prototype of the project team | 4 |
| Experimental nine Teamwork 5- team project needs improvement and system design | 4 |
| Improved system design and detailed design of the project team: 6 experiment ten teamwork | 5 |
| Experimental eleven Teamwork 7: Team project design & coding perfect | 4 |
| Experimental twelve Teamwork 8: software testing and Alpha sprint | 8 |
| Experimental thirteen Teamwork 9: Beta team sprint and project acceptance | 9 |
| Experimental fourteen project review team & course summary | 6 |
• Which one job to make you the most impressive? why?
Throughout the project development process, what impressed me most is the experimental thirteen teamwork 9: Beta team sprint and project acceptance, acceptance of each other in the team and assistant teacher acceptance process, our system is running out of a little bit of a failure, the captain under various modifications and commissioning was operating normally, the experimental results have also been other students and the teacher's assistant recognition, and ultimately the successful completion of the project team.
• cumulative number of hours spent on the practice of software engineering? The average number of hours per week spent?
It took a total of 60 hours on the practice of software engineering, spend an average of four hours a week.
• You learn and master a new language, a new platform;
Language: Java Web, android, JAVA
platform: blog Garden, GitHub, China MOOC University Network
• 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 |
|---|---|---|
| process on, blade, graphite document, mockplus | Prototype method, the object-oriented analysis (OOA), NABCD analysis, object-oriented design (OOD), black box testing | Object-oriented modeling, structural modeling method |
• Other aspects of harvesting or lifting.
In the individual events software engineering, project and team twinning project implementation process, my programming capabilities, document writing ability, logical analysis capabilities, mission planning skills, teamwork and others have a certain amount of upgrading and improvement.
5. What problems do you think the current curriculum, do you have any better suggestions.
In the experimental class , I think the amount of work still a little above normal, especially in the twinning project, will complete the last week writing system implementation and various documents, the time a little tight; in the classroom context, some concepts and knowledge we are difficult to understand, so I suggest that when teachers can speak some key knowledge example to illustrate this, let us easy to understand and remember. Other aspects, very conscientious teacher, will tell us a few things after practice that need attention and need to master basic skills, and finally thank you very much on behalf of the teachers inculcate this semester!