Brief Technology Competences Overview

Total Page：16

File Type：pdf, Size：1020Kb

TECHNOLOGY OVERVIEW C++ At a glance: • 25 C++/Qt developers • 95+ successfully delivered projects • 15 ongoing projects • average experience in IT domain – 10 years, in C++ – 7 years Desktop/Server: • Windows family (XP, Vista, 7/8) • Linux • Mac OS • Unix: HP UX, IBM AIX, Sun Solaris Mobile: iOS, Android, WP, Blackberry, Maemo5, Symbian, Meego, Sailfish Cross-platform applications: C++/Qt (across all of the following: Windows, Mac OS X, Linux, Android, iOS, Windows Phone) Embedded: Windows CE, RTOS (FreeRTOS, QNX, VxWorks) CPU architecture: x86, ARM Databases: MS SQL Server, MySQL, PostgreSQL, SQLite, Oracle, Sybase, MongoDB, DB2, FireBird etc. Frameworks / Libraries: Qt, STL, Boost, MFC, ATL, WTL, .NET, litorrent, ffmpeg, OpenSSL, Crypto++, gSoap, wxWidgets, Zinc, Ogre3d, OpenGL, DirectX, OpenCL, OpenMP, MPI, Protobuf, OpenCV, NaCl, etc. Planning: MS Project, JIRA Software Design: Microsoft Visio, Enterprise Architect Development tools: IDE (MS Visual Studio, Qt Creator, Xcode, Eclipse, etc.), static code analysis (cppcheck, cppcat, Visual Studio), refactoring tools (Visual Assist, Resharper), debuggers (MSVC Dbg, WinDBG, gdb, Valgrind,) AStyle, CMake, QMake etc. Testing: Squish, CTest, QTest, cppunit, cfix, gtest, GoogleMock, etc. Version Control: Git, SVN, Mercurial, Perforce, CVS, SourceSafe Continuous Integration / Build automation: CMake/CDash/CTest, GYP, Hudson, CruiseControl, Jenkins, Buildbot TECHNOLOGY OVERVIEW Development approaches: Scrum, Kanban, Iterative, Waterfall, DDD, TDD Featured C++ projects: 1. An all-in-one web browser specifically suitable for music connoisseurs, video lovers and people with an active online presence; an auto-updates subsystem which is user-friendly and highly customizable as well as a solution for torrents managing from the browser 2. A multiplatform desktop application which would help users to concentrate on particular tasks by blocking the Internet access or filtering time-consuming websites 3. A handy desktop application to help users enjoy a better experience of downloading videos from popular file-sharing websites .

Copy Link

Recommended publications

