Teamwork - Design results summary

First, the team scores


 

grades ranking

 Second, the cumulative team score


Thousand sails compete chart

 

Total score table

Group No group name The first two Blog Outline design Database Design

detailed design

Respondent score

Scores
1

Mystery

174.3 21 14 14 14 27 264.3
2

Royal Macau programming team 

174.2 22 13
13 13 24
259.2
3

TEAM PANTHER 

166.4 21 14 13
12 24
250.4
4

Have become 

161.3 22
13
12
13 24
245.3
5

Machine you're so beautiful 

152.8 19 12 13 12 24
232.8
6

Six gold 

181.2 22 13
13
13 27
269.2
7

Three cobbler 

159.5 22 13 13 14 27
248.5
8

Dancing and singing rap programming 

145.4 18 13 13 11 27
227.4
9

Successful wonder 

191.8 23 14
13
14 30
285.8 
10

Software dream team

171.7 22 14 13
13 27
260.7

11

Tumescent 

1559

20

10

10

10

24

229.9

12

Make a million small projects 

158.7

19

13

12

13

24

239.7 

13

Flying Pig who 

167.4

20

13

11

13

24

248.4

14

Shanhai flat Jieke 

148.5

15

11

12

13

24

223.5

15

RTD 

174

22

13

12

12

24

257

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Third, the assessment criteria


 

(1) blog (25%)

(2) Write outline design specification (15%)

(3) database design specifications (15%)

(4) The detailed design specification (15%)

(5) reply: (30%)

Description:

(1) blog score consists of the following:

         1. Add the beginning of the job description format

         2. The list of student number of team members

         3. Summary of design: software architecture (described configuration diagram available) and the main service module description (input and output functions)

         4. Database Design: conceptual model and logical model

         5. The next phase of detailed work plan

         6. The next phase of the division of tasks

(2) the instructions to submit scores from the center of the course is based on the document

(3) the respondent achievement given case against the respondent for teachers

IV Summary


 According to the students summed up the defense case mainly where the following should be noted:

 (1) Software Architecture FIG care not to draw a flow chart to differentiate between the two.

 (2) is the main business module include business Login Register is not included.

 (3) how to arrange the progress of the team, to be detailed. Note that the first integration time, the time α and β test test.

 (4) no software configuration diagram of input and output modules after optimization.

 (5) Note that distinguish ER static relationship of FIG.

 


Guess you like

Origin www.cnblogs.com/moxxxmo/p/10926480.html