Relevant bibliographies by topics / Specifications

Academic literature on the topic 'Specifications'

Author: Grafiati
Published: 4 June 2021
Last updated: 30 July 2024

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Contents

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Specifications.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Specifications"

1

NAKAMURA, M., W. KONG, K. OGATA, and K. FUTATSUGI. "A Specification Translation from Behavioral Specifications to Rewrite Specifications." IEICE Transactions on Information and Systems E91-D, no. 5 (May 1, 2008): 1492–503. http://dx.doi.org/10.1093/ietisy/e91-d.5.1492.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Easterling, W. Samuel, and Lisa Gonzalez Giroux. "Shear Lag Effects in Steel Tension Members." Engineering Journal 30, no. 3 (September 30, 1993): 77–89. http://dx.doi.org/10.62913/engj.v30i3.618.

Full text
Abstract:
The non-uniform stress distribution that occurs in a tension member adjacent to a connection, in which all elements of the cross section are not directly connected, is commonly referred to as the shear lag effect. This effect reduces the design strength of the member because the entire cross section is not fully effective at the critical section location. Shear lag effects in bolted tension members have been accounted for in the American Institute of Steel Construction (AISC) allowable stress design specification1 (ASD) since 1978. The 1986 load and resistance factor design specification2 (LRFD) and the 1989 ASD specification stipulate that the shear lag effects are applicable to welded, as well as bolted, tension members. Past research on the subject of shear lag has focused primarily on bolted tension members. Recently, more attention has been given to welded members, evident by their inclusion in the AISC specifications. Shear lag provisions for welded members were introduced into the specifications primarily because of a large welded hanger plate failure. To maintain a uniform approach to both welded and bolted members, the same provisions for shear lag in bolted members were applied to welded members. Additional requirements for welded plates were added. However, the application of the shear lag requirements to welded members has raised several questions. This paper examines shear lag in steel tension members in the following context. First, the background for the current AISC specification provisions is reviewed. Second, the results of an experimental research program in which 27 welded tension members were loaded to failure is presented. Third, based on the first two parts of the paper, recommended changes to the AISC specifications are presented.
APA, Harvard, Vancouver, ISO, and other styles
3

CORNELIUS, FELIX, MICHAEL BALDAMUS, HARTMUT EHRIG, and FERNANDO OREJAS. "Abstract and behaviour module specifications." Mathematical Structures in Computer Science 9, no. 1 (February 1999): 21–62. http://dx.doi.org/10.1017/s0960129598002606.

Full text
Abstract:
The theory of algebraic module specifications and modular systems was developed initially mainly on the basis of equational algebraic specifications. We show that it is in fact almost independent of what kind of underlying specification framework is chosen. More specifically, we present a formulation where this framework appears as an indexed category or, equivalently, specification frame. The ensuing theory is called the theory of abstract module specifications. We are able to prove main results concerning the correctness and compositionality of abstract module specifications in a purely categorical way, assuming the existence of pushouts of morphisms between abstract specifications that allow model amalgamation, functor extension and/or suitable free constructions. Then, by instantiating the theory of abstract module specifications to the behaviour specification frame in the sense of Nivela and Orejas, we obtain a theory of behaviour module specifications.
APA, Harvard, Vancouver, ISO, and other styles
4

Khazal, Ammar S., Nazar N. Ismael, and Adbulfattah Khalaf Husein. "Statistical Study to Check the Conformity of Aggregate in Kirkuk City to Requirement of Iraqi Specification." Tikrit Journal of Engineering Sciences 24, no. 2 (June 30, 2017): 11–27. http://dx.doi.org/10.25130/tjes.24.2.02.

Full text
Abstract:
This research reviews a statistical study to check the conformity of aggregates (Coarseand Fine) was used in Kirkuk city to the requirements of the Iraqi specifications. The data ofsieve analysis (215 samples) of aggregates being obtained from of National CentralConstruction Laboratory and Technical College Construction Laboratory in Kirkuk city haveanalyzed using the statistical program SAS. The results showed that 5%, 17%, and 18% of fineaggregate samples are passing sieve sizes 10 mm, 4.75 mm, and 2.36 mm, respectively, whichwere less than the minimum limit allowed by the Iraqi specifications for each sieve. Thepercentages passing sieve sizes 1.18mm, 600micrometers, and 300micrometers were morethan the upper limit of specification by 5%, 20%, and 30% respectively. The samples werepassing sieve sizes 1.18mm, and 600micrometers less than the minimum limit of specificationby 17%, and 4%, respectively. The results showed that the deviation in a sieve size of 150micrometers for the upper limit of the specification performs 2% of the total number of samples.For Coarse aggregate, the samples passing sieves size 37.5mm and 20mm were comfortingthe Iraqi specifications by 100% and 83% respectively, it has found that the samples werepassing sieve sizes 10mm was 5% was more than the higher limit of Iraqi specifications, and27% of these samples were less than the minimum limit, whereas sample passing sieve size5mm was 1% which is more than the upper limit of the Iraqi specification. As a result ofstatistical analysis of data for fine aggregate, it has found that the samples were passing sievesizes 10mm, 2.36mm, 1.18mm and 150micrometers conforming from statistical point of view theIraqi specifications, whereas the samples were passing sieve sizes 4.75mm, 600micrometersand 300 micrometers didn’t conform. Statistical analysis of the results of the coarse aggregatesalso showed that conforming to sieve sizes of 37.5mm and 20mm and didn’t conform for sievesizes 10mm and 5mm.
APA, Harvard, Vancouver, ISO, and other styles
5

