DOCSLIB.ORG

Devops for Hybrid Cloud: an IBM Point of View

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Devops for Hybrid Cloud: an IBM Point of View IBM Cloud July 2017 Thought Leadership White Paper DevOps for hybrid cloud: an IBM point of view How DevOps for hybrid cloud can help organizations succeed with digital reinvention 2 DevOps for hybrid cloud: an IBM point of view Introduction The IBM point of view on DevOps makes the following DevOps started as a culture and set of practices to support assumptions: collaboration and communication across development and oper- ations, and to apply automation to key phases of the software ●● DevOps covers the end-to-end software delivery lifecycle delivery process. It has been popularized by successful new including an expanded set of stakeholders such as business companies developing business models and related applications owners and end users, and practices such as design thinking empowered by the cloud (cloud-native applications). More and user analytics. recently, large, established enterprises have recognized the need ●● DevOps adoption is expanding in large organizations as they to deliver innovation faster to stay relevant and capitalize on enable existing IT applications for cloud (cloud-enabled industry disruption, while also improving operational metrics for applications). New methods enable organizations to success- application quality and cost. DevOps and cloud have emerged as fully implement DevOps as they move to cloud. essential parts of their IT strategy as they improve core compe- ●● Hybrid cloud architecture is becoming the norm for both tency in continuous delivery of software-driven innovation. cloud-enabled and cloud-native applications. Hybrid cloud provides flexibility in deployment, enabling organizations to choose the right platform to run their workloads. ●● DevOps solutions can vary as teams across large organizations Business as usual have different goals, processes, culture and tools. Months/years Production ●● In cases where disparate teams work together on common Line of business DevelopmentQuality assurance Operations Customer experience business objectives, DevOps helps organizations respond Customer feedback to the challenges of multi-speed IT in combination with Back officeFront office methods such as the Scaled Agile Framework environment Weeks/months Customers (SAFe) to facilitate collaboration. Business disruption ●● Application security is essential and needs to be integrated Days/weeks early and throughout the DevOps lifecycle to keep pace Customer with frequent releases and not be a bottleneck. Application experience teams ●● Continuous delivery is the desired future-state achieved Platform team with the application of a DevOps approach. Customer feedback DevOps and cloud help enterprises succeed in digital disruption Figure 1. The ingredients for business disruption: continuous innovation, The business change driven by cloud, analytics, mobile, and fast time-to-market, exceptional user experience, and fast time-to-feedback— social technologies is unprecedented in its speed and scope. pointing to the need for Continuous Delivery. New business models are emerging while others are becoming obsolete; born-on-the-web enterprises such as Uber, Airbnb and Spotify are among the highest-profile examples of how tradi- tional businesses are being disrupted by new market entrants. This disruption is driven primarily by changes in customer behavior, facilitated by new technologies. As customers seek a direct, digital link with the businesses they deal with— increasingly, from their mobile devices—application developers are taking on major responsibility for the customer experience. IBM Cloud 3 No industry today is untouched by this dramatic transformation; software that meets emerging business needs—or even creates more than ever before, innovation and adaptability are critical to those needs in the market. For senior application development the survival and development of both existing businesses and executives, the primary concern is about improving operational startups. metrics around cost, risk, quality, productivity and speed in the development cycle. DevOps practitioners want to work on great In the present business environment, product and service applications, focus on delivering value, eliminating waste, auto- delivery processes must be optimized for innovation and time- mating grunt work, and making release party weekends a thing to-market. Methodologies including Agile, Lean Startup and of the past. Design Thinking are well-suited to supporting the design and build of truly innovative offerings, and cloud is increasingly seen IBM defines DevOps as an “essential enterprise capability for as the best platform for software delivery. the continuous delivery of software-driven innovation that enables organizations to seize market opportunities and reduce Organizations are embracing approaches to software develop- time to customer feedback”. DevOps has three main objectives ment that put the customer front and center. By increasing around business transformation which map to three objectives the frequency of software delivery and reducing the time-to- around IT efficiency, as shown in Table 1: feedback from customers, they can respond faster to shifts in the market and keep customers happy. Naturally, increased release frequency demands tighter align- Transformation and organizational objectives ment and collaboration than are seen traditionally between line of business, development, and IT operations, which drives Business-transformation objectives IT-efficiency objectives the requirement for enhanced collaboration, automation and • To speed continuous innovation • To correct the present information transparency among these groups. To achieve of ideas by enabling collaborative misalignment of people and goals development and testing across the by fostering closer links between this seamless internal cooperation and promote sustained value chain. developers, operations and the business. innovation across the enterprise, IBM recommends the adoption • To enable continuous delivery of of DevOps. these innovations by automating • To accelerate and remove error software delivery processes and from the delivery of changes by eliminating waste—while still helping introducing automation throughout to address regulatory concerns. the development cycle. Defining DevOps • To provide a feedback loop for • To improve insight into the real As an approach that promotes closer collaboration among line of continuous learning from customers value of applications by using by monitoring and optimizing the customer feedback to drive business, development and IT operations, DevOps has an impact software-driven innovation. optimization. across the business. For line of business executives and CIOs, a key concern is the capability of DevOps to enable business transformation through faster development of innovative Table 1. DevOps objectives 4 DevOps for hybrid cloud: an IBM point of view Practicing DevOps Many successful startups naturally apply all of the above Organizations that practice DevOps successfully tend to adopt practices from the outset; particularly in the case of smaller orga- the following processes and technologies: nizations, it is easier for a new company to adopt a whole new approach than for an existing company to change its practices. Design thinking: for a focus on delivering exceptional user Nevertheless, at the enterprise level, traditional IT organizations experience and for increasing user conversion are transforming the way they work to incrementally adopt these processes and technologies. Lean startup: for validating ideas and testing possible solutions before committing significant manpower, helping organizations Digital disruption is also driving associated cultural changes in to stay focused on solving the problems that matter the way software is delivered. The DevOps processes and tech- nologies outlined above require a shift in mindset away from Agile: as the development methodology for fast feedback cycles isolated development teams and rigid silos toward collaborative through early customer involvement best practices. Typically, we see successful DevOps organizations embracing the following: Cloud operations: for fast and flexible management of development and production environments ●● A work environment that welcomes innovation, productivity, satisfaction and continuous improvement. Continuous Security: for eliminating security vulnerabilities ●● Software delivery based on autonomous co-located from applications before they reach production squads—small, cross-functional, self-organizing teams that own end-to-end responsibility. Delivery automation: for removing the silos between ●● A process that delivers transparency with metrics and development and IT operations, and enabling the continuous embraces free and open collaboration to enable visibility, delivery of changes continuous learning, and continuous improvements for all stakeholders. Application Monitoring: for quickly detecting and addressing ●● An environment where developers can fail fast in a software application issues in test and production environments penalty-free environment where individuals are empowered to try something new and different without risk of doing Application and user analytics: for continuous learning used to damage or looking foolish and where they can turn small-scale improve the quality and value of applications. mistakes into productive sources of future creativity. IBM provides process, software and service offerings to enable the implementation of these practices. IBM Cloud 5 IBM DevOps approach
Load more

