| project | content |
|---|---|
| This work belongs courses | Teachers Home Links |
| Where this requirement in the job | Job link address |
| Course learning objectives | (1) master the software project review process will be (2) summarize the course content to reflect |
Task One:
Team project submitted Party Github repository fill in the acceptance of the views of acceptance comments table as follows:
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.
Job address link: https://www.cnblogs.com/nunw-qslhd/p/10507022.html
2. "Experimental Software Engineering to prepare a" mission five questions to answer, answer the following table:
| Answers Question 1 | Question 2 Answers | Question 3 Answers |
|---|---|---|
| If a new idea to join a team of personnel proposed, a certain degree of desirability, then other developers should then decide whether to take through communication, so that either creative or efficiency requires developers together to discuss the decision to give the best solution Method | When this issue, it should be clearly aware of the importance of the code management, so the project team coding implementation, should take advantage of the software's source code management tools coupled with the build system, in order to ensure a complex software in multiple roles, the cooperation of multiple teams, continue to maintain the integrity of the code | In the software project development team, from the beginning of a project, the project members should be a reasonable division of labor, their duties and their respective mandates |
3. summed up his analysis of the feasibility of the project / demand analysis / software design / implementation / testing / project acceptance / learned what "knowledge."
(1) feasibility analysis : project feasibility analysis is the most important part of a pre-development projects, according to the construction project background, necessity, feasibility and project product market analysis, product planning and project implementation of the project to analyze the progress of the project feasibility
(2) Requirements Analysis : developers by making a choice based on the needs of users, to meet the needs of users on the basis of realization of software, so the demand analysis both for users and developers are very important
(3) Software design : software design, including software design, design data, design and other aspects of the interface. From the software requirements specification, 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 program forming the software design of the specific design of the process and the count
(4) the implementation phase : detailed design specification through software system for encoding software to achieve, in the coding phase, the team at any time writing code to interact, collaborate, and must be standardized coding
(5) the testing phase : software testing is essential, must be tested by the software after the coding phase, to ensure the availability, accuracy and security of the software, but also to choose the appropriate test methods, such as white-box testing and Black box testing
(6) Acceptance Project : Project Acceptance representatives of the users, developers, and users must have a certain ability to communicate, to develop their own software fully demonstrated to the customer, for customers to understand their own software
4. The combination of personal project / twinning individual program / project team experience, to talk about the experience.
Through these projects, I realized that this class of software engineering plays a key role in project implementation, but also allows us to understand how the specific process a software development and software development. Specific experience as follows:
(1) programming skills
In the latter pair programming and design and implementation of the project team, we use the Java language development, as a developer, select a programming language is vital that we choose B / S framework, the JavaWeb language, after the initial software requirements analysis after the software system design, detailed design and database design these stages, we have access to relevant information, while learning to use programming languages and frameworks, on the other hand learning knowledge database, the front and rear contact each other, the team members to each other cooperation. During programming, also encountered a lot of problems, but also learned how to use a programming language to solve problems, but also appreciate the charm of the object-oriented software development programming language. With a programming language beautiful interface, functional user needs, so as to enhance my sense of achievement in programming, but also let me interest to enhance the programming.
(2) pair programming and project team cooperation
pair programming and project team members need mutual cooperation, teamwork team project is the most important part, as far as I feel, the most important is the division of labor and exchange. The same task, I deeply aware of the lack of a reasonable division of labor team may be slower than a strong programmer, a very likely scenario is that each member in the case of unclear division of labor, are not considered to be a task of its own things, the relative difficulty of the task of passing the buck, resulting in the progress of the stop. On the other hand, the result of the division of labor is done by a different person each part of the work, to the synthesis of the entire project, carried out between the team members must be fluent exchange, eliminating the possibility of misunderstanding, understand the ideas implemented in various parts of the module, to achieve successful docking . Just before and after the end of the dock, with the front-end or back-end, also we need to have a clearer understanding of each other's work, reaching grasp of the overall project, understand what they have to realize what to pay attention.
(3) to reflect
in the development process, the project team also encountered a lot of problems. First teamwork lack of experience, and take a lot of detours, the early division of labor is not very efficient, resulting in a very full schedule, programming later there is a problem, the team is still a lack of communication, resulting in a lot of errors, but the team found the problem in time, each other collaboration, timely communication, finally, was completed this project.
5. Summary practice summary of the course and upgrade to bring you, including the following:
(1) statistical software engineering practice, completed the code you how many rows?
A: In software engineering practice, I probably complete more than 5,000 lines of code.
(2) how much time you are in the practice of software engineering homework? (Make a list)
| Software Engineering jobs | Time (h) |
|---|---|
| Experimental Software Engineering to prepare a | 5h |
| Software engineering experiment two individual events | 4h |
| Improvement of the peer review with three operations | 2h |
| Experiment 4 software engineering twinning projects | 4h |
| "BUG to create a team" first job: team debut | 4h |
| "BUG to create a team" Second Team work: Team Project Selection Report | 4h |
| "BUG team to create the" third job: prototyping and development project team | 10h |
| "BUG to create a team" Fourth job: demand research and analysis based on the prototype of the project team | 7h |
| "BUG to create a team," the fifth job: project needs analysis and system design improvements | 5h |
| "BUG to create a team" Sixth job: project design team to improve the system and detailed design | 5h |
| "BUG to create a team," the eighth team work: Alpha sprint | 40h |
| "BUG to create a team," the ninth team work: Beta team sprint and project acceptance | 10h |
| Experimental fourteen project review team & course summary | 5h |
| The total time spent | 160 |
| The average time spent per week | 10 |
(3) Which one job to make you the most impressive? why?
A: The team project work impressed me the most profound, because the team project we first adopt MVC framework for B / S, the framework is relatively new, and special use, but in this project, we use this architecture is not easy.
(4) the cumulative number of hours spent on the practice of software engineering? The average number of hours per week spent?
A: On the practice of software engineering work this semester, I spent a total of 160 hours on the practice of software engineering, spent an average of 10 hours per week.
(5) you learn and master a new language, a new platform;
A: This semester I learned JavaWeb, how to write blog, as well as prototyping tools mockplus, blade, Github platform, process on, visio, questionnaires star, leangoo software park in blog
(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 |
|---|---|---|
| MyEclipse、sublime、Github | Object-oriented software development methods | Object-oriented analysis model, object-oriented design model |
6. What problems do you think the current curriculum, do you have any better suggestions.
A: Relatively speaking, this semester's software program I learned a lot of basic knowledge about project design and implementation, but more course assignments, lead us to spend a lot of time writing blog and writing on the document.