|name||style||software engineering roles|
|WENTAO LIN||Leadership||Team Leader & Software Engineer|
|WENYONG LIAN||All-round||Database Administrator & Research and Development|
|YI LU||Have the big picture||AI Development|
|RONGPEI CAI||Contracted||Front-End Development|
|RUNJIE ZHOU||Work hard||Project Manager|
Our team has rich project experience and professional knowledge. The members of our team are very active.
We have certain AI capabilities and are good at transforming requirements into technologies for implementation.
Logo of team
"Individual contribution" rule
30% -- Participation time
(We use the time of each member in the completion of the project to represent the enthusiasm of students in the project)
30% -- Degree of task completion
(Considering the actual situation, we use a certain degree of project completion to represent the students' efforts)
40% -- Cost of learning
(Many students are novices, learning from scratch. Since each student is responsible for different parts and the cost of learning is also different, according to this situation, we set certain contributions for these students)
MAP (mind map and burnout map)
(1) Part APP Client
(2) Part Database Administrator & Research and Development
|Week N||New code (line)||Cumulative code (line)||Time spent on learning this week (hours)||Cumulative time spent on learning (hours)||Important growth|
|1||1000||1000||6||6||Determine the topic and draw the app prototype|
|2||4000||5000||25||31||According to the prototype drawing write the landing module and realize the interface docking and testing|
|3||3000||8000||20||51||Gradually implement the interface and ai algorithm model search|
|4||1000||9000||10||61||Personnel test work and other interface docking|
Selection of UML design tools, reasons for selection and evaluation of tools after use
We used proccesson, which is easy for beginners to get started with.
Our team members expressed their appreciation after using this tool. It enabled us to have a closer understanding of the project architecture, and it also allowed us to reasonably arrange the development steps and processes.
What are the main difficulties in moving this project forward?
First of all, I have no experience in writing demand analysis report and do not know where to start.
Don't know what a UML diagram is?
To solve these problems:
The team leader divided the task into two parts: drawing the prototype and writing the software requirement specification, giving the overall time planning, and designating the person in charge of the two parts of the task;
The person in charge will refine the task, arrange the schedule, and designate specific personnel to complete the corresponding part;
Team members complete the corresponding content;
Such division of labor can improve efficiency, and it can accurately locate the problem and the problem solver, and quickly deal with the corresponding problem.
Since drawing the prototype and writing the software requirement specification can not be completed by a single person, but requires multiple people to collaborate online at the same time, we tried the Ink Knife enterprise edition, Tencent document, graphite, tower content sharing and production, which really greatly improved the efficiency. If you put all the content in qq group is inefficient, and disorderly, orderly in the online document will be more clear.
How do you solve this problem?
What have you got?