Добірка наукової літератури з теми "Interface and specification languages"

Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями

Оберіть тип джерела:

Ознайомтеся зі списками актуальних статей, книг, дисертацій, тез та інших наукових джерел на тему "Interface and specification languages".

Біля кожної праці в переліку літератури доступна кнопка «Додати до бібліографії». Скористайтеся нею – і ми автоматично оформимо бібліографічне посилання на обрану працю в потрібному вам стилі цитування: APA, MLA, «Гарвард», «Чикаго», «Ванкувер» тощо.

Також ви можете завантажити повний текст наукової публікації у форматі «.pdf» та прочитати онлайн анотацію до роботи, якщо відповідні параметри наявні в метаданих.

Статті в журналах з теми "Interface and specification languages":

1

Hatcliff, John, Gary T. Leavens, K. Rustan M. Leino, Peter Müller, and Matthew Parkinson. "Behavioral interface specification languages." ACM Computing Surveys 44, no. 3 (June 2012): 1–58. http://dx.doi.org/10.1145/2187671.2187678.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Paulweber, Philipp, Georg Simhandl, and Uwe Zdun. "Specifying with Interface and Trait Abstractions in Abstract State Machines: A Controlled Experiment." ACM Transactions on Software Engineering and Methodology 30, no. 4 (July 2021): 1–29. http://dx.doi.org/10.1145/3450968.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Анотація:
Abstract State Machine (ASM) theory is a well-known state-based formal method. As in other state-based formal methods, the proposed specification languages for ASMs still lack easy-to-comprehend abstractions to express structural and behavioral aspects of specifications. Our goal is to investigate object-oriented abstractions such as interfaces and traits for ASM-based specification languages. We report on a controlled experiment with 98 participants to study the specification efficiency and effectiveness in which participants needed to comprehend an informal specification as problem (stimulus) in form of a textual description and express a corresponding solution in form of a textual ASM specification using either interface or trait syntax extensions. The study was carried out with a completely randomized design and one alternative (interface or trait) per experimental group. The results indicate that specification effectiveness of the traits experiment group shows a better performance compared to the interfaces experiment group, but specification efficiency shows no statistically significant differences. To the best of our knowledge, this is the first empirical study studying the specification effectiveness and efficiency of object-oriented abstractions in the context of formal methods.
3

ACHEE, B. L., and DORIS L. CARVER. "OBJECT EXTENSIONS TO Z: A SURVEY." International Journal of Software Engineering and Knowledge Engineering 06, no. 03 (September 1996): 507–30. http://dx.doi.org/10.1142/s0218194096000211.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Анотація:
Formal specification languages provide assistance to solving the problem of high maintenance costs caused by ineffective communication of a system’s requirements. Using a sound mathematical basis, a formal specification language provides a precise and definitive system description that can serve as a binding contract. Additionally, the integration of the object-oriented paradigm with a formal specification language provides increased potential for software reuse, conceptually cleaner specifications and a framework for defining interfaces. To this end, there has been significant work done to extend existing specification languages to allow object-oriented specifications. This paper provides a comparison of such object-oriented specification languages, specifically, those extending Z. The paper is organized into five major sections. After a brief introduction to the concepts of formal specification languages and Z, a simple library system is defined and used as an example throughout the paper. Each of the object-oriented specification languages is introduced and classified as either using Z in an object-oriented style or providing a true object-oriented extension of Z. For each language, the specification of the example library system is presented following a brief overview of the language’s features. An in-depth comparison is made of each of the languages which provide a true object-oriented extension of Z.
4

