10 years agoScene 1 / 15
At the time, the technology was enough.
The company built a system where customers and employees handle their work in one web service.
Customers submit the documents needed, and staff download them to do the work. When the work is done, the results are registered in the web service.
Most files customers submitted then were tens to hundreds of MB.
Customers' environments were fairly limited, too.
ORIGINAL SERVICE ENVIRONMENT
Enterprise service portal
Original releaseSubmit supporting documents
technical_report.zipBrowse...
File size: 128 MB
Maximum file size: 2 GB
Upload document- Customer accounts
- 1,200
- Typical file size
- 10–200 MB
- File transfer screens
- 4
The development team built the file transfer feature to the company's requirements.
The service ran reliably, and the company kept adding new work to it.
And so ten years passed.
SERVICE STATUSNow
10 years ago
Customer serviceOriginal file transfer
Share of new transfers
0%
INNORIX
Existing technology 100%
- Team's current work
- Launching the first service
Next—
Next story, TodayDeciding to replace →TodayScene 2 / 15
Customers and their work have changed, but the file transfer technology has not.
Over ten years the company's customer base grew a great deal.
The operating systems and browsers people use to reach the service became far more varied.
What customers submit grew from ordinary documents to design data, video, backups and raw data for analysis.
The development team starts receiving inquiries it never had before.
Development requests
Recent customer feedbackCustomer supportToday, 09:20
A customer says they cannot submit files from a new browser.
Enterprise salesYesterday, 14:30
An enterprise customer asked whether they can submit design data of 80 GB or more.
Security team3 days ago
The components and support status of the existing file transfer module need review.
Service planningLast week
Can the new project management service use the existing file transfer feature too?
Development teamLast week
It is hard to tell how a change to the file transfer module affects other business screens.
One way is to keep patching the existing technology for each problem.
But every new environment then needs more development, and every change has to be checked against the other work already running.
Rather than fixing each problem on its own, the company decides to look at replacing the file transfer technology itself.
What the development team has to solve
Keeping existing work running matters more than building new features.
- Customers' workExisting customers must keep using their accounts and their work.
- Existing materialsTen years of materials and their download permissions must stay.
- Business systemsExisting approval, review, analysis and data handling must keep working.
- Service operationThe replacement must affect customers as little as possible.
SERVICE STATUSNow
Today
Customer serviceRunning as is
Share of new transfers
0%
INNORIX
Existing technology 100%
- Team's current work
- Planning the replacement
NextSurvey the existing environment
Next story, Week 1Surveying the existing system →Week 1Scene 3 / 15
Find out where the file transfer technology is used.
The team surveys 24 screens and 8 business systems.
At first the development team thought replacing a few upload screens would be enough.
But the survey found the same file transfer technology in employee business systems, partner services and the archive lookup system as well as the customer web service.
Some systems were built to start the next task automatically when a transfer completed.
On some screens the transfer result changed the customer's work status; on others, a security check starts once the file has arrived.
EXISTING SERVICE INVENTORY
File transfer dependencies
- File transfer screens
- 24
- Related business systems
- 8
- Registered customer accounts
- 38,000
| Service | Screens | Transfer dependency |
|---|
| Customer portal | 5 | Submit materials and download results |
| Project workspace | 4 | Register project materials |
| Document management | 3 | Register and look up documents |
| Employee workspace | 4 | Receive work files and register results |
| Partner portal | 3 | Exchange files with partners |
| Approval system | 2 | Review and approval materials |
| Document archive | 2 | Download past materials |
| Support portal | 1 | Submit support materials |
The team studies how each screen selects files, which transfer server it uses, user authentication, storage location, completion events and error handling.
It is not only looking for the code that calls the file transfer feature, but for which business work the transfer technology is tied to.
DEPENDENCY DETAIL
Customer portal / Submit materials
- AuthenticationExisting customer session
- DestinationCustomer project storage
- Access permissionProject membership
- On transfer completedRegister submitted documents
- On transfer failedKeep request in pending state
- Post-transfer processingSecurity inspection
- Audit recordsEnterprise request history
After the survey, the team sees that the work it must keep is far wider than the technology it must replace.
SERVICE STATUSNow
Week 1
Customer serviceRunning as is
Share of new transfers
0%
INNORIX
Existing technology 100%
- Team's current work
- Dependency analysis
- Changes for customers
- None
NextSettle the scope
Next story, Week 2Designing the scope →Week 2Scene 4 / 15
Draw a clear line between what stays and what is replaced.
The development team decided not to rebuild the whole web service.
Existing user accounts, project data, data management and business processes stay in use.
What gets replaced is the technology that selects and delivers files, and the part that connects it to existing business systems.
REPLACEMENT SCOPE
The existing service stays; the file transfer technology is replaced.
BEFORE
- Customer authentication
- Project management
- Business information
- Existing access policies
- File transfer componentLegacy file transferExisting integration layer
- Business processing
- Document repository
- Existing customer records
AFTER
- Customer authentication
- Project management
- Business information
- Existing access policies
- File transfer componentINNORIXUpdated integration layer
- Business processing
- Document repository
- Existing customer records
A conceptual view of what the existing service must keep and what is replaced.
Here the team focuses less on removing the old technology than on whether the new one produces the same business results as the existing service.
For example, when a customer submits materials, they must be registered to the same project as before.
When a transfer fails, the existing work status must not change by mistake.
Nor may the change let users download materials they are not allowed to.
SERVICE STATUSNow
Week 2
Customer serviceRunning as is
Share of new transfers
0%
INNORIX
Existing technology 100%
- Team's current work
- Integration design
NextDevelopment integration
Next story, Week 3Integrating the first screen →Week 3Scene 5 / 15
The first file is transferred in the existing web service.
The new file transfer technology goes into the existing web service.
The team chose the most used screen, the customer material submission, as the first to replace.
It does not build a new web service; it applies INNORIX in the existing service's development environment.
The business screen and the way customers enter information stay as they are.
DEVELOPMENT ENVIRONMENT
The same business screen, a new file transfer technology
Existing component
Submit materials
Project #48291
Document category
Engineering dataDescription
Updated engineering materialsAttachmentsBrowse...
No file selectedMaximum file size: 2 GB
Submit materialsINNORIX integration
Submit materials
Project #48291
Document category
Engineering dataDescription
Updated engineering materialsAttachmentsAdd files
engineering_data.zip
File size 12.8 GB
Transfer completed
Submit materialsThe new file transfer technology can now be used in the existing web service.
But the team does not call the replacement done at this stage.
A file arriving correctly and the company's existing work being processed correctly are two different questions.
FIRST INTEGRATION TEST
- Test file
- 12.8 GB
- File transfer
- Completed
- Business integration
- Under verification
SERVICE STATUSNow
Week 3
Customer serviceRunning as is
Share of new transfers
0%
INNORIX
Existing technology 100%
- Team's current work
- Validating in development
NextConnect business events
Next story, Week 4Connecting business systems →Week 4Scene 6 / 15
How will existing business systems understand the new technology?
The team checks that existing work carries on correctly.
In the existing service, when a transfer completes, a business program was built to use the result to register the project materials.
The team writes integration code so the existing business systems can process the new technology’s transfer results.
Rather than changing every business system the company uses, it keeps the existing business call rules wherever it can.
BUSINESS INTEGRATION
The transfer technology changes; the meaning of existing work does not.
EXISTING BUSINESS CONTRACT
Transfer completed
- Project ID
- Customer ID
- Transferred files
- Storage reference
- Transfer result
Register project materials
UPDATED INTEGRATION
INNORIX transfer result
- Request context
- File information
- Destination information
- Completion status
- Error information
Convert to existing business contract
BUSINESS VERIFICATION
- Link customer account and filesVerified
- Register existing project materialsVerified
- Start security inspectionVerified
- Notify the person in chargeVerified
- Change the customer's work statusVerified
- Record transfer and business resultsVerified
What existing systems expect may differ from what the new technology returns.
The team builds an integration layer to handle those differences and verifies how transfer results affect existing work.
The team does not test only the success cases.
| Test condition | Expected business behavior | Result |
|---|
| All files transferred | Project materials registered | Passed |
| Some files failed | Work completion held | Passed |
| Network connection lost | Transfer status checked and recovered | Passed |
| User cancels transfer | Existing work status kept | Passed |
| Same completion processed again | Duplicate registration prevented | Passed |
| User session expired | Authentication and follow-up per policy | Passed |
| Storage error | Material registration held | Passed |
In particular, the team verifies the existing business logic so that work never starts wrongly when a completion is processed twice or only some files arrive.
SERVICE STATUSNow
Week 4
Customer serviceRunning as is
Share of new transfers
0%
INNORIX
Existing technology 100%
- Team's current work
- Integration testing
NextCompatibility validation
Next story, Week 5Validating data and environments →Week 5Scene 7 / 15
Files submitted ten years ago must still download.
Past materials and today's customer environments are checked.
The team has finished testing transfers of new files.
But the company's customers do not use only new materials.
They reopen materials from projects finished years ago, or download results delivered in the past.
Existing materials must stay usable after the replacement.
Document archive
Compatibility testingTen years of materials
| Created | File | Size | Download test |
|---|
| 10 years ago | original_documents.zip | 128 MB | Verified |
| 8 years ago | project_report.pdf | 42 MB | Verified |
| 6 years ago | reference_materials.zip | 840 MB | Verified |
| 3 years ago | engineering_archive.zip | 1.8 GB | Verified |
| Last month | project_update.zip | 1.4 GB | Verified |
| Today | new_engineering_data.tar | 12.8 GB | Verified |
HISTORICAL DATA VERIFICATION
- Actual storage location of existing filesChecked
- File names and formats of existing materialsChecked
- Download permission per materialChecked
- Existing encryption and compression formatsChecked
- Links between past projects and materialsChecked
If existing materials can be read as they are from the current storage, there is no need to move every file to new storage.
But if a storage format or encryption can only be used by the old technology, a separate conversion and compatibility plan is needed.
The team checks the structure of the real materials before deciding how to keep them.
Customers' environments are validated too.
CLIENT ENVIRONMENT VALIDATION
| Operating system | Browser | Upload | Download |
|---|
| Windows | Chrome | Verified | Verified |
| Windows | Edge | Verified | Verified |
| macOS | Safari | Verified | Verified |
| macOS | Chrome | Verified | Verified |
A fictional operating environment this company validates in its project. The test targets are set to the actual support scope.
The team also checks security software, network policies and installation restrictions at enterprise customers, and whether the new technology can coexist with existing modules.
This is to make sure no customer loses access to the service during the replacement.
SERVICE STATUSNow
Week 5
Customer serviceRunning as is
Share of new transfers
0%
INNORIX
Existing technology 100%
- Team's current work
- Preparing the launch
- Changes for customers
- None
NextLimited rollout
Next story, Week 6Applying to some customers →