ANTONIK, ADAM, MICHAEL HUTH, KIM G. LARSEN, ULRIK NYMAN, and ANDRZEJ WĄSOWSKI. "Modal and mixed specifications: key decision problems and their complexities." Mathematical Structures in Computer Science 20, no. 1 (February 2010): 75–103. http://dx.doi.org/10.1017/s0960129509990260.

Full text
Abstract:
Modal and mixed transition systems are specification formalisms that allow the mixing of over- and under-approximation. We discuss three fundamental decision problems for such specifications: —whether a set of specifications has a common implementation;—whether an individual specification has an implementation; and—whether all implementations of an individual specification are implementations of another one. For each of these decision problems we investigate the worst-case computational complexity for the modal and mixed cases. We show that the first decision problem is EXPTIME-complete for both modal and mixed specifications. We prove that the second decision problem is EXPTIME-complete for mixed specifications (it is known to be trivial for modal ones). The third decision problem is also shown to be EXPTIME-complete for mixed specifications.
APA, Harvard, Vancouver, ISO, and other styles
6

Fuchs, Norbert E., and David Robertson. "Declarative specifications." Knowledge Engineering Review 11, no. 4 (December 1996): 317–31. http://dx.doi.org/10.1017/s0269888900008018.

Full text
Abstract:
AbstractDeriving formal specifications from informal requirements is extremely difficult since one has to overcome the conceptual gap between an application domain and the domain of formal specification methods. To reduce this gap we introduce application-specific specification languages, i.e., graphical and textual notations that can be unambiguously mapped to formal specifications in a logic language. We describe a number of realised approaches based on this idea, and evaluate them with respect to their domain specificity vs. generality.
APA, Harvard, Vancouver, ISO, and other styles
7

Kovalev, Igor, Dmitry Kovalev, Komil Astanakulov, Valerya Podoplelova, Dmitry Borovinsky, and Svetlana Efa. "Conceptual basis for digitalization of specifications of transport and technological cycles of agricultural UAVs." E3S Web of Conferences 443 (2023): 06014. http://dx.doi.org/10.1051/e3sconf/202344306014.

Full text
Abstract:
The conceptual basis for digitalization of the specifications of transport and technological cycles of agricultural UAVs used in performing agrotechnical operations in smart agriculture is presented in the article. The basic properties of specifications have been studied. Methods for analyzing the main properties of specifications are considered and the relationship between specifications and the main stages of the life cycle of transport and technological cycles of UAVs is established. Based on GERT-oriented conceptual specification tools, a method for organizing conceptual specification tools based on GERT-like nodal logic is proposed in the article. Formalization of the GERT-network specification of transport and technological cycles of agricultural UAVs has been completed. The proposed approach to creating specifications for transport and technological cycles of UAVs in smart agriculture makes it possible to ensure full compliance of the specifications with the basic requirements for accuracy, clarity and completeness of description.
APA, Harvard, Vancouver, ISO, and other styles
8

HOUDEK, FRANK, THILO SCHWINN, and DIETMAR ERNST. "DEFECT DETECTION FOR EXECUTABLE SPECIFICATIONS — AN EXPERIMENT." International Journal of Software Engineering and Knowledge Engineering 12, no. 06 (December 2002): 637–55. http://dx.doi.org/10.1142/s0218194002001128.

Full text
Abstract:
The deployment of executable specifications has increased significantly in the last few years. Just as with any other specification documents, these specifications must be examined to ensure the necessary degree of quality. A common and successful technique used for examining traditional specifications is inspection. Now the question has arisen whether inspections on executable specification are the best choice, or if other techniques which use the execution capabilities of the models perform better. In this paper, we empirically compare several defect detection techniques for executable specifications. In particular, we examine inspections, testing, and ad-hoc simulation. Here, we use the specification languages Statemate and Matlab/Simulink. Also, we take a closer look at the inspection process itself and try to quantify the benefits of an inspection meeting for executable specifications.
APA, Harvard, Vancouver, ISO, and other styles
9

