I. Introduction Team
- Team name: Hu Li Li Luo He Reymundo team;
- Number of teams: 7;
- Team guidelines: united as one, a person in trouble, six support;
- Team Features: teamwork, communication facilities work actively, extraordinarily high efficiency.
- Student ID list of players
| He Quanjiang (captain) | 201731024218 |
|---|---|
| Wu Chi-wai | 201731024240 |
| Li Hong Kong | 201731024232 |
| Meng Cheng Cheng | 201731024242 |
| Luo Junjie | 201731024226 |
| Lei Anyong | 201731024215 |
| Li Xuanxiao | 201731024108 |
Second, the team Introduction
- Quanjiang : positive, pro-human and specializes in c # programming, programming interests are very strong, hoping assume the role of algorithm design;
- Leian Yong : wide open wide, known for warm, sociable, cheerful cooperation with the players. For programming beyond their grasp, hoping to serve as auxiliary work;
- Li Hong Kong : Steady, serious and responsible work, good general idea of the program design, creative writing program window, hoping to serve as the chief architect of the team.
- Li Xuanxiao : pay more attention to details of the deal, I was interested in programming, but not a solid foundation, as amended want to work.
- Luo Junjie : There is a sense of team, rigorous and serious people understand the simple programming knowledge, have some knowledge about database design, database design work as hoped in a team.
- Wu Chi-wai : sociable, serious and responsible work, focus on teamwork, rigorous and earnest only every player to have a good harvest, positive, optimistic, cheerful, hope as publicity work in teams.
Meng Cheng Cheng : Careful and team spirit, love programming, there is a positive heart, brains like thinking, put forward original ideas, but in terms of programming capacity needs to be strengthened, hope as test work in teams.
3. Introduction
Name: daily roll call
Project Description
"Every day naming" is a case for educational institutions and universities lines, supervise the free software named student in class on time, implemented on the Windows platform. This product is most suitable for the current school is located. The user can at any time by naming this product and time-consuming short, high efficiency, and can be recorded on the student's attendance information.
Four, NABCD analysis
- Need
traditional roll-call time and effort, this product can greatly save time and effort of teachers and students. - Approach
1, WPF using C # language program development;
2, team members completed the division of labor. - Benefit
1, save manpower;
2, convenient records of student attendance information; - Competitors
compared to other named platform, we have the following competitive advantages:
1, the control interface is simple, nothing fancy, such as advertisements affect the user experience;
2, high efficiency, a key randomly named, completed more than just a roll call Suddenly;
3, can record student attendance information can be every roll call attendance record, easy to summarize the teacher recorded in the end of the semester. Delivery
on-site promotion, the promotion of social platform forward.Fifth, the initial division of tasks and schedules.
Preliminary division of tasks
| student ID | Division of work |
|---|---|
| 201731024218 | Project planning process ① ② organizing meetings, assign tasks to participate in document drafting ③ |
| 201731024240 | ① ② responsible for the back-end developers to participate in document drafting |
| 201731024232 | ① ② responsible for the back-end developer responsible for the learning algorithm, responsible for the design and development ③ PPT production |
| 201731024242 | ① UI design ③ ② responsible for front-end developers responsible for the program is responsible for defense |
| 201731024226 | ① ② responsible for the development of back-end database design |
| 201731024108 | ① ② participate in UI design program is responsible for unit testing |
| 201731024215 | ① ② responsible for front-end developers to participate in the program UI design ③ responsible for making PPT |
- Schedule
one day: 1. Demand analysis
;: 2.UI and database design 3 days
7 days;: 3. algorithms and programming
4. Test: 3 days;
5. operation and maintenance: Software undead, operation and maintenance than.