What is the difference between object-oriented system analysis and system design?

Object-Oriented Design UML practices:
"An analysis model is different from a design model. It does not involve developing any characteristics of the system, but aims to capture some aspects and features of the business in the" real world.
Generally, the analysis model describes the data processed in the application and various processes of data processing. In traditional analysis methods, these models are represented by graphs, such as logical data models and data flow diagrams. It is worth noting that the analysis model is used to describe the business process, which is earlier than and independent from this process. For example, organization charts and descriptions of specific production processes have been used for quite a long time in business and industry."

Object-oriented System Analysis:
"One idea is to stick to the consensus that people have formed in the software engineering shower over the years-the analysis focuses on what the system" does, no matter how it "does it", and does not involve details; design and solve the "how to do" problem and describe the relevant details. According to this point of view, the details about object attributes and services are not considered in OOA, and they are put into the West Lake in the OOD stage, such as the Berard method and Rumbaugh method both adopt this division of labor. Another point of view is that the analysis only targets problems and system responsibilities, and establishes an OOA model independent of implementation without considering implementation-related factors. This OOA model is a complete expression of the problem domain and system responsibility, including the expression of attributes and services. The design considers implementation-related issues (such as the selected programming languages, databases, and graphic user programs), recognizes related objects, and establishes an OOD model for specific implementation, for example, Coad/Yourdon adopts this division of labor."

Building WEB applications with UML:
"In the analysis phase, important processes and objects in the problem space are identified, named, and classified.
The analysis focuses on the functional requirements of the system, while ignoring the constraints on the system architecture. The focus is to ensure that all functional requirements described by use cases and other stable expressions are implemented somewhere in the system ."