Search

This book is by far the most systematic and comprehensive review of the field of automated software composition. Based on a formally described and reproducible methodology, it critically discusses the approaches, which are relevant for experts interested in an organized overview of related work. It also provides an introduction and intuitive classification system for researchers new to the field.In order to create this survey, several dozen papers were analyzed with respect to the concrete problems they tackle and the proposed solutions. It delivers both an overview and a qualitative comparison of the approaches, and answers three research questions: What types of automated software composition problems exist? In which use cases do these problems typically occur? And what are the most prominent solution paradigms for the different types? Overall, this book saves a great deal of time for everyone pursuing research in the area of automated software compositionwho needs a comprehensive guide that helps them understand the field, and that relates new approaches to existing ones.

Elevate your software development process with expert technical writing skills, fostering clarity, collaboration, and successful product outcomesKey FeaturesOptimize documentation workflows with collaborative version-controlled'docs-as-code'tooling optionsEngage with interactive learning modules embedded throughout the bookImprove software quality as a lead developer through effective communication in documentationPurchase of the print or Kindle book includes a free PDF eBookBook DescriptionEffective documentation is key to the success of products in remote software development teams, facilitating clear instructions that benefit the entire development team. Technical Writing for Software Developers lays a solid foundation of essential grammar, providing language tips and explaining how precise writing enhances documentation, and walks you through the fundamental types and styles of documentation. Starting with an exploration of the current state of the tech writing industry and its significance in both the software and hardware realms, you'll master the building blocks of technical writing, exploring tooling choices and style guides, and create dynamic multimedia-laden documentation. This book equips you with valuable insights into the writing and feedback process to ensure continuous improvement. Additionally, you'll take a peek at the emerging trends and technologies, including AI tools, shaping the future of technical writing. By the end of this technical writing book, you'll have developed the expertise you need to tackle documentation requests effectively, armed with the knowledge of the best approach for documenting any topic, encompassing text, media elements, structure, and appropriate tools. The skills acquired will enable you to achieve seamless teamwork, enhanced project efficiency, and successful software development.What you will learnCreate engaging multimedia-rich documentationUnderstand the types and styles of documentationDiscover grammar and language tips for clear communicationStreamline your documentation process with the right tooling choiceMaster the writing and feedback process for continuous improvementExplore automation techniques for efficient documentation workflowsEmbrace AI-powered tools for enhanced technical writingWho this book is forThis book is for software developers who want to improve their technical writing prowess. Whether you are a junior developer looking to refine your documentation skills or a professional striving for smoother collaboration, this resource equips you with all the essential knowledge and practical insights you need. Covering everything from creating clear documentation to enhancing career prospects, this book caters to a diverse range of software developers, including programmers, software architects, and software engineers looking to streamline the product development process and save time.

This book highlights recent research advances in various domains related to software ecosystems such as library reuse, collaborative development, cloud computing, open science, sentiment analysis and machine learning. A key aspect of software ecosystems is that software products belong to ever more interdependent networks of co-evolving software components. The ever-increasing importance of social coding platforms has made software ecosystems indispensable to software practitioners, in commercial as well as open-source settings.The book starts with an introductory chapter that provides a historical account of the origins of software ecosystems. It provides the necessary context about the domain of software ecosystems by highlighting its different perspectives, definitions, and representations. It also exemplifies the variety of software ecosystems that have emerged during the previous decades. The remaining book is composed of five parts: Part I contains two chapters on software ecosystem representations, Part II two chapters that focus on complementary ways and techniques of analyzing software ecosystems. Next, Part III includes two chapters that focus on aspects related to the evolution within software ecosystems, while Part IV looks at workflow automation and infrastructure-as-code ecosystems. Finally, Part V focuses on ecosystems for software modeling and for data-intensive software.This book is intended for researchers and practitioners interested in data mining, tooling, and empirical analysis of software ecosystems. The reader will appreciate chapters that cover a wide spectrum of social and technical aspects of software ecosystems, each including an overview of the state of the art.Chapter 2 The Software Heritage Open Science Ecosystem is available open access under a Creative Commons Attribution 4.0 International License via link.springer.com.

Software is everywhere, but despite being so common and useful, it remains magical and mysterious to many. Still, more and more people are finding themselves working for tech companies, or with an array of software products, services, and tools. This can segregate those who understand tech from those that don't. But it doesn't have to be this way.This book aims to bring these two worlds closer together, allowing people to learn basic concepts of software development in a casual and straight-forward way. Assuming no previous technical knowledge, you'll embark on a journey where you can understand and build a new software project from scratch until it is an advanced product with multiple users. A Friendly Guide to Software Development makes technical concepts broadly available and easy to understand. Imagine moving from a “traditional” company and suddenly finding yourself in one where software is the main product or is a foundational component to it. One is often left to wade through the infinite concepts while still doing their actual jobs. This book closes that gap. In doing so, you'll be able to achieve better communication, which will undoubtedly lead to better working relationships, a better working environment, and ultimately better software.What You'll LearnSee how a new software project is createdExamine the basics of software development and architectureKnow which questions to ask to avoid potential problems and pitfallsStart using and building software projectsWho This Book Is ForThose without a traditional technical background people like business and project managers who need to work closely with software developers and teamsPeople who are interested in building a software system but don't know where to start.Programmers who want to jump to development but have no experience in the industry and its common concepts

The high failure rate of enterprise resource planning (ERP) projects is a pressing concern for both academic researchers and industrial practitioners. The challenges of an ERP implementation are particularly high when the project involves designing and developing a system from scratch. Organizations often turn to vendors and consultants for handling such projects but, every aspect of an ERP project is opaque for both customers and vendors. Unlocking the mysteries of building a large-scale ERP system, The Adventurous and Practical Journey to a Large-Scale Enterprise Solution tells the story of implementing an applied enterprise solution. The book covers the field of enterprise resource planning by examining state-of-the-art concepts in software project management methodology, design and development integration policy, and deployment framework, including: A hybrid project management methodology using waterfall as well as a customized Scrum-based approach A novel multi-tiered software architecture featuring an enhanced flowable process engine A unique platform for coding business processes efficiently Integration to embed ERP modules in physical devices A heuristic-based framework to successfully step into the Go-live period Written to help ERP project professionals, the book charts the path that they should travel from project ideation to systems implementation. It presents a detailed, real-life case study of implementing a large-scale ERP and uses storytelling to demonstrate incorrect and correct decisions frequently made by vendors and customers. Filled with practical lessons learned, the book explains the ins and outs of adopting project methodologies. It weaves a tale that features both real-world and scholarly aspects of an ERP implementation.

Innovation is the key to maintain competitive advantage. Innovation in products, processes, and business models help companies to provide economic value to their customers. Identifying the innovative ideas, implementing those ideas, and absorbing them in the market requires investing many resources that could incur large costs. Technology encourages companies to foster innovation to remain competitive in the marketplace. Emerging Technologies for Innovation Management in the Software Industry serves as a resource for technology absorption in companies supporting innovation. It highlights the role of technology to assist software companies—especially small start-ups—to innovate their products, processes, and business models. This book provides the necessary guidelines of which tools to use and under what situations. Covering topics such as risk management, prioritization approaches, and digitally-enabled innovation processes, this premier reference source is an ideal resource for entrepreneurs, software developers, software managers, business leaders, engineers, students and faculty of higher education, researchers, and academicians.

