Ada-Europe 2010 That Will Take Place June 2010 in Valencia, Spain
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
GNAT User's Guide for Native Platforms
GNAT User's Guide for Native Platforms GNAT User's Guide for Native Platforms , January 13, 2017 AdaCore Copyright c 2008-2017, Free Software Foundation i Table of Contents 1 About This Guide :::::::::::::::::::::::::::::: 2 1.1 What This Guide Contains ::::::::::::::::::::::::::::::::::::: 2 1.2 What You Should Know before Reading This Guide :::::::::::: 2 1.3 Related Information :::::::::::::::::::::::::::::::::::::::::::: 3 1.4 A Note to Readers of Previous Versions of the Manual :::::::::: 3 1.5 Conventions:::::::::::::::::::::::::::::::::::::::::::::::::::: 4 2 Getting Started with GNAT ::::::::::::::::::: 5 2.1 Running GNAT :::::::::::::::::::::::::::::::::::::::::::::::: 5 2.2 Running a Simple Ada Program :::::::::::::::::::::::::::::::: 5 2.3 Running a Program with Multiple Units :::::::::::::::::::::::: 6 2.4 Using the gnatmake Utility ::::::::::::::::::::::::::::::::::::: 7 3 The GNAT Compilation Model ::::::::::::::: 9 3.1 Source Representation:::::::::::::::::::::::::::::::::::::::::: 9 3.2 Foreign Language Representation:::::::::::::::::::::::::::::: 10 3.2.1 Latin-1::::::::::::::::::::::::::::::::::::::::::::::::::: 10 3.2.2 Other 8-Bit Codes:::::::::::::::::::::::::::::::::::::::: 10 3.2.3 Wide Character Encodings ::::::::::::::::::::::::::::::: 11 3.2.4 Wide Wide Character Encodings ::::::::::::::::::::::::: 12 3.3 File Naming Topics and Utilities :::::::::::::::::::::::::::::: 13 3.3.1 File Naming Rules ::::::::::::::::::::::::::::::::::::::: 13 3.3.2 Using Other File Names :::::::::::::::::::::::::::::::::: 14 3.3.3 Alternative -
Rational Rhapsody Frameworks and Operating Systems Reference
Rational Rhapsody Frameworks and Operating Systems Reference Before using the information in this manual, be sure to read the “Notices” section of the Help or the PDF available from Help > List of Books. This edition applies to IBM® Rational® Rhapsody® 7.5 and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM Corporation 1997, 2009. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ii Contents Frameworks and Operating Systems . 1 Real-Time Frameworks . 1 Rational Rhapsody Statecharts . 2 The Object Execution Framework (OXF). 3 Working with the Object Execution Framework . 3 The OXF Library. 4 Rational Rhapsody Applications and the RTOS. 5 Operating System Abstraction Layer (OSAL). 5 Threads . 7 Stack Size . 7 Synchronization Services . 8 Message Queues . 8 Communication Port. 9 Timer Service . 10 Real-time Operating System (RTOS) . 11 AbstractLayer Package (OSAL) . 11 Classes . 12 OSWrappers Package . 12 Adapting Rational Rhapsody for a New RTOS . 13 Run-Time Sources . 13 Adding the New Adapter . 13 Creating the Batch File and Makefiles. 14 Sample <env>build.mak File . 15 Creating New Makefiles . 16 OXF Versions . 16 Animation Libraries. 16 Implementing the Adapter Classes . 18 Modifying rawtypes.h . 19 Other Operating System-Related Modifications . 19 Building the Framework Libraries . 20 Rational Rhapsody i Table of Contents Building the C or C++ Framework for Windows Systems . 20 Building the Ada Framework . 21 Building the Java Framework . 22 Building the Framework for Solaris Systems . 22 Creating Properties for a New RTOS . .24 Modifying the site<lang>.prp Files . -
A Model-Driven Development and Verification Approach
A MODEL-DRIVEN DEVELOPMENT AND VERIFICATION APPROACH FOR MEDICAL DEVICES by Jakub Jedryszek B.S., Wroclaw University of Technology, Poland, 2012 B.A., Wroclaw University of Economics, Poland, 2012 A THESIS submitted in partial fulfillment of the requirements for the degree MASTER OF SCIENCE Department of Computing and Information Sciences College of Engineering KANSAS STATE UNIVERSITY Manhattan, Kansas 2014 Approved by: Major Professor John Hatcliff Abstract Medical devices are safety-critical systems whose failure may put human life in danger. They are becoming more advanced and thus more complex. This leads to bigger and more complicated code-bases that are hard to maintain and verify. Model-driven development provides high-level and abstract description of the system in the form of models that omit details, which are not relevant during the design phase. This allows for certain types of verification and hazard analysis to be performed on the models. These models can then be translated into code. However, errors that do not exist in the models may be introduced during the implementation phase. Automated translation from verified models to code may prevent to some extent. This thesis proposes approach for model-driven development and verification of medi- cal devices. Models are created in AADL (Architecture Analysis & Design Language), a language for software and hardware architecture modeling. AADL models are translated to SPARK Ada, contract-based programming language, which is suitable for software veri- fication. Generated code base is further extended by developers to implement internals of specific devices. Created programs can be verified using SPARK tools. A PCA (Patient Controlled Analgesia) pump medical device is used to illustrate the primary artifacts and process steps. -
Programas Incluidos En El DVD DVD-Programación 2012-12
D 2 i c 1 - i e 2 DVD-Programación 2012-12 m 1 0 b 2 r Programas incluidos en el DVD e n d ó i (continuación) Eclipse PDT Helios SR2 - Elgg 1.8.9 - Erlang R15B03 - Etherpad Lite 1.2.1 - Euphoria 3.1.1 - e c ez Components 2009.2.1 - eZ Publish Community 2012.09 - Feng Office 2.2.1 - FileZilla Server 0.9.41 - 2 a 0 m Firebird 2.5.2 - Firebug 1.10.6 - FlameRobin 0.9.3.1186200 - Free Pascal 2.6.0 - FreeBasic 0.24.0 - 1 a 2 r FreeDOS 1.1 Full CD - Gazpacho 0.7.2 - Geany 0.21 - gedit 2.30.1 - Git 1.8.0 - GNAT Programming Studio g 5.1.1 - GnuWin32 Indent 2.2.10 - GTK+ 2.14.7 - Guido van Robot 4.4 - gVim 7.3.46 - HM NIS Edit 2.0.3 - IE o r Tab 2.0 2012.03.12 - Inno Setup 5.5.2 - Inno Setup Tool 5.3.0.1 - InstallJammer 1.2.15 - Instant Rails 2.0 - P - IzPack 4.3.5 - Java Runtime Environment 6 update 37 - Java Runtime Environment 7 update 9 - jEdit 5.0.0 - D Jelix Developer Edition 1.4.1 - Joomla! 2.5.8 - Joomla! 3.0.1 - Komodo Edit 7.1.3 - Kompozer 0.8.b3 - V D Kompozer 0.8.b3 Català - Lazarus 1.0.4 - lightTPD 1.4.30.3 - LinkChecker 8.2 - Mambo 4.6.5 - MantisBT 1.2.12 - MediaWiki 1.20.1 - Mercurial 2.4 - Minimum Profit 5.2.3 - Mono 2.10.9 - monotone 1.0 - Moodle 2.3.3 - MS .NET Framework 1.1 - MS .NET Framework 2.0 - MS Windows Installer 4.5 - MySql 5.5.28 - MySQL WorkBench OSS 5.2.44 - NetBeans Java EE IDE 7.2.1 - Notepad++ 5.9 - NSIS 2.46 - NumPy 1.6.2 (py 2.7) - NumPy 1.6.2 (py 3.2) - Open Watcom Fortran 1.9 - OpenLaszlo 4.9.0 - Parrot 4.10.0 - PECL 5.2.6 - pgAdmin3 1.14.1 - PHP 5.3.19 VC9 (instalador) - PHP-Fusion 7.02.05 - phpMyAdmin 3.5.4 -
SEWIP Program Leverages COTS P 36 P 28 an Interview with Deon Viergutz, Vice President of Cyber Solutions at Lockheed Martin Information Systems & Global Solutions
@military_cots John McHale Obsolescence trends 8 Special Report Shipboard displays 44 Mil Tech Trends Predictive analytics 52 Industry Spotlight Aging avionics software 56 MIL-EMBEDDED.COM September 2015 | Volume 11 | Number 6 RESOURCE GUIDE 2015 P 62 Navy SEWIP program leverages COTS P 36 P 28 An interview with Deon Viergutz, Vice President of Cyber Solutions at Lockheed Martin Information Systems & Global Solutions Military electronics market overview P 14 Volume 11 Number 6 www.mil-embedded.com September 2015 COLUMNS BONUS – MARKET OVERVIEW Editor’s Perspective 14 C4ISR funding a bright spot in military 8 Tech mergers & military electronics electronics market obsolescence By John McHale, Editorial Director By John McHale Q&A EXECUTIVE OUTLOOK Field Intelligence 10 Metadata: When target video 28 Defending DoD from cyberattacks, getting to data is not enough the left of the boom By Charlotte Adams 14 An interview with Deon Viergutz, Vice President of Cyber Solutions at Lockheed Martin Information Mil Tech Insider Systems & Global Solutions 12 Broadwell chip boosts GPU performance for COTS SBCs 32 RF and microwave innovation drives military By Aaron Frank radar and electronic warfare applications An interview with Bryan Goldstein, DEPARTMENTS General Manager of the Aerospace and Defense, Analog Devices 22 Defense Tech Wire By Mariana Iriarte SPECIAL REPORT 60 Editor’s Choice Products Shipboard Electronics 112 University Update 36 U.S. Navy’s electronic warfare modernization On DARPA’s cybersecurity radar: 36 effort centers on COTS Algorithmic and side-channel attacks By Sally Cole, Senior Editor By Sally Cole 114 Connecting with Mil Embedded 44 Key to military display technologies: Blog – The fascinating world of System integration By Tom Whinfrey, IEE Inc. -
The Rational Rhapsody Family from IBM Collaborative Systems Engineering and Embedded Software Development 2 the Rational Rhapsody Family from IBM
IBM Software Design and Development The Rational Rhapsody family from IBM Collaborative systems engineering and embedded software development 2 The Rational Rhapsody family from IBM Model-driven development helps build a Unified Modeling Language (UML) standards. Throughout competitive edge the development process, the Rational Rhapsody family assists How do systems engineers and software developers, creating in managing complexity through visualization and helps main- embedded and real-time applications, meet the demands for tain consistency across the development life cycle to facilitate complex, robust deliverables—especially when there is little agility in response to ever changing requirements. time to produce, let alone test, the systems and software before they go into production? With its robust SysML/UML-based environment and model- driven development (MDD) approach, the Rational Rhapsody In fields such as automotive electronics, avionic controls, family of products helps in addressing the needs of both sys- next-generation wireless infrastructures, consumer electronics, tems engineers and software developers. The IBM Rational medical devices and industrial automation, systems engineers Rhapsody family of products has been recognized by engineers and software designers are facing intense global competition. and developers as the leading MDD solution in a wide variety of industries including aerospace, defense, automotive, To overcome these challenges, IBM provides the telecommunications, medical devices, consumer electronics, IBM® -
LNCS 4119, Pp
Exceptions in Java and Eiffel: Two Extremes in Exception Design and Application Joseph R. Kiniry School of Computer Science and Informatics University College Dublin Belfield, Dublin 8, Ireland [email protected] Abstract. Exceptions are frequently a controversial language feature with both language designers and programmers. Exceptions are controversial because they complicate language semantics—and thus program design, testing, and verifica- tion—and some programmers find them annoying or difficult to use properly. By examining two programming languages that have very different, even opposing, exception mechanisms, a set of exception principles is introduced that summarize the key semantic and social issues surrounding exceptions. 1 Introduction The designers of future programming languages must decide whether to include excep- tions in their new languages. If they decide exceptions are warranted, they must then consider what exceptions represent: (1) a structure for control flow, (2) a structure for handling abnormal, unpredictable situations, or (3) something in-between. Additionally, the syntax and meaning of exceptions must be considered. The syntax of exception mechanisms is also important. Syntax impacts how program code looks and is comprehended, it influences the design and realization of algorithms, and it affects the manner in which programmers handle unusual cases and unexpected situations, and thus indirectly impacts software reliability. And, while the syntax of exception mechanisms is the aspect most programmers see, tool developers and lan- guage theoreticians must wrestle with exception semantics. In general, a small, elegant semantics is desired by all parties. One way to consider how to design a feature like exceptions in future languages is to analyze their design in today’s languages. -
From Eiffel to the Java Virtual Machine
From Eiffel to the Java Virtual Machine Adding a new language target to the EiffelStudio compiler Søren Engel, [email protected] Supervisor Dr. Joseph R. Kiniry Thesis submitted to The IT University of Copenhagen for the degree of Bachelor of Science in Software Development August 2012 Abstract Previous attemps has been made towards translating and executing programs written in Eiffel on the Java platform, as described in Baumgartner [1]. However, the generated Java code has not been easy to use in terms of interoperability between the two languages, due to the restrictions of the Java language. Due to the evolution of the Java language, the work presented in this thesis examines whether it is possible to simplify the translation model of Eiffel to Java. In doing so, this thesis describes a refined translation model that leverages on some of the new features of the Java language, such as the invokedynamic bytecode instruction. Moreover, in order to verify the correctness of the proposed translation model, a description follows on how the translation model may be integrated into the existing EiffelStudio compiler, in terms extending the back-end to target the Java platform. In regards of simplicity, it was found that by using new language features of Java, the translation model of Eiffel to Java could be simplified to the extend that it solves the known issues found in the solution presented in Baumgartner [1]. In trying to integrate the translation model into the existing EiffelStudio compiler, it was found that no public documentation exists which described the internal structure of the EiffelStudio compiler. -
Volume 28 Number 1 March 2007
ADA Volume 28 USER Number 1 March 2007 JOURNAL Contents Page Editorial Policy for Ada User Journal 2 Editorial 3 News 5 Conference Calendar 38 Forthcoming Events 45 Articles C. Comar, R. Berrendonner “ERB : A Ravenscar Benchmarking Framework” 53 Ada-Europe 2006 Sponsors 64 Ada-Europe Associate Members (National Ada Organizations) Inside Back Cover Ada User Journal Volume 28, Number 1, March 2007 2 Editorial Policy for Ada User Journal Publication Original Papers Commentaries Ada User Journal – The Journal for the Manuscripts should be submitted in We publish commentaries on Ada and international Ada Community – is accordance with the submission software engineering topics. These published by Ada-Europe. It appears guidelines (below). may represent the views either of four times a year, on the last days of individuals or of organisations. Such March, June, September and All original technical contributions are articles can be of any length – December. Copy date is the first of the submitted to refereeing by at least two inclusion is at the discretion of the month of publication. people. Names of referees will be kept Editor. confidential, but their comments will Opinions expressed within the Ada Aims be relayed to the authors at the discretion of the Editor. User Journal do not necessarily Ada User Journal aims to inform represent the views of the Editor, Ada- readers of developments in the Ada The first named author will receive a Europe or its directors. programming language and its use, complimentary copy of the issue of the general Ada-related software Journal in which their paper appears. Announcements and Reports engineering issues and Ada-related We are happy to publicise and report activities in Europe and other parts of By submitting a manuscript, authors grant Ada-Europe an unlimited license on events that may be of interest to our the world. -
Eiffel, Smarteiffel, Conception Par Objets, Programmation Par
Eiffel, SmartEiffel, conception par objets, programmation par objets, programmation par contrats, interface, g´en´ericit´e, liaison dynamique, simulation, et cætera. Dominique Colnet { [email protected] 11 juillet 2007 Avertissement Ce document en cours de r´edaction n'a pas la pr´etention d'^etre un ou- vrage complet et exhaustif sur la conception et la programmation par objets avec le langage Eiffel. Ce n'est pas un manuel de r´ef´erence du langage Eiffel ni la documentation du com- pilateur et des outils de SmartEiffel1. Il s'agit plut^ot d'un ensemble de notes de cours, d'une suite plus ou moins p´edagogique de transparents ainsi qu'une collection h´et´erog`ene d'exercices. Comme c'est souvent le cas pour les polycopi´es d'enseignement, le document actuel est constamment en cours de r´edaction. La premi`ere version de ce document doit dater des ann´ees 19902, date `a laquelle nous avons d´ecid´e d'utiliser Eiffel pour la licence d'in- formatique de l'Universit´e Henri Poincar´e (Nancy 1) ainsi qu’`a l'ESIAL (Ecole´ Sup´erieure d'Informatique et Applications de Lorraine). Toutes les suggestions seront les bienvenues (m^eme les corrections orthographiques). Ce document peut ^etre diffus´e reproduit et/ou modifi´e librement a` la seule condition d'indiquer sa provenance initiale et de laisser le pr´esent avertissement inchang´e. Si vous souhaitez disposer du texte source (LATEX) du document, il suffit de me le demander par mail ([email protected]). Table des mati`eres 1 Les premiers pas 3 1.1 Le premier programme . -
Com.Telelogic.Rhapsody.Core
com.telelogic.rhapsody.core Package Class Use Tree Serialized Deprecated Index Help PREV PACKAGE NEXT PACKAGE FRAMES NO FRAMES All Classes Package com.telelogic.rhapsody.core Interface Summary The IRPAcceptEventAction interface represents Accept Event IRPAcceptEventAction Action elements in a statechart or activity diagram. The IRPAcceptTimeEvent interface represents Accept Time Event IRPAcceptTimeEvent elements in activity diagrams and statecharts. The IRPAction interface represents the action defined for a IRPAction transition in a statechart. The IRPActionBlock interface represents action blocks in IRPActionBlock sequence diagrams. The IRPActivityDiagram interface represents activity diagrams in IRPActivityDiagram Rational Rhapsody models. IRPActor The IRPActor interface represents actors in Rhapsody models. The IRPAnnotation interface represents the different types of IRPAnnotation annotations you can add to your model - notes, comments, constraints, and requirements. The IRPApplication interface represents the Rhapsody application, IRPApplication and its methods reflect many of the commands that you can access from the Rhapsody menu bar. The IRPArgument interface represents an argument of an IRPArgument operation or an event. IRPASCIIFile The IRPAssociationClass interface represents association classes IRPAssociationClass in Rational Rhapsody models. The IRPAssociationRole interface represents the association roles IRPAssociationRole that link objects in communication diagrams. The IRPAttribute interface represents attributes of -
Eiffelstudio: a Guided Tour
EiffelStudio: A Guided Tour Interactive Software Engineering 2 EIFFELSTUDIO: A GUIDED TOUR § Manual identification Title: EiffelStudio: A Guided Tour, ISE Technical Report TR-EI-68/GT. (Replaces TR-EI-38/EB.) Publication history First published 1993 as First Steps with EiffelBench (TR-EI-38/EB) and revised as a chapter of Eiffel: The Environment (TR-EI- 39/IE), also available as An Object-Oriented Environment (Prentice Hall, 1994, ISBN 0-13-245-507-2. Version 3.3.8, 1995. Version 4.1, 1997 This version: July 2001. Corresponds to release 5.0 of the ISE Eiffel environment. Author Bertrand Meyer. Software credits Emmanuel Stapf, Arnaud Pichery, Xavier Rousselot, Raphael Simon; Étienne Amodeo, Jérôme Bou Aziz, Vincent Brendel, Gauthier Brillaud, Paul Colin de Verdière, Jocelyn Fiat, Pascal Freund, Savrak Sar, Patrick Schönbach, Zoran Simic, Jacques Sireude, Tanit Talbi, Emmanuel Texier, Guillaume Wong-So; EiffelVision 2: Leila Ait-Kaci, Sylvain Baron, Sami Kallio, Ian King, Sam O’Connor, Julian Rogers. See also acknowledgments for earlier versions in Eiffel: The Environment (TR-EI-39/IE) Non-ISE: special thanks to Thomas Beale, Éric Bezault, Paul Cohen, Paul-Georges Crismer, Michael Gacsaly, Dave Hollenberg, Mark Howard, Randy John, Eirik Mangseth, Glenn Maughan, Jacques Silberstein. Cover design Rich Ayling. Copyright notice and proprietary information Copyright © Interactive Software Engineering Inc. (ISE), 2001. May not be reproduced in any form (including electronic storage) without the written permission of ISE. “Eiffel Power” and the Eiffel Power logo are trademarks of ISE. All uses of the product documented here are subject to the terms and conditions of the ISE Eiffel user license.