What Is Quality Management in System Development? Processes, Key Points, and Methodological Differences Explained

"I'm worried about quality control when proceeding with system development."

"I want to know the key points to watch out for in quality control."

This article is for those who have questions or concerns about quality in system development. We will cover the theme of quality control.

In the first half, we explain how quality control is conducted during the development process. We summarize the specific actions that both the ordering company and the development company should take.

In the second half, we’ll introduce key points to improve quality and how to choose a development partner that emphasizes quality control. Please use this as a reference to lead your project to success.

Akira Shimazoe

CEO of Solashi Japan LLC. Engaged in the development and operation of internal systems at Suntory. Founded Yper Inc., serving as CTO and CPO, contributing to product launch and growth.

What is Quality Control in System Development?

Quality control in system development refers to efforts to ensure the quality of the system being developed. This includes not only the system itself but also design documents, test cases, and development processes.

Quality control is extremely important in system development. Without proper quality control, there is a risk that the ideal system cannot be built or that various problems will arise.

Let’s begin by looking at the purpose of quality control and the main stages involved.

Purpose of Quality Control

The main purpose of quality control is to ensure that the deliverables meet the expectations of the client company and end-users. Other objectives include enhancing security, ensuring reliability, and optimizing performance.

In addition, high-quality deliverables make maintenance more efficient, offering the benefit of easier system upkeep.

Main Stages of Quality Control

The general process of system development is as follows. Quality control is performed at each stage to ensure the quality of the deliverables.

1. Requirement Definition
2. Specifications Definition
3. Design (Basic Design / Detailed Design)
4. Implementation
5. Testing (Unit Test, Integration Test, System Test, Acceptance Test)
   

In the requirement and specification definition phases, it's necessary to define all the system functionalities without any omissions.

In the design phase, in addition to ensuring that all necessary features are included, it is important to consider aspects such as security, privacy, and usability.

After that, implementation is carried out, and testing is done to confirm there are no quality issues.

During the actual development process, various risks may arise such as “missing necessary features” or “bugs occurring.”

It is essential to consider foreseeable risks at each stage in advance and to continuously manage and address them.

Quality Control Involving the Client Company

From here, we’ll explain specific quality control tasks at each phase, from both the perspectives of the client company and the development company. Let's first take a look at the quality control responsibilities of the client company.

• Requirement Definition
• Specifications Definition
• Basic Design
• Acceptance Testing

Of course, it's essential for the development company to implement the system with quality in mind, but just as important is the quality of the preceding phases—requirement definition, specifications definition, and design.

That’s why the client company also needs to take a proactive role in quality control.

Requirement Definition

Requirement definition is the process of clarifying what kind of system the client company wants to develop.

This is a crucial phase for conveying needs to the development company and is typically led by the development company.

From a quality control perspective, keep the following points in mind:

• Are there any missing requirements for the system?
• Are there any missing business requirements that the system must fulfill?
• Are there any ambiguous definitions?

Specifications Definition

In the specifications definition phase, you will identify and finalize the functions, performance, and security requirements the system must meet based on the requirement definition.

The finalized content is documented in a specifications definition document, which is shared across the entire project. Since this step is essential for developing the expected system, proceed with caution.

While specifications definition is generally the responsibility of the client company, if there is insufficient expertise, the task can be delegated to the development company.

However, complete delegation can lead to problems. Be sure to maintain communication with the development company and confirm that the requirement definitions are properly reflected.

Related article: What is System Development Requirement Definition? A Clear Explanation of the Process and Key Points

Basic Design

The basic design phase is the process of developing the basic system design based on the finalized specifications definition. Core functionalities and interfaces are defined, and system tests are also planned at this stage.

Although the design documents are prepared by the development company, it is important for the client company to verify that there are no issues. Once the process enters detailed design and implementation, the client company has limited influence.

To avoid misalignment in expectations, thoroughly review elements such as usability and security at this stage.

Acceptance Testing

System development testing is generally divided into the following four types:

• Unit Testing
• Integration Testing
• System Testing
• Acceptance Testing

Among these, "acceptance testing" is conducted before delivery and is carried out by the development company. Make sure to verify that the delivered system meets the requirement and specification definitions.

