System Analysis And Design Soccer Club Database Computer Science Essay

System Analysis And Design soccer confederation Database Computer Science EssayThe aim of this project is to design and implement the entropybase application to flip-flop the current paper system of the soccer Club. This is the objective of system. The deputation of association football hostelry emergencys to expend this system for segment registration, gift payment, creation of goes list, set up the provision sessions, breakes the result of each pole. The coaches want to use this system to allocation of team.c) A Data Flow Diagram for the system including (12 marks) Process descriptions1. Register Membership, when populace want to join the membership, the committee of Soccer cabaret will provide the application from to ordinary, and check the application from is complete or not. And verified their ID and communicate address. If the development is correct. Then will collect the membership fee and create the membership card to the member. And the information of the member will keep in the member display panel panel.2. class allocation, the coach will get the playing members information from the member bow circumvent. And the coach will select the compatible member into the on game list. This is use to join the game of League and Cup. And besides will update the information of the team to the team up fudge get across. For example select the captain of the team.3. broadcast Training Session, the Soccer club bind hold a number of training sessions, the training session is lead by international player. When the committee of Soccer club setting up the training sessions, they need to connect with international player for lead the session. And the international player needs to confirm to lead the sessions. The selective information of international player is storehouse in international player convey in instrument panel and the data of training session is store in Training card table.4. Create resort lists, when the Soccer club joins the game of league competition and cup competition. The league competition and cup competition will collect other 15 teams and provide the fixture list to the Soccer club. The committee of Soccer club need to publish this fixture list to the public, let them know the dwelling team, away team, oppose address, tick day and time. This data will store in muddle list and result table. In this fixture list we also will know which team will join the league and cup. former(a) Soccer teams information will store in Other teams table table.5. supply result, all the result of the matches, will be provide from the league competition and cup competition. The result of Soccer club and other teams also need to collect. This data will store in the result table table, they will publish the result to the public. Data store contents1. Member Detail, This is the table of members information. It include the line of products Member_ID, severalise, Date_of_Birth, Membership_type, Ph whizz, Addres s, Email, drug user_ID, team_ID, On_game_list, committal_ID2. Team Detail, This is the table o f Soccer Cups Team. It include the land Team_ID, director_ID, Captain_Member_ID, Vice_Captain_Member_ID, Team_ conjure up, Member_ID3. outside(a) instrumentalist Detail This is the table of international players information, this table include the battleground Player_ID, Ph whiz, Address, Email, Salary, user_ID4. Training Detail, this is the table of Trainings information, it include this field Session_ID, fig, Player_ID, Player_Name, session_ free_day, Address, time, total_hour, Session_Fee, Committee_ID5. Other_Teams Detail, this is the table of other teams information which team are join the match with Soccer club. This table include the field Other_team_ID, Name6. fixation Lists and result Detail, this is table of the match list and the result of the match. This table include the field Match_ID, Team_ID, Other_team_ID, Match_address, Date, Time, Team_score, Other_team_score Ex ternal entity definitions1. Member of Public, this is the peck who join the Soccer club membership and they have been pay the membership fee every year. They canful be playing members or simply social members.2. Coach and International player, this is the people who responsible for training and selecting the team. And they also make the arrangements for travelling to matches at other Soccer club. And the international player is the trainer of open training session.3. Committee, this is the people who responsible for organizing open training sessions, inviting international players to lead the sessions, advertising the training sessions and determining and collecting the fee for such sessions. And they also need to collect and publish the matches result.4. League and cup, this is the local league competition and local cup competition, the Soccer join the match by this two competitions. They provide the matches result and the fixture lists to the Soccer club. line of work 2 Create a data model detailing the data structure required to support the information and process requirements of the soccer club system includinga) An Entity analogyship Diagram for the system. (6 marks)b) Entity descriptions for all entities in the diagram. (4 marks)1. user2. Coach3. Member4. Team5. Position6. Committee7. Other team8. Training9. speed List and impart10. International Player11. Training Student12. Studentc) Appropriate attributes for all entities including primary and immaterial keys. (5 marks)1. Entity exploiter butt eccentric Relation interpretation This is a table for the User login ID and password. The user of this system will use the information of this table to login.Attributes User_ID, User_Login, Password, Group prime delineate User_ID2. Entity Coach end Type Relation rendering The coachs personal information which system need are store in this table.Attribute Coach_ID, Name, Address, Ph unity, Email, User_ID simple key out Coach_ID contrary pick out User _ID book of factss to User table.3. Entity Memberobjective Type Relation rendering This is a table to store members criminal record.Attribute Member_ID, Name, ID_card_number, Date_of_birth, Membership_type, Ph peerless, Address, Email, User_ID, On_game_listPrimary Key Member_IDForeign Key User_ID references to User table table.Foreign Key Committee_ID references to Committee table4. Entity Team bearing Type Relation interpretation This is a table to store Soccer club player teams record.Attribute Team_ID, Coach_ID, Captain_Member_ID, Vice_Captain_Member_ID, Team_Name, Member_IDPrimary Key Team_IDForeign Key Coach_ID references to Coach table.Foreign Key Member_ID references to Member table.5. Entity Position object Type Relation exposition This is a table to store the locating of committees record.Attribute Position_ID, Position_namePrimary Key Position_ID6. Entity Committee intent Type Relationverbal description This is a table to store the committee record.Attribute Committee_I D, Team_ID, Position_IDPrimary Key Committee_IDForeign Key Team_ID reference to Team table.Foreign Key Position_ID reference to Position table.7. Entity Other TeamObject Type RelationDescription This is a table to store the record of other Soccer team which will match with Soccer Clubs team.Attribute Other_team_ID, NamePrimary Key Other_team_ID8. Entity TrainingObject Type RelationDescription This is a table to store the open training sessions record.Attribute Session_ID, Name, Player_ID, Player_Name, Session_open_day, Address, Time, Total_hour, Session_Fee, Committee_IDPrimary Key Session_IDForeign Key Player_ID references to International Player.Foreign Key Committee_ID references to Committee.9. Entity Fixture Lists and ResultObject Type RelationDescription This is a table to store the record of fixture Lists and the match result.Attribute Match_ID, Team_ID, Other_team_ID, Match_address, Date, Time, Team_score, Other_team_scorePrimary Key Match_IDForeign Key Team_ID references to Team table.Foreign Key Other_team_ID references to Other team table.10. Entity International PlayerObject Type RelationDescription This is a table to store the record of international player. The international player is the trainer of open training session.Attribute Player_ID, band, Address, Email, Salary, User_IDPrimary Key Player_IDForeign Key User_ID references to User table.11. Entity Training StudentObject Type RelationDescription This is the link entity of Training table and Student table. Because one student can join umteen training session and one training session can have legion(predicate) students. So we need to use link entity to re gain this legion(predicate) to umpteen an(prenominal) relationship.Attribute Training_studnet_ID, Session_ID, ID_card_NumberPrimary key Traininig_student_IDForeign Key Session_ID references to Training table.Foreign Key ID_card_number references to Student table.12. Entity StudentObject Type RelationDescription This is a table to store the record of student.Attribute ID_card_number, Name, call up, Address, EmailPrimary Key ID_card_numberd) alliances detailing optionality and degree of relationships between entities. (5 marks)1. relationship ID R1Name Coach table to User tableObject Type kinshipDescription Each coach has only one unique User_IDCardinality one to one,Coach table is the one side. whizz User_ID only blend in to one coach.User table also is the one side. One coach only has one unique User_ID.Optional Coach table is the optional side. A user may be not a coach.User table is the obligatory side. A coach mustiness be a user.2. Relationship ID R2Name International Player table to User tableObject Type RelationshipDescription Each international player has one unique User_IDCardinality one to oneInternational Player table is the one side. One User_ID only can belong to one international player.User table also is the one side. One international player only has one User_ID.Optional International Player table is the optional side. A user may be not a international player.User table is the mandatory side. A international player must be a user.3. Relationship ID R3Name Member table to User tableObject Type RelationshipDescription Each member has one unique user_ID.Cardinality one to oneMember table is the one side. One User_ID only belong to one member.User table is the one side. One member only can have one User_ID.Optional Member table is the optional side. A use may be not a member.User table is the mandatory side. A member must be a user.4. Relationship ID R4Name Member table to Team tableObject Type RelationshipDescription Member belongs to Ruby Clubs team.Cardinality many to oneMember table is the many side. One team can have many members.Team table is the one side. One member only can belong one team.Optional Member table is the optional side. A team may be not has any member.Team table is the optional side. A member may be not belongs to any team.5. Relationship ID R5Name Te am table to Coach tableObject Type RelationshipDescription Each team must have a coach.Cardinality one to oneTeam table is the one side. One coach only can belong one team.Coach table is the one side. One team only can have one coach.Optional Team table is the optional side. A coach can have any team to lead.Coach table is the mandatory side. A team must have a coach.6. Relationship ID R6Name Member table to Committee tableObject Type RelationshipDescription Some member is the committee of Soccer Club.Cardinality many to oneMember table is the many side. One committee position can belong to many members.Committee table is the one side. One member only can have one committee position.Optional Member table is the mandatory side. A committee position must belong to member.Committee table is the optional side. A member may be not have a committee position.7. Relationship ID R7Name Position table to Committee tableObject Type RelationshipDescription Each committee member of Soccer Club h as a position.Cardinality one to manyPosition table is the one side. One committee members only can have one position.Committee table is the many side. One position only can belong to many committee members.Optional Position table is the mandatory side. A committee must have a position.Committee table is the optional side. A position may be not belongs to any committee member.8. Relationship ID R8Name Team table to Committee tableObject Type RelationshipDescription Every committee member belongs to their team of Soccer Club.Cardinality one to manyTeam table is the one side. One committee member only belong one team.Committee table is the many side. One team can have many committee members.Optional Team table is the mandatory side. Every committee member must belong to a team.Committee table is the optional side. A team may be not has any committee member.9. Relationship ID R9Name Team table to Fixture List and Result tableObject Type RelationshipDescription The team of Soccer Club w ill have match will other team.Cardinality one to manyTeam table is the one side. One match only can join with one Soccer club team and one other team.Fixture List and Result table is the many side. One team can has many matches to play.Optional Team table is the mandatory side. The match must have Soccer clubs team.Fixture List and Result table is optional side. A team may be not has any match.10. Relationship ID R10Name Other Team table to Fixture List and Result tableObject Type RelationshipDescription Some member is the committee of Soccer Club.Cardinality one to manyOther Team table is the one side. One match only can join with one Soccer club team and one other team.Fixture List and Result table is the many side. One other team can have many matches to play.Optional Team table is the mandatory side. The match must have Soccer clubs team.Fixture List and Result table is the optional side. A team may be not has any match.11. Relationship IDR11Name Committee table to Training tab leObject Type RelationshipDescription Committee member with accountability for this open training session.Cardinality many to oneCommittee table is the one side. One session will lead by one committee member.Training table is the many side. One committee member can lead many training session.Optional Committee table is the mandatory side. The training session must lead by committee member and international player.Training table is the optional side. A committee member may be not lead any open training session.12. Relationship IDR12Name International Player table to Training tableObject Type RelationshipDescription International player with responsibility for this open training session.Cardinality many to oneInternational Player table is the one side. One session will lead by one international player.Training table is the many side. One international player can lead many training session.Optional Committee table is the mandatory side. The training session must lead by committee memb er and international player.Training table is the optional side. A international player may be not lead any open training session.13. Relationship IDR13Name Training Student table to Training tableObject Type RelationshipDescription It is a link entity to solve the many to many relationship of Training table and Student table. It break it to two one to many relationships.Cardinality many to oneTraining Student table is the many side.Training table is one the side.Optional Training Student table is the mandatory side.Training table is the mandatory side.14. Relationship IDR14Name Training Student table to Student tableObject Type RelationshipDescription It is a link entity to solve the many to many relationship of Training table and Student table. It break to two one to many relationships.Cardinality many to oneTraining Student table is the many side.Student table is the one side.Optional Training Student table is the mandatory side. The student must carry training session, if not t ake the training session, only is public not student.Student table is the mandatory side.Task 3 Create an Entity Life History for a training session. firstly is Join Member phase angle, then Member Amendment is the second stage, this stage can be repeat. And under this stage have three options, qualify Membership Type, Change Personal table and Do nothing. Finish this stage will become to Membership Overdue stage. This is the third stage of member. It has two options, Pay membership fee and Resign Member. If choose Pay member fee, then will back to the Member Amendment, and if choose Resign Member, then will become the last stage of member Delete Member. This is the end of this entity.Task 4 Create a database design for the soccer club system includinga) A set of tables identifying primary and foreign keys.(10 marks)User (User_ID, password, Group)Coach (Coach_ID, Name, Address, Phone, Email, User_ID)Team (Team_ID, Coach_ID, Captain_Member_ID, Vice_Captain_Member_ID, Team Name)Me mber (Member_ID, Name, ID_card_num,ber, Date_of_birth, Membership_Type, Phone, Address, Email, User_ID, On_game_list, Committee_ID, Team_ID)Position (Position_ID, Position_name)Committee (Committee_ID, Team_ID, Position_ID)Other team (Other_team_ID, Name)Fixture List and Result (Match_ID, Team_ID, Other_team_ID, Match_address, Date, Time, Team_score, Other_team_score)Training (Session_ID, Session_Name, Player_ID, Session_open_day, Address, Time,Total_hour, Session_Fee, Committee_ID)International Player (Player_ID, Player_Name, Phone, Address, Email, Salary, User_ID)Training Student (Training_student_ID, Session_ID, ID_card_number)Student (ID_card_number, Name, Phone, Address, Email)b) Data Dictionary entries for all items included in the database design. (10 marks) turn off Name User Table Type Entity Description It contains users detail. This is a table that includes all users password and login name.Data FieldName formatKeyUser_IDCHAR(10)Primary KeyUser_LOGINVARCHAR(20)PasswordVAR CHAR(15)GroupVARCHAR(15)Table Name Coach Table Type Entity Description It contains coachs detail. This is a table that includes the personal information of coach.Data FieldNameFormatKeyCoach_IDCHAR(10)Primary KeyNameVARCHAR(50)AddressVARCHAR(50)PhoneCHAR(8)EmailVARCHAR(30User_IDCHAR(10)Foreign Key reference User tableTable Name Member Table Type Entity Description It contains members detail. This is a table that includes the members membership type, belong to which team and their personal information.Data FieldNameFormatKeyMember_IDCHAR(10)Primary KeyNameVARCHAR(50)ID_card_numberCHAR(8)Date_of_birth encounterMembership_typeCHAR(1)PhoneCHAR(8)AddressVARCHAR(50)EmailVARCHAR(30User_IDCHAR(10)Foreign Key reference User table.On_game_listCHAR(1)Committee_IDCHAR(10)Foreign Key reference Committee table.Team_IDCHAR(10)Foreign Key reference Team table.Table Name Team Table Type Entity Description It contains teams detail. This is a table that includes the name of team, the coach of team, th e captain and the vice captain of the team.Data FieldNameFormatKeyTeam_IDCHAR(10)Primary KeyCoach_IDCHAR(10)Foreign Key reference Coach table.Captain_Member_IDCHAR(10)Vice_Captain_Member_IDCHAR(10)Team_NameVARCHAR(50)Table Name Position Table Type Entity Description It contains position name and unique identifier..Data FieldNameFormatKeyPosition_IDCHAR(10)Primary KeyPosition_NameVARCHAR(50)Table Name Committee Table Type Entity Description It contains committee detail. This is a table that includes the information of the committee is which position of which team.Data FieldNameFormatKeyCommittee_IDCHAR(10)Primary KeyTeam_IDCHAR(10)Foreign Key reference Team table.Position_IDCHAR(10)Foreign Key reference Position table.Table Name Other Team Table Type Entity Description It contains other team detail. The other team is the team which will match with Soccer clubs team. This table includes their name and unique identifier.Data FieldNameFormatKeyOther_team_IDCHAR(10)Primary KeyNameVARCHAR (50)Table Name Training Table Type Entity Description It contains open training sessions detail. It includes the date, time and the trainer.Data FieldNameFormatKeySession_IDCHAR(10)Primary KeyNameVARCHAR(50)Foreign Key reference Coach table.Player_IDCHAR(10)Foreign Key reference International Player tableSession_open_dayDATEAddressVARCHAR(100)TimeTIMETotal_hourCHAR(2)Session_FeeDECIMALCommittee_IDCHAR(10)Table Name Fixture List and Result Table Type Entity Description It contains the fixture list and match result detail.Data FieldNameFormatKeyMatch_IDCHAR(10)Primary KeyTeam_IDCHAR(10)Foreign Key reference Coach table.Other_team_IDCHAR(10)Foreign Key reference International Player tableSession_open_dayDATEAddressVARCHAR(100)TimeTIMETotal_hourCHAR(2)Session_FeeDECIMALCommittee_IDCHAR(10)Table Name International Player Table Type Entity Description It contains the international player (open training session coach) detail. It includes their name, salary and personal contact.Data FieldNa meFormatKeyPlayer_IDCHAR(10)Primary KeyNameVARCHAR(50)PhoneCHAR(8)AddressVARCHAR(100)EmailVARCHAR(50)SalaryDECIMALUser_IDCHAR(10)Foreign Key reference User table.Table Name Training Student Table Type Entity Description It contains link entity of Training and Student tables.Data FieldNameFormatKeyTraining_student_IDCHAR(20)Primary KeySession_IDCHAR(10)Foreign Key reference Training table.Student_IDCHAR(10)Foreign Key reference Student tableTable Name Student Table Type Entity Description It contains the open training sessions student detail. This includes the ID card, name and contact of student.Data FieldNameFormatKeyID_card_numberCHAR(8)Primary KeyNameVARCHAR(50)PhoneCHAR(8)AddressVARCHAR(100)EmailVARCHAR(50)Task 5 Create a prototype user interface for the soccer club system including, as a minimum, the following functionsa) Adding a new member. (5 marks)b) Creating a fixture list for a team. (5 marks)c) Recording a match result. (5 marks)Task 6 You are responsible for organisin g the initial training of the system users and producing the User Guide for the new system.Create an system training plan for the new system including who would be trained, how the session(s) would be organised (e.g. all together, small groups, etc.) (8 marks)This is the training plan of the Soccer club system, the objective is want the user understand more just about the system, and let them user this system smoothly.We have three user groups need to training, Public, Coach and Committee are our target. The public user group we want they know how to use this system to download application form, view the fixture list and view the result of match. The coach user group we want them understand how to allocate team. And the committee user group we want them understand how to create new member, edit member detail, create fixture list, update fixture list, create match result and update match result.We will give training session to each user group and give user guide with print screens to them. And need a computer room let them use the system at the training session.For the public user group we need about 30 minutes to training. The coach user group we need about 60 minutes to training. And the committee user we need about 2 hours to trainingGroupUserSkillMaterialPublicMember and publicDownload application from trip up fixture listView match resultPublic user guideCoachTeam coachAllocation teamCoach user guideCommitteeCommittee memberCreate new memberUpdate member detailCreate fixture listUpdate fixture listCreate match resultUpdate match resultCommittee user guide Create a User Guide for the system. This should not be a house-to-house system manual but a reference document that users can use as a quick guide to the tasks they need to carry out. (10 marks)Task 7 Create a comprehensive, professional standard report describing your system design for the soccer club. This should include the details of tasks 1 6 including the User Guide. annexe1 Colin Bentley, 2002 , NCC Education Managing Business Projects, second edition, Galatea Training Services Limited, Singapore2 Mark Brown, 2002, Project steering in a week, Hodder Stoughton, UK3 Sue Craig, Hadi Jassim, People and Project Management for IT, McGraw-Hill4 Dinsmore, Paul C, 1993, The AMA Handbook of Project Management, New York AMACOM Books, 1993, New York5Lewls, James P, 1995, Fundamentals of Project Management, New York AMACOM Books, 1995, New York6 Toby Teorey, 2008, Database design know it all, Morgan Kaufmann7 M. Vaziri and D. Jackson, Some shortcomings of OCL, the Object Constraint Language of UML, MIT, 1999.8 N. V. Cuong and X. Qafmolla, Meta-model Transformation with Kermeta, in 13th International Conference OBJEKTY 2008 proceedings, p. 109-116.9 Object Management Group, Business process modeling notation, February 2006,