1© Nokia Siemens Networks Presentation / Author / Date For internal use T-76.4115 Better Code Faster - Next Generation Java Continuous Integration Environment.

Slides:



Advertisements
Similar presentations
Are Parametric Techniques Relevant for Agile Development Projects?
Advertisements

IBM Software Group ® Traceability From Need To Solution What, Why and How Tammy Lavi Alon Bar-Ner.
Introduction to Maven 2.0 An open source build tool for Enterprise Java projects Mahen Goonewardene.
Continuous Integration (CI) By Jim Rush Version Control Build Test Report.
Extreme Programming Alexander Kanavin Lappeenranta University of Technology.
® IBM Software Group © 2010 IBM Corporation What’s New in Profiling & Code Coverage RAD V8 April 21, 2011 Kathy Chan
Engineering Secure Software. The Power of Source Code  White box testing Testers have intimate knowledge of the specifications, design, Often done by.
Alternate Software Development Methodologies
JIRA – An Introduction -Arpit Jindal
Virtual SharePoint Summit 2010 hosted by Rackspace Overcoming Collaboration Challenges with SharePoint Chris Samson Leslie Sistla Virtual SharePoint Summit.
T Iteration Demo BaseByters [I1] Iteration
Using R as enterprise-wide data analysis platform Zivan Karaman.
Eclipse Process Framework Plugin example: documents & maps generation
Version Enterprise Architect Redefines Modeling in 2006 An Agile and Scalable modeling solution Provides Full Lifecycle.
Standards for Technology in Automotive Retail STAR Workbench 1.0 Michelle Vidanes & Dave Carver STAR XML Data Architects, Certified Scrum Masters.
SharePoint Portal Server 2003 JAMES WEIMHOLT WEIDER HAO JUAN TURCIOS BILL HUERTA BRANDON BROWN JAMES WEIMHOLT INTRODUCTION OVERVIEW IMPLEMENTATION CASE.
T EAM F OUNDATION S ERVER IN D EVELOPMENT Kambiz Saremi.
Standardize on Team Foundation Server across the enterprise with Teamprise Corey Steffen General Manager
CONTINUOUS INTEGRATION, DELIVERY & DEPLOYMENT ONE CLICK DELIVERY.
COMPARISON STUDY BETWEEN AGILEFANT AND XPLANNER PLUS Professor Daniel Amyot Ruijun Fan Badr Alsubaihi Submitted to Professor Daniel Amyot.
Achieving Agility with WSO2 App Factory S. Uthaiyashankar Director, Cloud Solutions WSO2 Inc. Dimuthu Leelarathne Software Architect WSO2 Inc.
FINAL DEMO Apollo Crew, group 3 T SW Development Project.
Chapter 3 – Agile Software Development 1Chapter 3 Agile software development.
Sumedha Rubasinghe October,2009 Introduction to Programming Tools.
VS Anywhere. Visual Studio Industry Partner VS Anywhere NEXT STEPS Contact us at: Websitehttps://vsanywhere.com Blog- Facebook.
Presented by Abirami Poonkundran.  Introduction  Current Work  Current Tools  Solution  Tesseract  Tesseract Usage Scenarios  Information Flow.
1 SEG4912 University of Ottawa by Jason Kealey Software Engineering Capstone Project Tools and Technologies.
 Mathias Dutour / UAB Dev. team  UNICOS regular meeting  29 January 2009.
DEV 303 Visual Studio "Whidbey" Enterprise Tools: Source Control and Work Item Tracking Brian Harry Product Unit Manager Microsoft Visual Studio.
Visit our Focus Rooms Evaluation of Implementation Proposals by Dynamics AX R&D Solution Architecture & Industry Experts Gain further insights on Dynamics.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
Visualizing Peer-to-Peer Networks Final Presentation By Team SPEW.
Operated by Los Alamos National Security, LLC for NNSA U N C L A S S I F I E D Slide 1 LANL-stor and the Challenges of Evolutionary Development Managing.
DEV-8: OpenEdge® Architect – Extensibility & Third Party Integration Sunil Belgaonkar Principal Software Engineer Architect Phillip Magnay.
Status and first objectives 14/06/2012Jean-Christophe Garnier1.
Eclipse Simple Profiler Ben Xu Mar 7,2011. About Eclipse simple profiler is a open source project to analyze your plug-ins/RCPs performance.
What is Eclipse? Official Definition: Eclipse Evolution
T Iteration Demo METAXA PP Iteration 17 November November November 2015.
Distribution and components. 2 What is the problem? Enterprise computing is Large scale & complex: It supports large scale and complex organisations Spanning.
Chapter 7 The Practices: dX. 2 Outline Iterative Development Iterative Development Planning Planning Organizing the Iterations into Management Phases.
Brian Harry Technical Fellow Microsoft. Demo “self organizing teams are 35% more effective.” Supports planning & sprint execution Modern, simple and.
Extreme Programming Based on and
T Sprint Demo Team Tarantino Iteration 1 / Sprint
Chapter 1 Introducing Ant. What is ant? Ant is a build tool  Automate the tasks of compiling code, running test, and packaging the results for redistribution.
GUI For Computer Architecture May01-05 Team Members: Neil HansenCprE Ben JonesCprE Jon MathewsCprE Sergey SannikovCprE Clients/Advisors: Manimaran Govindarasu.
Extreme programming (XP) Variant of agile Takes commonsense practices to extreme levels © 2012 by Václav Rajlich1.
Using Symbolic PathFinder at NASA Corina Pãsãreanu Carnegie Mellon/NASA Ames.
® IBM Software Group © 2009 IBM Corporation Essentials of Modeling with the IBM Rational Software Architect, V7.5 Module 15: Traceability and Static Analysis.
Extreme Programming. Extreme Programming (XP) Formulated in 1999 by Kent Beck, Ward Cunningham and Ron Jeffries Agile software development methodology.
Boost Developer Productivity with a 360- Degree View of Every Software Change by Using FinditEZ, Certified Microsoft Platform Ready for SQL Azure MICROSOFT.
Survey of Tools to Support Safe Adaptation with Validation Alain Esteva-Ramirez School of Computing and Information Sciences Florida International University.
Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.
Software Architecture in Practice Mandatory project in performance engineering.
ITP 109 Week 2 Trina Gregory Introduction to Java.
INFSO-RI JRA2 Test Management Tools Eva Takacs (4D SOFT) ETICS 2 Final Review Brussels - 11 May 2010.
GROUP PresentsPresents. WEB CRAWLER A visualization of links in the World Wide Web Software Engineering C Semester Two Massey University - Palmerston.
Challenges in Agile Unclear project scope, multiple iterations, minimal documentation, early and frequent testing needs and active stakeholder involvement.
1. ENTERPRISE AGILE TRANSFORMATION AT THE US POSTAL SERVICE MAY 24, Agile Business Solutions.
Automation Testing Trainer: Eran Ruso. Training Agenda Automation Testing Introduction Microsoft Automation Testing Tool Box Coded UI Test and Unit Test.
Review for Eclipse Release Review | © 2012 by Review for Eclipse Committers, made available under the EPL v1.0 1 Review for Eclipse (R4E) 0.11 Release.
SG scmGalaxy Author: KaliPrasad / Rajesh Kumar
Anjana & Shankar September,2010 Introduction to Programming Tools.
Planning Engagement Kickoff
InGenius Connector Enterprise Microsoft Dynamics CRM
Office 365 FastTrack Planning Engagement Kickoff
Continuous Integration (CI)
Design and Programming
Harness the competitive advantages of Power BI and obtain business-critical insights with Adastra’s enterprise analytics platform using Microsoft Azure.
Proposed Approach and Considerations
White Box testing & Inspections
Presentation transcript:

