A BCE model for Sinsing interpretation of time series graphs

First, what is BCE?

The so-called BCE, which is boundary-control-entity Patterns, is usually a way for us to draw time series diagrams. the BCE model divides objects into three categories: boundary classes, control classes, and entity classes.

Second, BCE's object introduction

Boundary class: Used to isolate internal and external systems, usually responsible for receiving and responding to internal and external messages, participants and system objects for message passing through the boundary class to achieve.

Control class: A control class is generated using a regular session. Used to control complex operations or business logic during the execution of a use case.

Entity class: An object inside the system.

Thirdly, the similarities and differences between BCE and MVC

Basic rule: The control class generally has only one, the boundary class and the entity class can have multiple.

It's a bit like our MVC, though it's not the same thing. The boundary class here is a bit like a view, which acts as a V. The entity class here is a bit like a model, which is the role of M.

The four basic steps of the BCE model

(1) Identify participants and add use case control classes.

(2) The boundary class and the entity class are then constantly populated according to the use case process.

A BCE model for Sinsing interpretation of time series graphs