PREPARATION OF METHOD STATEMENT

Standard Format for Method Statement

1. Cover page (Title page)
   
2. List of Content
   
3. Purpose and Scope
   
4. Standards used or referred
   
5. Organisation
   
   1. Designation of Officers (named officers)
      
   2. Scope and Responsibility
      
6. Plants and Equipments
   
   1. Numbers and type of plant and machineries
      
   2. Certificate and Type of permits/certificate of fitness
      
   3. Specialised equipments (if any)
      
7. Specialised staff
   
   1. Designation of officers and workers
      
   2. Scope and responsibility
      
8. Construction Activities and Sequence of Works
   
   1. Preliminary works
      
      1. Pre-site checks
         
      2. Site survey and setting out
         
      3. Temporary works
         
      4. Location of works
         
      5. Level of workers competencies for each activities and works
         
   2. Main works
      
      1. Sequence of works to include persons involved
         
         1. Sequence of activity and work
            
         2. Construction dimensional tolerances and limits
            
         3. Holding points and approval before commencement of next activity
            
         4. Sketches, kinematics drawings, etc
            
         5. Maintenance of construction works
            
         6. Construction of work inspections and tests
            
         7. Material sampling, delivery and inspection
            
         8. Usage of plants and machineries
            
         9. Acceptance criteria
            
      2. Accesses to site
         
      3. Hours of works
         
      4. Approval process and/or special approval requirements
         
      5. Third party involvement or handover of work site or temporary access for nominated sub-contractors and/or contractors
         
      6. Specialist or Specialised contractor's method statement
         
      7. Construction constraints
         
      8. Energy and water usage and requirements
         
   3. Acceptance and Finishing Works
      
9. Legal requirements
   
10. Environmental measures
    
11. Health and Safety Measures
    
12. Risk Management
    
13. Design and/or Construction and/or Shop Drawings
    
14. List of Related Method Statements
    
15. Detailed Inspection and Test Plan
    
16. List of quality control forms
    
17. Standards, specifications and other documents listed in paragraph 4 above
    

Note:

The method statement submitted is not limited to the above statements but only the minimum requirements that are required in a method statement

XML Attributes

From HTML you will remember this: < IMG SRC="comp.gif" >. The SRC attribute provides additional information about the IMG element. In HTML (and in XML) attributes provide additional information about elements:

< img src="computer.gif" >
< a href="demo.asp" >

Attributes often provide information that is not a part of the data. In the example below, the file type is irrelevant to the data, but important to the software that wants to manipulate the element:

< file type="gif" > computer.gif < /file >
Students now u know abt basic XML, its scripting rules. Lets understand XML attributes which can be understood as property of an element.

Here are simple rules for XML elements

Quote Styles, "female" or 'female'?
Attribute values must always be enclosed in quotes, but either single or double quotes can be used. For a person's sex, the person tag can be written like this:

< person sex="female" > or like this:
< person sex='female' >

Note: If the attribute value itself contains double quotes it is necessary to use single quotes, like in this example:

< Inspector name='George "Rain" Abslum' >

Note: If the attribute value itself contains single quotes it is necessary to use double quotes, like in this example:

< Inspector name="George 'Rain' Abslum" >

Use of Elements vs. Attributes: Data can be stored in child elements or in attributes.

E.g. Take a look at these examples:

< firstname > Anna < /firstname >
lastname > Smith < /lastname >
< /person >
< person >
< sex > female < /sex >
< firstname > Anna > /firstname >
< lastname > Smith > /lastname >
< /person >

In the first example sex is an attribute. In the last, sex is a child element. Both examples provide the same information. There are no rules about when to use attributes, and when to use child elements. My experience is that attributes are handy in HTML, but in XML you should try to avoid them. Use child elements if the information feels like data.

E.g.Storing data in child elements.

The following three XML documents contain exactly the same information:
A date attribute is used in the first example:
< note date="12/11/2002" >
< to > Tove < /to >
< from>Jani < /from >
< heading>Reminder < /heading >
< body>Don't forget me this weekend! < /body >
< /note >

A date element is used in the second example:

< note >
< date > 12/11/2002 < /date >
< to > Tove < /to >
< from>JaniReminder < /heading >
< body>Don't forget me this weekend! < /body >
< /note >
An expanded date element is used in the third: (THIS IS MY FAVORITE):

< note >
< date >
< day > 12 < /day >
< month > 11 < /month >
< year > 2002 </year >
< /date >
< to > Tove < /to >
< from > Jani < /from >
< heading > Reminder < /heading >
< body >Don't forget me this weekend! < /body >
< /note >

