Software Requirement Specification
Software Requirement Specification
4.1.1 Objective:
The objective of Online voting system is to help the organization in automating the
whole manual processing of the existing system.
The main objective to develop the system is to make the accurate & efficient decisions in
different tasks at different time at different situations. The existing system is manual so
members of the unit generally face a lot of embarrassing situations many times. Now they
need to automate the whole process so as to make it more easy and accurate.
System should support multi-user environment.
System should be fully automated.
System should provide concrete security features like creating users and assigning
privileges to users of the system.
System should be capable to keep track of all the detailed descriptions of the client and the
whole details of services offered by the client organization.
Various outputs (reports) should be available online any time.
System should be able to handle extremely large volumes of data (i.e. Large database
support)
4.1.2 Scope:-
It reduces the paper work and makes the work less tedious for ELESTION COMMISION.
Assembly
Assemblies are the building blocks of .NET Framework applications; they form the
fundamental unit of deployment, version control, reuse, activation scoping, and
security permissions. An assembly is a collection of types and resources that are
built to work together and form a logical unit of functionality. An assembly provides
the common language runtime with the information it needs to be aware of type
implementations. To the runtime, a type does not exist outside the context of an
assembly
The .NET runtime/Common Language Runtime (CLR) ships three different classes of
JITters. The Main JIT compiler converts the MSIL code it to native code with out any
optimizations. The JIT compiler takes the MSIL code and optimizes it. So this compiler
requires lot of resources like, time to compile, larger memory footprint, etc. The PreJIT
is based on the Main JIT and it works like the traditional compilers (compiles MSIL to
native code during compilation time rather than runtime). This compiler is usually used at
the time of installation.
No matter whatever language we used to develop the HelloWorld program, its a known
fact that compilers are going to generate a MSIL format, once our code has been
converted in to MSIL format, from MSIL format all the code that we write will be
converted to native code in the same way whether if it is a VB.NET source or C# source.
.
Debugging is the most important feature of any programming language and Visual Studio
NET IDE provides this feature in an effective manner (but you can still do pretty good.
job with the .NET SDK alone). Application source code goes through two distinct steps
before a user can run it. First, the source code is compiled to Microsoft Intermediate
Language (MSIL) code using a .NET compiler. Then, at runtime, the MSIL code is
compiled to native code. When we debug a .NET application, this process works in
reverse. The debugger first maps the native code to the MSIL code. The MSIL code is
then mapped back to the source code using the programmer's database (PDB) file. In
order to debug an application, these two mappings must be available to the .NET runtime
environment.
To accomplish the mapping between the source code and the MSIL, use
the/debug:pdbonly compiler switch to create the PDB file (Note: When building
ASP.NET applications, specify the compilation setting debug="true" in the applications
Web.config file). The second mapping between the MSIL code and native code is
accomplished by setting the JITTracking attribute in our assembly. By specifying the
/debug compiler switch, the PDB file is created and the JITTracking attribute is enabled.
When using this compiler switch, a debugger can be attached to an application loaded
outside of the debugger.
Once the required mappings exist, there are several means by which to debug our
applications. We can use the integrated debugger within Visual Studio .NET, or, if we
prefer, we can use DbgClr, a GUI-based debugger. There is also a command line
debugger, CorDBG that is included in the .NET Framework SDK.
Constants &Variables
A variable is a named memory location. They are programming elements that can change
during program execution. Data that needs to be stored in memory & accessed at a later
time are stored in variables. Instead of referring to the memory location by the actual
memory address you refer to it with a variable name.
Variables are declared as follows
Dim a as Integer
They can also be initialized at the time of declaration as follows:
Dim a as Integer = 10
Constants are very similar to variables. The main difference is that the value contained in
memory cannot be changed once the constant is declared. When you declare a constant
its value is also specified and this value cannot be changed during program execution.
Constants are used in situations where we need to keep the value in some memory
location constant. If you use hard-coded values, and the value is changed then it has to be
changed in all the locations in the code where it has been used. Instead if we are using
constants, all we will need to do is to change the value of the constant. This would
propagate the changes to our entire application.