Important: Use custom search function to get better results from our thousands of pages

Use " " for compulsory search eg:"electronics seminar" , use -" " for filter something eg: "electronics seminar" -"/tag/" (used for exclude results from tag pages)
Tags: student, management, system, full, report, student management system, student management system ppt, student management system pdf, student management system project, student management system project in java, student management system in .net, student management system in vb, student management system project in c++, student management system dfd, student management system documentation, student management system er diagram, student management system srs,
Ask More Info Of  A Seminar Ask More Info Of A Project Post Reply  Follow us on Twitter
26-02-2010, 11:06 PM
Post: #1
student management system full report

.doc  STUDENT MANAGEMENT SYSTEM.doc (Size: 770.5 KB / Downloads: 7534)

STUDENT MANAGEMENT SYSTEM
PROJECT REPORT
Submitted by
FALCON FRANCIS MANJU V RAVINDRAN
RANJITH KIRAN K VINU K THANKACHAN
ABSTRACT
Student Management System deals with all kind of student details, academic related reports, college details, course details, curriculum, batch details and other resource related details too. It tracks all the details of a student from the day one to the end of his course which can be used for all reporting purpose, tracking of attendance, progress in the course, completed semesters years, coming semester year curriculum details, exam details, project or any other assignment details, final exam result; and all these will be available for future references too.
Our program will have the databases of Courses offered by the college under all levels of graduation or main streams, teacher or faculty's details, batch execution details, students' details in all aspects.
This program can facilitate us explore all the activities happening in the college, even we can get to know which teacher / faculty is assigned to which batch, the current status of a batch, attendance percentage of a batch and upcoming requirements of a batch.
Different reports and Queries can be generated based of vast options related to students, batch, course, teacher / faculty, exams, semesters, certification and even for the entire college.
TABLE
SMS_College SMS_Category SMS_Login SMS_Sub SMSStudacademic SMS_Studpersonal SMS_Examdetail SMS_Finalreport SMS_Studparti
LIST OF TABLES
PAGE NUMBER
2 3 3 3 5 5 8 8 9
LIST OF FIGURES
NAME OF FIGURES
LEVEL 1 DFD LEVEL 2 DFD COLLEGE DETAILS DEPARTMENT DETAILS SIGNUP DETAILS
SIGNIN DETAILS
CHANGE PASSWORD
SUBJECT DETAILS PERSONAL DETAILS
PARENT DETAILS ACADEMIC DETAILS EXAM DETAILS STUDENT PARTICULARS FINAL REPORT
PAGE NUMBER
31
31
32
33
34
35
36
37
38
39
40
41
43
44
CHAPTER 1
INTRODUCTION
About the project
The student management system is an automated version of manual Student Management System. It can handle all details about a student. The details include college details, subject details, student personnel details, academic details, exam details etc...
In case of manual system they need a lot of time, manpower etc.Here almost all work is computerized. So the accuracy is maintained. Maintaining backup is very easy. It can do with in a few minutes. Our system has two type of accessing modes, administrator and user. Student management system is managed by an administrator. It is the job of the administrator to insert update and monitor the whole process. When a user log in to the system. He would only view details of the student. He can't perform any changes .The system has four modules. They are
College and Department details
Login and subject
Student Details
Exam Details
CHAPTER 2 MODULES
Student Management System is expected to maintain a number of details. The needed modules are given below.
College and Department details
This module deals with the college details and different departments in the college. The college details are stored in the table SMSCollege. And department details are stored in SMSCategory. It deals with the details of college and department. TABLE: SMSCollege
Field Constraints
SMS_Coll_Collegeid varchar(50) Not Null
SMS_Coll_Collegename varchar(300) Not Null
SMS_Coll_Address varchar(300) Not Null
SMS_Coll_Pincode varchar(50) Not Null
SMS_Coll_District varchar(50) Not Null
SMS_Coll_State varchar(50) Not Null
SMS_Coll_Phone1 varchar(50) Not Null
SMS_Coll_Phone2 varchar(50) Not Null
SMS_Coll_Fax varchar(50) Not Null
SMS_Coll_Email varchar(100) Not Null
SMS_Coll_Website varchar(100) Not Null
SMS_Coll_Emblem varchar(100) Not Null
This table is used to store the details of college like college name, address, phone numbers, fax, e¬mail id, website. This table is filled at first.
This table is used to store the details of different department and its category. Category specifies the course is bachelor or master degree. Department gives the various departments. Duration specifies the number of semesters.
Login and subject
This module based with the login process and subject details. The login process specifies the user mode such as administrator or user. This module consist of two tables, SMSLogin and SMSSub . It contains the details of login process and subject details. Login process includes sign in sign up, sign out, change password.
TABLE: SMS_Login
Field Constraints
SMS_Log_Category varchar(50) Not Null
SMS_Log_Department varchar(50) Not Null
SMS_Log_Username varchar(20) Not Null
SMS_Log_Password varchar(20) Not Null
SMS_Log_Privilege varchar(20) Not Null
The table stores the values like category, department, username, password and privilege. The privilege specifies the user mode is administrator or user.
TABLE: SMS_Sub
Field Constraints
SMS_Sub_Category varchar(50) Not Null
SMS_Sub_Department varchar(50) Not Null
SMS_Sub_Semester varchar(50) Not Null
SMS_Sub_Noofsubjects int Not Null
SMS_Sub_Sub1 varchar(50)
SMS_Sub_Code1 varchar(50)
SMS_Sub_Sub2 varchar(50)
SMS_Sub_Code2 varchar(50)
SMS_Sub_Sub3 varchar(50)
SMS_Sub_Code3 varchar(50)
SMS_Sub_Sub4 varchar(50)
SMS_Sub_Code4 varchar(50)
SMS_Sub_Sub5 varchar(50)
SMS_Sub_Code5 varchar(50)
SMS_Sub_Sub6 varchar(50)
SMS_Sub_Code6 varchar(50)
SMS_Sub_Sub7 varchar(50)
SMS_Sub_Code7 varchar(50)
SMS_Sub_Sub8 varchar(50)
SMS_Sub_Code8 varchar(50)
SMS_Sub_Sub9 varchar(50)
SMS_Sub_Code9 varchar(50)
SMS_Sub_Sub10 varchar(50)
SMS_Sub_Code10 varchar(50)
SMS_Sub_Sub11 varchar(50)
SMS_Sub_Code11 varchar(50)
SMS_Sub_Sub12 varchar(50)
SMS_Sub_Code12 varchar(50)
This table shows the details of the category, department, semester, and number of subjects in semester and different subjects in various department and semesters.
Student Details
This module deals with the student academic details and personnel details. This module consists of the tables SMSStudacademic and SMSStudpersonal.
TABLE: SMS_Studacademic
Field Constraints
SMS_Studaca_Admino varchar(50) Not Null
SMS_Studaca_Batch varchar(50) Not Null
SMS_Studaca_Category varchar(50) Not Null
SMS_Studaca_Department varchar(50) Not Null
SMS_Studaca_Sem varchar(50) Not Null
SMS_Studaca_Name varchar(50) Not Null
SMS_Studaca_Edulquali 1 varchar(50)
SMS_Studaca_Percentage1 float
SMS_Studaca_Edulquali2 varchar(50)
SMS_Studaca_Percentage2 float
SMS_Studaca_Entrancerank varchar(50)
SMS_Studaca_Photo varchar(50)
This table shows the values like admission number, batch, category, department, joining semester, his/her name, their qualifications, entrance rank and photo.
SMS_Studper_Dayscholororhostler varchar(50)
SMS_Studper_Studentemail varchar(50)
SMS_Studper_Temadd varchar(200)
SMS_Studper_Temphone1 varchar(50)
SMS_Studper_Peradd varchar(200)
SMS_Studper_Perphone1 varchar(50)
SMS_Studper_Fathername varchar(50)
SMS_Studper_Fatheraddress varchar(200)
SMS_Studper_Fatherphone varchar(50)
SMS_Studper_Fatherj ob varchar(50)
SMS_Studper_Foffadd varchar(200)
SMS_Studper_Foffphone varchar(50)
SMS_Studper_Mothername varchar(50)
SMS_Studper_Motheraddress varchar(200)
SMS_Studper_Motherphone varchar(50)
SMS_Studper_Motherj ob varchar(50)
SMS_Studper_Moffadd varchar(200)
SMS_Studper_Moffphone varchar(50)
SMS_Studper_Annualincome varchar(50)
This table stores the admission number, the personnel details like date of birth, religion, cast, gender, blood group, day scholar or hosteller, e-mail, address, parent details and annual income.
Exam Details
This module deals with the student exam details, student particular such as various activities, final report. The tables comes in this modules are SMSExamdetail, SMSFinalreport and SMSStudparti.
TABLE: SMS_Examdetail
Field Constraints
SMS_Exam_Studcode varchar(50) Not Null
SMS_Exam_Regno varchar(50)
SMS_Exam_Sem varchar(50)
SMS_Exam_Monthandyear varchar(50)
SMS Exam Internalmax varchar(50)
SMS Exam Externalmax varchar(50)
SMS Exam Externalminimum varchar(50)
SMS_Exam_Total varchar(50)
SMS_Exam_Pa ssout varchar(50)
SMS_Exam_Sub1 varchar(50)
SMS_Exam_Emark1 varchar(50)
SMS_Exam_Imark1 varchar(50)
SMS_Exam_Total1 varchar(50)
SMS_Exam_Sub2 varchar(50)
SMS_Exam_Emark2 varchar(50)
SMS_Exam_Imark2 varchar(50)
SMS_Exam_Total2 varchar(50)
SMS_Exam_Sub3 varchar(50)
SMS Exam Emark3 varchar(50)
SMS_Exam_Imark3 varchar(50)
SMS_Exam_Total3 varchar(50)
SMS_Exam_Sub4 varchar(50)
SMS_Exam_Emark4 varchar(50)
SMS_Exam_Imark4 varchar(50)
SMS_Exam_Total4 varchar(50)
SMS_Exam_Sub5 varchar(50)
SMS Exam Emark5 varchar(50)
SMS_Exam_Imark5 varchar(50)
SMS_Exam_Total5 varchar(50)
SMS_Exam_Sub6 varchar(50)
SMS Exam Emark6 varchar(50)
SMS_Exam_Imark6 varchar(50)
SMS_Exam_Total6 varchar(50)
SMS_Exam_Sub7 varchar(50)
SMS_Exam_Emark7 varchar(50)
SMS_Exam_Imark7 varchar(50)
SMS_Exam_Total7 varchar(50)
SMS_Exam_Sub8 varchar(50)
SMS_Exam_Emark8 varchar(50)
SMS_Exam_Imark8 varchar(50)
SMS_Exam_Total8 varchar(50)
SMS_Exam_Sub9 varchar(50)
SMS_Exam_Emark9 varchar(50)
SMS_Exam_Imark9 varchar(50)
SMS_Exam_Total9 varchar(50)
SMS_Exam_Sub10 varchar(50)
SMS_Exam_Emark10 varchar(50)
SMS_Exam_Imark10 varchar(50)
SMS_Exam_Total10 varchar(50)
SMS_Exam_Sub11 varchar(50)
SMS_Exam_Emark11 varchar(50)
SMS_Exam_Imark11 varchar(50)
SMS_Exam_Total11 varchar(50)
SMS_Exam_Sub12 varchar(50)
SMS_Exam_Emark12 varchar(50)
SMS_Exam_Imark12 varchar(50)
SMS_Exam_Total12 varchar(50)
This table stores the values stud code, register number, semester, month and year of exam, internal and external maximum marks, the marks obtained for various subjects like its internal, external and total mark. This table gives the performance of students in various exams.
TABLE: SMS_Finalreport
Field Constraints
SMS_Final_Adminno varchar(50) Not Null
SMS_Final_Miniproj ectworkdone varchar(MAX)
SMS_Final_Mainproj ectworkdone varchar(MAX)
SMS_Final_Techinicalactivity varchar(50)
SMS_Final_Neatness varchar(50)
SMS_Final_Characterandconduct varchar(50)
SMS_Final_Remarks varchar(50)
Constraints
Not Null Not Null
This table stores the values of admission number, mini project done, main project done, technical activities, neatness and standard of lab record, character and conduct and remarks.
TABLE: SMS_Studparti
Field
SMS_Studaca_Admino varchar(50)
SMS_Studparti_sem varchar(50)
SMS_Studparti_arts varchar(50)
SMS_Studparti_athletics varchar(50)
SMS_Studparti_games varchar(50)
SMS_Studparti_scholarship varchar(50)
SMS_Studparti_disaction varchar(50)
SMS_Studparti_cour se star varchar(50)
SMS_Studparti_tutor varchar(50)
This table stores the values of extra curricular details, admission number , scholarship, disciplinary action , starting of course, tutor.
CHAPTER 3 SYSTEM STUDY
System study aims at establishing requests for the system to be acquired, developed and installed. It involves studying and analyzing the ways of an organization currently processing the data to produce information. Analyzing the problem thoroughly forms the vital part of the system study. In system analysis, prevailing situation of problem carefully examined by breaking them into sub problems. Problematic areas are identified and information is collected. Data gathering is essential to any analysis of requests. It is necessary that this analysis familiarizes the designer with objectives, activities and the function of the organization in which the system is to be implemented.
3.1 STUDY OF EXISTING SYSTEM
Today in colleges student details are entered manually. The student details in separate records are tedious task. Referring to all these records and updating is needed. There is a chance for more manual errors.
3.2 PROPOSED SYSTEM
By developing the system we can attain the following facilities.
> Easy to handle and feasible.
> Cost reduction.
> Fast and convenient.
3.3 INTRODUCTION TO .NET
This proposed software is going to be developed using the latest technology from Microsoft called Microsoft. NET and it is the software that connects information, people, systems, and devices. It spans clients, servers, and developer tools, and consists of:
¢ The .NET Framework 1.1, used for building and running all kinds of software, including Web-based applications, smart client applications, and XML Web services”components that facilitate integration by sharing data and functionality over a network through standard, platform-independent protocols such as XML (Extensible Markup Language), SOAP, and HTTP.
¢ Developer tools, such as Microsoft Visual Studio.NET 2003, which provides an integrated
development environment (IDE) for maximizing developer productivity with the .NET Framework.
¢ A set of servers, including Microsoft Windows Server 2003, Microsoft SQL Server, and Microsoft BizTalk Server, that integrates, runs, operates, and manages Web services and Web-based applications.
Client software, such as Windows XP, Windows CE, and Microsoft Office XP, that helps developers deliver a deep and compelling user experience across a family of devices and existing products
3.3.1 ADVANTAGES OF NET
The .NET Framework offers a number of advantages to developers. The following paragraphs describe them in detail.
3.3.1.1 Consistent programming model
Different programming languages have different approaches for doing a task. For example, accessing data with a VB 6.0 application and a VC++ application is totally different. When using different programming languages to do a task, a disparity exists among the approach developers use to perform the task. The difference in techniques comes from how different languages interact with the underlying system that applications rely on.
With .NET, for example, accessing data with a VB .NET and a C# .NET looks very similar apart from slight syntactical differences. Both the programs need to import the System. Data namespace, both the programs establish a connection with the database and both the programs run a query and display the data on a data grid. The VB 6.0 and VC++ example mentioned in the first paragraph explains that there is more than one way to do a particular task within the same language. The .NET example explains that there's a unified means of accomplishing the same task by using the .NET Class Library, a key component of the .NET Framework.
The functionality that the .NET Class Library provides is available to all .NET languages resulting in a consistent object model regardless of the programming language the developer uses.
3.3.1.2 Direct support for security
Developing an application that resides on a local machine and uses local resources is easy. In this scenario, security isn't an issue as all the resources are available and accessed locally. Consider an application that accesses data on a remote machine or has to perform a privileged task on behalf of a nonprivileged user. In this scenario security is much more important as the application is accessing data from a remote machine.
With .NET, the Framework enables the developer and the system administrator to specify method level security. It uses industry-standard protocols such as TCP/IP, XML, SOAP and HTTP to facilitate distributed application communications. This makes distributed computing more secure because .NET developers cooperate with network security devices instead of working around their security limitations.
3.3.1.3 Simplified development efforts
Let's take a look at this with Web applications. With classic ASP, when a developer needs to present data from a database in a Web page, he is required to write the application logic (code) and presentation logic (design) in the same file. He was required to mix the ASP code with the HTML code to get the desired result.
ASP.NET and the .NET Framework simplify development by separating the application logic and presentation logic making it easier to maintain the code. You write the design code (presentation logic) and the actual code (application logic) separately eliminating the need to mix HTML code with ASP code. ASP.NET can also handle the details of maintaining the state of the controls, such as contents in a textbox, between calls to the same ASP.NET page.
Another advantage of creating applications is debugging. Visual Studio .NET and other third party providers provide several debugging tools that simplify application development. The .NET Framework simplifies debugging with support for Runtime diagnostics. Runtime diagnostics helps you to track down bugs and also helps you to determine how well an application performs. The .NET Framework provides three types of Runtime diagnostics: Event Logging, Performance Counters and tracing.
3.3.1.4 Easy application deployment and maintenance
The .NET Framework makes it easy to deploy applications. In the most common form, to install an application, all you need to do is copy the application along with the components it requires into a directory on the target computer. The .NET Framework handles the details of locating and loading the components an application needs, even if several versions of the same application exist on the target computer. The .NET
Framework ensures that all the components the application depends on are available on the computer before the application begins to execute.
3.3.2 NET FRAMEWORK
The Microsoft .NET Framework is a software component that can be added to or is included with the Microsoft Windows operating system. It provides a large body of pre-coded solutions to common program requirements, and manages the execution of programs written specifically for the framework. The .NET Framework is a key Microsoft offering, and is intended to be used by most new applications created for the Windows platform.
The pre-coded solutions that form the framework's class library cover a large range of programming needs in areas including: user interface, data access, database connectivity, cryptography, web application development, numeric algorithms, and network communications. The functions of the class library are used by programmers who combine them with their own code to produce applications.
Programs written for the .NET Framework execute in a software environment that manages the program's runtime requirements. This runtime environment, which is also a part of the .NET Framework, is known as the Common Language Runtime (CLR). The CLR provides the appearance of an application virtual machine, so that programmers need not consider the capabilities of the specific CPU that will execute the program. The CLR also provides other important services such as security mechanisms, memory management, and exception handling. The class library and the CLR together compose the .NET Framework. The framework is intended to make it easier to develop computer applications and to reduce the vulnerability of applications and computers to security threats.
First released in 2002, it is included with Windows XP SP2, Windows Server 2003 and Windows Vista, and can be installed on most older versions of Windows.
Microsoft .NET Framework was designed with several intentions:
¢ Interoperability - Because interaction between new and older applications is commonly required, the .NET Framework provides means to access functionality that is implemented in programs that execute outside the .NET environment. Access to COM components is provided in the System.Runtime.InteropServices and System.EnterpriseServices namespaces of the framework, and access to other functionality is provided using the P/Invoke feature.
¢ Common Runtime Engine - Programming languages on the .NET Framework compile into an intermediate language known as the Common Intermediate Language, or CIL (formerly known as Microsoft Intermediate Language, or MSIL). In Microsoft's implementation, this intermediate language is not interpreted, but rather compiled in a manner known as just-in-time compilation (JIT) into native code. The combination of these concepts is called the Common Language Infrastructure (CLI), a specification; Microsoft's implementation of the CLI is known as the Common Language Runtime (CLR).
¢ Language Independence - The .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. Because of this feature, the .NET Framework supports development in multiple programming languages. This is discussed in more detail in the .NET languages section below.
¢ Base Class Library - The Base Class Library (BCL), sometimes referred to as the Framework Class Library (FCL), is a library of types available to all languages using the .NET Framework. The BCL provides classes which encapsulate a number of common functions, including file reading and writing, graphic rendering, database interaction and XML document manipulation.
¢ Simplified Deployment - Installation of computer software must be carefully managed to ensure that it does not interfere with previously installed software, and that it conforms to increasingly stringent security requirements. The .NET framework includes design features and tools that help address these requirements.
¢ Security - .NET allows for code to be run with different trust levels without the use of a separate sandbox.
A design goal of the .NET Framework was to support platform independence[citation needed]. That is, a program written to use the framework should run without change on any type of computer for which the framework is implemented. However, Microsoft has only implemented the full .NET framework on the Windows operating system. Microsoft and others have implemented portions of the framework on non-Windows systems, but to date these implementations are neither complete nor widely used, so full cross-platform support has not been achieved.
3.4 INTRODUCTION TO SQL SERVER 2005
Microsoft SQL Server 2005 is comprehensive, integrated data management and analysis software that enables organizations to reliably manage mission-critical information and confidently run today's increasingly complex business applications. SQL Server 2005 allows companies to gain greater insight from their business information and achieve faster results for a competitive advantage. SQL Server 2005 is the Data Platform leader:
¢ SQL Server is the fastest growing Database and Business Intelligence vendor.
¢ SQL Server ships more units than Oracle and IBM combined.
¢ SQL Server is the #1 OLAP Server on the market.
¢ SQL Server is more secure than Oracle. Since July 2003 more than 100 critical Oracle database security vulnerabilities have been identified, compared to ZERO for SQL Server for that period.
¢ SQL Server is a benchmark leader, with the best price/performance for TPC-H 1TB & 3TB (non-clustered) as well as best performance for TPC-H 1TB.
¢ Gartner 2006 worldwide RDBMS market share reports highest growth rate in market share for Microsoft SQL Server. With 28% growth in market share, growth is almost twice the nearest competitor at 14.8% growth.
¢ SQL Server Manages the World's Largest Databases
CHAPTER 4
SYSTEM ANALYSIS
The primary goal of the system analyst is to improve the efficiency of the existing system. For that the study of specification of the requirements is very essential. For the development of the new system, a preliminary survey of the existing system will be conducted. Investigation done whether the upgradation of the system into an application program could solve the problems and eradicate the inefficiency of the existing system.
4.1 FEASIBILITY STUDY
The initial investigation points to the question whether the project is feasible. A feasibility is conducted to identify the best system that meets the all the requirements. This includes an identification description, an valuation of the proposed systems and selection of the best system for the job. The requirements of the system are specified with a set of constraints such as system objectives and the description of the out puts. It is then duty of the analyst to evaluate the feasibility of the proposed system to generate the above results. Three key factors are to be considered during the feasibility study.
4.1.1 Operation Feasibility
An estimate should be made to determine how much effort and care will go into the developing of the system including the training to be given to the user. Usually, people are reluctant to changes that come in their progression. The computer initialization will certainly affected the turn over, transfer and employee job status. Hence an additional effort is to be made to train and educate the users on the new way of the system.
4.1.2 Technical Feasibility
The main consideration is to be given to the study of available resources of the organization where the software is to be implemented. Here the system analyst evaluates the technical merits of the system giving emphasis on the performance, Reliability, maintainability and productivity.
By taking the consideration before developing the proposed system, the resources availability of the organization was studied. The organization was immense computer facilities equipped with sophisticated machines and the software hence this technically feasible.
4.1.3 Economic Feasibility
Economic feasibility is the most important and frequently used method for evaluating the effectiveness of the proposed system. It is very essential because the main goal of the proposed system is to have economically better result along with increased efficiency. Cost benefit analysis is usually performed for this purpose. It is the comparative study of the cost verses the benefit and savings that are expected from the proposed system. Since the organization is well equipped with the required hard ware, the project was found to be economically.
CHAPTER 5
SYSTEM SPECIFICATION
5.1 HARDWARE REQUIREMENTS
Processor
: Pentium IV
Ram
: 512 MB RAM
Hard Disk
: 80 GB Hard disk
5.2 SOFTWARE REQUIREMENTS
Operating System
: Microsoft XP/VISTA/2003 server
Platform
: Visual Studio 2005
Database
: Microsoft SQL Server 2005
Application Software : Microsoft Office 2003
5.3 SOFTWARE FEATUERS
5.3.1 LANGUAGES USED: C#
Visual C# .Net is designed to be a fast and easy way to create .NET applications, including Web services and ASP.NET Web applications. Applications written in Visual C# are built on the services of the common language runtime and take full advantage of the .NET Framework.
It is a simple, elegant, type-safe, object-oriented language recently developed by Microsoft for building a wide range of applications. Anyone familiar with C and similar languages will find few problems in adapting to C#. C# is designed to bring rapid development to the C++ programmer without sacrificing the power and control that are a hallmark of C and C++. Because of this heritage, C# has a high degree of fidelity with C and C++, and developers familiar with these languages can quickly become productive in C#. C# provides intrinsic code trust mechanisms for a high level of security, garbage collection, and type safety. C# supports single inheritance and creates Microsoft intermediate language (MSIL) as input to native code compilers.
It is fully integrated with the .NET Framework and the common language runtime, which together provide language interoperability, garbage collection, enhanced security, and improved versioning support. C# simplifies and modernizes some of the more complex aspects of C and C++, notably namespaces, classes,
enumerations, overloading, and structured exception handling. C# also eliminates C and C++ features such as macros, multiple inheritance, and virtual base classes. For current C++ developers, C# provides a powerful, high-productivity language alternative.
Visual C# provides prototypes of some common project types, including:
¢ Windows Application.
¢ Class Library.
¢ Windows Control Library.
¢ ASP.NET Web Application.
¢ ASP.NET Web Service.
¢ Web Control Library.
¢ Console Application.
¢ Windows Service.
CHAPTER 6 SYSTEM DESIGN
System design is the solution to the creation of a new system. This phase is composed of several systems. This phase focuses on the detailed implementation of the feasible system. It emphasis on translating design specifications to performance specification. System design has two phases of development logical and physical design.
During logical design phase the analyst describes inputs (sources), out puts (destinations), databases (data sores) and procedures (data flows) all in a format that meats the uses requirements. The analyst also specifies the user needs and at a level that virtually determines the information flow into and out of the system and the data resources. Here the logical design is done through data flow diagrams and database design.
The physical design is followed by physical design or coding. Physical design produces the working system by defining the design specifications, which tell the programmers exactly what the candidate system must do. The programmers write the necessary programs that accept input from the user, perform necessary processing on accepted data through call and produce the required report on a hard copy or display it on the screen.
6.1 LOGICAL DESIGN
Logical design of an information system shows the major features and also how they are related to one another. The first step of the system design is to design logical design elements. This is the most creative and challenging phase and important too. Design of proposed system produces the details of the state how the system will meet the requirements identified during the system analysis that is, in the design phase we have to find how to solve the difficulties faced by the existing system. The logical design of the proposed system should include the details that contain how the solutions can be implemented. It also specifies how the database is to be built for storing and retrieving data, what kind of reports are to be created and what are the inputs to be given to the system. The logical design includes input design, output design, and database design and physical design
6.2 INPUT DESIGN
The input design is the link between the information system and the user. It comprises the developing specification and procedures for data preparation and those steps are necessary to put transaction data into a usable form for processing data entry. The activity of putting data into the computer for processing can be achieved by inspecting the computer to read data from a written or printed document or it can occur by having people keying the data directly into the system. The design of input focuses on controlling the amount of input required, controlling errors, avoiding delay, avoiding extra steps and keeping the process simple.
The system needs the data regarding the asset items, depreciation rates, asset transfer, physical verification for various validation, checking, calculation and report generation.. The error raising method is also included in the software, which helps to raise error message while wrong entry of input is done. So in input design the following things are considered.
What data should be given as input
¢ How the data should be arranged or coded
¢ The dialogue to guide the operating personnel in providing input.
¢ Methods for preparing input validations and steps to follow when error occur
¢ The samples of screen layout are given in the appendix.
6.3 OUTPUT DESIGN
Computer output is the most important and direct information source to the user. Output design is a process that involves designing necessary outputs in the form of reports that should be given to the users according to the requirements. Efficient, intelligible output design should improve the system's relationship with the user and help in decision making. Since the reports are directing referred by the management for taking decisions and to draw conclusions they must be designed with almost care and the details in the reports must be simple, descriptive and clear to the user. So while designing output the following things are to be considered.
¢ Determine what information to present
¢ Arrange the presentation of information in an acceptable format
¢ Decide how to distribute the output to intended receipts
Depending on the nature and future use of output required, they can be displayed on the monitor for immediate need and for obtaining the hardcopy. The options for the output reports are given in the appendix.
6.4 PHYSICAL DESIGN
The process of developing the program software is referred to as physical design. We have to design the process by identifying reports and the other outputs the system will produce. Coding the program for each module with its logic is performed in this step. Proper software specification is also done in this step.
6.5 MODULAR DESIGN
A software system is always divided into several sub systems that makes it easier for the development. A software system that is structured into several subsystems makes it easy for the development and testing. The different subsystems are known as the modules and the process of dividing an entire system into subsystems is known as modularization or decomposition.
A system cannot be decomposed into several subsystems in any way. There must some logical barrier, which facilitates the separation of each module. The separation must be simple but yet must be effective so that the development is not affected.
The system under consideration has been divided into several modules taking in consideration the above-mentioned criteria. The different modules are
1.College and Department details
2. Login and subject
3. Student Details
4. Exam Details
6.6 DATABASE DESIGN
The overall objective in the development of database technology has been to treat data as an organizational resource and as an integrated whole. DBMS allow data to be protected and organized separately from other resources. Database is an integrated collection of data. The most significant form of data as seen by the programmers is data as stored on the direct access storage devices. This is the difference between logical and physical data.
Database files are the key source of information into the system. It is the process of designing database files, which are the key source of information to the system. The files should be properly designed and planned for collection, accumulation, editing and retrieving the required information.
The organization of data in database aims to achieve three major objectives: -
¢ Data integration.
¢ Data integrity.
¢ Data independence.
The proposed system stores the information relevant for processing in the MS SQL SERVER database. This database contains tables, where each table corresponds to one particular type of information. Each piece of information in table is called a field or column. A table also contains records, which is a set of fields. All records in a table have the same set of fields with different information. There are primary key fields that uniquely identify a record in a table. There are also fields that contain primary key from another table called foreign keys.
6.6.1 NORMALIZATION
Normalization is a technique of separating redundant fields and braking up a large table in to a smaller one. It is also used to avoid insertion, deletion and updating anomalies. All the tables have been normalized up to the third normal form. In short the rules for each of the three normal forms are as below.
¢ First normal form
A relation is said to be in 1NF if all the under lying domain of attributes contain simple individual
values.
¢ Second normal form
The 2NF is based on the concept of full functional dependency. A relation said to be in 2NF if and only if it is in 1NF and every non-key attribute is fully functionally dependent on candidate key of the table.
¢ Third normal form
The 3NF is based on the concept of transitive dependency. A relation in 2NF is said to be in 3NF if every non-key attribute is non-transitively.
CHAPTER 7
CODING
The goal of the coding phase is to translate the design. The aim in this phase is to implement the design in the best possible manner. Well known code can reduce the testing and maintenance effort. During coding, the focus should on developing programs that are easy to read and understand and not simply on developing the programs that are easy to write. Simplicity and clarity should be strived for during the code phase. An important concept that help the understandability of the programs is structured programming. The program that should be organized as a sequence of statements and during execution of the statements is executed in the sequence given in the program. There are many different criteria for judging of the program, execution time and required memory.
CHAPTER 8 SYSTEM TESTING AND IMPLEMENTATION
8.1 SYSTEM TESTING
System testing is a critical aspect of Software Quality Assurance and represents the ultimate review of specification, design and coding. Testing is a process of executing a program with the intent of finding an error. A good test is one that has a probability of finding an as yet undiscovered error. The purpose of testing is to identify and correct bugs in the developed system. Nothing is complete without testing. Testing is the vital to the success of the system.
In the code testing the logic of the developed system is tested. For this every module of the program is executed to find an error. To perform specification test, the examination of the specifications stating what the program should do and how it should perform under various conditions.
Unit testing focuses first on the modules in the proposed system to locate errors. This enables to detect errors in the coding and logic that are contained within that module alone. Those resulting from the interaction between modules are initially avoided. In unit testing step each module has to be checked separately.
System testing does not test the software as a whole, but rather than integration of each module in the system. The primary concern is the compatibility of individual modules. One has to find areas where modules have been designed with different specifications of data lengths, type and data element name.
Testing and validation are the most important steps after the implementation of the developed system. The system testing is performed to ensure that there are no errors in the implemented system. The software must be executed several times in order to find out the errors in the different modules of the system.
Validation refers to the process of using the new software for the developed system in a live environment i.e., new software inside the organization, in order to find out the errors. The validation phase reveals the failures and the bugs in the developed system. It will be come to know about the practical difficulties the system faces when operated in the true environment. By testing the code of the implemented software, the logic of the program can be examined. A specification test is conducted to check whether the specifications stating the program are performing under various conditions. Apart from these tests, there are some special tests conducted which are given below:
Peak Load Tests: This determines whether the new system will handle the volume of activities when the system is at the peak of its processing demand. The test has revealed that the new software for the agency is capable of handling the demands at the peak time.
Storage Testing: This determines the capacity of the new system to store transaction data on a disk or on other files. The proposed software has the required storage space available, because of the use of a number of hard disks.
Performance Time Testing: This test determines the length of the time used by the system to process transaction data.
In this phase the software developed Testing is exercising the software to uncover errors and ensure the system meets defined requirements. Testing may be done at 4 levels
¢ Unit Level
¢ Module Level
¢ Integration & System
¢ Regression
8.1.1 UNIT TESTING
A Unit corresponds to a screen /form in the package. Unit testing focuses on verification of the corresponding class or Screen. This testing includes testing of control paths, interfaces, local data structures, logical decisions, boundary conditions, and error handling. Unit testing may use Test Drivers, which are control programs to co-ordinate test case inputs and outputs, and Test stubs, which replace low-level modules. A stub is a dummy subprogram.
8.1.2 MODULE LEVEL TESTING
Module Testing is done using the test cases prepared earlier. Module is defined during the time of
design.
8.1.3 INTEGRATION & SYSTEM TESTING
Integration testing is used to verify the combining of the software modules. Integration testing addresses the issues associated with the dual problems of verification and program construction. System testing is used to verify, whether the developed system meets the requirements. 8.1.4 REGRESSION TESTING
Each modification in software impacts unmodified areas, which results serious injuries to that software. So the process of re-testing for rectification of errors due to modification is known as regression testing.
Installation and Delivery:
Installation and Delivery is the process of delivering the developed and tested software to the customer. Refer the support procedures. Acceptance and Project Closure:
Acceptance is the part of the project by which the customer accepts the product. This will be done as per the Project Closure, once the customer accepts the product, closure of the project is started. This includes metrics collection, PCD, etc.
8.2 SYSTEM IMPLEMENTATION
Implementation includes all those activities that take place to convert from the old system to the new. The old system consists of manual operations, which is operated in a very different manner from the proposed new system. A proper implementation is essential to provide a reliable system to meet the requirements of the organizations. An improper installation may affect the success of the computerized
system.
8.2.1 IMPLEMENTATION METHODS:
There are several methods for handling the implementation and the consequent conversion from the old to the new computerized system.
The most secure method for conversion from the old system to the new system is to run the old and new system in parallel. In this approach, a person may operate in the manual older processing system as well as start operating the new computerized system. This method offers high security, because even if there is a flaw in the computerized system, we can depend upon the manual system. However, the cost for maintaining two systems in parallel is very high. This outweighs its benefits.
Another commonly method is a direct cut over from the existing manual system to the computerized system. The change may be with in a week or with in a day. There are no parallel activities. However, there is no remedy in case of a problem. This strategy requires careful planning.
A working version of the system can also be implemented in one part of the organization and the personnel will be piloting the system and changes can be made as and when required. But this method is less preferable due to the loss of entirety of the system.
8.2.2 IMPLEMENTATION PLAN:
The implementation plan includes a description of all the activities that must occur to implement the new system and to put it into operation. It identifies the personnel responsible for the activities and prepares a time chart for implementing the system. The implementation plan consists of the following steps.
o List all files required for implementation.
o Identify all data required to build new files during the implementation.
o List all new documents and procedures that go into the new system.
The implementation plan should anticipate possible problems and must be able to deal with them. The usual problems may be missing documents; mixed data formats between current and files, errors in data translation, missing data etc.
CHAPTER 9
FIGURES
The different modules, forms and tables in our system are displayed here. 9.1 DATA FLOW DIAGRAM
The following dataflow diagrams show the control flow in our system.
User
Service
USER
SIGN UP
-H
LOGIN
DATA BASE ACCES
VIEW
DATABASE
Fig13.2 LEVEL 2 DFD
9.2 SCREEN SHOTS
9.2.1 College and Department details
It deals with the details of college and department.
Fig 1: College details
This form is used to enter the details of the college.
Fig 2: Department details
This form is used to enter the details about various courses.
9.1.2 Login and subject
It contains the details of login process and subject details. Login process include sign in sign up ,sign out, change password.
Fig3: Signup
This form is used for sign up process.
Fig4: Sign in form
This form is used to sign in to the system
Fig5: Change password form
This form is used to change the password of users.
Fig5 :Subject form
This form is used to enter the details about different subjects of different departments and semesters.
9.1.3 Student Details
Fig7:Parent details
Fig6 and Fig7 are used to enter the personnel details of student.
Fig8:Acdemic details
This form is used enter different types
Fig9: Exam details
This form is used to enter marks got for various exams including its register number.
Fig11: Other details
This form is used to enter the achievements, disciplinary action taken and the month and year of under going course.
Fig12: Final report
This form is used to enter technical knowledge, about the lab record, his/her character any remarks.
CHAPTER 10
CONCLUSION
The system has been developed with much care that it is free of errors and at the same time it is efficient and less time consuming. The important thing is that the system is robust. Avoid malfunction from outsiders .It goes through all phases of software development cycle. So product is accurate. Also provision is provided for future developments in the system.
RESUME
The current application developed is in accordance with the request that has been provided by the organization. On regarding the future enhancement, the application can further expanded in accordance with changing scenario. Since the change in testing and user needs arises frequently in certain short intervals of time, the application can be further upgraded to meet the requirements that may arise in the far or near future. With regarding to the needs that arises, more and more features can be included by adding it as separate modules and integrate it with the existing system.
The .NET today is based on OOPs concept, whose main advantage is modularity, which helps us in adding the future needs as add-on modules to work with the main system which can be done effortlessly instead of rewriting or modifying the entire application. So the scope of future enhancement is absolutely clear with the concept that is incorporated in the today that was made used to build the application.
REFERENCES
http://www.msdn.microsoft..com http://www.csharpcorner.com http://www.getdotnet.com http://www.google.com
22-04-2010, 11:09 AM
Post: #2
RE: student management system full report

