Technology Stack

Backend Based on Spring Boot

Spring Boot streamlines application development by leveraging the Spring framework with a convention-over-configuration approach. It supplies sensible defaults so developers can prioritize core functionality over boilerplate configuration. Automatic setup detects project dependencies and applies appropriate settings with out manual XML or annotation-heavy files. Builds rely on Maven or Gradle for dependency resolution and task automation. Developers often start from Spring Initializr to scaffold projects and select required modules. This reduces operational friction and accelerates delivery cycles.

Frontend Powered by Vue.js

Vue.js emphasizes simplicity and approachability for building reactive interfaces. Its declarative rendering model and component-based architecture enable clear separation of concerns. Two-way data binding via directives like v-model keeps view and state synchronized automatically, eliminating tedious DOM manipulations. Lifecycle hooks give grenular control during component creation, mounting, updating, and destruction phases, facilitating advanced behaviors with minimal effort.

Feasibility Considerations

Assessing viability ensures alignment between system goals and practical constraints. Technical feasibility is confirmed through mature Java ecosystem support and tooling. Economic viability weighs projected benefits—such as reduced manual processing and improved asset tracking—against development and maintenance costs. Operational feasibility focuses on intuitive workflows for end users, ensuring adoption without steep learning curves. The system targets reduction of administrative overhead while enhancing accuracy and accessibility of cultural artifact records.

System Testing Strategy

Testing validates functional integrity and user experience across scenarios. The primary aim is early detection of defects to align delivered behavior with specifications. Functional verification employs black-box techniques: boundary value checks, mandatory field validation, and role-based access tests. Each test case defines input, expected outcome, observed result, and analysis.

Sample Login Tests

Input Data	Expected Outcome	Observed Result	Analysis
User: curator Pass: pwd123 Captcha: correct	Access granted	Granted	Matches expectation
User: curator Pass: wrong Captcha: correct	Authentication failure	Failure message shown	Matches expectation
User: curator Pass: pwd123 Captcha: incorrect	Captcha error	Error displayed	Matches expectation
User: (empty) Pass: pwd123 Captcha: correct	Username required	Prompt shown	Matches expectation
User: curator Pass: (empty) Captcha: correct	Password required	Prompt shown	Matches expectation

Sample User Management Tests

Input Data	Expected Outcome	Observed Result	Analysis
Complete user form	Record added and visible in list	Present in list	Matches expectation
Modify existing record	Updates reflected instantly	Changes visible	Matches expectation
Select delete action	Confirmation then removal	Record absent after confirmation	Matches expectation
Omit username field	Validation blocks submission	Required field warning	Matches expectation
Reuse existing username	Duplicate prevention triggered	Duplicate warning shown	Matches expectation

Database Schema Design

CREATE TABLE heritage_item (
  item_id BIGINT AUTO_INCREMENT PRIMARY KEY,
  created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
  catalog_code VARCHAR(64),
  name VARCHAR(128),
  description TEXT,
  preservation_status VARCHAR(32),
  registered_by VARCHAR(64),
  contact_number VARCHAR(20)
);

CREATE TABLE patron (
  patron_id BIGINT AUTO_INCREMENT PRIMARY KEY,
  created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
  login_name VARCHAR(200) NOT NULL UNIQUE,
  secret_hash VARCHAR(200) NOT NULL,
  full_name VARCHAR(200),
  gender VARCHAR(10),
  avatar_path VARCHAR(200),
  phone VARCHAR(20),
  id_card VARCHAR(30)
);

CREATE TABLE feedback (
  note_id BIGINT AUTO_INCREMENT PRIMARY KEY,
  created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
  submitter_id BIGINT NOT NULL,
  submitter_name VARCHAR(200),
  message_body LONGTEXT NOT NULL,
  reply_text LONGTEXT
);

Example Code Implementation

@RestController
@RequestMapping("/api/util")
public class UtilityController {

    private final ConfigRepository configRepo;
    private final GeoService geoService;

    public UtilityController(ConfigRepository cfgRepo, GeoService gs) {
        this.configRepo = cfgRepo;
        this.geoService = gs;
    }

    @GetMapping("/locate")
    public ResponseEntity<?> resolveLocation(@RequestParam String longitude,
                                             @RequestParam String latitude) {
        String apiKey = configRepo.findByKey("baidu_map_key")
                                 .map(ConfigEntry::getValue)
                                 .orElseThrow(() -> new ResponseStatusException(HttpStatus.BAD_REQUEST, "Missing API key"));

        Map<String, String> cityData = geoService.fetchCity(apiKey, longitude, latitude);
        return ResponseEntity.ok(cityData);
    }

    @PostMapping("/compareFaces")
    public ResponseEntity<?> compareFacialImages(@RequestParam String firstImg,
                                                 @RequestParam String secondImg) {
        Path uploadRoot = Paths.get("static/upload").toAbsolutePath();
        Path imgPath1 = uploadRoot.resolve(firstImg);
        Path imgPath2 = uploadRoot.resolve(secondImg);

        if (!Files.exists(imgPath1) || !Files.exists(imgPath2)) {
            throw new ResponseStatusException(HttpStatus.NOT_FOUND, "Image not found");
        }

        byte[] bytes1 = readAllBytes(imgPath1);
        byte[] bytes2 = readAllBytes(imgPath2);
        String encoded1 = Base64.getEncoder().encodeToString(bytes1);
        String encoded2 = Base64.getEncoder().encodeToString(bytes2);

        MatchResult result = FaceRecognitionClient.compare(encoded1, encoded2);
        return ResponseEntity.ok(result);
    }
}

Supplementary SQL Scripts

INSERT INTO heritage_item (catalog_code, name, description, preservation_status, registered_by, contact_number)
VALUES ('CHN-001', 'Ancient Vase', 'Ming Dynasty ceramic piece', 'Stored', 'admin', '13800138000');

INSERT INTO patron (login_name, secret_hash, full_name, gender, phone)
VALUES ('researcher01', 'hashed_pwd', 'Li Wei', 'Male', '13900139000');