Loading...Posted date
Updated date
Nablarch System Development Guide
Table of contents
- Preface
- Purpose of this guide
- Who should read this guide?
- Notes on reading
- Overall picture
- Project plan
- Requirements definition phase
- Requirement definition
- Architecture design
- Checking the project deliverables
- Test plan
- Creating a development guide for a project
- Design phase
- Standardization
- Programming and Unit testing phase
- Initial build of Nablarch project
- Setting up the team development environment
- Preparation of setup guide for development environment
- Establishment of development standards
- Integration test phase
- Preparation for integration test (communication confirmation)
- Nablarch Pattern Collection
- Nablarch Batch Processing Pattern
- Classification by startup method
- Classification by input/output
- Important points
- Asynchronous Operation in Nablarch
- To sending emails
- Nablarch Anti-pattern
- Web Application
- Nablarch Batch
- Jakarta Batch-compliant Batch
- Customization of UI Standards
- UI standard (screen)
- UI standard (screen) separate volume_UI parts catalog
- Examination of Test Items
- Collecting test viewpoints
- Extraction of test viewpoint
- Nablarch Environment Construction
- Generating projects from archetypes
- Component settings
- Introduction of static analysis tool
- Java Style Guide
- Setting Up the Team Development Environment
- Preparation of Setup Guide for Development Environment
- xxx Project development environment construction guide
- Prerequisites
- Development environment construction procedure
- Package Configuration Study
- Concept of package configuration
- Example of division by business function
- Example of division by class role
Java Style Guide
This section describes the coding conventions, code formatters and static inspection guides to help you code using Java. Use these resources to prevent bugs and write code of high quality.
Refer to the Java coding conventions to write better code.
The Java coding conventions assumes that what can be checked automatically with a code formatter or static inspection has been implemented in advance.
Format it with the code formatter. A code formatter that can be used immediately is provided.
Resolve any code violations that can be detected automatically with Checkstyle.
Exclude code that can clearly cause problems with SpotBugs or that is likely to cause problems later.
Limit the APIs used by the unauthorized API check tool as needed.
Resolve any architectural violations that can be detected by ArchUnit’s tests.