Geschwindner, Louis F. "Evolution of Shear Lag and Block Shear Provisions in the AISC Specification." Engineering Journal 43, no. 4 (December 31, 2006): 237–40. http://dx.doi.org/10.62913/engj.v43i4.892.

Full text
Abstract:
The American Institute of Steel Construction (AISC) has published two standards for design of steel structures for the past 19 years, an allowable stress specification, ASD, and a limit states specification, LRFD. The AISC Committee on Specifications has developed a new standard that includes provisions for design according to both ASD and LRFD. For connection design, the specification evolved as provisions from the previous specifications were integrated into the new provisions. This paper highlights the provisions for shear lag and block shear from the 2005 AISC Specification for Structural Steel Buildings provisions and the changes that have taken place from previous editions of the specifications.
APA, Harvard, Vancouver, ISO, and other styles
10

Quiroga, Cesar, David Ford, Timothy Taylor, Stanley Kranc, and Edgar Kraus. "Construction Specification Framework for Utility Installations." Transportation Research Record: Journal of the Transportation Research Board 2060, no. 1 (January 2008): 162–72. http://dx.doi.org/10.3141/2060-18.

Full text
Abstract:
Utility accommodation policies nationwide contain requirements for the accommodation, location, installation, relocation, and maintenance of utility facilities on the state right-of-way. The policies normally cover basic requirements, making it necessary to use additional specifications and special provisions to handle situations not covered by the policies. Frequently, because of the lack of standard utility installation construction specifications at transportation agencies, many different versions of special specifications and special provisions exist. Closely related to the need to standardize construction specifications for utility installations is the need to standardize methodologies and procedures for determining the cost of utility relocation. This lack of standardization translates into difficulties such as how to verify the validity of the cost data submitted for reimbursement and how to prepare adequately for audits and other internal and external inquiries. This paper summarizes the work completed to develop a prototype framework of construction specification requirements for utility installations, with a focus on water, sanitary sewer, and communication specifications. The specification framework includes five groups of specifications: earth work, pipes and boxes, appurtenances, other, and general (including specifications such as mobilization and traffic control, which highway construction contracts typically include but are also relevant to the utility relocation process). The framework uses tables that summarize the main characteristics of proposed new and modified standard specifications and includes a listing of pay items, subsidiary items, and corresponding measurement units. The framework also includes specification requirements.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Specifications"

1

Tan, Yang Meng. "Formal specification techniques for promoting software modularity, enhancing documentation, and testing specifications." Thesis, Massachusetts Institute of Technology, 1994. http://hdl.handle.net/1721.1/35391.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Utiome, Erezi Ame Emmanuel. "Extending building information models to construction specifications." Thesis, Queensland University of Technology, 2015. https://eprints.qut.edu.au/84929/1/Erezi_Utiome_Thesis.pdf.

Full text
Abstract:
This project examined the role that written specifications play in the building procurement process and the relationship that specifications should have with respect to the use of BIM within the construction industry. A three-part approach was developed to integrate specifications, product libraries and BIM. Typically handled by different disciplines within project teams, these provide the basis for a holistic approach to the development of building descriptions through the design process and into construction.
APA, Harvard, Vancouver, ISO, and other styles
3

Leung, Ping-hung Karl Richard. "Towards a semantics bridge between structured specifications and logic specifications /." [Hong Kong : University of Hong Kong], 1992. http://sunzi.lib.hku.hk/hkuto/record.jsp?B13212771.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Wong, Hong-Yee. "Abstract scene specifications." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 1997. http://www.collectionscanada.ca/obj/s4/f2/dsk3/ftp04/nq21323.pdf.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Simmons, Robert J. "Substructural Logical Specifications." Research Showcase @ CMU, 2012. http://repository.cmu.edu/dissertations/205.