1© Nokia Siemens Networks Presentation / Author / Date For internal use T Better Code Faster - Next Generation Java Continuous Integration Environment Nokia Siemens Networks Hannu Kokko

For internal use 2© Nokia Siemens Networks OES Middleware induction plan Introduction OSS MiddlewareOSS Middleware business line in Nokia Siemens Networks is building next generation network management software platform.next generation network management software platform - Largest agile & iterative development project in Finland - several countries, several teams in each country - One of the largest Java projects in Finland, if not the largest Increase code quality and productivity by exploring and integrating simple, state of the art tooling to our working environment and daily practices – provide proof of concepts or ready solutions Challenge With large codebases the information can be overwhelming and hard to get – tools must be automatic and non-intrusive, very easy to use - integrate the information from different tools in an innovative way to provide insights that a single tool can not. - Provide just the needed information continually – information presented in a form that would be quickly usable by the stakeholder - Stakeholders: developers, architects and R&D management.

For internal use 3© Nokia Siemens Networks OES Middleware induction plan Project goals Outcome is to Increase code quality and productivity by exploring and integrating simple, state of the art tooling to our continuous integration environment – provide proof of concepts or ready solutions Investigate which would be the most needed enhancements from stakeholders (developers and management). Some examples of possible needs: what would be the most practical ways to do static analysis continuously – what kind of static analysis and code metrics would be best to do – what tools to use (open source, commercial) – how to integrate the information from possibly several tools to continuous integration environment and provide feedback quickly enough – how to filter information and show it over time how to help developer find the most likely spots to refactor or improve his code or his unit tests – for example: integrate information from coverage analysis, junit test information, complexity analysis to provide guidance for developer – verifying the quality of unit tests how to help architects & R&D Management to find ways to pinpoint refactoring needs globally in codebase – for example: find duplication, areas of complexity, architectural rule violations...

For internal use 4© Nokia Siemens Networks OES Middleware induction plan Tools and technology Eclipse For continuous integration environment an existing environment consisting of – Maven / Subversion / Bamboo / Cobertura would be used and enhanced. – Runtime environment is Linux. – Development can be done also on Windows or Macs as long as end result runs on Windows and Linux environment. For enhancement of the environment both open source and commercial tools compatible and integrated to previous can be considered. – Possible open source and commercial tools to consider: findbugs, pmd, Clover, JTest, Lattix, Macker... Integration of the features to the continuous integration environment could be done for example as Maven plugins and Bamboo plugins. Documentation of the results could be done in a wiki format and as Microsoft Word documents.

For internal use 5© Nokia Siemens Networks OES Middleware induction plan Skills The team should have enough Java and XML development skills and familiarity with java open source tooling to be able to provide proof of concepts or finished code to the target environment or in a form that could be integrated to the target environment. Familiarity with agile & iterative development is a plus. Familiarity with Maven for some members in the team is a plus. Development team is international so communication in english in both written and verbal form is needed.

For internal use 6© Nokia Siemens Networks OES Middleware induction plan Project where you get to (at least) - interview software developers and R&D management about their needs in continuous integration of software - Build product backlog by interviewing subject matter experts – not everything is ready made for you, you have flexibility in requirements - Balance the product backlog against your capability to deliver - learn to integrate software - explore best ways to analyze, use and present information from build systems and version control - develop your skills in understanding code & properties of large systems - learn to use Maven & other tools within context of complex systems - build Maven and Bamboo plugins with Java - study tools to integrate Project which is quantified as above expectations by customer will get team members a personal Nokia N95 after project.