Learn, develop and hone your Linux and DevOps skills by building a lab for learning, testing and exploring the latest Linux and open-source technologies. This book helps Linux users and others to master modern DevOps practices using a wide range of software and tools.Having a home or work-based Linux lab is indispensable to anyone looking to experiment with the ever-evolving landscape of new software and DevOps. With open-source tools and readily available hardware, you will end up with a lab you can use to try virtually any modern software, including Chef, Docker, Kubernetes and stalwarts like DNS, Dovecot, and Postfix for email. You'll set up pipelines for software deployment and focus on discrete projects that help you learn through doing. In the end, you'll acquire the skills needed to become better informed, more marketable engineers and developers, and better able to take on a wide array of software projects with confidence.Practical Linux DevOps is the perfect companion for those who want to learn how to build systems with utility and learn about modern hardware and software practices.What You'll LearnSet up a Linux-based virtualization environment and workstationCreate a lab network with a fully qualified domainBuild web-based applications with NGINX and LAMPUse version-control tools like GitAutomate deployments and configurationsThink like a modern DevOps engineerWho This Book Is ForNew and modestly experienced users with basic understanding of a basic understanding of Windows or Linux command line, as well as would-be and current DevOps engineers, and full-stack and other software developers

Deliver Any Service Far More Effectively, Based on What Customers Really Want As service stacks grow more complex, it becomes even tougher to deliver on-demand IT services that meet customers'expectations for speed, consistency, reliability, security, privacy, and value. Layering on new cloud technologies, architectural approaches, or methodologies can aggravate the problem by widening the gap between what delivery teams think they're delivering and what customers actually experience. In Lean DevOps, technical leader Robert Benefield helps you escape this spiral, reverse bad habits, and regain the situational awareness you need to deliver the right services in the right way. Writing for delivery team members and their leaders, Benefield shows how to improve information flow throughout your organization, so you can move toward your customers'target outcomes. He identifies problems arising from traditional approaches to managing teams, debunks excuses often used to prevent progress, and offers realistic recommendations for everything from requirements to incentives. • Understand key dynamics that impact service delivery, and avoid focusing on the wrong issues • Give your delivery teams stronger abilities to learn and improve • Improve team maturity and implement prerequisites for effective use of automation and AI/ML • Optimize key service delivery elements, from instrumentation to queue masters and cycles • Organize and manage workflows more effectively • Handle governance associated with internal controls and external legal/regulatory requirements • Leverage the power of Lean and Mission Command to accelerate innovation, empower subordinates, and drive the outcomes you want

Software development has been a troubling since it first started. There are seven chronic problems that have plagued it from the beginning: Incomplete and ambiguous user requirements that grow by >2% per month. Major cost and schedule overruns for large applications > 35% higher than planned. Low defect removal efficiency (DRE) 30% above 10,000 function points. Poor quality and low reliability after the software is delivered: > 5 bugs per FP. Breach of contract litigation against software outsource vendors. Expensive maintenance and enhancement costs after delivery. These are endemic problems for software executives, software engineers and software customers but they are not insurmountable. In Software Development Patterns and Antipatterns, software engineering and metrics pioneer Capers Jones presents technical solutions for all seven. The solutions involve moving from harmful patterns of software development to effective patterns of software development. The first section of the book examines common software development problems that have been observed in many companies and government agencies. The data on the problems comes from consulting studies, breach of contract lawsuits, and the literature on major software failures. This section considers the factors involved with cost overruns, schedule delays, canceled projects, poor quality, and expensive maintenance after deployment.The second section shows patterns that lead to software success. The data comes from actual companies. The section's first chapter on Corporate Software Risk Reduction in a Fortune 500 company was based on a major telecom company whose CEO was troubled by repeated software failures. The other chapters in this section deal with methods of achieving excellence, as well as measures that can prove excellence to C-level executives, and with continuing excellence through the maintenance cycle as well as for software development.

The agile transformation is an act of transforming an organization's form or nature gradually to one that can embrace and thrive in a flexible, collaborative, self-organizing, and fast-changing environment. It seems like most of the companies starting an agile transformation never reach the goal of agility, but there are those few that truly become agile and reap incredible benefits by utilizing DevOps as well.This book introduces the theory and practice of the'double-flywheels model'of Continuous Delivery 2.0: Discovery Loop, which allows information technology (IT) organizations to help businesses figure out the most efficacious ways to develop. Additionally, it explores applications of the Verification Loop that allows IT organizations to deliver value quickly and safely with high quality. Along the way, the book provides an array of insights and case studies that dive into all the aspects of software delivery, and how to implement Continuous Delivery in the most economical way for long-run business development.Features Organization culture and software architecture Business requirement management Pipeline and tooling Branching and releasing strategy Automation strategy Configuration and artefacts management Deployment and production healthy The case studies at the end of the book—scenarios in which the author was personally involved—are explored in depth and meticulously detailed in order to represent typical agile transition scenarios that will benefit all readers.

With the rise of DevOps, low-cost cloud computing, and container technologies, the way Java developers approach development today has changed dramatically. This practical guide helps you take advantage of microservices, serverless, and cloud native technologies using the latest DevOps techniques to simplify your build process and create hyperproductive teams.Stephen Chin, Melissa McKay, Ixchel Ruiz, and Baruch Sadogursky from JFrog help you evaluate an array of options. The list includes source control with Git, build declaration with Maven and Gradle, CI/CD with CircleCI, package management with Artifactory, containerization with Docker and Kubernetes, and much more. Whether you're building applications with Jakarta EE, Spring Boot, Dropwizard, MicroProfile, Micronaut, or Quarkus, this comprehensive guide has you covered.Explore software lifecycle best practicesUse DevSecOps methodologies to facilitate software development and deliveryUnderstand the business value of DevSecOps best practicesManage and secure software dependenciesDevelop and deploy applications using containers and cloud native technologiesManage and administrate source control repositories and development processesUse automation to set up and administer build pipelinesIdentify common deployment patterns and antipatternsMaintain and monitor software after deployment

Most companies developing software employ something they call'Agile.'But there's widespread misunderstanding of what Agile is and how to use it. If you want to improve your software development team's agility, this comprehensive guidebook's clear, concrete, and detailed guidance explains what to do and why, and when to make trade-offs.In this thorough update of the classic Agile how-to guide, James Shore provides no-nonsense advice on Agile adoption, planning, development, delivery, and management taken from over two decades of Agile experience. He brings the latest ideas from Extreme Programming, Scrum, Lean, DevOps, and more into a cohesive whole. Learn how to successfully bring Agile development to your team and organization--or discover why Agile might not be for you.This book explains how to:Improve agility: create the conditions necessary for Agile to succeed and scale in your organizationFocus on value: work as a team, understand priorities, provide visibility, and improve continuouslyDeliver software reliably: share ownership, decrease development costs, evolve designs, and deploy continuouslyOptimize value: take ownership of product plans, budgets, and experiments--and produce market-leading software

This book focuses on crisis management in software development which includes forecasting, responding and adaptive engineering models, methods, patterns and practices. It helps the stakeholders in understanding and identifying the key technology, business and human factors that may result in a software production crisis. These factors are particularly important for the enterprise-scale applications, typically considered very complex in managerial and technological aspects and therefore, specifically addressed by the discipline of software engineering. Therefore, this book throws light on the crisis responsive, resilient methodologies and practices; therewith, it also focuses on their evolutionary changes and the resulting benefits.

In todayâ??s IT architectures, microservices and serverless functions play increasingly important roles in process automation. But how do you create meaningful, comprehensive, and connected business solutions when the individual components are decoupled and independent by design? Targeted at developers and architects, this book presents a framework through examples, practical advice, and use cases to help you design and automate complex processes.As systems are more distributed, asynchronous, and reactive, process automation requires state handling to deal with long-running interactions. Author Bernd Ruecker demonstrates how to leverage process automation technology like workflow engines to orchestrate software, humans, decisions, or bots.Learn how modern process automation compares to business process management, service-oriented architecture, batch processing, event streaming, and data pipeline solutionsUnderstand how to use workflow engines and executable process models with BPMNUnderstand the difference between orchestration and choreography and how to balance both

