Experimental eleven Teamwork 7: Team project design & coding perfect

Experimental eleven Teamwork 7 : team projects designed to improve & coding

Experimental time 2019-6-6


Deadline:

2019-6-12 10:00, the team submitted essays to the class blog Bowen of time shall prevail.

Grading:

  • Time delivery - scoring rules based on the experimental ten score (out of 100 points, the team blog)
  • Task 1 (30 minutes)
  • Task 2 (43 minutes)
  • Task 3 (27 minutes)
  • In this study, the task for the team, the team members to the team score Bowen performance-based
  • Night AC - 0
  • Plagiarism - Flip this assignment scores

1, experimental purposes and requirements

Master the engineering requirements of the software coding to achieve.

Second, the experimental environmental requirements

(1) Experiment nine project team compiled system design specifications;

(2) Experimental ten project team prepared detailed design specification;

(3) Common UML graphic drawing tools are:

  •  Visio, Rational Rose, PowerDesign, Visio recommend using lightweight.
  • Online mapping tools processon: https://www.processon.com/

(4) knowledge of burndown, refer to: https://yq.aliyun.com/articles/619571?from=groupmessage

Third, the experimental content and steps

Task 1 : Team-designed software projects:

According OOD detailed design requirements, revise and improve the team project system design specifications and detailed design specifications, content will improve with the "XX project software design team," published in the name of a team blog, and upload documents in a team project Github repository "software design specification." Stated in the technical design of the project team blog is a summary of how to embody the following principles:

  • abstract
  • Strong cohesion / weak coupling / Modular
  • Information hiding and encapsulation
  • Interface and implementation separation
  • Error handling cases
  • Program modules for the operating environment, the associated template, input and output parameters have any hypothesis?
  • For design flexibility to respond to change
  • Data processing capability of design
  • Software design reuse case
  • Design which uses heuristic rules?

Task 2 : Team Coding software project requirements are as follows:

  1. Set up and configure the project Integrated Development Environment;
  2. Within the group members to consult together to develop a team project coding standard, and the project team Github repository upload a document "software coding standard specification";
  3. According to the software design specification requirements, select the computer language collaborative writing software code, software development association database creation program, make the necessary code testing;
  4. Uploaded this week to complete the project to a team project source code repository Github.

Task 3 : Published in Bowen team blog, with burndown statement execution process of the experiment, the team implemented a scene photos uploaded this work, describe the division of team members, the total proportion of job tasks and do the actual work of their respective mandates time, combined with the division of tasks each member of this experiment are summarized experiences, and finally summarized statement by the project leader.

Team blog format meets the following requirements

Essay Bowen team name: "XXX team" Seventh job: team projects designed to improve & coding (2 points)

Text of the job at the beginning of the format: (3 min)

project

content

This work belongs courses

<Classroom teachers blog Home Links>

Where this requirement in the job

<Job link address>

Team Name

<Fill in team name>

Job learning objectives

<Fill specific objectives>

Essay Bowen body content include:

  1. Github project team warehouse address link; (2 points)
  2. Github repository upload "Software Design Manual" (10 points)
  3. Press 1 project summary task how to embody the technical design software design criteria; (20 points)
  4. Warehouse Github Upload "software coding standard specification"; (10 minutes)
  5. Github repository upload source projects have been completed; (33 points)
  6. Task 3 is completed according to the requirements of this work are summarized. (20 points)

 

Guess you like

Origin www.cnblogs.com/nwnu-daizh/p/10980707.html