.pdf  Student Management System.pdf (Size: 381.67 KB / Downloads: 3995)

INTRODUCTION

Student Management System is software which is helpful for students as well as the school authorities. In the current system all the activities are done manually. It is very time consuming and costly. Our Student Management System deals with the various activities related to the students.
There are mainly 3 modules in this software
¢ User module
¢ Student Module
¢ Mark management


In the Software we can register as a user and user has of two types, student and administrator. Administrator has the power to add new user and can edit and delete a user. A student can register as user and can add edit and delete his profile. The administrator can add edit and delete marks for the student. All the users can see the marks.

SYSTEM ANALYSIS






EXISTING SYSTEM:
System Analysis is a detailed study of the various operations performed by a system and their relationships within and outside of the system. Here the key question is- what all problems exist in the present system? What must be done to solve the problem? Analysis begins when a user or manager begins a study of the program using existing system.
During analysis, data collected on the various files, decision points and transactions handled by the present system. The commonly used tools in the system are Data Flow Diagram, interviews, etc. Training, experience and common sense are required for collection of relevant information needed to develop the system. The success of the system depends largely on how clearly the problem is defined, thoroughly investigated and properly carried out through the choice of solution. A good analysis model should provide not only the mechanisms of problem understanding but also the frame work of the solution. Thus it should be studied thoroughly by collecting data about the system. Then the proposed system should be analyzed thoroughly in accordance with the needs.