Learn the fundamentals of Design Thinking and how to apply Design Thinking techniques in defining software development and AI solutions. Design Thinking is an approach to innovation which identifies problems and generates solution ideas that can be rapidly proven through prototyping.This book provides a brief history of Design Thinking and an overview of the process. It then drills down into more detail regarding methods and tools used in a Design Thinking workshops leading to useful prototypes. Guidance is provided on: Preparing for a Design Thinking Workshop Uncovering potential business problems that might be solvedPrioritizing potential solutionsIdentifying and characterizing stakeholdersChoosing the right prototypes for developmentLimiting scope and best practices in prototype buildingThe book concludes with a discussion of best practices in operationalizing successful prototypes, and describes change management techniques critical for successful adoption. You can use the knowledge gained from reading this book to incorporate Design Thinking techniques in your software development and AI projects, and assure timely and successful delivery of solutions.What You Will LearnGain foundational knowledge of what Design Thinking is and when to apply the techniqueDiscover preparation and facilitation techniques used in workshopsKnow how ideas are generated and then validated through prototypingUnderstand implementation best practices, including change management considerationsWho This Book Is ForBusiness decision makers and project stakeholders as well as IT project owners who seek a method leading to fast development of successful software and AI prototypes demonstrating real business value. Also for data scientists, developers, and systems integrators who are interested in facilitating or utilizing Design Thinking workshops to drive momentum behind potential software development and AI projects.

Establish business agility in your organization by applying industry-proven scaling strategies from popular Scrum frameworks such as Scrum of Scrums (SoS), Scrum@Scale, Nexus, Large-Scale Scrum (LeSS), Disciplined Agile, and SAFeKey FeaturesBook DescriptionScaled Scrum and Lean-Agile practices provide essential strategies to address large and complex product development challenges not addressed in traditional Scrum. This Scrum/ Lean-Agile handbook provides a comprehensive review and analysis of industry-proven scaling strategies that enable business agility on an enterprise scale. Free of marketing hype or vendor bias, this book helps you decide which practices best fit your situation. You'll start with an introduction to Scrum as a lightweight software development framework and then explore common approaches to scaling it for more complex development scenarios. The book will then guide you through systems theory, lean development, and the application of holistic thinking to more complex software and system development activities. Throughout, you'll learn how to support multiple teams working in collaboration to develop large and complex products and explore how to manage cross-team integration, dependency, and synchronization issues. Later, you'll learn how to improve enterprise operational efficiency across value creation and value delivery activities, before discovering how to align product portfolio investments with corporate strategies. By the end of this Scrum book, you and your product teams will be able to get the most value out of Agile at scale, even in complex cyber-physical system development environments.What you will learnUnderstand the limitations of traditional Scrum practicesExplore the roles and responsibilities in a scaled Scrum and Lean-Agile development environmentTailor your Scrum approach to support portfolio and large product development needsApply systems thinking to evaluate the impacts of changes in the interdependent parts of a larger development and delivery systemScale Scrum practices at both the program and portfolio levels of managementUnderstand how DevOps, test automation, and CI/CD capabilities help in scaling Scrum practicesWho this book is for

Operations Anti-Patterns, DevOps Solutions shows how to implement DevOps techniques in the kind of imperfect environments most developers work in. Part technology tutorial, part reference manual, and part psychology handbook, this practical guide shows you realistic ways to bring DevOps to your team when you don't have the flexibility to make sweeping changes in organizational structure. Summary Operations Anti-Patterns, DevOps Solutions shows how to implement DevOps techniques in the kind of imperfect environments most developers work in. Part technology tutorial, part reference manual, and part psychology handbook, this practical guide shows you realistic ways to bring DevOps to your team when you don't have the flexibility to make sweeping changes in organizational structure. Purchase of the print book includes a free eBook in PDF, Kindle, and ePub formats from Manning Publications. About the technology To some extent, all organizations—even yours—suffer from poor development practices, garbled communications, and outdated legacy systems. The good news is DevOps can help you improve your processes. First, however, you'll need to recognize the core issues holding you back. This book empowers you to deliver DevOps with limited resources while navigating the office politics and entrenched mindsets that are all too common in actual workplaces. About the book Operations Anti-Patterns, DevOps Solutions offers clear steps for transforming development and communication. Using jargon-free language, this book describes incremental techniques that pay off immediately. Streamline your workflow, manage unplanned time, and build operational metrics. Whatever your issues, this book holds the keys to organizational success. What's inside Turn failure into opportunity Drive change through culture Break down knowledge silos Settle middle management turf wars About the reader For team leaders and managers. About the author Jeffery D. Smith has been in the technology industry for over 15 years. He has managed DevOps transformations at the ad-tech firm Centro and the online ordering platform Grubhub. Table of Contents 1 The DevOps ingredients 2 The paternalist syndrome 3 Operational blindness 4 Data instead of information 5 Quality as a condiment 6 Alert fatigue 7 The empty toolbox 8 Off-hour deployments 9 Wasting a perfectly good incident 10 Information hoarding: Only Brent knows 11 Culture by decree 12 Too many yardsticks

Today, software engineers need to know not only how to program effectively but also how to develop proper engineering practices to make their codebase sustainable and healthy. This book emphasizes this difference between programming and software engineering.How can software engineers manage a living codebase that evolves and responds to changing requirements and demands over the length of its life? Based on their experience at Google, software engineers Titus Winters and Hyrum Wright, along with technical writer Tom Manshreck, present a candid and insightful look at how some of the world's leading practitioners construct and maintain software. This book covers Google's unique engineering culture, processes, and tools and how these aspects contribute to the effectiveness of an engineering organization.You'll explore three fundamental principles that software organizations should keep in mind when designing, architecting, writing, and maintaining code:How time affects the sustainability of software and how to make your code resilient over timeHow scale affects the viability of software practices within an engineering organizationWhat trade-offs a typical engineer needs to make when evaluating design and development decisions

Delve deep into the various technical practices, principles, and values of Agile.Key FeaturesDiscover the essence of Agile software development and the key principles of software designExplore the fundamental practices of Agile working, including test-driven development (TDD), refactoring, pair programming, and continuous integrationLearn and apply the four elements of simple designBook DescriptionThe number of popular technical practices has grown exponentially in the last few years. Learning the common fundamental software development practices can help you become a better programmer. This book uses the term Agile as a wide umbrella and covers Agile principles and practices, as well as most methodologies associated with it. You'll begin by discovering how driver-navigator, chess clock, and other techniques used in the pair programming approach introduce discipline while writing code. You'll then learn to safely change the design of your code using refactoring. While learning these techniques, you'll also explore various best practices to write efficient tests. The concluding chapters of the book delve deep into the SOLID principles - the five design principles that you can use to make your software more understandable, flexible and maintainable. By the end of the book, you will have discovered new ideas for improving your software design skills, the relationship within your team, and the way your business works.What you will learnLearn the red, green, refactor cycle of classic TDD and practice the best habits such as the rule of 3, triangulation, object calisthenics, and moreRefactor using parallel change and improve legacy code with characterization tests, approval tests, and Golden MasterUse code smells as feedback to improve your designLearn the double cycle of ATDD and the outside-in mindset using mocks and stubs correctly in your testsUnderstand how Coupling, Cohesion, Connascence, SOLID principles, and code smells are all relatedImprove the understanding of your business domain using BDD and other principles for'doing the right thing, not only the thing right'Who this book is forThis book is designed for software developers looking to improve their technical practices. Software coaches may also find it helpful as a teaching reference manual. This is not a beginner's book on how to program. You must be comfortable with at least one programming language and must be able to write unit tests using any unit testing framework.

