Metrics for the Analysis Model-
These metrics are used to examine the analysis model with the objective of predicting the size of the resultant system. Size acts as an indicator of increased coding, integration, and testing effort; sometimes it also acts as an indicator of complexity involved in the software design. Function point and lines of code are the commonly used methods for size estimation.

Function Point (FP) Metric:
The function point metric, which was proposed by A.J Albrecht, is used to measure the functionality delivered by the system, estimate the effort, predict the number of errors, and estimate the number of components in the system.

Lines of Code (LOC):

Lines of code (LOC) is one of the most widely used methods for size estimation. LOC can be defined as the number of delivered lines of code, excluding comments and blank lines. It is highly dependent on the programming language used as code writing varies from one programming language to another.

Metrics for design model-
The success of a software project depends largely on the quality and effectiveness of the software design. Hence, it is important to develop software metrics from which meaningful indicators can be derived. With the help of these indicators, necessary steps are taken to design the software according to the user requirements. Various design metrics such as architectural design metrics, component-level design metrics, user-interface design metrics, and metrics for object-oriented design are used to indicate the complexity, quality, and so on of the software design.

Architectural Design Metrics:
These metrics focus on the features of the program architecture with stress on architectural structure and effectiveness of components (or modules) within the architecture.

Many software quality indicators that are based on measurable design characteristics of a computer program have been proposed. One of them is Design Structural Quality Index (DSQI), which is derived from the information obtained from data and architectural design. To calculate DSQI, a number of steps are followed, which are listed below.

1. To calculate DSQI, the following values must be determined.

Number of components in program architecture (S1)
Number of components whose correct function is determined by the Source of input data (S2)
Number of components whose correct function· depends on previous processing (S3)
Number of database items (S4)
Number of different database items (S5)
Number of database segments (S6)
Number of components having single entry and exit (S7).

Production rules system consist of (condition, action) pairs which mean, “If condition then action”. It has mainly three parts:

• The set of production rules
• Working Memory
• The recognize-act-cycle

In production rules agent checks for the condition and if the condition exists then production rule fires and corresponding action is carried out. The condition part of the rule determines which rule may be applied to a problem. And the action part carries out the associated problem-solving steps. This complete process is called a recognize-act cycle.

The working memory contains the description of the current state of problems-solving and rule can write knowledge to the working memory. This knowledge match and may fire other rules.

If there is a new situation (state) generates, then multiple production rules will be fired together, this is called conflict set. In this situation, the agent needs to select a rule from these sets, and it is called a conflict resolution.

Example:

• IF (at bus stop AND bus arrives) THEN action (get into the bus)
• IF (on the bus AND paid AND empty seat) THEN action (sit down).
• IF (on bus AND unpaid) THEN action (pay charges).
• IF (bus arrives at destination) THEN action (get down from the bus).

If two computers with the same IP connected to the same LAN want to share information then maybe they cause IP Conflicts.

As An IP conflict occurs when two or more devices in the same network share an IP address. This clash causes one or both devices to stop communicating with the rest of the network, which could lead to a slew of problems. Figuring out how to find IP conflicts, as well as how to fix an IP conflict when it occurs, is crucial to the health of your network and its devices.

The network layer is more intelligent than the data-link layer mainly because the network layer has a broader view of the network than the data-link layer. The data-link layer (Ethernet, WiFI, etc.) talks about network cards, links between them and local networks. The network layer (mainly IP) talks about IP addresses and how hosts must route a network packet to achieve an end-to-end communication.

And Also,

In OSI model Network layer is responsible for ‘source-to-destination’ delivery of a packet possibly across the multiple networks( links ),whereas the data link layer oversees the delivery of the packets btw ‘two’ systems on same network.