Lima, Lucas, Rodrigo Bonifácio, Edna Canedo, Thiago Mael de Castro, Ricardo Fernandes, Alisson Palmeira, and Uirá Kulesza. "NeoIDL: A Domain Specific Language for Specifying REST Contracts Detailed Design and Extended Evaluation." International Journal of Software Engineering and Knowledge Engineering 25, no. 09n10 (November 2015): 1653–75. http://dx.doi.org/10.1142/s0218194015400379.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Анотація:
Service-oriented computing has emerged as an effective approach for integrating business (and systems) that might spread throughout different organizations. A service is a unit of logic modularization that hides implementation details using well-defined contracts. However, existing languages for contract specification in this domain present several limitations. For instance, both WSDL and Swagger use language-independent data formats (XML and JSON) that are not suitable for specifying contracts and often lead to heavyweight specifications. Interface description languages, such as CORBA IDL and Apache Thrift, solve this issue by providing specific languages for contract specifications. Nevertheless, these languages do not target to the REST architectural style and lack support for language extensibility. In this paper we present the design and implementation of NeoIDL, an extensible domain specific language and program generator for writing REST based contracts that are further translated into service’s implementations. In addition, we also present a systematic evaluation of our approach from different perspectives, which involved the implementation of different services using NeoIDL from the domain of Command & Control. In particular, we found initial evidences that shows that NeoIDL can contribute: (i) to bring return on investment with respect to the design and development of NeoIDL, after the implementation of 4 to 7 services; and (ii) to reduce significantly the number of lines of specification when compared to an existing service specification language such as Swagger.
5

SINGH, NARINDER, MICHAEL GENESERETH, and MUSTAFA SYED. "A DISTRIBUTED AND ANONYMOUS KNOWLEDGE SHARING APPROACH TO SOFTWARE INTEROPERATION." International Journal of Cooperative Information Systems 04, no. 04 (December 1995): 339–67. http://dx.doi.org/10.1142/s0218843095000159.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Анотація:
The support for automatic interoperation of software components can reduce cost and provide greater functionality. This paper describes a novel approach to software interoperation based on specification sharing. Software components, called agents, provide machine processable descriptions of their capabilities and needs. Agents can be realized in different programming languages, and they can run in different processes on different machines. In addition, agents can be dynamic — at run time agents can join the system or leave. The system uses the declarative agent specifications to automatically coordinate their interoperation. The architecture supports anonymous interoperation of agents, where each agent has the illusion that the capabilities of all the other agents are provided directly by the system. The distinctive feature of this approach is the expressiveness of the declarative specification language, which enables sophisticated agent interoperation, e.g. decomposing complex requests into a collection of simpler requests, and translating between the interface of a requesting agent and the interface of an agent that can service the request. The agent-based interoperation scheme relies on a shared vocabulary, and it is our thesis that more effective software interoperation is made possible by agreeing to a shared declarative vocabulary, than by agreeing to procedural interface specifications that do not address the semantics of the software component (e.g. object interface specifications in an object-oriented programming environment).
6

Dandekar, Abhay, Ibrahim Zeid, and Theodore Bardasz. "User interface for specification language for case-based mechanical design." Artificial Intelligence for Engineering Design, Analysis and Manufacturing 11, no. 1 (January 1997): 17–31. http://dx.doi.org/10.1017/s0890060400001815.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Анотація:
AbstractCase-based design (CBD) systems aim to solve a design problem by tailoring previously solved design problems to the current problem. Designers' specifications are used for indexing the knowledge base of the CBD system to retrieve an appropriate design case. Menu-based systems fail to capture designers' specifications effectively due to lack of expressiveness, while natural language systems are too immature to satisfy the goal. This paper presents the development of a graphical user interface (GUI) to implement a mechanical design specification language (MDSL) (Stelling, 1994) used to facilitate indexing in case-based mechanical design. The specification language is context-free and hence computable. It represents mechanical design knowledge in a (feature):(attribute) format suitable for indexing. An augmented transition network (ATN) parser is built using the grammar of the specification language. The parser provides syntactic as well as semantic checks. It also has capabilities to expand grammar and to adapt to a specific user domain. A graphical front end to the parser assists and guides the user through the specification language syntax in entering the design specifications. Provisions have been made to expand or edit the language grammar and vocabulary. The ATN parser was implemented in Common Lisp and the graphical user interface was written using the Gold Hill Windows Toolkit. Sample user interactions with the interface and screen dumps of the GUI are included.
7

