The fourth team work - project system design and database design
Foreword
In the requirements analysis operations, it is well documented user scenarios project, functional description, and beautifully drawn prototype, and develop a detailed validation and acceptance criteria;
but we are still stuck in the product design point of view, rather than a development standpoint ;
the purpose of this work is followed by the last results of the project design landing, before the development of good design and database systems, to develop a good plan and division of labor;
quicken the work, I hope you pay attention to this assignment, as Alpha team next sprint work to prepare in advance;
did not talk much, followed by operational requirements;
Work requirements
① 1 blog post essays, published in the blog team blog, the blog title is set to - "XXX (team name) project system design and database design", and submit the job
, "System Design Manual" ② 1 part (pdf file);
③ 1 part "database design manual" (PDF file);
④. 1 part "reply the PPT" (class site assessment);
⑤. 1 parts online review form, scoring entry comprising at least: the PPT quality, system, database, presentation, the presence of questions and suggestions are part
⑥ establish github team warehouse , the "system design manual" "database design specifications," "reply PPT" and other team documents submitted to the team warehouse;
⑦ site assessment requirements:
a) in a timely manner for the other team scoring;
b ) score requirements: respect for his group, scoring serious, pragmatic, adopt a standard for all groups, scores can truly reflect consensus report quality and other groups of this group, a pot where prohibited end flat ;
Blog essay requirements:
Expected development plan schedule 1) team project (specific to a week ), with clear milestones, there must be a corresponding output; (15 ') (in mid-April - early June plans for the project sprint stage development plan Rang arrangement including at least this time);
the expected development plan arrangements for the division 2) team project (specific to each individual's role, responsible for the development section); (15 ')
3) gives the architecture design + functional module hierarchy diagram design class diagram, ER + analysis table structure design, system security and permission design, and a brief description; (30 ')
4) analysis of the problem needs to answer the last job teacher assistants and other teams in the table to review the project proposed or ideas to solve the problem; (20 ')
5) described as a complete workflow of this assignment, the division members, members contribution ratio; (15') (scores will be used to group individual scores mapping, together discussion, the proportion of proper arrangements);
6) provide team github repository link at the end of the essay, the blog pdf download link (can be any downloadable link cloud disk, such as playing blue cloud / Baidu Cloud / micro cloud). (5 ')
Documentation Requirements:
1) Refer to "System Design Manual", "Database Design Manual" GB specification text, write the corresponding software design projects. (System design specifications and database design specifications to find on the web)
2) In addition to formally meet the requirements specification text, the entire content of the project must revolve around the essence of the project to be developed to ensure that try to be clear and complete and accurate.
3) using a hierarchical fashion described, with the further "layer", the contents of the specific details described.
4) using the same graphic symbols and text description.
5) All abbreviations shall be defined in advance.
6) Format : typography norms beautiful, illustrated, throughout the document there is a uniform style style, pay attention to the font and line spacing, etc.
7) put themselves in the position of the reader - if the software project is not familiar with the technical staff, by reading this document, the ability to fully understand how the software is designed.
8) Teamwork (ask everyone within the team are required to make the appropriate commit).
9) document review rules: Introduction (5 '), architectural design + functional block level diagram (20'), the design class diagram (10 '), ER Analysis + tables design (20'), the system security and permissions design ( 20 '), the document graphics, text, style uniform and compliant (15')
PPT requirements
1) "System Design Manual" "database design specifications," the main content;
2) the expected development team project planned schedule, the division is expected to develop plans to arrange a team project;
3) previous demand analysis to answer job other teams in the review form questions to the project proposed or ideas to solve the problem;
4) description of the operation of the workflow, the division members, members contribution ratio;
Defense requirements
1) speech should grasp the key points, well ahead of commissioning equipment;
2) time control in 10 minutes (8 minutes presentation + 2 minutes to reply);
Grading
1) Score reply (consistent with previous scoring rules) Rate = sum of the other groups / (total number of groups -1) 0.25+ sum score ta / (ta number) 0.35+ teacher grades sum / (number of teachers) 0.40
2) TA Rating (blog 30%, 35% of system design specifications, design specifications database 35%)
3) the work team score = reply mutual evaluation score of 40% + 60% * TA Rating
Tutorial
1) UML class diagram the https://www.cnblogs.com/LangZXG/p/6208716.html
2) the UML class diagram Detailed https://blog.csdn.net/loumoxiaozi/article/details/81036408
. 3) Detailed Design mode six principles https://www.cnblogs.com/toutou/p/4870926.html
. 4) several design criteria database table structure https://www.cnblogs.com/wyq178/p/8549715.html
. 5) database table design (one to many, many to many) https://blog.csdn.net/fighteryang/article/details/82848505
6) common web attacks and defenses summary https://blog.csdn.net/qappleh / Article This article was / Details / 80,485,197
. 7) the user password encryption https://blog.csdn.net/weixin_34221073/article/details/89652071
. 8) separating the front and rear ends project JavaWeb https://www.cnblogs.com/donggedada/p/11377062 .html
9) RBAC users, roles, permissions, set design https://blog.csdn.net/ljw499356212/article/details/81055141
More Tutorials: https://www.cnblogs.com/hengyumo/p/12217218.html (welcome contribution, provided in the tail of the job do you think can be a good tutorial included)
Rules & Format
1, in order to facilitate other school teachers or teaching assistants understand the course of live, please add at the beginning of the job description :( format will do)
| This work belongs courses | <Class link> |
|---|---|
| Where the job requires | <Link job requirements> |
| The target job | <Write on specific aspects> |
| Pair Student ID | <Knot student number two on the students write> |
| Text of the job | .... |
| Other references | ... |
markdown Code
|这个作业属于哪个课程|<班级的链接>|
|-- |-- |
|这个作业要求在哪里|<作业要求的链接>|
|结对学号 |<写上两个结对同学的学号>|
|这个作业的目标|<写上具体方面>|
|作业正文|.... |
|其他参考文献|... |
2, submission rules
- Before delivery deadline, to give the actual score * 100%;
- Pay: Submit treated as pay within the deadline two days later, was the actual score * 50%;
- The lack of pay: in two days after the deadline to pay is not considered to lack of blog post with a score of 0;
(Forget to submit jobs and pay deduction agreement)
3, scoring rules
Reference 100 points per job, the job is scaled according to the actual scores have difficulty job,
such as:
对同一次作业，统计得分时为满分100分，换算权重为25%
小李此次作业得分85分，作业在deadline前提交，那么他的实际得分为85*100%*25% = 21.25
小张此次作业得分85分，并是在deadline后的两天内补交，那么实际得分为85*50%*25% = 10.625
小王在作业deadline两天后还未补交，作业提交已经关闭，此次作业得0分
...
4, other rules
- Plagiarism job: teaching assistant found two blog text / image when / code similarity of more than 50%, determined that two blog are copied, scores are -100%;
- Submit fake: Although the job is not completed blog, but to submit to the job accounting position, determined to forge submit scores 0 points;
- Micro-channel release notification if the class group is part of the job requirements, please see the notice group;
- If you need to fill out the information in a micro-channel group, failed to complete the before the deadline, buckle actual score of 50%;
- Questions on the job, three days before the group presented in the class deadline;
- If the job requires a modification assistant, you will notice in the group, be sure to check and press new demands perfect job;