Download Database Solution for Polly Pipe and more Assignments Computer science in PDF only on Docsity!
Higher Nationals
Internal verification of assessment decisions – BTEC (RQF)
INTERNAL VERIFICATION – ASSESSMENT DECISIONS Programme title BTEC HND in Computing Assessor Abdur Rahman Internal Verifier Unit(s) Unit 04: Database Design & Development Assignment title Database Solution for Polly Pipe Student’s name M D H S Gunathilake List which assessment criteria the Assessor has awarded. Pass Merit Distinction INTERNAL VERIFIER CHECKLIST Do the assessment criteria awarded match those shown in the assignment brief? Y/N Is the Pass/Merit/Distinction grade awarded justified by the assessor’s comments on the student work? Y/N Has the work been assessed accurately? Y/N Is the feedback to the student: Give details:
- Constructive?
- Linked to relevant assessment criteria?
- Identifying opportunities for improved performance?
- Agreeing actions? Y/N Y/N Y/N Y/N Does the assessment decision need amending? Y/N Assessor signature Date Internal Verifier signature Date Programme Leader signature (if required) Date Confirm action completed Remedial action taken Give details: Assessor signature Date Internal Verifier signature Date Programme Leader signature (if required) Date
Higher Nationals - Summative Assignment Feedback Form
Student Name/ID M D H S Gunathilake / E Unit Title Unit 0^4 :^ Database Design & Development Assignment Number 1 Assessor Abdur Rahman Submission Date 15/09/2022 (^) Date Received 1st submission Re-submission Date Date Received 2nd submission Assessor Feedback: LO1 Use an appropriate design tool to design a relational database system for a substantial problem Pass, Merit & Distinction Descripts
P1 M1 D
LO2 Develop a fully functional relational database system, based on an existing system design Pass, Merit & Distinction Descripts P 2 P3 M (^2) M3 D LO3 Test the system against user and system requirements. Pass, Merit & Distinction Descripts P 4 M 4 D 2 LO4 Produce technical and user documentation. Pass, Merit & Distinction Descripts P 5 M 5 D Grade: Assessor Signature: Date: Resubmission Feedback: Grade: Assessor Signature: Date: Internal Verifier’s Comments: Signature & Date:
- Please note that grade decisions are provisional. They are only confirmed once internal and external moderation has taken place and grades decisions have been agreed at the assessment board.
Pearson Higher Nationals in
Computing
Unit 04: Database Design & Development
Assignment 01
General Guidelines
- A Cover page or title page – You should always attach a title page to your assignment. Use previous page as your cover sheet and make sure all the details are accurately filled.
- Attach this brief as the first section of your assignment.
- All the assignments should be prepared using a word processing software.
- All the assignments should be printed on A4 sized papers. Use single side printing.
- Allow 1” for top, bottom , right margins and 1.25” for the left margin of each page. Word Processing Rules
- The font size should be 12 point, and should be in the style of Time New Roman.
- Use 1.5 line spacing. Left justify all paragraphs.
- Ensure that all the headings are consistent in terms of the font size and font style.
- Use footer function in the word processor to insert Your Name, Subject, Assignment No, and Page Number on each pag e. This is useful if individual sheets become detached for any reason.
- Use word processing application spell check and grammar check function to help editing your assignment. Important Points:
- It is strictly prohibited to use textboxes to add texts in the assignments, except for the compulsory information. eg: Figures, tables of comparison etc. Adding text boxes in the body except for the before mentioned compulsory information will result in rejection of your work.
- Carefully check the hand in date and the instructions given in the assignment. Late submissions will not be accepted.
- Ensure that you give yourself enough time to complete the assignment by the due date.
- Excuses of any nature will not be accepted for failure to hand in the work on time.
- You must take responsibility for managing your own time effectively.
- If you are unable to hand in your assignment on time and have valid reasons such as illness, you may apply (in writing) for an extension.
- Failure to achieve at least PASS criteria will result in a REFERRAL grade.
- Non-submission of work without valid reasons will lead to an automatic RE FERRAL. You will then be asked to complete an alternative assignment.
- If you use other people’s work or ideas in your assignment, reference them properly using HARVARD referencing system to avoid plagiarism. You have to provide both in-text citation and a reference list.
- If you are proven to be guilty of plagiarism or any academic misconduct, your grade could be reduced to A REFERRAL or at worst you could be expelled from the course
Student Declaration I hereby, declare that I know what plagiarism entails, namely to use another’s work and to present it as my own without attributing the sources in the correct form. I further understand what it means to copy another’s work.
- I know that plagiarism is a punishable offence because it constitutes theft.
- I understand the plagiarism and copying policy of Edexcel UK.
- I know what the consequences will be if I plagiarise or copy another’s work in any of the assignments for this program.
- I declare therefore that all work presented by me for every aspect of my program, will be my own, and where I have made use of another’s work, I will attribute the source in the correct way.
- I acknowledge that the attachment of this document signed or not, constitutes a binding agreement between myself and Pearson, UK.
- I understand that my assignment will not be considered as submitted if this document is not attached to the assignment. Student’s Signature: [email protected] Date: 15/09/ ( Provide E-mail ID ) ( Provide Submission Date )
Higher National Diploma in Computing
Assignment Brief
Student Name /ID Number (^) M D H S Gunathilake / E Unit Number and Title Unit 4: Database Design & Development Academic Year (^2022) /2 3 Unit Tutor Assignment Title Data base system for^ Polly Pipe Issue Date Submission Date (^) 15/09/ IV Name & Date Submission format Part 1: The submission should be in the form of an individual written report written in a concise, formal business style using single spacing and font size 12. You are required to make use of headings, paragraphs and subsections as appropriate, and all work must be supported with research and referenced using Harvard referencing system. Please also provide in-text citation and bibliography using Harvard referencing system. The recommended word limit is 3 ,000– 3 ,500 words, although you will not be penalised for exceeding the total word limit. Part 2: The submission should be in the form of a fully functional relational database system demonstrated to the Tutor; and an individual written report (please see details in Part 1 above). Part 3: The submission should be in the form of a witness statement of the testing completed by the Tutor; technical documentation; and a written report (please see details in Part 1 above). Unit Learning Outcomes: LO1 Use an appropriate design tool to design a relational database system for a substantial problem. LO2 Develop a fully functional relational database system, based on an existing system design. LO3 Test the system against user and system requirements. LO4 Produce technical and user documentation. Assignment Brief and Guidance:
Instillation Management Form Installation ID Installation Type Installation Name and Address Customer Equipment Types of Staff Required Period of Staff assignm ent 234 Freshwater Tropical Oak House, 17 Wroxton Road, Hertfordsh ire, H5 667 Lee A. sun 2 air pumps 200 gallons fish tank 1 x standard thermostat 1 x Carpenter 1 x Aquatics installer 1 x Electrician From 1st Septemb er 2012 654 Freshwater Cold Bayliss House, Orange Street, Kent, K 988 Sally Dench 2 air pumps 200 gallons fish tank Large Gravel Bag 2 x standard thermostat s 5 x Carpenters 1 x Installation Manager 1 x Aquatics installer 1 x Plumber 3 x Labourers 1 st June 2005 – 1 st June 2011 767 Marine Eaglestone Castle, Eaglestone , Kent Perry Vanderru ne 2 x 200 gallons fish tanks 500 Wood panels 10 x Carpenters 2 x Installation Manager 1 x Aquatics installer 1 x Plumber 3 x Labourers From 30 th June 2012 943 Marine 23 Sackville Street, Wilts. W Eric Mackinto sh 2 air pumps 200 gallons fish tank 1 x standard thermostat No staff required 157 Freshwater Tropical Humbertso n Castle, Kent, K Perry Vanderru ne 2 air pumps 400 gallons fish tank 3 x standard thermostat 1 x Aquatics installer 1 st Septemb er 2005
Activity 1
1.1. Identify the user and system requirements to design a database for the above scenario and design a relational database system using conceptual design (ER Model) by including identifiers (primary Key) of entities and cardinalities, participations of relationships. Convert the ER Model into logical database design using relational database model including primary keys foreign keys and referential Integrities. It should contain at least five interrelated tables. Check whether the provided logical design is normalised. If not, normalize the database by removing the anomalies. (Note:-It is allowed to have your own assumptions and related attributes within the scope of the case study given)
1.2. Design set of simple interfaces to input and output for the above scenario using
Wireframe or any interface-designing tool. Evaluate the effectiveness of the given design (ERD and Logical design) in terms of the identified user and system requirements.
Activity 2
Activity 2. a. Develop a relational database system according to the ER diagram you have created (Use SQL DDL statements). Provide evidence of the use of a suitable IDE to create a simple interface to insert, update and delete data in the database. Implement proper security mechanisms in the developed database. Evaluate the database solution developed and its effectiveness with relevant to the user and system requirements identified, system security mechanisms (EX: - User groups, access permissions) and the maintenance of the database. Activity 2. a. Explain the usage of DML with below mentioned queries by giving at least one single example per each case from the developed database. Assess the usage of the below SQL statements with the examples from the developed database to prove that the data extracted through them are meaningful and relevant to the given scenario. Select/ Where / Update / Between / In / Group by / Order by / Having
Grading Criteria Achieved Feedback LO1 Use an appropriate design tool to design a relational database system for a substantial problem P1 Design a relational database system using appropriate design tools and techniques, containing at least four interrelated tables, with clear statements of user and system requirements. M1 Produce a comprehensive design for a fully functional system that includes interface and output designs, data validations and data normalization. D1 Evaluate the effectiveness of the design in relation to user and system requirements.
LO2 Develop a fully functional relational database system, based on an existing system design P2 Develop the database system with evidence of user interface, output, and data validations, and querying across multiple tables. P3 Implement a query language into the relational database system M2 Implement a fully functional database system that includes system security and database maintenance. M3 Assess whether meaningful data has been extracted using query tools to produce appropriate management information.
Table of Contents
- Acknowledgment
- Introduction
- Activity 01..........................................................................................................................
- 1.1 Requirements
- 1.1.1 User Requirements
- 1.1.2 System Requirements..............................................................................................
- 1.1.2.1 Software Specification
- 1.1.2.2 Hardware Specification:
- 1.1.3 Design Requirements
- 1.2 Entity Relationship Diagram (ER Diagram)
- 1.2.1 Notations and Symbols of Entity Relationship Diagram
- 1.2.2 Entity Relationship Diagram for the M/s Polly Pipe
- 1.3 Relational Database Model
- 1.3.1 Structured Query Language (SQL)
- 1.4 Logical Database Design
- 1.5 Relational Mapping
- 1.6 Normalization
- 1.7 Data Validation
- 1.7.1 Different Kind of Data Validation
- 1.7.2 Types of Data Validation
- 1.7.3 Data Validation Constraints
- 1.7.4 Performing Data Validation
- 1.8 Simple Interfaces for Polly Pipe Management System using Wireframe..............
- 1.9 Interfaces for Poly Pipe Management System
- 1.10 Justification of Effectiveness
- 1.11 Summary
- Activity 02..........................................................................................................................
- 2.1 Data Definition Language (DDL)
- 2.1.1 Why use DDL
- 2.1.2 Commands in Data Definition Language
- 2.2 Data Manipulation
- 2.2.1 Why Use DML
- 2.2.2 Commands in Data Manipulation Language
- 2.2.3 Process of Data Manipulation
- 2.3 Data Types
- 2.4 SQL Commands Use to Develop Poly Pipe Management System
- 2.4.1 DDL and DML Commands
- 2.4.2 Join Command
- 2.4.3 Aggregation Command
- 2.5 Integrated Development Environment
- 2.6 Microsoft Visual Studio
- 2.7 Connection of Database
- 2.8 Database Protection
- 2.8.1 Threats and Challenges for Database Security
- 2.8.2 Database Protection Tools and Platforms
- 2.8.3 Security Mechanism for Poly Pipe Management System
- 2.9 Summary
- Activity 03........................................................................................................................
- 3.1 Testing...................................................................................................................
- 3.1.1 Levels of Testing...................................................................................................
- 3.1.2 Test Methods
- 3.1.3 Comparison of Testing Method
- 3.2 Test Plan................................................................................................................
- 3.3 Test Cases for the Poly Pipe Management System
- 3.4 Feedback
- 3.5 Summary
- Activity 04........................................................................................................................
- 4.1 User Manual
- 4.2 Technical Documentation
- 4.3 Unified Modeling Language Diagrams
- 4.3.1 Flow Chart
- 4.3.2 Use Case Diagram.................................................................................................
- 4.3.3 DFD Level 0 and 1 Diagram
- 4.3.4 Class Diagram
- 4.3.4 Sequences Diagram
- 4.4 Future Enhancement
- 4.4 Summary
- References
- Figure 1: System Requirement........................................................................................... Table of Figures
- Figure 2: ER Diagram
- Figure 3: SQL Architecture
- Figure 4: Logical Database Model
- Figure 5: Relational Mapping
- Figure 6: Welcome Page
- Figure 7: Login Page
- Figure 8: Dashboard
- Figure 9: Customer Form
- Figure 10: Staff Type Form
- Figure 11: Staff Form.........................................................................................................
- Figure 12: Installation Type Form
- Figure 13: Installation Form
- Figure 14: Installation Staff
- Figure 15: Equipment Type Form......................................................................................
- Figure 16: Equipment Form
- Figure 17: Installation Equipment Form
- Figure 18: Welcome Page
- Figure 19: Login Page
- Figure 20: Dashboard
- Figure 21: Customer Form
- Figure 22: Staff Type Form
- Figure 23: Staff Form.........................................................................................................
- Figure 24: Installation Type Form
- Figure 25: Installation Form
- Figure 26: Installation Staff Form......................................................................................
- Figure 27: Equipment Type Form......................................................................................
- Figure 28: Equipment Form
- Figure 29: Installation Equipment Form
- Figure 30: Create Database Command
- Figure 31: Login Command
- Figure 32: Use Database Command
- Figure 33: Create Table Command
- Figure 34: Insert Command
- Figure 35: Delete Command
- Figure 36: Result of Delete Command
- Figure 37: Update Command and Result of Update Command
- Figure 38: Drop Command
- Figure 39: Select Command...............................................................................................
- Figure 40: Where Command
- Figure 41: Update Command and Result of Update Command
- Figure 42: Between Command
- Figure 43: In Command
- Figure 44: Group By Command
- Figure 45: Order By Command
- Figure 46: Having Command.............................................................................................
- Figure 47: Create Table Command
- Figure 48: Insert Command
- Figure 49: Delete Command and Result of Delete Command
- Figure 50: Drop Command
- Figure 51: Update Command and Result of Update Command
- Figure 52: Select Command...............................................................................................
- Figure 53: Where Command
- Figure 54: Between Command
- Figure 55: In Command
- Figure 56: Group By Command
- Figure 57: Order By Command
- Figure 58: Having Command.............................................................................................
- Figure 59: Create Table Command
- Figure 60: Insert Command
- Figure 61: Alter Command
- Figure 62: Delete Command and Result of Delete Command
- Figure 63: Drop Command
- Figure 64: Update Command and Result of Update Command
- Figure 65: Select Command...............................................................................................
- Figure 66: Where Command
- Figure 67: Update Command and Result of Update Command
- Figure 68: Between Command
- Figure 69: In Command
- Figure 70: Group By Command
- Figure 71: Order By Command
- Figure 72: Having Command.............................................................................................
- Figure 73: Create Table Command
- Figure 74: Insert Command and Result of Insert Command
- Figure 75: Delete Command and Result of Delete Command
- Figure 76: Update Command and Result of Update Command
- Figure 77: Drop Command
- Figure 78: Select Command...............................................................................................
- Figure 79: Where Command
- Figure 80: Between Command
- Figure 81: Group Command
- Figure 82: Order By Command
- Figure 83: Having Command.............................................................................................
- Figure 84: Create Command
- Figure 85: Insert Into Command and Result of Insert Command
- Figure 86: Delete Command and Result of Delete Command
- Figure 87: Drop Command
- Figure 88: Update Command and Result of Update Command
- Figure 89: Alter Command
- Figure 90: Select Command.............................................................................................
- Figure 91: Update Command and Result of Update Command
- Figure 92: Between Command
- Figure 93: In Command
- Figure 94: Group By Command
- Figure 95: Order By Command
- Figure 96: Having Command...........................................................................................
- Figure 97: Create Command
