hardware specification The hardware specification is the term used to describe the requirements of the PC hardware in various environments.

It depends on the demands of the end users who require reliability, consistent performance and integration of systems. It is also aimed to match the needs of the commercial and the industrial units. It enables the industrial people to work well with the software about which they have good know how. Hardware specification allows for much flexibility and adaptation at the users end especially with the industrial users. The industrial applications are unique and also require adequate training to staff in order to perform well. The hardware specifications of a computer will vary depending on what an individual user will be doing with it. A person that wants to use their computer for graphically intense games or video editing will need a totally different configuration than somebody that just wants to browse the Internet and type word documents. Take a look at this advertisement that was copied from an online store. technical specifications [teknkl spesfkshnz] (engineering) A detailed description of technical requirements stated in terms suitable to form the basis for the actual design, development, and production processes of an item having the qualities specified in the operational characteristics. Technical Specifications a document, included as part of the technical documentation of an industrial product, that states the technical requirements for the product, rules for acceptance and delivery, testing methods, and conditions for operation, transportation, and storage. Technical requirements define a products basic parameters and dimensions, properties or performance characteristics, quality indices, and the complete product system, which includes spare parts, materials, and documents. The rules for acceptance and delivery state the procedure and conditions for carrying out control testing when the manufacturing plant submits the product for delivery and the client accepts it. The section on testing methods (testing, analyses, and measurements) establishes the following: methods for determining all parameters and characteristics of the product corresponding to the relevant standards and requirements; rules for sampling or testing and for the selection of equipment, instruments, materials, and reagents; and procedures for preparing and conducting tests, analyses, and measurements and methods used to process the results. The section covering conditions for operation, transportation, and storage contains instructions on assembly, installation, and use of the product; rules for packing and transportation; and permissible locations, conditions, and durations of storage. Technical specifications may pertain to individual types of products or to groups of products. In the USSR technical specifications are compiled in accordance with All-Union State Standards and are confirmed and registered by bodies of Gosstandart (the USSR State Committee for Standards). Technical specifications remain in force for a limited period of time. When a certain level of production is attained, they are replaced by All-Union State Standards based on the original technical specifications. >> software specification A document that describes what the software will do (e.g., how it works, what the screens look like, what happens when a button is clicked, etc.) Generally this is the first step of software programming. The software requirements specification document enlists all necessary requirements for project development.[1] To derive the requirements we need to have clear and thorough understanding of the products to be developed. This is prepared after detailed communications with project team and the customer. A general organization of an SRS is as follows [2][3] Software requirements specification A software requirements specification (SRS) is a complete description of the behavior of the system to be developed. It includes a set of use cases that describe all of the interactions that the users will have with the software. Use cases are also known as functional requirements. In addition to use cases, the SRS also contains nonfunctional (or supplementary) requirements. Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance requirements, quality standards, or design constraints). Recommended approaches for the specification of software requirements are described by IEEE 830-1998. This standard describes possible structures, desirable contents, and qualities of a software requirements specification. Hardware Requirements [Describe hardware requirements and any related processes. Include a detailed description of specific hardware requirements and associate them to specific project functionality/deliverables. Include information such as type of hardware, brand name, specifications, size, security, etc. Assign a unique ID number to each requirement.] Software Requirements [Describe software requirements and any related processes. Include a detailed description of specific software requirements and associate them to specific project functionality/deliverables. Include information such as in-house development or purchasing, security, coding language, version numbering, functionality, data, interface requirements, brand name, specifications, etc. Assign a unique ID number to each requirement.] A technical requirement pertains to the technical aspects that your system must fulfill, such as performance-related issues, reliability issues, and availability issues. These types of requirements are often called quality of service (QoS) requirements, service-level requirements or non-functional requirements (I dont like that term as it makes them sound like requirements that wont work). Examples of technical requirements are presented in Figure 1. As you can see, technical requirements are summarized in a similar manner as business rules: they have a name and a unique identifier (my convention is to use the format TR#, where TR stands for technical requirement). You document technical requirements in the same manner as business rules, including a description, an example, a source, references to related technical requirements, and a revision A detailed description of technical requirements, usually with specific acceptance criteria, stated in terms suitable to form the basis for the actual design development and production processes of an item having the qualities specified in the operational characteristics. See also operational characteristics.