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
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: 838)
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: 459)
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: 344)
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: 461)
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.
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
  Organization Administrative Support System with Fingerprint & Barcode Integration seminar code 0 10 Yesterday 03:03 PM
Last Post: seminar code
  Customer Relationship Management System(CRM) seminar code 0 13 Yesterday 03:02 PM
Last Post: seminar code
  Construction Resource Management seminar code 0 8 Yesterday 03:00 PM
Last Post: seminar code
  college management system seminar code 0 6 Yesterday 02:57 PM
Last Post: seminar code
  College Alumni Management System seminar code 0 7 Yesterday 02:57 PM
Last Post: seminar code
  Cloud Based Outstation Claim Calculation System seminar code 0 9 Yesterday 02:57 PM
Last Post: seminar code
  CITIZEN CARD SYSTEM seminar code 0 11 Yesterday 02:50 PM
Last Post: seminar code
  Online Salary Management System seminar code 0 10 Yesterday 02:48 PM
Last Post: seminar code
  E-Institute Management System seminar code 0 9 Yesterday 02:45 PM
Last Post: seminar code
  Real Estate Management System seminar code 0 17 Yesterday 02:43 PM
Last Post: seminar code
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: