201671030110 Jiang Jiayu experiment fourteen project review team & course summary

operation link
Course work belongs Northwest Normal University Software Engineering
Work requirements Experimental fourteen project review team & course summary
Jobs goal Summarize learning experience

This semester course summary

  • Solve experimental software engineering to prepare a question raised by Task 5:

    One problem: the code easier to maintain for the reviewer, the code has reached a number of criteria reviewers think, or compile the code for the software is concerned, the code to achieve the most stringent compiler warning level or compiling software defined team after some of the requirements of the code can be considered that the code is easy to maintain it?
    Answer: After a semester studying software engineering knowledge and experience gained in software engineering practice, I think it is easier to maintain the code for the software or maintenance personnel are developers. And not a standard for compiling software, the software in the overall design, with strong poly + weak coupling design will make

    Second problem: the code review should be carried out in order to step in which the entire software development to achieve its purpose?
    Answer: After a semester studying software engineering knowledge and experience gained in software engineering practice, I think code review should be carried out to better play its role in the coding phase. This is because, for me, although we have agreed "code specifications manual", but still more or less problems after entering the coding phase of the project team and team members in the encoding process, such as logical confusion and so on, we Alpha will be in the final stage of the regular meeting of the code already written a review, we can solve many problems.

    Question three: What aspects of a software project can be mentioned with the Symphony Orchestra mode "are practiced repeatedly played the track, focusing on the implementation of" correspond?
    Answer: After a semester studying software engineering knowledge and experience gained in software engineering practice, I think the play is practiced many times the corresponding tracks in software engineering is a part of every software project: from requirements analysis the overall design to the detailed design to software testing to final acceptance of the project, these links are essential software engineering and has been repeated in other projects to achieve the encoding step.

  • Summary of the project feasibility analysis / requirement analysis / software design / implementation / testing / project acceptance / learned "knowledge":

    In the project's feasibility analysis phase: I understand that, if they want a product is not a figment of the imagination nor hotheaded impulsive but with reasonable scientific software engineering feasibility study ways to measure.

    In the project's requirements analysis phase: I learned the various needs of research methods. For example, in the team project, we focused on a class of users, Northwest Normal University textbook ordering system: the Senate had taken a teacher face to face interviews to use prototyping way to do software prototype, we want to get a good The data.
    In the project's software design phase: I learned to use different graphical tools to design depicts the software architecture software. You need to use such that overall block diagram level design software is: is used to depict the hierarchical structure of data. Detailed design required graphical tool used is a flowchart of: is used to express the algorithm. In addition, the software design, the independence of the module is also very important, the degree of independence of modules can be two kinds of metrics: cohesion and coupling. In general, strong cohesion + weak coupling conducive to the maintenance of software.

    In the project's Coding phase: I think strong coding ability is the best weapon to support the implementation phase, otherwise the final product will be a lifeless isolated city.

    In the project's test phase: I learned, software testing is used to find errors; good test solutions can be found wrong so far not been found; error successful test is to find so far not been found.

    In the project's project acceptance stage: I learned, when the acceptance of the project to be ready all the project documentation for review, and in accordance with the contract.

  • My experience of program / project team of personal experience in project / knot.

    In the individual programming phase and pair programming stage due to the knowledge beginner software engineering, in both stages I did not come to complete the project according to the software engineering approach, the only done once the document is the junction cooperation programming and teammates prepared "code specifications manual ", then for software engineering has not been particularly deep feelings, only to find a person or two to complete a project is a more difficult thing. Until the later phase of the project team, as I am PM team leader of the project is the first time we complete a project was completed according to the software engineering approach, although the final project completed only basic functionality due to technical limitations and capabilities, our software does not riparian good-looking interface. In phase I of the project team to understand each stage of software development as well as guidelines for their team members are clear and unambiguous. In addition, I also experienced the hardships of a PM, but the pay is worth it.

  • To upgrade my software engineering in the course of which:

    In software engineering, this course, I learned a lot about software development, after a semester of software engineering practice, I experienced every stage of software development have told me of follow-up research project has a clear role in the guidelines. Before this, I believe that software development is the most important coding to achieve, especially in the previous high-level practical lesson language, I think that as long as the encoding implements a project functionality and interface even developed a project, and but I learned to understand the development of software engineering project needs a feasibility analysis / needs analysis / software design / implementation / testing / project acceptance of these links, and the best way to complete the development team.

  • The statistics I have accumulated a 2000+ lines of code in the course of them.
  • I schedule tasks in software engineering practice:
operation time
experiment one 2h
The second experiment 20h
Third experiment 2h
Experiment 4 30h
Experiment 5 (team project) 5h
Experiments six (team project) 5h
Experiment 7 (team project) 5h
Experiments eight (team project) 5h
Experimental nine (team project) 5h
Experimental ten (team project) 5h
Experimental eleven, twelve (team project) 30h
Experimental thirteen (team project) 15h
Experimental fourteen 3h
  • The most impressive work is once: Pair programming is completed word frequency statistics software. Because of the way this job is the first collaboration between two people to complete, and the two coding capabilities are weak spent a long time at the coding stage to complete that night very late coming to completion, so far deep impression.
  • The statistics, time spent on software engineering practice: 75h, average weekly spend: 5h.

  • I learn and master the new language: JavaWeb new platform:. Tomcat.

  • A summary of the semester, the software engineering development tools, development methods and modeling methods I learn or use the following table:

    Software development tools, project management tools Software development methods Modeling software
    Eclipse MySQL TomCat GitHub blade Leangoo Kanban Object-oriented software reuse method Jackson prototyping method Level block diagram showing the structure of a database modeling Modeling
  • My suggestions to this course:

      I think this course uses practical way of doing experimental class project very well. For theoretical courses, I recommend teaching by example the way will have better teaching results in the form of flipping the classroom.

Guess you like

Origin www.cnblogs.com/SeattleCarrot/p/11111492.html