Software Engineering fourth time Assignment (topic, process Arrangement)

First, team composition and topic Description:

① Introduction Team Composition:

Team members:

Wu Jingan:201728211028 (left one)

Chen Yang:2017282110288 (left two)

Zhang Huiyu:2017282110284 (Right One)

Hanwha Ode:2016282110142 (second right)

Hu Zhiquan:2016282110143 (Unable to participate in team meeting and group photo due to field interview)

Team Git:

Https://github.com/orgs/WHUSE2017/teams/java-team/members

② Collection Requirements:

The first step: each of our team members in their own laboratory or dormitory to the surrounding people in the initial demand collection (about one to two each).

Step two: Discuss the team meeting and summarize all the requirements collected.

The third step: According to the project time node limit, to complete Alpha version Our project development time is about 14 days, we have collected the requirements of the requirements analysis and feasibility analysis, and finally screened out the most suitable projects.

③ Topic Analysis:

we chose to do a "course group" project for teachers and students, the project name tentative: "Curriculum Group System"

N (need): Class teacher said: "Which classmate to do the class, build a QQ group, let me choose this class of students are added, I will be after class homework and classroom PPT sent to the group."

After class, the students say, each lesson is a QQ Group Group, my group has dozens of, silly points not clear which class is which group, search half a day.

Our team is to collect the needs of the people around us and to understand that teachers and students have this QQ build group of trouble and hope to have a dedicated system to solve this problem instead of each course exchange depends on QQ, this is what we get in the user's need to be resolved pain points.

A (Approach): Our team uses the Java language. Browse the Web to do a good interface and functions for reference, combined with our own usual blog, QQ, client and web version of the experience, consider the objective conditions, we set ourselves to achieve the outline of the project and the general implementation steps.

B (Benefit): Teachers can not be in the classroom to find class representative, looking for someone to set up QQ group and a classmate of a classmate's approval to join. Teachers can easily arrange assignments, publish learning materials, course information, and the students who have chosen this course to communicate, similar to the QQ group part of the function of separate out with the blog to combine specialized services in the teaching system. Students can easily join the class at the time of the course, without having to search for each group number in the first week's class.

C (competitors): At present in the Wuhan University campus are based on QQ building groups, building groups of the way to carry out the course exchange activities, so it is very creative to solve the target user pain points of the new project.

D (Delivery): Because of the short time, we plan the function is not perfect, we intend to do not do so complex, later increment and modification function. Because of the choice of classes and student information can not be used in the school database, can only do their own simulation of our own relatively simple, if done better need to get the school database can be used in the whole university or even other school promotion.

Second, the project schedule:

①wbs

estimated effort required: within two weeks , 5 people were working together, and the two were mainly responsible for coding and all involved in the development process.

members committed to working hours: It takes a little more time to encode the members, and the average person spends 5 hours per day.

② Schedule : a week to complete the system design and basic framework, two weeks to achieve the basic functions of the requirements analysis plan, the completion of the alpha version of the release.

The Division of labor and the proportion of workload of the planners :

Zhang Huiyu: (284) responsible for coding, accounting for 25%.

Hanwha Ode: (142) responsible for coding, accounting for 25%.

Chen Yang: (288) PM, responsible for the requirements analysis document preparation, project testing and test report, accounting for 12%.

Wu Jingan: (286) responsible for system design and documentation, the beta version of the summary, accounting for 12%.

Hu Zhiquan: (143) responsible for the system Alpha version summary, the development process required other generated documents, accounting for 12%.

The remaining 14% is allocated according to the contribution value in the project implementation process.

The Requirements Specification Git links:

Https://github.com/WHUSE2017/Java-Team

Software Engineering fourth time Assignment (topic, process Arrangement)