Development Scope
Scope and Basic Check
Determine the existing foundation, technical dependencies and content that needs to be developed based on the user role, device page, operation process, platform API, target client and version range.
Implementation and integration
Develop lists, maps, trends, alarms and device operation interfaces to handle loading, no data, offline, failure and insufficient permission states.
Delivery Documentation
Deliver the agreed client source code, build configuration and interface integration testing records.
Verification and Constraints
The client display status needs to indicate the update time and source; third-party maps, messages and application release conditions must be confirmed separately.
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
- User Role, Device Page, Operational Flow, Platform API, Target Client and Version Range.
- 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 the agreed client source code, build configuration and interface integration testing records. | Check the real-time status of the interface and equipment. |
| Integrated data | Versions and dependencies, interface configuration, usage or deployment steps, and integration changes | Test permissions, failure feedback, and repeat actions. |
| Verify records | Test conditions, execution records, problem lists and regression results | Verify target terminal size and system version. |
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
Do App, mini programs and Web have to be developed together?+
One or more clients can be selected based on user scenarios. First determine the device usage, permissions, notifications and offline requirements, and then agree on the functions, interfaces and maintenance scope of each end.
4G equipment Web/+
Please give priority to user role, device page, operation process, platform API, target client and version range. 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 requires attention: the client display status needs to indicate the update time and source; third-party maps, messages and application release conditions must be confirmed separately. Existing and new functions must undergo regression testing within the agreed scope after the changes.
Online
Phone
WeChat
Top