Quotes About Use Cases

The concepts in Marketing 5.0 are, thus, tools-agnostic. Companies can implement the methods with any supporting hardware and software available in the market. The key is that those companies must have marketers who understand how to design a strategy that applies the right technology for various marketing use cases.

We started with the customer and worked backward. We understood the service's use cases, identified its key aspects, and established and adjusted the SLA.

Which kinds of decisions are premature? Decisions that have nothing to do with the business requirements—the use cases—of the system.

Architecture should reveal operation. The architecture of the system should elevate the use cases, the features, and the required behaviors of the system to first-class entities that are visible landmarks for the developers. This simplifies the understanding of the system and, therefore, greatly aids in development and maintenance.

Why are Entities high level and use cases lower level? Because use cases are specific to a single application and, therefore, are closer to the inputs and outputs of that system. Entities are generalizations that can be used in many different applications, so they are farther from the inputs and outputs of the system. Use cases depend on Entities; Entities do not depend on use cases.

Jacobson makes the point that software architectures are structures that support the use cases of the system. Just as the plans for a house or a library scream about the use cases of those buildings, so should the architecture of a software application scream about the use cases of the application.

a good architecture must support: • The use cases and operation of the system. • The maintenance of the system. • The development of the system. • The deployment of the system.

A shopping cart application with a good architecture will look like a shopping cart application. The use cases of that system will be plainly visible within the structure of that system. Developers will not have to hunt for behaviors, because those behaviors will be first-class elements visible at the top level of the system.

USE CASES The software in the use cases layer contains application-specific business rules. It encapsulates and implements all of the use cases of the system. These use cases orchestrate the flow of data to and from the entities, and direct those entities to use their Critical Business Rules to achieve the goals of the use case.

Local commerce, without question, will be one of the fundamental use cases enabled by mobile devices over the next several years.

We don't know which use cases will ultimately be the most important for 5G, but we know that early adopters tend to get a sustainable advantage.

We need to come up with use cases for this technology that drive clear benefits for individuals and institutions - these are our customers. Too often we see bitcoin and blockchain technologies as solutions in search of a problem. We don't just need these systems to be technically better than the alternatives - we need them to be more user-friendly.