Cheon, Yoonsik, and Gary T. Leavens. "The Larch/Smalltalk interface specification language." ACM Transactions on Software Engineering and Methodology 3, no. 3 (July 1994): 221–153. http://dx.doi.org/10.1145/196092.195325.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
8

SAVIDIS, ANTHONY, MARGHERITA ANTONA, and CONSTANTINE STEPHANIDIS. "A DECISION-MAKING SPECIFICATION LANGUAGE FOR VERIFIABLE USER-INTERFACE ADAPTATION LOGIC." International Journal of Software Engineering and Knowledge Engineering 15, no. 06 (December 2005): 1063–94. http://dx.doi.org/10.1142/s0218194005002646.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Анотація:
In automatic user interface adaptation, developers pursue the delivery of best-fit user interfaces according to the runtime-supplied profiles of individual end users and usage contexts. Software engineering of automatic interface adaptability entails: (a) storage and processing of user and usage-context profiles; (b) design and implementation of alternative interface components, to optimally support the various user activities and interface operations for different users and usage contexts; and (c) runtime decision-making, to choose on the fly the most appropriate alternative interface components, given the particular user and context profile. In automatic interface adaptation, the decision making process plays a key role in optimal on-the-fly interface assembly, engaging consolidated design wisdom in a computable form. A verifiable language has been designed and implemented which is particularly suited for the specification of adaptation-oriented decision-making logic, while also being easily deployable and usable by interface designers. This paper presents the language, its contextual role in adapted interface delivery and the automatic verification method. The employment of the language in an adaptation-design support tool is discussed, the latter automatically generating language rules by relying upon adaptation rule patterns. Finally, the deployment methodology of the language in supporting dynamic interface assembly is discussed, further generalizing towards dynamic software assembly, by introducing architectural contexts and polymorphic architectural containment.
9

Rath, Kamlesh, Venkatesh Choppella, and Steven D. Johnson. "Decomposition of Sequential Behavior Using Interface Specification and Complementation." VLSI Design 3, no. 3-4 (January 1, 1995): 347–58. http://dx.doi.org/10.1155/1995/74543.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Анотація:
Decomposition of system behavior along functional boundaries into interacting sequential components is a key step in top-down system design. In this paper, we present sequential decomposition, a method for factoring sequential components from a system specification based on interface specifications of the components. The resulting components can be independently synthesized, or realized using off-the-shelf components. We introduce interface specification language (ISL), based on finite-state machine semantics, to specify the input/output behavior of synchronous sub-systems. A component is factored from a system by embedding an implementation of the complement of its interface into the system description. The composition of a machine with its complement is shown to be isomorphic to the machine, and the composition of a machine with an implementation of its component is shown to be a safe interaction. We apply sequential decomposition to a non-trivial example, a special-purpose computer with Scheme programming language primitives as its instructions.
10

Castro Silva, Daniel, Pedro Henriques Abreu, Luís Paulo Reis, and Eugénio Oliveira. "Development of flexible languages for scenario and team description in multirobot missions." Artificial Intelligence for Engineering Design, Analysis and Manufacturing 31, no. 1 (May 2, 2016): 69–86. http://dx.doi.org/10.1017/s0890060416000184.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Анотація:
AbstractThe work described in this paper is part of the development of a framework to support the joint execution of cooperative missions by a group of vehicles, in a simulated, augmented, or real environment. Such a framework brings forward the need for formal languages in which to specify the vehicles that compose a team, the scenario in which they will operate, and the mission to be performed. This paper introduces the Scenario Description Language (SDL) and the Team Description Language (TDL), two Extensible Markup Language based dialects that compose the static components necessary for representing scenario and mission knowledge. SDL provides a specification of physical scenario and global operational constraints, while TDL defines the team of vehicles, as well as team-specific operational restrictions. The dialects were defined using Extensible Markup Language schemas, with all required information being integrated in the definitions. An interface was developed and incorporated into the framework, allowing for the creation and edition of SDL and TDL files. Once the information is specified, it can be used in the framework, thus facilitating environment and team specification and deployment. A survey answered by practitioners and researchers shows that the satisfaction with SDL+TDL is elevated (the overall evaluation of SDL+TDL achieved a score of 4 out of 5, with 81%/78.6% of the answers ≥4); in addition, the usability of the interface was evaluated, achieving a score of 86.7 in the System Usability Scale survey. These results imply that SDL+TDL is flexible enough to represent scenarios and teams, through a user-friendly interface.