Discover DevOps secrets from leading experts. Viktor Farcic interviews DevOps industries voices including Mike Kail, Greg Bledsoe, Jeff Sussna, James Turnbull, Kohsuke Kawaguchi, Liz Keogh, and more.Key FeaturesLeading DevOps experts share their insights into modern DevOps practiceEngage with the real-world challenges of putting DevOps to workStrengthen your DevOps practices now and prepare for future DevOps trendsBook DescriptionDevOps promises to break down silos, uniting organizations to deliver high quality output in a cross-functional way. In reality it often results in confusion and new silos: pockets of DevOps practitioners fight the status quo, senior decision-makers demand DevOps paint jobs without committing to true change. Even a clear definition of what DevOps is remains elusive. In DevOps Paradox, top DevOps consultants, industry leaders, and founders reveal their own approaches to all aspects of DevOps implementation and operation. Surround yourself with expert DevOps advisors. Viktor Farcic draws on experts from across the industry to discuss how to introduce DevOps to chaotic organizations, align incentives between teams, and make use of the latest tools and techniques. With each expert offering their own opinions on what DevOps is and how to make it work, you will be able to form your own informed view of the importance and value of DevOps as we enter a new decade. If you want to see how real DevOps experts address the challenges and resolve the paradoxes, this book is for you.What you will learnExpert opinions on:Introducing DevOps into real-world, chaotic business environmentsDeciding between adopting cutting edge tools or sticking with tried-and-tested methodsInitiating necessary business change without positional powerManaging and overcoming fear of change in DevOps implementationsAnticipating future trends in DevOps and how to prepare for themGetting the most from Kubernetes, Docker, Puppet, Chef, and AnsibleCreating the right incentives for DevOps success across an organizationThe impact of new techniques, such as Lambda, serverless, and schedulers, on DevOps practiceWho this book is forAnybody interested in DevOps will gain a lot from this book. If you want to get beyond the simplistic ideals and engage with the deep challenges of putting DevOps to work in the real world, this book is for you.

How do you detangle a monolithic system and migrate it to a microservice architecture? How do you do it while maintaining business-as-usual? As a companion to Sam Newman's extremely popular Building Microservices, this new book details a proven method for transitioning an existing monolithic system to a microservice architecture.With many illustrative examples, insightful migration patterns, and a bevy of practical advice to transition your monolith enterprise into a microservice operation, this practical guide covers multiple scenarios and strategies for a successful migration, from initial planning all the way through application and database decomposition. You'll learn several tried and tested patterns and techniques that you can use as you migrate your existing architecture.Ideal for organizations looking to transition to microservices, rather than rebuildHelps companies determine whether to migrate, when to migrate, and where to beginAddresses communication, integration, and the migration of legacy systemsDiscusses multiple migration patterns and where they applyProvides database migration examples, along with synchronization strategiesExplores application decomposition, including several architectural refactoring patternsDelves into details of database decomposition, including the impact of breaking referential and transactional integrity, new failure modes, and more

This open access book presents the outcomes of the “Design for Future – Managed Software Evolution” priority program 1593, which was launched by the German Research Foundation (“Deutsche Forschungsgemeinschaft (DFG)”) to develop new approaches to software engineering with a specific focus on long-lived software systems. The different lifecycles of software and hardware platforms lead to interoperability problems in such systems. Instead of separating the development, adaptation and evolution of software and its platforms, as well as aspects like operation, monitoring and maintenance, they should all be integrated into one overarching process.Accordingly, the book is split into three major parts, the first of which includes an introduction to the nature of software evolution, followed by an overview of the specific challenges and a general introduction to the case studies used in the project. The second part of the book consists of the main chapters on knowledge carrying software, and cover tacit knowledge in software evolution, continuous design decision support, model-based round-trip engineering for software product lines, performance analysis strategies, maintaining security in software evolution, learning from evolution for evolution, and formal verification of evolutionary changes. In turn, the last part of the book presents key findings and spin-offs. The individual chapters there describe various case studies, along with their benefits, deliverables and the respective lessons learned. An overview of future research topics rounds out the coverage.The book was mainly written for scientific researchers and advanced professionals with an academic background. They will benefit from its comprehensive treatment of various topics related to problems that are now gaining in importance, given the higher costs for maintenance and evolution in comparison to the initial development, and the fact that today, most software is not developed from scratch, but as part of a continuum of former and future releases.

Develop faster with DevOps DevOps embraces a culture of unifying the creation and distribution of technology in a way that allows for faster release cycles and more resource-efficient product updating. DevOps For Dummies provides a guidebook for those on the development or operations side in need of a primer on this way of working. Inside, DevOps evangelist Emily Freeman provides a roadmap for adopting the management and technology tools, as well as the culture changes, needed to dive head-first into DevOps. Identify your organization's needs Create a DevOps framework Change your organizational structure Manage projects in the DevOps world DevOps For Dummies is essential reading for developers and operations professionals in the early stages of DevOps adoption.

Are you working on a codebase where cost overruns, death marches, and heroic fights with legacy code monsters are the norm? Battle these adversaries with novel ways to identify and prioritize technical debt, based on behavioral data from how developers work with code. And that's just for starters. Because good code involves social design, as well as technical design, you can find surprising dependencies between people and code to resolve coordination bottlenecks among teams. Best of all, the techniques build on behavioral data that you already have: your version-control system. Join the fight for better code! Use statistics and data science to uncover both problematic code and the behavioral patterns of the developers who build your software. This combination gives you insights you can't get from the code alone. Use these insights to prioritize refactoring needs, measure their effect, find implicit dependencies between different modules, and automatically create knowledge maps of your system based on actual code contributions. In a radical, much-needed change from common practice, guide organizational decisions with objective data by measuring how well your development teams align with the software architecture. Discover a comprehensive set of practical analysis techniques based on version-control data, where each point is illustrated with a case study from a real-world codebase. Because the techniques are language neutral, you can apply them to your own code no matter what programming language you use. Guide organizational decisions with objective data by measuring how well your development teams align with the software architecture. Apply research findings from social psychology to software development, ensuring you get the tools you need to coach your organization towards better code. If you're an experienced programmer, software architect, or technical manager, you'll get a new perspective that will change how you work with code.What You Need:You don't have to install anything to follow along in the book. TThe case studies in the book use well-known open source projects hosted on GitHub. You'll use CodeScene, a free software analysis tool for open source projects, for the case studies. We also discuss alternative tooling options where they exist.

This book provides a comprehensive overview of the field of software processes, covering in particular the following essential topics: software process modelling, software process and lifecycle models, software process management, deployment and governance, and software process improvement (including assessment and measurement). It does not propose any new processes or methods; rather, it introduces students and software engineers to software processes and life cycle models, covering the different types ranging from “classical”, plan-driven via hybrid to agile approaches.The book is structured as follows: In chapter 1, the fundamentals of the topic are introduced: the basic concepts, a historical overview, and the terminology used. Next, chapter 2 covers the various approaches to modelling software processes and lifecycle models, before chapter 3 discusses the contents of these models, addressing plan-driven, agile and hybrid approaches. The following three chapters address various aspects of using software processes and lifecycle models within organisations, and consider the management of these processes, their assessment and improvement, and the measurement of both software and software processes. Working with software processes normally involves various tools, which are the focus of chapter 7, before a look at current trends in software processes in chapter 8 rounds out the book.This book is mainly intended for graduate students and practicing professionals. It can be used as a textbook for courses and lectures, for self-study, and as a reference guide. When used as a textbook, it may support courses and lectures on software processes, or be used as complementary literature for more basic courses, such as introductory courses on software engineering or project management. To this end, it includes a wealth of examples and case studies, and each chapter is complemented by exercises that help readers gain a better command of the concepts discussed.

