Beruflich Dokumente
Kultur Dokumente
Building
Technology 04
Standard Specifications
Table of Contents
Specification
Definition 1
Purpose 1
Format 1
Types 4
Division 6
References 7
Summary and Conclusion 8
Sample of Specificiatons
(07)-201513410
2/27/2018
Arch. Christopher Coma
Adamson University – College of Architecture
Building Technology 04
2017-2018 Second Semester
Specifications
Specifications describe the nature and the class of the work, materials to be used in
the work, workmanship etc. and is very important for the execution of the work. The
cost of a work depends much on the specifications. Specifications should be clear.
Cover Page
Team Name, Logo (optional), Deliverable name, Date, Course-Section.
Credits Page
Follow these guidelines.
1.0 Introduction
1.1 Scope
Give a one sentence explanation of what the product will do.
Explain why this product is needed. Discuss the specific problems that this product
will attempt to solve.
1.4 Constraints
Describe any constraint that may limit the choices available to the developers, such as
regulatory policies, intellectual property restrictions, high level language requirements,
etc.
Two common notations for stating requirements are "atomic sentences" or "Use
Cases." Atomic sentences are appropriate where the system functioning is primarily
computational or processing oriented. Use Cases are often preferred where the system
is primarily interactive or event driven.
Winter 2004. Using the ASCENT CASE tool you should write your functional
requirements (or "mini-specs") as "Process Logic" within the CASE tool itself. You then
have several alternatives for how to submit it.
1. You may submit your ASCENT project itself in computer readable form (be sure
to include all the ".cde" files that contain the mini-specs).
2. You may convert the content of all the ".cde" into HTML and include them in
this section of the SRS.
One way to distinguish a functional requirement is that you can point to the source
code that implements it, but nonfunctional requirements can't be isolated in the
code. The best example is performance requirements, e.g., "the executable module
must fit on a 1.4MB floppy disk."
These requirements are subject to the same criteria as the previous section. Special
attention must be given to stating the requirements in a manner that is objective and
quantifiable; there must be some measurable way to assess whether the requirement
has been met.
Consult this online reference as well as your textbook. Also refer to section 5.3.6 of
the IEEE template.
6.0 Appendices
Describe all interfaces between the software and any hardware components in the
system (e.g. touch tablet).
Describe the way in which the software will interact with any other required software
(e.g. database, legacy system, web server, etc). It is not necessary to detail any well-
documented interface (e.g., SQL).
Specify the format for all data input to or output from the system. This includes any
external file formats and the layout of any printed reports.
6.4 QA Checklist, (with items checked off), signed by your QA person. You
must provide an explanation for any items not checked off.As a general rule,
checklists with more than five unchecked items are not ready for submission. If
an item is missing or obviously unsatisfactory that has been checked off, the
entire document will be returned for correction and a late penalty will accrue.
Types of Specifications
General Specifications
In general specifications, nature and class of works and names of materials that
should be used are described. Only a brief description of each and every item is given.
It is useful for estimating the project. The general specifications do not form a part of
contract document.
Detailed Specifications
The detailed specifications form a part of a contract document. They specify the
qualities, quantities and proportions of materials and the method of preparation and
execution for a particular item of works in a project. The detailed specifications of the
different items of the work are prepared separately and they describe what the work
should be and how they shall be executed. While writing the detailed specifications,
the same order sequence as the work is to be carried out is to be maintained.
Examples of products or systems that should have detailed installation specs, and
issues to cover in the specs, include:
Quality standards. Installation specs for visible finish work often contain quality
standards as well
Performance specs. This type of spec describes the standards that must be met,
rather than the specific product of system to be used
MasterFormat Divisions
MasterFormat was first released in 1975 and only had 16 Divisions until the new 50-
Division MasterFormat 2004 was released in late 2004. Divisions that are not listed
below are reserved for future use (including Division 49.)
References
https://www.archtoolbox.com/representation/specifications/csidivisions.html
http://www.civilprojectsonline.com/civil-projects/purpose-of-specifications-
and-types-of-specifications/
http://buildingadvisor.com/project-management/where-to-get-plans-and-
specs/construction-specifications/
http://users.csc.calpoly.edu/~jdalbey/205/Deliver/SRSformat.html
Specifications describe the nature and the class of the work, materials to be
used in the work, workmanship etc. and is very important for the execution of the
work. The cost of a work depends much on the specifications. Specifications should be
clear. Specification of a work is required to describe the quality and quantity of
different materials required for a construction work and is one of the essential
contract documents.
There are format on creating a specifications guidelines with provided
standards of requirements.
In general specifications, nature and class of works and names of materials that
should be used are described. Only a brief description of each and every item is given.
It is useful for estimating the project. The general specifications do not form a part of
contract document.
The detailed specifications form a part of a contract document. They specify the
qualities, quantities and proportions of materials and the method of preparation and
execution for a particular item of works in a project. The detailed specifications of the
different items of the work are prepared separately and they describe what the work
should be and how they shall be executed. While writing the detailed specifications,
the same order sequence as the work is to be carried out is to be maintained. To
further define specification these type of specifation are required.
Quality standards, Installation specs for visible finish work often contain
quality standards as well.
Performance specs, This type of spec describes the standards that must be met,
rather than the specific product of system to be used.
There are also divisions on which a certain specification are specified and
detailed which is as follows; Division 00 - Procurement and Contracting Requirements
,Division 01 - General Requirements, Division 02 - Existing Conditions, Division 03 –
Concrete, Division 04 – Masonry, Division 05 – Metals, Division 06 - Wood, Plastics,
Specifications Standard Page 8
Adamson University – College of Architecture
Building Technology 04
2017-2018 Second Semester