Team Blog-Requirements Specification (SU Chahar-chan)

Players

3116004643 Liang Langzhang
3116004644 Leung (group leader)
3116004645 Lin Qipeng
3116004646 Liu Shaoyun
3116004656 Wu Hao
3116004667 Shing and

Requirements Specification Sheet

Title: Activity Reservation System
The system provides a reservation system for small and medium-sized activities, such as film/concert/seminar/Concert/lecture/conference/ball games and other required seats, and the need to anticipate the number of participants in advance activities, any organization/individual events can unconditionally use this reservation system.

Basic requirements

(1) Event organizers can pre-register the event for the audience to select seats
(2) The audience can see information about the event, such as the content of the event, the time and place
(3) The audience may specify the designated seat for the designated event.
(4) The visitor can change the ticket and seat under the specified conditions.
(5) The audience can score and evaluate the activities they have already participated in.

User-oriented Analysis

This system allows small and medium-sized event organizers to publish their events free of charge, publish seat information, and generate links on their own promotion page, which allows users to easily view information about the event and make reservations. Users can also find their own activities and reservations on the page.

Functional Requirements

The system can graphically present the active seat information to the user, who can see the selected seats and the selected seats. Event organizers can simply submit their own event information and seat information, and view the selection of seats.

Technical Requirements

The system switches JSON format data through front-end Ajax and back-end using spring boot + JPA to manipulate MySQL.

Expected number of users

The initial expected number of users is 100 due to server performance limitations

Authenticity

At present, the activities of the school community, concerts, lectures, and so on most of the small and medium-sized activities are still using the most primitive people to sit, no seat standing or the distribution/sale of tickets and other traditional way, this means that the cost of human resources and can easily adversely affect the audience. Therefore, small and medium-sized event organizers have a simple and non-threshold reservation system needs

Availability of

The system in addition to the basic booking function without any impact on the subject of content (such as advertising), simple operation, the page concise.

Value of

For the organizers, the use of the system can be very good control of the number of participants to avoid excessive number of seats caused by the shortage. At the same time, the market reservation system more or less need a certain price and conditions, and our system for individuals and small organizations are completely free and 0 threshold.
For the general audience, the system is no other software so bloated, so many ads, the overall system is concise style. And the system can use the recommended algorithm for the general audience to recommend their interest activities.

Team Project Address

Https://github.com/team-suchan/Booking

Issues

Team Planning original arrangement

Time	Task Progress
6th Week	1. Team teams, Team blogs
	2. Team presentation, member presentation, role assignment, selection of topics
	3. Develop team planning arrangements, Team contribution sub-rules
7th Week	1. Requirements Specification Sheet
	2. Prototype design, team members estimate task difficulty and learn the necessary techniques
	3. Coding specification Complete, platform environment set up, preliminary construction
8th Week	1. Prototype improvement (to demonstrate the prototype to the target user and further understand the requirements)
	2. Architecture design, WBS, team members estimate the time required for their respective tasks
	3. Test Plan
9th Week	1. Team Project Alpha Task assignment schedule
	2.7 consecutive days of Alpha Agility Sprint, 7 daily Scrum meeting blog + code submission
10th Week	1. User feedback + test plan improvement
	2. Team Alpha Stage Personal summary
	3. Team Project Alpha Blog: Release notes, test reports, presentation blogs, project management
11th Week	1. Team Project Alpha Blog: Post-mortem analysis
	2. One person on each team must leave and look for the next team to accept. The team sent out blogs announcing the departure and acceptance of the members.

Post-correction arrangements

Time	Task Progress
6th Week	1 team, Team blog (? finish)
	2. Team presentation, member presentation, role assignment, selection of topics (completion)
	3. Set up team planning, Team contribution sub-rules (? complete)
7th Week	1. Requirements specification (? completed)
	2. Prototype design, team members estimate task difficulty and learn the necessary techniques (? finish)
	3. Coding specification Complete, platform environment set up, initial structure construction (? completed)
8th Week	1. Prototype improvement (to demonstrate the prototype to the target user and further understand the requirements)
	2. Architecture design, WBS, team members estimate the time required for their respective tasks
	3. Test Plan
9th Week	1. Team Project Alpha Task assignment schedule
	2.7 consecutive days of Alpha Agility Sprint, 7 daily Scrum meeting blog + code submission
10th Week	1. User feedback + test plan improvement
	2. Team Alpha Stage Personal summary
	3. Team Project Alpha Blog: Release notes, test reports, presentation blogs, project management
11th Week	1. Team Project Alpha Blog: Post-mortem analysis
	2. One person on each team must leave and look for the next team to accept. The team sent out blogs announcing the departure and acceptance of the members.

Correction calculation method

As team work completed this week coincides with the plan, there is no need to revise the original plan for the time being.

Other team Division

member	Division
Liang Langzhang	Algorithm design
Minghui man, Lin Qipeng, Wu Hao	Web front end design and UI design
Liu Shaoyun, Shing and	Back-end development and testing

Complete situation

Liang Langzhang: Complete Basic functional requirements
Leung: basic knowledge of HTML, CSS, JavaScript, jquery
Lin Qipeng: Learning html,javascript Basic knowledge
Liu Shaoyun: Complete the creation of the database and the creation of the table structure, set up the preliminary API document
Wu Hao: initial mastery of html5,css, understanding JavaScript
Shing and: The initial completion of the overall structure analysis, specific additions and deletions depending on the implementation of the situation.

Team members ' impressions

Liang Langzhang: After reviewing the Bayesian and learning the Lagrange multiplier, feel that their mathematical ability is limited, to continue to work hard.
Leung: After learning the basic language, look at the various sources of web pages, fully aware of the complexity of web design, but also aware of the shortage of programming experience, to learn more after this.
Lin Qipeng: This week learned the basic knowledge of html,javascript, later to learn a lot.
Liu Shaoyun: Because there was little contact with the front end of things, and did not seriously do the demand analysis, so in the design before and after the interaction of no experience, changed a lot of times are not very satisfied, about the project structure design also thought for a long time, so there are a lot of places to learn.
Wu Hao: Beginner HTML5 and CSS, the development of the front-end experience is not much, especially for the process to use the JavaScript is not very understanding, in the hands of a lot of difficulties encountered, or need to read more books, and actively discuss with the students, to keep up with the team progress, not to drag.
Shing: A key part of the software is the overall architecture, the software model came out, then the rest is only to fill the content, so to the software after the concrete implementation will be what it is, what functions, to have a clear understanding.

Team Blog-Requirements Specification (SU Chahar-chan)