Provides a coherent, comprehensive and concise coverage of the software project management, discipline and concepts. The first part focuses on the project management life cycle activities, which includes planning, evaluation, scheduling, resource allocation and monitoring with special emphasis on hands-on tools and techniques, models, methods, and documentation. A primer on the SDLC is also provided with the focus on various popular models and paradigms like waterfall and prototyping as well as new trends like agile methods. The second part of the book covers the entire gamut of umbrella activities like risk, cost, quality, configuration, contract, change and people management -- Back cover.

Learn from an expert on how use self-adapting and self-healing systems within Docker.Key FeaturesViktor Farcic shows you all aspects in the creation of self-adapting and self-healing systems in both a practical and hands-on approach.Learn how to choose a successful solution for metrics storage and query, including InfluxDB, Nagios and Sensu, Prometheus and Graphite.Discover how to integrate Docker Flow Monitor with Docker Flow Proxy.How to apply Docker self-healing and self-adaptive to both services and infrastructure.Book DescriptionBuilding on The DevOps 2.0 Toolkit and The DevOps 2.1 Toolkit: Docker Swarm, Viktor Farcic brings his latest exploration of the Docker technology as he records his journey to explore two new programs, self-adaptive and self-healing systems within Docker. The DevOps 2.2 Toolkit: Self-Sufficient Docker Clusters is the latest book in Viktor Farcic's series that helps you build a full DevOps Toolkit. This book in the series looks at Docker, the tool designed to make it easier in the creation and running of applications using containers. In this latest entry, Viktor combines theory with a hands-on approach to guide you through the process of creating self-adaptive and self-healing systems. Within this book, Viktor will cover a wide-range of emerging topics, including what exactly self-adaptive and self-healing systems are, how to choose a solution for metrics storage and query, the creation of cluster-wide alerts and what a successful self-sufficient system blueprint looks like. Work with Viktor and dive into the creation of self-adaptive and self-healing systems within Docker. What you will learnLet Viktor Farcic show you all aspects in the creation of self-adapting and self-healing systems in both a practical and hands-on approach.Learn how to choose a successful solution for metrics storage and query, including InfluxDB, Nagios and Sensu, Prometheus and Graphite.Understand how to integrate Docker Flow Monitor with Docker Flow Proxy.The creation of cluster-wide alerts by creating alerts based on metrics.How to apply self-healing and self-adaptive to both services and infrastructure.Who this book is forThis book is for professionals experienced with Docker looking to create both self-adapting and self-healing systems using the software.

Build systems faster and more effectively with Mob Programming. Mob Programming is an approach to developing software that radically reduces defects and key-person dependencies by having a group of people work together at a single machine. See how to avoid the most common pitfalls that teams make when first starting out. Discover what it takes to create and support a successful mob. Now you can take collaborative programming to the next level with Mob Programming. Mob Programming is a natural extension of the popular Pair Programming concept, and is not restricted to a specific programming language or technology. It can be used by anyone who develops software, including dev leads, software developers, and agile coaches. The more people working on a bug or feature results in fewer dependencies on individuals, and overall increased learning for everyone involved. With more eyes on the code, you'll find you develop better solutions with fewer defects. Set up your team for success by introducing Mob Programming in a way that benefits them. Create a good first Mobbing experience for your team with a template that avoids the common traps beginners may fall into. Master a collaborative and empathic mindset to help optimize the Mobbing experience. Learn how to make adjustments when things go wrong. Adapt your mobbing to different types of development tasks. Get management buy-in for your Mobbing experiment by demonstrating the benefits. Discover the equipment and resources you need, and how to adjust your workspace for an effective mob. Get important features to market sooner, squish bugs faster, and collaborate better today with Mob Programming. What You Need: All you need is three or more programmers, a meeting workspace that's large enough to accommodate your mob, and a computer on which to work.

This book is a self-contained, practical introduction how to use FeatureIDE for modeling and implementing variable systems. In particular, readers learn how to analyze domains using feature models, specify requirements in form of configurations, and how to generate code based on conditional compilation and feature-oriented programming. Given the interactive style of the book, readers can directly try out the open-source development environment. All code examples are available in the standard distribution on GitHub and can immediately been used for individual modifications. Each part of the book is presented as a step-by-step tutorial and additionally illustrated using an ongoing example of elevator control software written in Java.Written by the core development team of FeatureIDE, this book is suitable for students using a tool for deepening the theoretical foundations of variability modeling and implementation, and as a reference for practitioners needing a stable and scalable tool for industrial applications. FeatureIDE is the most used open-source tool for feature modeling and has been continuously improved since 2004. The success of FeatureIDE is due to being a vehicle for cutting-edge product-line research by still providing an easy-to-use and seamless integration into Eclipse.

Why does poor software quality continue to plague enterprises of all sizes in all industries? Part of the problem lies with the process, rather than individual developers. This practical guide provides ten best practices to help team leaders create an effective working environment through key adjustments to their process.As a follow-up to their popular book, Building Maintainable Software, consultants with the Software Improvement Group (SIG) offer critical lessons based on their assessment of development processes used by hundreds of software teams. Each practice includes examples of goalsetting to help you choose the right metrics for your team.Achieve development goals by determining meaningful metrics with the Goal-Question-Metric approachTranslate those goals to a verifiable Definition of DoneManage code versions for consistent and predictable modificationControl separate environments for each stage in the development pipelineAutomate tests as much as possible and steer their guidelines and expectationsLet the Continuous Integration server do much of the hard work for youAutomate the process of pushing code through the pipelineDefine development process standards to improve consistency and simplicityManage dependencies on third party code to keep your software consistent and up to dateDocument only the most necessary and current knowledge

Reduce the time spent analyzing infrastructure modules while lowering your cost and resources in the process. Most software project teams that develop custom software build the systems from scratch. With limited budgets and time, they often concentrate on the business functionality and try to minimize or ignore the infrastructure functionality. This book shows you how to develop flexible and and reusable modules that can be enhanced over time. Software infrastructure modules are the base modules in any software system. This book examines the key functionality supported by each of them and discusses the essential services for other modules.You'll explore the infrastructure modules required in large enterprise projects and each one will be explained with high-level use-cases, wireframes, and entities.Add Infrastructure Software Modules for Enterprises to your company's library today. What You'll LearnReview infrastructure modules and how they interact together or with other business modules Understand the main functionalities provided by infrastructure modules Explore the design of infrastructure modules via use-cases, wireframes, and entities Who This Book Is ForProject team members that implement custom portals or software systems provided by public or private sector organizations.

SummaryWriting Great Specifications is an example-rich tutorial that teaches you how to write good Gherkin specification documents that take advantage of the benefits of specification by example. Foreword written by Gojko Adzic.Purchase of the print book includes a free eBook in PDF, Kindle, and ePub formats from Manning Publications.About the TechnologyThe clearest way to communicate a software specification is to provide examples of how it should work. Turning these story-based descriptions into a well-organized dev plan is another matter. Gherkin is a human-friendly, jargon-free language for documenting a suite of examples as an executable specification. It fosters efficient collaboration between business and dev teams, and it's an excellent foundation for the specification by example (SBE) process.About the BookWriting Great Specifications teaches you how to capture executable software designs in Gherkin following the SBE method. Written for both developers and non-technical team members, this practical book starts with collecting individual feature stories and organizing them into a full, testable spec. You'll learn to choose the best scenarios, write them in a way that anyone can understand, and ensure they can be easily updated by anyone.management. What's InsideReading and writing GherkinDesigning story-based test casesTeam CollaborationManaging a suite of Gherkin documentsAbout the ReaderPrimarily written for developers and architects, this book is accessible to any member of a software design team.About the AuthorKamil Nicieja is a seasoned engineer, architect, and project manager with deep expertise in Gherkin and SBE.Table of contentsIntroduction to specification by example and Gherkin PART 1 - WRITING EXECUTABLE SPECIFICATIONS WITH EXAMPLESThe specification layer and the automation layer Mastering the Given-When-Then template The basics of scenario outlines Choosing examples for scenario outlines The life cycle of executable specifications Living documentation PART 2 - MANAGING SPECIFICATION SUITES Organizing scenarios into a specification suite Refactoring features into abilities and business needs Building a domain-driven specification suite Managing large projects with bounded contexts

