!--a11y-->
The Component Concept 
Arranging Web Dynrpo projects in components is a basic concept that allows programs and program parts to be versioned and reused.
To develop a development component (DC) of type Web Dynpro for a subsequent versioning of the application in the SAP NetWeaver Java Development Infrastructure (NWDI), only the definition of the respective Web Dynpro project type is necessary. In doing so, a container for the development objects and resources is defined. The DC concept additionally offers the opportunity to structure complex Web Dynpro applications and to divide them into smaller application parts. A further central advantage is the option to support application development across team boundaries. A software component (SC) merges the DCs into larger units for the deployment. A mutual usage relation can exist between SCs. As an SC does not contain any development objects, it exclusively defines the dependencies of those components that are assigned to it. During the planning phase, the Web Dynpro application developer assigns task-oriented application objects such as views (an example of this could be a view with a search or display function) to individual DCs and names them correspondingly. At design time, only a few steps are required to create the objects for a DC explicitly.
The Web Dynpro programming model allows a clear separation of the three software layers presentation logic, process logic and data collection thanks to the Model View Controller (MVC) concept. This achieves a high degree of reutilization. In addition, a high degree of reutilization of programs or program parts accelerates the development process in the project teams. The maintenance of Web Dynpro applications that use the NWDI and are versioned in the Design Time Repository, is extremely simplified by the use and modeling of Web Dynpro components. The arrangement of a Web Dynpro application into component offers even more advantages; entire application parts can be nested, for example.