Дисертації з теми "Interface and specification languages":

1

Hussain, Faraz. "Enhancing a behavioral interface specification language with temporal logic features." [Ames, Iowa : Iowa State University], 2009.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Sousa, Vasco Nuno da Silva de. "Model driven development implementation of a control systems user interfaces specification tool." Master's thesis, FCT - UNL, 2009. http://hdl.handle.net/10362/1961.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Lallier, Martial. "Un environnement d'édition evolué, graphique et syntaxique, pour la conception des systemes repartis." Nancy 1, 1988. http://www.theses.fr/1988NAN10284.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Анотація:
Proposition d' un outil d' assistance à l' utilisateur dans les problèmes d' édition et de contrôle des différents niveaux de descriptions intervenant lors de la conception d' application informatiques réparties
4

Duan, Daliang. "Epsp : un environnement support de genie logiciel base sur l'approche du prototypage de systeme et sur le langage prolog." Toulouse 3, 1987. http://www.theses.fr/1987TOU30223.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Анотація:
Epsp offre une interface informelle pour etablir un prototype de systeme en prolog (psp). Cette interface a essentiellement pour but de rendre prolog le plus transparent possible a l'utilisateur. Epsp utilise une specification executable comme prototype, ecrit en prolog. Epsp permet le raffinage a partir de la specification par tranformation successive du psp. Epsp est constitue de plusieurs outils logiciels. Il est developpe en prolo nongp et pascal
5

Willison, Richard. "PyGraph : a graphic front-end for the PAISLey executable specification language /." Online version of thesis, 1987. http://hdl.handle.net/1850/10142.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Ashlund, Stacey Lynn. "IDEAL : a tool to enable usability specification and evaluation /." Thesis, This resource online, 1992. http://scholar.lib.vt.edu/theses/available/etd-12052009-020100/.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Meyer, Randall Paul. "Semantic specification using tree manipulation languages." W&M ScholarWorks, 1988. https://scholarworks.wm.edu/etd/1539623776.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Анотація:
Software tools are used to generate compilers automatically from formal descriptions of languages. Methods for specifying the syntax of languages are well-established and well-understood; however, methods for formal semantic specification are not. The method most commonly used for semantic specification is an attribute grammar.;This thesis examines an alternative method of semantic specification. TreeSem is defined as a Tree Manipulation Language applicable to semantic specification. A TreeSem program is easier to read and to write than a corresponding attribute grammar specification.;Algorithms for translation of a TreeSem program into an equivalent attribute grammar specification, and for translation of an attribute grammar specification into an equivalent Tree Sem program are presented. Proof of correctness of the algorithms is discussed. The dual translations show the theoretical "specification power" of TreeSem to be the same as that of attribute grammars. Also, since both translations are provided, the compiler writer is free to choose the semantic specification method he wishes to use. The appropriate translation can be applied to implement the compiler using the more efficiently interpreted method, as research continues to improve the executable efficiency of either method.
8

England, David. "Graphical support for user interface specification." Thesis, Lancaster University, 1990. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.306558.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Martin, Patrick J. "Motion description languages: from specification to execution." Diss., Georgia Institute of Technology, 2010. http://hdl.handle.net/1853/33860.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Анотація:
Many emerging controls applications have seen increased operational complexity due to the deployment of embedded, networked systems that must interact with the physical environment. In order to manage this complexity, we design different control modes for each system and use motion description languages (MDL) to specify a sequence of these controllers to execute at run-time. Unfortunately, current MDL frameworks lose some of the important details (i.e. power, spatial, or communication capabilities) that affect the execution of the control modes. This work presents several computational tools that work towards closing MDL's specification-to-execution gap, which can result in undesirable behavior of complex systems at run-time. First, we develop the notion of an MDL compiler for control specifications with spatial, energy, and temporal constraints. We define a new MDL for networked systems and develop an algorithm that automatically generates a supervisor to prevent incorrect execution of the multi-agent MDL program. Additionally, we derive conditions for checking if an MDL program satisfies actuator constraints and develop an algorithm to insert new control modes that maintain actuator bounds during the execution of the MDL program. Finally, we design and implement a software architecture that facilitates the development of control applications for systems with power, actuator, sensing, and communication constraints.
10

Zimmerman, Marc Kenton 1975. "Investigating the readability of formal specification languages." Thesis, Massachusetts Institute of Technology, 2001. http://hdl.handle.net/1721.1/82206.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.

Книги з теми "Interface and specification languages":

1

Liang, Sheng. The Java Native interface: Programmer's guide and specification. Reading, Mass: Addison-Wesley, 1999.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Grimm, Christoph, ed. Languages for System Specification. Boston, MA: Springer US, 2004. http://dx.doi.org/10.1007/b116586.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Bjørner, Dines, and Martin C. Henson, eds. Logics of Specification Languages. Berlin, Heidelberg: Springer Berlin Heidelberg, 2007. http://dx.doi.org/10.1007/978-3-540-74107-7.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
4

Villar, Eugenio, and Jean Mermet, eds. System Specification & Design Languages. Boston, MA: Springer US, 2003. http://dx.doi.org/10.1007/b105967.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Andrews, D. J., J. F. Groote, and C. A. Middelburg, eds. Semantics of Specification Languages (SoSL). London: Springer London, 1994. http://dx.doi.org/10.1007/978-1-4471-3229-5.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Kaźmierski, Tom J., and Adam Morawiec, eds. System Specification and Design Languages. New York, NY: Springer New York, 2012. http://dx.doi.org/10.1007/978-1-4614-1427-8.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Bergé, Jean-Michel. High-Level System Modeling: Specification Languages. Boston, MA: Springer US, 1995.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Villar, Eugenio, ed. Embedded Systems Specification and Design Languages. Dordrecht: Springer Netherlands, 2008. http://dx.doi.org/10.1007/978-1-4020-8297-9.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Langworthy, David. The Oslo modeling language: Draft specification. Upper Saddle River, NJ: Addison-Wesley Professional, 2008.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Guttag, John. Larch: Languages and Tools for Formal Specification. New York City, New York, USA: Springer, 1993.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.

Частини книг з теми "Interface and specification languages":

1

Roubtsova, E. E., L. C. M. van Gool, R. Kuiper, and H. B. M. Jonkers. "A Specification Model for Interface Suites." In ≪UML≫ 2001 — The Unified Modeling Language. Modeling Languages, Concepts, and Tools, 457–71. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/3-540-45441-1_33.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Guttag, John V., James J. Horning, S. J. Garland, K. D. Jones, A. Modet, and J. M. Wing. "LCL: A Larch Interface Language for C." In Larch: Languages and Tools for Formal Specification, 56–101. New York, NY: Springer New York, 1993. http://dx.doi.org/10.1007/978-1-4612-2704-5_5.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Souchon, Nathalie, and Jean Vanderdonckt. "A Review of XML-compliant User Interface Description Languages." In Interactive Systems. Design, Specification, and Verification, 377–91. Berlin, Heidelberg: Springer Berlin Heidelberg, 2003. http://dx.doi.org/10.1007/978-3-540-39929-2_26.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
4

Guttag, John V., James J. Horning, S. J. Garland, K. D. Jones, A. Modet, and J. M. Wing. "LM3: A Larch Interface Language for Modula-3." In Larch: Languages and Tools for Formal Specification, 102–20. New York, NY: Springer New York, 1993. http://dx.doi.org/10.1007/978-1-4612-2704-5_6.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Crowle, Simon, and Linda Hole. "ISML: An Interface Specification Meta-language." In Interactive Systems. Design, Specification, and Verification, 362–76. Berlin, Heidelberg: Springer Berlin Heidelberg, 2003. http://dx.doi.org/10.1007/978-3-540-39929-2_25.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Alonso, Fernando, José L. Fuertes, Ángel L. González, and Loïc Martínez. "LERUS: A User Interface Specification Language." In Innovations and Advances in Computer Sciences and Engineering, 209–14. Dordrecht: Springer Netherlands, 2009. http://dx.doi.org/10.1007/978-90-481-3658-2_36.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Nácul, André C., Marcello Lajolo, and Tony Givargis. "Interface-Centric Abstraction Level for Rapid Hardware/Software Integration." In Applications of Specification and Design Languages for SoCs, 83–99. Dordrecht: Springer Netherlands, 2006. http://dx.doi.org/10.1007/978-1-4020-4998-9_5.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Nicolae, A. F., and E. Cerny. "Port-Stitching: An Interface-Oriented Hardware Specification and VHDL Model Generation." In Electronic Chips & Systems Design Languages, 263–72. Boston, MA: Springer US, 2001. http://dx.doi.org/10.1007/978-1-4757-3326-6_22.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Gray, Phil, and Chris Johnson. "Requirements For The Next Generation Of User Interface Specification Languages." In Eurographics, 113–33. Vienna: Springer Vienna, 1995. http://dx.doi.org/10.1007/978-3-7091-9437-9_8.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Zhao, Jianjun, and Martin Rinard. "Pipa: A Behavioral Interface Specification Language for Aspect." In Fundamental Approaches to Software Engineering, 150–65. Berlin, Heidelberg: Springer Berlin Heidelberg, 2003. http://dx.doi.org/10.1007/3-540-36578-8_11.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.

Тези доповідей конференцій з теми "Interface and specification languages":

1

Riener, Heinz, Mathias Soeken, Clemens Werther, Görschwin Fey, and Rolf Drechsler. "MetaSMT: a unified interface to SMT-LIB2." In 2014 Forum on Specification and Design Languages (FDL). IEEE, 2014. http://dx.doi.org/10.1109/fdl.2014.7119353.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Gailliard, Gregory, Hugues Balp, Christophe Jouvray, and Francois Verdier. "Towards a common HW/SW interface-centric and component-oriented specification and design methodology." In Design Languages (FDL). IEEE, 2008. http://dx.doi.org/10.1109/fdl.2008.4641417.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Wang, L. j., and A. S. M. Sajeev. "Abstract interface specification languages for device-independent interface design: classification, analysis and challenges." In 2006 First International Symposium on Pervasive Computing and Applications. IEEE, 2006. http://dx.doi.org/10.1109/spca.2006.297576.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
4

Bucs, Robert Lajos, Luis Gabriel Murillo, Ekaterina Korotcenko, Gaurav Dugge, Rainer Leupers, Gerd Ascheid, Andreas Ropers, Markus Wedler, and Andreas Hoffmann. "Virtual hardware-in-the-loop co-simulation for multi-domain automotive systems via the functional mock-up interface." In 2015 Forum on Specification and Design Languages (FDL). IEEE, 2015. http://dx.doi.org/10.1109/fdl.2015.7306355.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Schöttle, Matthias, Omar Alam, Gunter Mussbacher, and Jörg Kienzle. "Specification of domain-specific languages based on concern interfaces." In the 13th workshop. New York, New York, USA: ACM Press, 2014. http://dx.doi.org/10.1145/2588548.2588551.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Lewchenko, Nicholas V. "Computer-assisted specification of asynchronous interfaces with non-deterministic behavior." In SPLASH '17: Conference on Systems, Programming, Languages, and Applications: Software for Humanity. New York, NY, USA: ACM, 2017. http://dx.doi.org/10.1145/3135932.3135944.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Guedes, Álan L. V., and Simone D. J. Barbosa. "Extending multimedia languages to support multimodal-multiuser interactions." In XXV Simpósio Brasileiro de Sistemas Multimídia e Web. Sociedade Brasileira de Computação - SBC, 2019. http://dx.doi.org/10.5753/webmedia_estendido.2019.8125.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Анотація:
Hardware and software technologies have given rise to a new class of human-computer interfaces that both explores multiple modalities and allows for multiple collaborating users. When compared to the development of traditional single-user WIMP (windows, icons, menus, pointer)-based applications, however, applications supporting the seamless integration of multimodal-multiuser interactions bring new specification and runtime requirements. In this thesis, with the aim of assisting the specification of multimedia applications that integrate multimodal-multiuser interactions, we: (1) propose the MMAM (Multimodal-Multiuser Authoring Model); (2) present three different instantiations of it (in NCL, HTML, and a block-based syntax); and (3) evaluate the proposed model through a user study. MMAM enables programmers to design and ponder different solutions for applications with multimodal-multiuser requirements. Its instantiations served as proofs of concept about the feasibility of our model and enabled us to perform the user study. The user study focused on capturing evidence of both the user understanding and the user acceptance of the proposed model. 94.47% of the participants gave positive answers to the block-based representation TAM questions, whereas 75.17% of them gave positive answers to the instantiations-related questions.
8

Feng, Shaw C., Walter W. Nederbragt, Serge Kaing, and Ram D. Sriram. "Incorporating Process Planning Into Conceptual Design." In ASME 1999 Design Engineering Technical Conferences. American Society of Mechanical Engineers, 1999. http://dx.doi.org/10.1115/detc99/dfm-8922.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Анотація:
Abstract This paper describes recent developments in the Design and Process Planning Integration (DPPI) project at the National Institute of Standards and Technology (NIST). The project addresses the need for improved communication between design and process planning in the early product design stage. Since major manufacturing costs are committed during product specification and design, it is critical to successfully assess manufacturability and cost as early as possible in the design process. Documenting the DPPI foundation, this paper reviews industry needs for an integrated design and manufacturing environment for rapid product development. Additionally, this paper describes the project’s approach and the current status. Conceptual design and process planning prototype systems, that have been implemented, are also described. Finally, it describes the future direction for developing mechanisms to enable the integration of design and process planning, including information models and language interface specifications.
9

De Lima, Rafael, Lincoln S. Rocha, Rossana M. C. Andrade, and Valeria Lelli. "CatchML - A Language for Modeling and Verification of Context-Aware Exception Handling Behaviour." In I Workshop em Modelagem e Simulação de Sistemas Intensivos em Software. Sociedade Brasileira de Computação - SBC, 2019. http://dx.doi.org/10.5753/mssis.2019.7559.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Анотація:
The context-aware exception handling (CAEH) is an error recovery technique employed to improve the ubiquitous software robustness. The design of CAEH is a difficult and error-prone task. The erroneous specification of such conditions represents a critical design fault that can lead the CAEH mechanism to behave erroneously or improperly at runtime. To deal with this problem, we propose a domain-specific language for modeling CAEH, called CatchML, using a high-level interface to make the design of CAEH models simpler and more intuitive. The CatchML language is integrated into a tool to allow designers to perform automatic model verifications by looking at the errors directly in the specification code. We conducted a case study on a sample system called UbiParking with nine volunteers. The results showed that the CatchML language is easy to model the context-aware exception handling and also allowed the participants to quickly locate the injected design faults.
10

Simko, Gabor, Tihamer Levendovszky, Sandeep Neema, Ethan Jackson, Ted Bapty, Joseph Porter, and Janos Sztipanovits. "Foundation for Model Integration: Semantic Backplane." In ASME 2012 International Design Engineering Technical Conferences and Computers and Information in Engineering Conference. American Society of Mechanical Engineers, 2012. http://dx.doi.org/10.1115/detc2012-70534.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Анотація:
One of the primary goals of the Adaptive Vehicle Make (AVM) program of DARPA is the construction of a model-based design flow and tool chain, META, that will provide significant productivity increase in the development of complex cyber-physical systems. In model-based design, modeling languages and their underlying semantics play fundamental role in achieving compositionality. A significant challenge in the META design flow is the heterogeneity of the design space. This challenge is compounded by the need for rapidly evolving the design flow and the suite of modeling languages supporting it. Heterogeneity of models and modeling languages is addressed by the development of a model integration language – CyPhy – supporting constructs needed for modeling the interactions among different modeling domains. CyPhy targets simplicity: only those abstractions are imported from the individual modeling domains to CyPhy that are required for expressing relationships across sub-domains. This “semantic interface” between CyPhy and the modeling domains is formally defined, evolved as needed and verified for essential properties (such as well-formedness and invariance). Due to the need for rapid evolvability, defining semantics for CyPhy is not a “one-shot” activity; updates, revisions and extensions are ongoing and their correctness has significant implications on the overall consistency of the META tool chain. The focus of this paper is the methods and tools used for this purpose: the META Semantic Backplane. The Semantic Backplane is based on a mathematical framework provided by term algebra and logics, incorporates a tool suite for specifying, validating and using formal structural and behavioral semantics of modeling languages, and includes a library of metamodels and specifications of model transformations.

Звіти організацій з теми "Interface and specification languages":

1

Haberman, B., ed. A Dedicated Routing Policy Specification Language Interface Identifier for Operational Testing. RFC Editor, August 2010. http://dx.doi.org/10.17487/rfc5943.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Barker, S. Integrated Information Support System (IISS). Volume 8. User Interface Subsystem. Part 22. Graph Language Development Specification. Fort Belvoir, VA: Defense Technical Information Center, September 1990. http://dx.doi.org/10.21236/ada248930.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Jones, Larry, and Frank Glandorf. Integrated Information Support System (IISS). Volume 8. User Interface Subsystem. Part 14. Forms Language Compiler Development Specification. Fort Belvoir, VA: Defense Technical Information Center, November 1985. http://dx.doi.org/10.21236/ada182582.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
4

Morenc, Carol, Sandy Barker, and Penny Robie. Integrated Information Support System (IISS). Volume 8. User Interface Subsystem. Part 15. Forms Language Compiler Product Specification. Fort Belvoir, VA: Defense Technical Information Center, November 1985. http://dx.doi.org/10.21236/ada182583.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Clements, Paul C., Carolyn E. Gasarch, and Ralph D. Jeffords. Evaluation Criteria for Real-Time Specification Languages. Fort Belvoir, VA: Defense Technical Information Center, February 1992. http://dx.doi.org/10.21236/ada246612.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Barkmeyer, Ed, Steven Ray, and Evan K. Wallace. Control entity interface specification. Gaithersburg, MD: National Institute of Standards and Technology, 1993. http://dx.doi.org/10.6028/nist.ir.5272.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Savage, Sam. User-Friendly Microcomputer Interface With Optimization Languages AF94-007. Fort Belvoir, VA: Defense Technical Information Center, December 1994. http://dx.doi.org/10.21236/ada293184.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Demeure, Isabelle M., and Leon J. Osterweil. What We Learn About Process Specification Languages from Studying Recipes. Fort Belvoir, VA: Defense Technical Information Center, August 1987. http://dx.doi.org/10.21236/ada631494.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
9

McLean, Charles, Y. Tina Lee, Guodong Shao, and Frank Riddick. Shop data model and interface specification. Gaithersburg, MD: National Institute of Standards and Technology, 2005. http://dx.doi.org/10.6028/nist.ir.7198.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Belta, Calin. Specification Languages and Distributed Control Schemes for Teams of Unmanned Vehicles. Fort Belvoir, VA: Defense Technical Information Center, July 2012. http://dx.doi.org/10.21236/ada577491.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.

До бібліографії