Glassfish™ Community Lighting Talks
GlassFish™ Community Lighting Talks GlassFish Community Speakers Moderator: Alexis Moussine-Pouchkine, Sun Microsystems Session ID: S297769 Agenda GreenFire SailFin Underworld RTL use-case IzPack Hudson Terracotta Embedded GlassFish 2008 CommunityOne Conference | developers.sun.com/events/communityone | 2 GreenFire Adam Bien Who am I? Adam Bien (blog.adam-bien.com) • Expert Group Member (jcp.org) of Java EE 6, EJB 3.1, Time and Date and JPA 2.0 • Java Champion, speaker, consultant and author: Enterprise Java Frameworks, J2EE Patterns, J2EE HotSpots, Struts, SOA Expertenwissen, Enterprise Architekturen, Java EE 5 Architekturen and about 50 published articles • Trainer (since JDK 1.0) • Project owner/committer: http://underworld.dev.java.net http://greenfire.dev.java.net, http://p4j5.dev.java.net, http://o24j.dev.java.net, http://fishfarm.dev.java.net/ 2008 CommunityOne Conference | developers.sun.com/events/communityone | 4 GreenFire.dev.java.net Situation/context dependent prioritization of „bio“ resources (solar over pellets etc.) Highest possible energy and CO2 savings Intelligent control of circulation-pumps, heating and ventilation Monitoring, reports and remote control …and FUN (JavaFX, SunSPOTs, Groovy etc.) 2008 CommunityOne Conference | developers.sun.com/events/communityone | 5 Buffer – the heart of the heating system. Source: paradigma.de 2008 CommunityOne Conference | developers.sun.com/events/communityone | 6 Hacking Java EE 5 is good for the environment! 2008 CommunityOne Conference | developers.sun.com/events/communityone | 7 2008 CommunityOne Conference | developers.sun.com/events/communityone | 8 UnderWorld Adam Bien Context Wonderland.dev.java.net is a “Second Life”-like 3D virtual reality in pure Java. It’s opensource – and easy to build from source (try it!) Wonderland is not a game, rather than an extensible communication/collaboration platform with high demands on scalability and performance.
[Show full text]
Avatud Lähtekoodiga Vahendite Kohandamine Microsoft Visual C++ Tarkvaralahenduste Kvaliteedi Analüüsiks Sonarqube Serveris
TALLINNA TEHNIKAÜLIKOOL Infotehnoloogia teaduskond Tarkvarateaduse instituut Anton Ašot Roolaid 980774IAPB AVATUD LÄHTEKOODIGA VAHENDITE KOHANDAMINE MICROSOFT VISUAL C++ TARKVARALAHENDUSTE KVALITEEDI ANALÜÜSIKS SONARQUBE SERVERIS Bakalaureusetöö Juhendaja: Juhan-Peep Ernits PhD Tallinn 2019 Autorideklaratsioon Kinnitan, et olen koostanud antud lõputöö iseseisvalt ning seda ei ole kellegi teise poolt varem kaitsmisele esitatud. Kõik töö koostamisel kasutatud teiste autorite tööd, olulised seisukohad, kirjandusallikatest ja mujalt pärinevad andmed on töös viidatud. Autor: Anton Ašot Roolaid 21.05.2019 2 Annotatsioon Käesolevas bakalaureusetöös uuritakse, kuidas on võimalik saavutada suure hulga C++ lähtekoodi kvaliteedi paranemist, kui ettevõttes kasutatakse arenduseks Microsoft Visual Studiot ning koodikaetuse ja staatilise analüüsi ülevaate saamiseks SonarQube serverit (Community Edition). Seejuures SonarSource'i poolt pakutava tasulise SonarCFamily for C/C++ analüsaatori (mille eelduseks on SonarQube serveri Developer Edition) asemel kasutatakse tasuta ja vaba alternatiivi: SonarQube C++ Community pluginat. Analüüsivahenditena eelistatakse avatud lähtekoodiga vabu tarkvaravahendeid. Valituks osutuvad koodi kaetuse analüüsi utiliit OpenCppCoverage ja staatilise analüüsi utiliit Cppcheck. Siiski selgub, et nende utiliitide töö korraldamiseks ja väljundi sobitamiseks SonarQube Scanneri vajadustega tuleb kirjutada paar skripti: üks PowerShellis ja teine Windowsi pakkfailina. Regulaarselt ajastatud analüüside käivitamist tagab QuickBuild,
[Show full text]
IBM Rational Team Concert V4.0.3 Keeps Development Teams Focused
IBM United States Software Announcement 213-236, dated June 3, 2013 IBM Rational Team Concert V4.0.3 keeps development teams focused and on track by enabling collaboration, coordination, and automation of project status for all stakeholders Table of contents 1 Overview 5 Publications 2 Key prerequisites 5 Technical information 2 Planned availability date 9 Ordering information 2 Description 22 Terms and conditions 4 Statement of direction 25 Prices 4 Program number 25 Order now At a glance IBM® Rational Team ConcertTM provides the developer role for the Rational® Solution for Collaborative LifeCycle Management. This release focuses on user productivity. Rational Team Concert V4.0.3: • Includes a design that is easy to use. • Provides faster performance. • Enables tighter Software Configuration Management (SCM) integration when using Jenkins-Hudson open source tools. For ordering, contact your IBM representative or an IBM Business Partner. For more information contact the Americas Call Centers at 800-IBM-CALL (426-2255). Reference: AE001 Overview Rational Quality Manager assists organizations of all sizes and levels of complexity to optimize organizational quality by introducing quality early in the application lifecycle and by coordinating quality processes and teams throughout the lifecycle. Rational Quality Manager V4.0.3 offers these main enhancements: • Integrating service virtualization with test management. By linking virtual components deployed in Rational Test Virtualization Server with test execution records in Rational Quality Manager, testers can plan and control virtual components availability for testing and accelerate testing cycles. • Increasing team productivity and agility. Enhanced keyword support for multi- channel testing helps QA teams reuse test scenarios across multiple end points such as web and mobile.
[Show full text]
Enabling Devops on Premise Or Cloud with Jenkins
Enabling DevOps on Premise or Cloud with Jenkins Sam Rostam [email protected] Cloud & Enterprise Integration Consultant/Trainer Certified SOA & Cloud Architect Certified Big Data Professional MSc @SFU & PhD Studies – Partial @UBC Topics The Context - Digital Transformation An Agile IT Framework What DevOps bring to Teams? - Disrupting Software Development - Improved Quality, shorten cycles - highly responsive for the business needs What is CI /CD ? Simple Scenario with Jenkins Advanced Jenkins : Plug-ins , APIs & Pipelines Toolchain concept Q/A Digital Transformation – Modernization As stated by a As established enterprises in all industries begin to evolve themselves into the successful Digital Organizations of the future they need to begin with the realization that the road to becoming a Digital Business goes through their IT functions. However, many of these incumbents are saddled with IT that has organizational structures, management models, operational processes, workforces and systems that were built to solve “turn of the century” problems of the past. Many analysts and industry experts have recognized the need for a new model to manage IT in their Businesses and have proposed approaches to understand and manage a hybrid IT environment that includes slower legacy applications and infrastructure in combination with today’s rapidly evolving Digital-first, mobile- first and analytics-enabled applications. http://www.ntti3.com/wp-content/uploads/Agile-IT-v1.3.pdf Digital Transformation requires building an ecosystem • Digital transformation is a strategic approach to IT that treats IT infrastructure and data as a potential product for customers. • Digital transformation requires shifting perspectives and by looking at new ways to use data and data sources and looking at new ways to engage with customers.
[Show full text]
Tooling Support for Enterprise Development
TOOLING SUPPORT FOR ENTERPRISE DEVELOPMENT RYAN CUPRAK & REZA RAHMAN JAVA EE DEVELOPMENT • Java EE has had a bad reputation: • Too complicated • Long build times • Complicated/expensive tooling • Copious amounts of repetitive code • Expensive application servers • Overkill for most projects • Times have changed since 2000! • Java EE 5 made great strides leveraging new features introduced in Java 5. Java EE 6 pushes us forward. • Excellent tooling support combined with a simplification of features makes Java EE development fast, easy, and clean (maintainable). • It is Java EE – NOT J2EE!!! OBJECTIVE Challenge: Starting a new project is often painful. In this presentation you’ll learn: • How to setup a new Java EE project. • Disconnect between theory and practice. • Tools that you should consider learning/adding. • Best practices for Java EE development from tools side. When is the last time you evaluated your tools? APPLICATION TYPES Types of Java EE applications: • Prototype – verify technology, try different techniques, learn new features. • Throw-away – application which has a short-life space, temporary use. • Internal/external portal – application with a long life expectancy and which will grow over time. • Minimize dependence on tools. • Product – an application which deployed at a more than one customer site. Possibly multiple code branches. • Minimize dependence on tools. Life expectancy drives tooling decisions. PRELIMINARIES Considerations for a Java EE toolbox: • Build system: Ant, Maven, IDE specific? • Container: GlassFish/JBoss/ WebLogic/etc. • Technologies: EJB/JPA/CDI/JSF • IDE: Eclipse, NetBeans, IntelliJ IDEA • Other tools: Unit testing, integration testing, UI testing, etc. IDES • NetBeans • Easy to use Java EE templates. • Includes a pre-configured GlassFish container.
[Show full text]
The Kate Handbook
The Kate Handbook Anders Lund Seth Rothberg Dominik Haumann T.C. Hollingsworth The Kate Handbook 2 Contents 1 Introduction 10 2 The Fundamentals 11 2.1 Starting Kate . 11 2.1.1 From the Menu . 11 2.1.2 From the Command Line . 11 2.1.2.1 Command Line Options . 12 2.1.3 Drag and Drop . 13 2.2 Working with Kate . 13 2.2.1 Quick Start . 13 2.2.2 Shortcuts . 13 2.3 Working With the KateMDI . 14 2.3.1 Overview . 14 2.3.1.1 The Main Window . 14 2.3.2 The Editor area . 14 2.4 Using Sessions . 15 2.5 Getting Help . 15 2.5.1 With Kate . 15 2.5.2 With Your Text Files . 16 2.5.3 Articles on Kate . 16 3 Working with the Kate Editor 17 4 Working with Plugins 18 4.1 Kate Application Plugins . 18 4.2 External Tools . 19 4.2.1 Conﬁguring External Tools . 19 4.2.2 Variable Expansion . 20 4.2.3 List of Default Tools . 22 4.3 Backtrace Browser Plugin . 25 4.3.1 Using the Backtrace Browser Plugin . 25 4.3.2 Conﬁguration . 26 4.4 Build Plugin . 26 The Kate Handbook 4.4.1 Introduction . 26 4.4.2 Using the Build Plugin . 26 4.4.2.1 Target Settings tab . 27 4.4.2.2 Output tab . 28 4.4.3 Menu Structure . 28 4.4.4 Thanks and Acknowledgments . 28 4.5 Close Except/Like Plugin . 28 4.5.1 Introduction . 28 4.5.2 Using the Close Except/Like Plugin .
[Show full text]
Git and Gerrit in Action and Lessons Learned Along the Path to Distributed Version Control
Git and Gerrit in Action And lessons learned along the path to distributed version control Chris Aniszczyk (Red Hat) Principal Software Engineer [email protected] http://aniszczyk.org About Me I've been using and hacking open source for ~12 years - contribute{d} to Gentoo Linux, Fedora Linux, Eclipse Hack on Eclipse, Git and other things at Red Hat Member of the Eclipse Board of Directors Member in the Eclipse Architecture Council I like to run! (2 mins short of Boston qualifying ;/) Co-author of RCP Book (www.eclipsercp.org) An Introduction to Git and Gerrit | © 2011 by Chris Aniszczyk Agenda History of Version Control (VCS) The Rise of Distributed Version Control (DVCS) Code Review with Git and Gerrit Lessons Learned at Eclipse moving to a DVCS Conclusion Q&A An Introduction to Git and Gerrit | © 2011 by Chris Aniszczyk Version Control Version Control Systems manage change “The only constant is change” (Heraclitus) An Introduction to Git and Gerrit | © 2011 by Chris Aniszczyk Why Version Control? VCS became essential to software development because: They allow teams to collaborate They manage change and allow for inspection They track ownership They track evolution of changes They allow for branching They allow for continuous integration An Introduction to Git and Gerrit | © 2011 by Chris Aniszczyk Version Control: The Ancients 1972 – Source Code Control System (SCCS) Born out of Bell Labs, based on interleaved deltas No open source implementations as far as I know 1982 – Revision Control System (RCS) Released as an alternative to SCCS
[Show full text]
What's New for Oracle Developer Cloud Service E70263-03 July 2016
Oracle® Cloud What's New for Oracle Developer Cloud Service E70263-03 July 2016 What’s New in Oracle Developer Cloud Service As soon as new features become available, cloud tools for managing Oracle Developer Cloud Service instances are upgraded in the data centers where Oracle Cloud services are hosted. You don©t need to request an upgrade to be able to use the new features± they come to you automatically. Here's an overview of new features and enhancements added recently to improve your Oracle Developer Cloud Service experience. Topics · July 2016 · March 2016 July 2016 1 Feature Description Choose Oracle Java Cloud While adding an Oracle Java Cloud Service instance as a Service Clusters before remote target, you can now choose which servers or deploying clusters of Oracle Java Cloud Service you want to deploy your application to. See Adding an Oracle Java Cloud Service Instance as a Deployment Target. You can also deploy your application to an Oracle Java Cloud Service Standard Edition instance that does not support clusters. Choose Runtime environment You can now choose the Runtime environment and the and the Subscription type of Subscription type before deploying an application to Oracle Application Container Oracle Application Container Cloud Service. See Cloud Service before Deploying an Application to Oracle Application Container deploying Cloud Service. 2 Feature Description Raw support in Git Using the Raw view of the Code tab, you can now view the unformatted contents of a file and copy the direct download URL of the file from the browser's address bar. See Viewing and Downloading a File in the Raw View.
[Show full text]
Zookeeper 3.3.0 Release Notes
ZooKeeper 3.3.0 Release Notes by Table of contents 1 Changes Since ZooKeeper 3.2...........................................................................................2 Copyright © 2008 The Apache Software Foundation. All rights reserved. ZooKeeper 3.3.0 Release Notes These release notes include new developer and user facing incompatibilities, features, and major improvements. See 3.0 release notes and migration instructions if you are upgrading from version 2 of ZooKeeper (SourceForge) to version 3 or later. 1. Changes Since ZooKeeper 3.2 Issue Notes Sub-task ZOOKEEPER-397 mainline tests conversion Bug ZOOKEEPER-3 syncLimit has slightly different comments in the class header, and > inline with the variable. ZOOKEEPER-59 Synchronized block in NIOServerCnxn ZOOKEEPER-86 intermittent test failure of org.apache.zookeeper.test.AsyncTest ZOOKEEPER-121 SyncRequestProcessor is not closing log stream during shutdown ZOOKEEPER-287 high cpu utilization caused by nioserver factory thread ZOOKEEPER-413 two flaws need addressing in the c tests that can cause false positive failures ZOOKEEPER-420 build/test should not require install in zkpython ZOOKEEPER-457 Make ZookeeperMain public, support for HBase (and other) embedded clients ZOOKEEPER-460 bad testRetry in cppunit tests (hudson failure) ZOOKEEPER-466 crash on zookeeper_close() when using auth with empty cert ZOOKEEPER-467 Change log level in BookieHandle ZOOKEEPER-468 avoid compile warning in send_auth_info() ZOOKEEPER-469 make sure CPPUNIT_CFLAGS isn't overwritten ZOOKEEPER-470 include unistd.h
[Show full text]
From Build Automation to Continuous Integration
Beginners guide to continuous integration Gilles QUERRET Riverside Software About the speaker • Working with Progress and Java since 10 years • Started Riverside Software 7 years ago • Based in Lyon, France • Focused on technical expertise and continuous integration in those environments • Code analysis for OpenEdge http://geekandpoke.typepad.com define:continuous integration Continuous Integration is a software development practice of performing software integration frequently…several times a day, in fact. Ideally, your software application or system should be built automatically after each commit into a shared version control repository. Upon each successful build, the system integrity should be verified using automated tests that cover if not all, then at least most of the functionality. If some tests fail, the developer responsible is notified instantly and the problem can be identified and solved quickly. Using this approach, you can deliver working and reliable code to the customer much faster, while also mitigating the risk of releasing unstable, buggy software to your users. define:continuous integration 5 steps to continuous integration 1 •Source code repository 2 •Build automation 3 •CI server setup 4 •Automated deployment 5 •Automated tests Use the right tools Step 1 : Source code repository • Keeps track of every change in your codebase • Using homegrown solution can be challenging in a continuous integration environment • Lots of tools on the market : CVS, Subversion, Mercurial, Perforce, BitKeeper, Roundtable… • Side note
[Show full text]
Version Control with Subversion for Subversion 1.1 (Book Compiled from Revision 1337)
Version Control with Subversion For Subversion 1.1 (book compiled from Revision 1337) Ben Collins-Sussman Brian W. Fitzpatrick C. Michael Pilato Version Control with Subversion: For Subversion 1.1: (book com- piled from Revision 1337) by Ben Collins-Sussman, Brian W. Fitzpatrick, and C. Michael Pilato Published (TBA) Copyright © 2002, 2003, 2004, 2005 Ben Collins-SussmanBrian W. FitzpatrickC. Michael Pilato This work is licensed under the Creative Commons Attribution License. To view a copy of this license, visit http://creativecommons.org/licenses/by/2.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. Table of Contents Foreword......................................................................................................................................11 Preface.........................................................................................................................................13 Audience ..............................................................................................................................13 How to Read this Book ........................................................................................................... 13 Conventions Used in This Book ................................................................................................ 14 TypographicConventions ................................................................................................14 Icons ...........................................................................................................................14
[Show full text]
Formal Verification to Ensuring the Memory Safety of C++ Programs
FORMAL VERIFICATION TO ENSURING THE MEMORY SAFETY OF C++ PROGRAMS A DISSERTATION SUBMITTED TO THE POSTGRADUATE PROGRAM IN INFORMATICS OF FEDERAL UNIVERSITY OF AMAZONAS IN FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF MASTER OF SCIENCE Felipe R. Monteiro April 2020 © Copyright by Felipe R. Monteiro 2020 All Rights Reserved ii I certify that I have read this dissertation and that, in my opinion, it is fully adequate in scope and quality as a dissertation for the degree of Master of Science. (Lucas Cordeiro) Principal Adviser I certify that I have read this dissertation and that, in my opinion, it is fully adequate in scope and quality as a dissertation for the degree of Master of Science. (Raimundo Barreto) I certify that I have read this dissertation and that, in my opinion, it is fully adequate in scope and quality as a dissertation for the degree of Master of Science. (Herbert Rocha) Approved for the Institute of Computing Committee on Postgraduate Studies iii Abstract In the last three decades, memory safety issues in low-level programming languages such as C or C++ have been one of the significant sources of security vulnerabilities; however, there exist only a few attempts with limited success to cope with the complexity of C++ program verification. This work describes and evaluates a novel verification approach based on bounded model checking (BMC) and satisfiability modulo theories (SMT) to verify C++ programs formally. This verification approach analyzes bounded C++ programs by encoding various sophisticated features that the C++ programming language offers into SMT, such as templates, sequential and associative containers, inheritance, polymorphism, and exception handling.
[Show full text]