| project | content |
|---|---|
| This work belongs courses | 2016 Computer Science and Engineering Software Engineering (Northwest Normal University) |
| Where this requirement in the job | Experimental fourteen project review team & course summary |
| Course learning objectives | 1. Master software project review meeting process; 2. to review all the knowledge of the semester and comb; 3. to think again and try to answer by the present prior knowledge of what they have learned doubts. |
1, a task: the task to answer questions and clarify a proposed ways to solve the question, raised new problems in learning
1.1 connection task five blog
Experimental Software Engineering to prepare a
1.2 Task answer five questions
1, in Chapter III presents the ability of software engineers, I want to know how software engineers the ability of specific performance in the real world, highlighting how this "ability" in the interview, but this ability and prompt way and code quality enhance the way different?
A: Implementation and Application ① software engineering aspects like speed and algorithm performance capability not only just knock code, software engineers more capacity should be reflected in the analysis of a problem, and summary form a general-purpose solution. In the interview can analyze documents and detailed design documents given their previous written demand to develop a project.
② enhance the ability of this approach is to master communicate with people, to understand is the greatest manifestation of this ability other people think. So this ability to enhance and improve the code quality of the place is different is the embodiment of a humanistic society and the other is reflected in the continuous accumulation of experience.
Way to get the last knot writing on a variety of project documentation.
2, can be achieved by Java port and inheritance, and these ports and how should inherit the parent class design mentioned in the fourth chapter in the book and they work in?
A: is the parent class and the interface may be provided to form a virtual function code specifications, design time to consider their input, output, and data processing can be a way. Obtaining the experience of several joint development get.
3. Cooperation in multiplayer chapter in the book that is mentioned in the coordination team, how each person's strengths to the fullest, so as to achieve the best state of a software.
A: After the last convoy project, I get a little bit of experience of them. Harvest in this collaboration, of course, there are unpleasant. Everyone wants to do the most simple things, but every simple task with regard to so many, with much more troublesome thing. But this development has given me the experience of each person assigned to the task of fixing and asking them to complete on time and consider each person's strengths (its role is to make everyone's module will have a good quality guarantee) when scheduling tasks, but also consider the ease of the task, is more than a simple assignment, is less cumbersome distribution, in order to protect everyone's working hours are close to the same.
New problems arising 1.3
At the junction of development, I found that some people are particularly difficult to communicate, it is difficult to obtain accurate he needs for the project, there is no way to get more smoothly.
2, summed up his analysis / needs analysis / software design / implementation / testing / project acceptance / learned what "knowledge" in the feasibility of the project.
Software development process including feasibility analysis, needs analysis, outline design, detailed design, implementation, operation and maintenance of seven steps:
Feasibility Analysis: Feasibility analysis mainly on technical feasibility, economic viability, market feasibility analyzes three aspects to determine whether the need for further software development, to avoid unnecessary economic losses and time.
Requirements Analysis: needs analysis of the target system is mainly made complete, accurate, clear, specific system requirements to clarify what must be done.
Summary of design: the outline design is to design and select the best implementation, the system functions after decomposition software architecture and database design and test plans.
Detailed design: detailed design of the system is mainly a detailed description and specific design, facilitate the development of personnel in the development of late, it determines the quality of the final code.
Implementation: coding and testing collectively achieve, because the programming process to continue to be tested to ensure the normal development of software quality and software.
Operation and Maintenance: The software can be put into use after conducting internal and operational testing, then the software maintenance process used to ensure that the software has a very long service life.
Finally, on the way to develop my knowledge gained in fact, I think the most important thing is: a team of enthusiasm for a project development and cooperation is of decisive influence
3, curriculum ideas
3.1 Personal items:
In the individual event, I found that the development of more freedom, completely in accordance with their own ideas to knock code, the code bitter difficult to understand. I do not want to read the back of my own code. So I got the experience, vivre when knocked the code do not plan to, have their own code specification, and this specification to be most acceptable.
3.2 twinning projects:
In the convoy project, I can not integrate the code there had been an accident, and later on the project team to avoid a lot of trouble as a warning. To be good at communication, identify problems solved.
3.3 Project team:
From the Project Selection, needs analysis and document preparation, system design, detailed design, coding and testing of the project, personal experience and feelings of the process of a complete project, by writing a series of instructions, I learned about writing requirements analysis specification, detailed design description, like coding standard specification specification specification specification, learning use of tools, such as the use mockplus prototyping project using Visio modeling projects, also some very bald knock code (the number of the amount of code it is bald), in the course of a team project, the experience I get is a team must first have that attitude, timely stifle neglect the psychological particularly important because the psychological contagious, leading to lax a group. Second is fit, the end of a project or not totally fit a team. It is in everyone's attitude, that determines the quality of a project is completed.
4, sum up practical summary of the course and upgrade to bring you, including the following:
4.1 statistical software engineering practice, completed the code you how many rows;
I probably completed 8,000 lines of code.
4.2 You were how much time each homework software engineering practices?
| Software engineering work | Spend time / h |
|---|---|
| Experimental Software Engineering to prepare a | 2 |
| Software engineering experiment two individual events | 6 |
| Improvement of the peer review with three operations | 1.5 |
| Experiment 4 software engineering twinning projects | 5 |
| Experiment 5 software R & D team building | 1 |
| Experiments six team project topics | 2 |
| Experiment 7 team prototyping and development project | 2 |
| Experimental research and analysis needs eight prototype-based team projects | 2.5 |
| Experimental nine team project needs improvement and system design | 4 |
| Experimental ten project team to improve the system and detailed design | 5 |
| Well-designed experimental eleven project team and coding | 3 |
| If a software testing and test Alpha sprint | 7 |
| Beta test thirteen team sprint and project acceptance | 8 |
4.3 Which one job to make you the most impressive? why?
I was most impressed by a work team work is the experimental twelve 7: software testing and Alpha sprint, this experiment requires programming to complete the project, although the previous design have been doing, but due to lack of expertise, resulting in very slow progress in programming .
The cumulative number of hours spent on the practice of software engineering? The average number of hours per week spent?
Cumulative spending 50 hours, spend an average of three hours per week
4.4 You learn and master a new language, a new platform;
Language: Markdown, jsp, xml
platform: blog Garden, GitHub, China University of MOOC, Tomcat, the code cloud (China)
4.5 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 |
|---|---|---|
| GitHub, MyEclipse, MySQL, process on, blade, graphite document, mockplus | Object-oriented approach, Jackson method, rapid prototyping | Data flow diagrams, database modeling, object-oriented modeling |
5 What problems do you think the current curriculum, do you have any better suggestions.
In fact, I find it hard to accept just begun teaching this semester, the teacher, and later found that this is important is not what course to rote knowledge, but the knowledge learned will be applied to the project.
Hope in project selection the teacher can look into each person's ability to develop, and the development of language. And according to these groups and the teacher looked at you, everyone with different abilities tend to occur 1 = N phenomenon. Fortunately, we are lucky group does not appear the phenomenon. I hope the teachers are grouped by ability, and the ability to give different stages of the project, so the project can best play a role.