SPECIFICATION 
TECHNICAL WRITING 
STANDARD
What are we going to know about Specification? 
• What is Specification? 
• Kinds of Specification 
• How Specification may be develop? 
• Uses of Specification 
• Guidance 
• Process capability considerations
Note: 
please take note 
of the bolded 
words.
What is Specification? 
• Specification (often abbreviated as spec) is an 
explicit set of requirements to be satisfied by 
a material, product, or service. 
• a type of technical standard. 
• Should a material, product or service fail to 
meet one or more of the applicable 
specifications.
how Specification may be develop? 
• A technical specification may be developed by 
any of various kinds of organizations, both public 
and private. 
 . Example organization types include a 
corporation, a consortium (a small group of 
corporations), a trade association (an industry-wide 
group of corporations), a national 
government (including its military, regulatory 
agencies, and national laboratories and 
institutes), a professional association (society), or 
a purpose-made standards organization such as 
ISO.
Kinds of Specification 
Formal specification 
Program specification 
Functional specification 
Web service specification 
Document specification
Formal specification 
• is a mathematical description of software or hardware 
that may be used to develop an implementation 
• It describes what the system should do, not 
(necessarily) how the system should do it 
• it is possible to use formal verification techniques to 
demonstrate that a candidate system design is correct 
with respect to the specification 
• This has the advantage that incorrect candidate system 
designs can be revised before a major investment has 
been made in actually implementing the design
Program specification 
• the definition of what a computer program is expected 
to do 
• It can be informal, in which case it can be considered as 
a user manual from a developer point of view, or 
formal, in which case it has a definite meaning defined 
in mathematical or programmatic terms 
• In practice, many successful specifications are written 
to understand and fine-tune applications that were 
already well-developed, although safety-critical 
software systems are often carefully specified prior to 
application development 
• Specifications are most important for external 
interfaces that must remain stable.
Functional specification 
• In software development, a functional 
specification (also, functional spec or specs or 
functional specifications document (FSD)) is the 
set of documentation that describes the behavior 
of a computer program or larger software system 
• The documentation typically describes various 
inputs that can be provided to the software 
system and how the system responds to those 
inputs.
Web service specification 
• Web services specifications 
are often under the 
umbrella of a quality 
management system
Document specification 
• These types of documents define how a 
specific document should be written, which 
may include, but is not limited to, the systems 
of a document naming, version, layout, 
referencing, structuring, appearance, 
language, copyright, hierarchy or format, etc 
• Very often, this kind of specifications is 
complemented by a designated template.
• It is common for one organization to refer to 
(reference, call out, cite) the standards of 
another. 
• . Voluntary standards may become mandatory 
if adopted by a government or business 
contract. 
Sometimes the term specification is used in 
connection with a data sheet (or spec sheet). 
•describes the technical characteristics of an item or 
product. 
•It can be published by a manufacturer to help people 
choose products or to help use the products 
•is not a technical specification as described in this article.
Uses of Specification 
• In engineering, manufacturing, and business, 
it is vital for suppliers, purchasers, and users 
of materials, products, or services to 
understand and agree upon all requirements. 
• It is a type of a standard which is often 
referenced by a contract or procurement 
document. It provides the necessary details 
about the specific requirements.
• Specifications may be written by government agencies, 
standards organizations (ASTM, ISO, CEN, DoD, etc.), 
trade associations, corporations, and others. 
• A product specification does not necessarily prove a 
product to be correct. An item might be verified to 
comply with a specification or stamped with a 
specification number: This does not, by itself, indicate 
that the item is fit for any particular use. The people 
who use the item (engineers, trade unions, etc.) or 
specify the item (building codes, government, industry, 
etc.) have the responsibility to consider the choice of 
available specifications, specify the correct one, 
enforce compliance, and use the item correctly. 
Validation of suitability is necessary
Guidance 
a standing operating procedure is available to 
help write and format a good specification 
Specification may include the following: 
•Person, office, or agency responsible 
for questions on the specification, 
updates, and deviations. 
•The significance, scope or importance 
of the specification and its intended 
use. 
•Terminology, definitions and 
abbreviations to clarify the meanings of 
the specification[9][10] 
•Test methods for measuring all 
specified characteristics 
•Descriptive title, number, 
identifier, etc. of the 
specification 
•Date of last effective revision 
and revision designation 
•A logo or trademark to indicate 
the document copyright, 
ownership and origin[8] 
•Table of Contents (TOC), if the 
document is long
• Material requirements: physical, 
mechanical, electrical, chemical, 
etc. Targets and tolerances. 
• Acceptance testing, including 
Performance testing requirements. 
Targets and tolerances. 
• Drawings, photographs, or 
technical illustrations 
• Workmanship 
• Certifications required. 
• Safety considerations and 
requirements 
• Environmental considerations and 
requirements 
• Quality control requirements, 
acceptance sampling, inspections, 
acceptance criteria 
• Provisions for rejection, reinspection, 
rehearing, corrective measures 
• References and citations for which 
any instructions in the content 
maybe required to fulfill the 
traceability and clarity of the 
document 
• Signatures of approval, if necessary 
• Change record to summarize the 
chronological development, revision 
and completion if the document is to 
be circulated internally 
• Annexes and Appendices that are 
expand details, add clarification, or 
offer options 
• Person, office, or agency responsible 
for enforcement of the specification. 
• Completion and delivery.
Process capability considerations 
• A good engineering specification, by itself, does 
not necessarily imply that all products sold to that 
specification actually meet the listed targets and 
tolerances. Actual production of any material, 
product, or service involves inherent variation of 
output. With a normal distribution, the tails of 
production may extend well beyond plus and 
minus three standard deviations from the process 
average.
• The process capability of materials and products 
needs to be compatible with the specified 
engineering tolerances. Process controls must be in 
place and an effective Quality management system, 
such as Total Quality Management, needs to keep 
actual production within the desired tolerances. 
• Effective enforcement of a specification is 
necessary for it to be useful.
BY: GROUP 3 
LEADER: INGRID MARIE ACBANG 
SECRETARY: JULLIE ANGELINE BELEN 
REPORT MAKER: JOEDY MAE MANGAMPO 
MEMBERS: Mary grace orcine 
daryl samson 
jomar onding
10- item quiz 
1. What is Specification? 
2.-6. Kinds of Specification 
7-8. Give at least two things where we uses 
Specification 
9. What is a standing operating procedure is 
available to help write and format a good 
specification? 
10. how Specification may be develop?

