What are the reasons for using layered protocols?

Layered protocols are typically used in the field of networking technology. There are two main reasons for using the layered protocols and these are:

1. Specialization and
2. Abstraction

- A neutral standard is created by a protocol which can be used by the rival companies for creating programs that are compatible. 

- So many protocols are required in the field and that should also be organized properly and these protocols have to be directed to the specialists that can work up on these protocols. 

- A network program can be created using the layered protocols by a software house if the guidelines of one layer are known. 

- The services of the lower level protocols can be provided by the companies. 

- This helps them to specialize. 

- In abstraction, it is assumed that another protocol will provide the lower services. 

- A conceptual framework is provided by the layered protocol architecture that divides the complex task of information exchange into much simpler tasks between the hosts. 

- The responsibility for each of the protocols is narrowly defined. 

- A protocol provides an interface for the successive higher layer protocol. 

- As a result of this, it goes in to hiding the details of the higher protocol layers that underlies. 

- The advantage of using the layered protocols is that the same application i.e., the user level program can be used by a number of diverse communication networks.

- For example, when you are connected to a dial up line or internet via LAN you can use the same browser. 

- For simplifying the networking designs, one of the most common techniques used is the protocol layering. 

- The networking designs are divided in to various functional layers and the protocols are assigned for carrying out the tasks of each layer. 

- It is quite common to keep the functions of the data delivery separate from each other and separate layers for the connection management too.  

- Therefore, we have one protocol for performing the data delivery tasks and second one for performing connection management. 

- The second one is layered up on the first one. 

- Since the connection management protocol is not concerned with the data delivery, it is also quite simple. 

- The OSI seven layer model and the DoD model are one of the most important layered protocols ever designed. 

- A fusion of both the models is represented by the modern internet. 

- Simple protocols are produced by the protocol layering with some well defined tasks. 

- These protocols then can be put together to be used as a new whole protocol. - As required for some particular applications, the individual protocols can be either replaced or removed. 

- Networking is such a field involving programmers, electricians, mathematicians, designers, electricians and so on. 

- People from these various fields have very less in common and it is because of the layering that people with such varying skills to make an assumption or feel like others are carrying out their duty. 

- This is what we call abstraction. 

- Protocols at a level can be followed by an application programmer via abstraction assuming that network exists and similarly electricians assume and do their work. 

- One layer can provide services to the succeeding layer and can get services in return too. 

- Abstraction is thus the fundamental foundation for layering. 

- Stack has been used for representing the networking protocols since the start of network engineering. 

- Without stack, it would be unmanageable as well as overwhelming. 

- Representing the layers of specialization for the first protocols derived from TCP/ IP.

What are four major elements of design model in software engineering ?

There are two dimensions in which a design model can be illustrated: process and abstraction dimension. Process dimension points the changes in the design model as the design tasks are implemented as part of software process. Abstraction dimension represents the level of detail as each element of analysis model is transformed into design equivalent and refined iteratively.

Design model elements are not developed in a sequential fashion. The design model has four major elements:
- Data
- Architecture
- Components
- Interface

Data design focuses on files or databases at an architectural level and on a component level, data design considers the data structures that are required to implement local data objects.

The architectural model is derived from the application domain, the analysis model and available styles and patterns.

The interface design elements for software tells us how the information flows in and out of the system and how it is communicated among the components. There are three parts to interface design elements: the user interface, interfaces to systems external to application and interfaces to components within the application.
User interface elements include aesthetic elements, ergonomic elements and technical elements. External interface design requires information about entity to which information is sent or received. Internal interface design is closely related to component level design.

The component level design elements describes the internal detail of software component. The component level design defines data structures for all local data objects and algorithmic detail processing that occurs within a component and an interface that allows access to all behaviors.

What is Design Engineering? What are different design concepts?

Design engineering focuses on the creation of a representation or model that are concentrated on architecture of the software, data structures, interfaces and components that are necessary to implement the software.

The design process is an iterative process of refinement, i.e.from a higher level of abstraction to lower levels of abstraction. The design should implement both explicit and implicit requirements. It should be readable and understandable. It provides an over-all illustration of the software from the perspective of the data, function and behavior.

Design concepts provides the software engineer a foundation from which design methods can be applied. These concepts include:
- Abstractions: Software engineers different levels of abstractions as we design the blueprint of the software. Two types of abstraction called data and procedural abstractions are defined.
- Modularity: It leads to information hiding and encourages functional independence.
- Coupling: It is the degree of interconnectedness between design objects. Two types of coupling are used: Interaction and Inheritance Coupling.
- Cohesion: It is the measure to which an element contributes to a single purpose.
- Refinement: Abstraction complements refinement as they enable a software engineer to specify the behavior and data of a class or module yet suppressing low levels of detail.
- Refactoring: It simplifies the design of the component without changing its function and behavior.

The work product of the design engineering phase is the design model which consists of the architectural design, data design, interface design and component-level design and deployment level design.