|
Aggregation of events: Users do what they do through XX, where the object "XX" is the function of the product; the main function of this step is to cluster and aggregate the carriers required for discrete function points; Through this method, a capability list is derived based on user roles → core tasks → key product capabilities in The capability list will no longer be posted here. Capability Map Version planning version is actually very simple. It only needs to ensure that the main link of "API release → API display → API usage" can be communicated. Other API documents, logs and other functions can be replaced by alternative solutions, such as through offline documents. Online documentation and the ability to
answer questions through WeChat instead of work orders. However, the R&D side Malaysia Phone Number Data still needs to build the system directly according to the architecture of the product side, in one step, so that functions can be quickly iteratively added without changing the system architecture. It is recommended to iterate the first few versions as follows: Version : Design according to the product architecture, build the system framework, and display the menu completely on each end. After clicking the menu, the same page is displayed. The page prompts "the function is under
construction". The final product effect is equivalent to an empty shell system. Version : MVP, R&D will design the core functional logic architecture and implement the simplest version of the core functions. The relevant core functions are "production and R&D release API → public network client display API → customer application for qualification certification → platform operation approval qualification →Customers apply for API usage rights→Platform operation approves API usage applications→Signature verification when calling API." Take the "Publish API" function
|
|