iOS Development practice: implementation of a full microblogging client

This paper describes the implementation of a complete microblogging client based on two tools: Data dictionary and Flow graph. Both the data dictionary and the flow diagram can be used to express the thread's execution process, while defining the required classes, which is the basis for further design of the class.

The data dictionary is actually a table whose first field is the identifier in the program code, the other fields describe how it is used in the thread, and the other elements it relies on, and the identifiers in the data dictionary are basically sorted by the thread's execution process.

A data flow diagram is a planar topology in which each node is either external or a code module that can be executed by a thread. The edge from the external data to the code module means that the thread needs to use the external data when executing the code module, from the code module to the side of the code module, indicating that the thread executes a code module and jumps to another code module to begin execution. Other types of edges have no specific meaning.

Data dictionary

· The thread starts and executes the function main.

· int main(int argc, char *argv[])

--the thread first jumps to the code block where the function main is located, and then jumps to the function Uiapplicationmain.

· int uiapplicationmain (

int argc,
Char *argv[],
NSString *principalclassname,
NSString *delegateclassname
);

--the thread turns to the code block where the function Uiapplicationmain, and then creates two memory blocks in memory that refer to the app itself and the application proxy, which is actually the UIApplication Class (subclass) and an instance of the Saappdelegate class (subclass);.

·

Streaming chart

iOS Development practice: implementation of a full microblogging client