Download Assignment Web Design and Development and more Assignments Web Design and Development in PDF only on Docsity!
ASSIGNMENT 1 BRIEF
Qualification BTEC Level 5 HND Diploma in Computing Unit number 10: Website Design & Development Assignment title Web Services Presentation and Guidebook Academic Year 2018 – 2019 Unit Tutor Vo Thi Thanh Van Issue date Submission date 22/2/ IV name and date Submission Format: Format: Two ten-minute Microsoft® PowerPoint® style presentations to be presented to your colleagues Submission Students are compulsory to submit the assignment in due date and in a way requested by the Tutors. The form of submission will be a soft copy posted on http://cms.greenwich.edu.vn/ Note: The Assignment must be your own work, and not copied by or from another student or from books etc. If you use ideas, quotes or data (such as diagrams) from books, journals or other sources, you must reference your sources, using the Harvard style. Make sure that you know how to reference properly, and that understand the guidelines on plagiarism. If you do not, you definitely get failed Unit Learning Outcomes: LO1 Explain server technologies and management services associated with hosting and managing websites. LO2 Categorise website technologies, tools and software used to develop websites. Assignment Brief and Guidance: You work as a full-stack web team leader for a leading creative web solutions and marketing company. Your team is about to have a big contract to develop an online shopping mall. One of the preparation tasks is to choose appropriate tools and techniques to realise a custom built
website. As part of your role, you have been asked to create an engaging presentation to help train junior staff members on basic web technologies including hosting and website management as well as server technologies. Your presentation should not only explain basic knowledge in the domain but also points out the impact of these technologies to website design, functionality, management or performance. You also need to present more technical presentation to senior staff members to discuss about frontend, back-end technologies as well as other tools, techniques and softwares used to develop website from simple (online website creation tools) to complicated (custom built). Your presentation will be used as guidance of choosing suitable tools and techniques for the next project.
A. Definition 9 B. How Does DNS Work 10 Example 12 C.Types of DNS 14
- Three types of DNS Queries 14 2. Three types of DNS Servers 15
- Top ten types of DNS Records 16 D. How Domain Names Are Organized And Managed 17 P2. EXPLAIN THE PURPOSE AND RELATIONSHIPS BETWEEN COMMUNICATION PROTOCOLS, SERVER HARDWARE, OPERATING SYSTEMS AND WEB SERVER SOFTWARE WITH REGARDS TO DESIGNING, PUBLISHING AND ACCESSING A WEBSITE. 19 A. Communication Protocols 19 B. Web Server Hardware 20 C. Web Server Software 21 D. Host Operating System 22 E. Relationship 23 P3. DISCUSS THE CAPABILITIES AND RELATIONSHIPS BETWEEN FRONT-END AND BACK-END WEBSITE TECHNOLOGIES AND EXPLAIN HOW THESE RELATE TO PRESENTATION AND APPLICATION LAYERS. 25 A. Front End 26
- What is Front End. 26
- Front End Technologies. 26 a) HTML 26 b) HTML5 27 c) CSS 27 e) SASS 28 f) JavaScript 28 g) Responsive Design 29 h) Perceived Performance 30 A. Back End 30
- What is Back End. 30
- Back End Technologies. 31 a) Languages & Frameworks 31 b) Web Servers 32 c) Web services 32 d) Database Management Systems 32 e) Local Development Environments 33 f) Collaboration Services 33 g) Website Performance Testers 33 h) APIs 33
C. The relationship between Front-end and Back-end 34
- What should frontend and backend developers both know? 34 a) Version control systems (VCS) 34 b) Testing and debugging 35 c) Full Stack Development 35
- Difference between Frontend and Backend 36 a) Meaning of Frontend and Backend 36 b) Role of Frontend verses Backend 36 c) Developer of Frontend verses Backend 36 d) Essentials of Frontend verses Backend 36 c) Frontend vs. Backend: Comparison Chart 37 d) Summary of Frontend versus Backend 37 D. How Front-End and Back-End Relate To Presentation And Application Layer 38
- Presentation Layer 38
- Application layer 38
- Database Layer 38 P4. DISCUSS THE DIFFERENCES BETWEEN ONLINE WEBSITE CREATION TOOLS AND CUSTOM BUILT SITES WITH REGARDS TO DESIGN FLEXIBILITY, PERFORMANCE, FUNCTIONALITY, USER EXPERIENCE (UX) AND USER INTERFACE (UI). 40 A. Online Website Creation Tools and Custom Built Sites. 40
- Online Website Creation Tool 41
- CUSTOM-BUILT SITES 42 B. Differences Between Online Website Creation Tools And Custom-Built Sites 43
- Flexibility 43 2. Performance 44
- Functionality 44
- User Experience (UX) 44
- User Interface (UI) 45 M1. EVALUATE THE IMPACT OF COMMON WEB DEVELOPMENT TECHNOLOGIES AND FRAMEWORKS WITH REGARDS TO WEBSITE DESIGN, FUNCTIONALITY AND MANAGEMENT. 47 [12] [13] 47
P1. IDENTIFY THE PURPOSE AND TYPES OF DNS,
INCLUDING EXPLANATIONS ON HOW DOMAIN
- A. Evaluation Of Web Application Frameworks
- Degrees Of Activeness Web Frameworks
- Advantages Of Using A Framework
- Disadvantage Of Using A Framework
- B. The Impact Of Frameworks With Regards To Functionality
- Convention Over Configuration
- Integrated Development Environment
- Internationalization (Localization)
- Validation
- Testing
- VALUE AND RANK THROUGH SEARCH ENGINE OPTIMIZATION. AND PROVIDE EVIDENCE-BASED SUPPORT FOR IMPROVING A SITE’S INDEX
- A. What is Search Engine? - 1. How do search engines work?51 a) Scheduling - b) Crawling - c) Parsing - d) Indexing
- B. What is SEO and How It Works? [17]
- C. Technical solutions to optimize website for search engine based SEO. - 1. Understand what Keywords people are searching for - 2. Create content that searchers want to see - 3. Get clicks with a compelling title - 4. Keep URLs short and descriptive - 5. Optimize your images - 6. Make sure your content is easy to read
- DEVELOP A CUSTOM BUILT WEBSITE. AND
- A. Visual Design
- Photoshop
- Abode XD
- Dreamweaver
- B. IDE
- Netbeans
- Eclipse
- PHPStorm
- WebStorm
- C. Text Editor
- Sublime Text
- Visual Studio Code
- Atom
- Bracket
- D. Programming Language and Techniques
- JavaScript Libraries
- Task Runners / Package Managers
- CSS Preprocessors
- Markdown Editors
- APIs Tool
- PHP
- .NET
- Javascript
- BUILT WEBSITE. D1. JUSTIFY THE TOOLS AND TECHNIQUES CHOSEN TO REALISE A CUSTOM
- A. Design Wideframe
- B. Design Visual
- C. Languages
- HTML5
- CSS3
- JavaScript
- jQuery
- Bootstrap
- D. Text Editor
- A well-thought GUI
- Highly discoverable extensions
- Easy split-screen
- Git diff view
- Easy split-screen
- Built-in terminal/debugger
- IntelliSense
- E. Local Server
- Apache
- MYSQL
- PHP
- F. Web Hosting
- Bluehost is User-Friendly
- Fast Page Loading Speed
- Bluehost provides 24/7 Technical Support
- REFERENCES
A few of the more popular are host, or A record, canonical name, or CNAME, and mail exchanger, or MX. An A Record is the basic mapping of an IP to a hostname. A CNAME is an that points to another DNS hostname for ultimate resolution. For example, 1.google.com is a CNAME that points us to 2.google.com which is ultimately resolved to an IP. An MX record is the first step in sending the email. When our email server wants to forward a message to the google.com domain, it will request google.com's MX record. The email will then be forwarded to whatever host IP was resolved by the MX record. [2] B. How Does DNS Work When you visit a domain such as dyn.com, your computer follows a series of steps to turn the human readable web address into a machine-readable IP address. This happens every time you use a domain name, whether you are viewing websites, sending email or listening to internet radio stations such as Pandora. This image provides a high-level overview of how DNS works: Image 2: How DNS work Let’s take an in-depth look at the process: Step 1: Request information The process begins when you ask your computer to resolve a hostname, such as visiting https://dyn.com. The first place your computer looks for the corresponding IP address is its local DNS cache, which stores information that your computer has recently retrieved. If your computer doesn’t already know the answer, it needs to perform a DNS query to find out.
Step 2: Ask the recursive DNS servers If the information is not stored locally, your computer queries (contacts) the recursive DNS servers (resolvers) from your internet service provider (ISP). These specialized computers perform the legwork of a DNS query on your behalf. Resolvers have their own caches, and given that many of the ISP’s customers are using the same resolvers, there is a reasonable chance that popular domains will already be cached. If this is the case for our example, dyn.com, the process usually ends here and the information is returned to the user. Just about every ISP runs their own resolvers, yet those aren’t necessarily what you could be using. Some companies and perhaps even technically sophisticated home users could run their own resolvers on site. Additionally, there are several very popular open resolvers available, including Google Public DNS, OpenDNS, Dyn Recursive DNS, and Quad9. Step 3: Ask the root name servers If the recursive servers don’t have the answer, they query the root name servers. A name server is a computer that answers questions about domain names, such as IP addresses. These 13 servers act as a kind of telephone switchboard for DNS. They don’t know the answer, but they can direct DNS queries to someone that knows where to find it. Step 4: Ask the TLD name servers The root name servers will look at the first part of our request, reading from right to left — www.dyn.com — and in our case, direct our query to the top-level domain (TLD) name servers for .com. Each TLD, such as those for .com, .org, and .us, has its own set of name servers, which act like a receptionist for each TLD. These servers don’t have the information we need, but they can refer us directly to the servers that do have the information. Step 5: Ask the authoritative DNS servers The TLD name servers review the next part of our request — www.dyn.com — and direct our query to the name servers responsible for this specific domain. These authoritative name servers are responsible for knowing all the information about a specific domain, which is stored in DNS records. There are many types of records, which each contain a different kind of information. In this example, we want to know the IP address for www.dyn.com, so we ask the
The DNS server then queries the .com Domain Server, and says, ".com Domain, do we know where the "support.example domain is?" The .com Domain Server then says, "Well, I don't know where the .support Domain is, "but I do know where the .example Domain is, "and this is the IP address for it." And then it sends that IP address on back to the DNS Server. ISP's DNS Server then sends a query to the .example Domain, and says, ".example Domain, do we happen to know where the .support Domain is?" The .example Domain looks at that and says, "Yes, I do know where the .support Domain is, "It's one of the domains I'm responsible for". Here's the IP address for it, it then forwards that IP address back to the ISP's DNS Server, and ISP's DNS Server then sends that IP address to the Client. The Client then sends out a query to the support.example.com Domain asking for the stuff_specs.htm document.
C.Types of DNS [4]
1. Three types of DNS Queries Recursive Query In a recursive query, a DNS client provides a hostname, and the DNS Resolver “must” provide an answer—it responds with either a relevant resource record, or an error message if it can't be found. The resolver starts a recursive query process, starting from the DNS Root Server, until it finds the Authoritative Name Server (for more on Authoritative Name Servers see DNS Server Types below) that holds the IP address and other information for the requested hostname. Iterative Query In an iterative query, a DNS client provides a hostname, and the DNS Resolver returns the best answer it can. If the DNS resolver has the relevant DNS records in its cache, it returns them. If not, it refers the DNS client to the Root Server, or another Authoritative Name Server which is nearest to the required DNS zone. The DNS client must then repeat the query directly against the DNS server it was referred to. Non-Recursive Query A non-recursive query is a query in which the DNS Resolver already knows the answer. It either immediately returns a DNS record because it already stores it in local cache, or queries a DNS Name Server which is authoritative for the record, meaning it definitely holds the correct IP for that hostname. In both cases, there is no need for additional rounds of queries (like in recursive or iterative queries). Rather, a response is immediately returned to the client. 2. Three types of DNS Servers The following are the most common DNS server types that are used to resolve hostnames into IP addresses.
- Mail exchanger record (MX Record) —specifies an SMTP email server for the domain, used to route outgoing emails to an email server.
- Name Server records (NS Record) —specifies that a DNS Zone, such as “example.com” is delegated to a specific Authoritative Name Server, and provides the address of the name server.
- Reverse-lookup Pointer records (PTR Record) —allows a DNS resolver to provide an IP address and receive a hostname (reverse DNS lookup).
- Certificate record (CERT Record) —stores encryption certificates—PKIX, SPKI, PGP, and so on.
- Service Location (SRV Record) —a service location record, like MX but for other communication protocols.
- Text Record (TXT Record) —typically carries machine-readable data such as opportunistic encryption, sender policy framework, DKIM, DMARC, etc.
- Start of Authority (SOA Record) —this record appears at the beginning of a DNS zone file, and indicates the Authoritative Name Server for the current DNS zone, contact details for the domain administrator, domain serial number, and information on how frequently DNS information for this zone should be refreshed. D. How Domain Names Are Organized And Managed [5] The Domain names were developed to organize and find the IP address of computers on a large distributed network and before the domain structure was developed computer names and IP address are managed by using flat list and stored in a simple text file known as host file as well as every domain consists of two parts which is actual domain and top-level domain. Similarly, domains are under the jurisdiction of ICANN and also managed by ICANN too and they are under contract from ICANN to manage the domain for specified amount of time. In addition, top-level domains have been managed by one or mote than one organization in its history and Organizations operating a high- level domain are responsible for the authoritative name server and the maintenance of a written record database; among the alternative requirements made public in the written record agreement of ICANN. Moreover, these 13 servers kept the records and one-of-akind servers that is of low preferred of the statically. It additionally saves the facts which might be particular to the workplaces which are complete current database and arrange the domains browser which went to the customers and after that it bypass to the internet carrier provider DNS server, subsequently some guidelines are solved to it as well as domain management refers to the ongoing task of keeping a personal or corporate domain which will be more stable, secure and able to support related website. Furthermore, domain management depends upon the owner’s goals and need as there are also
different tools which will be helpful to manage the domain as well but tools must be genuine otherwise there may be different problem with your domain and these tools help to renewing or terminating domain registration’s, validating IP address and configuring name server. In addition, domain management tools and services can help to keep domain secure, stable and reliable. Image 3: Example of Domain Management Application.
Popular protocols include File Transfer Protocol (FTP), TCP/IP, User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), Post Office Protocol (POP3), Internet Message Access Protocol (IMAP), Simple Mail Transfer Protocol (SMTP). B. Web Server Hardware [7] A server is a computer that provides data to other computers. It may serve data to systems on a local area network (LAN) or a wide area network (WAN) over the Internet. Many types of servers exist, including web servers, mail servers, and file servers. Each type runs software specific to the purpose of the server. For example, a Web server may run Apache HTTP Server or Microsoft IIS, which both provide access to websites over the Internet. A mail server may run a program like Exim or iMail, which provides SMTP services for sending and receiving email. A file server might use Samba or the operating system's built-in file sharing services to share files over a network. While server software is specific to the type of server, the hardware is not as important. In fact, a regular desktop computers can be turned into a server by adding the appropriate software. For example, a computer connected to a home network can be designated as a file server, print server, or both. While any computer can be configured as a server, most large businesses use rack-mountable hardware designed specifically for server functionality. These systems, often 1U in size, take up minimal space and often have useful features such as LED status lights and hot-swappable hard drive bays. Multiple rack mountable servers can be placed in a single rack and often share the same monitor and input devices. Most servers are accessed remotely using remote access software, so input devices are often not even necessary. While servers can run on different types of computers, it is important that the hardware is sufficient to support the demands of the server. For instance, a web server that runs lots of web scripts in real-time should have a fast processor and enough RAM to handle the "load" without slowing down. A file server should have one or more fast hard drives or SSDs that can read and write data quickly. Regardless of the type of server, a fast network connection is critical, since all data flows through that connection.
Image 5: Web Server Hardware [8] C. Web Server Software [9] Web servers are computer systems that serve up/deliver web pages in response to requests from remote browsers using software applications based on:
- the client/server model – a computational architecture that involves client processes requesting service from server processes, and
- the Hypertext Transfer Protocol (HTTP) - an application protocol which defines how files are transferred on the World Wide Web. There are many web server software/applications available. Some of the more popular ones are: Apache – a general purpose HTTP server from the Apache HTTP Server Project, which aimed to develop and maintain an open-source HTTP server for modern operating systems including UNIX and Windows NT Apache Tomcat – the servlet container used in the official Reference Implementation for the Java Servlet and JavaServer Pages (JSP); it is developed in an open environment and released under the Apache Software License; Tomcat 3.3.2 is for Servlet 2.2/JSP 1.1 technologies, Tomcat 4.1.30 for the 2.3/1.2 and Tomcat 5.0.19 for the 2.4/2.0, respectively
