PROGRESSIVE REPORT

Project Analysis.

The intended project is a database project targeting NBA Basketball teams owning private
arenas. The outcome of the project is a system that can manage the daily operations of the
arenas as well as the team. Using the system, the team management can track the progress of
the teams and the players based on the data stored in the system’s database. Additionally, the
teams can use the platform provided in the system for communication and also plan for future
matches.

The approaches taken in the development of this system will follow the Rapid Development
model to ensure accurate and timely delivery of the system. The five major steps to be taken
in this process are Analysis, Logical Design, Physical Design, implementation and
modification, and maintenance. The database will be modeled based on the needs of the
industry.

Mission Statement.
To develop an NBA Management system. Our mission encompasses both the stadium and
team management. The system will ease the process of tracking the performance of both the
arenas and the team. The vision will extend beyond the NBA game to other leagues globally.

Supporting Dialogue.

Reporter: Hello
Technical Manager: Hello, welcome to our headquarters
Reporter: Thank you for having me. I contacted your organization about the activities of
today.
Technical Manager: Yes, I was informed and you’ve come at the right time. We are currently
facing some challenges that the project may come to solve.
Reporter: Kindly tell me, what challenges are you facing.
Technical Manager: Mostly, we are unable to keep track of the revenue we raise during the
matches held in our arena.
Reporter: So, what kind of solution are looking to deploy to help you solve these prevailing
problems?
Technical Manager: We need an NBA Team management system customized to handle teams
with their own arenas.
Reporter: all right thanks so much.

Mission Objective:
The objective of this proposed system is to develop an NBA Team management system that
would:
1. Capture and store employees’ data
2. Generate reports on players and coaches
3. Records the outcome of previous matches
4. Generate reports of previous matches
5. Capture records of future matches and generate subsequent reports.
6. Record revenue from the events held in the arena and the subsequent reports.

Supporting dialogues.
Reporter: What kind of information do you store currently?
Technical Manager: currently we hold information about players and other employees, the
matches we are about to play or the ones we have played and where we played. Additionally,
we also record information about the arena.
Reported: What kind of information do hold on about the arena?
Technical Manager: About the arena, we store mostly the name of the events taking place and
also the outcome in terms of the revenue generated.
Reporter: Are the records manual and how do you generate the reports?
Technical Manager: Yes, all the records are paper-based and highly prone to misplacement.
The reports are also generated based on these manual reports and at times are highly
inconsistent.
Reporter: Ok thank you very much.

List of Subjects:
The list of subjects entails the actors or the category of users of the system and other
components whose details are necessary to the operations of the syste. The users are grouped
as below:

1. employees or users
2. clients
3. The arena
4. Matches
5. Departments
6. Matches
7. Opponents

Supporting Dialogue.
Reporter: Whom do you intend to assign this system to:
Technical Manager: This system will be used by the essentials. By essentials I mean, the
people who are relevant to the processes of the team.
Reported: Kindly elaborate further
Technical Manager: I mean the employees of the teams such as the managers, the players, the
technical teams, and our clients of the arena.
Technical Manager: Which roles do these people play?
Reporter: The technical team is responsible for managing data acquisition and management,
while the managers need the information in the system to make decisions and that goes even
for the coaches. The clients will book events through the system. Additionally, the player can
view details of previous interactions with the opposing teams.

List of characteristics.
The list of characteristics in this case forms the basis of developing the database for the
intended system. The y are the attributes of the subjects mentioned above and additional
necessary components. The list of attributes includes:
1. employeesID
2. empName
3. empPhone
4. empAddress
5. empDepartment
6. empCategory
7. custID
 8. custName
9. custPhone
10. custAddress
11. matchID
12. matchDate
13. eventID
14. eventDate
15. eventTime
16. amountRaised
17. bookingID
18. bookingDate
19. bookingTime
20. amount
21. departmentID
22. departmentName
23. categoryID
24. categoryName
25. opponentID
26. opponentName
27. previousOutcome

The list above details the expected characteristics to constitute the database. They double up
as the preliminary list and upon approval will constitute plus ay other changes recommended
or changed.

Preliminary Table List:

Below is a list of expected tables to constitute the database as well as details the
characteristics
1. Employee
2. Customer
3. Event
4. Booking
5. Category
6. Department
7. Opponent

The database structure.

The table below details the fields contained within each and every table and the tables
contained in the proposed database.

Employee Customer Event Booking Category Department

employeesID custID eventID bookingID categoryID departmentID

empName custName eventDate bookingDate categoryName departmentName
empPhone custPhone eventTime bookingTime
empAddress custAddress amountRaised amount
empDepartment
empCategory

Opponent
opponentID
opponentName
previousOutcome

Implementation Progressive.
So far the table structure of the database has been designed based on the interview carried out
to determine the needs of the client. The database covers every subject identified through the
interview. The language of to be used on the system is C# and based on the Microsoft Access
Database. The database will be implemented according to the schedule provided on the
proposal.