Functional requirements define the internal workings of the software: i.e., the calculations, technical details, data manipulation and processing and other specific functionality that show how the use cases are to be satisfied. They are supported by non-functional requirements, which impose constraints on the design or implementation.
·          The internal data manipulations are handled by the in built ADO.NET engine while programming and as we use SQL queries to access/manipulate data, RDBMS concepts come into action provided by System.Data.Oledb namespace.
·          The e-mail functionality is provided by the System.Web.Mail namespace and allows users to send/receive e-mails using SMTP standards.
·          Several other standard DotNet components are also used in programming functionality of the project.
·          Since the project is built on top of Dotnetfx 2.0, it is completely stable in memory handling as it runs in managed environment.
·          In built & robust exception handling helps to catch unwanted bugs in application.
·          As it can be noticed, the project is platform independent. It can be run on all WIN32 systems that support Dotnetfx, and on all Mac/Linux systems using Mono, an open source implementation of the Dotnetfx.
Non-functional requirements are requirements which specify criteria that can be used to judge the operation of a system, rather than specific behaviors. This should be contrasted with functional requirements that specify specific behavior or functions. Typical non-functional requirements are reliability, scalability, and cost. 
            As mentioned earlier the project is build at no extra cost by making use of all free & open source technologies and the hardware requirements provided by our institution.