SAP NetWeaver Developer Studio and SAP NetWeaver Development Infrastructure (NWDI) support the component-based development. This means that you perform the software development in standard projects following SAP's component model principles. The projects you work on are wrapped in development components (DC), which are organized in software components (SCs). You get the SCs with the development configuration you got in your Developer Studio. The development itself can be under version control (from the Design Time Repository (DTR), provided by the NWDI) and is based on SAP's component model or results from local development in the Developer Studio.
If you have been developing the software outside a DC, you must first migrate it to a DC. For more information, see Migrating Standard Projects into Development Components .
These are the tasks you can perform with a DC:
Creating Development Components
Describes how to create a new DC from scratch.
Synchronizing a DC in a Local File System
Describes how to obtain DCs that another developer has created and you need to edit. The process of getting an up-to-date version of a certain DC from the versioning system is called sync .
Editing Development Components
Describes how to edit DCs in Developer Studio.
Describes how to work with activities that gather the changes to the software you make.
Describes how to configure the public parts of your DC. You use the public parts to show which parts of the software you develop in the DC can be used from outside DCs, and which parts should remain hidden.
Nesting Development Components
Describes how to nest DCs. The concept is described in more details in the SAP's component model.
For more information about defining substitution variables for the DC, see SAP Note 1042076 .
Defining Development Component Dependencies
Describes how to define dependencies to other DCs, as required by the component model.
Describes how to move a DC from one SC to another SC (even in different development configurations).
Describes how to generate the Javadoc for your Java sources out of your DCs.
Transporting the Software to the Transport System
Describes how to trigger the transport of the developed software to the transport system.