Volleyball scoring (i) demand analysis and database design

Requirements Analysis:

As a volleyball scoring rules of the page program, the general user for the fans audience and volleyball scoring staff.

1. As a volleyball scoring player, you need to achieve the score of the addition and subtraction, and automatically determine the outcome, the final incoming database.

2. As a volleyball scorer, it is necessary to record the score in detail while achieving the score.

3. As a volleyball scoring member, some records may be modified.

4. As a fan audience, you first want to see all the basic records of the game.

5. As a fan audience, I would like to see a detailed record of each game.

Attached use case diagram one:

Database:

Record table:

ID int match ID notnull primary key, self-increment

Gamename varchar (50) Contest name Notnull

TeamA varchar (50) main squad Notnull

Teamb varchar (50) Guest squad Notnull

Vsab varchar (20) field score Notnull

Gamefirst varchar (20) first inning score Null

Gamesecond varchar (20) second inning score Null

Gamethird varchar (20) third inning score Null

Gameforth varchar (20) fourth inning score Null

Gamefifth varchar (20) fifth inning score Null

Teamwinner varchar (50) Winner Team Null

Gamecontent varchar (max) verbose content Null

How to decide if it's a scorecard or a fan audience table

As a visitor, a record can be viewed as a non-establishment account.

A scorecard adds a data account to the default administrator

Scoring table:

ID int Administrator ID notnull primary key, self-increment
Name varchar (20) Login name Notnull
Password varchar (50) login Password Notnull

Volleyball scoring (i) demand analysis and database design