Other tests are mainly handled by the development company, but the quality of testing can vary depending on the vendor.

If testing is completed without confirming critical points, or if necessary test steps are skipped, bugs may be discovered later.

Ensure good communication with the development company by checking points such as “Are test cases reviewed to ensure test quality?” and “Is the number of testers appropriately allocated according to the development scale?”

Quality Control Conducted by the Development Company

Next, let’s take a look at the quality control performed by the system development company.

• Basic Design
• Detailed Design
• Implementation
• Unit Test, Integration Test, System Test

We will explain each of these stages one by one.

Basic Design

Based on the requirement definition, the overall structure of the system to be developed is documented in the basic design document.

The basic design document is used to describe the fundamental structure, functions, performance, security, etc., and to align understanding between the client and the development company.

At this stage, the project’s objectives, scope, schedule, risk management, and constraints are also designed.

The basic design directly affects the subsequent implementation phase. Therefore, it is important to balance feasibility with the client’s needs while considering the processes that follow detailed design.

Also, make sure that the basic design is consistent with the requirement definition.

Detailed Design

Detailed design is the phase where internal system structures are designed based on the basic design.

While the basic design outlines the overall direction of the project, the detailed design document serves as a set of instructions for the programmers who will do the actual implementation.

During detailed design, rules for standardizing development practices are established, and test plans for each testing stage are also prepared.

It’s important to check whether the design documents are readable and maintainable, and whether the test code is correct.

Implementation

Implementation is the process in which programmers write code based on the detailed design document.

In addition to checking for common issues such as bugs or omissions, code readability should also be evaluated.

Poorly readable source code can be difficult to interpret, especially for anyone other than the original author.

This increases the risk of bugs and can make future modifications more time-consuming.

Unit Test, Integration Test, System Test

Testing is used to identify bugs that may have been introduced during implementation and to ensure the system works as expected. The development company conducts the following three types of tests:

• Unit Test
• Integration Test
• System Test

Each of these will be explained below.

Unit Test

Unit testing is conducted when individual modules are completed. This is a low-complexity process focused on small components, making it easier to detect bugs.

Integration Test

Integration testing involves combining the individually tested modules to check how they interact and function together.

Even modules that passed unit tests may exhibit bugs or malfunction during integration testing.

This is a crucial step to ensure the project proceeds smoothly in later phases, so it is important to verify that the system behaves as intended.

System Testing

After the overall system is developed, the development company conducts this final testing phase for confirmation.

The goal is to verify whether the functionalities defined in the requirements specification are implemented, and whether the performance meets the expectations of the client company.

Differences in Quality Management Based on Development Methodologies

There are two main types of system development methodologies: "Waterfall Development" and "Agile Development".

This section compares and explains the characteristics of quality management in each approach.

Waterfall Development

In Waterfall development, the specifications are finalized first, and each development phase proceeds in a fixed sequential order.

While this makes quality control easier, a drawback is that if any defect occurs, you cannot proceed to the next step. Also, it is difficult to go back and make changes to the specifications or plans once the development has moved forward.

Agile Development

Agile development is a methodology where design, implementation, and testing are repeated in cycles, not for the entire system at once, but for each small functional unit.

With Agile development, it’s possible to evaluate the quality of each feature incrementally even during development. This allows for the release of a prototype followed by quality improvements and functional expansions.

Since feedback between the client and the development company is incorporated iteratively, frequent communication is crucial.

For more details, please see "What is Agile Development? Detailed Explanation of Its Advantages, Disadvantages, and How It Works".

6 Key Points for Quality Management in System Development

Here are six key points for managing quality in system development.

1. Evaluate using quantitative indicators
2. Clarify the criteria
3. Check for any missing requirements
4. Manage quality in each phase
5. Maintain regular communication
6. Ensure appropriate quality assurance

1. Evaluate Using Quantitative Indicators

When assessing the quality of each phase, it's important to use quantitative indicators.

Instead of vague evaluations, manage using specific metrics like "How many minutes were spent on reviews?" or "How many defects were identified?".

Using objective data makes it easier to share the project status with all members and clarify the goals and direction. Visualizing this data with graphs can also be helpful.

