Targets of Standardization
This section describes the naming rules for application development. The naming rules include the following items.
1. Online Application
| Classification | Description |
|---|---|
Application |
A collection of programs for processing user requests, consisting of SQL written for data access and processing, classes for implementing business logic, and configuration files. |
Service |
A group of operations for processing user requests invoked externally from user screens, external systems, etc. |
Operation |
Refers to a method of a Service. The In and Out types of a Service operation must be IO. |
Bean |
A reusable Java class that implements business logic, composed of multiple methods. |
DBIO |
A development resource written for data access, consisting of a Java class and an SQL Mapper (.dbio) file. |
SQL ID |
An identifier that represents a query generated in DBIO. It becomes the method name of the DBIO interface. |
IO |
A framework standard data transfer object that provides the capability to be converted into message forms (Serialized Object, fixed-length data, XML). It is used for operation request/response, internal/external interfaces, business rule invocation, etc. |
General class |
A pure Java class that users can write freely. |
Service Test case |
A Service test case file that can test a Service. |
2. Batch Application
| Classification | Description |
|---|---|
Application |
A collection of programs for batch jobs, consisting of batch job configuration files, SQL written for data access and processing, and classes for implementing business logic. |
Job |
The execution and re-execution unit of a batch job, composed of a flow for processing batch tasks and written as an XML configuration that defines the flow. |
Step |
The minimum unit of business implementation that composes a Job. |
Job Configuration Configuration file |
A file that sets the options and execution order of Jobs and Steps. |