A peek at my setup…
A great speech from Cesar De La Torre LIorente. Simply well put and provides important insights into microservice architectural approach. https://channel9.msdn.com/Events/Build/2017/T6051 https://channel9.msdn.com/events/Ignite/Microsoft-Ignite-Orlando-2017/BRK3317?term=Microservice%20architecture%20
In this study we concern to structural testing methods, especially which are related to Decision Coverage (DC), and Modified Condition / Decision Coverage (MCDC). These coverage metrics are discussed in the next chapter. We analyze several projects – written in Ada programming language – in subprogram level, and estimate how many test cases are needed to satisfy the 100% of DC and MCDC coverage. At last we answer to the question: how many test cases need more to satisfy MCDC then DC. In the second chapter we describe the most frequently used coverage metrics. In the third chapter we give a detailed description about how we analyzed the source codes of projects. Then we discuss the results of our analysis in the fourth chapter. And the summary and the conclusion comes in the fifth chapter. TestCasesForDecisionCoverageAndMCDC http://people.inf.elte.hu/lupin/dc_mcdc_study.pdf
Enterprises are increasingly realizing cost savings, solving deployment problems, and improving DevOps and production operations by using containers. Microsoft has been releasing container innovations for Windows and Linux by creating products like Azure Container Service and Azure Service Fabric, and by partnering with industry leaders like Docker, Mesosphere, and Kubernetes. These products deliver container solutions that help companies build and deploy applications at cloud speed and scale, whatever their choice of platform or tools. https://aka.ms/microservicesebook
Eric Evans has written a fantastic book on how you can make the design of your software match your mental model of the problem domain you are addressing. “His book is very compatible with XP. It is not about drawing pictures of a domain; it is about how you think of it, the language you use to talk about it, and how you organize your software to reflect your improving understanding of it. Eric thinks that learning about your problem domain is as likely to happen at the end of…
Getting software released to users is often a painful, risky, and time-consuming process. This groundbreaking new book sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers, and operations, delivery teams can get changes released in a matter of hours— sometimes even minutes–no matter what the size of a project or the complexity of its code base. Jez Humble and David Farley begin by…
Testing of software intended for safety-critical applications in commercial transport aircraft must achieve modified condition/decision coverage (MC/DC) of the software structure. This requirement causes anxiety for many within the aviation software community. Results of a survey of the aviation software industry indicate that many developers believe that meeting the MC/DC requirement is difficult, and the cost is exorbitant. Some of the difficulties stem, no doubt, from the scant information available on the subject. This paper provides a practical 5-step approach for assessing MC/DC for aviation software products, and an analysis…
In this completely revised introduction to Extreme Programming (XP), Kent Beck describes how to improve your software development by integrating these highly desirable concepts into your daily development process. The first edition of Extreme Programming Explained is a classic. It won awards for its then-radical ideas for improving small-team development, such as having developers write automated tests for their own code and having the whole team plan weekly. Much has changed in five years. This completely rewritten second edition expands the scope of XP to teams of any size by suggesting a…
Use cases provide a beneficial means of project planning because they clearly show how people will ultimately use the system being designed. This guide provides software developers with a nuts-and-bolts tutorial for writing use cases. It covers introductory, intermediate, and advanced concepts, and is suitable for all knowledge levels. https://www.amazon.com/Writing-Effective-Cases-Alistair-Cockburn/dp/0201702258
As the application of object technology–particularly the Java programming language–has become commonplace, a new problem has emerged to confront the software development community. Significant numbers of poorly designed programs have been created by less-experienced developers, resulting in applications that are inefficient and hard to maintain and extend. Increasingly, software system professionals are discovering just how difficult it is to work with these inherited, non-optimal applications. For several years, expert-level object programmers have employed a growing collection of techniques to improve the structural integrity and performance of such existing software programs.…
Even bad code can function. But if code isn’t clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn’t have to be that way. Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship . Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code “on the fly” into a book that will instill within you the…