A Component-Based Multi-Tier Web Architecture for Enhancing ERP System Development Efficiency and Maintainability
This paper proposes and validates a component-based multi-tier web architecture that integrates object-oriented design and event-driven programming to significantly enhance ERP system development efficiency, maintainability, and scalability, demonstrating a 44% reduction in development effort through a practical case study.
Original paper licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are trying to build a massive, intricate city. In the old days, every time you wanted to add a new bakery or a fire station, you had to pour fresh concrete, lay new bricks, and wire new electricity from scratch, right next to the existing buildings. If the city grew too big, the roads would clog, the power grid would overload, and if you needed to fix a leak in the bakery's plumbing, you might accidentally knock down the fire station next door. This is how many early computer systems for big companies were built: everything was glued together in a messy, tangled knot.
But what if, instead of building from scratch every time, you had a set of magical, pre-made LEGO bricks? These bricks are smart. They know how to connect to each other, they have standard plugs for power and water, and you can snap them together in seconds to build a bakery, a school, or a hospital. If you need to change the bakery's menu, you just swap out one specific brick without touching the rest of the city. This is the world of "Component-Based Software Engineering." It's about building software out of reusable, standardized blocks rather than writing a unique script for every single button and screen. When you combine this with a "Multi-Tier" approach—where the front door (what you see), the kitchen (where the cooking happens), and the pantry (where the food is stored) are in separate rooms—you get a system that is faster, easier to fix, and much harder to break. This is exactly the kind of problem that businesses face when they try to run their entire operations on a single, clunky computer system.
The researchers in this paper, a team from universities in China, decided to test if this "LEGO brick" approach could save time and money when building Enterprise Resource Planning (ERP) systems. ERP systems are the giant digital brains of companies, handling everything from buying supplies and managing inventory to paying employees and tracking sales. Traditionally, building these systems is a slow, expensive nightmare where developers often have to rewrite the same code over and over. The team proposed a new architecture that mixes these reusable software components with a "three-tier" structure and an "event-driven" style. Think of "event-driven" like a waiter in a restaurant: the waiter doesn't constantly check on every table; instead, they wait for a specific signal (an "event"), like a customer raising a hand, before taking action. This keeps the kitchen from getting overwhelmed.
To see if their idea worked, the team didn't just guess; they built a real-life test case. They created a module for managing orders in a company, using their new "smart brick" system, and compared it against the old, traditional way of building the same thing. The results were surprisingly clear. By using their component-based framework, the team found that they could cut the time it took to build the software by about 41.5%. In terms of money, the cost dropped by roughly 45.2%. Instead of taking 3,750 days of work from a team of developers, the new method only required about 2,195 days. That is a massive saving of over 1,500 days of labor.
The benefits didn't stop at just building it faster. The new system was also much easier to maintain. In the old way, fixing a small bug or changing a rule often meant tearing apart large chunks of code, which was risky and expensive. With the new approach, because the pieces were separated and standardized, fixing a problem was like swapping out a single LEGO brick. The study showed that the cost of keeping the system running dropped dramatically, and the system could handle more people using it at the same time without slowing down. When they tested it with up to 200 users at once, the new system responded in just 2.2 seconds, while the old system took a sluggish 7.8 seconds.
The researchers are confident in these numbers because they ran the test in a real-world setting with actual developers and real business data, not just in a computer simulation. They used statistical tools to prove that the improvements weren't just luck; the difference was significant. However, they are careful to note that this was tested on a specific type of software (an order-management module) within one company's consulting environment. While the results are very promising, they suggest that more testing in different industries would be needed to say for sure that this works everywhere.
In short, this paper suggests that by treating software like a set of reusable, interchangeable parts rather than a unique sculpture for every project, companies can build their digital systems much faster, spend less money, and keep them running smoothly for years. It's a shift from "building everything by hand" to "snapping together a smarter future," and for the businesses that adopt it, the difference looks like a massive leap forward in efficiency.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.