SPECIFICATIONS

  • 1.
  • 2.
    What are wegoing to know about Specification? • What is Specification? • Kinds of Specification • How Specification may be develop? • Uses of Specification • Guidance • Process capability considerations
  • 3.
    Note: please takenote of the bolded words.
  • 4.
    What is Specification? • Specification (often abbreviated as spec) is an explicit set of requirements to be satisfied by a material, product, or service. • a type of technical standard. • Should a material, product or service fail to meet one or more of the applicable specifications.
  • 5.
    how Specification maybe develop? • A technical specification may be developed by any of various kinds of organizations, both public and private.  . Example organization types include a corporation, a consortium (a small group of corporations), a trade association (an industry-wide group of corporations), a national government (including its military, regulatory agencies, and national laboratories and institutes), a professional association (society), or a purpose-made standards organization such as ISO.
  • 6.
    Kinds of Specification Formal specification Program specification Functional specification Web service specification Document specification
  • 7.
    Formal specification •is a mathematical description of software or hardware that may be used to develop an implementation • It describes what the system should do, not (necessarily) how the system should do it • it is possible to use formal verification techniques to demonstrate that a candidate system design is correct with respect to the specification • This has the advantage that incorrect candidate system designs can be revised before a major investment has been made in actually implementing the design
  • 8.
    Program specification •the definition of what a computer program is expected to do • It can be informal, in which case it can be considered as a user manual from a developer point of view, or formal, in which case it has a definite meaning defined in mathematical or programmatic terms • In practice, many successful specifications are written to understand and fine-tune applications that were already well-developed, although safety-critical software systems are often carefully specified prior to application development • Specifications are most important for external interfaces that must remain stable.
  • 9.
    Functional specification •In software development, a functional specification (also, functional spec or specs or functional specifications document (FSD)) is the set of documentation that describes the behavior of a computer program or larger software system • The documentation typically describes various inputs that can be provided to the software system and how the system responds to those inputs.
  • 10.
    Web service specification • Web services specifications are often under the umbrella of a quality management system
  • 11.
    Document specification •These types of documents define how a specific document should be written, which may include, but is not limited to, the systems of a document naming, version, layout, referencing, structuring, appearance, language, copyright, hierarchy or format, etc • Very often, this kind of specifications is complemented by a designated template.
  • 12.
    • It iscommon for one organization to refer to (reference, call out, cite) the standards of another. • . Voluntary standards may become mandatory if adopted by a government or business contract. Sometimes the term specification is used in connection with a data sheet (or spec sheet). •describes the technical characteristics of an item or product. •It can be published by a manufacturer to help people choose products or to help use the products •is not a technical specification as described in this article.
  • 13.
    Uses of Specification • In engineering, manufacturing, and business, it is vital for suppliers, purchasers, and users of materials, products, or services to understand and agree upon all requirements. • It is a type of a standard which is often referenced by a contract or procurement document. It provides the necessary details about the specific requirements.
  • 14.
    • Specifications maybe written by government agencies, standards organizations (ASTM, ISO, CEN, DoD, etc.), trade associations, corporations, and others. • A product specification does not necessarily prove a product to be correct. An item might be verified to comply with a specification or stamped with a specification number: This does not, by itself, indicate that the item is fit for any particular use. The people who use the item (engineers, trade unions, etc.) or specify the item (building codes, government, industry, etc.) have the responsibility to consider the choice of available specifications, specify the correct one, enforce compliance, and use the item correctly. Validation of suitability is necessary
  • 15.
    Guidance a standingoperating procedure is available to help write and format a good specification Specification may include the following: •Person, office, or agency responsible for questions on the specification, updates, and deviations. •The significance, scope or importance of the specification and its intended use. •Terminology, definitions and abbreviations to clarify the meanings of the specification[9][10] •Test methods for measuring all specified characteristics •Descriptive title, number, identifier, etc. of the specification •Date of last effective revision and revision designation •A logo or trademark to indicate the document copyright, ownership and origin[8] •Table of Contents (TOC), if the document is long
  • 16.
    • Material requirements:physical, mechanical, electrical, chemical, etc. Targets and tolerances. • Acceptance testing, including Performance testing requirements. Targets and tolerances. • Drawings, photographs, or technical illustrations • Workmanship • Certifications required. • Safety considerations and requirements • Environmental considerations and requirements • Quality control requirements, acceptance sampling, inspections, acceptance criteria • Provisions for rejection, reinspection, rehearing, corrective measures • References and citations for which any instructions in the content maybe required to fulfill the traceability and clarity of the document • Signatures of approval, if necessary • Change record to summarize the chronological development, revision and completion if the document is to be circulated internally • Annexes and Appendices that are expand details, add clarification, or offer options • Person, office, or agency responsible for enforcement of the specification. • Completion and delivery.
  • 17.
    Process capability considerations • A good engineering specification, by itself, does not necessarily imply that all products sold to that specification actually meet the listed targets and tolerances. Actual production of any material, product, or service involves inherent variation of output. With a normal distribution, the tails of production may extend well beyond plus and minus three standard deviations from the process average.
  • 18.
    • The processcapability of materials and products needs to be compatible with the specified engineering tolerances. Process controls must be in place and an effective Quality management system, such as Total Quality Management, needs to keep actual production within the desired tolerances. • Effective enforcement of a specification is necessary for it to be useful.
  • 21.
    BY: GROUP 3 LEADER: INGRID MARIE ACBANG SECRETARY: JULLIE ANGELINE BELEN REPORT MAKER: JOEDY MAE MANGAMPO MEMBERS: Mary grace orcine daryl samson jomar onding
  • 22.
    10- item quiz 1. What is Specification? 2.-6. Kinds of Specification 7-8. Give at least two things where we uses Specification 9. What is a standing operating procedure is available to help write and format a good specification? 10. how Specification may be develop?