Learn how to use stories throughout the agile software development lifecycle. Through lessons and examples, Agile UX Storytelling demonstrates to product owners, customers, scrum masters, software developers, and designers how to craft stories to facilitate communication, identify problems and patterns, refine collaborative understanding, accelerate delivery, and communicate the business value of deliverables. Rebecca Baker applies the techniques of storytelling to all facets of the software development lifecycle—planning, requirements gathering, internal and external communication, design, and testing—and shows how to use stories to improve the delivery process.What You'll LearnCraft stories to facilitate communication within the project team and with stakeholdersLeverage stories to identify problems and patterns, accelerate delivery, and communicate business valueApply storytelling techniques to all stages of the SDLCMarshal user stories to focus requirements gathering and ensure a consistent messageWho This Book Is ForAll SDLC and UX roles: product owners, customers, scrum masters, software developers, and UX designers

Achieve streamlined, rapid production with enterprise-level DevOps Awarded DevOps 2017 Book of the Year, The DevOps Adoption Playbook provides practical, actionable, real-world guidance on implementing DevOps at enterprise scale. Author Sanjeev Sharma heads the DevOps practice for IBM; in this book, he provides unique guidance and insight on implementing DevOps at large organizations. Most DevOps literature is aimed at startups, but enterprises have unique needs, capabilities, limitations, and challenges;'DevOps for startups'doesn't work at this scale, but the DevOps paradigm can revolutionize enterprise IT. Deliver high-value applications and systems with velocity and agility by adopting the necessary practices, automation tools, and organizational and cultural changes that lead to innovation through rapid experimentation. Speed is an advantage in the face of competition, but it must never come at the expense of quality; DevOps allows your organization to keep both by intersecting development, quality assurance, and operations. Enterprise-level DevOps comes with its own set of challenges, but this book shows you just how easily they are overcome. With a slight shift in perspective, your organization can stay ahead of the competition while keeping costs, risks, and quality under control. Grasp the full extent of the DevOps impact on IT organizations Achieve high-value innovation and optimization with low cost and risk Exceed traditional business goals with higher product release efficiency Implement DevOps in large-scale enterprise IT environments DevOps has been one of IT's hottest trends for the past decade, and plenty of success stories testify to its effectiveness in organizations of any size, industry, or level of IT maturity, all around the world. The DevOps Adoption Playbook shows you how to get your organization on board so you can slip production into the fast lane and innovate your way to the top.

This book opens the “black box” of software sourcing by explaining how dynamic software alignment is established and how it impacts business performance outcomes. By investigating how software-sourcing modes are related to value generation in the post-implementation phase, it shows researchers and managers the impact logic of on-demand, on-premises, and in-house software on dynamic fit and process-level performance outcomes in a client organization. It describes dynamic IT alignment as the key to success in a fast-moving digital world with software-as-a-service on the rise and highlights the fact that today companies can choose between developing software in-house (make) or sourcing packaged systems in an on-premises (buy) or an on-demand (lease) mode. This book is the first to explicitly compare these sourcing arrangements with each other in terms of alignment and business performance.

Increase profitability, elevate work culture, and exceed productivity goals through DevOps practices.More than ever, the effective management of technology is critical for business competitiveness. For decades, technology leaders have struggled to balance agility, reliability, and security. The consequences of failure have never been greater―whether it's the healthcare.gov debacle, cardholder data breaches, or missing the boat with Big Data in the cloud.And yet, high performers using DevOps principles, such as Google, Amazon, Facebook, Etsy, and Netflix, are routinely and reliably deploying code into production hundreds, or even thousands, of times per day.Following in the footsteps of The Phoenix Project, The DevOps Handbook shows leaders how to replicate these incredible outcomes, by showing how to integrate Product Management, Development, QA, IT Operations, and Information Security to elevate your company and win in the marketplace.

Learn the nuts and bolts of scrum—its framework, roles, team structures, ceremonies, and artifacts—from the scrum master's perspective.The Art of Scrum details the scum master's responsibilities and core functions in planning and facilitating the ceremonies and artifacts of a scrum team: sprint planning, sprint execution, backlog refinement, daily standups, sprint reviews, and sprint retrospectives. It analyzes the scrum master's interactions with other scrum roles, including the product owner, development team members, other scrum masters, and the agile coach. Scrum Master Dave McKenna catalogs the three skill sets that you must master to be successful at binding teams and unleashing agility: soft skills, technical skills, and contingency skills. You'll benefit from the author's examination of these skill sets with insights and anecdotes drawn from his own experience as an engineer, agile coach, and scrum master. He illustrates common mistakes scrum masters make, as well as modeling successful strategies, adaptations to changes, and solutions to tricky problems.What You'll Learn:How scrum masters facilitate the agile ceremoniesHow scrum masters align scrum teams to sprint goals and shield them from interferenceHow scrum masters coach product owners to build a backlog and refine user storiesHow scrum masters manage contingencies such as intra-team conflicts, organizational impediments, technical debt, emergent architecture, personnel changes, scope creep, and learning from failure.Who This Book Is For:The primary readership is scrum masters, product owners, and dev team members. The secondary readership is scrum stakeholders, including executive sponsors, project managers, functional and line managers, administrative personnel, expert consultants, testers, vendors, and end users. The tertiary readership is anybody who wants to know how build an agile team that consistently delivers value and continuous improvement.

Key FeaturesBook DescriptionNo matter whether you are a student or an industry veteran, self employment adds a new dimension of opportunities to “learn and earn”, whether it be on a full-time or part-time basis. Develop the business acumen and understanding of the link between software patterns and business strategy that you need to become a successful and profitable independent software developer. Discover how to apply your software development skills to entrepreneurship. Decide whether you just want to earn or aspire to build the next Facebook. Supported by real world case studies and input from industry experts, the book looks at the business topics you need to understand to become an independent software developer. From the initial steps of identifying how you can make a profit with your software development skills, through to making your first sale and managing your projects, you will learn how to manage each of the major steps involved in becoming a self employed software developer – whether you decide to go freelance, take up contracting or develop your own product. Written specifically for software and web developers, the book identifies how business issues have a direct impact on code patterns used in software projects. Learn how to build your code to support your business model and with safety features to protect against potential threats that may emerge from the changing business environment.What you will learnIdentify and understand your target market. Propose the value of what your service or product offers. Build a business model that identifies key entities required to make your software business work. Develop marketing a marketing strategy that targets the right customer segments and produces the sales you need to be profitable. Analyze information to make better decisions and understand your business performance. Understand people through observation and use this to your advantage in project management and negotiation. Improve accuracy of estimates for time and costs of your software projects. Understand the relationship between code and the business strategy. Identify software features from a business perspective, allowing you to prioritise must have features from those that are less important to your profitability. Avoid the trap of increasing software development time and costs from features that provide no benefit or sales increase.Who this book is for