Full text
Abstract:
A logical framework and its implementation should serve as a flexible tool for specifying, simulating, and reasoning about formal systems. When the formal systems we are interested in exhibit state and concurrency, however, existing logical frameworks fall short of this goal. Logical frameworks based on a rewriting interpretation of substructural logics, ordered and linear logic in particular, can help. To this end, this dissertation introduces and demonstrates four methodologies for developing and using substructural logical frameworks for specifying and reasoning about stateful and concurrent systems. Structural focalization is a synthesis of ideas from Andreoli’s focused sequent calculi and Watkins’s hereditary substitution. We can use structural focalization to take a logic and define a restricted form of derivations, the focused derivations, that form the basis of a logical framework. We apply this methodology to define SLS, a logical framework for substructural logical specifications, as a fragment of ordered linear lax logic. Logical correspondence is a methodology for relating and inter-deriving different styles of programming language specification in SLS. The styles we connect range from very high-level specification styles like natural semantics, which do not fully specify the control structure of programs, to low-level specification styles like destination-passing, which provide detailed control over concurrency and control flow. We apply this methodology to systematically synthesize a low-level destination-passing semantics for a Mini-ML language extended with stateful and concurrent primitives. The specification is mostly high-level except for the relatively few rules that actually deal with concurrency. Linear logical approximation is a methodology for deriving program analyses by performing abstract analysis on the SLS encoding of the language’s operational semantics. We demonstrate this methodology by deriving a control flow analysis and an alias analysis from suitable programming language specifications. Generative invariants are a powerful generalization of both context-free grammars and LF’s regular worlds that allow us to express invariants of SLS specifications in SLS.We show that generative invariants can form the basis of progress-andpreservation- style reasoning about programming languages encoded in SLS.
APA, Harvard, Vancouver, ISO, and other styles
6

Salgado, Fonseca Cerveira Pinto Helena Sofia Silva Borges. "Understanding service specifications." Thesis, University of Warwick, 2005. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.425519.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

NGUYEN, HONG PHUONG. "Derivation de specifications formelles b a partir de specifications semi-formelles." Paris, CNAM, 1998. http://www.theses.fr/1998CNAM0321.

