| project | content |
|---|---|
| This work belongs courses | Software Engineering |
| Where this requirement in the job | Experimental fourteen project review team & course summary |
| Job learning objectives | (1) master the software project will be assessed process; (2) to reflect summarize course content. |
Start：
Part1. Project has been completed acceptance, approval opinion has turned over the table to see. Team blog
. Part2 personal study concluded:
Software engineering jobs first reading: the point I see
Prior to raise questions answered:
- Q1: After a series of I understand, bug is the bug, which at this stage can only represent a code error is encountered in the development of software, resulting in the user feeling good. The differences between software defects generated and user belongs to the level of communication, is the issue needs analysis and detailed analysis phase, I think it can not be attributed to the bug.
- Q2: Although the changes are not controllable, but the first step for software development: first of all, accurate positioning, followed no matter how changes in demand, are negotiable, seemingly uncontrollable, in fact, there is no problem completely offset, This requires long-term experience in the development and presentation of experiences at the beginning of the software for accurate positioning, only so many unimaginable without problems. It takes years of experience honing, it can be resolved.
- Q3: The new, innovative software design high indeed can bring a fresh feeling to the people, but can not say that something new will certainly suit the needs of users, our software development process, can not stand still, but not old version out of line. Be sure to progressive development and implementation imagination. Secondly For users, the new transaction is not necessarily completely popular, so it is still early requirements analysis phase, accurate positioning problems.
- Learning Path: The answer to these questions, if we must learn to read, then it is plain that there is no degree of support. I was reading in conjunction with the course of team practice, we understand these issues.
- Emerging issues: software development for all the work early, not necessarily all be considered in place, remove the uncontrollable factors, there must be other important factors are not taken into account. Hope can slowly discover in later studies.
In practice the knowledge learned:
Feasibility Analysis
Learned NABCD law
demand analysis
Discussion and analysis in teams, to figure out the target user and target user we need to provide the kind of experience
software design
Knives and other tools used in ink design prototyping
achieve
Learn a lot of language-related knowledge, as well as with the use of the environment
test
The black box testing method of proficiency in the use
Project Acceptance
Defense techniques and how Cangzhuo and the highlight of
Feelings and experiences:
The project team before the experiment began, I did not have any experience in the development. Team there are four people, including two more individuals do not understand anything. I first served as background development, it is really very difficult. For the effect of the project ultimately compromised, really sorry.
But in the course of the start of the experiment team, first of all I learned to write the blog, github management. Secondly, I can be "and how I was wrong okay," team leader, the team learned a lot of internal coordination method, the pressure is very large, learned knowledge is far greater than I imagined. At the beginning of the project, various problems have emerged, coding aspects considered a problem, writing various documents aspects occupy more than two-thirds of development time, need to be more carefully treated and processed. Really learned a lot of things.
Summary and enhance the practice:
(1): In software engineering practice, I probably finished 5000 + lines of code.
(2): each time a job in software engineering practices are spending schedule:
| experiment | Spend time |
| Experiment 1: Preparation Software Engineering | 3h |
| Experiment two: Software Engineering Individual Project | 5h |
| Experiment III: Improvement mutual evaluation operations | 2h |
| Experiment 4: Software engineering twinning projects | 5h |
| Experiment 5 Teamwork 1: set up software R & D team | 2h |
| Experiments six team Assignment 2: Project Selection Team | 1h |
| Experiment 7 Team Assignment 3: prototyping and development project team | 4h |
| Experiments eight Teamwork 4: demand research and analysis based on the prototype of the project team | 3h |
| Experimental nine Teamwork 5: Team project needs improvement and system design | 6h |
| Improved system design and detailed design of the project team: 6 experiment ten teamwork | 7h |
| Experimental eleven Teamwork 7: Team project design & coding perfect | 8h |
| Experimental twelve Teamwork 8: software testing and Alpha sprint | 5h |
| Experimental thirteen Teamwork 9: Beta team sprint and project acceptance | 4h |
- (3): once the job is the most profound: "Statistical analysis of the English text," Experiment 4 twinning project reports
The reason: many times compared to the experimental team, made me feel a deep software engineering is the twinning project. At that time in early April, the format of writing the blog is still unfamiliar, can not write a nice blog (even if even the format is very simple (chou) ...) and coding skills particularly weak, the teacher assigned to knot word frequency statistics project to achieve the English text , I really panicked .... I pair with the junior partner of the foundation is weak. So it will not only go to school, I remember that night in order to learn the development of small projects, we have learned four o'clock in the evening, yes, that is 4 points. This is who hold up ah, really feel super bald head ... but we withstood the pressure to achieve this small project, really happy, I feel particularly enriched! ! !
(4): It took a total of 100 hours on the practice of software engineering, spent an average of 10 hours per week. Manual smile :)
(5): I have to learn and master a new language, the new platform is: in the process of project development team, you can not say that the new language should be based on the Java language, we learned to build a framework and repair simple bug, new platform project can be run directly encapsulated into Tomcat 8.0, is no longer operational and deployment environment in the traditional inside eclipse.
(6): complete the form below, summarizes:
| Software development tools, project management tools | Software development methods | Modeling software |
| eclipse、Tomcat、mysql | Object-oriented development methodology | Object-Oriented Modeling |
- (7): other gains or upgrade: mainly within the group to harvest more of it, first gain a better relationship, project, for a substantial learning experience; followed by compression capability has been strengthened, deep get to the blog play park.