Superior software productivity requires a relentless focus on people, motivation, and communication. In Improving Software Development Productivity, world-renowned software engineering expert Dr. Randall W. Jensen introduces a proven, quantitative approach to achieving this focus. Jensen helps you measure your organization's capacity and productivity, and then use that information to improve multiple facets of developer and team performance, and to build more accurate estimates and schedules. Focusing on management as the principal cost and schedule driver in software projects, he demonstrates a powerful tool based on his Jensen II (Seer) model: the model that underlies many leading software estimation tools. Through real case studies, you'll learn how to predict the productivity impact of any major management decision, and quantitatively support a transition to “extreme” or “agile” software development environments. For decades, Jensen has been the industry's go-to expert on improving software project productivity. This book distills his insights and gives you the tools and knowledge to apply them. This book will help you Recognize the centrality of communication and culture, and translate this awareness into quantitative improvements Predict the impact of changes in personnel, management style, development environments, product constraints, and technologies Optimize decision making throughout a project's lifecycle, and avoid counterproductive changes Understand modern estimating models and parameters, so you can apply them more effectively Formulate more accurate and useful estimates with leading tools such as Sage, REVIC, COCOMO II, and SEER-SEM Maintain firmer control over costs and timeframes in agile or extreme project environments Register your book for access to the Capability Calculator, a Microsoft Excel tool created by the author and based on the Jensen II (Seer) model. Go to informit.com/title/9780133562675.

Innovative tools and techniques for the development and design of software systems are essential to the problem solving and planning of software solutions. Software Design and Development: Concepts, Methodologies, Tools, and Applications brings together the best practices of theory and implementation in the development of software systems. This reference source is essential for researchers, engineers, practitioners, and scholars seeking the latest knowledge on the techniques, applications, and methodologies for the design and development of software systems.

You've heard about pair programming's benefits: fewer bugs, improved skills, and faster delivery. But what happens when you want to pair with someone in another city, country, or even hemisphere? With the right tools, you won't have to relocate to refactor. In this book, you'll learn techniques used by the most productive remote programmers in the industry to pair with anyone on the globe on any kind of project. You'll use collaborative editors, screen sharing, secure networking, and virtualization to create a remote pairing environment that feels as if your partner is sitting right next to you.

Scrum ist ein sehr einfaches Framework für die agile Softwareentwicklung, dennoch ist es mitunter schwer einzuführen. Die Praxis hat gezeigt, dass Unternehmen, die Scrum in ihren Entwicklungsabteilungen umsetzen wollen, immer wieder vor denselben Herausforderungen stehen. Dieses Buch gibt zunächst eine ausreichend kurz gefasste Einführung und beschreibt das Wesen von Scrum, beschränkt auf den Kern. Basierend auf mehrjährigen Coaching- und Trainingserfahrungen gibt Andreas Wintersteiger eine Starthilfe, um einfach mal loslegen zu können. Dabei werden jene Gesichtspunkte nicht vernachlässigt, auf die es ankommt, um mit Scrum erfolgreich zu werden. Neben Hinweisen auf gute und etablierte Praktiken gibt das Buch auch Antworten auf häufig gestellte Fragen. Die kompakte Form wurde absichtlich gewählt, um auch mit wenig Zeitaufwand die relevanten Informationen für einen Start mit Scrum zu erfassen, zum Beispiel an einem Wochenende. Das Buch zeigt damit nicht die gesamte Welt von Scrum auf, sondern vermittelt, gemäß den agilen Prinzipien, den kleinsten gemeinsamen Nenner an Wissen und Hinweisen, um mit Scrum zu starten. Das erfolgreiche Buch liegt in der zweiten aktualisierten und erweiterten Auflage vor. Zielgruppe Dieses Büchlein ist für Personen gedacht, die sich über Scrum informieren möchten oder Scrum in der Organisation einführen wollen und hierfür eine kompakte Informationsquelle suchen. Es ist ebenso zur Vorbereitung auf ein Zertifizierungstraining, wie zum Beispiel den Certified Scrum Master geeignet.

There has never been a CMMI Guide like this. CMMI 44 Success Secrets is not about the ins and outs of CMMI. Instead, it answers the top 44 questions that we are asked and those we come across in our forums, consultancy and education programs. It tells you exactly how to deal with those questions, with tips that have never before been offered in print. Get the information you need--fast! This comprehensive guide offers a thorough view of key knowledge and detailed insight. This Guide introduces everything you want to know to be successful with CMMI. A quick look inside of the subjects covered: Understanding the Elements of CMMI Configuration Management, CMMI Project: Keys to Success of CMMI Implementation, The Basics of CMMI, The Basics of CMMI Appraisal, CMMI Processes - Achieving Goals and Best Practices, Area Specific CMMI: The Continuous Approach, How CMMI Process Areas are evaluated?, Features of CMMI Level 1 Organizations, The Advantage of Attending CMMI Conference, Ways to Conduct CMMI Assessments, CMMI Process Improvement - Maximize Resources and Eliminate Mistakes, CMMI Project Management System: Optimizing Corporate Project Management Models, SEI CMMI: Trailblazing the Way towards Technological Development, CMMI Assessment Key Indicators, The Old CMM and the New CMMI, How to Select an Appropriate CMMI Model, Two Most Common Approaches in CMMI Implementation, CMMI Staged Representation: Providing a Window for CMMI Implementation, CMMI vs ITIL: Knowing What to Choose, CMMI Certification: Do You Really Need It?, The Benefits of CMMI Software, CMMI Overview: A Quick Peek at CMMI, CMMI Online - Evaluating Process Improvement Models for Your Organization, Defining the Different CMMI Levels, Understanding CMMI framework, The Difference between the CMM and CMMI, Understanding the Steps Involved in CMMI SCAMPI, CMMI Consulting Firms: Providing Vital Help for Companies, Introduction to CMMI: Going Back to the Basics of CMMI, Some reasons why companies adopt CMMI, The Steps Involved In Using CMMI ITIL, CMMI Training: Improving the Skills of Management Professionals, Some important notes on CMMI Level 5, A more comprehensive approach to IT erudition: ITIL intermediate + CMMI, What is a CMMI level 3?, CMMI maturity level: define, The CMMI has been developed from several bodies of knowledge that targets the general improvement of, Understanding the difference between CMM and CMMI, Intro to CMMI: Why is Important to Understand the Basics of CMMI?, CMM vs CMMI: Understanding both ends, ISO CMMI Model: Creating a Synergy to Improve the Business Process, SEI-CMMI: Some standards, procedures, and policies accounted, and much more...

Software development and information systems design have a unique relationship, but are often discussed and studied independently. However, meticulous software development is vital for the success of an information system. Software Development Techniques for Constructive Information Systems Design focuses the aspects of information systems and software development as a merging process. This reference source pays special attention to the emerging research, trends, and experiences in this area which is bound to enhance the reader's understanding of the growing and ever-adapting field. Academics, researchers, students, and working professionals in this field will benefit from this publication's unique perspective.

Learn how to track bugs and issues, and manage your software development projects with JIRAKey FeaturesLearn how to set up JIRA for software developmentEffectively manage and handle software bugs and issuesIncludes updated JIRA content as well as coverage of the popular GreenHopper pluginBook DescriptionAtlassian's JIRA provides issue tracking and project tracking for software development teams to aid speed of development and quality of code. This book will show you how to develop software more efficiently by planning, designing, and customizing your own JIRA implementation.JIRA is a popular issue tracking product designed for better bug tracking, issue tracking, and project management. JIRA 5.2 Essentials provides a comprehensive guide covering everything you will need to plan, set up, design, customize, and manage your software development projects efficiently and to a professional standard.In this practical book you will learn how to design and implement JIRA for project and issue tracking. You will jump into the installation and design of JIRA before going through the required techniques to effectively manage issues that threaten your software development project.Each chapter builds on the last, taking you through important concepts and techniques such as business processes and workflows, setting up e-mail notifications, field and screen management, and reporting. Using these techniques you will be able to make JIRA adapt to your organization and save time and energy by developing software more efficiently.Newly improved and updated to JIRA 5.2 this book also includes a section about GreenHopper and Agile development with JIRA.What you will learnDesign and implement JIRA to work for you and your teamMaster JIRA issue and project tracking methodsMake your data tell a story through powerful data query and information retrievalGet to grips with GreenHopper, Bonfire, and Agile development with JIRASecure JIRA to protect your dataCapture and display data to users by using different types of fields in JIRAWho this book is forIf you want to get started with JIRA, then this book is made for you. Only basic computer skills and project or issue management knowledge is required. The book will provide the rest. This book would also be of interest to experienced JIRA users who wish to improve their workflow and master the new features of JIRA 5.2.

