Team name: Inequality of
Leader blog
Job blog
Team project schedule
A crew: Zhang Yijie (Leader)
- Over the past two days to complete the task:
- Text / verbal description:
- We developed a preliminary project plan, and began to learn some of the recommendations, search algorithm class
- GitHub commit record:
- No
- Text / verbal description:
- The next plan:
- Next week urging responsible for front-end crew quickly completed, and began writing the back end
Burndown chart:
- What is left tasks:
- Each module coding, testing, project management, pressed forward docking after each module is completed
- Real test feedback optimization
- According to the feedback optimization test
- What are the difficulties encountered:
- Players to develop software application is not skilled
- Java no basis more players, we need a temporary self
- Adjust the time schedule is more difficult
- What have we learned and questions:
- reward:
- And his teammates can learn new algorithm with knowledge, knowledge database, he taught himself some knowledge about team management.
- doubt:
- Are some of the technical questions
- reward:
Crew II: Lin Jiawei
Crew II: Lin Jiawei
- Over the past two days to complete the task:
- Text / verbal description:
- Completed the construction of the database
- Learn how to build interactive web framework and the front and rear ends
- GitHub commit record:
- No
- Text / verbal description:
- The next plan:
- Burndown chart:
- Burndown chart:
- What is left tasks:
- Truly build Web framework
- Python complete operation of the database
- What are the difficulties encountered:
- Courses pressure, more exams, lack of time
- More practice, difficult to schedule
- What have we learned and questions:
- reward:
- Learn python framework of Flask
- doubt:
- How to be resolved to complete the data loaded at the same time rendering interface
- reward:
Members three: Wu Zhiyong
- Over the past two days to complete the task:
- Text / verbal description:
- We developed a preliminary project plan, and began to learn some of the recommendations, search algorithm class
- GitHub commit record:
- No
- Text / verbal description:
- The next plan:
- The beginning of next week to prepare the database
- What is left tasks:
- Database development
- Optimization algorithms
- What are the difficulties encountered:
- Selection Algorithm
- There is no basis for java, the need for temporary self-study
- Adjust the time schedule is more difficult
- What have we learned and questions:
- reward:
- Learning a new algorithm knowledge, knowledge database
- doubt:
- Are some of the technical questions
- reward:
Members four: Yeung Kam Bin
- Over the past two days to complete the task:
- Text / verbal description:
- Part of the development of the front end
- GitHub commit record:
- No
- Text / verbal description:
- The next plan:
- The complete front-end development
- What is left tasks:
- Left half of the front-end tasks
- What are the difficulties encountered:
- Front-end application development software is not skilled
- Insufficient time
- What have we learned and questions:
- reward:
- Learn about the development of knowledge about the front end of the
- doubt:
- Are some of the technical questions
- reward:
Members five: Chen Rongjie
- Over the past two days to complete the task:
- Text / verbal description:
- Understand the recommendations, search algorithm class
- GitHub commit record:
- No
- Text / verbal description:
- The next plan:
- Continue to write the back end
- What is left tasks:
- Implementation of the algorithm
- What are the difficulties encountered:
- Software development is not skilled to use
- There is no basis for java, the need for temporary self-study
- What have we learned and questions:
- reward:
- And his teammates can learn with new algorithms knowledge database knowledge.
- doubt:
- Are some of the technical questions
- reward:
Members Six: Bao as ice
- Over the past two days to complete the task:
- Text / verbal description:
- The front end of the message, a message, the Home page
- GitHub commit record:
- No
- Text / verbal description:
- The next plan:
- Learning Js, perfect interaction page
- What is left tasks:
- Front-end interface
- What are the difficulties encountered:
- Time to catch, interaction rough
- Heavy load a little difficult to extract a lot of time
- What have we learned and questions:
- reward:
- Use of htmlcss a better understanding of the
- doubt:
- Are some of the technical questions
- reward:
Members seven: Liu Wang Yang
- Over the past two days to complete the task:
- Text / verbal description:
- Understanding of the need to use the buttons and other plug-ins, trying to design.
- GitHub commit record:
- No
- Text / verbal description:
- The next plan:
- To complete the work as soon as possible is responsible for front-end
- What is left tasks:
- The front end portion of the coding, testing
- What are the difficulties encountered:
- The biggest difficulty is the lack of time, there are two exams this week
- What have we learned and questions:
- reward:
- Front-end development for a better understanding and familiarity
- doubt:
- Still some technical questions
- reward:
Members eight: Huang Binhuang
Over the past two days to complete the task:
writing / verbal description:
Learn some data before and after the end of the interaction, knowledge about Flask framework
GitHub check the record:
- No
next plan:
have a problem to solve a
what tasks left:
continue to explore the problems encountered algorithm
encountered what difficulties:
more exams and assignments, time is really tight schedule
What have you learned and questions:
harvest:
the case of using ajax algorithm successfully without changing pages, interact with the back-end, and the useful information recorded in the database
question:
can specifically talk about Flask in the framework of how the page is loaded on to interact with back-end get some information, and as the page is not rendered together? Js use it?
Crew Nine: Huang Zhifeng
- Over the past two days to complete the task:
- Text / verbal description:
- No
- GitHub commit record:
- no
- Text / verbal description:
- The next plan:
- Burndown chart:
- Burndown chart:
- The next plan:
- With the team to complete the preliminary design software
- What is left tasks:
- Development front page
- Teammates with back-end connectivity
- What are the difficulties encountered:
- Not familiar with the new language
- What have we learned and questions:
- reward:
- Master the skills of some of the front-end development
- doubt:
- Are some of the technical questions
- reward:
Members ten: Su Kaiting
- Over the past two days to complete the task:
- Text / verbal description:
- Completed the front-end part of the content writing
- Completed the front-end part of the content writing
- GitHub commit record:
- No
- Text / verbal description:
- The next plan:
- Js add behavior to each page
- What is left tasks:
- Linked pages
- Learn js
- What are the difficulties encountered:
- No
- What have we learned and questions:
- reward:
- Html have done relatively quickly
- doubt:
There are currently no doubt
Crew XI: Wang Chin Shih
- reward:
- Over the past two days to complete the task:
- Text / verbal description:
- Learn some of the back-end knowledge
- GitHub commit record:
- No
- Text / verbal description:
- The next plan:
- Familiar with the interface and learn knowledge, implement the interface
- What is left tasks:
- Learn and achieve
- What are the difficulties encountered:
- Software development is not skilled to use
- Interface type of project that may be required not know enough about
- What have we learned and questions:
- reward:
- And everyone can learn together and progress together.
- doubt:
- They are
- reward:
Showcase the latest achievements within the group
login interface
Search interface
Send a message
Personal Center interface
1 Shopping Cart Interface
Shopping Cart Interface 2
Shopping Cart Interface 3
Shopping Cart Interface 4
Recommended Books interface
1 setup interface
2 settings interface
Home
Book detail screen
I received orders
I'm under orders interface
Message interface
Change Password interface
Interface gift
Registration Interface
Standup photo:
Meeting time-consuming record table
N-meeting | time consuming |
---|---|
1 | 10 |
2 | 8 |
3 | 8 |
4 | 8 |
psp table
PSP2.1 | Personal Software Process Stages | Estimated time consuming (minutes) | The actual time-consuming (minutes) |
---|---|---|---|
Planning | plan | 10 | 20 |
Estimate | Estimate how much time this task requires | 5 | 5 |
Development | Develop | 10 | 10 |
Analysis | Needs analysis (including learning new technologies) | 60 | 50 |
Design Spec | Generate design documents | 0 | 0 |
Design Review | Design Review | 0 | 0 |
Coding Standard | Code specifications (development of appropriate norms for the current development) | 10 | 10 |
Design | Specific design | 10 | 15 |
Coding | Specific coding | 60 | 140 |
Code Review | Code Review | 10 | 10 |
Test | Test (self-test, modify the code, submit modifications) | 30 | 20 |
Reporting | report | 0 | 0 |
test repor | testing report | 0 | 0 |
Size Measurement | Computing workload | 0 | 0 |
Postmortem & Process Improvement Plan | Later summarized, and process improvement plan | 10 | 10 |
total | 215 | 300 |
Learning schedule
N-Week | New Code (lines) | Cumulative codes (lines) | This week learning time-consuming (hours) | Cumulative learning time-consuming (hours) | Important growth |
---|---|---|---|---|---|
12 | 200 | 2000 | 20 | 120 | Learn html |