System analysis can be categorized into four parts.
S System planning and initial investigation
S Information Gathering
S Applying analysis tools for structured analysis
S Feasibility study
S Cost/ Benefit analysis.

In the current system we need to keep a number of records related to the student and want to enter the details of the student and the marks manually. In this system only the teacher or the school authority views the mark of the student and they want to enter the details of the student. This is time consuming and has much cost.

PROPOSED SYSTEM



In our proposed system we have the provision for adding the details of the students by themselves. So the overhead of the school authorities and the teachers is become less. Another advantage of the system is that it is very easy to edit the details of the student and delete a student when it found unnecessary. The marks of the student are added in the database and so students can also view the marks whenever they want.

Our proposed system has several advantages
> User friendly interface
> Fast access to database
> Less error
> More Storage Capacity
> Search facility
> Look and Feel Environment
> Quick transaction

All the manual difficulties in managing the student details in a school or college have been rectified by implementing computerization.

FEASIBILITY ANALYSIS

Whatever we think need not be feasible .It is wise to think about the feasibility of any problem we undertake. Feasibility is the study of impact, which happens in the organization by the development of a system. The impact can be either positive or negative. When the positives nominate the negatives, then the system is considered feasible. Here the feasibility study can be performed in two ways such as technical feasibility and Economical Feasibility.



