Requirements Specification--Small Valley Wai in Guangdong, an industry 719 electric competition Brigade
I. INTRODUCTION 1. Objective:
This document is written to clarify project requirements, plan projects, confirm progress, organize project development, and Test. At the same time, the detailed analysis of the overall project requirements, can be used as the basis and basis for project development work and confirm the test and acceptance of the basis.
2. Project and Team:
The system to be developed for the wide-life community, from the Small Valley Wai in Guangdong, an industry 719 power Group team proposed and developed.
member |
School Number |
member |
Soft worker Role |
He Simin |
3216005167 |
Product Planning |
Product Manager (group leader) |
Liu Yue Xuan |
3216005168 |
|
UI Design |
Ye Wentao |
3116004708 |
Java Development |
Background development |
Luo Zhanhong |
3116005151 |
Front-end development |
Front-end development |
Yiukangyu |
3116004707 |
Front-end development |
Front-end development |
Xia Donghong |
3116005159 |
Front-end development |
Test |
Ii. Overview of the project 1. Product Description
Nowadays, the sale of idle goods more and more diversified channels, including "Idle Fish", the major colleges and universities to deal with idle items, but still bring a lot of distress, such as: idle fish is not humane, long time period, courier transactions make it difficult for buyers and sellers to communicate and so on; the number of idle groups is too difficult to manage, Too many messages, the trading information of idle items is difficult to retain. These various reasons have greatly wasted the user's time and energy, therefore, our team plans to launch a community based on the school's teachers and students, including the use of idle items trading platform and chat community, as much as possible to facilitate the trading of idle items.
2. Product Features
Our team's project is a community of Guang-gong living, simple and practical second-hand platform and chat community, the goal is to solve the problem of idle items of university students. Users can use the second-hand platform to publish trading information (including the items they want to sell and what they want to buy) and price them, and the rest of the community will be able to view unused items on the second-hand platform and enter chat community-related discussion groups.
1. This product mainly has the following functions: (with the version update, features may be added or deleted)
2. Object-oriented (expected user volume):
All teachers and students of Guangdong University of Technology may later expand to the whole university city
3. Project Warehouse
Our team has built a warehouse on the gitlab of the lab, which makes it inconvenient to open the project address.
4. Team's unique design/function
Based on the daily life of college students, practical and convenient daily life
Third, the specific needs of 1. function diagram
2. Prototype diagram
3. Properties
1. Authenticity
- Reliable data and complete database design
2. Availability
- Simple and beautiful interface, easy to operate
- Stable system, no bugs
- When a delete operation is involved, a reminder is associated
3. Security
- Data backup to prevent users from losing data and recovering data in a timely manner
- Protect User Privacy
- Pre-offline trading to protect users ' trading security
4. maintainability
- Use GitHub for source management for ease of maintenance and repair
Iv. Team planning 1. Original plan
time (number of weeks) |
Plan |
is completed |
1 |
· 1. Team teams, Team blogs |
Is |
1 |
· 2. Team presentation, member presentation, role assignment, selection of topics |
Is |
1 |
· 3. Develop team planning arrangements, team contribution sub-rules |
Is |
2 |
· 1. Requirements Specification Sheet |
Is |
2 |
· 2. Prototype design, team members estimate task difficulty and learn the necessary techniques |
Is |
2 |
· 3. Coding specification Complete, platform environment set up, preliminary construction |
Is |
3 |
· 1. Prototype improvement (to demonstrate the prototype to the target user and further understand the requirements) |
|
3 |
· 2. Architecture design, WBS, team members estimate the time required for their respective tasks |
|
3 |
· 3. Test Plan |
|
4 |
· 1. Team Project Alpha Task assignment schedule |
|
4 |
· 2.7 consecutive days of Alpha Agility Sprint, 7 daily Scrum meeting blog + code submission |
|
2. Calibration Plan
time (number of weeks) |
Plan |
is completed |
1 |
· 1. Team teams, Team blogs |
Is |
1 |
· 2. Team presentation, member presentation, role assignment, selection of topics |
Is |
1 |
· 3. Develop team planning arrangements, team contribution sub-rules |
Is |
2 |
· 1. Requirements Specification Sheet |
Is |
2 |
· 2. Prototype design, team members estimate task difficulty and learn the necessary techniques |
Is |
2 |
· 3. Coding specification Complete, platform environment set up, preliminary construction |
Is |
3 |
· 1. Prototype improvement (to demonstrate the prototype to the target user and further understand the requirements) |
|
3 |
· 2. Architecture design, WBS, team members estimate the time required for their respective tasks |
|
3 |
· 3. Test Plan |
|
4 |
· 1. Team Project Alpha Task assignment schedule |
|
4 |
· 2.7 consecutive days of Alpha Agility Sprint, 7 daily Scrum meeting blog + code submission |
|
5 |
· 1. User feedback, test plan improvement |
|
5 |
· 2. Team Alpha Stage Personal summary |
|
5 |
· 3. Team Project Alpha Blog: Release notes, test reports, presentation blogs, project management |
|
6 |
· 1. Team Project Alpha Blog: Post-mortem analysis |
|
Requirements Specification--Small Valley Wai in Guangdong, an industry 719 electric competition Brigade