| project | content |
|---|---|
| Course Title | 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 the software project will be assessed process; (2) summarizes the course content to reflect |
A test
of the semester course content, 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.
Q1: In the absence of contact with this course, very vague on software engineering, computer science though, but simply programming. Read "Construction of Law" after 70 for book style specification code, just prior to the result object. These specifications on the books, although understand that such a reason, but do not know how specification. I do not know the way.
Answer for Q1: coding style specification includes profiles for the name of the interface class and the like, as well as representation variables such as you are within a predetermined set of variables described in English together with the specific role underlined, etc., or every predetermined between operators must have a space, forming the code need to develop specific style, easy to merge code.
Q2: Second it is, on page 101 of the book for the bureaucratic model, since Finally, this model because selfish people, it is easy to have an impact on the whole project, but why, there is little reason to ask this question it?
For Q2 answer: because the bureaucratic model would have a negative effect works so to raise this issue, avoid excessive interference layman experts have negative effects.
Q3: Software Engineering in the end what real use in the computer industry it What is the role? Very broad concept, but specifically ask you, can do it in the end, it is difficult to answer.
For Q3 answer: On the engineering method is to guide the project guidelines, although extensive, but do any of the software companies must follow certain soft work process to get results.
The second experiment
summed up his analysis / needs analysis / software design / implementation / testing / project acceptance / learned what "knowledge" in the feasibility of the project.
• 1, feasibility analysis
using NABCD primary method of team project feasibility analysis, with minimal cost to determine the problem in the shortest possible time if you can solve, whether it is worthwhile to resolve.
• 2, needs analysis
using Visio UML graphic drawing tools to draw a use case diagram, communicate and share with the people; the questionnaire analyzing the needs of users. The ultimate goal of a project developed to allow users to use, it is necessary to clearly understand the real needs of users, such as user needs features, interface, and so want to see. Needs analysis a fly can reduce project development time and improve the efficiency of project development.
• 3, outline design
outline design is to design and select the best implementation, the system functions after decomposition software architecture and database design and test plans.
• 4, the 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, determines the quality of the final code.
Third experiment
combined with personal items / junction personal experience of program / project team, talk about the experience.
Through the implementation of individual projects, I am deeply aware of their relevant expertise is not enough to master, but also found a lack of learning and practice. Software engineering requirements analysis is insufficient, inappropriate these are the need to improve and after learning the software development process, various documents prepared by the ability of software development also need to upgrade, conscientiously sum up and improve in the future learning and practice, reference others software projects, software engineering experience excellent idea. In the time to do anything I must have felt standing on the shoulders of giants, rather than repeating the idea to do things the production of wheels. Overall, this personal project I got a better understanding of the software development, learned a lot. This semester, the teacher asked to continue to cooperate in small groups to develop a software, software development methods and studying the process side of the theoretical knowledge and practical combination, I began to have the software engineering shallow understanding. I think the greatest achievement is to know the difference between the outline design and detailed design, documentation needs to know how to write, why do you write, write and why. Of course, it changed my thoughts on software development inherent in the software development process is not just coding and testing, design part is more important, if there is a good software design, then it should be relatively easy to develop, programming It will be more clear, even if the software developed by another big.
Experiment 4
Summing up the course of the practice of summary and bring you upgrade.
• 1, statistics software engineering practice, completed the code you how many rows;
in the practice of software engineering, about the completion of more than 3,000 lines of code.
• 2, respectively, you spent much time in the second practice of software engineering job? (Make a list)
| task | Spend time (h) |
|---|---|
| Experimental Software Engineering to prepare a | 4h |
| Software engineering experiment two individual events | 15h |
| Improvement of the peer review with three operations | 12h |
| Experiment 4 software engineering twinning projects | 8h |
| Experiment 5 Preparation Software Engineering | 5h |
| Experiments six team project topics | 7h |
| Experiment 7 team prototyping and development project | 6h |
| Experimental research and analysis needs eight prototype-based team projects | 15h |
| Experimental nine team project needs improvement and system design | 20h |
| Experimental ten project team system design and detailed design | 18h |
| Experimental eleven team project designed to improve coding & | 30h |
| If a software testing and test Alpha sprint | 15h |
| Beta test thirteen team sprint and project acceptance | 10h |
| Experimental fourteen project review team & course summary | 5h |
• 3, which allows you to work once the most impressive? why?
In the Beta team sprint and project acceptance of this job I was very impressed. There may be a lot of our team in a variety of pre-made designs are not very detailed, team building early intend things to learn did not learn solid. It led become very difficult in this experiment. Originally intended to develop a good way to not take too, finally changed another way. Finally, within the team members are not particularly united, do web page is very general, a good multi-purpose can not be achieved. Finally, in cooperation with me and one other team members in turn the entire project was carried out most of the changes implemented function is not very comprehensive, very sorry.
• 4, the cumulative number of hours spent on the practice of software engineering? The average number of hours per week spent?
Lost and Found SDI system from the initial to the end of the acceptance, the cumulative total cost of 300 hours, an average of 13 hours per week.
• 5, you learn and master a new language, a new platform;
written in the Java language level has improved; skilled some of the basic grammar and writing method HTML page; MySQL database.
The new platform: blog Garden, Markdown, GitHub, panels, rain classroom, using the blade, UML use case diagram drawn, as well as burndown production.
• 6, complete the form below, summarizes a semester of study, software engineering development tools, development methods and modeling methods you learn or use;
language: Java Web, Java
Platform: blog Garden, GitHub, China University of MOOC
• 7, or to enhance other aspects of the harvest.
(1) learn to blog and how to develop rigorous complete software projects, documentation and code writing ability has improved.
(2) to improve their ability to analyze and solve problems, but also recognizes the need to correct some shortcomings of their own.
(3) through the knot to complete the project and project team, recognizing the importance of teamwork.
Experiment 5
What do you think the current problems of course, do you have any better suggestions.
In practice this part, avoids the tedious nature of software engineering this course itself. To practice to consolidate. I think the flipped classroom teaching methods teacher, very strange, however, a little to adapt, however, may need a certain transition period, the new teaching methods necessarily suitable for us, me personally, I do not think our class efficiency high.