| project | content |
|---|---|
| Course work belongs | Owned courses |
| Work requirements | Work requirements |
| Course learning objectives | (1) master the software project will be assessed process; (2) summarizes the course content to reflect |
Task One: Team project review has been completed, the project acceptance process feedback form has been turned over.
Task two: course summary
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.
"Experimental Software Engineering to prepare a" blog link
One problem: through the semester to learn software engineering, software engineering is to understand a very interesting subject, after learning the software engineering, learning and life will first carry out a variety of analyzes, reducing a lot of mistakes. Software engineering is an engineering discipline, to teach us is thinking about how to get the problem solved and give specific solutions to problems, rather than the beginning were writing code.
Second problem: computer science and technology in the province contains the knowledge of software engineering. Software engineering is to learn every computer science students must do.
Question three: Through this project teams from design to completion and acceptance, I think the most important thing is to have a good team leader able to all team members at a certain time to organize exchanges and cooperation.
Question 4: In the field of computer software engineering development has a good future. Completion of software engineering, is really the equivalent of ability to have a life-long learning.
2. summed up his analysis of the feasibility of the project / needs analysis / software design / implementation / testing / project acceptance / learned what "knowledge."
| title | Learned "knowledge" |
|---|---|
| Project feasibility analysis | Learn to analyze the feasibility of the project NABCD law |
| Project needs analysis | Learned what type of project what kind of survey methods |
| software design | Learn how to build software prototypes early in the project |
| achieve | And re-learn software development methods needed for the project |
| test | How to use the black box testing, test their projects |
| Project Acceptance | Finishing acceptance of the document to be careful not miss any document |
3. The combination of individual project / twinning individual program / project team experience, to talk about the experience.
Experiences:
time flies very fast, blink of an eye this semester software engineering study is over, a personal training program during the study software engineering, programming junction project, the project team programming right. But also learned a lot of things, not only the ability to complete training alone in individual projects, the ability to think independently. And the most important thing is the team project from design to implementation, testing, and acceptance of the process learned a lot of ability, from the initial topics beginning, when I learned that each project will need to consider the feasibility of the project, study significance. In later also learned prototyping software that can communicate with users and adjustment after the completion of the prototype design-related functions of the project, of course, also gives us the late prototyping coding and testing is a big help. In the team project more of a need to reflect the ability of teamwork, not individual ability. While everyone on the team has their own task, I do not want any team member is not actively to complete their task. By the final project acceptance, once again remind ourselves, really weak in programming capability, a lot of room for improvement, but also need to work hard.
4. Summary of Practice on the course and upgrade to bring you, including the following:
(1) statistical software engineering practice, completed the code you how many rows;
In the study and practice of software engineering of the entire process is completed about 3000 lines of code it.
(2) how much time you are in the practice of software engineering homework? (Make a list)
| Experimental subject | time spent |
|---|---|
| Experiment 1: Preparation Software Engineering | 2h |
| Experiment two: Software Engineering Individual Project | 4h |
| Experiment III: Improvement mutual evaluation operations | 2h |
| Experiment 4: Software engineering twinning projects | 6h |
| Experiment 5: Team Job 1: set up software R & D team | 2h |
| Experiment Six: Team Assignment 2: Project Selection Team | 2h |
| Experiment 7: Teamwork 3: prototyping and development project team | 3h |
| Experiment Eight: Team Assignment 4: prototype-based research and analysis needs of the project team | 3h |
| Experimental nine: Teamwork 5: Team project needs improvement and system design | 4h |
| Experiment X: designed to improve the system and detailed design of the project team: 6 teamwork | 4h |
| Experiment XI: Team Assignment 7: Team project design & coding perfect | 4h |
| Experiment 12: Teamwork 8: software testing and Alpha sprint | 16h |
| Experimental thirteen: Teamwork 9: Beta team sprint and project acceptance | 8h |
| Experiment 14: Team Project Review & course summary | 4h |
(3) Which one job to make you the most impressive? why?
The most impressive work: Beta team sprint and project acceptance
The reason: Beta acceptance in the sprint and team work in this project I was very impressed. There may be a lot of our team in a variety of pre-made designs are not very detailed, team building early intend things to learn did not learn solid. It led become very difficult in this experiment. Originally intended to develop a good way to not take too, finally changed another way. Finally, within the team members are not particularly united, do web page is very general, a good multi-purpose can not be achieved. Finally, in cooperation with me and one other team members in turn the entire project was carried out most of the changes implemented function is not very comprehensive, very sorry.
(4) the cumulative number of hours spent on the practice of software engineering? The average number of hours per week spent?
Cumulative time in software engineering practice a lot, I do not know specifically how to count, sometimes really spent a lot of time, and no results. Especially in the latter part of the project team to implement and test. This basic software engineering course every week a new task. If all goes well at least 4-5 hours per week. (Not including time on theory, experiment course).
(5) you learn and master a new language, a new platform;
Software engineering project practice no new language to learn, but on the basis of the freshman sophomore learning and in-depth understanding and learning, compared to first learn JAVA, Dreamweaver CS6, etc., have made great progress. Learning class blog platform Park, Github, China University of MOOC
(6) complete 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 |
|---|---|---|
| eclipse, mysql, Dreamweaver CS6, etc. | Object-Oriented | Object-Oriented |
(7) or to enhance other aspects of the harvest.
Harvest a lot of, there are aspects of the project design capacity of learning software engineering, there is a team through cooperation projects, learn how to communicate with each other between the team members and coordinate with each other, help each other.
5. What problems do you think the current curriculum, do you have any better suggestions.
The current course is no problem, the teacher teaching methods used well, let us unprepared, very good. There is, I hope that in the experimental class after the teacher had finished the test requirements, allowing students to quickly enter this experiment.