Welcome

TECHNEST / Blog

Offshore performance requirements: start with peak business workload

Turn “the system must be fast” into business scenarios, measurable conditions and clear responsibilities shared by Japanese clients and offshore development teams.

When commissioning offshore software development, clarify “the system must be fast” early. For SIers, CTOs and PMs in Japan, the discussion should start with the business: at the busiest time, who is doing what, and which tasks must finish by a deadline? A specific scenario provides a basis for discussing design, cost and acceptance.

1. Describe the busiest day through real tasks

Choose a moment that matters to the business: month-end closing, the morning order rush or consolidating data from multiple branches. Record user roles, concurrent activities, data volumes and completion deadlines. Distinguish registered accounts from the number of people actively using the system at the same time.

IPA’s material on Non-Functional Requirements Grades includes business workload, expected growth and normal or peak operating conditions under performance and scalability.[1]

2. Define targets together with measurement conditions

For each priority workflow, write a short description of the operation being measured, where timing starts and ends, concurrent load, data volume, environment and acceptance threshold. If acceptance depends on the proportion of requests meeting a time target, specify that proportion and the observation period as well.

Avoid grouping screen display, completion of data saving and report generation under a single word: “fast.” For background processing, agree on a completion deadline and how users will find out the result.

3. Hypothetical example: reporting during month-end closing

Suppose a company wants staff to keep entering orders while its accounting department generates month-end reports. This is an illustrative scenario, not a TECHNEST project result.

Rather than checking each function separately, both parties agree on a scenario that runs them concurrently, using representative data authorized for this purpose. Define a response target for order entry and a completion deadline for the report. Where actual usage figures are unavailable, record the assumption, the person responsible for confirming it and the date for obtaining the missing information. Do not treat an assumption as a verified commitment.

4. Align responsibilities and costs before choosing an approach

The client confirms peak periods, business priorities and the impact of delays. The development team proposes measurement methods, prepares testing and explains technical options. Infrastructure or external-service owners should confirm conditions within their respective areas of responsibility.

Before selecting an approach, compare development effort, the test environment and expected operating costs. Any proposal to adjust a target should explain the business impact so that an authorized decision-maker can assess it.

5. Share results with the limits of verification

A report should include the software version, configuration, data, load conditions and results for each acceptance criterion. Identify differences from the production environment and anything not yet verified. When branch numbers or data volumes change, include a review of the scenario in the next development plan.

Clarify requirements from the business with TECHNEST

TECHNEST brings years of experience working with the Japanese market in business-system design and development and legacy modernization. Start with one important workflow and a description of your busiest day. Explore our software outsourcing services or contact TECHNEST to discuss a suitable scope and verification approach.

Reference

[1] IPA, Lecture on Non-Functional Requirements Grades (Japanese), March 4, 2019, section 2-4, page 18. A reference for classifying requirements; project-specific criteria require agreement between the parties.