Development Scope
Scope and Basic Check
Determine the existing foundation, technical dependencies, and content that needs to be developed based on the device model, quantity, tenant relationship, authentication, data cycle, alarm rules, and deployment conditions.
Implementation and integration
Develop device registration, binding, grouping, access, status, historical data, alarms and API, and define data retention and permission auditing.
Delivery Documentation
Deliver source code or deployment package and interface documentation.
Verification and Constraints
Number of devices, concurrency, and data retention all affect capacity, and unlimited device access or fixed performance is not preset.
Project implementation process
Verification of data and interfaces → Confirmation of technical solutions and verification use cases → Implementation of integration with the target environment → Regression of abnormal scenarios → Transfer of version data.
Verify the implementation results in the target hardware and software environment, and deliver records of associated interface configurations, version dependencies, and problem handling to facilitate subsequent integration and maintenance by the enterprise R&D team.
Project Inputs
- Device model, quantity, tenant relationship, authentication, data period, alarm rules and deployment conditions.
- Design information, code, interface permissions and target test equipment can be provided.
- Source files, programs or tools expected to be delivered, inter-module integration testing responsibilities and project nodes.
- Acceptance samples, environment, test conditions and passing thresholds.
Deliverables and Acceptance
| Deliverables | Delivery content | Verification method |
|---|---|---|
| achieve results | Deliver source code or deployment package and interface documentation. | Verify tenant and device access isolation. |
| Integrated data | Versions and dependencies, interface configuration, usage or deployment steps, and integration changes | Test device reconnection, status updates, and alarm rules. |
| Verify records | Test conditions, execution records, problem lists and regression results | Test access, query, backup and recovery according to the agreed scale. |
The delivery scope and acceptance criteria are determined based on the target environment. Third-party SDK, licenses, laboratories, cloud resources, equipment materials and on-site support are listed separately; when the existing information is insufficient, follow-up work will be determined through interface verification or key function verification.
Frequently Asked Questions
Can the platform be deployed to corporate-owned servers?+
The deployment method, database, certificate, network and backup plan can be agreed upon according to the server or cloud environment. Dependencies, configuration and recovery steps are documented upon delivery, and actual capacity is verified by device and data load.
4G What information is required for device management and data platform development?+
Please give priority to providing device model, quantity, tenant relationship, authentication, data cycle, alarm rules and deployment conditions. At the same time, the existing implementation, problems encountered, expected changes, and compatible test conditions are explained to facilitate the determination of implementation scope and reproduction methods.
Can it be implemented on existing products?+
You can first evaluate the scope of existing designs and versions that can be changed, retain the verified parts, and determine the interfaces and dependencies that need to be adjusted. This service needs to be noted: the number of devices, concurrency and data retention jointly affect capacity, and does not preset unlimited device access or fixed performance. Existing and new functions must undergo regression testing within the agreed scope after the changes.
Online
Phone
WeChat
Top