Technical Feasibility:
We can strongly says that it is technically feasible, since there will not be much difficulty in getting required resources for the development and maintaining the system as well. All the resources needed for the development of the software as well as the maintenance of the same is available in the organization here we are utilizing the resources which are available already.

Economical Feasibility
Development of this application is highly economically feasible .The organization needed not spend much money for the development of t he system already available. The only thing is to be done is making an environment for the development with an effective supervision. I f we are doing so , we can attain the maximum usability of the corresponding resources .Even after the development , the organization will not be in condition to invest more in t he organization .There fore , the system is economically feasible.

SYSTEM REQUIREMENTS




This management system can be used in windows 98, Windows2000, Windows XP and Windows NT, supported for other platform such as Applet, Macintosh and UNIX.
The system must be running Windows 98, Windows 98 or Windows NT4.0 operating system and must meet the following hardware requirements.
> For Windows 95 based computers , a 486 / 66 MHz or higher processor with 8MB
> For Windows 98 based computers , a 500/88MHz or higher processor with 32 Mb of RAM
> For Windows NT based computers , a 488 / 66 MHz or higher processor with 16 MB of RAM
> For Windows 200 based computers , a 700/850 MHz or higher processor with 512 MB of Ram

DATA FLOW DIAGRAM






Context Diagram




User







SYSTEM DESIGN


INPUT DESIGN

Input design is the process of converting user-oriented input to a computer based format. Input design is a part of overall system design, which requires very careful attention .Often the collection of input data is the most expensive part of the system. The main objectives of the input design are ...
1. Produce cost effective method of input
2. Achieve highest possible level of accuracy
3. Ensure that the input is acceptable to and understood by the staff. Input Data
The goal of designing input data is to make entry easy, logical and free from errors as possible. The entering data entry operators need to know the allocated space for each field; field sequence and which must match with that in the source document. The format in which the data fields are entered should be given in the input form .Here data entry is online; it makes use of processor that accepts commands and data from the operator through a key board. The input required is analyzed by the processor. It is then accepted or rejected. Input stages include the following processes
¢ Data Recording
¢ Data Transcription
¢ Data Conversion
¢ Data Verification
¢ Data Control
¢ Data Transmission
¢ Data Correction

One of the aims of the system analyst must be to select data capture method and devices, which reduce the number of stages so as to reduce both the changes of errors and the cost .Input types, can be characterized as.
¢ External
¢ Internal
¢ Operational
¢ Computerized
¢ Interactive
Input files can exist in document form before being input to the computer. Input design is rather complex since it involves procedures for capturing data as well as inputting it to the computer.



OUTPUT DESIGN




Outputs from computer systems are required primarily to communicate the results of processing to users. They are also used to provide a permanent copy of these result for latter consultation .Computer output is the most important and direct source of information to the users. Designing computer output should proceed in an organized well through out the manner. The right output must be available for the people who find the system easy o use. The outputs have been defined during the logical design stage. If not, they should defined at the beginning of the output designing terms of types of output connect, format, response etc,



Various types of outputs are
¢ External outputs
¢ Internal outputs
¢ Operational outputs
¢ Interactive outputs
¢ Turn around outputs
All screens are informative and interactive in such a way that the user can full fill his requirements through asking queries.



DATABASE DESIGN


The general theme behind a database is to handle information as an integrated whole. A database is a collection of interrelated data stored with minimum redundancy to serve many users quickly and effectively. After designing input and output, the analyst must concentrate on database design or how data should be organized around user requirements. The general objective is to make information access, easy quick, inexpensive and flexible for other users. During database design the following objectives are concerned:-

>

Controlled Redundancy

>

Data independence

>

Accurate and integrating

>

More information at low cost

>

Recovery from failure

>

Privacy and security

>

Performance

>

Ease of learning and use


SYSTEM IMPLEMENTATION




Implementation is the stage in the project where the theoretical design is turned into a working system. The implementation phase constructs, installs and operates the new system. The most crucial stage in achieving a new successful system is that it will work efficiently and effectively.

There are several activities involved while implementing a new project. They are
> End user training
> End user Education
> Training on the application software
> System Design
> Parallel Run and To New System
> Post implementation Review

End user Training:
The successful implementation of the new system will purely upon the involvement of the officers working in that department. The officers will be imparted the necessary training on the new technology

End User Education:
The education of the end user start after the implementation and testing is over. When the system is found to be more difficult to under stand and complex, more effort is put to educate the end used to make them aware of the system, giving them lectures about the new system and providing them necessary documents and materials about how the system can do this.
Training of application software:
After providing the necessary basic training on the computer awareness, the users will have to be trained upon the new system such as the screen flows and screen design type of help on the screen, type of errors while entering the data, the corresponding validation check at each entry and the way to correct the data entered. It should then cover information needed by the specific user or group to use the system.



Post Implementation View:
The department is planning a method to know the states of t he past implementation process. For that regular meeting will be arranged by the concerned officers about the implementation problem and success

SOFTWARE TESTING

Is the menu bar displayed in the appropriate contested some system related features included either in menus or tools? Do pull -Down menu operation and Tool-bars work properly? Are all menu function and pull down sub function properly listed ?; Is it possible to invoke each menu function using a logical assumptions that if all parts of the system are correct, the goal will be successfully achieved .? In adequate testing or non-testing will leads to errors that may appear few months later.
This create two problem
1. Time delay between the cause and appearance of the problem.
2. The effect of the system errors on files and records within the system
The purpose of the system testing is to consider all the likely variations to which it will be suggested and push the systems to limits.
The testing process focuses on the logical intervals of the software ensuring that all statements have been tested and on functional interval is conducting tests to uncover errors
and ensure that defined input will produce actual results that agree with the required results. Program level testing, modules level testing integrated and carried out.

There are two major type of testing they are
1) White Box Testing.
2) Black Box Testing.

White Box Testing

White box some times called "Glass box testing" is a test case design uses the control structure of the procedural design to drive test case.

Using white box testing methods, the following tests where made on the system
a) All independent paths within a module have been exercised once. In our system, ensuring that case was selected and executed checked all case structures. The bugs that were prevailing in some part of the code where fixed
b) All logical decisions were checked for the truth and falsity of the values.

Black box Testing

Black box testing focuses on the functional requirements of the software. This is black box testing enables the software engineering to derive a set of input conditions that will fully exercise all functional requirements for a program. Black box testing is not an alternative to white box testing rather it is complementary approach that is likely to uncover a different class of errors that white box methods like..
1) Interface errors
2) Performance in data structure
3) Performance errors
4) Initializing and termination errors
CONCLUSION






Our project is only a humble venture to satisfy the needs in an Institution. Several user friendly coding have also adopted. This package shall prove to be a powerful package in satisfying all the requirements of the organization.


The objective of software planning is to provide a frame work that enables the manger to make reasonable estimates made within a limited time frame at the beginning of the software project and should be updated regularly as the project progresses. Last but not least it is no the work that played the ways to success but ALMIGHTY

BIBLIOGRAPHY
1) http://www.javaworld.com/javaworld/jw-01...eview.html
2) Database Programming with JDBC and Java by O'Reilly
3) Head First Java 2nd Edition
4) http://www.jdbc-tutorial.com/
5) Java and Software Design Concepts by APress

Please Use Search http://seminarprojects.com/search.php wisely To Get More Information About A Seminar Or Project Topic
01-05-2010, 11:17 PM
Post: #3
RE: student management system full report
[attachment=3452][attachment=3452]

INTRODUCTION
Student Management System is software which is helpful for students as well as the school authorities. In the current system all the activities are done manually. It is very time consuming and costly. Our Student Management System deals with the various activities related to the students.
There are mainly 3 modules in this software
¢ User module
¢ Student Module
¢ Mark management
In the Software we can register as a user and user has of two types, student and administrator. Administrator has the power to add new user and can edit and delete a user. A student can register as user and can add edit and delete his profile. The administrator can add edit and delete marks for the student. All the users can see the marks.
SYSTEM ANALYSIS
EXISTING SYSTEM:
System Analysis is a detailed study of the various operations performed by a system and their relationships within and outside of the system. Here the key question is- what all problems exist in the present system What must be done to solve the problem Analysis begins when a user or manager begins a study of the program using existing system.
During analysis, data collected on the various files, decision points and transactions handled by the present system. The commonly used tools in the system are Data Flow Diagram, interviews, etc. Training, experience and common sense are required for collection of relevant information needed to develop the system. The success of the system depends largely on how clearly the problem is defined, thoroughly investigated and properly carried out through the choice of solution. A good analysis model should provide not only the mechanisms of problem understanding but also the frame work of the solution. Thus it should be studied thoroughly by collecting data about the system. Then the proposed system should be analyzed thoroughly in accordance with the needs.
System analysis can be categorized into four parts.
System planning and initial investigation
Information Gathering
Applying analysis tools for structured analysis
Feasibility study
Cost/ Benefit analysis.
In the current system we need to keep a number of records related to the student and want to enter the details of the student and the marks manually. In this system only the teacher or the school authority views the mark of the student and they want to enter the details of the student. This is time consuming and has much cost.
PROPOSED SYSTEM

In our proposed system we have the provision for adding the details of the students by themselves. So the overhead of the school authorities and the teachers is become less. Another advantage of the system is that it is very easy to edit the details of the student and delete a student when it found unnecessary. The marks of the student are added in the database and so students can also view the marks whenever they want.
Our proposed system has several advantages
User friendly interface
Fast access to database
Less error
More Storage Capacity
Search facility
Look and Feel Environment
Quick transaction
All the manual difficulties in managing the student details in a school or college have been rectified by implementing computerization.
FEASIBILITY ANALYSIS
Whatever we think need not be feasible .It is wise to think about the feasibility of any problem we undertake. Feasibility is the study of impact, which happens in the organization by the development of a system. The impact can be either positive or negative. When the positives nominate the negatives, then the system is considered feasible. Here the feasibility study can be performed in two ways such as technical feasibility and Economical Feasibility.
Technical Feasibility:
We can strongly says that it is technically feasible, since there will not be much difficulty in getting required resources for the development and maintaining the system as well. All the resources needed for the development of the software as well as the maintenance of the same is available in the organization here we are utilizing the resources which are available already.
Economical Feasibility
Development of this application is highly economically feasible .The organization needed not spend much money for the development of t he system already available. The only thing is to be done is making an environment for the development with an effective supervision. I f we are doing so , we can attain the maximum usability of the corresponding resources .Even after the development , the organization will not be in condition to invest more in t he organization .There fore , the system is economically feasible.
HARDWARE CONFIGURATION

Processor : Pentium III 630MHz
RAM : 128 MB
Hard Disk : 20GB
Monitor : 15 Color monitor
Key Board : 122 Keys
SOFTWARE CONFIGURATION
Operating System : Windows NT,
Windows 98,
Windows XP.
Language : Java 2 Runtime Environment
Database : MS Access2007.
SYSTEM REQUIREMENTS

This management system can be used in windows 98, Windows2000, Windows XP and Windows NT, supported for other platform such as Applet, Macintosh and UNIX.
The system must be running Windows 98, Windows 98 or Windows NT4.0 operating system and must meet the following hardware requirements.
For Windows 95 based computers , a 486 / 66 MHz or higher processor with 8MB
For Windows 98 based computers , a 500/88MHz or higher processor with 32 Mb of RAM
For Windows NT based computers , a 488 / 66 MHz or higher processor with 16 MB of RAM
For Windows 200 based computers , a 700/850 MHz or higher processor with 512 MB of Ram
DATA FLOW DIAGRAM
Context Diagram
SOFTWARE INTERFACE
Login
Add New User
Edit User Type
Delete User
Student Registration
Edit Student Details
Delete Student details
Add/Edit Mark Details
View Marks
View User details
View Student Details
Add New Subjects
Edit Subject details
Delete Subject details
Subject Allocation
SYSTEM DESIGN
INPUT DESIGN
Input design is the process of converting user-oriented input to a computer based format. Input design is a part of overall system design, which requires very careful attention .Often the collection of input data is the most expensive part of the system. The main objectives of the input design are ¦
1. Produce cost effective method of input
2. Achieve highest possible level of accuracy
3. Ensure that the input is acceptable to and understood by the staff.
Input Data
The goal of designing input data is to make entry easy, logical and free from errors as possible. The entering data entry operators need to know the allocated space for each field; field sequence and which must match with that in the source document. The format in which the data fields are entered should be given in the input form .Here data entry is online; it makes use of processor that accepts commands and data from the operator through a key board. The input required is analyzed by the processor. It is then accepted or rejected. Input stages include the following processes
¢ Data Recording
¢ Data Transcription
¢ Data Conversion
¢ Data Verification
¢ Data Control
¢ Data Transmission
¢ Data Correction
One of the aims of the system analyst must be to select data capture method and devices, which reduce the number of stages so as to reduce both the changes of errors and the cost .Input types, can be characterized as.
¢ External
¢ Internal
¢ Operational
¢ Computerized
¢ Interactive
Input files can exist in document form before being input to the computer. Input design is rather complex since it involves procedures for capturing data as well as inputting it to the computer.
OUTPUT DESIGN
Outputs from computer systems are required primarily to communicate the results of processing to users. They are also used to provide a permanent copy of these result for latter consultation .Computer output is the most important and direct source of information to the users. Designing computer output should proceed in an organized well through out the manner. The right output must be available for the people who find the system easy o use. The outputs have been defined during the logical design stage. If not, they should defined at the beginning of the output designing terms of types of output connect, format, response etc,
Various types of outputs are
¢ External outputs
¢ Internal outputs
¢ Operational outputs
¢ Interactive outputs
¢ Turn around outputs
All screens are informative and interactive in such a way that the user can full fill his requirements through asking queries.
DATABASE DESIGN

The general theme behind a database is to handle information as an integrated whole. A database is a collection of interrelated data stored with minimum redundancy to serve many users quickly and effectively. After designing input and output, the analyst must concentrate on database design or how data should be organized around user requirements. The general objective is to make information access, easy quick, inexpensive and flexible for other users. During database design the following objectives are concerned:-
Controlled Redundancy
Data independence
Accurate and integrating
More information at low cost
Recovery from failure
Privacy and security
Performance
Ease of learning and use
TABLES USED
Student
Field Name Data Type Description
RollNo Number Primary Key
SName Text(50) -
Phno Text(15) -
Sex Text(10) -
FName Text(50) -
Occupation Text(50) -
MName Text(50) -
DOB Date/Time -
Age Number -
Caste Text(25) -
Religion Text(30) -
Hname Text(50) -
City Text(50) -
District Text(50) -
State Text(50) -
Pin Text(10) -
Year Number -
Qualification Text(25) -
UAD
Field Name Data Type Description
Username Text(25) Primary Key
Password Text(15) -
Type Text(15) -
Subjects
Field Name Data Type Description
Subjectcode Text(10) Primary Key
Subjectname Text(50) -
Creditmark Number -
MaxMark Number -
Type Text(25) -
SubjectAllocation
Field Name Data Type Description
Subjectname Text(50) -
Semester Number -
Batch Text(15) -
SSLC1
Field Name Data Type Description
RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -
SSLC2
Field Name Data Type Description
RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -
SSLC3
Field Name Data Type Description
RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -
SSLC4
Field Name Data Type Description
RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -
SSLC5
Field Name Data Type Description
RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -
SSLC6
Field Name Data Type Description
RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -
PLUSTWO1
Field Name Data Type Description
RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -
PLUSTWO2
Field Name Data Type Description
RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -
PLUSTWO3
Field Name Data Type Description
RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -
PLUSTWO4
Field Name Data Type Description
RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -
PLUSTWO5
Field Name Data Type Description
RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -
SYSTEM IMPLEMENTATION
Implementation is the stage in the project where the theoretical design is turned into a working system. The implementation phase constructs, installs and operates the new system. The most crucial stage in achieving a new successful system is that it will work efficiently and effectively.
There are several activities involved while implementing a new project. They are
End user training
End user Education
Training on the application software
System Design
Parallel Run and To New System
Post implementation Review
End user Training:
The successful implementation of the new system will purely upon the involvement of the officers working in that department. The officers will be imparted the necessary training on the new technology
End User Education:
The education of the end user start after the implementation and testing is over. When the system is found to be more difficult to under stand and complex, more effort is put to educate the end used to make them aware of the system, giving them lectures about the new system and providing them necessary documents and materials about how the system can do this.
Training of application software:
After providing the necessary basic training on the computer awareness, the users will have to be trained upon the new system such as the screen flows and screen design type of help on the screen, type of errors while entering the data, the corresponding validation check at each entry and the way to correct the data entered. It should then cover information needed by the specific user or group to use the system.
Post Implementation View:
The department is planning a method to know the states of t he past implementation process. For that regular meeting will be arranged by the concerned officers about the implementation problem and success
SOFTWARE TESTING
Is the menu bar displayed in the appropriate contested some system related features included either in menus or tools Do pull “Down menu operation and Tool-bars work properly Are all menu function and pull down sub function properly listed ; Is it possible to invoke each menu function using a logical assumptions that if all parts of the system are correct, the goal will be successfully achieved . In adequate testing or non-testing will leads to errors that may appear few months later.
This create two problem
1. Time delay between the cause and appearance of the problem.
2. The effect of the system errors on files and records within the system
The purpose of the system testing is to consider all the likely variations to which it will be suggested and push the systems to limits.
The testing process focuses on the logical intervals of the software ensuring that all statements have been tested and on functional interval is conducting tests to uncover errors and ensure that defined input will produce actual results that agree with the required results. Program level testing, modules level testing integrated and carried out.
There are two major type of testing they are
1) White Box Testing.
2) Black Box Testing.
White Box Testing
White box some times called Glass box testing is a test case design uses the control structure of the procedural design to drive test case.
Using white box testing methods, the following tests where made on the system
a) All independent paths within a module have been exercised once. In our system, ensuring that case was selected and executed checked all case structures. The bugs that were prevailing in some part of the code where fixed
b) All logical decisions were checked for the truth and falsity of the values.
Black box Testing
Black box testing focuses on the functional requirements of the software. This is black box testing enables the software engineering to derive a set of input conditions that will fully exercise all functional requirements for a program. Black box testing is not an alternative to white box testing rather it is complementary approach that is likely to uncover a different class of errors that white box methods like..
1) Interface errors
2) Performance in data structure
3) Performance errors
4) Initializing and termination errors
CONCLUSION
Our project is only a humble venture to satisfy the needs in an Institution. Several user friendly coding have also adopted. This package shall prove to be a powerful package in satisfying all the requirements of the organization.
The objective of software planning is to provide a frame work that enables the manger to make reasonable estimates made within a limited time frame at the beginning of the software project and should be updated regularly as the project progresses. Last but not least it is no the work that played the ways to success but ALMIGHTY
BIBLIOGRAPHY
1) http://www.javaworld.com/javaworld/jw-01...eview.html
2) Database Programming with JDBC and Java by O'Reilly
3) Head First Java 2nd Edition
4) http://www.jdbc-tutorial.com/
5) Java and Software Design Concepts by APress


Attached File(s)
.zip  Student Management System source code.zip (Size: 996.45 KB / Downloads: 1080)

Please Use Search http://seminarprojects.com/search.php wisely To Get More Information About A Seminar Or Project Topic
11-07-2010, 10:59 AM
Post: #4
RE: student management system full report
can i get dfds and re diagrams of school management system in vb
18-07-2010, 12:23 AM
Post: #5
RE: student management system full report
Hey... Nice project...!

Thanks!!!

Student Management System [url]www.learney.com[/url]
09-10-2010, 03:40 PM
Post: #6
RE: student management system full report

.ppt  Student Management System.ppt (Size: 157.5 KB / Downloads: 731)

Student Management System
EXISTING SYSTEM
DISADVANTAGES:
1)Physical Strain 2)Less Interactive
3)Time Consuming

PRESENT SYSTEM
ADVANTAGES:

Highly Interactive
Instant Response
Time Saving
24-12-2010, 02:49 PM
Post: #7
RE: student management system full report


.doc  ARMS.doc (Size: 3.55 MB / Downloads: 823)


ABSTRACT


Student Management System deals with all kind of student details, academic related reports, college details, course details, curriculum, batch details and other resource related details too. It tracks all the details of a student from the day one to the end of his course which can be used for all reporting purpose, tracking of attendance, progress in the course, completed semesters years, coming semester year curriculum details, exam details, project or any other assignment details, final exam result; and all these will be available for future references too.

Our program will have the databases of Courses offered by the college under all levels of graduation or main streams, teacher or faculty's details, batch execution details, students' details in all aspects.This program can facilitate us explore all the activities happening in the college, even we can get to know which teacher / faculty is assigned to which batch, the current status of a batch, attendance percentage of a batch and upcoming requirements of a batch.

Different reports and Queries can be generated based of vast options related to students, batch, course, teacher / faculty, exams, semesters, certification and even for the entire college.
The main objective of using this management tool is for academic institutions range from schools and colleges to simplify their administrative process involving personnel management, inventory and payments.

The additional feature which is added in this tool is messaging services like SMS & E-mail which means tool can able to send messages to parents regarding students activities and school events. This system eases the process of tracking a record with its in built search option. For each and every organization, Business Process Reengineering (BPR) is important because BPR is a management approach aiming at improvements by means of elevating efficiency and effectiveness of the processes that exist within and across organizations.
The key to BPR is for organizations to look at their business processes from a "clean slate" perspective and determine how they can best construct these processes to improve how they conduct business and business process change management. So ARMS is designed and developed in the way to ensure the BPR is very much possible in the future requirements and transformations.

Our ARMS also provides proper solutions and reports for the top management for taking proper decisions and policies for Business process redesign and Business Transformations.ARMS also reduces the work load of the End users by eliminating the data-entry work while preparing reports for the top management.

ARMS is developed by using the Microsoft .NET platform so it provides high end security and user friendly environment for the users and provides great control over the system for the administrators.


INTRODUCTION

About the project
The student management system is an automated version of manual Student Management System. It can handle all details about a student. The details include college details, subject details, student personnel details, academic details, exam details etc...
In case of manual system they need a lot of time, manpower etc. Here almost all work is computerized. So the accuracy is maintained. Maintaining backup is very easy. It can do with in a few minutes.

Our system has two type of accessing modes, administrator and user. Student management system is managed by an administrator. It is the job of the administrator to insert update and monitor the whole process.

When a user log in to the system. He would only view details of the student. He can't perform any changes.
04-01-2011, 02:41 PM
Post: #8
RE: student management system full report




SUBMITTED BY:
Aditya Kumar

SUBMITTED TO

Department of Computer Science and Engineering
Lovely Professional University
Phagwara
PUNJAB





.doc  FEE MANAGEMENT SYSTEM.doc (Size: 64.5 KB / Downloads: 405)

TABLE OF CONTENTS

1. Introduction

2. Proposed system
a) Description
b) System requirements

3. Requirement Analysis

4. System Design

5. Flow Chart

6. Source Code

7. Future Scope of the Project

8. Conclusion


INTRODUCTION

In the existing system, most of the records are maintained on paper. It becomes very inconvenient to modify the data. In the existing system, here is a possibility that the same data in different registers may have different values which means the entries of the same data do not match. This inconsistent state does not supply the concrete information which poses a problem in the case information related to particular search record.
Our project is very useful. User is no longer required to check his register in search of records, as now it can be searched over the software by choosing some options. The user need not to type in most of the information. He/she is just required to enter the desired options. On the whole it liberates the user from keeping lengthy manual records. In a nutshell, it abates the work load of an organization.
In today’s world, no one likes to perform calculations on calculator or manually when computer is there. Every one wants his/her work to be done by computer automatically and displaying the result for further manipulations. So this project is about providing convenience regarding fee management system.



PROPOSED SYSTEM

The following documentation is a project the “FEE MANAGEMENT SYSTEM”. It is a detailed summary of all the drawbacks of the old system and how the new proposed system overcomes these shortcomings. The new system takes into account the various factors while designing a new system. It keeps into the account the Economical bandwidth available for the new system. The foremost thing that is taken care of is the need and requirements of the user.

DESCRIPTION

Before developing software we keep following things in mind that we can develop powerful and quality software.

PROBLEM STATEMENT

Problem statement was to design a module:
o Which is user friendly
o Which will restrict the user from accessing other user’s data.
o Which will help user in viewing his data and privileges.
o Which will help the administrator to handle all the changes.

FUNCTIONS TO BE PROVIDED:

The system will be user friendly and completely menu driven so that the users shall have no problem in using all options.
o The system will be efficient and fast in response.
o The system will be customized according to needs.
FOR FEE MANAGEMENT SYSTEM
o (View
o Add
o Delete)


SYSTEM REQUIRMENTS
Operating system: MS Windows XP or Windows Vista
Language: C Language
Processor: Pentium IV Processor
RAM: 512 MB
Hard disk: 5 GB


REQUIREMENT ANALYSIS

This process is adopted when management of the system development, Personnel decide that the particular system needs improvement. The system development life cycle is the set of activities, carried out by the analyst, designers and users to develop and implement a system. The systems that are present in the nature follow common life cycle pattern. For example consider the raining system. Initially the rain falls into the river, river flows into sea, the sea water evaporates to form vapors, the vapors form clouds which again bring rain. Similarly consider a man made system initially a system is analyzed, designed and made operational by the efforts of system analysis.

After successful operation or a number of users, the system becomes less and less effective by change in the environment. So these changes have to be incorporated in to the system by minor modifications. So the general activities from the life cycle of the system are given below:
• Select ion and identification of the system to be studied
• Preliminary study
• Defining the system
• Design and development of the system
• Implementation of the system

SYSTEM DESIGN

Then we began with the design phase of the system. System design is a solution, a “HOW TO” approach to the creation of a new system. It translates system requirements into ways by which they can be made operational. It is a translational from a user oriented document to a document oriented programmers. For that, it provides the understanding and procedural details necessary for the implementation. Here we use Flowchart to supplement the working of the new system. The system thus made should be reliable, durable and above all should have least possible maintenance costs. It should overcome all the drawbacks of the Old existing system and most important of all meet the user requirements.





27-01-2011, 02:45 PM
Post: #9
RE: student management system full report
pliss help me with a full project on student manegement system
28-01-2011, 11:07 AM
Post: #10
RE: student management system full report
hi
for full report, please go through the following link.

http://www.seminarprojects.com/Thread-st...9#pid11669
04-02-2011, 01:38 PM
Post: #11
RE: student management system full report
please send me ,a running project on student management system,its urgent thanks in advance
22-03-2011, 11:54 AM
Post: #12
RE: student management system full report

.doc  final SE (2).doc (Size: 546.5 KB / Downloads: 927)
1. Introduction
1.1 Purpose

The purpose this documents is to present a detailed description of the Student Result
Management System. It will explain the purpose and features of the software, the
interfaces of the software, what the software will do, the constraints under which it must
operates and how the software will react to external stimuli. This document is intended
for both the end users and the developers of the software.
1.2 Document Conventions
To develop the SRS on Student Result Management System we have used IEEE format
SRS, Font size is 12, Font type is Times New Roman.
1.3 Intended audience and Reading Suggestions
The intended audiences for this document are:
• The developers of the project
• The Lecturers who is the client
• The Programmer who are going to implement the software
This document will be reviewed frequently by the above audience to check if the different phases of he project are being completed by meeting the given requirement.
1.4 Project Scope
This document covers the requirements for the Student Result Management System. This
software will provide a graphical environment in which the users of the system will be
able to perform various operations that are associated with storing, marinating, updating
and retrieving Student information. The purpose of this is to guide developers in selecting
a design that will be able to accommodate the full-scale application.
1.5 References
An Integrated Approach to Software Engineering Approach - Pankaj Jalote
Software Engineering A Practitioner’s Approach - Roger S Pressman
2. Overall Description
2.1 Product Perspective

The product Student Result Management system, is an independent product
and does not depend on any other product or system. The product will automate various tasks associated with handling student details and better organizing the stored information and optimum performance, thus helping the Colleges to ensure smooth working of these processes.
2.2 Product Features
The product, SDMS will automate various tasks associated with handling student details. The software will be used by office personnel to store the details of the admission forms of the enrolled students. Periodically it will be used by the office personnel to input the marks and attendance information after internal or end semester exams. He software inherently makes automatic calculations on marks and attendance. And all this information is accessible to administrators and teaching staff to keep track of their student’s progresss. Also the software has a provision that will allow end users to print the required reports of various student statistics.
2.3 User Classes and Characteristics
This software gives access to 2 kinds of users.
1. Administrator: The personnel and College administrator will have administrator access to add, delete and modify information stored in the database.
2. Authorized User: Teaching staff will have access to only view the data stored in the database in the form of formatted reports.
2.4 Operating Environment
2.4.1Software Components

• Product will only run on a computer with Windows Operating System
• Product will have to be configured to connect to the centralized database
• The required software’s has to be installed to run the software
• All data is stored in and retrieved from a centralized database
2.4.2 Hardware Components
• Product will run on a Pentium or AMD based desktop
• Product will run on a computer with at least 128MB RAM and 40GB hard disk
• Printer has to be installed on the machine to print reports
• The machine will have to be a part of the College LAN to access the centralized database.
2.5 Design and Implementation Constraints
This software provides security. The login form prevents the system from being misused by unauthorized users. Only an authorized operator will be granted rights to modify as per requirements. This software is also reliable and fault tolerant. The system developed is designed to handle invalid inputs. Since reliability is major area of concern the system has a backup to avoid data loss. The user should know the programming language very well that is used to develop a software.
2.6 User Documentation
In order to help the client extra documentation components like user manual, on-line help and tutorials will be delivered along with the software.
2.7 Assumptions and Dependencies
• We assume that the Office personnel do all the data entry based n the correct values obtained from forms and registers.
• We assume that the computers that will use the software will be part of the college LAN.
• Users with administrator access should be careful in deleting or modifying any information knowingly or unknowingly which will lead to inconsistency of the database.
• The end users of this software are assumed to have basic level of computer knowledge i.e point and click .
3.System Features
Login

3.1.1 Description and Priority
The login form is used all the users. This module has the highest priority when compared to all the other modules.This model allows the the user to enter his username and password in order to make use of the software.
3.1.2 Stimulus/Response Sequences
This module has text boxes where the user can enter the his username name and password.If the necessary information is not provided or if invalid inputs are given by the user then the system will pop a message box.
3.1.3 Functional Requirements
Only authorized users are allowed to login. The authorized users are the bank
administrator, deposit officer, loan officer and the other banking staff. If invalid user
name or password is given by the bank the system should inform the user. If
unauthorized users try to access then it should nit allow the user to work on the
system.
3.2 Data Entry module
3.2.1Description and Priority

This module is used by data entry operator who is responsible for entrying the details of a student.The module requests that the Data entry Operator specify the function he/she would like to perform(either Add a student,update a student, or delete a student details).
3.2.2 Stimulus/Response Sequences
Once the Data entry Operator provides the requested information , one of the sub-flows is executed.
• “Add a student” sub flow
• “Update a student” sub flow
• “Delete a student” sub flow
3.2.3 Functional Requirements
In “Add a student” Once the Data entry operator provides the requested information , the student is added to the system and an appropriate message is displayed
In “Update a student” Once the Data entry Operator updates the necessary information ,the system updates the student record with the updated information
In“Delete a student” Once the Data entry operator deletes the record, the system prompt s the user to confirm the deletion of the student.
3.3 Marks Entry Module
3.3.1Description and Priority

This module allows the Marks entry operator to add, delete or modify the student information from the system
3.3.2 Stimulus/Response Sequences
The system requests the Marks entry clerk to specify the function she/he wuld like to perform(either Add Marks,Update marks,Delete Marks and Generate Report).
3.3.3 Functional Requirements
In “Add Marks” Once the Marks entry clerk provide the requested information , the system saves the marks and an appropriate message is displayed
In “Update Marks” the Marks entry operator makes the desired changes to the marks details and at the same time the database will save the changes that are made by the Marks entry operator.
In “Delete Marks” if the clerk wishes to proceed with the deletion of the record on click of this the record is deleted from the system
In “Report generation” the computed result of a particular student is displayed
05-04-2011, 12:25 PM
Post: #13
RE: student management system full report
presented by:
Santosh
Parmjeet Kaur


.doc  Student.doc (Size: 208 KB / Downloads: 510)
REQUIREMENTS
1) Hardware Requirements
a) Processor:- Pentium 866 MHZ
b) RAM:- 64 MB
c) Hard Disk:- 20 GB
d) Keyboard
e) CD-Rom
f) Color Monitor
2) Software Requirements
a) Language Turbo C++
b) Operating System:- MS-DOS
INTRODUCTION TO ‘C++’
C++ was developed by Bjarne Stroustrup of AT&T Bell Laboratories in the early 1980's, and is based on the C language. The name is a pun - "++" is a syntactic construct used in C (to increment a variable), and C++ is intended as an incremental improvement of C. Most of C is a subset of C++, so that most C programs can be compiled (i.e. converted into a series of low-level instructions that the computer can execute directly) using a C++ compiler.
C is in many ways hard to categorize. Compared to assembly language it is high-level, but it nevertheless includes many low-level facilities to directly manipulate the computer's memory. It is therefore an excellent language for writing efficient "systems" programs. But for other types of programs, C code can be hard to understand, and C programs can therefore be particularly prone to certain types of error. The extra object-oriented facilities in C++ are partly included to overcome these shortcomings.
SOURCE CODE
#include<iostream.h>
#include<conio.h>
#include<stdio.h>
#include<string.h>
#include<dos.h>
#include<stdlib.h>

class fee
{
public:

char n[25],cl[10];
long int id,tf,dp,i1,i2,i3,bl;


public:

void get()
{
cout<<" Enter Student Name: ";
gets(n);
gotoxy(2,3);
cout<<"Enter Class: ";
cout<<"\n\n(class name should MCA, BCA, BA)";
gotoxy(15,3);
gets(cl);
gotoxy(2,8);
cout<<"Enter DownPayment: ";
cin>>dp;
}
};

void main()
{
FILE *p;
fee ob;

int c;
clrscr();
while(1)
{

gotoxy(18,8);
cout<<"******************************************";
gotoxy(20,10);
cout<<"Press 1 for Admmission";
gotoxy(20,12);
cout<<"Press 2 for Check All Data";
gotoxy(20,14);
cout<<"Press 3 for Check Individual Class Data";
gotoxy(20,16);
cout<<"Press 4 for Check One Student Detail";
gotoxy(20,18);
cout<<"Press 5 for Deposit Fee";
gotoxy(20,20);
cout<<"Press 6 for Check Fee Structure";
gotoxy(20,22);
cout<<"Press 7 for Exit";
gotoxy(20,24);
cout<<"Enter Your Choice: ";
gotoxy(18,26);
cout<<"******************************************";
gotoxy(39,24);
cin>>c;
clrscr();
switch©
{
case 1:
char y='y';
while(y=='y'||y=='Y')
{

rewind(p);
p=fopen("fdata.dat","rb+");
int count=0;
while(fread(&ob,sizeof(ob),1,p)==1)
{
count=count+1;
}

p=fopen("fdata.dat","ab+");
ob.get();
if(count==0)
{
ob.id=101;
}
if(count!=0)
{
ob.id=101+count;
}
if(stricmp(ob.cl,"MCA")==0)
{
ob.tf=50000;
}
if(stricmp(ob.cl,"BCA")==0)
{
ob.tf=25000;
}
if(stricmp(ob.cl,"BA")==0)
{
ob.tf=7000;
}
09-05-2011, 11:36 AM
Post: #14
RE: student management system full report
Presented by
PHANUEL OTIENO ILLAH


.doc  SOWK DATABASE.doc (Size: 719 KB / Downloads: 386)
ABSTRACT
Department of swasa department has been experiencing a lot of problem especially data track and error in retrieved information there fore it is of great importance to them to take advantage over the this system with the ability to store , process and gives out information with a lot of accuracy.
1.0 INTRODUCTION
The student management system is an improved Student Management System. It can handle all details about a student. The details include lecture, subject details, student personal details e.t.c.
In case of current system they need a lot of time, manpower e.t.c here almost all work is computerized. So the accuracy is maintained. Student management system is managed by an administrator. It is the job of the administrator to insert update and monitor the whole process .The system has four modules. They are
student details
subject details
lecturer details.
1.2 BACKGROUND OF CURENT SYSTEM.
The school of social sciences is a school which track the personal data of student registered in the department each and every year and keeps the record.
Currently they use Microsoft exel to track their data but due to increasing population the excel has become slow in data retrievement and therefore after preliminary investigation I realize that there is a need for a better system.
The current system is a semi computerized system where the data are printed out at the end of every semester to allow new entry of data. The current system they are using Is Microsoft exell which still can not compute complex questions which can be handled by Microsoft access.
1.3 Problem statement
The data in this system are kept manually especially after the end of every semester which makes it difficult to search data after a good number of years when a student need to know some of his details. It takes time to search on the pile of files. Also there are some questions which the system can not answer which has to be done manually like if asked to find subjects which were done by phanuel in 2006. You will have to search manually and write down which actually takes a lot of time.
1.3 Objectives
1.3 .1 General objective.

To develop a database system which can easily store, retrieve and update data.
1.3.2 Specific objectives
• The system is to eliminate their manual counting of student taking a particular subject to a computerized system which can query.
• The system is to shorten the time of retrieving data when required.
1.4 Justification
The current system is unreliable it is likely to deteriorate when the number of students increase in the department. After proposed system every tasks will take short time and no more wastage of files to keep some data which can stay within the system for over years.
1.5 Scope
The system will capture information about student’s personal details lectures and the courses. Storing updating and retrieving in a fast and accurate way.
CHAPTER 2
2. O literature review
2.1 Justification for the use of Access Database

Access database comes over the rest of the databases due to a number of reasons. Being one of the database pioneers, Access has became more easy to use as well as learning because of this it make developing a new database system much quicker compared to others such as Oracle, My sql etc. Microsoft access has been considered because of its ability to support and enhance the appearance and navigation of html generated. (Carry N Prague,micheal R. Irwin,and jennifer Reardon access 2003 bible pg952) The fact that access is always upgraded makes it easier and compatible with new systems. For example Access 2003 uses ASP technology which also complies with new technologies such as XML. (Cary N Prague, Micheal R. Irwin, and Jennifer Reardon access 2003 bible)
Access was most preferred because of its ability to create dynamic data and html pages and they can be displayed in Microsoft Explorer 5.0. Cary N Prague, Micheal R. Irwin, and Jennifer Reardon access 2003 bible Access has the ability to export and import data through ADODB which is a common connector among most web application. MySql Though MySql is well known for being capable of handling very powerful and large data bases it also has a couple of setbacks that the developer could not take chances with it. MySql does not support transactions or concurrent update of complex table which if used would have become a huge hindrance to the development of the system in the making. Oracle Oracle is very well known for the use of SQL statements. It is one of the most expensive databases on the market. There is no graphical interface for creation or modification of tables. This implies that the use of this database is very time consuming.
2.2 Justification for the use of SQL
This is also another data retrieving language that is used by most databases i.e. Microsoft Access, Oracle and MySql. There are quite a number of reasons for the use of SQL. One of the most common reasons why most web developers’ use this language is because it is easy to use and a standard query language that can be used for both database and web pages. Because of the fact that SQL is can be used to manipulate data in all ways, it can be used to retrieve, create, store or even update records.
2.3 Feedback- for every action on a system:
A feedback is necessary in order to confirm that the action been executed or accomplished for without feedback it becomes difficult to continue or to move to the next level. On designing the interaction design the designer require design principle guiding tool. Feedback is one of the guiding principles, this is very essential for both the user and the designer because it is an aspect that can lead them to the next step of their task. These principle are based on common sense, experience as well as theory based knowledge. In order to have a well designed interface the most common principles one ought to observe are consistency that is the ability to observe uniformity, visibility, affordance and constraint. In the simplest terms these principles could be defined as:
Uniformity:
Consistency is very vital and this refers to the ability to maintain uniformity in the system interaction design. This implies the system follows a certain criteria for example: The use of certain operations to log on to a system. All in all, consistence makes learning very easy and quick for the new users as well as the existing ones. April 13, 2009 BSC(HONS) BUSINESS INFORMATION SYSTEM 21
Visibility:
The visibility of functions enable the user to know how to manipulate or use the system, for that matter it’s very important to mind where and how functions are placed, as for the case of the system, the making of links and icons are very important because they have to be visible enough.
2.4 Affordance:
Affordance is another principle that could refer to clues that enable the user to know how to use the system it is also defined as “an attribute of an object that allows the people to know how to use it” (interaction design beyond human-computer interaction 2nd edition by John Wiley & sons, ltd page 33) though affordance is categorised into two and that is real and perceived affordance.
2.5 Constraint:
Constraint can be referred to as controls or limitations that are within a system allowing what actions to be done during the interaction the common constraint use is the deactivation of some menus while another action still executes. This is very important because if graphical representations that are used to constraint the users’ interpretation of a problem or information. (Interaction design beyond human-computer interaction 2nd edition by John Wiley &sons,ltd page 31) As for the case of the patients’ online booking system, it could be referred to as perceived affordance because it is web base which means it is virtual. Therefore all the mentioned principle should be present in a well designed system and all these can be witnessed in the finished product of the patients booking system. There are quite a number of problems that might a result from the need to apply all design principles. The attempt to recreate physical objects into a virtual form in order to achieve affordance may result into absolute difficulty to be used. In that case such a principle could be ignored. Visibility of information may be compromised if constraint is over emphasised within an interface. All in all these design interaction principles are all applies trade-offs may occur. (Interaction design beyond human-computer interaction 2nd edition by John Wiley&Sons Ltd page34)
CHAPTER 3
3.0 Methodology

After the feasibility studies it was decision time to decide what methodology will suit the development of the required system. The system to be developed for the project will be done by applying software engineering tools and techniques. The analysis and design is concerned with understanding the current and the proposed system requirements. In other to do this systematically, a methodology will be applied so as to go through the systems development life cycle.
The life cycle is the process of development which is to be followed in stages in order to develop a computerized information system. These stages are to be developed in sequence and one stage has to be completed before going on to the next stage.
It is a bit difficult to define the term methodology but still there are many definitions from different authors. Here are some few of them
[Check land, 1981]: “a methodology is a set of principles which in any particular situation have to be reduced to a method uniquely suitable to that particular situation.”
[Avision & Wood-Harper, 1995 Pg. 20]: “a coherent collection of concepts, beliefs, values and principles supported by resources to help a problem-solving group to perceive, generate assess and carry out in a non-random way changes to the Information situation.”
[Vision & Fitzgerald, 1988]: “a methodology is a collection of procedures, Techniques, tools and documentation aid which consists of phases...but a Methodology is more than merely a collection of these things. It is usually based on some philosophical view, otherwise it is merely a method, like a recipe.”
After analysis and design here are some of the methodologies which I considered before coming up with the final methodologies I used in order to achieve the development of a system which will meet the specification of the users with bounds specified by the business. be working and reliable meet the requirements of the users, i.e. meet the business objectives of the users.
This is Yourdon Structured Method (YSM) and Soft Systems
Yourdon Structured Method (YSM) was derived from the works of Edward Yourdon, Tom DeMarco and Larry Constantine. This methodology was considered for the project development. Reasons for considering the methodology are:
It has been updated on a regular basis since its appearance on the system development scene so it is hoped it will meet a modern day system development demands.
It also have a good modeling tool which is expected will suit the system developed.
Though the methodology was considered I found it will not be suitable for the
Development of the proposed system. The reasons for its rejection are:
It stages are not precisely defined and it is not well documented
It does not lay much emphasis on modeling current system. It advocates going straight to the modeling of the required logical system. This is not advisable for the current project as the current system needs to be understood to be able to propose a required system.
Soft Systems Method which was derived from the work of Check land (1981, 1990) was also considered for the project. The reasons behind the consideration were:
The methodology approach concentrates on the human aspects of a problem area it finds way of improving human activities mainly business objectives which may or may not be associated with automation i.e. computerization.
Despite these attributes the methodology was not deemed right for the development of this system.
The reasons being: the methodology does not believe in breaking down complex problems into smaller fragments.
Breaking down of the problem is needed for this project as this will help in understanding of the problem domain very well.
It does not operate in a tightly defined and more prescriptive manner, i.e. it is not well structured. It is flexible, which can lead to confusion in system development to a junior analyst like me.
It identifies a problem but does not really suggest ways of solving the problem, leaving the analyst to provide options for solving the problems themselves. One of the main reasons for using a methodology is to tackle the problems associated with lack of control and non-standard of methods in system development which is compromised by Soft Systems Methodology.
After consideration of several methodologies there are two methodologies are used for the development of the system. They are Structured Systems Analysis and Design Method (SSADM4) Version 4
Prototyping For the design, Structured Systems Analysis and Design Method (SSADM) will be used while Prototyping will be used for the implemented process. The type of prototyping to be used will be incremental prototyping.
Structured System Analysis and Design Methods, SSADM is a systematic approach to the analysis and design of Information Technology, IT applications designed by Central Computer and Telecommunication Agency, CCTA. It is a collection of activities which exploit a collection of techniques. These techniques include Data Flow Modeling, Logical Data Modeling, Relational Data Analysis and many more.
11-05-2011, 11:40 AM
Post: #15
RE: student management system full report


.doc  SMS.doc (Size: 837.5 KB / Downloads: 514)
INTRODUCTION:
The Student Management System can handle all the details about a Student.
The details include College details, Course details, Students personal details, Academic details etc., The Student Management System is an automated version of manual Student Management System.
SYSTEM REQUIREMENT ANALYSIS (SRA)
1. PROBLEM DEFINITION:

The College Management has to handle records for many number of students and maintenance was difficult. Though it has used an information system, it was totally manual. Hence there is a need to upgrade the system with a computer based information system.
2. EXISTING SYSTEM:
All the details of the student are maintained in a single record.
So searching and upgrading the details is a tedious task. Also there is a chance of errors.
PROPOSED SYSTEM:
By developing the system we can attain the following features:
• Easy to handle and feasible
• Cost Reduction
• Fast and Convenient
3. PROJECT DESCRIPTION:
Our system has two types of accessing modes,
1. Administrator
2. User
i) Administrator:
SMS is managed by Administrator. Administrator has to update
and monitor the registered student details , provide register number for all students, generate hall tickets for all students, evaluate examination marks and allocate fees for each course etc.,
ii) User:
User can only view their personal details, fees details, examination schedule, mark sheet, download hall tickets for each semester.
4. PURPOSE OF THE PROJECT:
Developing a proper managed SMS for the Academic Institution becomes the essence to let the users – students, teachers to gain the information about the institution.
The Objective can be listed below as:
• To provide a proper registration channel / system to the new students.
• To maintain all the accounts of the students from enrollement upto the end of the study.
• To update the information that is essential to transmit to the users.
• To have a centralized control over the records of the students, departments, teachers, staffs, library, etc., and monitor the changes in these records.
SOFTWARE REQUIREMENT SPECIFICATION(SRS):
SOFTWARE REQUIREMENTS:

Operating system : Microsoft XP/2000/VISTA/Windows 7
Platform : Visual Studio 2005
Database : Oracle/Access
Application Software : MS Office 2003
HARDWARE REQUIREMENTS :
Processor : Pentium
RAM : 128 MB RAM
Hard Disk : 40 GB Hard Disk
FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS:
1. Functional requirements:
Student Management System involves the following functions
A) Student Admission:
1. SMS provides online registration and status information to the student to view their application status.
2. SMS provides automatic student register number generation based on course and year.
B) Fees Management:
1. SMS provide a fee management system to define various fees based on semester, annual, one-off-payment and tuition fee.
2. A Student can pay through the bank and in turn the bank sends a soft copy of the transaction to the university.
C) Student Attendance Management:
1. Easily track attendance information of students.
2. Quickly produce single or multiple day attendance bulletins.
D) Examination Management:
1. SMS provides a comprehensive examination scheduling based on course.
2. Students can facilitate to download their hall tickets by entering their register number.
E) Mark Evaluation Management:
1. Student CGPA will be calculated automatically based on the student mark and the grade setting made in the system.
2. Deficiency point will be calculated based on the CGPA and the academic status of the student will be set based on this point.
Non-Functional Requirements:
A) Security:
Only authorized users can access the system with username and password.
B) Performance:
Easy tracking of records and updation can be done.
C) User Friendly:
The System is very interactive.
D) Maintainability:
Backups for database are available.
USECASE DIAGRAM:
DESIGN:
MODULES AND DESCRIPTION

Student Management System contain the following modules:
• Login Module
• Student Details Module
• Result Module
• Subject Module
• Schedule Module
1. Login Module:
In login module separate login will be create for Administrator and Student.
Student can view Result, Subject details, and Exam Schedule in their login.
Administrator can access the students record and update any changes in their login.
2. Student Details Module:
Student information can be added, deleted, updated and any particular record can be searched and viewed.
3. Result Module:
Each student grades will be calculated and the result will be displayed in this module.
4. Subject Module:
This modules deals with subject details. It performs addition, deletion, updation and we can view the list.
5. Schedule Module:
Examination Schedule and events schedule will be done in this module.
29-05-2011, 10:59 PM
Post: #16
RE: student management system full report
Student Information System along with college details implemented using JAVA

