Professional Documents
Culture Documents
A PROJECT REPORT
Submitted By
Shanwaz
Syed Shafi ur Rahman
Shuja Shabbir
Shubham Kumar Singh
Shivam Chabbra
for the award of the degree
of
BACHELOR OF TECHNOLOGY
IN
CERTIFICATE
This is to certify that the work contained in this project report entitled
“IIMSR STUDENT MANAGEMENT SYSTEM” by Shanwaz, Syed
Shafi ur Rahman , Shuja Shabbir,Shubham Kumar Singh,Shivam
Chabbra is a faithful record of work that has been carried out by the
students, under my supervision and the level of work is good for submission.
To the best of my/our knowledge, this work has not been submitted for
award of any degree or diploma to this University or elsewhere.
Miss.Minsha Jafar
Project Guide
Assistant Professor
C.S.E Department
Integral University
RECOMMENDATION
Shanwaz (1000112201)
Syed Shafi ur Rahman(1000112218)
Shuja Shabbir (1000112206)
Shubham Kumar Singh(1000112205)
Shivam Chabbra(1000112203)
ABSTRACT
1. Acknowledgement
2. Abstract
3. Table of content
4. List of Figure
5. List of Table
6. List of Symbols, Abbreviations and Nomenclature
7. Chapters
1 Introduction
2 Problem Identification & Feasibility Study
3 Requirement Analysis
4 Review of Previous work
5 Proposed Work (Framework or Algorithm)
6 Hardware & Software Specification
7 Design
Context Diagram
Data Flow Diagrams
Entity Relationship Diagrams
Flowchart
Snapshot of the Project
8. Result & Snapshot
9 Conclusion
10. References
11. Bio data of each group member
LIST OF FIGURE
IIMSR,
Shanwaz(1000112201)
Shuja Shabbir(1000112206)
Shivam Chabbra(1000112203)
have successfully completed the project on “IIMSR Student Management system” with
the following requirement as specified
INTRODUCTION
This project on “IIMSR Student Management System” is useful for easy user
interface. The system utilizes the powerful database management, data retrieval
and data manipulation. This project provides more ease for managing the data than
manually maintaining in the documents. The project is useful for saving valuable
time and reduces the huge paper work.
It will help educational Institutions like schools and colleges will keep track of
their student records like personal details,contact details,marks details, etc. The
Internet is rapidly becoming a part of the everyday lives of a majority of people in
the world. People perform various activities on the Internet and one of them is
storing their data in data-base where they are interested in. In these data base’s they
can post the queries and they can retrieve the required data. Obviously there is a
need of Student Information System software for management of student’s data.
For example when a student needs his course completion certificate it needs to
check many details about the student like his name, registration number, year of
study, exams he attended and many other details. So it needs to contact all the
modules that are office, department and examination and result of students.
Types of Feasibility
a) Technical Feasibility: During this study, the analyst identifies the existing
computer systems of the concerned department and determines whether
these technical resources are sufficient for the proposed system or not. If they are
not sufficient, the analyst suggests the configuration of the computer
systems that are required. The analyst generally pursues two or three different
configurations which satisfy the key technical requirements but which
represent different costs. During technical feasibility study, financial resources and
budget is also considered. The main objective of technical feasibility is to
determine whether the project is technically feasible or not, provided it is
economically feasible.
c) Operational Feasibility: When it is found that the project is both economic and
technical feasible, the next step is to detemine whether it is operationally feasible
or not. During operational feasibility study, it is operationally feasible or not,
During operational feasibility study, it is determined whether the system will
operate in the way that user wants or not. Operational feasibility depends upon
human resources for the development and implementation of the system. It is
considered whether the qualified or experienced manpower is available for
development and implementation of the system or not. User involvement is more
required in determining the operational feasibility.
REQUIREMENT ANALYSIS
1 Introduction
The following subsections are an overview of the entire Software Requirements
Specification (SRS).
1.1 Purpose
The document will not only define the product functions, user characteristics,
constraints, and specific requirements of the system, but also serve as a basis for
the Software Design Document that is prepared according to IEEE Std.
Accuracy
Reliability
No Redundancy
Easy to Operate
1.2 Scope
“STUDENT MANAGEMENT SYSTEM” is a project with a mission of viewing
and manipulating student information of IIMSR in a Web-based environment.
Thus, the overall system will consist of a Student Database System and Web
Interface.
The Student Database System will supply the fundamental database structure of the
entire system whereas Web Interface will provide a secure Web interface between
the users and the database.
The Software aims to create a “paperless office” rather than using a traditional
record keeping system.
Although this project is presently being designed specifically for Integral Institute
of Medical Sciences and Research but there exist the possibility in future to
upgrade it to general level.
The software will not only help the following levels of user in viewing the
information but also each user can alongside update changes within their
respective access limits.
Administrative Level
User Level
Management of Institute
Faculty
Students
Department Staff
1.3 Definition
Paperless Office: refers to an integrated working environment where all the data
and documentation is represented in electronic format.
Traditional Record Keeping System: refers to a manual system where all records
are kept on papers by manual in-charge.
1.4 References
1.5 Overview
This document is prepared in accordance with the IEEE Std, IEEE Recommended
Practice for Software Requirements Specifications.
2 Overall Description
This section describes the general factors that affect software and its requirements.
In order to be easily understandable, this part of SRS provides a background for the
requirements.
The interfaces will involve check boxes, combo boxes, text boxes, and radio
buttons. The combo boxes and the radio buttons will be used to prevent users from
entering wrong type of information. They will also enable fast data entry. Text
boxes will be controlled for avoiding invalid and inconsistent data.
Users can use “Tab” key to move cursor on screen items easily.
There will be two types of messages for constructive advice to the users: error and
confirmation messages. There will be four types of error messages for application
control: input, output, process and database/Web server error messages.
There will be several types of users, and each user will access the screens
according to their types after entering their id and passwords. Standard screen
format (fixed colors, fonts, background, the page layout, etc.) will be used
throughout the interfaces.
The language of the user interfaces will be English.
The client computer, which runs the web browser, should have enough physical
memory to run this program.
User- The other user like staff or faculty can view only their individual report and
analyze their own performance based on that.
2.4 Assumptions
Every user will be having the appropriate hardware and software configuration as
per the necessary requirement.
3 Specific Requirements
The software is meant to generate a student id which will provide unique identity
to individual students. It is through this student id that each students data can
accessed on this platform.The requirements under Student Management System are
to maintain information relevant to the following fields:
Students Profile- The full information of each and every student must be
maintained in System along with the facility to regularly update it from time
to time at regular intervals which will be easily possible through each
students unique id.
Accuracy
Reliability
No Redundancy
Easy to Operate
Reliability
The system has to operate in a reliable manner with no scope for any flaws. This is
to ensure efficient working and processing of information.
Availability
The site should be available all the time without any issues. A backup must be
available for recovery issues so that the existing is not lost in case of any issue.
Security
The system has an authorization mechanism for users to identify their personal
profiles. Therefore, different users will have different authorization levels to access
the data. Data integrity for critical variables will also be checked.
Maintainability
The system can meet the changing requirements easily, since the infrastructure of
the system would not need major changes. The requirements of the software while
evolving, will be met by just adding new sub-functions. Therefore, the
maintainability of the system would not be a complex issue.
Portability
All of the code which will be deployed at the web server will be written in
ASP.Net 4.5 and using SQL Server for database storage. So, using IIS(Internet
Information Server) the software will remain portable.
PLATFORM
(TECHNOLOGIES/TOOLS)
Visual Studio .NET ships with languages such as Visual Basic .NET,
Visual C#, and Visual C++ with managed extensions, as well as the
J Script scripting language. You can also write managed code for the
-NET Framework in other languages. Third-party tools and compilers.
To understand how the common language runtime manages code execution, you
must examine the structure of a .NET application. The primary unit of a NET
application is the assembly. An assembly is a self-describing collection of code,
resources, and metadata. The assembly manifest contains information about what
is contained within the assembly. The assembly manifest provides:
Each assembly has one and only one assembly manifest, and it contains all the
description infomiation for the assembly. However, the assembly manifest can be
contained in its own file or within one of the assembly’s modules.
An assembly contains one or more modules. A module contains the code that
makes up your application or library, and it contains metadata that describes that
code. When you compile a project into an assembly, your Code is converted from
high-level code to IL. Because all managed code is first converted to IL code,
applications written in different languages can easily interact. For example, one
developer might write an application in visual C# that accesses a DLL in Visual
Basic .Net. Both resources will be converted to IL modules before being executed,
thus avoiding any language interoperability issues.
Each module also contains a number of types. Types are templates that describe a
set of data encapsulation and functionality. There are two kinds of types: reference
types (classes) and value types (structures).
When you compile a .NET application it is not compiled to binary machine code;
rather it is converted to Intermediate language. This is the form that your deployed
application takes-one or more assemblies consisting of executable files and DLL
files in IL form. At least one of these assemblies will contain an executable file
that has been designed as an entry point of an application.
Thus, each portion of code is compiled only once when an application executes.
Whenever program execution branches to code that has not yet run, the
JIT compiler compiles it ahead of execution and stores it in memory as
binary code. This way, application performance is maximized because
only the parts of a program that are executed are compiled.
.NET FRAMEWORK
DESIGN:
1) Interoperability:
Because computer systems commonly require interaction between newer
and older applications, .NET Framework provides means to access
functionality implemented in newer and older programs that execute outside
.NET environment. Access to COM components is provided in the
System.Runtime.InteropServices and System.EnterpriseServices namespaces
of the framework; access to other functionality is achieved using
the P/Invoke feature.
3) Language independence:
.NET Framework introduces a Common Type System, or CTS. The
CTS specification defines all possible data types and programming
constructs supported by the CLR and how they may or may not interact with
each other conforming to the Common Language Infrastructure (CLI)
specification. Because of this feature, .NET Framework supports the
exchange of types and object instances between libraries and applications
written using any conforming .NET language.
5) Simplified deployment:
.NET Framework includes design features and tools which help manage
the installation of computer software to ensure it does not interfere with
previously installed software, and it conforms to security requirements.
6) Security:
The design addresses some of the vulnerabilities, such as buffer overflows,
which have been exploited by malicious software. Additionally, .NET
provides a common security model for all applications.
7) Portability:
While Microsoft has never implemented the full framework on any system
except Microsoft Windows, it has engineered the framework to be platform-
agnostic, and cross-platform implementations are available for other
operating systems (see Silverlight and the Alternative
implementations section below). Microsoft submitted the specifications for
the Common Language Infrastructure (which includes the core class
libraries, Common Type System, and the Common Intermediate Language),
the C# language, and the C++/CLI language to both ECMA and the ISO,
making them available as official standards. This makes it possible for third
parties to create compatible implementations of the framework and its
languages on other platforms.
ARCHITECTURE:
2) SECURITY:
.NET has its own security mechanism with two general features: Code
Access Security (CAS), and validation and verification. Code Access
Security is based on evidence that is associated with a specific assembly.
Typically the evidence is the source of the assembly (whether it is installed
on the local machine or has been downloaded from the intranet or Internet).
Code Access Security uses evidence to determine the permissions granted to
the code. Other code can demand that calling code is granted a specified
permission. The demand causes the CLR to perform a call stack walk: every
assembly of each method in the call stack is checked for the required
permission; if any assembly is not granted the permission a security
exception is thrown.
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING. , INTEGRAL UNIVERSITY Page
IIMSR STUDENT MANGMENT SYSTEM 2014
3) CLASS LIBRARY:
.NET Framework includes a set of standard class libraries. The class library
is organized in a hierarchy of namespaces. Most of the built-in APIs are part
of either System.* or Microsoft.* namespaces. These class libraries
implement a large number of common functions, such as file reading and
writing, graphic rendering, database interaction, and XML document
manipulation, among others. .NET class libraries are available to all CLI
compliant languages. .NET Framework class library is divided into two
parts: the Framework Class Library and the Framework Class Library
The Framework Class Library (FCL) includes a small subset of the entire
class library and is the core set of classes that serve as the basic API of
the Common Language Runtime.
The Framework Class Library (FCL) is a superset of the FCL classes and
refers to the entire class library that ship with .NET Framework. It includes
an expanded set of libraries, including Windows
Forms, ADO.NET, ASP.NET, Language Integrated Query, Windows
Presentation Foundation, Windows Communication Foundation among
others. The FCL is much larger in scope than standard libraries for
languages like C++, and comparable in scope to the standard libraries of
Java.
4) Memory Management:
.NET Framework CLR frees the developer from the burden of
managing memory (allocating and freeing up when done); it
handles memory management itself by detecting when memory
can be safely freed. Instantiations of .NET types (objects) are
allocated from the managed heap; a pool of memory managed by
the CLR. As long as there exists a reference to an object, which
might be either a direct reference to an object or via a graph of
objects, the object is considered to be in use. When there is no
reference to an object, and it cannot be reached or used, it becomes
garbage, eligible for collection. .NET Framework includes
a garbage collector which runs periodically, on a separate thread
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING. , INTEGRAL UNIVERSITY Page
IIMSR STUDENT MANGMENT SYSTEM 2014
TECHNOLOGY USED
MICROSOFT FRAMEWORK:-
Features:
Easy deployment
Dynamic update of running application
XML web services
Flexible language option
Great tool support
Rich output caching
Enhanced reliability
Compiled execution
Easy programming mode
Enterprise manager is the main administrative console for sql server installation.
We can perform high level administrative function that affects one or more servers,
schedule common maintenance tasks or create & modify the structure of individual
database. Query analyzer offers a quick & dirty method for performing query
against sql server database. SQL profiler provides a window into inner working of
our database. Service manager is used to Ms-SQL servers, Ms-Distributed
transaction co-coordinator & sql server agent processes. Data transformation
services provides an extremely data between a Microsoft sql server installation &
large variety of other formats.
Features:
Database mirroring
Online restore opportunity
Online indexing operations
SQL-server management studio
Native XML support
Security enhancement
PROPOSED WORK
Student Information System is a software where students details are been setup by
an accountant and marks are been setup by teacher. Required data is been retrieved
by the principal. This system is a hierarchical structure. It contains certain numbers
of actors. Each will have their respective actions. Students are to be registered
dynamically. For each of the actor to perform their action, they must be logged in
with their respective ids. It is a web application managing student’s generated
content. Earlier versions were to store the details of student. Here updating,
retrieving actions are also been performed.
The proposed system is very user friendly, providing 3 actors. Administrator for
registering a student, teacher for adding and updating marks of a student. Where as
a student can retrieve the required data relevant to himself only.
Software:
Front End : ASP.NET 4.5 With C# (Visual
Studio 2012)
Back End : SQL Server 2008
Web Server : IIS 7.0 or above (Internet
Information Server)
Documentation Tool : Microsoft Office
Hardware:
TESTING
White-Box testing
White-box testing (also known as clear box testing, glass box testing,
transparent box testing and structural testing) tests internal structures or
workings of a program, as opposed to the functionality exposed to the end-user. In
white-box testing an internal perspective of the system, as well as programming
skills, are used to design test cases. The tester chooses inputs to exercise paths
through the code and determine the appropriate outputs. This is analogous to
testing nodes in a circuit, e.g. i ‐ ir uit testi g (ICT).
Black-box testing
and requirements, i.e., what the application is supposed to do. It uses external
descriptions of the software, including specifications, requirements, and designs to
derive test cases. These tests can be fu tio al or o ‐fu tio al, though usually
functional.
Ad ho testi g and e plorator testi g are important methodologies for checking
software integrity, because they require less preparation time to implement, while
the important bugs can be found quickly. In adhoc testing, where testing takes
place in an improvised, impromptu way, the ability of a test tool to visually record
everything that occurs on a system becomes very important
Grey-box testing
Grey-box testing involves having knowledge of internal data structures and
algorithms for purposes of designing tests, while executing those tests at the user,
or black-box level. The tester is not required to have full access to the software's
source code. Manipulating input data and formatting output do not qualify as grey-
box, because the input and output are clearly outside of the "black box" that we are
calling the system under test. This distinction is particularly important when
conducting i tegratio testi g between two modules of code written by two
different developers, where only the interfaces are exposed for test.
TESTING LEVELS
There are generally four recognized levels of tests: unit testing, integration testing,
system testing, and acceptance testing. Tests are frequently grouped by where they
are added in the software development process, or by the level of specificity of the
test. The main levels during the development process as defined are unit-,
integration-, and system testing that are distinguished by the test target without
implying a specific process model. Other test levels are classified by the testing
objective.
Unit Testing
Unit testing, also known as component testing, refers to tests that verify the
functionality of a specific section of code, usually at the function level. In an
object-oriented environment, this is usually at the class level, and the minimal unit
tests include the constructors and destructors.
These types of tests are usually written by developers as they work on code (white-
box style), to ensure that the specific function is working as expected. One function
might have multiple tests, to catch or er ases or other branches in the code. Unit
testing alone cannot verify the functionality of a piece of software, but rather is
used to assure that the building blocks the software uses work independently of
each other.
Integration testing
Integration testing is any type of software testing that seeks to verify the interfaces
between components against a software design. Software components may be
integrated in an iterative way or all together ("big bang"). Normally the former is
considered a better practice since it allows interface issues to be located more
quickly and fixed.
Integration testing works to expose defects in the interfaces and interaction
between integrated components (modules). Progressively larger groups of tested
software components corresponding to elements of the architectural design are
integrated and tested until the software works as a system.
System testing
Acceptance testing
Regression testing
Regression testing focuses on finding defects after a major code change has
occurred. Specifically, it seeks to uncover soft are regressio s, as degraded or
lost features, including old bugs that have come back. Such regressions occur
whenever software functionality that was previously working, correctly, stops
working as intended. Typically, regressions occur as an u i te ded o se ue e
of program changes, when the newly developed part of the software collides with
the previously existing code. Common methods of regression testing include re-
running previous sets of test-cases and checking whether previously fixed faults
have re-emerged. The depth of testing depends on the phase in the release process
and the risk of the added features.
Alpha testing
Alpha testing is simulated or actual operational testing by potential
users/customers or an independent test team at the developers' site. Alpha testing is
often employed for off-the-shelf software as a form of internal acceptance testing,
before the software goes to beta testing
Beta testing
Beta testing comes after alpha testing and can be considered a form of external
user a epta e testi g. Versions of the software, known as eta ersio s, are
released to a limited audience outside of the programming team. The software is
released to groups of people so that further testing can ensure the product has few
faults or ugs. Sometimes, beta versions are made available to the open public to
increase the feed a k field to a maximal number of future users.
Top Down Testing is an approach to integrated testing where the top integrated
modules are tested and the branch of the module is tested step by step until the end
of the related module.
In both, ethod stu s and drivers are used to stand-in for missing components and
are replaced as the levels are completed.
MAINTENANCE
Software maintenance in soft are e gi eeri g is the modification of a software
product after delivery to correct faults, to improve performance or other attributes.
A common perception of maintenance is that it merely involves fixing defe ts.
However, one study indicated that the majority, over 80%, of the maintenance
effort is used for non-corrective actions. This perception is perpetuated by users
submitting problem reports that in reality are functionality enhancements to the
system. More recent studies put the bug-fixing proportion closer to 21%.
IMPLEMENTATION
DESIGN
LEVEL 0 DFD:
Level 1 DFD:
ER DIAGRAM:
FLOWCHART:
TABLES IN DATABASE
Academic Session
Admin Table
Exam marks
Attendance Table
Faculty Table
Time Table
SNAPSHOT OF PROJECT
Home Page
About
Gallery
Faculty Registration
Future Scope
Such a web based platform has immense potential for future growth not only for
students but also for faculty as well as department concerned in improving upon
their efficiency of work with no or less burden. Some of the areas where future
scope lies and if implemented would help a great deal to the students at large.
Also, it would be possible for students to watch lectures in the form of video
content which would facilitate easy access to study material.
CONCLUSION
REFERENCES
BOOKS REFERRED:
WEBSITES REFERRED:
1. www.google.com
2. www.wikipedia.com
3. www.w3schools.com
4. www.aspforums.net
5. www.forums.tutorialized.com
6. www.youtube.com