However, be aware that quantitative indicators alone do not guarantee quality. For example, a high number of bugs found does not necessarily mean all issues were detected.

Nonetheless, if the number of defects is extremely high or extremely low, it may indicate potential issues that need to be addressed. It is an effective way to detect signs of problems.

2. Clarify the Criteria

Another key point is to define the criteria that must be met according to the project conditions. Quality management in system development often involves evaluating intangible aspects.

By setting clear standards to be met, the expected quality level of the ordering company can be clearly shared, preventing discrepancies with the development company.

For example, in terms of security, you can set standards such as "only authorized personnel can access" or "logs can be tracked."

3. Confirm there are no missing requirements

To smoothly proceed with system development, it is important to cover all requirements. Avoiding omissions involves a solid process of requirement and specification definitions.

The requirement definition document must clearly document the requirements by categorizing them into functional and non-functional requirements. It is also essential to prioritize them according to their importance and impact.

4. Manage quality at each development phase

By managing quality at each development phase, it becomes possible to respond quickly to problems or bugs.

Even in later stages like design, where the development company takes the lead, collaboration from the ordering company is essential to detect issues early. Stay actively involved and regularly check the progress.

5. Communicate frequently

To ensure smooth project execution, communication with the development team is crucial. By building trust with the development company, you can expect more frequent and reliable progress updates and consultations.

Internal communication is also important. Especially during the requirement and specification definition phases, be sure to collaborate with departments that will actually use the system.

By listening to on-site feedback, you can fine-tune the direction of system development accordingly.

6. Understand if quality assurance is adequate

It’s also important to understand whether quality assurance is being properly conducted. Quality assurance refers to the process of verifying the actual quality of a developed system, identifying and fixing any issues or bugs.

Check whether the required standards are met, and if issues are found, ensure they are properly addressed and corrected.

How to Choose a Company for Smooth Quality Management

To ensure smooth quality management, focus on the following points when choosing a development company.

• Choose a development company with a well-established quality management system
• Outsource to a company that specializes solely in quality assurance tasks

Choose a development company with a well-established quality management system

Choose a development company with a comprehensive and organization-wide quality management system in place.

In system development, high quality can be achieved by regularly reviewing outputs from each phase and test.

Therefore, it is crucial that the organization has a structure to support the achievement of quality goals across all teams.

In general, a project manager is responsible for quality management in system development. Choosing a development company with skilled project managers is key.

At our company, Solashi Co., Ltd, we have multiple project managers with experience in launching new businesses and handling startup projects. Feel free to reach out for a consultation.

Outsource to a company that specializes solely in quality assurance tasks

If you’re handling system development in-house, it’s also an option to outsource just the quality assurance to professionals. By entrusting quality control to specialized companies, there’s a higher chance of early bug detection.

Additionally, incorporating an external perspective may help identify bugs that your internal team might overlook.

Although there are few companies that offer only quality assurance services, they are recommended if you want to manage quality more efficiently.

For High-Quality System Development, Contact Solashi

If you’re looking for high-quality system development, consider reaching out to the Vietnamese development company Solashi Co., Ltd. We provide smooth development at a high cost-performance ratio.

Our team includes many engineers with expertise in cutting-edge technologies such as blockchain and AI. We also support agile development that allows for prototyping, quality improvements, and function expansion.

Furthermore, our Japanese-speaking bridge SEs will support communication with local engineers, conveying detailed requests and instructions clearly. You can rest assured there will be no language-related misunderstandings.

If you’re looking for a development company with a strong quality management system, feel free to contact Solashi Co., Ltd.

Akira Shimazoe

Representative of Solashi Japan LLC. Born in April 1989 in Fukuoka Prefecture. Graduated from the Graduate School of Information and Mathematical Sciences at Osaka Prefecture University. Joined Suntory System Technology Co., Ltd., an IT subsidiary of Suntory Holdings, in 2014. Broadly responsible for the development, operation, and implementation of vending machine delivery management, efficiency improvements, and sales management systems. Founded Yper Inc. in 2017, serving as CTO and CPO. Contributed to the launch and growth of the app-linked delivery bag "OKIPPA." Selected for Toyo Keizai's prestigious "Amazing Venture 100" and Forbes' "Forbes 30 Under 30 Asia 2019."