Full text
Abstract:
Les methodes les plus utilisees en conception des systemes d'information sont basees principalement sur l'utilisation de diverses notations semi-formelles (diagrammes d'objets, diagrammes etats/transitions, ) qui presentent des avantages indeniables : puissance d'expression, vue graphique et synthetique du systeme d'information, faculte de communication avec les utilisateurs. Cependant il leur manque les qualites de concision, de precision et la possibilite de preuves des methodes formelles (basees en particulier sur la logique et la theorie des ensembles). Ce travail s'inscrit dans le cadre de l'integration des methodes semi-formelles et formelles. L'objectif de ce travail est de combiner leurs avantages respectifs en fournissant des regles de derivation de specifications formelles (en particulier en b) a partir de specifications semi-formelles (en particulier par objets). Tout d'abord, nous selectionnons les concepts les plus repandus des methodes semi-formelles et examinons precisement leur semantique. Cet examen nous conduit souvent a effectuer un choix entre plusieurs interpretations possibles des notations semi-formelles et meme a les completer lorsqu'elles s'averent insuffisantes pour decrire des situations reelles. Puis nous donnons des regles de traduction des concepts des modeles semi-formels en b. Notre objectif est de proposer des regles de derivation menant a une specification formelle a la fois comprehensible, fidele a la specification semi-formelle de depart, et modulaire afin de permettre des preuves incrementales et la reutilisation des composants. Afin de valider la methode de derivation, sont presentees trois etudes de cas developpees sous l'atelier b en appliquant nos regles.
APA, Harvard, Vancouver, ISO, and other styles
8

Tangvichachan, Theera. "Conversion of solid ink density and dot gain specifications into colorimetric specifications /." Online version of thesis, 1993. http://hdl.handle.net/1850/11886.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Alves, Campos de Sousa Dionísio Francisco Miguel. "Composition of hierarchic default specifications." [S.l. : s.n.], 1997. http://deposit.ddb.de/cgi-bin/dokserv?idn=95433891X.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Martinsson, Christoffer. "Requirements Specifications Simplified and Adapted." Thesis, Örebro University, Swedish Business School at Örebro University, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:oru:diva-4832.

Full text
Abstract:

Systems development projects and their documents are more or less standardized and can mainly be applied on systems that are supposed to be built from scratch, or updated. In pace with the number of IT-systems are increasing worldwide there is no need for every organization to build their own IT-system. Nowadays it is also possible to purchase licenses which allow the purchaser to modify or add functions to the system. Along with those changes, there have been an increased amount of “rapid development methods” such as Agile and “Quick and Dirty” solutions, but these methods and perspectives are mainly focusing on entire systems development processes, as the old ones, but quicker.

If a company purchases an off-the-shelf system with source code available, there is no real need to go through a proper systems development process. During interviews with a small company that has acquired a system as mentioned above, the researcher realized that only one single document is needed, the requirements specification. Today’s requirements specifications can be either well detailed or less, but a project still needs the details specified. Combining a known agile development process with IEEE’s standardized requirements specification, a new way to proceed with projects based on one single document (the requirements specification) has been made. This document also has a focus on simplicity for the inexperienced readers, but with the depth that every developer has got a use for.

APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Specifications"

1

Mark, Kalin, and Rosen Harold J, eds. Construction specifications writing: Principles and procedures. 6th ed. Hoboken, N.J: John Wiley & Sons, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Searstone, Ken. Specifications. Sheffield: Sheffield City Polytechnic Centre For Quality Assurance, 1987.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Fischer, James E. International petroleum specifications: Feedstock specifications. 4th ed. [Camden, Me.]: International Petroleum Specifications, 1995.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

Inc, International Petroleum Specifications, ed. International petroleum specifications: Product specifications. [Camden, Me.]: International Petroleum Specifications, Inc., 1992.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Inc, International Petroleum Specifications, ed. International petroleum specifications: Feedstock specifications. 3rd ed. [Camden, Me.]: International Petroleum Specifications, 1993.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Fischer, James E. International petroleum specifications: Product specifications. 2nd ed. [Camden, Me.]: International Petroleum Specifications, 1995.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Scott, Sidney, Linda Konrath, and Ted Ferragut. Framework for Performance Specifications: Guide for Specification Writers. Washington, D.C.: Transportation Research Board, 2013. http://dx.doi.org/10.17226/22558.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

French, Alan Paul. Generic specifications. Loughborough: Loughborough University Business School, 1993.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Association, Canadian Roofing Contractors'. Roofing specifications. [Ottawa]: Canadian Roofing Contractors Association, 1997.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Association, UK Steel, ed. Steel specifications. 9th ed. London: UK Steel Association, 1997.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Specifications"

1

Chrest, Anthony P. "Specifications." In Parking Structures, 573–84. Boston, MA: Springer US, 2001. http://dx.doi.org/10.1007/978-1-4615-1577-7_16.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Chrest, Anthony P. "Specifications." In Parking Structures, 313–95. Boston, MA: Springer US, 1996. http://dx.doi.org/10.1007/978-1-4684-9922-3_11.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Baily, P. J. H. "Specifications." In Purchasing and Supply Management, 145–55. Boston, MA: Springer US, 1987. http://dx.doi.org/10.1007/978-1-4899-6898-2_11.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Burdick, Richard K., David J. LeBlond, Lori B. Pfahler, Jorge Quiroz, Leslie Sidor, Kimberly Vukovinsky, and Lanju Zhang. "Specifications." In Statistical Applications for Chemistry, Manufacturing and Controls (CMC) in the Pharmaceutical Industry, 227–67. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-50186-4_7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Broy, Manfred, and Ketil Stølen. "Specifications." In Specification and Development of Interactive Systems, 69–99. New York, NY: Springer New York, 2001. http://dx.doi.org/10.1007/978-1-4613-0091-5_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Cohen, Edward. "Specifications." In Programming in the 1990s, 61–79. New York, NY: Springer New York, 1990. http://dx.doi.org/10.1007/978-1-4613-9706-9_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Maston, Gregory A., Tony R. Taylor, and Julie N. Villar. "Specifications." In Elements of STIL, 131–44. Boston, MA: Springer US, 2003. http://dx.doi.org/10.1007/978-1-4615-0463-4_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Laszlo, Ervin. "Specifications." In Introduction to Systems Philosophy, 23–32. London: Routledge, 2021. http://dx.doi.org/10.4324/9781003205586-4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Sitnikovski, Boro. "Specifications." In Introducing Software Verification with Dafny Language, 61–75. Berkeley, CA: Apress, 2022. http://dx.doi.org/10.1007/978-1-4842-7978-6_6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Nyce, David S. "Specifications." In Understanding Position Sensors, 17–76. Boca Raton: CRC Press, 2023. http://dx.doi.org/10.1201/9781003368991-2.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Specifications"

1

Liu, Shaoying. "Validating formal specifications using testing-based specification animation." In ICSE '16: 38th International Conference on Software Engineering. New York, NY, USA: ACM, 2016. http://dx.doi.org/10.1145/2897667.2897668.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Otto, Kevin N. "Forming Product Design Specifications." In ASME 1996 Design Engineering Technical Conferences and Computers in Engineering Conference. American Society of Mechanical Engineers, 1996. http://dx.doi.org/10.1115/96-detc/dtm-1517.

Full text
Abstract:
Abstract Design teams commonly form quantitative functional specification lists that define performance targets for a product. Meeting these specifications ensures that the customer needs are satisfied. A central difficulty is to identify the relevant metrics to use as specifications. A working methodology is presented here to establish relevant, quantitative, measurable performance specifications. To start, customer needs, their importances, and the customer use patterns are gathered for the product. Voice-of-the-customer methods are augmented to distinguish no-compromise constraints that must be met. Next, a design is analyzed to establish a representative function structure, applying Pahl and Beitz’s systematic design approach. An optimal function structure can now be defined by a condition of simultaneous maximum simplicity and comprehensive coverage of the gathered customer needs. The function structure can then be used as a list over which specifications are to be made, with at least one specification per sub-function. Having a rational function structure allows a team to more easily determine variables on which to make specifications. A team can then use the House of Quality to document and form consensus over these specifications in the typical way.
APA, Harvard, Vancouver, ISO, and other styles
3

Luna-Ortiz, Eduardo, Cathy Yao, Jon Barnes, Matthew Winter, and Matthew Healey. "Development of A CO2 Specification for Industrial CCS Transport Networks: Methodology, Limitations and Opportunities." In Offshore Technology Conference. OTC, 2022. http://dx.doi.org/10.4043/32103-ms.

Full text
Abstract:
Abstract Impurities in anthropogenic CO2 affect several aspects of a full-chain industrial CCS hub. The concentration and type of impurities expected from various CO2 sources will differ depending on the technology that is emitting CO2. Rather than provide individual specifications to different customers, a single specification approach is being usually considered. The intent of this specification is to provide a single requirement that all sources of CO2 must abide by. If different specifications were provided to different customers, the transport network might become reliant on acombination of users supplying CO2 at specified rates to meet an overall specification. Several CO2 specifications have been developed over the years. Although these specifications serve as guidance,each project/development will develop its own specification that is appropriate for its owncharacteristics. In this paper, we develop a multi-purpose fluid specification for a CCStransport hub. The specification is flexible as it takes into consideration a wide range of emitters,industry type and capture technology. We describe a development framework that takes intoconsideration: mechanical integrity (corrosion), operational integrity (two-phase zone, hydrateformation, water dropout, ductile fracture), HSE, storage capacity and integrity. The proposed specification contains a wide range ofimpurities but the limits in the specification are as broad as reasonably possible. Moreover, the CO2 specification covers a large range of operating conditions: from low pressure (gas phase) and highpressure (liquid phase). As we considered more than 30 species in the fluid, the proposed specificationhas a wider scope that current known industry standards (or even known projects). A comparison with other publicly available specifications is provided. In addition, the specification is heavily relying on good understanding of thethermodynamics of CO2 fluids with impurities: we assess and provide a comparative framework of themost adequate EoS for the chemical nature of the potential impurities. This paper offers an extended CO2 fluid specification for an industrialCCS transport system where a range of emitters (each of different nature) will tie-in. The proposedspecification offers a starting point for the design of CCS networks. It provides a common basis for thedesign of the components of the CCS system. We provide guidance on the specific issues that shouldbe particular for each project in order to optimize and customize the specification.
APA, Harvard, Vancouver, ISO, and other styles
4

Luna-Ortiz, Eduardo, Cathy Yao, Jon Barnes, Matthew Winter, and Matthew Healey. "Development of A CO2 Specification for Industrial CCS Transport Networks: Methodology, Limitations and Opportunities." In Offshore Technology Conference. OTC, 2022. http://dx.doi.org/10.4043/32103-ms.

Full text
Abstract:
Abstract Impurities in anthropogenic CO2 affect several aspects of a full-chain industrial CCS hub. The concentration and type of impurities expected from various CO2 sources will differ depending on the technology that is emitting CO2. Rather than provide individual specifications to different customers, a single specification approach is being usually considered. The intent of this specification is to provide a single requirement that all sources of CO2 must abide by. If different specifications were provided to different customers, the transport network might become reliant on acombination of users supplying CO2 at specified rates to meet an overall specification. Several CO2 specifications have been developed over the years. Although these specifications serve as guidance,each project/development will develop its own specification that is appropriate for its owncharacteristics. In this paper, we develop a multi-purpose fluid specification for a CCStransport hub. The specification is flexible as it takes into consideration a wide range of emitters,industry type and capture technology. We describe a development framework that takes intoconsideration: mechanical integrity (corrosion), operational integrity (two-phase zone, hydrateformation, water dropout, ductile fracture), HSE, storage capacity and integrity. The proposed specification contains a wide range ofimpurities but the limits in the specification are as broad as reasonably possible. Moreover, the CO2 specification covers a large range of operating conditions: from low pressure (gas phase) and highpressure (liquid phase). As we considered more than 30 species in the fluid, the proposed specificationhas a wider scope that current known industry standards (or even known projects). A comparison with other publicly available specifications is provided. In addition, the specification is heavily relying on good understanding of thethermodynamics of CO2 fluids with impurities: we assess and provide a comparative framework of themost adequate EoS for the chemical nature of the potential impurities. This paper offers an extended CO2 fluid specification for an industrialCCS transport system where a range of emitters (each of different nature) will tie-in. The proposedspecification offers a starting point for the design of CCS networks. It provides a common basis for thedesign of the components of the CCS system. We provide guidance on the specific issues that shouldbe particular for each project in order to optimize and customize the specification.
APA, Harvard, Vancouver, ISO, and other styles
5

Walsh, Kenneth F. "Optical Shop Specifications." In Optical Fabrication and Testing. Washington, D.C.: Optica Publishing Group, 1990. http://dx.doi.org/10.1364/oft.1990.owa1.

Full text
Abstract:
This tutorial will explore the process of establishing the specifications for optical components. It is intended to help the Optical Shop Supervisor or Process Engineer gain a better understanding of the reasons behind the specifications sent to the shop by the designers. The factors considered by the Optical Designer and Engineer in selecting materials, finishes, and tolerances, as well as the consequence of excessive variance from specification.
APA, Harvard, Vancouver, ISO, and other styles
6

Correa, Alexandre, Cláudia Werner, and Márcio Barros. "Enhancing the Understandability of OCL Specifications." In Simpósio Brasileiro de Engenharia de Software. Sociedade Brasileira de Computação, 2007. http://dx.doi.org/10.5753/sbes.2007.21297.

Full text
Abstract:
OCL (Object Constraint Language) is the OMG standard language for the precise specification of constraints associated to MOF-compliant models and meta-models. Although OCL has been created with the intention to be a simpler language when compared to traditional formal specification languages, it is common to find specifications containing OCL constraints that are difficult to understand and evolve. This paper presents a set of potential problematic constructions often found in specifications written in OCL and a set of refactorings that can be applied to remove them. We also present an experimental study that has been performed to evaluate the effects of applying those strategies on the understandability of OCL specifications.
APA, Harvard, Vancouver, ISO, and other styles
7

von Bochmann, G., and R. Gotzhein. "Deriving protocol specifications from service specifications." In the ACM SIGCOMM conference. New York, New York, USA: ACM Press, 1986. http://dx.doi.org/10.1145/18172.18190.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Kim, Hyungtae, Youngho Lee, and Taejin Kim. "Optimization of Body Parts Specifications Using A.I Technology." In WCX SAE World Congress Experience. 400 Commonwealth Drive, Warrendale, PA, United States: SAE International, 2024. http://dx.doi.org/10.4271/2024-01-2017.

Full text
Abstract:
<div class="section abstract"><div class="htmlview paragraph">Optimizing the specifications of the parts that make up the vehicle is essential to develop a high performance and quality vehicle with price competitiveness. Optimizing parts specifications for quality and affordability means optimizing various factors such as engineering design specifications and manufacturing processes of parts. This optimization process must be carried out in the early stages of development to maximize its effectiveness. Therefore, in this paper, we studied the methodology of building a database for parts of already developed vehicles and optimizing them on a data basis. A methodology for collecting, standardizing, and analyzing data was studied to define information necessary for specification optimization. In addition, AI technology was used to derive optimization specifications based on the 3D shape of the parts. Through this study, body parts specification optimization system using AI technology was developed. Then, the simulation confirmed that using this system improves work efficiency and has a great effect on specification optimization.</div></div>
APA, Harvard, Vancouver, ISO, and other styles
9

Sun, Nuogang, Youyun Zhang, and Xuesong Mei. "A Simplified Systematic Method of Acquiring Design Specifications From Customer Requirements." In ASME 2007 International Design Engineering Technical Conferences and Computers and Information in Engineering Conference. ASMEDC, 2007. http://dx.doi.org/10.1115/detc2007-34769.

Full text
Abstract:
Faithfully obtaining design specifications from customer requirements is essential for successful designs. The natural lingual, inexact, incomplete and vague attributes of customer requirements make it very difficult to map customer requirements to design specifications. In general design process, the design specifications are determined by designers based on their experience and intuition, and often a certain target value is set for a specification. However, it is on one hand very difficult, on the other hand unreasonable, so a suitable limit range rather than a certain value is preferred at the beginning of design, especially at the concept design process. In this paper, a simplified systematic approach of transforming customer requirements to design specifications is proposed. First, a two-stepped clustering approach for grouping customer requirements and design specifications based on HOQ matrix is presented, by which the mapping is limited to within each group. To further simplify the inference mapping rules of customer requirements and design specifications, the minimal condition inference mapping rules for each design specification are extracted based on rough set theory. In the end, a suitable value range is determined for a specification by applying the fuzzy rule matrix.
APA, Harvard, Vancouver, ISO, and other styles
10

Sampson, E. R., and R. Sulit. "Development of Machine Element OEM and Repair Specifications." In ITSC 2000, edited by Christopher C. Berndt. ASM International, 2000. http://dx.doi.org/10.31399/asm.cp.itsc2000p1309.

Full text
Abstract:
Abstract MIL-STD-1687 (SH) has been in use for many years as one of the specifications that the United States Military performs thermal spray operations at overhaul facilities. The U.S. NAVY has asked AWS (American Welding Society) to develop an ANSI/AWS national standard to replace it and then provide long range maintenance of the new specification when necessary. This paper discusses both the procedure used to develop this standard and the content of the specification. Particular attention will be paid to the quality controls, training of operators and use of other specifications to accomplish compliance with this specification. The approval process for this document will be discussed with a probable time line including a plan to publicize and smoothly replace the MIL-STD-1687 (SH) specification. The further integration and use of it globally will be discussed and recommendations presented. The new standard will be in harmony with the ISO thermal spray standards program.
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Specifications"

1

Mathey, Robert G., and James R. Clifton. Guide specifications and reference specification system. Gaithersburg, MD: National Institute of Standards and Technology, 1989. http://dx.doi.org/10.6028/nist.ir.89-4094.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Anlauff, Matthias, Dusko Pavlovic, and Douglas R. Smith. Specification-Carrying Software: Evolving Specifications for Dynamic System Composition. Fort Belvoir, VA: Defense Technical Information Center, February 2005. http://dx.doi.org/10.21236/ada430917.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Montgomery, Doug, Mark Carson, Timothy Winters, Michayla Newcombe, and Timothy Carlin. NIST IPv6 Profile. National Institute of Standards and Technology, November 2020. http://dx.doi.org/10.6028/nist.sp.500-267ar1.

Full text
Abstract:
This profile establishes a basic taxonomy of IPv6 capabilities, defined in terms of IETF specifications, resulting in specific capability labels for common network functions and usage scenarios. The profile maps each such labeled capability to one or more specific technical specifications, or parts of specifications. Each labeled capability adopts by reference the normative requirements of the cited specifications. In rare cases the profile may augment or modify the normative requirements of a base specification. The defined capability labels effectively form a vocabulary for expressing IPv6 requirements for, and documenting the IPv6 capabilities of, specific products. It is expected that, when combined with specific acquisition and product testing programs, this profile can facilitate the efficient adoption of IPv6 technologies in many industry sectors.
APA, Harvard, Vancouver, ISO, and other styles
4

Montgomery, Doug, Mark Carson, Timothy Winters, Michayla Newcombe, and Timothy Carlin. USGv6 Profile. National Institute of Standards and Technology, November 2020. http://dx.doi.org/10.6028/nist.sp.500-267br1.

Full text
Abstract:
This profile establishes a basic taxonomy of IPv6 capabilities, defined in terms of IETF specifications, resulting in specific capability labels for common network functions and usage scenarios. The profile maps each such labeled capability to one or more specific technical specifications, or parts of specifications. Each labeled capability adopts by reference the normative requirements of the cited specifications. In rare cases the profile may augment or modify the normative requirements of a base specification. The defined capability labels effectively form a vocabulary for expressing IPv6 requirements for, and documenting the IPv6 capabilities of, specific products. It is expected that this profile, when combined with the USGv6 Test Program, can facilitate the efficient adoption of IPv6 technologies in Federal information systems.
APA, Harvard, Vancouver, ISO, and other styles
5

Gardner C. J. BOOSTER INFLECTOR SPECIFICATIONS. Office of Scientific and Technical Information (OSTI), February 1990. http://dx.doi.org/10.2172/1150537.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Duffy, P., and P. Stefan. LCLS XTOD UHV Specifications. Office of Scientific and Technical Information (OSTI), March 2007. http://dx.doi.org/10.2172/909640.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Hagerty, K. J. 310 Facility chemical specifications. Office of Scientific and Technical Information (OSTI), May 1997. http://dx.doi.org/10.2172/10148694.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

CORPS OF ENGINEERS WASHINGTON DC. Engineering and Design: Specifications. Fort Belvoir, VA: Defense Technical Information Center, December 1998. http://dx.doi.org/10.21236/ada404159.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Burch, Hal, Fred Long, and Robert Seacord. Specifications for Managed Strings. Fort Belvoir, VA: Defense Technical Information Center, May 2006. http://dx.doi.org/10.21236/ada449432.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Luecke, William E., Thomas A. Siewert, and Frank W. Gayle. Contemporaneous structural steel specifications. Gaithersburg, MD: National Institute of Standards and Technology, 2005. http://dx.doi.org/10.6028/nist.ncstar.1-3a.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Specifications' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography