Application Framework Principles

Frameworks

In computer systems, a framework is generally a layered structure implying what kind of programs can or should be built and how they would interrelate.

An Application Framework composed of a software framework used by software developers to implement the standard structure of application software.

To give you an idea, let us consider the below scenario about the chassis of a car or the steel structure of a building.

Application frameworks became famous with the growth of graphical user interfaces (GUIs) since these tended to promote a standard structure for applications.

Developers usually use object-oriented programming (OOP) techniques to implement frameworks such that the unique parts of an application can simply inherit from classes extant in the framework. 

Choosing a suitable framework among the available frameworks can be a tedious task. No matter which framework you go for remember the needs of your application and the tools needed for it. 

There are 5 principles in application framework.They are listed below.

 

S.O.L.I.D

S - Single responsibility

O - Open-close

L - Liskov substitution

I - Interface segregation

D - Dependency inversion

Single responsibility

The single-responsibility principle is a computer-programming principle that states that every module or class should have responsibility over a single part of the functionality provided by the software, and that responsibility should be entirely encapsulated by the class, module or function.

Open-close

In object-oriented programming, the open/closed principle states "software entities should be open for extension, but closed for modification"; that is, such an entity can allow its behavior to be extended without modifying its source code.

Liskov substitution

The Liskov Substitution Principle (LSP, lsp) is a concept in Object Oriented Programming that states: Functions that use pointers or references to base classes must be able to use objects of derived classes without knowing it.

Interface segregation

In the field of software engineering, the interface-segregation principle states that no client should be forced to depend on methods it does not use. ISP splits interfaces that are very large into smaller and more specific ones so that clients will only have to know about the methods that are of interest to them.

Dependency inversion

The Dependency Inversion Principle (DIP) states that high level modules should not depend on low level modules; both should depend on abstractions. Abstractions should not depend on details.