Experimental study concluded fourteen
| project | content |
|---|---|
| Software Engineering | Classroom teachers blog |
| Work requirements | Job link address |
| Course objectives | (1) master the software project will be assessed process; (2) to reflect summarize course content. |
First, the course content of the semester, compared to "a test preparation software engineering," the task 5 questions (you mentioned question blog link ), to try to answer questions and clarify how the discussion by learning / practice / clear of; whether learning creates new problems? If so, please ask.
Q1: Chapter VIII Requirements Analysis: Analyze the demand before to carry out the project, a variety of data acquisition path analysis in the end is what? The team gather their own? Or from the other team get in the way?
Demand analysis prior to carry out the project, a variety of data acquisition path analysis is to gather their own team. Collected by other means such as questionnaires and organize the data.
Q2: requirements analysis phase, the actual software development process, from requirements to design, how to ensure the completion of the task within the stipulated time?
First of all have small but efficient team, followed by the development of an optimal implementation, under the premise of repeated communications with customers, identify solutions. Communication between programmers and customers, collaboration, and results of the work as the basis of the original, but also that this common software. From the definition of the problem to a different encoding test in strict accordance with each stage of task execution, in a team effective cooperation, can guarantee to complete the task within the stipulated time.
Q3: In the actual project open method, each person on the team plays a vital role, but the level of the level everyone is different, how to allocate it reasonable?
According to the differences of each person different knowledge levels, should have discovered the advantages and disadvantages of each member of the body as much as possible, let the advantage of amplification, such as a foundation in terms of writing code and very loving, which determines the role in the team, but also such as some members are not good at writing code, but has a strong analytical skills, you can do analysts, as well as some members of the system is good at communicating with people, then you can do the pre-defined problems, work feasibility analysis of collected data, and organize documents. But also according to each person's personality, make a different division of labor, so that role in the team to play to the maximum.
Second, summed up his analysis / needs analysis / software design / implementation / testing / project acceptance / learned what "knowledge" in the feasibility of the project.
1, feasibility analysis: system project feasibility study include the following: technical feasibility, economic viability, feasibility and other aspects of the operating environment feasibility. In the analysis of the system, the need for a greatly compressed and simplified systems analysis and design, feasibility analysis is an important basis for determining whether this project.
2, needs analysis: through the use of on-site observation, interviews, questionnaires, meetings seminars, prototype evaluation, scene analysis, acquisition method to collect and organize data analysis and case requirements. Learning software UML drawing tools visio, personally felt the whole process of obtaining various needs survey methodology approach questionnaire study of the "software requirements specification" written format.
3, software design: heavy preliminary work system, spent a lot of time to find errors, review, correct, add the collaboration diagram and component diagram. Team members are very high with the degree, clear division of labor to complete the speed, quality also can be, although the entire course of the project there will be many unexpected problems, but through concerted efforts, and ultimately solve the problem. Division of the functional modules and functions required for the system to achieve the overall system to achieve clarity and understanding of the structure of the database tables. Upon completion of the preliminary research as well as with members conducted in-depth discussion and analysis, based on clear that the system should have the functionality, performance and interface, and on this basis the iteration, further completing the subsequent design and development projects.
4, implementation, testing: The testing of the system, errors are found in the existing inventory management system to ensure each module can correctly perform its intended function. Detection and exclusion subsystem (or system) or a corresponding structural errors program structure, so that all modules with the right, the overall performance and functional integrity.
5, project acceptance: When the system is complete presentation, the heart is very excited, when their results show, is the most stressful time, I hope the results of the efforts of the whole team to be sure, from feasibility analysis to final testing, One can imagine the hardships of the road, in the acceptance test is whether the whole team united as one, whether to fulfill their duties, each member of the team have learned what, if carefully complete the teacher assigned tasks.
Third, the combination of individual projects / junction personal experience of program / project team, talk about the experience.
Personal project: personal items, an error often occurs, the error because I lack of computer knowledge of the language, resulting in many not solve the problems in the encoding process, the use of the software aspect, not enough skilled, etc. These problems make develop a lot of mistakes.
The purpose of the program due to the limited capacity of two people in the late stages of coding, we only have access to large amounts of data be written, the code will also apply to the framework of the Internet to make changes when necessary, has reached realize their system functions: Pair Programming , after the code integration is emerging bug, after repeated modifications, reduce the error rate to the maximum extent.
Project team: Team project I learned a lot of lessons, software developers, designers lack the ability to make our biggest obstacle, do not pay attention to project quality. In code and database design time to devote very little work has always been more abstract, good requires constant research and refinement to the design, but we have to schedule, soon driven out. So in the future we must learn more knowledge in this area and strive to do better products.
After learning this semester software engineering, mastered a lot of knowledge about software design, and under the guidance of teachers, the development team belonging to "inventory management system."
Fourth, sum up practical summary of the course and upgrade to bring you, including the following:
1, statistical software engineering practice, how many lines of code you have completed the
About 200 lines
2, respectively, you spent much time in the second practice of software engineering job?
| task | Spend time |
|---|---|
| Software R & D team building | 3h |
| Determine team project and team name | 3h |
| Prototyping team projects | one week |
| Project needs research and analysis | one week |
| The project team needs to improve and detailed design | one week |
| Project design team and perfect coding | 5 days |
| Alpha sprint five days | 4 days |
| Beta sprint three days | 3 days |
2, which allows you to work once the most impressive? why?
Experiments six team Assignment 2: Project Selection team, team work experiment eleven 7: Team project design & coding perfect. These two operations, by identifying the topics, determine the division of labor cooperation and friendly relations of cooperation; each member of the second operation, the project team do every day into the night, not only a strong team of perseverance, but also tightly the spirit that unites us even more excited.
3, the total number of hours spent on the practice of software engineering? The average number of hours per week spent?
It took a total of 300 hours, an average of 13 hours per week
4, you learn and master a new language, a new platform?
Language acquisition: C #, java
platform to grasp: Students Mu class platform
5, complete the form below, summarizes a semester of study, software engineering development tools, development methods and modeling methods you learn or use of:
| Software development tools, project management tools | Software development methods | Modeling software |
|---|---|---|
| Microsoft Visual Studio 2017、GitHub | Prototype method, an object-oriented approach, structured approach | Object-oriented modeling, structural modeling |
Fifth, what are the problems you think the current curriculum, do you have any better suggestions.
No problem, the teacher in the classroom or with students very seriously strict, very seriously assistant coaching us to better study software engineering.