This project is read-only.

No! More!! Long!!! Days... at Work!!!!

Video 1 - Introduction to Nido Framework

Nido Framework at Use - The diagram below shows how Nido Framework reduces the size of your DAL and BLL.


Nido Framework is a reusable and highly generic code library developed using Microsoft .NET/ C# to provide a common platform all .NET systems of yours. It provides a platform for quick software delivery and to easily customize and extend software without breaking the already developed parts of the system.
Nido Framework is developed on top of MS .NET entity framework, and also heavily influenced by the code first technique. The framework provides a standard method of coding your business logic layer as well as data access layer. That allows you to have much predictable, standard, and best performing codes despite worrying about the expertise of the developers who write them. Additionally once you start using Nido across your development center you will easily be able to jump from one project to another without spending tons of time for knowledge transfers.

We have noted that the rapid nature of the modern businesses operate needs software solutions faster than ever before. The lifetime of the software is shortening, so the cost incurred in producing, cannot be justified by the time period that a business is using the software. This needs software to be produce faster while meeting reasonable cost and quality requirements.


The Nido Framework address all that for you. It is not just provides that but get you a quick start to the project while enforcing code consistency, coding best practices and architectural discipline irrespective to the experience or the skills and expertise of the developer. This way, development time can be reduced and the problem of system depends on individual developers and their expertise will be resolved for good. This framework and the set of guidelines established will govern developers to develop systems in a similar manner using similar techniques and coding patterns allowing even for the newly introduced resources to manage the systems during urgent situations. In practice, we did very limited knowledge transferring when shifting resources from one part of a system to another as well as when introducing new resources.

As said a project that is not completed within the budgeted time period can be taken over by another set of new developers (who has experience developing on Nido) could continue the work with having limited amount of knowledge transferring. This is made possible due to the consistency of the code the Nido framework provides.

Common Project Usage.jpg

As you can see in the figure given above, the development time is significantly reduced by having common features centrally developed and by reducing the amount of coding required to write. It increases overall efficiency of the development work by accelerating the time-to-market, reducing defect and increasing bug tracking/ fixing rate.

Last edited Dec 29, 2013 at 4:13 AM by RocketFramework, version 28