Java Project report
Under the guidance of Mr. Rajeev Gupta
What is the significance of MVC model ?
It ensures that applications are well designed with greater maintainability by integrating the well established Model-View-Controller (MVC) design pattern into its architecture. So it clearly separates behavior (Model) and presentation of data (View) in an application. UI components represent View (Typically in JSP), managed logics represent Model and Servlets are the Controllers . All the requests are handled by this controller. Any request passes through and examined by Servlets that calls various actions on the model (managed logic). The separation of behavior and presentation enables a wide range of users Page authors( web-page designers), Application developers, Component writers, Application architects , Tool vendors and allows members of team to focus on their own work only , resulting in division of labor and shorter development cycle.

Project Details
Student Information System along with college details
List of Modules
Model Classes
1.Conjdbc.java
2.Enterdb.java
3.Upadatedb.java
4.Updatedb1.java
5.deletedb1.java

Controllers servlets
1.control.java
2.Control1.java
3. Control2.java
4. Control3.java
5.Control5.java
6.Control6.java
7.Control7.java
8.Control8.java
9.Control9.java

Uml Diagram for student
Uml Diagram for Administrator
Database Schema



.rar  Student Information System along with college details.rar (Size: 1.72 MB / Downloads: 796)

Please Use Search http://seminarprojects.com/search.php wisely To Get More Information About A Seminar Or Project Topic
07-06-2011, 07:00 PM
Post: #17
RE: student management system full report
Hi i would like to run this project ,, i tried in local host its not working.,,


can u guide me haw to run,,

which are software i have to install..
12-06-2011, 12:50 PM
Post: #18
RE: student management system full report
fdgsdgsgsd bsgsdgsdg sdgsdg sdg sg sgsd gsd gsd gsd gs g sdgsd g sdg s g sd gsd sd sd g gs dg sdg sd gsd gsd gsd gs dg sdg sd gsd gs dg sdg sdg sd gds gds g sdg sd g sdg sd g s faw rtawg sd gsd gsd g sdg sd gsd g sd g sd gsd
09-07-2011, 02:32 PM
Post: #19
RE: student management system full report

.docx  documentation.docx (Size: 743.95 KB / Downloads: 411)
ABSTRACT
Our project explains about the student management. This project mainly explains the various actions related to student details. This project shows some ease in adding, editing and deleting the student details. It also provides a less time consuming process for viewing, adding, editing and deleting the marks of the students.
Our project includes
• Student Registration
• Subject Allocation
• Branch selection
• Semester wise selection.
• Examination marks entry
• Displaying branch and semester wise result.
1. INTRODUCTION
Student Management System is software which is helpful for students as well as the school authorities. In the current system all the activities are done manually. It is very time consuming and costly. Our Student Management System deals with the various activities related to the students.
There are mainly 3 modules in this software
• User module
• Student Module
• Mark management Module.
In the Software we can register as a user and user has of two types, student and administrator. Administrator has the power to add new user and can edit and delete a user. A student can register as user and can add edit and delete his profile. The administrator can add edit and delete marks for the student. All the users can see the marks.
2. SYSTEM ANALYSIS
2.1 EXISTING SYSTEM:

System Analysis is a detailed study of the various operations performed by a system and their relationships within and outside of the system. Here the key question is- what all problems exist in the present system? What must be done to solve the problem? Analysis begins when a user or manager begins a study of the program using existing system.
During analysis, data collected on the various files, decision points and transactions handled by the present system. The commonly used tools in the system are Data Flow Diagram, interviews, etc. Training, experience and common sense are required for collection of relevant information needed to develop the system. The success of the system depends largely on how clearly the problem is defined, thoroughly investigated and properly carried out through the choice of solution. A good analysis model should provide not only the mechanisms of problem understanding but also the frame work of the solution. Thus it should be studied thoroughly by collecting data about the system. Then the proposed system should be analyzed thoroughly in accordance with the needs.
System analysis can be categorized into four parts.
 System planning and initial investigation
 Information Gathering
 Applying analysis tools for structured analysis
 Feasibility study
 Cost/ Benefit analysis.
In the current system we need to keep a number of records related to the student and want to enter the details of the student and the marks manually. In this system only the teacher or the school authority views the mark of the student and they want to enter the details of the student. This is time consuming and has much cost.
2.2 PROPOSED SYSTEM
In our proposed system we have the provision for adding the details of the students by themselves. So the overhead of the school authorities and the teachers is become less. Another advantage of the system is that it is very easy to edit the details of the student and delete a student when it found unnecessary. The marks of the student are added in the database and so students can also view the marks whenever they want.
Our proposed system has several advantages
 User friendly interface
 Fast access to database
 Less error
 More Storage Capacity
 Search facility
 Look and Feel Environment
 Quick transaction
All the manual difficulties in managing the student details in a school or college have been rectified by implementing computerization.
07-08-2011, 11:19 AM
Post: #20
Thumbs Up RE: student management system full report
Please i need u to post me diagrams, images, design of this project. I'll appreciate.
08-08-2011, 10:45 AM
Post: #21
RE: student management system full report
To get more information about the topic " student management system full report" please refer the link below

http://www.seminarprojects.com/Thread-st...6#pid53806
10-08-2011, 09:51 AM
Post: #22
RE: student management system full report

.docx  SCHOOL MANAGEMENT SYSTEM.docx (Size: 7.68 MB / Downloads: 1056)
Why is SMS so important these days?
1. All in all, the SMS function is still to a large degree administrative and common to all institutes.
2. To varying degrees, most institutes have formalized selection, evaluation, and payroll processes.
3. Efficient and effective management of the “STUDENT AND FACULTY POOL” has become an increasingly imperative and complex activity.
4. The SMS functions consist of tracking innumerable data points on each student, from personal histories, data skills, capabilities, experience of faculty members and other necessary records.
5. To reduce the manual workload of these activities, institutes began to electronically automate many of these processes by introducing SMS technology.
6. The SMS are characteristically developed around some important principals like:
 Student’s personal as well as educational information.
 Faculty personal as well as educational information.
 Salary information of the faculty.
 Attendance of the students as well as the faculty.
 Fee Structure and maintenance.
 Maintaining annual records.
 Reports on performance of the students.
 Maintaining records on purchase of books and articles.
ABOUT MODEL ENGLISH SCHOOL
MODEL ENGLISH SCHOOL was started in the year 1978.
It is managed by Keraleeya Samajam ,Dombivli.
Presently, there are more than 5,000 students and more than
50 teaching and non-teaching staffs.
It has 4 branches in Dombivli.
It has successfully completed 25 years .
NEED FOR SMS.
As we had already seen the need for SMS for the institutes and also the background of Model English School. We therefore need to see why MES needs such software.
The main reason can be thought as the problem of having manual entry procedures
Such as:
 Large time for processing.
 Data redundancy and maintenance.
 No data security.
 No facility for easy retrieval of data
 No data modification facility.
 Difficulty in managing large data
 Upgrades, dropouts, breaks
 No priority to generate reports.
Thus SMS have tried to sort out many of the problems faced by the institutes.
Thus using SMS provides many of the facility like attendance, salary structure, and even performance analysis.
10-08-2011, 01:59 PM
Post: #23
RE: student management system full report

.doc  Student.doc (Size: 625.5 KB / Downloads: 285)
INTRODUCTION
Student Management System is software which is helpful for students as well as the school authorities. In the current system all the activities are done manually. It is very time consuming and costly. Our Student Management System deals with the various activities related to the students.
There are mainly 3 modules in this software
• User module
• Student Module
• Mark management
In the Software we can register as a user and user has of two types, student and administrator. Administrator has the power to add new user and can edit and delete a user. A student can register as user and can add edit and delete his profile. The administrator can add edit and delete marks for the student. All the users can see the marks.
SYSTEM ANALYSIS
EXISTING SYSTEM:

System Analysis is a detailed study of the various operations performed by a system and their relationships within and outside of the system. Here the key question is- what all problems exist in the present system? What must be done to solve the problem? Analysis begins when a user or manager begins a study of the program using existing system.
During analysis, data collected on the various files, decision points and transactions handled by the present system. The commonly used tools in the system are Data Flow Diagram, interviews, etc. Training, experience and common sense are required for collection of relevant information needed to develop the system. The success of the system depends largely on how clearly the problem is defined, thoroughly investigated and properly carried out through the choice of solution. A good analysis model should provide not only the mechanisms of problem understanding but also the frame work of the solution. Thus it should be studied thoroughly by collecting data about the system. Then the proposed system should be analyzed thoroughly in accordance with the needs.
System analysis can be categorized into four parts.
 System planning and initial investigation
 Information Gathering
 Applying analysis tools for structured analysis
 Feasibility study
 Cost/ Benefit analysis.
In the current system we need to keep a number of records related to the student and want to enter the details of the student and the marks manually. In this system only the teacher or the school authority views the mark of the student and they want to enter the details of the student. This is time consuming and has much cost.
PROPOSED SYSTEM
In our proposed system we have the provision for adding the details of the students by themselves. So the overhead of the school authorities and the teachers is become less. Another advantage of the system is that it is very easy to edit the details of the student and delete a student when it found unnecessary. The marks of the student are added in the database and so students can also view the marks whenever they want.
Our proposed system has several advantages
 User friendly interface
 Fast access to database
 Less error
 More Storage Capacity
 Search facility
 Look and Feel Environment
 Quick transaction
All the manual difficulties in managing the student details in a school or college have been rectified by implementing computerization.
FEASIBILITY ANALYSIS
Whatever we think need not be feasible .It is wise to think about the feasibility of any problem we undertake. Feasibility is the study of impact, which happens in the organization by the development of a system. The impact can be either positive or negative. When the positives nominate the negatives, then the system is considered feasible. Here the feasibility study can be performed in two ways such as technical feasibility and Economical Feasibility.
Technical Feasibility:
We can strongly says that it is technically feasible, since there will not be much difficulty in getting required resources for the development and maintaining the system as well. All the resources needed for the development of the software as well as the maintenance of the same is available in the organization here we are utilizing the resources which are available already.
Economical Feasibility
Development of this application is highly economically feasible .The organization needed not spend much money for the development of t he system already available. The only thing is to be done is making an environment for the development with an effective supervision. I f we are doing so , we can attain the maximum usability of the corresponding resources .Even after the development , the organization will not be in condition to invest more in t he organization .There fore , the system is economically feasible.
31-08-2011, 08:27 AM
Post: #24
RE: student management system full report
i need full documentation for STUDENT RESULT MANAGEMENT SYSTEM please help me
01-09-2011, 10:04 AM
Post: #25
RE: student management system full report
To get more information about the topic " student management system full report" please refer the link below

http://www.seminarprojects.com/Thread-st...1#pid55991

http://www.seminarprojects.com/Thread-st...ull-report

http://www.seminarprojects.com/Thread-st...ort?page=2

http://www.seminarprojects.com/Thread-st...ort?page=3

http://www.seminarprojects.com/Thread-st...ort?page=4
Rating student management system full report Options
Share student management system full report To Your Friends :- Seminar Topics Bookmark
Post Reply 

Marked Categories : c project, school management project documentation, dfd for library managment in asp net c, c project on student management system, student details project, problem of student management system, student management system project, screen shots for student admission system project in net, student management system, online share market using dbms, student management system in java, college database management system project in asp net, er diagram for student progress report, list of project for i t students with e r diagram, academic management system, context level data flow diagram for college management system, dfd diagram for old student information system,

[-]
Quick Reply
Message
Type your reply to this message here.


Image Verification
Image Verification
(case insensitive)
Please enter the text within the image on the left in to the text box below. This process is used to prevent automated posts.

Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  PDA DRIVEN WAREHOUSE INVENTORY MANAGEMENT SYSTEM computer science crazy 0 0 Yesterday 05:29 PM
Last Post: computer science crazy
  Courier Management System full report seminar tips 5 13,268 30-05-2016 10:32 AM
Last Post: dhanabhagya
  Secure Net Auction System full report smart paper boy 4 3,640 20-05-2016 03:06 PM
Last Post: dhanabhagya
  college website project full report project report tiger 51 142,170 07-05-2016 09:52 AM
Last Post: dhanabhagya
  telephone management system project report helper 3 8,797 25-04-2016 12:38 PM
Last Post: mkaasees
  HOSPITAL MANAGEMENT SYSTEM full report project topics 21 60,027 16-04-2016 09:42 AM
Last Post: mkaasees
  college management system project report helper 7 5,632 11-04-2016 02:18 PM
Last Post: dhanabhagya
  Full Report on Online Job Consultancy System study tips 2 3,870 08-04-2016 10:30 AM
Last Post: mkaasees
  RATIONSHOP INVENTORY CONTROL SYSTEM full report smart paper boy 30 17,592 07-04-2016 11:43 AM
Last Post: mkaasees
  ONLINE MOBILE RECHARGE FULL REPORT project girl 1 1,558 06-04-2016 02:16 PM
Last Post: mkaasees
This Page May Contain What is student management system full report And Latest Information/News About student management system full report,If Not ...Use Search to get more info about student management system full report Or Ask Here

Options: