Bibliografías temáticas / Formal methods for software engineering

Índice

  1. Artículos de revistas
  2. Tesis
  3. Libros
  4. Capítulos de libros
  5. Actas de conferencias
  6. Informes

Literatura académica sobre el tema "Formal methods for software engineering"

Autor: Grafiati
Publicado: 25 de mayo de 2024

Crea una cita precisa en los estilos APA, MLA, Chicago, Harvard y otros

Elija tipo de fuente:

Consulte las listas temáticas de artículos, libros, tesis, actas de conferencias y otras fuentes académicas sobre el tema "Formal methods for software engineering".

Junto a cada fuente en la lista de referencias hay un botón "Agregar a la bibliografía". Pulsa este botón, y generaremos automáticamente la referencia bibliográfica para la obra elegida en el estilo de cita que necesites: APA, MLA, Harvard, Vancouver, Chicago, etc.

También puede descargar el texto completo de la publicación académica en formato pdf y leer en línea su resumen siempre que esté disponible en los metadatos.

Artículos de revistas sobre el tema "Formal methods for software engineering"

1

Hinchey, Mike, Michael Jackson, Patrick Cousot, Byron Cook, Jonathan P. Bowen y Tiziana Margaria. "Software engineering and formal methods". Communications of the ACM 51, n.º 9 (septiembre de 2008): 54–59. http://dx.doi.org/10.1145/1378727.1378742.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
2

Aichernig, Bernhard y Bernhard Beckert. "Software engineering and formal methods". Software & Systems Modeling 7, n.º 3 (11 de junio de 2008): 255–56. http://dx.doi.org/10.1007/s10270-008-0091-2.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
3

Barthe, Gilles, Alberto Pardo y Gerardo Schneider. "SEFM: software engineering and formal methods". Software & Systems Modeling 14, n.º 1 (22 de febrero de 2014): 3–4. http://dx.doi.org/10.1007/s10270-014-0404-6.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
4

Perseil, Isabelle y Laurent Pautet. "Formal methods integration in software engineering". Innovations in Systems and Software Engineering 6, n.º 1-2 (3 de febrero de 2010): 5–11. http://dx.doi.org/10.1007/s11334-009-0115-2.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
5

King, Trevor. "Introduction to Formal Methods for Software Engineering". Measurement and Control 26, n.º 1 (febrero de 1993): 19–21. http://dx.doi.org/10.1177/002029409302600105.

Texto completo
Resumen
This paper describes what is meant by formal methods for software engineering. It is intended for the non-mathematical reader, and a simple formal specification is presented. The process of formal specification, development and proof is described briefly. Finally the benefits and limitations of formal methods are summarized.
Los estilos APA, Harvard, Vancouver, ISO, etc.
6

Schaefer, Ina y Reiner Hahnle. "Formal Methods in Software Product Line Engineering". Computer 44, n.º 2 (febrero de 2011): 82–85. http://dx.doi.org/10.1109/mc.2011.47.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
7

de Man, Josef. "Session D2: Software engineering: Formal methods I". Microprocessing and Microprogramming 24, n.º 1-5 (agosto de 1988): 361. http://dx.doi.org/10.1016/0165-6074(88)90079-8.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
8

Wordsworth, John. "Education in formal methods for software engineering". Information and Software Technology 29, n.º 1 (enero de 1987): 27–32. http://dx.doi.org/10.1016/0950-5849(87)90017-6.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
9

Dodani, Mahesh. "Formal methods for object-oriented software engineering". Annals of Software Engineering 2, n.º 1 (diciembre de 1996): 121–60. http://dx.doi.org/10.1007/bf02063808.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
10

Liu, Shaoying. "Formal engineering methods for software quality assurance". Frontiers of Computer Science 6, n.º 1 (27 de enero de 2012): 1–2. http://dx.doi.org/10.1007/s11704-012-2900-6.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
Más fuentes

Tesis sobre el tema "Formal methods for software engineering"

1

Higgs, Clive Richard. "Formal methods and reuse in software engineering". Thesis, Cardiff University, 1990. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.264614.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
2

Glorio, Emanuele. "Formal methods for service oriented software engineering". Doctoral thesis, Università Politecnica delle Marche, 2013. http://hdl.handle.net/11566/242717.

Texto completo
Resumen
Il Service-Oriented Computing sta diventando sempre più importante e la proliferazione del grid e cloud computing sta incrementando ancora questa tendenza. Di conseguenza, sempre più aziende stanno esponendo su Internet i loro Web Service. Questo fatto ha l’effetto di trasformare il web da un contenitore di dati ad un contenitore di servizi. In questo scenario, un ingegnere del software è chiamato a progettare un’applicazione tenendo in considerazione l’opportunità/ bisogno di riusare servizi esistenti. Ciò richiede due cose: - una metodologia di ingegneria del software che parta dagli obiettivi di business e dall’organizzazione di una data azienda e arrivi ad identificare quali parti poter delegare a servizi esterni; - l’abilità di localizare i servizi più appropriati. Infatti, mentre le tecnologie e gli standard, come ad esempio iWeb Service, sono importanti, è stato ampiamente riconosciuto che non sono sufficenti da sole. Invece è di estrema importanza un approccio sistematico e completo, che prenda in considerazione i requisiti di business e segua le pratiche raccomandate. Per questo motivo, anche se oggigiorno ci sono molte metodologie orientate ai servizi, l’Ingegneria del Software orientata ai Servizi (SOSE) è ancora un campo aperto. In questa tesi presentiamo la definizione di una nuova metodologia SOSE. Innanzitutto usiamo le fasi iniziali di Tropos dato che è una metodologia orientata agli agenti che porta particolare attenzione alle esigenze degli stakeholder e all’analisi dei requisiti. Inoltre Tropos è stato già modificato in passato al fine di supportare la progettazione dei Web Service. Non modifichiamo le prime tre fasi (Early Requirements, Late Requirements e Architectural Design) e ci concentriamo sulle fasi finali (Detailed Design e Implementation). Nella fase di Detailed Design proponiamo un mapping fra concetti i* ed elementi BPMN 2.0 per avere una traduzione automatica del diagramma i* derivato dalle fasi precedenti in un linguaggio di workflow. In più forniamo delle tecniche e dei metodi formali per selezionare codice e servizi esistenti in modo da riutilizzarli all’interno del software che si sta progettando. Infine, nella fase Implementation proponiamo un mapping BPMN - Alan (un linguaggio di programmazione orientato agli agenti e agli oggetti) in modo da produrre automaticamente un’applicazione eseguibile. Presentiamo inoltre un caso di studio dall’ambito e-commerce e lo usiamo per mostrare come applicare passo passo la nostra metodologia.
Service-Oriented Computing is becoming more and more important. The proliferation of grid and cloud computing is increasing this trend. As a result, more companies than ever before are exposing their Web services on the Internet. This fact has the effect of transforming the web from a repository of data to a repository of service. In this scenario, a software engineer is called to design a software taking into account the opportunity/need of reusing existing services. This requires two issues: - a software engineering methodology that starts from business goals and organization of a given company and arrives to identify which parts can be delegated to external services; - the capability of locating the “most” appropriate services. In fact, while technology and standards, such as Web services, are important, it has been widely recognized that they are not sufficient on their own. Instead, a systematic and comprehensive approach is of critical importance, taking into account the business requirements and following recommended practices. For this reason, even if there are many service-oriented methodology nowadays, Service-Oriented Software Engineering (SOSE) is still an open field. In this thesis we present the definition of a new SOSE methodology. As start, we use Tropos early phases because it is an agent-oriented methodology which bears particular attention to stakeholder needs and requirements analysis. Besides, Tropos was already refined in order to support web service design. We leave the first three phases unchanged (Early and Late Requirements, Architectural Design) and we focus on the final phases (Detailed Design and Implementation). In Detailed Design phase we propose a mapping between i* concepts and BPMN 2.0 elements in order to translate automatically the i* diagram derived from the previous phases in a workflow language. Moreover we provide formal methods and techniques to select code and services in order to reuse them inside the to-be application. Finally, in Implementation phase we propose a mapping BPMN - Alan (an agent-object oriented programming language) to produce automatically an executable application. We present a case study from e-commerce and we use it to show how to apply our methodology step by step.
Los estilos APA, Harvard, Vancouver, ISO, etc.
3

Tran, Sang Cong. "Applications of formal methods in engineering". Thesis, University of Warwick, 1991. http://wrap.warwick.ac.uk/60452/.

Texto completo
Resumen
The main idea presented in this thesis is to propose and justify a general framework for the development of safety-related systems based on a selection of criticality and the required level of integrity. We show that formal methods can be practically and consistently introduced into the system design lifecycle without incurring excessive development cost. An insight into the process of generating and validating a formal specification from an engineering point of view is illustrated, in conjunction with formal definitions of specification models, safety criteria and risk assessments. Engineering specifications are classified into two main classes of systems, memoryless and memory bearing systems. Heuristic approaches for specification generation and validation of these systems are presented and discussed with a brief summary of currently available formal systems and their supporting tools. It is further shown that to efficiently address different aspects of real-world problems, the concept of embedding one logic within another mechanised logic, in order to provide mechanical support for proofs and reasoning, is practical. A temporal logic framework, which is embedded in Higher Order Logic, is used to verify and validate the design of a real-time system. Formal definitions and properties of temporal operators are defined in HOL and real-time concepts such as timing marker, interrupt and timeout are presented. A second major case study is presented on the specification a solid model for mechanical parts. This work discusses the modelling theory with set theoretic topology and Boolean operations. The theory is used to specify the mechanical properties of large distribution transformers. Associated mechanical properties such as volumetric operations are also discussed.
Los estilos APA, Harvard, Vancouver, ISO, etc.
4

Spegni, Francesco. "Formal methods for practical reverse engineering and software verification". Doctoral thesis, Università Politecnica delle Marche, 2012. http://hdl.handle.net/11566/242049.

Texto completo
Resumen
Software development processes are committed at producing high quality software system. Traditionally, this goal is reached through systematic testing. This thesis project analyzes the possibility of applying mathematical logic and so-called formal methods into the software development process. In fact software testing has two major limitations with respect to verification by means of software testing: every test can show correctness for one possible behavior, while formal methods verification shows that correctness, if proved, holds for all the executions of the system. Furthermore, testing can be used to stress the system implementation, while formal verification can be done also during earlier stages of software development, when abstract models of the system are first sketched. In this work we present an integrated working environment that aims at guiding the software engineer along some of the most relevant moments of a software system lifetime: its development, its verification, its maintenance up to a complete re-structuring. The core of the proposed environment is the language XAL , a parametric extension of the theory of networks of timed automata. After defining its syntax and semantics, we show a novel cutoff theorem for it, proving that systems that are both parametric and timed can be model checked. We then describe two methodologies: the former helps in restructuring existing applications using XAL , extracting parameterized finite-state models from legacy code. The latter is about conducting a formal verification using XAL and its cutoff theorem, if needed. A few case-studies are described that uses the proposed language and methodologies. These case-studies are real-world software systems analyzed in a joint effort with Computer VAR ITT and BINT, two Italian ITC companies.
Los estilos APA, Harvard, Vancouver, ISO, etc.
5

Corwin, Paul S. "Incremental Validation of Formal Specifications". DigitalCommons@CalPoly, 2009. https://digitalcommons.calpoly.edu/theses/71.

Texto completo
Resumen
This thesis presents a tool for the mechanical validation of formal software specifications. The tool is based on a novel approach to incremental validation. In this approach, small-scale aspects of a specification are validated, as part of the stepwise refinement of a formal model. The incremental validation technique can be considered a form of "lightweight" model checking. This is in contrast to a "heavyweight" approach, wherein an entire large-scale model is validated en masse. The validation tool is part of a formal modeling and specification language (FMSL), used in software engineering instruction. A lightweight, incremental approach to validation is beneficial in this context. Such an approach can be used to elucidate specification concepts in a step-by-step manner. A heavy-weight approach to model checking is more difficult to use in this way. The FMSL model checker has itself been validated by evaluating portions of a medium-scale specification example. The example has been used in software engineering courses for a number of years, but has heretofore been validated only by human inspection. Evidence for the utility of the validation tool is provided by its performance during the example validation. In particular, use of the tool led to the discovery of a specification flaw that had gone undiscovered by manual validation alone.
Los estilos APA, Harvard, Vancouver, ISO, etc.
6

Todorov, Vassil. "Automotive embedded software design using formal methods". Electronic Thesis or Diss., université Paris-Saclay, 2020. http://www.theses.fr/2020UPASG026.

Texto completo
Resumen
La part croissante des fonctions d'assistance à la conduite, leur criticité, ainsi que la perspective d'une certification de ces fonctions, rendent nécessaire leur vérification et leur validation avec un niveau d'exigence que le test seul ne peut assurer.Depuis quelques années déjà d’autres domaines comme l’aéronautique ou le ferroviaire sont soumis à des contextes équivalents. Pour répondre à certaines contraintes ils ont localement mis en place des méthodes formelles. Nous nous intéressons aux motivations et aux critères qui ont conduit à l’utilisation des méthodes formelles dans ces domaines afin de les transposer sur des scénarios automobiles et identifier le périmètre potentiel d'application.Dans cette thèse, nous présentons nos études de cas et proposons des méthodologies pour l'usage de méthodes formelles par des ingénieurs non-experts. Le model checking inductif pour un processus de développement utilisant des modèles, l'interprétation abstraite pour démontrer l'absence d'erreurs d'exécution du code et la preuve déductive pour des cas de fonctions critiques de librairie.Enfin, nous proposons de nouveaux algorithmes pour résoudre les problèmes identifiés lors de nos expérimentations. Il s'agit d'une part d'un générateur d'invariants et d'une méthode utilisant la sémantique des données pour traiter efficacement des propriétés comportant du temps long, et d'autre part d'un algorithme efficace pour mesurer la couverture du modèle par les propriétés en utilisant des techniques de mutation
The growing share of driver assistance functions, their criticality, as well as the prospect of certification of these functions, make their verification and validation necessary with a level of requirement that testing alone cannot ensure. For several years now, other industries such as aeronautics and railways have been subject to equivalent contexts. To respond to certain constraints, they have locally implemented formal methods. We are interested in the motivations and criteria that led to the use of formal methods in these industries in order to transpose them to automotive scenarios and identify the potential scope of application.In this thesis, we present our case studies and propose methodologies for the use of formal methods by non-expert engineers. Inductive model checking for a model-driven development process, abstract interpretation to demonstrate the absence of run-time errors in the code and deductive proof for critical library functions.Finally, we propose new algorithms to solve the problems identified during our experiments. These are, firstly, an invariant generator and a method using the semantics of data to process properties involving long-running timers in an efficient way, and secondly, an efficient algorithm to measure the coverage of the model by the properties using mutation techniques
Los estilos APA, Harvard, Vancouver, ISO, etc.
7

He, Xudong. "Integrating formal specification and verification methods in software development". Diss., Virginia Polytechnic Institute and State University, 1989. http://hdl.handle.net/10919/54535.

Texto completo
Resumen
This dissertation is a part of an intended long-term research project with the objectives to make software development more scientific and rigorous, thereby to achieve better software quality and to facilitate automated software production; and has two major components: the design of the specification transition paradigm for software development and the theoretical study of the system specification phase in the paradigm. First, after an extensive analysis and comparison of various formalisms, a paradigm for integrating various formal specification and verification methods (predicate transition Petri nets, first order temporal logic, the algebraic, the axiomatic, the denotational, and the operational approaches) in software development has been developed. The model more effectively incorporates foremost formalisms than any other models (the Automatic Programming Project [Bal85], the CIP Project [ClP85], the Larch Project [GHW85] and the RAISE Project [MG87]) and has the following distinctive features: (1) specifications are viewed both as a set of products and a set of well-defined steps of a process, (2) specifications (as a set of products) at different development steps are to be written and verified by different formalisms, (3) specification (as a process) spans from the requirement phase to the detailed design phase, (4) specification for both concurrent and sequential software is supported, and (5) specifications for different aspects (concurrent control abstraction, data abstraction, and procedural abstraction) of a piece of software are dealt with separately. Second, an intensive and in-depth investigation of the system specification phase in the paradigm results in: - a design methodology for predicate transition nets, which incorporates the separate definition technique in Ada [Ada83] and state decomposition technique in Statechart [Har88] into the traditional transformation techniques for Petri nets, and therefore will significantly reduce the design complexity and enhance the comprehensibility of large predicate transition net specifications; - the establishment of a fundamental relationship between predicate transition nets and first order temporal logic and the design of an algorithm for systematically translating predicate transition nets into equivalent temporal logic formulae. Therefore the goal to combine the strengths of both formalisms, i.e. to use predicate transition nets as a specification method and to use temporal logic as a verification method, is achieved; and - the discovery of a special temporal logic proof technique based on a Hilbert-style logic system to verify various properties of predicate transition nets and the associated theorems. Thus temporal logic is effectively used as an analysis method for both safety and liveness properties of predicate transition nets.
Ph. D.
Los estilos APA, Harvard, Vancouver, ISO, etc.
8

Wang, Shuo Yilmaz Levent. "Exploring the integration of model-based formal methods into software design education". Auburn, Ala., 2005. http://repo.lib.auburn.edu/2005%20Fall/Thesis/WANG_SHUO_14.pdf.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
9

Piveropoulos, Marios. "Requirements engineering for hard real-time systems". Thesis, University of York, 2000. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.310980.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
10

Lunglhofer, Jon R. (Jon Richard). "Complete safety software testing : a formal method". Thesis, Massachusetts Institute of Technology, 1996. http://hdl.handle.net/1721.1/88311.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
Más fuentes

Libros sobre el tema "Formal methods for software engineering"

1

Calinescu, Radu y Corina S. Păsăreanu, eds. Software Engineering and Formal Methods. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-92124-8.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
2

Roggenbach, Markus, Antonio Cerone, Bernd-Holger Schlingloff, Gerardo Schneider y Siraj Ahmed Shaikh. Formal Methods for Software Engineering. Cham: Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-030-38800-3.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
3

Schlingloff, Bernd-Holger y Ming Chai, eds. Software Engineering and Formal Methods. Cham: Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-031-17108-6.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
4

Riesco, Adrian y Min Zhang, eds. Formal Methods and Software Engineering. Cham: Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-031-17244-1.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
5

Breitman, Karin y Ana Cavalcanti, eds. Formal Methods and Software Engineering. Berlin, Heidelberg: Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-642-10373-5.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
6

Liu, Shaoying, Tom Maibaum y Keijiro Araki, eds. Formal Methods and Software Engineering. Berlin, Heidelberg: Springer Berlin Heidelberg, 2008. http://dx.doi.org/10.1007/978-3-540-88194-0.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
7

Duan, Zhenhua y Luke Ong, eds. Formal Methods and Software Engineering. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-68690-5.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
8

George, Chris y Huaikou Miao, eds. Formal Methods and Software Engineering. Berlin, Heidelberg: Springer Berlin Heidelberg, 2002. http://dx.doi.org/10.1007/3-540-36103-0.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
9

Ogata, Kazuhiro, Mark Lawford y Shaoying Liu, eds. Formal Methods and Software Engineering. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-47846-3.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
10

Cerone, Antonio y Marco Roveri, eds. Software Engineering and Formal Methods. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-319-74781-1.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
Más fuentes

Capítulos de libros sobre el tema "Formal methods for software engineering"

1

Peled, Doron A. "Formal Methods". En Handbook of Software Engineering, 193–222. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-00262-6_5.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
2

Srivastava, Amitabh. "Engineering Quality Software". En Formal Methods and Software Engineering, 11. Berlin, Heidelberg: Springer Berlin Heidelberg, 2004. http://dx.doi.org/10.1007/978-3-540-30482-1_6.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
3

Laplante, Phillip A. y Mohamad H. Kassab. "Formal Methods". En Requirements Engineering for Software and Systems, 167–94. 4a ed. New York: Auerbach Publications, 2022. http://dx.doi.org/10.1201/9781003129509-7.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
4

Robinson, Ken. "Embedding Formal Development in Software Engineering". En Teaching Formal Methods, 203–13. Berlin, Heidelberg: Springer Berlin Heidelberg, 2004. http://dx.doi.org/10.1007/978-3-540-30472-2_13.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
5

Schumann, Johann M. "Formal Methods in Software Engineering". En Automated Theorem Proving in Software Engineering, 11–22. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-662-22646-9_2.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
6

Lutz, Michael J. "Formal methods and the engineering paradigm". En Software Engineering Education, 119–30. Berlin, Heidelberg: Springer Berlin Heidelberg, 1992. http://dx.doi.org/10.1007/3-540-55963-9_44.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
7

Cartiere, Carmelo R. "Formal Methods for Quantum Software Engineering". En Quantum Software Engineering, 85–101. Cham: Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-031-05324-5_5.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
8

Johnson, D. Randolph. "Cost Effective Software Engineering for Security". En FM 2006: Formal Methods, 607–11. Berlin, Heidelberg: Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11813040_43.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
9

Duke, D. J. y M. D. Harrison. "From formal models to formal methods". En Software Engineering and Human-Computer Interaction, 159–73. Berlin, Heidelberg: Springer Berlin Heidelberg, 1995. http://dx.doi.org/10.1007/bfb0035813.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
10

McDermid, John y Andy Galloway. "Three Perspectives in Formal Engineering". En Formal Methods and Software Engineering, 35–54. Berlin, Heidelberg: Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11901433_3.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.

Actas de conferencias sobre el tema "Formal methods for software engineering"

1

Young, William D. "Formal methods versus software engineering". En the symposium. New York, New York, USA: ACM Press, 1991. http://dx.doi.org/10.1145/120807.120824.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
2

Cookson, M. D. "Software engineering using SDL". En IEE Colloquium on `Practical Application of Formal Methods'. IEE, 1995. http://dx.doi.org/10.1049/ic:19950711.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
3

Spichkova, Maria y Anna Zamansky. "Teaching of Formal Methods for Software Engineering". En Special Session on Collaborative Aspects of Formal Methods. SCITEPRESS - Science and and Technology Publications, 2016. http://dx.doi.org/10.5220/0005928503700376.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
4

Bjoerner, D. "A cloverleaf of software engineering". En Third IEEE International Conference on Software Engineering and Formal Methods. IEEE, 2005. http://dx.doi.org/10.1109/sefm.2005.2.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
5

Hall, Jon G., Lucia Rapanotti y Michael Jackson. "Problem Oriented Software Engineering: A design-theoretic framework for software engineering". En Fifth IEEE International Conference on Software Engineering and Formal Methods (SEFM 2007). IEEE, 2007. http://dx.doi.org/10.1109/sefm.2007.29.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
6

Jackson, Michael. "Specialising in Software Engineering". En Fifth IEEE International Conference on Software Engineering and Formal Methods (SEFM 2007). IEEE, 2007. http://dx.doi.org/10.1109/sefm.2007.37.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
7

Joochim, T., C. F. Snook, M. R. Poppleton y A. M. Gravell. "Timing Diagrams Requirements Modeling using Event-B Formal Methods". En Software Engineering. Calgary,AB,Canada: ACTAPRESS, 2010. http://dx.doi.org/10.2316/p.2010.677-028.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
8

Gargantini, Angelo, Elvinia Riccobene y Patrizia Scandurra. "Integrating Formal Methods with Model-Driven Engineering". En 2009 Fourth International Conference on Software Engineering Advances (ICSEA). IEEE, 2009. http://dx.doi.org/10.1109/icsea.2009.22.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
9

Hall, A. "Making formal methods work". En Third IEEE International Conference on Software Engineering and Formal Methods. IEEE, 2005. http://dx.doi.org/10.1109/sefm.2005.27.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
10

Lindsay, Peter A. "Behavior Trees: From Systems Engineering to Software Engineering". En 2010 8th IEEE International Conference on Software Engineering and Formal Methods (SEFM). IEEE, 2010. http://dx.doi.org/10.1109/sefm.2010.11.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.

Informes sobre el tema "Formal methods for software engineering"

1

Moriconi, Mark. Structure Based Formal Methods for Software Engineering. Fort Belvoir, VA: Defense Technical Information Center, julio de 1989. http://dx.doi.org/10.21236/ada211660.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
2

Black, Paul E. Formal methods for statistical software. Gaithersburg, MD: National Institute of Standards and Technology, octubre de 2019. http://dx.doi.org/10.6028/nist.ir.8274.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
3

Modlo, Yevhenii O., Serhiy O. Semerikov, Stanislav L. Bondarevskyi, Stanislav T. Tolmachev, Oksana M. Markova y Pavlo P. Nechypurenko. Methods of using mobile Internet devices in the formation of the general scientific component of bachelor in electromechanics competency in modeling of technical objects. [б. в.], febrero de 2020. http://dx.doi.org/10.31812/123456789/3677.

Texto completo
Resumen
An analysis of the experience of professional training bachelors of electromechanics in Ukraine and abroad made it possible to determine that one of the leading trends in its modernization is the synergistic integration of various engineering branches (mechanical, electrical, electronic engineering and automation) in mechatronics for the purpose of design, manufacture, operation and maintenance electromechanical equipment. Teaching mechatronics provides for the meaningful integration of various disciplines of professional and practical training bachelors of electromechanics based on the concept of modeling and technological integration of various organizational forms and teaching methods based on the concept of mobility. Within this approach, the leading learning tools of bachelors of electromechanics are mobile Internet devices (MID) – a multimedia mobile devices that provide wireless access to information and communication Internet services for collecting, organizing, storing, processing, transmitting, presenting all kinds of messages and data. The authors reveals the main possibilities of using MID in learning to ensure equal access to education, personalized learning, instant feedback and evaluating learning outcomes, mobile learning, productive use of time spent in classrooms, creating mobile learning communities, support situated learning, development of continuous seamless learning, ensuring the gap between formal and informal learning, minimize educational disruption in conflict and disaster areas, assist learners with disabilities, improve the quality of the communication and the management of institution, and maximize the cost-efficiency. Bachelor of electromechanics competency in modeling of technical objects is a personal and vocational ability, which includes a system of knowledge, skills, experience in learning and research activities on modeling mechatronic systems and a positive value attitude towards it; bachelor of electromechanics should be ready and able to use methods and software/hardware modeling tools for processes analyzes, systems synthesis, evaluating their reliability and effectiveness for solving practical problems in professional field. The competency structure of the bachelor of electromechanics in the modeling of technical objects is reflected in three groups of competencies: general scientific, general professional and specialized professional. The implementation of the technique of using MID in learning bachelors of electromechanics in modeling of technical objects is the appropriate methodic of using, the component of which is partial methods for using MID in the formation of the general scientific component of the bachelor of electromechanics competency in modeling of technical objects, are disclosed by example academic disciplines “Higher mathematics”, “Computers and programming”, “Engineering mechanics”, “Electrical machines”. The leading tools of formation of the general scientific component of bachelor in electromechanics competency in modeling of technical objects are augmented reality mobile tools (to visualize the objects’ structure and modeling results), mobile computer mathematical systems (universal tools used at all stages of modeling learning), cloud based spreadsheets (as modeling tools) and text editors (to make the program description of model), mobile computer-aided design systems (to create and view the physical properties of models of technical objects) and mobile communication tools (to organize a joint activity in modeling).
Los estilos APA, Harvard, Vancouver, ISO, etc.
4

Li, Wenchao. Formal Methods for Reverse Engineering Gate-Level Netlists. Fort Belvoir, VA: Defense Technical Information Center, diciembre de 2013. http://dx.doi.org/10.21236/ada623698.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
5

Williams, L. G. Formal methods in the development of safety critical software systems. Office of Scientific and Technical Information (OSTI), noviembre de 1991. http://dx.doi.org/10.2172/10146119.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
6

Luqi. Increasing the Practical Impact of Formal Methods for Computer-Aided Software Development,. Fort Belvoir, VA: Defense Technical Information Center, septiembre de 1995. http://dx.doi.org/10.21236/ada310438.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
7

Shatz, Sol M. Methods and Tools to Support Software Engineering Automation. Fort Belvoir, VA: Defense Technical Information Center, marzo de 2001. http://dx.doi.org/10.21236/ada392761.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
8

Vakaliuk, Tetiana A., Valerii V. Kontsedailo, Dmytro S. Antoniuk, Olha V. Korotun, Iryna S. Mintii y Andrey V. Pikilnyak. Using game simulator Software Inc in the Software Engineering education. [б. в.], febrero de 2020. http://dx.doi.org/10.31812/123456789/3762.

Texto completo
Resumen
The article presents the possibilities of using game simulator Sotware Inc in the training of future software engineer in higher education. Attention is drawn to some specific settings that need to be taken into account when training in the course of training future software engineers. More and more educational institutions are introducing new teaching methods, which result in the use of engineering students, in particular, future software engineers, to deal with real professional situations in the learning process. The use of modern ICT, including game simulators, in the educational process, allows to improve the quality of educational material and to enhance the educational effects from the use of innovative pedagogical programs and methods, as it gives teachers additional opportunities for constructing individual educational trajectories of students. The use of ICT allows for a differentiated approach to students with different levels of readiness to study. A feature of any software engineer is the need to understand the related subject area for which the software is being developed. An important condition for the preparation of a highly qualified specialist is the independent fulfillment by the student of scientific research, the generation, and implementation of his idea into a finished commercial product. In the process of research, students gain knowledge, skills of the future IT specialist and competences of the legal protection of the results of intellectual activity, technological audit, marketing, product realization in the market of innovations. Note that when the real-world practice is impossible for students, game simulators that simulate real software development processes are an alternative.
Los estilos APA, Harvard, Vancouver, ISO, etc.
9

Striuk, Andrii M., Сергій Олексійович Семеріков, Hanna M. Shalatska, Vladyslav P. Holiver, Андрій Миколайович Стрюк, Ганна Миколаївна Шалацька y Владислав Павлович Голівер. Software requirements engineering training: problematic questions. Криворізький державний педагогічний університет, enero de 2022. http://dx.doi.org/10.31812/123456789/6980.

Texto completo
Resumen
The key problems of training Requirement Engineering and the following ways to overcome the contradiction between the crucial role of Requirement Engineering in industrial software development and insufficient motivation to master it in the process of Software Engineering specialists professional training were identified based on a systematic research analysis on the formation of the ability of future software engineers to identify, classify and formulate software requirements: use of activity and constructivist approaches, game teaching methods in the process of modeling requirements; active involvement of stakeholders in identifying, formulating and verifying requirements at the beginning of the project and evaluating its results at the end; application of mobile technologies for training of geographically distributed work with requirements; implementation of interdisciplinary cross-cutting Software Engineering projects; involvement of students in real projects; stimulating the creation of interdisciplinary and age-old student project teams.
Los estilos APA, Harvard, Vancouver, ISO, etc.
10

Striuk, Andrii M. y Serhiy O. Semerikov. The Dawn of Software Engineering Education. [б. в.], febrero de 2020. http://dx.doi.org/10.31812/123456789/3671.

Texto completo
Resumen
Designing a mobile-oriented environment for professional and practical training requires determining the stable (fundamental) and mobile (technological) components of its content and determining the appropriate model for specialist training. In order to determine the ratio of fundamental and technological in the content of software engineers’ training, a retrospective analysis of the first model of training software engineers developed in the early 1970s was carried out and its compliance with the current state of software engineering development as a field of knowledge and a new the standard of higher education in Ukraine, specialty 121 “Software Engineering”. It is determined that the consistency and scalability inherent in the historically first training program are largely consistent with the ideas of evolutionary software design. An analysis of its content also provided an opportunity to identify the links between the training for software engineers and training for computer science, computer engineering, cybersecurity, information systems and technologies. It has been established that the fundamental core of software engineers’ training should ensure that students achieve such leading learning outcomes: to know and put into practice the fundamental concepts, paradigms and basic principles of the functioning of language, instrumental and computational tools for software engineering; know and apply the appropriate mathematical concepts, domain methods, system and object-oriented analysis and mathematical modeling for software development; put into practice the software tools for domain analysis, design, testing, visualization, measurement and documentation of software. It is shown that the formation of the relevant competencies of future software engineers must be carried out in the training of all disciplines of professional and practical training.
Los estilos APA, Harvard, Vancouver, ISO, etc.
También puede estar interesado en las bibliografías ampliadas sobre el tema "Formal methods for software engineering" para tipos de fuentes particulares:
Artículos de revistas Tesis Libros
Ofrecemos descuentos en todos los planes premium para autores cuyas obras están incluidas en selecciones literarias temáticas. ¡Contáctenos para obtener un código promocional único!

Pasar a la bibliografía