Wednesday, January 15, 2020
Entity Relationship Diagram Analysis
In this undertaking I have to roll up some entity, so an entity attributes and at last ERD.I think I will larn more about entity, attributes, Entity Relationship Diagram to make this undertaking.  Description:  Entity  An Entity is an object or existent thing such as a tabular array or signifier. An Entity contains some information about himself. In the entity some informations can be stored.  Properties  Properties means the information or inside informations of an Entity. Attribute may incorporate assorted sorts of value like numeral, Characters, Integer etc. Simply attributes are the belongingss of entity.Entity Relationship Diagram ( ERD )An entity-relationship diagram is a information mold diagram and technique. ERD can make a graphical representation of the relationships between entities, the entities, and within an information system.  There are three type relationships in the Entity Relationship Diagram ( ERD )  One to One  One to Many  Many to Many  The chief constituents of Entity Relationship Diagram ( ERD )  Entity  Properties  Relationship  CardinalityEntities:Department  Capable Area  Staff  Plan  Faculty  Student  Registration  Examination  Consequence  Coursework  Attendance  AdvancementEntities with Properties:Department  Department_ID ( PK )  Department_Name  Department_Details  Department_Leader  Discipline  Subject_Area_ID ( PK )  Subject_Area_Leader  Subject_Area_Name  Subject_Area_Details  Department_ID ( FK )  Employee  Employee_ID ( PK )  Employee_Leader  Employee_Type  Employee_Name  Employee_JoiningDate  Employee_Address  Department_ID ( FK )  Plan  Program_ID ( PK )  Program_Leader  Program_Name  Program_Type  Program_Details  Subject_Area_ID ( FK )  Registration  Registration_ID ( PK )  Registration_Date  Registration_Type  Registration_cost  Faculty  Module_ID ( PK )  Module_Name  Module_Leader  Module_Details  Module_Type  Student_ID ( FK )  Program_ID ( FK )  Student  Student_ID ( PK )  Student_Name  Student_Type  Student_Details  Student_Address  Module_ID ( FK )  Registration_ID ( FK )  Examination  Exam_ID ( PK )  Exam_Details  Exam_Name  Exam_Date  Exam_Time  Student_ID ( FK )  Consequence  Result_ID ( PK )  Result_Name  Result_Type  Result_Details  Result_Date  Result_time  Exam_ID ( FK )  Coursework  Coursework_ID ( PK )  Coursework_Name  Coursework_Type  Coursework_Details  Student_ID ( FK )  Attendance  Attendance_ID ( PK )  Attendance_Name  Attendance_Type  Attendance_Details  Student_ID ( FK )  Advancement  Progress_ID ( PK )  Progress_Type  Progress_DetailsEntity Relationship Diagram ( ERD ) :Relationship sum-up:In my ERD plot some relation description are given in the below:  In the Entity Relationship Diagram I find out the relation between section and capable country is one to many, because one section may hold many capable countries.  In the scenario I can see one capable country may hold more plans.  In the ERD diagram the relationship between plan and faculty is one to many. Many faculties are under of a plan. Module is used a foreign key of plans.  In the ERD diagram the relationship between pupils and faculties are one to many, because one pupil may hold more than one faculty. In the relationship pupil primary key is used as a foreign key in the faculty entity.  In the ERD diagram the relationship between pupil and test is one to many. One pupil may take part more tests.  In the ERD diagram the relationship between pupil and coursework is one to many. One pupil may take part in the more coursework.  In the ERD diagram the relationship between enrollment and pupil is one to many. The enrollment may be registers for more pupils at same clip.  In the ERD diagram really I see the one to many dealingss. For this ground I include one to many relationships in the ERD diagram. In the existent life for database one to many relationship is perfect to me.DrumheadIn this undertaking I draw an entity relationship diagram. To pull the diagram I find out some entities and properties of entities. To make this undertaking I besides learn about entities, properties and entity relationship diagram.Task-02Introduction:It is said to normalise in the undertaking 2. For doing a database successfully Normalization must be needed. The activities of a database depend on standardization. Standardization helps to do a database rebelliously. In the undertaking I will seek to normalise for a section system in the organisation. The standardization occurs in some stairss. In the undermentioned stairss are given.Description:StandardizationIn the organisation all activities now depend on the computing machine system. Some corporate organisation need dat   abase system for commanding all information. As a consequence database is most popular and indispensable things in the universe. For doing a database successfully standardization is the traditional manner. Without standardization it is impossible to do a database. Standardization is the procedure is used to form the informations absolutely in a database. I normalize the section information for some specific intent. The intent of standardization is divided into two parts. Removing unneeded informations and guaranting informations dependences. If same informations stay in some tabular array together the database may victim. Often it may data in the unrelated tabular array. To work out these jobs we can be done standardization. The intents of standardization are worthy to diminish the sum of infinite a database consumes and guarantee that information is logically stored. The public presentation of database direction system depends on the standardization.  Some stairss are indispensable for standardization. The stairss are given briefly in the followers:Gathering informationsGathering informations is the first measure of standardization. When I normalize I will roll up all information in the phase. I will implement all informations of this measure in the following measure.Choosing a keyFor making standardization a key is indispensable. The key is the chief informations for standardization. All informations depend on the key. The key must be one from garnering informations.First Normal Form ( 1NF )Some functions have to follow in the stairss. Repeating informations in the standardization, sometime it may harmful for standardization, so it necessary to take reiterating informations in the standardization. Removing reiterating informations is the chief work in this undertaking.Second Normal Form ( 2NF )Second normal signifier ( 2NF ) is used to different and take same informations in the database. The phase besides provides farther inform   ation for taking same informations in the database. The chief activities of the phase:  The all informations of first normal signifier must be represented in the phase.  Same information in the rows of database tabular array are removed in the phase.  The relationship of new tabular array is made in the phase.Third Normal Form ( 3NF )In the 3rd normal signifier some activities are occurred. The undermentioned activities are given in the below:  All demands of the 2nd normal signifier are present in the phase.  The activities of the phase is removed some columns that are non dependent upon the primary key. The taking informations and information are non depended on the primary key of tabular array. For this ground these columns informations and information are removed.OptimizationOptimization is the last measure of standardization. I will bring forth the whole standardization by bring forthing a standardization diagram. The standardization diagram is symbol of a better database. If standardization tabular array is clear, informations base become clear.Gathering DatasDepartment_ID  Department_Name  Department_Details  Department_Leader  Capable Area_ID  Capable Area_Leader  Capable Area_Name  Capable Area_Details  employee_ID  employee_Leader  employee _Type  employe _Name  employee_JoiningDate  Staff_Address  Programme_ID  Programme_Leader  Programme_Name  Programme_Type  Programme_Details  Student_ID  Registration_ID  Registration_Date  Registration_Type  Module_ID  Module_Name  Module_Leader  Module_Description  Module-Type  Student_ID  Student_Name  Student_Type  Student_Description  Student_Address  Module_ID  Registration_ID  Exam_ID  Exam_Description  Exam_Name  Exam_Date  Exam_Time  Result_ID  Result_Name  Result_Type  Result_Description  Result_Date  Result_time  Coursework_ ID  Coursework_Name  Coursework_Type  Coursework_Details  Attendance_ID  Attendance_Name  Attendance_Type  Attendance_Details  Progress_ID  Progress_Type  Progress_DetailsChoosing a key:Student_idConverting to 1st Normal Form ( Remove to reiterating informations )Student ( Repeating ) :Department_id  Department_name  Student_id  Student_name  Student_email  Student_phone  Student_address  Study_mode  Employee_id  Employee_name  Employee_phone  Employee_email  Employee_addresses  Sexual activity  Program_id  Program_name  Program_time  Credit_id  Total_course_marks  Total_module_marks  Total_credit  Consequence  Module_id  Module_name  Module_leader  Module_yearCapable Area ( Non Repeating ) :Subjectarea_id  Subjectarea_name  Subjectarea_LeaderConverting to 2nd Normal Form ( Remove parcel cardinal dependance )StudentStudent_id ( pk )  Student name  Student electronic mail  Studentphone  Student reference  Study manner  Program Idaho ( fk )  Programe name  Plan leaderRecognitionRecognition Idaho ( pk )  Student Idaho ( fk )  Entire coursework grade  Exam grade  Module grade  Entire recognition  ConsequenceFacultyModule Idaho ( pk  Module leader  Faculty name  Programe Idaho ( fk )  Programe nameEmployeeEmployee Idaho ( pk )  Employee name  Employee electronic mail  Employee phone  Employee reference  Sexual activity  Depatment Idaho ( fk )  Department nameDepartmentDepartment Idaho ( pk )  Department namePlanProgram Idaho ( pk )  Capable country Idaho ( fk )  Capable country name  Programe name  Plan leaderCapable countryCapable country Idaho ( pk )  Capable country name  Department Idaho ( fk )  Department name  Capable country leaderConverting to 3rd Normal Form: ( Remove not cardinal dependence ) :DepartmentDepartment_id ( PK )  Department_nameCapable AreaSubjectarea_id ( PK )  Subjectarea_name  Department_id ( FK )  Subjectarea_Leader ( FK )EmployeeEmployee_id ( PK )  Employee_name  Employee_phone  Employee_email  Employee_addresses  Sexual activity  Department_id ( FK )Student_moduleStudent_id ( PK )  Module_id ( PK )PlanProgram_id ( PK )  Subjetarea_id ( FK )  Program_leader ( FK )  Program_name  Program_timeFacultyModule_id ( PK )  Module_name  Module_leader ( FK )  Module_year  Program_id ( FK )StudentStudent_id ( PK )  Student_name  Student_email  Student_phone  Student_address  Study_mode  Program_id ( FK )RecognitionCredit_id ( PK )  Student_id ( FK )  Module_id ( FK )  Total_course_marks  Total_module_marks  Total_credit  ConsequenceOptimization:Summary:In the undertaking I normalized for a section. I normalize for keeping database direction system. To make this undertaking I analyzed about standardization. I think I normalized good. Clear standardization helps to do a better database direction system. I learned more about standardization to make this undertaking.Undertaking 3Introduction:The undertaking 3 contains some subjects. Database Management System ( DBMS ) is component of the undertaking. I will make a database by utilizing Database Management System ( DBMS ) . There are some ways to do database. But I will make database in the SQL waiter, because it is easy and flexible to me. To do database I will do some tabular array, each tabular array will incorporate minimal 5 records.Description:Some stairss I followed to make this undertaking. The stairss and demands are given in the below:Database Management System ( DBMS ) :To pull off a database some strong functions are followed. Database directi   on system is a sort of environment where all sorts ââ¬Ë functions and ordinance are included. A database direction system ( DBMS ) works as a database director. Database Management System ( DBMS ) is computing machine plan or package. The package helps others computing machine users create and entree informations in a database. Anyone can entree the information, where information is located it is non fact, It manages user petitions so that users and other plans are free from holding to understand informations in a multi-user system, on storage media and, who else may besides be accessing the information. Database direction system checks the unity of the database. The DBMS besides manage the hallmark procedure, merely authorized user and authorised web can entree the database. DBMS helps to do a secure database. Database direction system ââ¬Ës environment helps to do a good relationship in the database.The activities for this undertaking are following:MY database:Generated Scri   pt from ââ¬Å" Generate SQL Server Scripts Wizard â⬠ :SET ANSI_NULLS ON  Travel  SET QUOTED_IDENTIFIER ON  Travel  IF NOT EXISTS ( SELECT * FROM sys.objects WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ section ] ââ¬Ë ) AND type in ( N'U ââ¬Ë ) )  Get down  CREATE TABLE [ dbo ] . [ section ] (  [ department_id ] [ nchar ] ( 10 ) NOT NULL,  [ department_name ] [ nvarchar ] ( 50 ) NULL,  CONSTRAINT [ PK_department ] PRIMARY KEY CLUSTERED([ department_id ] ASC  ) WITH ( IGNORE_DUP_KEY = OFF ) ON [ PRIMARY ]  ) ON [ PRIMARY ]  End  Travel  SET ANSI_NULLS ON  Travel  SET QUOTED_IDENTIFIER ON  Travel  IF NOT EXISTS ( SELECT * FROM sys.objects WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ employee ] ââ¬Ë ) AND type in ( N'U ââ¬Ë ) )  Get down  CREATE TABLE [ dbo ] . [ employee ] (  [ employee_id ] [ nchar ] ( 10 ) NOT NULL,  [ employee_name ] [ nvarchar ] ( 50 ) NULL,  [ employee_email ] [ nvarchar ] ( 50 ) NULL,  [ employee_phon ] [ int ] NULL,  [ employee_address ] [ nvarchar ] ( 50 ) NULL,  [ department_id ] [ nchar ] ( 10 ) NULL,  [ sex ] [ nvarchar ] ( 1 ) NULL,  CONSTRAINT [ PK_employee ] PRIMARY KEY CLUSTERED([ employee_id ] ASC  ) WITH ( IGNORE_DUP_KEY = OFF ) ON [ PRIMARY ]  ) ON [ PRIMARY ]  End  Travel  SET ANSI_NULLS ON  Travel  SET QUOTED_IDENTIFIER ON  Travel  IF NOT EXISTS ( SELECT * FROM sys.objects WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ subjectarea ] ââ¬Ë ) AND type in ( N'U ââ¬Ë ) )  Get down  CREATE TABLE [ dbo ] . [ subjectarea ] (  [ subjectarea_id ] [ nchar ] ( 10 ) NOT NULL,  [ subjectarea_name ] [ nvarchar ] ( 50 ) NULL,  [ department_id ] [ nchar ] ( 10 ) NOT NULL,  [ subjectarea_leader ] [ nchar ] ( 10 ) NOT NULL,  CONSTRAINT [ PK_subjectarea ] PRIMARY KEY CLUSTERED([ subjectarea_id ] ASC  ) WITH ( IGNORE_DUP_KEY = OFF ) ON [ PRIMARY ]  ) ON [ PRIMARY ]  End  Travel  SET ANSI_NULLS ON  Travel  SET QUOTED_IDENTIFIER ON  Travel  IF NOT EXISTS ( SELECT * FROM sys.objects WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ plan ] ââ¬Ë ) AND type in ( N'U ââ¬Ë ) )  Get down  CREATE TABLE [ dbo ] . [ plan ] (  [ program_id ] [ nchar ] ( 10 ) NOT NULL,  [ subjectarea_id ] [ nchar ] ( 10 ) NULL,  [ program_name ] [ nvarchar ] ( 50 ) NULL,  [ program_leader ] [ nchar ] ( 10 ) NULL,  [ program_time ] [ nvarchar ] ( 50 ) NULL,  CONSTRAINT [ PK_program ] PRIMARY KEY CLUSTERED([ program_id ] ASC  ) WITH ( IGNORE_DUP_KEY = OFF ) ON [ PRIMARY ]  ) ON [ PRIMARY ]  End  Travel  SET ANSI_NULLS ON  Travel  SET QUOTED_IDENTIFIER ON  Travel  IF NOT EXISTS ( SELECT * FROM sys.objects WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ faculty ] ââ¬Ë ) AND type in ( N'U ââ¬Ë ) )  Get down  CREATE TABLE [ dbo ] . [ faculty ] (  [ module_id ] [ nchar ] ( 10 ) NOT NULL,  [ program_id ] [ nchar ] ( 10 ) NULL,  [ module_leader ] [ nchar ] ( 10 ) NULL,  [ module_name ] [ nvarchar ] ( 50 ) NULL,  [ twelvemonth ] [ nchar ] ( 10 ) NULL,  CONSTRAINT [ PK_module ] PRIMARY KEY CLUSTERED([ module_id ] ASC  ) WITH ( IGNORE_DUP_KEY = OFF ) ON [ PRIMARY ]  ) ON [ PRIMARY ]  End  Travel  SET ANSI_NULLS ON  Travel  SET QUOTED_IDENTIFIER ON  Travel  IF NOT EXISTS ( SELECT * FROM sys.objects WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ pupil ] ââ¬Ë ) AND type in ( N'U ââ¬Ë ) )  Get down  CREATE TABLE [ dbo ] . [ pupil ] (  [ student_id ] [ nchar ] ( 10 ) NOT NULL,  [ student_name ] [ nvarchar ] ( 50 ) NULL,  [ student_email ] [ nvarchar ] ( 50 ) NULL,  [ student_phon ] [ int ] NULL,  [ student_address ] [ nvarchar ] ( 100 ) NULL,  [ program_id ] [ nchar ] ( 10 ) NULL,  [ StudyMode ] [ nchar ] ( 10 ) NULL,  CONSTRAINT [ PK_student ] PRIMARY KEY CLUSTERED([ student_id ] ASC  ) WITH ( IGNORE_DUP_KEY = OFF ) ON [ PRIMARY ]  ) ON [ PRIMARY ]  End  Travel  SET ANSI_NULLS ON  Travel  SET QUOTED_IDENTIFIER ON  Travel  IF NOT EXISTS ( SELECT * FROM sys.objects WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ student_module ] ââ¬Ë ) AND type in ( N'U ââ¬Ë ) )  Get down  CREATE TABLE [ dbo ] . [ student_module ] (  [ student_id ] [ nchar ] ( 10 ) NOT NULL,  [ module_id ] [ nchar ] ( 10 ) NOT NULL,  CONSTRAINT [ PK_student_module ] PRIMARY KEY CLUSTERED([ student_id ] ASC,  [ module_id ] ASC  ) WITH ( IGNORE_DUP_KEY = OFF ) ON [ PRIMARY ]  ) ON [ PRIMARY ]  End  Travel  SET ANSI_NULLS ON  Travel  SET QUOTED_IDENTIFIER ON  Travel  IF NOT EXISTS ( SELECT * FROM sys.objects WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ recognition ] ââ¬Ë ) AND type in ( N'U ââ¬Ë ) )  Get down  CREATE TABLE [ dbo ] . [ recognition ] (  [ credit_id ] [ nchar ] ( 10 ) NOT NULL,  [ student_id ] [ nchar ] ( 10 ) NULL,  [ module_id ] [ nchar ] ( 10 ) NULL,  [ total_coursework_marks ] [ int ] NULL,  [ exam_marks ] [ int ] NULL,  [ total_module_marks ] [ int ] NULL,  [ total_credits ] [ int ] NULL,  [ consequence ] [ nchar ] ( 10 ) NULL,  CONSTRAINT [ PK_credit ] PRIMARY KEY CLUSTERED([ credit_id ] ASC  ) WITH ( IGNORE_DUP_KEY = OFF ) ON [ PRIMARY ]  ) ON [ PRIMARY ]  End  Travel  IF NOT EXISTS ( SELECT * FROM sys.foreign_keys WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ FK_employee_department ] ââ¬Ë ) AND parent_object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ employee ] ââ¬Ë ) )  ALTER TABLE [ dbo ] . [ employee ] WITH CHECK ADD CONSTRAINT [ FK_employee_department ] FOREIGN KEY ( [ department_id ] )  REFERENCES [ dbo ] . [ section ] ( [ department_id ] )  Travel  IF NOT EXISTS ( SELECT * FROM sys.foreign_keys WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ FK_subjectarea_department ] ââ¬Ë ) AND parent_object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ subjectarea ] ââ¬Ë ) )  ALTER TABLE [ dbo ] . [ subjectarea ] WITH CHECK ADD CONSTRAINT [ FK_subjectarea_department ] FOREIGN KEY ( [ department_id ] )  REFERENCES [ dbo ] . [ section ] ( [ department_id ] )  Travel  IF NOT EXISTS ( SELECT * FROM sys.foreign_keys WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ FK_subjectarea_employee ] ââ¬Ë ) AND parent_object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ subjectarea ] ââ¬Ë ) )  ALTER TABLE [ dbo ] . [ subjectarea ] WITH CHECK ADD CONSTRAINT [ FK_subjectarea_employee ] FOREIGN KEY ( [ subjectarea_leader ] )  REFERENCES [ dbo ] . [ employee ] ( [ employee_id ] )  Travel  IF NOT EXISTS ( SELECT * FROM sys.foreign_keys WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ FK_program_employee ] ââ¬Ë ) AND parent_object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ plan ] ââ¬Ë ) )  ALTER TABLE [ dbo ] . [ plan ] WITH CHECK ADD CONSTRAINT [ FK_program_employee ] FOREIGN KEY ( [ program_leader ] )  REFERENCES [ dbo ] . [ employee ] ( [ employee_id ] )  Travel  IF NOT EXISTS ( SELECT * FROM sys.foreign_keys WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ FK_program_subjectarea ] ââ¬Ë ) AND parent_object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ plan ] ââ¬Ë ) )  ALTER TABLE [ dbo ] . [ plan ] WITH CHECK ADD CONSTRAINT [ FK_program_subjectarea ] FOREIGN KEY ( [ subjectarea_id ] )  REFERENCES [ dbo ] . [ subjectarea ] ( [ subjectarea_id ] )  Travel  IF NOT EXISTS ( SELECT * FROM sys.foreign_keys WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ FK_module_employee ] ââ¬Ë ) AND parent_object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ faculty ] ââ¬Ë ) )  ALTER TABLE [ dbo ] . [ faculty ] WITH CHECK ADD CONSTRAINT [ FK_module_employee ] FOREIGN KEY ( [ module_leader ] )  REFERENCES [ dbo ] . [ employee ] ( [ employee_id ] )  Travel  IF NOT EXISTS ( SELECT * FROM sys.foreign_keys WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ FK_module_program ] ââ¬Ë ) AND parent_object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ faculty ] ââ¬Ë ) )  ALTER TABLE [ dbo ] . [ faculty ] WITH CHECK ADD CONSTRAINT [ FK_module_program ] FOREIGN KEY ( [ program_id ] )  REFERENCES [ dbo ] . [ plan ] ( [ program_id ] )  Travel  IF NOT EXISTS ( SELECT * FROM sys.foreign_keys WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ FK_student_program ] ââ¬Ë ) AND parent_object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ pupil ] ââ¬Ë ) )  ALTER TABLE [ dbo ] . [ pupil ] WITH CHECK ADD CONSTRAINT [ FK_student_program ] FOREIGN KEY ( [ program_id ] )  REFERENCES [ dbo ] . [ plan ] ( [ program_id ] )  Travel  IF NOT EXISTS ( SELECT * FROM sys.foreign_keys WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ FK_student_module_module ] ââ¬Ë ) AND parent_object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ student_module ] ââ¬Ë ) )  ALTER TABLE [ dbo ] . [ student_module ] WITH CHECK ADD CONSTRAINT [ FK_student_module_module ] FOREIGN KEY ( [ module_id ] )  REFERENCES [ dbo ] . [ faculty ] ( [ module_id ] )  Travel  IF NOT EXISTS ( SELECT * FROM sys.foreign_keys WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ FK_student_module_student ] ââ¬Ë ) AND parent_object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ student_module ] ââ¬Ë ) )  ALTER TABLE [ dbo ] . [ student_module ] WITH CHECK ADD CONSTRAINT [ FK_student_module_student ] FOREIGN KEY ( [ student_id ] )  REFERENCES [ dbo ] . [ pupil ] ( [ student_id ] )  Travel  IF NOT EXISTS ( SELECT * FROM sys.foreign_keys WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ FK_credit_module ] ââ¬Ë ) AND parent_object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ recognition ] ââ¬Ë ) )  ALTER TABLE [ dbo ] . [ recognition ] WITH CHECK ADD CONSTRAINT [ FK_credit_module ] FOREIGN KEY ( [ module_id ] )  REFERENCES [ dbo ] . [ faculty ] ( [ module_id ] )  Travel  IF NOT EXISTS ( SELECT * FROM sys.foreign_keys WHERE object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ FK_credit_student ] ââ¬Ë ) AND parent_object_id = OBJECT_ID ( N ââ¬Ë [ dbo ] . [ recognition ] ââ¬Ë ) )  ALTER TABLE [ dbo ] . [ recognition ] WITH CHECK ADD CONSTRAINT [ FK_credit_student ] FOREIGN KEY ( [ student_id ] )  REFERENCES [ dbo ] . [ pupil ] ( [ student_id ] )Summary:I used SQL waiter for doing database. I draw the diagram by utilizing normalized diagram. Some tabular arraies I created to bring forth the diagram of database. I included all table mean five records. To make the undertaking absolutely I show all tabular arraies screen shot with records.Undertaking 4IntroductionThe chief activities are said in the undertaking. In the undertaking I will quire of my database. Now in the undertaking I will seek to implement. I will verify the operation of database. I will quire of the database harmonizing the outlook of the undertaking. I will follow the activities harmonizing the undertaking.Description:In the undertaking I have to make questions for find out some demands these are said to make in the undertaking. In the undermentioned these activities are given in the below:1.Name callings of all the Subject Area Leaders ( SALs )Querie:SELECT dbo.subjectarea.subjectarea_leader, dbo.employee.empl   oyee_name, dbo.subjectarea.subjectarea_name  FROM dbo.employee INNER JOIN  dbo.subjectarea ON dbo.employee.employee_id = dbo.subjectarea.subjectarea_leaderEnd product:PLs along with the name ( s ) of the capable countryQuerie:SELECT dbo.program.program_leader, dbo.employee.employee_id, dbo.program.program_name  FROM dbo.employee INNER JOIN  dbo.program ON dbo.employee.employee_id = dbo.program.program_leaderEnd product:MLs along with the name ( s ) of the capable countrySELECT dbo.module.module_leader, dbo.employee.employee_name, dbo.module.module_name  FROM dbo.employee INNER JOIN  dbo.module ON dbo.employee.employee_id = dbo.module.module_leader2. Expose the undermentioned information for the ââ¬Å" Artificial Intelligence â⬠ capable country:a ) The list of plans that belong to that capable country ;Querie:SELECT program_name  FROM dbo.program  WHERE ( subjectarea_id = ââ¬Ësa-03 ââ¬Ë )End product:B ) The list of faculties that belong to these plans ;Querie:SELECT dbo.program.program_id, dbo.module.module_name  FROM dbo.program INNER JOIN  dbo.module ON dbo.program.program_id = dbo.module.program_id  WHERE ( dbo.program.subjectarea_id = ââ¬Ësa-03 ââ¬Ë )degree Celsius ) The list of pupils who have awarded a Pass for one of the facultiesQuerie:SELECT DISTINCT C.student_id, student.student_name, C.module_id, module.module_name, C.result  FROM recognition AS C INNER JOIN  faculty ON C.module_id = module.module_id INNER JOIN  pupil ON C.student_id = student.student_id INNER JOIN  plan ON module.program_id = program.program_id AND student.program_id = program.program_id INNER JOIN  subjectarea ON program.subjectarea_id = subjectarea.subjectarea_id  WHERE ( C.result = ââ¬Ëpass ââ¬Ë ) AND ( subjectarea.subjectarea_id = ââ¬Ësa-03 ââ¬Ë )End product:3. Expose the name of all the pupils who belong to one plan ââ¬â you can take which plan ââ¬â of the ââ¬Å" Database â⬠ capable country, along with the undermentioned information:a ) Their twelvemonth of survey ;Querie:SELECT DISTINCT dbo.student.student_id, dbo.student.student_name, dbo.program.program_id, dbo.program.program_name, dbo.module.year  FROM dbo.student INNER JOIN  dbo.program ON dbo.student.program_id = dbo.program.program_id INNER JOIN  dbo.module ON dbo.program.program_id = dbo.module.program_id INNER JOIN  dbo.student_module ON dbo.student.student_id = dbo.student_module.student_id AND dbo.module.module_id = dbo.student_module.module_id  WHERE ( dbo.program.subjectarea_id = ââ¬Ësa-01 ââ¬Ë )End product:B ) The faculties they study ;Querie:SELECT DISTINCT  dbo.student.student_id, dbo.student.student_name, dbo.module.module_name, dbo.student_module.module_id, dbo.student.program_id,  dbo.program.program_name  FROM dbo.student INNER JOIN  dbo.program ON dbo.student.program_id = dbo.program.program_id INNER JOIN  dbo.module ON dbo.program.program_id = dbo.module.program_id INNER JOIN  dbo.student_module ON dbo.student.student_id = dbo.student_module.student_id AND dbo.module.module_id = dbo.student_module.module_id  WHERE ( dbo.program.subjectarea_id = ââ¬Ësa-01 ââ¬Ë )End product:degree Celsiuss ) Their test and coursework Markss for these facultiesQuerie:SELECT dbo.credit.student_id, dbo.student.student_name, dbo.credit.module_id, dbo.module.module_name, dbo.credit.total_coursework_marks, dbo.credit.exam_marks, dbo.student.program_id  FROM dbo.credit INNER JOIN  dbo.module ON dbo.credit.module_id = dbo.module.module_id INNER JOIN  dbo.student ON dbo.credit.student_id = dbo.student.student_id INNER JOIN  dbo.program ON dbo.module.program_id = dbo.program.program_id AND dbo.student.program_id = dbo.program.program_id  where program.subjectarea_id='sa-01 ââ¬ËEnd product:Summary:Some quires are done in the undertaking harmonizing the functions of assignment. I finished the undertaking really carefully. As a proven I show some screen shooting of quires. I besides show SQL quires in the assignment.Undertaking 5Introduction:There are five undertakings in the assignment. Each undertaking is made for a specific and different subject. Such a undertaking is task 5. In the undertaking 5 I will seek to stand for a study for whole assignment. The study will incorporate the description of my system design for a section of an organisation. In this study I will besides include the inside informations information about undertaking one to five.DescriptionIn the phase I will seek to give a solution for this study.TitleReport no- Database Design and Development  Recipient- Mrs Jesmin Aktar  Author- Shanta MariaIntroduction of my premise:The rubric of the assignment is College Database Development. The college needs a computerized system for keeping the activities of a section. To keeping the section activities the college needs an ideal database direction system. To complete these activities of this assignment I mentioned each subject for the assignment in the separately. I think I learned more things as pupil, to make this assignment. After completing each undertaking right I will bring forth a study for discover my accomplishment on my analysis, design and thought accomplishment.Overview of whole assignment:The sum-up of the whole assignment, I want to bring forth a study. The study is given at the below:Undertaking 1EntityAn Entity is a existent thing such as a tabular array or signifier. An Entity contains some information about himself. The information of entity can assist for designation of entity.PropertiesAttributes refers the inside informations information of    an Entity. There are many types are fixed for property. These values are like numeral, Characters, Integer etc. Properties are the chief belongings of entities.Entity Relationship Diagram ( ERD )An entity-relationship diagram is a diagram for informations patterning. Entity relationship diagram ensures the relationships between entities, the entities, and within an information system. Entity relationship diagram makes a database good understand.  There are three type relationships in the Entity Relationship Diagram ( ERD )  One to One  One to Many  Many to Many  The chief constituents of Entity Relationship Diagram ( ERD )  Entity  Properties  Relationship  CardinalityUndertaking 2StandardizationSome corporate organisation need database system for commanding all information. To command information of organisation database must be needed. As a consequence database is most popular and indispensable things in the universe. Without standardization it is impossible to do a database. Standardization is the procedure is used to form the informations absolutely in a database. I normalize the section information for some specific intent. The intents of standardization are worthy to diminish the sum of infinite a database consumes and guarantee that information is logically stored. The public presentation of database direction system depends on the standardization.  Some stairss are indispensable for standardization.  In the assignment I followed some stairss for standardization. The stairss are given in the below:  Gathering informations  Choosing a key  First Normal Form ( 1NF )  Second Normal Form ( 2NF )  Third Normal Form ( 3NF )  OptimizationUndertaking 3I used SQL waiter to do database in this undertaking. Making database was the function of the undertaking. As a consequence I designed a diagram and a database in the undertaking.Undertaking 4The undertaking holds information for SQL quires. Harmonizing the undertaking some quires are made to use in the database. To make SQL quires in the undertaking I learned more things about SQL bid and other secure information of SQL waiter.Footings of mention:The scope for investigated system is extended. All the inside informations about the system hold given. The current system and the new system image are clear in the scenario. Anyone can see and compare the scenario.  The study focuses on the section of an organisation. The study is bring forthing with a inside informations description and information of the complete system analysis and design portion for the section of an organisation.Procedures and methods:In my assignment I used some techniques. I have investigated all the process in many ways. In the assignment I followed the operation and practically system of college and others pull offing activities. The chief process and method of the assignment is to settle the current system jobs and besides to present an ideal database system of the academy theatre for keeping the section procedure.  In this assignment I used entity relationship diagram and other demands and processs.Recommendation:Harmonizing the users demands and after probe the system, I could happen out some jobs and some other job in the college development diagram. The keeping system of the college development diagram was really hard to pull off. To work out the jobs I provide the new IT system. I will seek and bring forth the really easy manner to pull off the college development diagram for keeping procedure or systems in the new database system of College Database Development.  Requirement hardware: To set up the procedure some hardware and package are really indispensable. The name or hardware demands are given in the followers:  Personal computer ( Include all hardware )  Network Connection  SQL waiter  Windows XP  .NET modelFuture program for my database:In the assignment I produced a database direction system for a college section. There are many sections of the college. I will include more information about more sections in the database at future. To implement my database I will utilize latest tools. I will seek to happen how manner I can implement the database.Appendix:Entity Relationship Diagram ( ERD ) :Optimization diagram:DatabaseSummary:There are five undertakings in the assignment. The assignment contains some subjects of database. As a pupil any one can larn about database direction system from the topic. The undertaking five contains information of an premise. In the undertaking I tried to supply an ideal premise about the whole assignment.    
Subscribe to:
Post Comments (Atom)
 
 
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.