How to understand the interoperability of the system

It's about using one software to control other software and interoperate with each other

You're teaching yourself how to program software, huh.

The test of the software needs to have a basis, whether it is the software requirements specification, the summary design, the detailed design, even if it is the user's needs, it can be the basis!

Software testing can start with the analysis of the six major characteristics of quality and 27 sub-characteristics, and form test cases according to the operation manual

1. Functionality:

1. Suitability: The corresponding functions are provided.

2. Accuracy: correct (what the user needs).

3. Interoperability: the ability to exchange data between products.

4. Confidentiality and security: allow authorized users and systems to access the corresponding data and information normally, and prohibit unauthorized users from accessing.

5. Functional compliance: consistency of international and national industry enterprise standards and specifications.

2. Reliability: the ability of the product to complete the specified function under the specified conditions and within the specified time.

1. Maturity: the ability to prevent internal errors from causing software failure.

2. Fault tolerance: the ability to self-process when the software fails.

3. Recoverability: the ability to recover in the event of failure.

4. Compliance with reliability.

3. Ease of use: The ability of the product to be understood, learned, used and engaged by users under the specified use conditions.

1. Comprehensibility:

2. Ease of learning:

3. Ease of operation:

4. Attraction:

5. Ease of use compliance:

4. Efficiency: The ability of a software product to provide appropriate performance relative to the number of resources used under specified conditions.

1. Time characteristics: average transaction response time, throughput rate, TPS (transactions per second).

2. Resource utilization: CPU memory, disk IO, network bandwidth, queue, shared memory.

3. Efficiency compliance:

5. Software maintainability:"Four rules", the ability to repair a prescribed function using prescribed tools or methods under prescribed conditions and within a specified period of time.

1. Ease of analysis: the difficulty of analyzing and locating problems.

2. Changeability: the ability of a software product to make specified modifications can be realized.

3. Stability: Prevent accidental modification from causing the program to fail.

4. Easy to test: the ability to make the modified software can be confirmed.

5. Maintenance compliance.

6. Software portability: the ability to migrate from one environment to another.

1. Adaptability: adapt to different platforms.

2. Easy installation: the ability to be installed.

3. Coexistence:

4. Easy to replace.

5. Compliance with portability: hiIf the water plants in the South Lake are helpful, don't forget to adopt them! goto365testing,

Software adaptability test should first simulate the user's real operating environment, that is, hardware, to focus on testing the content of: software compatibility, platform compatibility, operating system compatibility, software expansion ability test, software interface test, software destructive test, performance test, etc., the above list is the content that must be tested, of course, different environments will test different content, this needs to be carefully studied requirements.

Double contingency is a concept proposed by the German social communication scientist Luhmann, which refers to the uncertainty of both sides of the communication, so that the choices made through communication are likely to be rejected. For example, you call a friend's **, but he happens to be in the shower, so he doesn't receive your **. This is "the rejection of the choice made through communication".

The existence of double contingencies indicates that the social information system is a multivariate system, and if not handled properly, it will cause communication barriers and communication barriers. This requires humanity to continuously identify and overcome barriers to transmission and barriers to transmission.

Serendipity has several meanings: 1Relative to inevitability, there is a certain probability; 2.

Contingency is not without laws to speak of, and probability is also the law of the movement of matter; 3.There is also inevitability in contingency, and everything that happens has its inevitable cause or follows the law of necessity; 4.Accident is caused by the lack of human cognitive ability, with the continuous enhancement of human ability to understand the world, the accident will gradually decrease, and the understanding of the world in human society is gradually moving from a chaotic accident to the inevitable.

There are three most commonly used drawings for electrical control systems: schematic diagrams, wiring diagrams, and position diagrams. The so-called consistency of the three diagrams means that although the three diagrams are presented in different ways, some are detailed, some are abbreviated, and some details are even omitted.

However, the composition, quantity and relationship between the components represented in the three drawings should be consistent, the text symbols used to represent the same part should be consistent, and the parameter labeling of the same part or component or terminal should be consistent. If there are other drawings, they must also be consistent with these three patterns.

Middleware is a kind of independent system software or service program, which is software that connects two independent applications or independent systems, even if they have different interfaces, but can still exchange information with each other through middleware.

Middleware is on top of the operating system, network and database, and the lower layer of application software, and its overall role is to provide an environment for the operation and development of application software on top of itself, helping users develop and integrate complex application software flexibly and efficiently.

With the rapid development of computer technology, more application software is required to operate on many different network protocols, different hardware manufacturers, and different network platforms and environments. As a result, software developers need to develop multiple applications to achieve operational purposes. Therefore, the emergence of middleware technology greatly reduces the burden on developers and makes the operation of the network more efficient.

Middleware literally means "software in the middle", and although it may seem unfamiliar to readers other than programmers, middleware has been around since the 1990s as the infrastructure for web applications. The Tuxedo system, which was born at Bell Labs, was one of the first middleware used in trading systems. The emergence of middleware solves the common problems of communication, interoperability, collaboration, transaction, and security of software systems in a heterogeneous distributed network environment.

Because of its importance in the system, middleware, operating systems, and databases are known as the troika of system software.

Alibaba's middleware mainly includes the following:

Distributed relational database DRDS horizontal splitting Message queue MQ is the middleware for message scalability.

Enterprise Distributed Application Service EDAS and some other middleware for distributed services, such as configuration services, caching, etc., will also be placed in the middleware.

The goal of software engineering is to develop software products that are applicable, effective, modifiable, reliable, understandable, maintainable, reusable, portable, traceable, interoperable, and meet user needs at a given cost and schedule. Pursuing these goals helps to improve the quality and development efficiency of software products and reduce the difficulty of maintenance.

1) Applicability: the difficulty of the software to meet the user's needs under different system constraints.

2) Effectiveness: The software system can make the most efficient use of the time and space resources of the computer. All kinds of software regard the time and space cost of the system as an important technical indicator to measure the quality of software.

In many cases, there is a contradiction between temporal and spatial validity, and it is necessary to sacrifice temporal validity for spatial validity, or spatial validity for temporal validity. Space-time compromise is a technique often employed.

3) Modifiability: Allows modifications to be made to the system without increasing the complexity of the original system. It supports the debugging and maintenance of the software, which is a difficult goal to achieve.

4) Reliability: It can prevent the failure of the software system caused by the imperfection of concept, design and structure, and has the ability to recover the failure of the software system caused by improper operation.

5) Comprehensibility: The system has a clear structure that directly reflects the needs of the problem. Comprehensibility helps control system software complexity and supports maintenance, portability, or reuse of software.

6) Maintainability: After the software is delivered, it can be modified to correct latent errors, improve performance and other attributes, and adapt the software product to changes in the environment. Software maintenance costs account for a large proportion of software development costs.

Maintainability is a very important goal in software engineering.

8) Portability: The ease with which software can be moved from one computer system or environment to another.

9) Traceability: the ability to track software design and program forward according to software requirements, or reverse track software requirements according to software design and programs.

10) Interoperability: The ability of multiple software elements to communicate with each other and work together to accomplish tasks.

Software engineering is a discipline that uses scientific knowledge and technical principles to define, develop, and maintain software. Software engineering goals: to pay low development costs; Fulfillment of the required functionality; Achieve better performance; The developed software is easy to port; Low maintenance costs; Able to complete development tasks on time and deliver them in a timely manner; The developed software is highly reliable.