The benefits of design patterns in the design phase are well-established. We claim that patterns can --and should-- play equally important roles in later stages of the lifecycle. But to make this feasible, we need to develop suitable ways to precisely specify the requirements associated with the use of specific patterns, and runtime monitoring tools to identify any violations of these requirements. We summarize a specification and monitoring approach focused on pattern-centric behavior that we developed previously, evaluate alternative ways to monitor systems based on the formalism, and discuss the overall utility of the specification and monitoring approach in the context of a case study.