Format Description
- : Which course of this work belongs to software engineering practice
- The operational requirements Where: Job Requirements
- Student Number: 221 600 435
- The objective job: software engineering practice summary
First, please look back to the beginning of the first job opening, you imagine for software engineering courses
(1) Comparison opening blog your course goals and expectations, "I hope that through practice and training, to enhance computer professional skills and employability and competitiveness", compared to the current learn and practice resulting in what up to your expectations and goals, What what are the weaknesses still exist, and why?
At the beginning of the practice of software engineering courses, I set myself the target of software development is the ability to take, in the course of this process, I slowly discover their ability to learn, so I learned during development of this game a lot of game development process and how to develop games, so I learned a lot.
We expect to achieve: learn to collaborate on the project. For game developers have a new understanding.
Shortcomings: professional knowledge is not solid.
(2) summarize the course of the practice of summary and upgrade to bring you, including the following:
- Statistics about you in the door that software engineering practice, how many lines of code is complete;
600 to 700 lines
- Each time a job working practices were soft spent much time? (Make a list)
| No. | operation | Time (h) |
|---|---|---|
| 1 | Personal job for the first time - to prepare papers | 1.5 |
| 2 | Pair job for the first time - prototyping (abstracts hot words statistics) | 13 |
| 3 | Pair job a second time - abstracts hot words statistics and advanced demand | 21 |
| 4 | Teamwork first - team show | 1 |
| 5 | Teamwork second - Project Selection Report | 10 |
| 6 | Teamwork third - Project prototyping | 12 |
| 7 | Teamwork fourth - the project needs analysis | 7 |
| 8 | Teamwork fifth - project system design and database design | 11 |
| 9 | Teamwork sixth - combat training team Github | 9 |
| 10 | Teamwork Seventh - Project Alpha sprint | 30 |
| 11 | Teamwork eighth - hindsight | 1 |
| 12 | Teamwork ninth - Project Beta sprint | 25 |
| 13 | Teamwork tenth -Beta peer assessment phase of the project team | 7 |
| 14 | The second private job - the job of software engineering practice summary | 2.5 |
| total | 151 |
- Which one job to make you the most impressive? why?
Project Alpha sprint, in a week's time to do a lot of things, feeling the pressure a bit big. - The cumulative number of hours spent on the soft labor practice? The average number of hours per week spent?
More than 150 hours, an average of 11 hours per week. Learn and use new software and tools:
Unity- To learn and master a new language, a new platform:
GitHub, C #, Unity - To learn and master new methods:
user research processes and methods. Other aspects of the upgrade:
compressive strength, learning ability, logical thinking ability
Second, write down their own Mythical Man-Month - analysis of lessons learned individuals or in pairs or team project practice examples + / illustration combined
Before the start of the project need to do a comprehensive needs analysis, this will be more purposeful in the development process, the more clearly what to do, you can improve efficiency.
When carrying out the task assigned code specifications need to be carefully planned, so you can rest a lot of time in the integration time.
The best you can and team members with the task of implementation, discuss with each other and thinking to achieve, the outcome of discussions tend to think it's better than a man.
Third, suggestions for the next practice, or for you at the beginning of the semester, freshman for you, for me the beginning of school, what do you want to suggest and inform it? For the later human expectations. In particular, in particular, the next not to change the way the players?
1. efforts to learn the knowledge, to lay the foundation.
2. completion of the task should be timely reporting, to facilitate the progress of planning.
3. study hard, every day.
Exchange views on the way players
Personal is not recommended to change the way the group. Because in my opinion, to complete a project in our current students stage is actually a rewarding thing. As for us certainly hope to participate in the single-mindedness of the original project development group.
Fourth, analyze yourself which team. Software engineering practice is rare serious university teamwork experience. Said the "Building of the law," there are several stages of the development team, the team you have experienced it, and finally to "create" stage yet? (Refer to "building law" in Chapter 17, performance and ethics)
Embryonic stage: Determine the topic of the project, to discuss the topic of rationality and implement technology it needs, and then discuss and ability to achieve goals.
Run-in phase: needs analysis, identify each player their own position, task assignment.
Specification phases: development projects based on location, every day in the group to report progress, the development process is more skilled.
Create stage: This stage requires team members to support each other, interdependent, roles and responsibilities can be naturally converted according to the requirements of the project, no one to worry or complain. But it does not seem to reach this level.
Fifth, how to prove you learn software engineering?
Before the project development process (mainly curriculum design) are all clear functional requirements, so the process of implementing useful purpose, and in the preparation process, and I just thought in mind, think of where where wrote. In the software engineering practice, I learned a complete software development process, including needs analysis, code planning, scheduling a series of processes. I learned a lot. There are all written blog can prove.