| |
|
|
|
|
| |
 Reusable Components |
| |
There are components that are reusable across projects (e.g. Login screen). But such assets are not created often. This is because projects vary in architecture and technology. How many times does one create the Login screen? For every project this would be created from scratch. Re-usable assets independent of architecture and technology could be of great help. |
| |
Impact Analysis |
| |
|
When any changes are to be made to software, impact of the change needs to be studied. The impact is done using code review, which is difficult to understand the assumptions made by the developer while writing the code. |
| |
Knowledge Base |
| |
|
Learning from a project is rarely documented. Thus, when a developer quits the team the knowledge is also carried with the developer. This makes maintenance of the project very difficult. An ideal scenario for development would be that the development and maintenance of the project conform to a strict enforced standard that is easy to customize, understand and learn. |
| |
Standards |
| |
|
Every project follows proprietary architecture. Currently, only software libraries (ODBC, ADO .Net, J2EE, JDBC) are available as standards. Not much standard data are available in terms of how to send data from business layer to database layer, how to design database tables, security implementation, etc. This makes the newcomer to be productive only after few months. |
| |
|
|
| |
|
|
|
|
| |
