Await: **Video Guide**
In todays context, Software architecture is a vastly neglected area by both senior managers and junior developers. As I see it, the software architect themselves has to be blamed for this. They were the ones who made things complex, less efficient and did
things that add no value to either developers nor customers with their complex designs. Architects produce things that senior managers do not understand and make things complex for their junior developers, so they both started to hate architects and that lead
to neglect the software architecture. But in my view poin the architecture should
- be simpler to use
- control/ reduce the complexity
- enforce best practices
- gives consistency and uniformity
- increases predictability
- enables re-use.
I uncourage you to use NIDO to standardize your Data Access Layer (DAL) and Business Logic Layer (BLL) Architecture. The NIDO layers are not tightly coupled nor it is too lose. It is just right for small to mid size applications. With this,
you will get your BLL and DAL organized without the hazel of complex architectures and repetitive codes, while letting the UI layer float at developer discretion...
What is Nido??
Nido is a code framework (a common project, architectural pattern) written on .NET framework 4.0, Entity framework 6.0 and few other additional libraries to encourage you (we developers) to develop our systems adhering to good architectural disciplines.
Nido will continue to evolve and befits you.
Who is it for??
If you are seeking for a good architecture, to build your rich, modern web application or any other systems (Nido is good for Small to mid size systems), then Nido is made just for you. You can use ASP.NET, MVC as well as any other front end technology to
build your system with Nido.
Why should you use it??
Nido help you in many ways. It reduce software cost and the time you take to develop systems.
Each developer has their own way of writing code, each system is different from one to another. The Nido framework gives you a way of standardizing both the developers as well as the systems in architectural as well as coding patterns perspective. This way
no matter who develop what system, they all get developed in the same way.
Help yourself by loosely coupling you from the project you do. Do you noticed that the individual dependencies you have with your projects are stopping you from enjoying your weekends as well as your vacations? This is a way of maturing your development
center overtime while removing individual dependencies. This way, you are ready to take up any other code with having a 'zero' learning curve.
No! More!! Long!!! Days... at Work!!!!
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.
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.