Element naming

XML elements must follow these naming rules:

• Names can contain letters, numbers, and other characters
• Names must not start with a number or punctuation character
• Names must not start with the letters xml (or XML, or Xml, etc)
• Names cannot contain spaces

Take care when you "invent" element names and follow these simple rules:
Any name can be used, no words are reserved, but the idea is to make names descriptive. Names with an underscore separator are nice.

Examples: < stud_name >, < stud_age > .


Avoid "-" and "." in names. For example, if you name something "first-name," it could be a mess if your software tries to subtract name from first. Or if you name something "first.name," your software may think that "name" is a property of the object "first." Element names can be as long as you like, but don't exaggerate. Names should be short and simple, like this:



< Thesis_title > not like this: < the_title_of_the_book >.



XML documents often have a corresponding database, in which fields exist corresponding to elements in the XML document. A good practice is to use the naming rules of your database for the elements in the XML documents. Non-English letters like éòá are perfectly legal in XML element names, but watch out for problems if your software vendor doesn't support them. The ":" should not be used in element names because it is reserved to be used for something called namespaces (more later).

XML SCRIPTING

XML Language can be understood as a generic language used to describe other markup languages. You need to understand that XML makes a clear distinction between the markup and the content of the webpage. Here markup implies tags and attributes that are being used in the XML document and content refers to the information being presented in the document.

E.g.
< p > XML is used to store data in a structured way < /p >

In this example < p >…. </p > refers to the markup being used in the document and the text written between these tags refer to the content of the document.

You can say that markup is actually used to describe the presentation of the content. This is done using standard tags and attributes that are available in HTML. You will find that the XML markup is generally used to describe the content of the document and is not related with the appearance of the document.

E.g. < quiz answer=”Qutab Minar” > Can you name a famous monument in delhi?< /quiz >

In this example < quiz > tag is being used to describe the type of content and the answer attribute specifies the answer for this question.

To start using XML effectively you need to learn about the terminology used in XML and understand the structure of a XML file. Consider following example:

< catalog >
< movie >
< title > Jung < >
< duration > 3 hrs < /duration >
< /movie >
< /catalog >

As you can see XML files have hierarchical structure. Each tag used in XML defines an element. Each element defined should have an opening as well as a closing tag. E.g. < catalog > has opening as well as closing tag. You will find that some of the elements are self-contained. You do not need to enclose any information in them. These tags can be considered empty element. Such tags can be made self-closing by adding "/ > >" at the end of the opening tag. The hierarchical structure enables easy parsing of the document. As in above example catalogue contains information about movie which ultimately contains detail about title and duration of the movie.

XML Syntax

Check out the following example:

Line 1: < ?xml version="1.0" ? >
Line 2: < library >
Line 3: < type="Operational Research" year="1992" >
Line 4: < book1 > Linear Programming < /book >
Line 5: < book2 > Non Linear Programming < /book >
Line 6: < book3 > Mathematical Programming < /book >
Line 7: < /book >
Line 8: < /library >

The first line is a processing Instruction. Processing Instruction is used to define the XML version of the document. From Line 1 you will find that the example written conforms to the 1.0 specification of XML:
< ?xml version=”1.0”? >

2 defines the first element of the document which is the root element:
< library >
next lines define child elements of the root i.e. Book which further has child elements (book1, book2, book3).

You can see that an XML documents use a self-describing syntax which is very simple to understand. Before you read further about xml scripting you need to be aware of the major components of an xml document. XML mark-up document can be broadly divided into a set of components which describe the makeup of a XML document. These components can be defined as follows:

1. Element Tag: An element can be understood as a piece of information that corresponds to a tag or a set of tags in a XML document. In other words element can be understood as a logical piece of markup that is represented as a tag in a XML document. E.g. In above example ‘quiz’ is an element which has been used as < quiz > &lgt; /quiz > tag in the document.


Note that an element need to have both starting and ending tags like < quiz > …< /quiz > ,< p > …< /p > or a simple empty tag like < img/ >. While coding in HTML empty tag < br > do not need to have end tag. However with XML be careful you need to close every tag.

2. Processing Instruction: Apart from markup and content you will find processing instructions written in a XML document which is the first statement in the document. A processing instruction can be understood as a special command passed along to the program which will process the document. Processing instruction written in < ?.....? > .
E.g. < ?xml version="1.0"? >

This processing instruction is the first statement of a XML document. You will find that the processing instruction is similar to a tag. It includes name and attribute/value pair. This processing instruction tells that the document adheres to the standard of xml version 1.0.

3. Comments in XML:

In a XML document comments can be written using following syntax:

