Requirements can be reviewed
Form business goals, usage scenarios, roles and rules into confirmable requirements.
S08 / TECHNICAL CONSULTING & IMPLEMENTATION
Technical consultation
with custom implementation 。
Put the business requirements into
Make the system operational and acceptable.
Organize requirements sorting, architecture design, development access and testing online to connect business goals, technical work and acceptance delivery.
Start with existing systems and business goals to clarify implementation scope and delivery.
DESIGN · BUILD · DELIVER Requirements & Architecture / Development & Access / Testing & Launch / Documentation & Handover
FROM REQUIREMENTS TO DELIVERY
From business requirements to launch,
Organize the implementation process completely.
Customized implementation requires converting business rules into system design, and then connecting it with development, external interfaces and acceptance. S08 Organize these work into consulting and implementation services with human participation, and determine the division of labor among products, teams, and partners by project.
The system can connect
Clarify the interfaces and responsibilities between systems, contracts, wallets, accounts and external platforms.
The results can be accepted
Complete testing around the agreed scenario and deliver the system, records and operating materials.
YOUR IMPLEMENTATION GOAL
The implementation goals are different,
The focus of the first discussion was also different.
Choose the closest implementation goal to see what to prepare. Begin with requirements design, development and integration, or launch readiness, then define scope.
FIRST CONVERSATION / communication starting point
First transform the business goals into a clear construction scope.
If you want to build an enterprise system, digital asset application or governance backend, you need to first clarify the users, scenarios and core rules, and then decide on the system modules, technical path and stage delivery.
- Which business problem should be solved first?
- Which roles are used and what are the key processes?
- Which functions have entered the first stage and how to accept them?
You can prepare it first
Business introduction, user roles, existing processes, proposed functions and internal decision-makers.
FIRST CONVERSATION / communication starting point
Start with existing system and interface conditions.
Already have a client, account or business backend and want to connect the wallet to an external platform. The focus is to check existing capabilities, data relationships, access permissions, and interface support from all parties.
- What tasks does the existing system perform and what connections need to be made?
- Are the interface documents, test environment and authorization complete?
- How to synchronize accounts, business status and exceptions?
You can prepare it first
Existing system description, interface documentation, data fields, platform contacts and available test environment information.
FIRST CONVERSATION / communication starting point
Let the confirmed rules be implemented into functions and permissions.
For changes to roles, rights, lock-up/release, incentives or approval rules, confirm the business basis and scope before configuration or custom development.
- Which rules have been confirmed by the enterprise?
- Which ones can be configured, and which ones require development or contract changes?
- How to connect historical data with existing users?
You can prepare it first
Rule files, role permissions, parameter descriptions, existing versions and business processes that need to be changed.
FIRST CONVERSATION / communication starting point
Turn launch preparation into a checklist that can be checked off one by one.
Test versions or development results are available and are ready for deployment and handover. It is necessary to check the environment, test results, partner conditions and enterprise operational preparations to formulate release and acceptance arrangements.
- At what stage has the agreed function, interface and permission testing been completed?
- What enterprise authorization and partner confirmation is required to go online?
- Who takes over the operation, and how are problems recorded and handled?
You can prepare it first
Current version, deployment environment, test and problem records, acceptance criteria and person in charge of launch.
SERVICE SCOPE / Service Scope
From the requirements and architecture,
Advance to testing and online.
Organize and implement around six tasks. Based on the existing system, interface conditions and completed design, determine the content that needs to be developed, connected and checked this time.
01
Requirements Review & Acceptance Design
Who does the system serve and what business tasks does it complete?
Sort out user roles, business scenarios, existing processes and functional requirements, and clarify the scope, priorities and verifiable acceptance criteria of this construction.
Delivery direction
Requirements · Functional Scope · Acceptance Basis
02
Technical architecture and implementation plan
Which capabilities need to be built, and which ones are provided by existing systems or partners?
Evaluate the distribution of responsibilities, data flow, permissions and environmental conditions of the system and contract, compare technical paths, list interface dependencies and phased implementation arrangements.
Delivery direction
Architecture solution · Data and permission description · Implementation plan
03
System and contract custom development
How to enter the confirmed business rules into the software?
Develop the client, backend and related contracts according to confirmed requirements, implement accounts, rights, processes and parameter rules, and record versions and changes. Specific modules are determined by project.
Delivery direction
Agreed software results·Configuration and version records
04
Wallet, Account & Interface Integration
How to connect wallet, business account and external platform?
Check access objects, interface permissions and data requirements, organize joint debugging of identity and account association, status synchronization and exception handling, and clarify the responsibilities of the technical side and the business side.
Delivery direction
Interface description · Access configuration · Joint debugging record
05
Environment deployment and testing verification
Can the system operate according to the rules in the agreed environment?
Configure deployment, perform agreed functionality, interface, permission and security tests, and follow up on fixes and user acceptance. Coordinate an independent security audit separately if needed.
Delivery direction
Deployment Records · Test Results · Issues & Fixes
06
Online preparation and results handover
Are the online conditions complete? How can companies take over and use it?
Check release conditions, access rights and business responsibilities, organize online operations, usage instructions and results transfer, and clarify open matters and follow-up maintenance arrangements.
Delivery direction
Go-live and handover checklist · Operation manual · Subsequent responsibilities statement
Existing product configuration, interface integration or customized development can be used. First confirm the adaptation method, responsible team and acceptance scope.
Confirm my scope of workWHAT YOU RECEIVE / deliverables
Deliver a functioning system,
also delivers the basis for use and acceptance.
Requirements, software, interface documentation and the launch-handover package explain what to do, what is delivered, how systems connect and how to use them. See the delivery-framework examples below.
REQUIREMENTS & ARCHITECTURE
Clearly write down the construction scope, technical path and acceptance basis.
Organize requirements, rules, architecture and implementation instructions according to the project, so that the enterprise and technical teams can advance around the same scope, and the interface dependencies and matters to be confirmed are well documented.
The value of this delivery
Discuss this delivery Form a common basis that can guide development, manage changes, and verify results.
S08 / Service Delivery Framework Example
Requirements & Architecture Documents
- Users and scenarios
Use roles, key processes and problems to be solved
Confirmation/Source: Provided by the enterprise, reviewed by the consulting team- Functions and rules
Construction scope, business rules, permissions and parameters
Confirmation / Source: Confirmation by the enterprise, compiled by the consulting and development team- Architecture and dependencies
System composition, data flow, environment and external interface conditions
Confirmation / Source: Technical team and platform partners- Acceptance Basis
Delivery list, verification scenarios and stage confirmation conditions
Confirmation/Source: Jointly confirmed by the enterprise and the implementing parties
Examples are used to illustrate the delivery structure; specific documents, responsible parties and acceptance items are confirmed in the project plan.
SOFTWARE & CONFIGURATION
Deliver software results corresponding to the agreed functions and versions.
Collect software, contracts and configuration results around confirmed modules. The delivery scope, usage rights and maintenance methods of source code, deployment parts and operating documents are determined according to the contract, and third-party components are subject to corresponding licenses.
The value of this delivery
Discuss this delivery Let the delivery version, functional scope and usage conditions map to the specific results.
S08 / Service Delivery Framework Example
Software and configuration results
- System module
Agreed client, backend and business functions
Confirmation/Source: Agreed development responsible party- Contracts and Rules
Description of contracts and configuration parameters developed by scope
Confirmation/Source: Technical team development, enterprise verification rules- Versions and Deployments
Agreed versions, release content and environment configuration records
Confirmation/Source: Technical team gathering, enterprise confirms receipt- Rights and dependence
Contractual delivery rights, third-party components and licensing instructions
Confirmation/Source: All parties to the contract and relevant rights holders
Examples are used to illustrate the delivery structure; specific documents, responsible parties and acceptance items are confirmed in the project plan.
INTERFACES & INTEGRATION
Make cross-system connections have clear inputs, outputs, and responsibilities.
Organize technical access to wallets, accounts and external platforms, record interface conditions, data correspondence, normal processes and exception handling; when involving custody, card issuance or securities business, the relevant business entities shall confirm the actual service conditions.
The value of this delivery
Discuss this delivery Make it clear what is connected, what is verified, and what matters still need to be confirmed by the business party.
S08 / Service Delivery Framework Example
Interface and joint debugging records
- Access object
Connection scope of system, wallet, account and platform
Confirmation / Source: Enterprise, technical team and platform partners- Interface and Authorization
Fields, calling methods, permissions and test environment requirements
Confirmation / Source: Interface provider and access technology party- Joint debugging and exceptions
Status synchronization, exception handling and verification records
Confirmation/Source: Joint verification by relevant technical parties- Business conditions
Partner approval, applicable areas and business confirmation matters
Confirmation/Source: Corresponding platform and business responsible entity
Examples are used to illustrate the delivery structure; specific documents, responsible parties and acceptance items are confirmed in the project plan.
TESTING & HANDOVER
Allows businesses to verify results and take over day-to-day operations.
Organize the results, deployment records, operation manuals and handover lists according to the agreed test and acceptance scope, and list the outstanding matters and the work connection after going online. If an independent safety audit is included in the project, the report will be issued by the corresponding reviewer.
The value of this delivery
Discuss this delivery Hand over the acceptance results, operational basis and follow-up responsibilities together.
S08 / Service Delivery Framework Example
Testing and Handover Documents
- Test results
Function, interface, permissions and agreed security test records
Confirmation/Source: Test Responsible Party and Enterprise Acceptance Party- Deployment & Release
Environment, version, release conditions and operation records
Confirmation/Source: Deployment Responsible Party and Enterprise Authorizer- Operations and Permissions
Operation Manual, Account Permissions and Instructions for Use
Confirmation/Source: Implementation team handover, enterprise acceptance- Follow-up matters
To-do list, maintenance scope, problem handling and responsible contact person
Confirmation / Source: The enterprise and the relevant service provider confirm according to the contract
Examples are used to illustrate the delivery structure; specific documents, responsible parties and acceptance items are confirmed in the project plan.
FROM DESIGN TO HANDOVER
From requirement confirmation to handover,
Each stage has a confirmation basis.
Advance requirements, design, development, testing and handover in phases. First agree on the acceptance scenarios and responsibilities, and then determine the schedule based on system complexity, external interfaces and review conditions.
- 01
Confirm requirements
What problems will this construction solve?
Sort out the business scenarios, usage roles, existing capabilities and rule documents, and clarify the scope and priorities.
Milestone DeliverablesRequirements & Acceptance Basis
The enterprise and implementing parties confirm the construction scope - 02
Determine the architecture
How to build it, and who will provide what conditions?
Evaluate the technical path, system responsibilities, interface dependencies and environmental requirements, and determine phase tasks and responsibilities.
Milestone DeliverablesArchitecture plan, implementation plan and dependency list
Confirm technical solutions, interface conditions and delivery arrangements - 03
Development and Access
How to implement functions and connections as agreed?
Promote system and contract development, rule configuration and interface joint debugging, and manage versions, issues and demand changes.
Milestone DeliverablesPhased software deliverables, configuration and integration-test records
The agreed function has the conditions to enter the test - 04
Deployment & Acceptance Testing
Can the results pass the agreed verification?
Configure the environment, test and perform user acceptance, checking fixes and any required third-party reviews.
Milestone DeliverablesDeployment records, test results and acceptance checklist
Check acceptance criteria and to-do items before going online - 05
Online and handover
Who confirms the release and who takes over the follow-up operations?
Confirm the release authorization and partner conditions, organize the launch, manual explanation and achievement handover, and clarify the maintenance connection.
Milestone DeliverablesRelease and handover records, operation manual
Relevant responsible parties confirm the online conditions and reception arrangements
Cooperation arrangements
You can carry out demand and architecture consultation first, or you can undertake the development, access or online preparation of existing solutions; the phase results, fees and follow-up support are agreed separately.
CLEAR RESPONSIBILITIES
Business, development and platform,
Collaborate on the same project.
Make it clear who confirms requirements, who completes development, who opens interfaces, and what matters require professional review. Organize implementation teams by project and assign responsible persons for docking and delivery.
DEFINE & ACCEPT
Enterprise and project leader
Provide business, rules and authorization information, confirm requirements and changes, arrange internal decision-making, test participation, online authorization and results reception, and be responsible for its own business and data management.
DESIGN & IMPLEMENT
Consulting and Development Team
Organize business requirements into technical solutions, be responsible for or coordinate development, configuration, deployment and testing as agreed, record issues and versions, and submit results and operation instructions. The specific responsible parties for each implementation work are clearly defined.
ENABLE & CONNECT
Platform and business partners
Confirm platform capabilities, interface permissions, access requirements and business conditions, and cooperate with joint debugging and verification. The actual custody, card issuance, payment and securities services are undertaken by the corresponding qualified entities according to the agreement.
REVIEW & REPORT
Third-party professional review agency
Carry out independent safety audits, legal or other professional reviews based on project needs and scope of entrustment, and issue corresponding opinions or reports; the implementation team is responsible for coordinating the processing of data and review matters.
Wallet, account, payment or securities-platform access depends on actual interfaces and partnership conditions. Assign responsibilities for systems implementation and related business procedures separately.
View STO structural design servicesBEFORE WE TALK
Let’s start with the issue of cooperation.
Be more specific.
Direct email consultation Can I continue to use the existing system?
You can first evaluate the existing functions, interfaces and deployment conditions to determine whether to meet the needs through configuration, interface access or new modules. List the processes, data and versions that need to be retained in the requirements description, and then confirm the scope and acceptance method of this transformation.
Does the software delivery include source code?
The delivery scope of source code, deployment parts, configuration and operation documents, as well as software usage rights, maintenance and subsequent change methods, shall be specified in the contract. When open source or other third-party components are involved, they should be used in accordance with the corresponding license; customized implementation cannot replace the authorization of the third-party software rights holder.
What is the difference between security testing and independent security audits?
Implement tests around agreed versions and scenarios, check functions, interfaces, permissions and related security issues, and record repair results. The independent safety audit is carried out by a separately entrusted professional reviewer according to the scope of the audit and a report is issued. The responsibilities, methods and results of the two are confirmed separately and included in the project arrangement when independent audit is required.
What does wallet and account integration cover?
Technical work may include account association, interface configuration, status synchronization and process joint debugging, which shall be subject to actual system support and agreed scope. Asset custody, card issuance, payment and securities services require corresponding business entities, authorizations and partner conditions; technical access results and actual business opening shall be inspected and accepted separately.
How to determine acceptance and post-launch services?
First agree on the delivery version, function and interface scope, test scenarios, reception methods and online conditions, and then check the software, interfaces, test results and operation manuals accordingly. The scope of monitoring, maintenance, customer service, response arrangements and version updates after going online will be clearly defined separately as needed, and responsibilities and service conditions will be determined in the contract.
START WITH YOUR PROJECT
Your business needs,
How far do you want to advance?
Tell us about the existing systems and usage scenarios,
and the content you wish to develop, access or bring online.
Start with a clear question to discuss scope of services and next steps.
A first conversation can cover
Learn about the AssetX Liquidity Technology System - Business scenarios, existing systems and interface conditions
- Desired functionality and usage
- Acceptance Goals, Responsible Teams & Partners
S08 / YOUR SERVICE INQUIRY
Check service consultation needs
Your request has not been sent. Open your email application, verify the recipient and message, then send it. You may also copy the content into your preferred email service.
Continue reading · Services
Technical consultation and delivery and supporting of customized implementation
Technical consultation and customization implementation involve personnel converting business requirements into system design, organizing development, interface access, testing and online handover. When choosing ready-made products and customization work, you need to first clarify the business process.
Reading & Selection Guidance Confirm the existing system, interface conditions, acceptance scenarios and delivery boundaries before implementation.