concept case in category software development

This is an excerpt from Manning's book The Mikado Method.
The graph is helpful if you need to practice and rehearse a refactoring, over and over, until it can be smoothly executed. This can be especially useful when you’re up against a change that has a lot of steps that all need to be done to make sense before checking in. An example would be moving from one version of a framework to another, or some other case where the undo phase is time consuming or expensive. There are cases where the last critical steps that actually do the job or switch can be harmful if the timing isn’t right. In cases like that, you can benefit a lot from rehearsing the steps and using the graph to reflect on the work ahead to maximize the odds of success.
In this appendix, you’ve seen how you can drive small changes to code with tests. This is useful in cases where you need to loosen a system enough to get it under test, and then modify it even more. This is particularly important in situations where you can’t rely on a compiler. The Mikado Method is about taking risky changes and transforming them into boring ones by breaking them down into safe steps. Getting to a safe step in JavaScript, as an example, differs slightly from similar changes in statically typed languages.

This is an excerpt from Manning's book Specification by Example: How Successful Teams Deliver the Right Software.
The key process patterns of Specification by Example are introduced in the next chapter. In this chapter, I’ll explain the benefits of Specification by Example. I’ll do so using Specification by Example style; instead of building a case for this book in a theoretical introduction, I’ll present 18 real-world examples of teams that got big dividends from Specification by Example.
When a team has a good understanding of TDD, making the case for executable specifications is easy: Explain them as tests for business functionality.

This is an excerpt from Manning's book Event Processing in Action.
Example 6: An emergency control system informs and directs first responders and people at risk in case of an incident (for example, a fire or the leakage of hazardous materials). In this case the event is a report on an incident, and the main focus of the system is the dissemination of information: who should be informed about what and at what time, given the nature of the incident.
This pattern detection process is looking for cases where a driver fails to make a pickup on time. The Pattern detect EPA (in this case the Pickup alert agent) generates a Pickup Alert derived event when the Pickup interval window terminates and no Pickup Confirmation event has been detected. The Pickup interval terminates 5 minutes after the required pickup time; let’s suppose that that is at 12:05. You will recall from chapter 8 that the detection time of the derived event is set to the latest possible time within the context interval, which in this case is 12:04. The question again is, what value should be set as the occurrence time of the Pickup alert derived event? Let’s examine the three policies discussed in the previous example to determine whether they make sense:
In most cases you might assume that an event in the computer domain (either a raw event detected by an event processing system, or a derived event produced by an event processing system) is exactly what you should use to trigger the reaction; however, in reality this might not be so. Consider the case in which an event processing system generates a derived event signaling that a network denial of service (DoS) attack has occurred. In this case the network DoS attack event is the situation we are looking for, because it obviously requires a reaction. However, the computational process that created this derived event is not an exact science, and can have two phenomena associated with it: false positive and false negative situation detection.

This is an excerpt from Manning's book Becoming Agile ...in an imperfect world.
The second website is focused on classified advertising for the local metropolitan area. The classifieds are for real estate, autos, and merchandise. The case study’s pilot project will deliver an application for the classifieds site.
In cases where the customer wasn’t available at all, we debriefed them before the session and had someone on our team named as a proxy in advance of the meeting.