Showing posts with label Web Technology. Show all posts
Showing posts with label Web Technology. Show all posts

Thursday, 7 December 2017

Database normalization

DashZin
Normalization split a large table into smaller tables and define relationships between them to increases the clarity in organizing data.
Some facts about database normalization
·         The words normalization and normal form refers to the structure of database.
·         Normalization was developed by IBM researcher E.F. Codd In the 1970s.
·         Normalization increases the clarity in organizing data in Database.
Normalization of a Database is achieved by following a set of rules called ‘forms’ in creating the database.
Database normalization rules
Database normalization process are divided into following normal form:
·         First Normal Form (1NF)
·         Second Normal Form (2NF)
·         Third Normal Form (3NF)
·         Boyce-Codd Normal Form (BCNF)
·         Fourth Normal Form (4NF)
·         Fifth Normal Form (5NF)

First Normal Form (1NF)

Each column is unique in 1NF.
Example:
Sample Employee table, it displays employees are working with multiple departments.
Employee
Age
Department
Melvin
32
Marketing, Sales
Edward
45
Quality Assurance
Alex
36
Human Resource
Employee table following 1NF:
Employee
Age
Department
Melvin
32
Marketing
Melvin
32
Sales
Edward
45
Quality Assurance
Alex
36
Human Resource

Second Normal Form (2NF)

The entity should be considered already in 1NF and all attributes within the entity should depend solely on the unique identifier of the entity.
Example:
Sample Products table:
productID
product
Brand
1
Monitor
Apple
2
Monitor
Samsung
3
Scanner
HP
4
Head phone
JBL
Product table following 2NF:
Products Category table:
productID
product
1
Monitor
2
Scanner
3
Head phone
Brand table:
brandID
brand
1
Apple
2
Samsung
3
HP
4
JBL
Products Brand table:
pbID
productID
brandID
1
1
1
2
1
2
3
2
3
4
3
4


Third Normal Form (3NF)

The entity should be considered already in 2NF and no column entry should be dependent on any other entry (value) other than the key for the table.
If such an entity exists, move it outside into a new table.
3NF is achieved are considered as the database is normalized.

Boyce-Codd Normal Form (BCNF)

3NF and all tables in the database should be only one primary key.

Fourth Normal Form (4NF)

Tables cannot have multi-valued dependencies on a Primary Key.

Fifth Normal Form (5NF)

Composite key shouldn’t have any cyclic dependencies.
Well this is a highly simplified explanation for Database Normalization. One can study this process extensively though. After working with databases for some time you’ll automatically create Normalized databases. As, it’s logical and practical.





Wednesday, 6 December 2017

Web Services - Components

DashZin

WSDL

  • WSDL stands for Web Services Description Language
  • WSDL is an XML-based language for describing Web services.
  • WSDL is a W3C recommendation

SOAP

  • SOAP stands for Simple Object Access Protocol
  • SOAP is an XML based protocol for accessing Web Services.
  • SOAP is based on XML
  • SOAP is a W3C recommendation

RDF

  • RDF stands for Resource Description Framework
  • RDF is a framework for describing resources on the web
  • RDF is written in XML
  • RDF is a W3C Recommendation

RSS

  • RSS stands for Really Simple Syndication
  • RSS allows you to syndicate your site content
  • RSS defines an easy way to share and view headlines and content
  • RSS files can be automatically updated
  • RSS allows personalized views for different sites
  • RSS is written in XML






AngularJS MVC Architecture

DashZin


MVC stands for Model View Controller. It is a software design pattern for developing web applications. It is very popular because it isolates the application logic from the user interface layer and supports separation of concerns.

The MVC pattern is made up of the following three parts:
  1. Model: It is responsible for managing application data. It responds to the requests from view and to the instructions from controller to update itself.
  2. View: It is responsible for displaying all data or only a portion of data to the users. It also specifies the data in a particular format triggered by the controller's decision to present the data. They are script-based template systems such as JSP, ASP, PHP and very easy to integrate with AJAX technology.
  3. Controller: It is responsible to control the relation between models and views. It responds to user input and performs interactions on the data model objects. The controller receives input, validates it, and then performs business operations that modify the state of the data model.





Monday, 4 December 2017

Discuss the differences between an HTML specification and a browser’s implementation thereof.

DashZin

Image result for html

HTML specifications such as HTML5 define a set of rules that a document must adhere to in order to be “valid” according to that specification. In addition, a specification provides instructions on how a browser must interpret and render such a document.
A browser is said to “support” a specification if it handles valid documents according to the rules of the specification. As of yet, no browser supports all aspects of the HTML5 specification (although all of the major browser support most of it), and as a result, it is necessary for the developer to confirm whether the aspect they are making use of will be supported by all of the browsers on which they hope to display their content. This is why cross-browser support continues to be a headache for developers, despite the improved specificiations.
In addition, while HTML5 defines some rules to follow for an invalid HTML5 document (i.e., one that contains syntactical errors), invalid documents may contain anything, and it is impossible for the specification to handle all possibilities comprehensively. Thus, many decisions about how to handle malformed documents are left up to the browser.

Briefly describe the correct usage of the following HTML5 semantic elements: <header><article><section><footer>.


The <header> element is used to contain introductory and navigational information about a section of the page. This can include the section heading, the author’s name, time and date of publication, table of contents, or other navigational information.
The <article> element is meant to house a self-contained composition that can logically be independently recreated outside of the page without losing it’s meaining. Individual blog posts or news stories are good examples.
The <section> element is a flexible container for holding content that shares a common informational theme or purpose.
The <footer> element is used to hold information that should appear at the end of a section of content and contain additional information about the section. Author’s name, copyright information, and related links are typical examples of such content.