DOCSLIB.ORG

Autosar Engineer

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

1 MP 2019 – 190 Autosar Engineer SUMMARY He has experience in automotive projects with C++ and Autosar Expertise SW architecture design (AR 3, AR4), system description design, BSW configuration (Com+CAN Stack, Dem/Dcm, BswM, Rte, Fee/NvM, BAC4),unit/system/functional tests C/C++, debugging requirements management, ISO 26262 Hardware Infineon Tricore TC29X, TC39X, PowerPC V850 Renesas, Atmel 8051 Tools Lauterbach Debugger, BMW FAT, Ediabas, E-sys, DMT/DST, CANoe, CANape, GreenHills compiler, EB Tresos, System desk, Artop, VSA, Autosar Bilder, DOORS (DXL), Rational Synergy, PTC Integrity, IBM Rhapsody, Enterprise Architect, OrCAD, Build systems (Jenkins) HIL, measurement devices for physical layer analysis (up to 2GHz) Communication SOME-IP/SD, Broad-Reach, Flexray, CAN, SPI, I2C, OSI, TCP/IP, ATM, Frame Relay, X.25 protocols Expertise Synthetic Aperture Radar (SAR), interferometric SAR, MTI, detection methods, X-Band/Ka-Band radar, corellation analysis, statistic data processing, model-based development, concept and modelling of complex distributed data processing systems for synthetic aperture radars and system for moving target indication SW development in Matlab/IDL, ANSI C, C++ Tools Matlab, GreenHils compiler/linker, IDL, ENVI, ArcView, remote sensing specific: TMSP, TTP, ITP, DFD PL Front-End, TopoSAR, STAR-4 EDUCATION 1996 – 2001 National University of Radio Electronics, Kharkiv, Ukraine. Faculty of Telecommunication and Instrumentation. Degree graduate engineer LANGUAGES Native speaker Russian, Ukrainian Fluent German, English Key Solutions Polska Sp. z o.o. Centrala SĄD REJONOWY DLA WROCŁAWIA FABRYCZNEJ WE WROCŁAWIU, ul. Wyścigowa 56E VI WYDZIAŁ GOSPODARCZY KRAJOWEGO REJESTRU SĄDOWEGO 53-012 Wrocław NIP 8992665881 | REGON 020927856 | KRS 0000324636 | Kapitał zakładowy 50 000 PLN 2 MP 2019 – 190 PROFESSIONAL EXPERIENCE Since 03.2017: Autoliv/Zenuity GmbH SW Architect Tasks: Objectives create SW Architecture for the advanced driver assistance system functions and deploy it on the dedicated HW. Analysis of former project SW Architecture, adapting it to the new HW, bus topology and OEM requirements. Communication with OEM and suppliers regarding SW Architecture issues Scheduling concepts, partitioning boundary conditions. Timing restriction, other requirements. Creating code guidelines for the developers, SW architecture common patterns. Tools: System Weaver, System Desk, Enterprise Architect, IBM Rational Rhapsody, Vector Davinci (occasionally) Since 01.2016: BMW AG Embedded SW Developer C++ Tasks: Objectives develop new SW component with Some IP communication according to the customer requirements. Requirements analysis and finalization (with the customer). SWC Architecture design. SWC functional implementation. debugging on Component-HIL with SomeIP/SD Simulation. Tools: cmake, Eclipse, Visual Studio, Lauterbach Debugger, CANoe, Component – HIL 09.2015 –10.2016: TRW Automotive GmbH System Engineer – Resident Tasks: Objectives support of the project and dedicated project tasks on site of the customer in coordination with the customer's person in charge. Acquiring and handling of the customer needs independent or in agreement with customer. Analysis and debugging of customer complaints and its relevance to the supplier's tasks. Initial analysis, management and tracking of customer complaints and its Key Solutions Polska Sp. z o.o. Centrala SĄD REJONOWY DLA WROCŁAWIA FABRYCZNEJ WE WROCŁAWIU, ul. Wyścigowa 56E VI WYDZIAŁ GOSPODARCZY KRAJOWEGO REJESTRU SĄDOWEGO 53-012 Wrocław NIP 8992665881 | REGON 020927856 | KRS 0000324636 | Kapitał zakładowy 50 000 PLN 3 MP 2019 – 190 solutions (also in OEM's and supplier's ticket systems). Technical support on site of the Customer. Support or independent conduction of the Setups, vehicle running, HIL-Tests, presentations and documentation. Tools: Lauterbach Debugger, CANoe, CANape, Restbus Simulation, Component - HIL 05.2015 – 10.2015: Schaeffler Engineering GmbH SW architecture/Design according to Autosar 4.0/4.1 Tasks: Objectives Delivery of the pre-configured Autosar OS (Elektrobit OS) according to the OEM requirements : basic software configuration Modelling of the software architecture for SG according to Autosar 4.0.3/4.1.1 considering ASIL B safety requirements Error Analysis, Debugging. Role SW architect, Basis Software configurator. Tools: System desk, EB Tresos Studio, Rational Synergy, IBM Rhapsody, DOORS, ANSI C, Lauterbach Debugger 04.2013 – 07.2015: Bertrandt AG (on behalf of BMW Group AG) SW architecture/Design according to Autosar 4.0/4.1 Tasks: Objectives Delivery of the Interface Package according to the Autosar 4.0/4.1 for diverse ECUs. Role SW architect, Team Leader. Person in charge of the Interface Specification Package Delivery. Supplier Feedbach Managing/Controlling, technical assessment of the issues relevant for SW-Architecture. Tools: Autosar Builder, EB Tresos Studio, DOORS Dxl 04.2011 – 03.2013: Elektrobit (on behalf of BMW Group AG) SW architecture/Design according to Autosar 3.2/4.0/4.1 Tasks: Objectives SW-Architecture Modelling (Autosar 3.2 / 4.0 / 4.1), Interface modelling for non-Autosar ECUs, Requirements management (also automated), integration component concept, definition and coordination its interface with SW. Role SW Architect. Designer for integration sw component. Developer of DOORS proprietary interface. Key Solutions Polska Sp. z o.o. Centrala SĄD REJONOWY DLA WROCŁAWIA FABRYCZNEJ WE WROCŁAWIU, ul. Wyścigowa 56E VI WYDZIAŁ GOSPODARCZY KRAJOWEGO REJESTRU SĄDOWEGO 53-012 Wrocław NIP 8992665881 | REGON 020927856 | KRS 0000324636 | Kapitał zakładowy 50 000 PLN 4 MP 2019 – 190 Know-How model based development, variants handling, test methods. ECU Virtualization (soft HIL). Developer C/C++ Tasks: Objectives Autosar 3.2/4.0 BMW Autocore extension and its configuration for x86 architecture Tools: Lauterbach Debugger, Tresos Studio 11, System, visual C++, XML, Autosar 3/4, OSEK, WinXP Kernel Scheduler, TCP/IP 08.2006 – 08.2010: German Aerospace Center TerraSAR-X Satellite Based Traffic Assessment Tasks: Objectives concept, development and putting into operation of new art GMTI system for large-scale acquisition and traffic situation assessment based on TerraSAR satellite system. Communication with pilot customers, interface definition and coordination, verification concept, cost estimate. Tools: DD Debugger (GDB, DBX), Purify, Profiler, DFT PL Front-End, Synthetic Aperture Radar (SAR), interferometric SAR, MTI, detection methods (Displaced Phase Center, Antenna, Along Track Interferometry, Histogram Detection Method), X-Band Radar, correlation analysis, statistical data processing, TerraSAR Satellite Multimode SAR Processor (TMSP) 01.2006 – 07.2006: Inter map Technologies (on behalf of German Aerospace Center) Tasks: Objectives development of Satellite Data Description Modul (Level 1B Annotation) for TerraSAR Multimode SAR Processor (TMSP). Role implementation of object oriented, extensible modules for generation and interpretation of the complex Terra-SAR product annotation in XML and in DLR proprietary data formats. Geografic and radiometric correction. Tools: IDL, XmlSpy, DD Debugger (GDB, DBX), Purify, Profiler, XML, Synthetic Aperture Radar (SAR), interferometric SAR, X-Band Radar, statistical data processing 12/2002 – 12/2005 Intermap Technologies Role R&D Engineer Key Solutions Polska Sp. z o.o. Centrala SĄD REJONOWY DLA WROCŁAWIA FABRYCZNEJ WE WROCŁAWIU, ul. Wyścigowa 56E VI WYDZIAŁ GOSPODARCZY KRAJOWEGO REJESTRU SĄDOWEGO 53-012 Wrocław NIP 8992665881 | REGON 020927856 | KRS 0000324636 | Kapitał zakładowy 50 000 PLN 5 MP 2019 – 190 Tasks: Objectives Enhancing of the productive SAR/IfSAR algorithms and bug fixing. Tools: Matlab, IDL, SAR specific: TopoSAR, STAR-4, C++, Synthetic Aperture Radar (SAR), interferometric SAR, digital signal processing, correlation anlysis, statistical data processing 05.2003 – 06.2003: Inter map Technologies Tasks: Objectives generation of the elevation models for Hayman Fires and Malaca Islands. Role Project manager, technical project manager. Operation control for the IfSAR-processor and mosaicking. Sub- and End- product quality control according to the ISO 9001 Standards. Know-How production cycle for orthorectified maps, value added imagery and high precision elevation models, project management, quality management. Tools: Matlab, IDL, SAR specific: TopoSAR, STAR-4 08/2002 – 08/2003 Inter map Technologies and Institute for Radio physic and Electronic of Ukrainian national science academy Concept and implementation of noise based SAR-System - Noise Waveform (NW) Replica Tasks: Objectives development of prototype Noise Waveform based SAR system for civil and military application. Role feasibility study, Noise Waveform processing algorithm development, tests. Tools: Matlab, IDL, SAR specific: TopoSAR, NW-Radar Prototype, C++, Synthetic Aperture Radar (SAR), interferometric SAR, detection methods, Ka-Band Radar, correlation analysis, statistical data processing, Doppler Radar, noise waveform processing 09/2001 – 08/2002 Charkow’s Institute for Radio Astronomy of Ukrainian National Academy of Science Tasks: Concept and implementation of the automatic calibration system. Objectives automate calibration process for the large radio telescope „UTR-2“. Role calibration concept. Tests. Maintenance. Tools: and measuring instruments for HW development Test and assembly, C ++, ANSI C, Assembler, Software in the Loop OrCAD Key Solutions Polska Sp. z o.o.
Recommended publications
  • Chapter 8 Instruction Set

    Chapter 8 Instruction Set

    Chapter 8 Instruction Set 80 80 This chapter lists the PowerPC instruction set in alphabetical order by mnemonic. Note that each entry includes the instruction formats and a quick reference ‘legend’ that provides such information as the level(s) of the PowerPC architecture in which the instruction may be found—user instruction set architecture (UISA), virtual environment architecture U (VEA), and operating environment architecture (OEA); and the privilege level of the V instruction—user- or supervisor-level (an instruction is assumed to be user-level unless the O legend specifies that it is supervisor-level); and the instruction formats. The format diagrams show, horizontally, all valid combinations of instruction fields; for a graphical representation of these instruction formats, see Appendix A, “PowerPC Instruction Set Listings.” The legend also indicates if the instruction is 64-bit, , 64-bit bridge, and/or optional. A description of the instruction fields and pseudocode conventions are also provided. For more information on the PowerPC instruction set, refer to Chapter 4, “Addressing Modes and Instruction Set Summary.” Note that the architecture specification refers to user-level and supervisor-level as problem state and privileged state, respectively. 8.1 Instruction Formats Instructions are four bytes long and word-aligned, so when instruction addresses are U presented to the processor (as in branch instructions) the two low-order bits are ignored. Similarly, whenever the processor develops an instruction address, its two low-order bits are zero. Bits 0–5 always specify the primary opcode. Many instructions also have an extended opcode. The remaining bits of the instruction contain one or more fields for the different instruction formats.
  • Book E: Enhanced Powerpc™ Architecture

    Book E: Enhanced Powerpc™ Architecture

    Book E: Enhanced PowerPC Architecture Version 1.0 May 7, 2002 Third Edition (Dec 2001) The following paragraph does not apply to the United Kingdom or any country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS DOCUMENT “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions; therefore, this statement may not apply to you. IBM does not warrant that the use of the information herein shall be free from third party intellectual property claims. IBM does not warrant that the contents of this document will meet your requirements or that the document is error-free. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the document. IBM may make improvements and or changes in the product(s) and/or program(s) described in this document at any time. This document does not imply a commitment by IBM to supply or make generally available the product(s) described herein. No part of this document may be reproduced or distributed in any form or by any means, or stored in a data base or retrieval system, without the written permission of IBM. Address comments about this document to: IBM Corporation Department B5H / Building 667 3039 Cornwallis Road P.O. Box 12195 Research Triangle Park, NC 27709 Portions of the information in this document may have been published previously in the following related documents: The PowerPC Architecture: A Specification for a New Family of RISC Processors, Second Edition (1994) The IBM PowerPC Embedded Environment: Architectural Specifications for IBM PowerPC Embedded Controllers, Second Edition (1998) IBM may have patents or pending patent applications covering the subject matter in this document.
  • PTC Integrity™ Lifecycle Manager™

    PTC Integrity™ Lifecycle Manager™

    PTC Integrity ™ Lifecycle Manager™ The PTC Integrity product family helps organizations accelerate product innovation by reducing complexity, improving collaboration, and automating best practices for software and systems engi- neering. PTC Integrity Lifecycle Manager, a member of the Integrity family, is a flexible, process-based ALM (Application Lifecycle Management) platform that helps teams deliver higher quality, more innovative software with less risk. In today’s world, the demand for smarter, more With seamless, collaborative management of all activi- connected products is increasingly fulfilled through ties and assets, the PTC Integrity Lifecycle Manager software. Software – whether embedded in a product platform helps software engineering teams achieve or providing supporting functionality – is key to driving greater transparency, better productivity and shorter product differentiation and profitability. PTC Integrity cycle times across the entire development lifecycle. Lifecycle Manager provides a global software devel- opment platform that supports all activities and What Makes Integrity Different? assets associated with the engineering and delivery of applications and embedded software. Business All too often, organizations struggle to gain an end- analysts, architects, engineers, developers, quality to-end view of software assets that span multiple managers, testers, partners/suppliers and other tools, with meta-data stored in multiple, disjointed stakeholders all use PTC Integrity Lifecycle Manager repositories. The result is a lack of visibility and as the means for collaboration and control over the traceability across the lifecycle, higher defects and end-to-end development lifecycle. longer development cycles. Our solution provides a unified, global software development platform that supports all activities and assets associated with the engineering and delivery of applications and products.
  • Command Line Interface

    Command Line Interface

    Command Line Interface Squore 21.0.2 Last updated 2021-08-19 Table of Contents Preface. 1 Foreword. 1 Licence. 1 Warranty . 1 Responsabilities . 2 Contacting Vector Informatik GmbH Product Support. 2 Getting the Latest Version of this Manual . 2 1. Introduction . 3 2. Installing Squore Agent . 4 Prerequisites . 4 Download . 4 Upgrade . 4 Uninstall . 5 3. Using Squore Agent . 6 Command Line Structure . 6 Command Line Reference . 6 Squore Agent Options. 6 Project Build Parameters . 7 Exit Codes. 13 4. Managing Credentials . 14 Saving Credentials . 14 Encrypting Credentials . 15 Migrating Old Credentials Format . 16 5. Advanced Configuration . 17 Defining Server Dependencies . 17 Adding config.xml File . 17 Using Java System Properties. 18 Setting up HTTPS . 18 Appendix A: Repository Connectors . 19 ClearCase . 19 CVS . 19 Folder Path . 20 Folder (use GNATHub). 21 Git. 21 Perforce . 23 PTC Integrity . 25 SVN . 26 Synergy. 28 TFS . 30 Zip Upload . 32 Using Multiple Nodes . 32 Appendix B: Data Providers . 34 AntiC . 34 Automotive Coverage Import . 34 Automotive Tag Import. 35 Axivion. 35 BullseyeCoverage Code Coverage Analyzer. 36 CANoe. 36 Cantata . 38 CheckStyle. ..
  • Implementing Powerpc Linux on System I Platform

    Implementing Powerpc Linux on System I Platform

    Front cover Implementing POWER Linux on IBM System i Platform Planning and configuring Linux servers on IBM System i platform Linux distribution on IBM System i Platform installation guide Tips to run Linux servers on IBM System i platform Yessong Johng Erwin Earley Rico Franke Vlatko Kosturjak ibm.com/redbooks International Technical Support Organization Implementing POWER Linux on IBM System i Platform February 2007 SG24-6388-01 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. Second Edition (February 2007) This edition applies to i5/OS V5R4, SLES10 and RHEL4. © Copyright International Business Machines Corporation 2005, 2007. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii Preface . ix The team that wrote this redbook. ix Become a published author . xi Comments welcome. xi Chapter 1. Introduction to Linux on System i platform . 1 1.1 Concepts and terminology . 2 1.1.1 System i platform . 2 1.1.2 Hardware management console . 4 1.1.3 Virtual Partition Manager (VPM) . 10 1.2 Brief introduction to Linux and Linux on System i platform . 12 1.2.1 Linux on System i platform . 12 1.3 Differences between existing Power5-based System i and previous System i models 13 1.3.1 Linux enhancements on Power5 / Power5+ . 14 1.4 Where to go for more information . 15 Chapter 2. Configuration planning . 17 2.1 Concepts and terminology . 18 2.1.1 Processor concepts .
  • A Developer's Guide to the POWER Architecture

    A Developer's Guide to the POWER Architecture

    http://www.ibm.com/developerworks/linux/library/l-powarch/ 7/26/2011 10:53 AM English Sign in (or register) Technical topics Evaluation software Community Events A developer's guide to the POWER architecture POWER programming by the book Brett Olsson , Processor architect, IBM Anthony Marsala , Software engineer, IBM Summary: POWER® processors are found in everything from supercomputers to game consoles and from servers to cell phones -- and they all share a common architecture. This introduction to the PowerPC application-level programming model will give you an overview of the instruction set, important registers, and other details necessary for developing reliable, high performing POWER applications and maintaining code compatibility among processors. Date: 30 Mar 2004 Level: Intermediate Also available in: Japanese Activity: 22383 views Comments: The POWER architecture and the application-level programming model are common across all branches of the POWER architecture family tree. For detailed information, see the product user's manuals available in the IBM® POWER Web site technical library (see Resources for a link). The POWER architecture is a Reduced Instruction Set Computer (RISC) architecture, with over two hundred defined instructions. POWER is RISC in that most instructions execute in a single cycle and typically perform a single operation (such as loading storage to a register, or storing a register to memory). The POWER architecture is broken up into three levels, or "books." By segmenting the architecture in this way, code compatibility can be maintained across implementations while leaving room for implementations to choose levels of complexity for price/performances trade-offs. The levels are: Book I.
  • IBM Powerpc 970 (A.K.A. G5)

    IBM Powerpc 970 (A.K.A. G5)

    IBM PowerPC 970 (a.k.a. G5) Ref 1 David Benham and Yu-Chung Chen UIC – Department of Computer Science CS 466 PPC 970FX overview ● 64-bit RISC ● 58 million transistors ● 512 KB of L2 cache and 96KB of L1 cache ● 90um process with a die size of 65 sq. mm ● Native 32 bit compatibility ● Maximum clock speed of 2.7 Ghz ● SIMD instruction set (Altivec) ● 42 watts @ 1.8 Ghz (1.3 volts) ● Peak data bandwidth of 6.4 GB per second A picture is worth a 2^10 words (approx.) Ref 2 A little history ● PowerPC processor line is a product of the AIM alliance formed in 1991. (Apple, IBM, and Motorola) ● PPC 601 (G1) - 1993 ● PPC 603 (G2) - 1995 ● PPC 750 (G3) - 1997 ● PPC 7400 (G4) - 1999 ● PPC 970 (G5) - 2002 ● AIM alliance dissolved in 2005 Processor Ref 3 Ref 3 Core details ● 16(int)-25(vector) stage pipeline ● Large number of 'in flight' instructions (various stages of execution) - theoretical limit of 215 instructions ● 512 KB L2 cache ● 96 KB L1 cache – 64 KB I-Cache – 32 KB D-Cache Core details continued ● 10 execution units – 2 load/store operations – 2 fixed-point register-register operations – 2 floating-point operations – 1 branch operation – 1 condition register operation – 1 vector permute operation – 1 vector ALU operation ● 32 64 bit general purpose registers, 32 64 bit floating point registers, 32 128 vector registers Pipeline Ref 4 Benchmarks ● SPEC2000 ● BLAST – Bioinformatics ● Amber / jac - Structure biology ● CFD lab code SPEC CPU2000 ● IBM eServer BladeCenter JS20 ● PPC 970 2.2Ghz ● SPECint2000 ● Base: 986 Peak: 1040 ● SPECfp2000 ● Base: 1178 Peak: 1241 ● Dell PowerEdge 1750 Xeon 3.06Ghz ● SPECint2000 ● Base: 1031 Peak: 1067 Apple’s SPEC Results*2 ● SPECfp2000 ● Base: 1030 Peak: 1044 BLAST Ref.
  • Opinnäytetyö Ohjeet

    Opinnäytetyö Ohjeet

    Lappeenrannan–Lahden teknillinen yliopisto LUT School of Engineering Science Tietotekniikan koulutusohjelma Kandidaatintyö Mikko Mustonen PARHAITEN OPETUSKÄYTTÖÖN SOVELTUVAN VERSIONHALLINTAJÄRJESTELMÄN LÖYTÄMINEN Työn tarkastaja: Tutkijaopettaja Uolevi Nikula Työn ohjaaja: Tutkijaopettaja Uolevi Nikula TIIVISTELMÄ LUT-yliopisto School of Engineering Science Tietotekniikan koulutusohjelma Mikko Mustonen Parhaiten opetuskäyttöön soveltuvan versionhallintajärjestelmän löytäminen Kandidaatintyö 2019 31 sivua, 8 kuvaa, 2 taulukkoa Työn tarkastajat: Tutkijaopettaja Uolevi Nikula Hakusanat: versionhallinta, versionhallintajärjestelmä, Git, GitLab, SVN, Subversion, oppimateriaali Keywords: version control, version control system, Git, GitLab, SVN, Subversion, learning material LUT-yliopistossa on tietotekniikan opetuksessa käytetty Apache Subversionia versionhallintaan. Subversionin käyttö kuitenkin johtaa ylimääräisiin ylläpitotoimiin LUTin tietohallinnolle. Lisäksi Subversionin julkaisun jälkeen on tullut uusia versionhallintajärjestelmiä ja tässä työssä tutkitaankin, olisiko Subversion syytä vaihtaa johonkin toiseen versionhallintajärjestelmään opetuskäytössä. Työn tavoitteena on löytää opetuskäyttöön parhaiten soveltuva versionhallintajärjestelmä ja tuottaa sille opetusmateriaalia. Työssä havaittiin, että Git on suosituin versionhallintajärjestelmä ja se on myös suhteellisen helppo käyttää. Lisäksi GitLab on tutkimuksen mukaan Suomen yliopistoissa käytetyin ja ominaisuuksiltaan ja hinnaltaan sopivin Gitin web-käyttöliittymä. Näille tehtiin
  • Solaris Powerpc Edition: Installing Solaris Software—May 1996 What Is a Profile

    Solaris Powerpc Edition: Installing Solaris Software—May 1996 What Is a Profile

    SolarisPowerPC Edition: Installing Solaris Software 2550 Garcia Avenue Mountain View, CA 94043 U.S.A. A Sun Microsystems, Inc. Business Copyright 1996 Sun Microsystems, Inc., 2550 Garcia Avenue, Mountain View, California 94043-1100 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Portions of this product may be derived from the UNIX® system, licensed from Novell, Inc., and from the Berkeley 4.3 BSD system, licensed from the University of California. UNIX is a registered trademark in the United States and other countries and is exclusively licensed by X/Open Company Ltd. Third-party software, including font technology in this product, is protected by copyright and licensed from Sun’s suppliers. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR 52.227-19. Sun, Sun Microsystems, the Sun logo, Solaris, Solstice, SunOS, OpenWindows, ONC, NFS, DeskSet are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the United States and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.
  • RISC-V Geneology

    RISC-V Geneology

    RISC-V Geneology Tony Chen David A. Patterson Electrical Engineering and Computer Sciences University of California at Berkeley Technical Report No. UCB/EECS-2016-6 http://www.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-6.html January 24, 2016 Copyright © 2016, by the author(s). All rights reserved. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission. Introduction RISC-V is an open instruction set designed along RISC principles developed originally at UC Berkeley1 and is now set to become an open industry standard under the governance of the RISC-V Foundation (www.riscv.org). Since the instruction set architecture (ISA) is unrestricted, organizations can share implementations as well as open source compilers and operating systems. Designed for use in custom systems on a chip, RISC-V consists of a base set of instructions called RV32I along with optional extensions for multiply and divide (RV32M), atomic operations (RV32A), single-precision floating point (RV32F), and double-precision floating point (RV32D). The base and these four extensions are collectively called RV32G. This report discusses the historical precedents of RV32G. We look at 18 prior instruction set architectures, chosen primarily from earlier UC Berkeley RISC architectures and major proprietary RISC instruction sets. Among the 122 instructions in RV32G: ● 6 instructions do not have precedents among the selected instruction sets, ● 98 instructions of the 116 with precedents appear in at least three different instruction sets.
  • Market Definition/Description Magic Quadrant

    Market Definition/Description Magic Quadrant

    Magic Quadrant for Application Development Life Cycle Management http://www.gartner.com/technology/reprints.do?id=1-1OR69EF&ct=131231&st=sb# 19 November 2013 ID:G00249074 Analyst(s): Thomas E. Murphy, Jim Duggan, Nathan Wilson Market Definition/Description The application development life cycle management (ADLM) tool market is focused on the planning and governance activities of the software development life cycle (SDLC). ADLM products are focused on the "development" portion of an application's life, with the term ADLM evolving from the term application life cycle management (ALM). Key elements of an ADLM solution include: Software requirements definition and management Software change and configuration management Software project planning, with a current focus on agile planning Work item management Quality management, including defect management In addition, other key capabilities include: Reporting Workflow Integration to version management Support for wikis and collaboration Strong facilities for integration to other ADLM tools This Magic Quadrant represents a snapshot of the ADLM market at a particular point in time. Gartner advises readers not to compare the placement of vendors from prior years. The market is changing — vendor acquisitions, partnerships, solution development and alternative delivery are evidence of these changes — and the criteria for selecting and ranking vendors continue to evolve. Our assessments take into account the vendors' current product offerings and overall strategies, as well as their future initiatives and product road maps. We also factor in how well vendors are driving market changes or adapting to changing market requirements. This Magic Quadrant will help CIOs and business and IT leaders who are developing their ADLM strategies to assess whether they have the right products and enterprise platforms to support them.
  • PTC Integrity

    PTC Integrity

    The Digital Enterprise Journey Matthew Hause PTC Engineering Fellow MBSE Specialist BOEING is a trademark of Boeing Management Company Copyright © 2016 Boeing. All rights reserved. Copyright © 2014 Northrop Grumman Corporation. All rights reserved. GPDIS_2016.ppt | 1 Integrated Systems Engineering Vision Hydraulic Fluid: SAE 1340 not- Power compliant Rating: 18 Amps Thermal/Heat Dissipation: 780° Ergonomic/Ped al Feedback: 34 ERGS Hydraulic Pressure: 350 PSI Sensor MTBF: 3000 hrs MinimumMinimum TurnTurn Radius:Radius: 2424 ft.ft. DryDry PavementPavement BrakingBraking DistanceDistance atat 6060 MPHMPH: : 110110 ft.ft. 90 ft INCOSE IW10 MBSE Workshop page 2 Current Integrated Systems Engineering Global Product Data Interoperability Summit | 2016 • Current systems engineering tools leverage computing and information technologies to some degree, and make heavy use of office applications for documenting system designs. The tools have limited integration with other engineering tools BOEING is a trademark of Boeing Management Company Copyright © 2016 Boeing. All rights reserved. Copyright © 2014 Northrop Grumman Corporation. All rights reserved. GPDIS_2016.ppt3 | 3 Global Product Data Interoperability Summit | 2016 A WORLD IN MOTION INCOSE Systems Engineering Vision • 2025 BOEING is a trademark of Boeing Management Company Copyright © 2016 Boeing. All rights reserved. Copyright © 2014 Northrop Grumman Corporation. All rights reserved. GPDIS_2016.ppt | 4 Integrated Systems Engineering Vision 2025 Global Product Data Interoperability Summit |