Summary Specification by Example is an emerging practice for creating software based on realistic examples, bridging the communication gap between business stakeholders and the dev teams building the software. In this book, author Gojko Adzic distills interviews with successful teams worldwide, sharing how they specify, develop, and deliver software, without defects, in short iterative delivery cycles. About the Technology Specification by Example is a collaborative method for specifying requirements and tests. Seven patterns, fully explored in this book, are key to making the method effective. The method has four main benefits: it produces living, reliable documentation; it defines expectations clearly and makes validation efficient; it reduces rework; and, above all, it assures delivery teams and business stakeholders that the software that's built is right for its purpose. About the Book This book distills from the experience of leading teams worldwide effective ways to specify, test, and deliver software in short, iterative delivery cycles. Case studies in this book range from small web startups to large financial institutions, working in many processes including XP, Scrum, and Kanban. This book is written for developers, testers, analysts, and business people working together to build great software. Purchase of the print book comes with an offer of a free PDF, ePub, and Kindle eBook from Manning. Also available is all code from the book. What's Inside Common process patterns How to avoid bad practices Fitting SBE in your process 50+ case studies =============================================== Table of Contents Part 1 Getting started Part 2 Key process patterns Part 3 Case studies Key benefits Key process patterns Living documentation Initiating the changes Deriving scope from goals Specifying collaboratively Illustrating using examples Refining the specification Automating validation without changing specifications Validating frequently Evolving a documentation system uSwitch RainStor Iowa Student Loan Sabre Airline Solutions ePlan Services Songkick Concluding thoughts

The surge of multicore processors coming into the market and on users'desktops has made parallel computing the focus of attention once again. This time, however, it is led by the industry, which ensures that multicore computing is here to stay. Nevertheless, there is still so much research work to be done in multicore hardware-software designs before consumer applications can leverage the benefits of this new paradigm. This e-book is being put forward as a platform for immediate collection of state-of-the-art technologies in both hardware and software designs for multicore computing. With the burgeoning prevalence of multicore processors in embedded systems, real-time systems, multimedia systems, bioinformatics systems, network systems, to list a few, this e-book attempts to cover the design and verification issues related to different application domains as a singular source of reference to the state-of-the-art techniques in multicore processor design and software programming that covers multiple application domains. This e-book will be of immense help to system and software engineers, including both experts and non-experts in parallel computing.

Building on their breakthrough bestsellers Lean Software Development and Implementing Lean Software Development, Mary and Tom Poppendieck's latest book shows software leaders and team members exactly how to drive high-value change throughout a software organization—and make it stick. They go far beyond generic implementation guidelines, demonstrating exactly how to make lean work in real projects, environments, and companies. The Poppendiecks organize this book around the crucial concept of frames, the unspoken mental constructs that shape our perspectives and control our behavior in ways we rarely notice. For software leaders and team members, some frames lead to long-term failure, while others offer a strong foundation for success. Drawing on decades of experience, the authors present twenty-four frames that offer a coherent, complete framework for leading lean software development. You'll discover powerful new ways to act as competency leader, product champion, improvement mentor, front-line leader, and even visionary. Systems thinking: focusing on customers, bringing predictability to demand, and revamping policies that cause inefficiency Technical excellence: implementing low-dependency architectures, TDD, and evolutionary development processes, and promoting deeper developer expertise Reliable delivery: managing your biggest risks more effectively, and optimizing both workflow and schedules Relentless improvement: seeing problems, solving problems, sharing the knowledge Great people: finding and growing professionals with purpose, passion, persistence, and pride Aligned leaders: getting your entire leadership team on the same page From the world's number one experts in Lean software development, Leading Lean Software Development will be indispensable to everyone who wants to transform the promise of lean into reality—in enterprise IT and software companies alike.

This instructive book takes you step by step through ways to track, merge, and manage both open source and commercial software projects with Mercurial, using Windows, Mac OS X, Linux, Solaris, and other systems. Mercurial is the easiest system to learn when it comes to distributed revision control. And it's a very flexible tool that's ideal whether you're a lone programmer working on a small project, or part of a huge team dealing with thousands of files.Mercurial permits a countless variety of development and collaboration methods, and this book offers several concrete suggestions to get you started. This guide will help you:Learn the basics of working with a repository, changesets, and revisionsMerge changes from separate repositoriesSet up Mercurial to work with files on a daily basis, including which ones to trackGet examples and tools for setting up various workflow modelsManage a project that's making progress on multiple fronts at onceFind and fix mistakes by isolating problem sourcesUse hooks to perform actions automatically in response to repository eventsCustomize the output of MercurialMercurial: The Definitive Guide maintains a strong focus on simplicity to help you learn Mercurial quickly and thoroughly.

'This remarkable book combines practical advice, ready-to-use techniques, anda deep understanding of why this is the right way to develop software. I haveseen software teams transformed by the ideas in this book.'--Mike Cohn, author of Agile Estimating and Planning'As a lean practitioner myself, I have loved and used their first book for years.When this second book came out, I was delighted that it was even better. If youare interested in how lean principles can be useful for software developmentorganizations, this is the book you are looking for. The Poppendiecks offer abeautiful blend of history, theory, and practice.'--Alan Shalloway, coauthor of Design Patterns Explained'I've enjoyed reading the book very much. I feel it might even be better than thefirst lean book by Tom and Mary, while that one was already exceptionallygood! Mary especially has a lot of knowledge related to lean techniques inproduct development and manufacturing. It's rare that these techniques areactually translated to software. This is something no other book does well(except their first book).'--Bas Vodde'The new book by Mary and Tom Poppendieck provides a well-written andcomprehensive introduction to lean principles and selected practices for softwaremanagers and engineers. It illustrates the application of the values andpractices with well-suited success stories. I enjoyed reading it.'--Roman Pichler'In Implementing Lean Software Development, the Poppendiecks explore moredeeply the themes they introduced in Lean Software Development. They beginwith a compelling history of lean thinking, then move to key areas such asvalue, waste, and people. Each chapter includes exercises to help you apply keypoints. If you want a better understanding of how lean ideas can work withsoftware, this book is for you.'--Bill Wake, independent consultant In 2003, Mary and Tom Poppendieck's Lean Software Development introduced breakthrough development techniques that leverage Lean principles to deliver unprecedented agility and value. Now their widely anticipated sequel and companion guide shows exactly how to implement Lean software development, hands-on. This new book draws on the Poppendiecks'unparalleled experience helping development organizations optimize the entire software value stream. You'll discover the right questions to ask, the key issues to focus on, and techniques proven to work. The authors present case studies from leading-edge software organizations, and offer practical exercises for jumpstarting your own Lean initiatives. Managing to extend, nourish, and leverage agile practices Building true development teams, not just groups Driving quality through rapid feedback and detailed discipline Making decisions Just-in-Time, but no later Delivering fast: How PatientKeeper delivers 45 rock-solid releases per year Making tradeoffs that really satisfy customers Implementing Lean Software Development is indispensable to anyone who wants more effective development processes--managers, project leaders, senior developers, and architects in enterprise IT and software companies alike.