Recommended publications
  • Analysis and Exploration for New Generation Debuggers Thomas Dupriez, Guillermo Polito, Stéphane Ducasse
    Analysis and exploration for new generation debuggers Thomas Dupriez, Guillermo Polito, Stéphane Ducasse To cite this version: Thomas Dupriez, Guillermo Polito, Stéphane Ducasse. Analysis and exploration for new generation debuggers. International Workshop on Smalltalk Technology IWST’17, Sep 2017, Maribor, Slovenia. pp.5:1–5:6, 10.1145/3139903.3139910. hal-01585338 HAL Id: hal-01585338 https://hal.archives-ouvertes.fr/hal-01585338 Submitted on 11 Sep 2017 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Analysis and exploration for new generation debuggers Thomas Dupriez Guillermo Polito Stephane´ Ducasse ENS Paris-Saclay - RMoD, Inria RMoD - Univ. Lille, CNRS, Centrale RMoD, Inria Lille-Nord Europe Lille-Nord Europe Lille, Inria, UMR 9189 - CRIStAL - [email protected] [email protected] Centre de Recherche en Informatique Signal et Automatique de Lille, F-59000 Lille, France [email protected] Abstract offer a different perspective to this problem: it should be Locating and fixing bugs is a well-known time consuming possible to adapt a debugger to a given domain or task. task. Advanced approaches such as object-centric or back- In this position paper we motivate the need to mature and in-time debuggers have been proposed in the literature, still develop more advanced techniques by showing a complex in many scenarios developers are left alone with primitive debugging scenario obtained from a real use case.
    [Show full text]
  • 21 Scenario-Based Programming, Usability-Oriented Perception
    Scenario-Based Programming, Usability-Oriented Perception GIORA ALEXANDRON, MICHAL ARMONI, MICHAL GORDON, and DAVID HAREL, Weizmann Institute of Science In this article, we discuss the possible connection between the programming language and the paradigm behind it, and programmers’ tendency to adopt an external or internal perspective of the system they develop. Based on a qualitative analysis, we found that when working with the visual, interobject language of live sequence charts (LSC), programmers tend to adopt an external and usability-oriented view of the system, whereas when working with an intraobject language, they tend to adopt an internal and implementation- oriented viewpoint. This is explained by first discussing the possible effect of the programming paradigm on programmers’ perception and then offering a more comprehensive explanation. The latter is based on a cognitive model of programming with LSC, which is an interpretation and a projection of the model suggested by Adelson and Soloway [1985] onto LSC and scenario-based programming, the new paradigm on which LSC is based. Our model suggests that LSC fosters a kind of programming that enables iterative refinement of the artifact with fewer entries into the solution domain. Thus, the programmer can make less context switching between the solution domain and the problem domain, and consequently spend more time in the latter. We believe that these findings are interesting mainly in two ways. First, they characterize an aspect of problem-solving behavior that to the best of our knowledge has not been studied before—the programmer’s perspective. The perspective can potentially affect the outcome of the problem-solving process, such as by leading the programmer to focus on different parts of the problem.
    [Show full text]
  • Scenario-Driven Continuous Mobility Requirements Analysis in Mobile App Maintenance
    Scenario-Driven Continuous Mobility Requirements Analysis in Mobile App Maintenance Xiaozhou Li1, Zheying Zhang2 and Timo Poranen3 1 University of Tampere, Kalevantie 4, 33014, Tampere, Finland {xiaozhou.li; zheying.zhang; timo.t.poranen}@uta.fi Abstract. As mobile devices have become an indispensable part of people’s lives, the growth of mobile app market is inevitably rapid. Accordingly, the mobile app users have increasing demands on the quality of the apps. Their tol- erance towards bugs and poor usability of the apps is growing low. In addition, as the mobile devices and apps have enabled users to use them in various con- texts, the mobility of the apps, referred to as their capability to provide ubiqui- tous services with quality, is also required. In this study, we propose the scenar- io-driven approach of mobility requirements analysis with context and ways of interaction. It supports the continuous requirements analysis in the maintenance of mobile apps where their mobility is constantly maintained despite the chang- es in the features. Keywords: Mobile App, Mobility, Requirements, Scenario, Situational Con- texts, Interaction, Maintenance. 1 Introduction The mobility of mobile apps, as their most significant feature, is defined as the ability to access services ubiquitously, on the move, though wireless networks and various mobile devices [1]. It enables the users to access the services with the independence from time and space [2]. The mobility of mobile apps is closely related to their con- text of use, especially the situational context, which largely influences the post- adoption behaviors of the users, including use continuance, word-of-mouth, and com- plaints [3].
    [Show full text]
  • Accelerating Software Development Through Agile Practices - a Case Study of a Small-Scale, Time-Intensive Web Development Project at a College-Level IT Competition
    Journal of Information Technology Education: Volume 11, 2012 Innovations in Practice Accelerating Software Development through Agile Practices - A Case Study of a Small-scale, Time-intensive Web Development Project at a College-level IT Competition Xuesong (Sonya) Zhang Bradley Dorn California State Polytechnic California State University, University, Pomona, CA, USA Fresno, CA, USA [email protected] [email protected] Executive Summary Agile development has received increasing interest both in industry and academia due to its bene- fits in developing software quickly, meeting customer needs, and keeping pace with the rapidly changing requirements. However, agile practices and scrum in particular have been mainly tested in mid- to large-size projects. In this paper, we present findings from a case study of agile prac- tices in a small-scale, time-intensive web development project at a college-level IT competition. Based on the observation of the development process, the interview of the project team, and the study of relevant documents, we describe how agile practices, such as daily scrums, backlogs, and sprints, were successfully adopted to the project development. We also describe several support- ing activities that the team employed, including cross-leveling of knowledge, socialization, and multiple communication modes. Finally, we discuss the benefits and challenges of implementing agile practices in the case project reported, as well as contribution and limitation of our findings. Keywords: Agile, Scrum, Software development, Project management, Web application. Introduction Created to be a lightweight software development method by 17 software developers at a ski re- sort a decade ago (“Agile Software Development,” 2011), agile development has received in- creasing interest both in industry and academia due to its benefits in developing software more quickly and at lower costs, meeting customer needs, and keeping pace with the rapidly changing requirements.
    [Show full text]
  • Use Cases, User Stories and Bizdevops
    Use Cases, User Stories and BizDevOps Peter Forbrig University of Rostock, Chair in Software Engineering, Albert-Einstein-Str. 22, 18055 Rostock [email protected] Abstract. DevOps is currently discussed a lot in computer science communi- ties. BizDev (business development) is only mentioned once in a computer sci- ence paper in connection with Continuous Software Engineering. Otherwise it is used in the domain of business administration only. Additionally, there seems to be a different interpretation of the term in the two communities. The paper discusses the different interpretations found in the literature. Addi- tionally, the idea of BizDevOps is discussed in conjunction with further ideas of taking new requirements for software features into account. These requirements can be described by models on different level of granularity. Starting points are use cases, use-case slices, user stories, and scenarios. They have to be commu- nicated between stakeholders. It is argued in this paper that storytelling can be a solution for that. It is used in as well in software development as in manage- ment. Keywords: BizDev, DevOps, BizDevOps, Continuous Requirements Engineer- ing, Continuous Software Engineering, Agile Software Development, Storytell- ing. 1 Introduction Developing Businesses if often related with the development of software because nowadays business processes have to be supported by IT. Continuous requirements engineering has to be performed to provide continuously the optimal support. Contin- uous business development seems to be a good description for the combined devel- opment of software and business. This term is not used so very often. Nevertheless, it exists like in [17]. However, more often the abbreviation BizDev (business development) is used.
    [Show full text]
  • Software Development a Practical Approach!
    Software Development A Practical Approach! Hans-Petter Halvorsen https://www.halvorsen.blog https://halvorsen.blog Software Development A Practical Approach! Hans-Petter Halvorsen Software Development A Practical Approach! Hans-Petter Halvorsen Copyright © 2020 ISBN: 978-82-691106-0-9 Publisher Identifier: 978-82-691106 https://halvorsen.blog ii Preface The main goal with this document: • To give you an overview of what software engineering is • To take you beyond programming to engineering software What is Software Development? It is a complex process to develop modern and professional software today. This document tries to give a brief overview of Software Development. This document tries to focus on a practical approach regarding Software Development. So why do we need System Engineering? Here are some key factors: • Understand Customer Requirements o What does the customer needs (because they may not know it!) o Transform Customer requirements into working software • Planning o How do we reach our goals? o Will we finish within deadline? o Resources o What can go wrong? • Implementation o What kind of platforms and architecture should be used? o Split your work into manageable pieces iii • Quality and Performance o Make sure the software fulfills the customers’ needs We will learn how to build good (i.e. high quality) software, which includes: • Requirements Specification • Technical Design • Good User Experience (UX) • Improved Code Quality and Implementation • Testing • System Documentation • User Documentation • etc. You will find additional resources on this web page: http://www.halvorsen.blog/documents/programming/software_engineering/ iv Information about the author: Hans-Petter Halvorsen The author currently works at the University of South-Eastern Norway.
    [Show full text]
  • The Devops Journey: from Waterfall to Continuous Delivery
    WHITE PAPER THE DEVOPS JOURNEY: FROM WATERFALL TO CONTINUOUS DELIVERY Implementing an agile, DevOps-centered workflow involves several distinct steps. In other words, the process required to evolve from traditional, “waterfall”-style development to continuous delivery of software is a journey, not something that organizations can implement all at once. While many organizations today have begun the DevOps journey by adopting some tools and methodologies that promote agility, a lack of fully automated testing often prevents them from completing it. The integration of efficient automated testing into workflows is therefore a crucial step for organizations seeking to achieve full agility and complete the DevOps journey. TABLE OF CONTENTS 3 Executive Summary 6 Automated testing is not a choice -- it’s a necessity 3 Stages of agility 6 Web apps: From waterfall to 3 Waterfall continuous delivery 3 Fast waterfall 7 Why automated testing is uniquely important to DevOps 4 Continuous integration 8 Conclusion 4 Continuous delivery 5 Moving down the trail with automating testing 5 Increasing testing agility 5 Automated testing 5 Cloud-based testing 6 Parallel testing 6 Shift-left testing EXECUTIVE SUMMARY DevOps. Agility. Continuous delivery. These are the buzzwords of the new software development and testing landscape. They describe some of the core values and processes that characterize an efficient, modern workflow. But they are also terms that can be misleading. That’s because they’re easy to conceptualize as qualities or values that an organization either has or does not have. In many common depictions, a company either “does” DevOps or it doesn’t. It’s agile or it’s not.
    [Show full text]
  • A Taxonomy for Scenario Use in Requirements Elicitation and Analysis of Software Systems
    A Taxonomy for Scenario Use in Requirements Elicitation and Analysis of Software Systems Brian D. Chance Bonnie E. Melhart Motorola Cellular Division TCU Fort Worth, TX 76137 Fort Worth, TX 76129 [email protected] [email protected] Abstract above. It is very difficult to see what is missing from a document by simply reading the document. Scenarios This work introduces a taxonomy of scenario use help one read and review with a different viewpoint with the objective to improve completeness of the because they encourage consideration of the details of requirements specification. Indications are given for each requirement instead of a general review. In future work to enable scenario development for some particular they enable discussion and review of dynamic weak categories of the taxonomy. behavior of the system under development. We are investigating scenarios as a means to improve completeness in a requirements specification document. Introduction Scenario Usage In systems development the first step in providing a solution that meets the customer’s needs is to define Scenario usage in development of software systems what problem must be solved. Requirements elicitation varies greatly and even the definition of a scenario is not and analysis is perhaps more iterative than any other consistent. Some use scenario to imply a particular phase of systems and software development. Rarely is customer use case, others refer to any sequence of system this process complete in one pass. Each iteration usually events as a scenario, and still others apply scenarios to includes these main activities: documenting the business goals or software inspections. We take the very requirements a system must provide; refining these general definition that a scenario refers to an ordered requirements; analysis for omissions, contradictions, and collection of inputs or internal states that produce a ambiguities; and review with consideration for a balance specific result.
    [Show full text]
  • Out-Of-Place Debugging: a Debugging Architecture to Reduce Debugging Interference
    Out-Of-Place debugging: a debugging architecture to reduce debugging interference Matteo Marraa, Guillermo Politob, and Elisa Gonzalez Boixa a Vrije Universiteit Brussel, Brussels, Belgium b Univ. Lille, CNRS, Centrale Lille, Inria, UMR 9189 - CRIStAL - Centre de Recherche en Informatique Signal et Automatique de Lille, F-59000 Lille, France Abstract Context Recent studies show that developers spend most of their programming time testing, ver- ifying and debugging software. As applications become more and more complex, developers demand more advanced debugging support to ease the software development process. Inquiry Since the 70’s many debugging solutions have been introduced. Amongst them, online debuggers provide good insight on the conditions that led to a bug, allowing inspection and interaction with the variables of the program. However, most of the online debugging solutions introduce debugging interference to the execution of the program, i.e. pauses, latency, and evaluation of code containing side-effects. Approach This paper investigates a novel debugging technique called out-of-place debugging. The goal is to minimize the debugging interference characteristic of online debugging while allowing online remote ca- pabilities. An out-of-place debugger transfers the program execution and application state from the debugged application to the debugger application, each running in a different process. Knowledge On the one hand, out-of-place debugging allows developers to debug applications remotely, overcoming the need of physical access to the machine where the debugged application is running. On the other hand, debugging happens locally on the remote machine avoiding latency. That makes it suitable to be deployed on a distributed system and handle the debugging of several processes running in parallel.
    [Show full text]
  • SOFTWARE DEVELOPMENT MODELS and THEIR REAL ASPECTS Divya Tanwar Sbs , Vivekananda Institute of Professional Studies, GGSIPU, Delhi
    SOFTWARE DEVELOPMENT MODELS AND THEIR REAL ASPECTS Divya Tanwar Sbs , Vivekananda Institute of Professional Studies, GGSIPU, Delhi ABSTRACT Software development life cycle models are the most integral part when it comes to software development which can fully justify today’s digitally environments with increasing mobile, web, and desktop applications. This research deals with a vital and important issue in information technology with respect to various models used in development. It is concerned with the software management processes that examine the area of software development through the development models, which are known as software development life cycle. It represents five of the development models namely, waterfall, Iteration, prototype and spiral and their real time examples which we can relate in our day to day life. These models are complex and difficult to identify related to real time scenario. Therefore, the main objective of this research is to represent different models of software development and make a comparison between them to show the features and defects of each model. This paper demystifies these concepts so that the SDLC is correctly understood with their real time. Keywords: Iterative Prototyping SDLC, Software development life cycle, Spiral model, Real aspects, Waterfall model I. INTRODUCTION Software development life cycle models are the important part of the Software Engineering which is a discipline whose aim to develop quality software, which is on time, with minimum cost and can satisfy the organization needs. There are basically four main models in SDLC with different characteristics and drawbacks [2] .The most difficult task is to identify the model which suits the organization structure, for this every organization need to know the model and its real time application so the user can relate, understand and find out how its actually working.
    [Show full text]
  • Introduction to Openup (Open Unified Process)
    Introduction to OpenUP (Open Unified Process) Different projects have different process needs. Typical factors dictate the needs for a more formal or agile process, such as team size and location, architecture complexity, technology novelty, conformance to standards, among others. Nevertheless, there are good software development practices that benefit any project team and help them to be more effective. This paper introduces the building blocks of OpenUP – an agile and Unified Process that contains the minimal set of practices that help teams to be more effective in developing software. OpenUP embraces a pragmatic, agile philosophy that focuses on the collaborative nature of software development. It is a tools-agnostic, low-ceremony process that can be used as is or extended to address a broad variety of project types. What is OpenUP OpenUP is a minimally sufficient software development process – meaning that only fundamental content is included. Thus, it does not provide guidance on many topics that projects may deal with, such as large team sizes, compliance, contractual situations, safety or mission critical applications, technology-specific guidance, etc. However, OpenUP is complete in the sense it can be manifested as an entire process to build a system. For addressing needs that are not covered in its content, OpenUP is extensible to be used as foundation on which process content can be added or tailored as needed. OpenUP is an agile process. Though OpenUP is lightweight, there is much more to agility than simply being light. Most recognized agile practices are intended to get a team communicating with one another providing a shared understanding of the project.
    [Show full text]
  • Applying Scrum Methods to ITS Projects
    Applying Scrum Methods to ITS Projects www.its.dot.gov/index.htm Final Report — August 2017 Publication Number: FHWA-JPO-17-508 1.1.1.1.1.1 Produced by Noblis, Inc. U.S. Department of Transportation ITS Joint Program Office Notice This document is disseminated under the sponsorship of the Department of Transportation in the interest of information exchange. The United States Government assumes no liability for its contents or use thereof. The U.S. Government is not endorsing any manufacturers, products, or services cited herein and any trade name that may appear in the work has been included only because it is essential to the contents of the work. Technical Report Documentation Page 1. Report No. 2. Government Accession No. 3. Recipient’s Catalog No. FHWA-JPO-17-508 4. Title and Subtitle 5. Report Date August 2017 Applying Scrum Methods to ITS Projects 6. Performing Organization Code 7. Author(s) 8. Performing Organization Report No. Barbara Staples, Dawn Hardesty, Blake Christie, Taylor Deurbrouck, and Josh Seder (Noblis), and Manny Insignares and Patrick Chan (ConSysTec) 9. Performing Organization Name And Address 10. Work Unit No. (TRAIS) Noblis 600 Maryland Ave., SW, Suite 755 11. Contract or Grant No. Washington, DC 20024 DTFH61-12-D-00042 T-5010 Consensus Systems Technologies Corporation (ConSysTec) 301 East 87th Street, Suite 7A New York, NY, USA 10128-4807 Under contract to Cambridge Systematics, Inc. 12. Sponsoring Agency Name and Address 13. Type of Report and Period Covered ITS-Joint Program Office Final Report 1200 New Jersey Avenue, S.E. Washington, DC 20590 14.
    [Show full text]