< !-- In this document you are learning about xml -->

Note: You can write comments in XML in the same way as you write in HTML.

4. Document Type Declaration: It is used for describing the structure of an XML document. It identifies the external DTD that defines the structure of an xml document. The external DTD( DTD stands for Document type definition) is created for describing the structure of the xml document. You need to put the ‘Document Type declaration’ on the top of the xml document. It is written just below the processing instruction. Its use is to perform three basic tasks:

1. Document Type Declaration is used to identify the root element of the document. In an xml document there is a root element such that all other elements are the children of the root element.

2. Identifies the external DTD of the file. An xml file is created according to the document structure defined in the DTD.

E.g. Check out the XML below which describes audio/video collection

< ? xml version="1.0"? >
< !DOCTYPE entertainment SYSTEM entertainment.dtd >
< entertainment >
< Audio >
< track1 > Tara Rampam < >
< track2 > Let's go for party < /track2 >
< /Audio >
< Video >
< track1 > Jumanji < /track1 >
< track2 > Home Alome < /track2 >
< /Video >
< /entertainment >

In above example first line is a processing instruction which shows that this document should be processed according to the xml version 1.0 standards. In second line is the document type declaration which states that the root element for this xml file is ‘entertainment’. Further it identifies that the document need to be verified according to the external DTD namely “entertainment.dtd”. While processing this file browser needs to look for “entertainment.dtd” and then validate the document structure according to this file.

Just quick recap

I am sure you must be able to answer following questions:


1. How XML differs from HTML?
2. What is advantage of XML?

Difference between HTML and XML

You need to understand that you will not use XML for replacing HTML. Both XML and HTML have been designed for different goals which can be summarized as follows:


a. XML is designed specifically for describing and structuring the data where as HTML is used for formatting and displaying the data.

b. XML is focused on defining data with its attributes. It basically tells what data is all about. HTML is focused on presentation of data and is used to customize looks of data.

c. In case of HTML Document tags to be used and the structure of the documents are predefined. While using HTML you can only use tags which are pre-defined in the HTML standards. In case of XML you can define your own tags and develop your own document structure.

d. An XML document is saved with an extension .XML whereas an HTML document is saved as .HTML.

E.g. The following example is an e-mail from Ram to Shyam stored as XML

< email >
< to > Ram </to >
< from > Shyam < /from >
< subject > Hi how are you? </subject >
< content > Let’s go for a New Year party </content >
< /email >

In above example e-mail has been stored using XML markup language. You can see that own tags have been created to store the names of sender and receiver. Similarly different tags have been created to store the subject and content of the web page.

CHARACTERISTICS OF XML

XML stands for ‘Extensible Markup Language’. It is a general-purpose specification which is commonly used for creating custom markup languages. It is an extensible language as it provides its users an ability to define their own elements. Thus it enables users to create custom tags that suit their requirement. XML has been primarily developed to information systems share their structured data online. It can be used to encode documents as well as to serialize data so that it can be efficiently used. Some of the features of XML have been summarized below:
1. XML can be understood as an extensible language which is freely available.
2. XML tags are user made tags. They are not predefined tags. In case of HTML predefined tags are used (like < p >, < h1 > etc.). While using XML users can define custom tags and develop document structure as per their requirement.
3. XML is not a replacement for HTML. It is actually a complement to HTML. Both scripting languages have their own purpose. As web is developing XML is being popularly used to describe and structure the data where as HTML is being be used for formatting and displaying the data.


4. XML has been inherited from SGML


Let us define SGML


SGML:SGML implies Standard Generalized Markup Language. SGML is an ISO standard that defines an extremely powerful markup language. It is popularly used in the publishing industry and large manufacturing companies. It is a meta language used for creating other markup languages such as HTML. It marks the origin of XML.




XML

XML can be understood as markup language like the Hypertext Markup Language (HTML) which is commonly used for scripting web page. XML is specifically designed to describe data so that it can be effectively stored online. Web today contains such vast information. XML enables structuring of data so that it can then be mined to get suitable information. In case of XML unlike HTML there are no predefined tags. XML can also be called as self-descriptive markup language as users need to define their on tags.

For better understanding check out the example below:

Suppose you are storing information about a set of books. You may store the information in html as follows:

Book.html

< html >
< head > < title > Storing Information < /title >
< body >
< p > Linear Programming by A.S. Bajaj

< p > Marketing Research by Kotler

< /body >
< /html >

Book.xml

< catalog >
< book >
< title > Linear Programming < title >
< author > A.S Bajaj </author >
< /book >
< book >
< title > <Marketing Research