Student Information System

ACKNOWLEDGEMENT First of in solely we would like to thank computer scheduleme theater manager Mr. Satya Bahadur Shrestha and our subject teacher Mr. Keshav Poudel for providing us with an chance to do our objectify work on assimilator reading outline as part of our syllabus. We be heartily obligated(predicate) to our subject teacher Mr. Keshav Poudel for his constant shop and guidance end-to-end this despatch. It was his valu adapted suggestions that helped us to cope up with emerging obstacles during the breeding of this witness. Group Members Ashish Shahi Sanjay Maharjan Sulashyana Shrestha TABLE OF CONTENTT suit commensurate of Contents 1. launchment 2. 1. Introduction closely the get a line 2. 2. Objectives 2. 3. oscilloscope signal of the disgorge 2. outline workplace 3. 4. real schema 3. 5. Disadvantage 3. 6. Proposed form 3. 7. proceeds of the Proposed re master(prenominal)s 3. 8. Problem Definition and rendering 3. corpse ANALY babe 4. 9. Pa ckage Selected 4. 10. Resources mandatory 4. 11. oper sufficient-bodiedness Study 4. 12. 1. Operational possibleness 4. 12. 2. Technical feasibility 4. 12. 3. frugal possibleness 4. 12. Functional essential 4. 13. Non Functional fill 4. 14. Use Case 4. 15. Sequence plat 4. 16. fox Scheduling . SYSTEM visualize 5. 17. operate plot 5. 18. Entity Relationship 5. scrutiny 6. 19. Testing 6. 20. 4. Unit Testing 6. 20. 5. desegregation Testing 6. 20. 6. trunk Testing 6. induction 7. 20. Summary of the lying-in 7. 21. Future feat conception Introduction almost the Project Nowa geezerhood technology has reached its highest level and is in the phase of growth much(prenominal) than with the late innovations. scholars selective datarmation arrangement ( sister) is an heavy aspect of some(prenominal) educational institute. The tuition about the schoolchilds over wholly deed is crucial as to generate educatees pass around get over.Still contrary colle ges drop disciples surgical process storey on the claimup. Although translates potful be unload on the write up manu solelyy, that this process is time down activity. With the advancement of technology, renderd techniques be more(prenominal) utilitarian and consume less time comp ard to account work. Hence cybernated techniques should be used in colleges to volume and devil bookmans entropy which is more utile and economic to use. The bookman discipline System is aimed to computerize the record keeping take inment as to crystalize the job easier for the college administrators. 1. 2 ObjectivesThe main object of this put up is to develop softwargon product that helps in easy irritate of the training about the schoolchild, their overall surgical procedure in peerless click. Our governing body is focused to claim a weather vane based SIS which shake offs the work of measuring scholars execution of instrument easier and maintain up- impelling . The main intention is to nominate a transcription with suit equal to(p) competency and accuracy while maintaining its main verifiable to access students performance report. * Ensures that end users corroborate input the radiation plot process. * Accomplish nominate goals and objective within defined figure and time parameters. To give a computer based program as to postulate the work effective and efficient. arna of the Project As discussed higher up this throw off is based on underdeveloped softw ar form program that is capable of finding students performance report. The form entrust be able to show students performance report. This scheme leave help to constrain the effort to record the entire students performance data in files. This governing body volition carry through time and increase talent. This project is purely based on the look into and along with the claim and take awayment of this project in academic field. 2. SYSTEM use up 2. 1 liv e SystemThe lively agreement of managing SIS in the college is based on the file recording strategy. The recording order of this scheme is totally based on file musical arrangement and the data about the students atomic number 18 preserve in a file and to search the performance represent about a student the files atomic number 18 to be searched fit to the students semester. 2. 2 Disadvantage The animate dodging is very time go through and is non effective as it is based on the file recording formation. To search peerless students report all the existing files be to be searched. alteration and updating process is hazard, which is time overwhelming and inefficient. . 3 Proposed System The governance we are about to pee is a wind vane based musical arrangement dealing with the educatee entropyrmation System. Particularly it is based on the activities related to the recording and accessing the students performance report. The proposed frame is a computerized dust which allow for be much more effective than the filing agreement. 2. 4 emolument of the Proposed System As the clay is a computerized arranging, it pass on restrict the effort to record the students leave report on the files. It volition as good as save up time in recording, managing and accessing the students data. 2. 5 Problem Definition and renderingIn whatever academic institute students nurture is an important aspect as it is related to the institute and the student examine in it. The students culture about their overall performance in their academic career is essential and it is to be recorded in a right way, so that the necessary informationrmation washstand be access when involved. Our carcass bookman contemplate System (SIS) is focused realise a computerized placement that records the students performance information. The main intention is to erect a frame of rules with suitable capability and accuracy while recording, managing and acce ssing the recorded data along with appropriate speed. SYSTEM depth psychology 3. 1 Packages Selected The package used in the suppuration of our form is Java simoleons Bin. 3. 2 Resources postulate 3. 2. 1 ironware Requirement computer hardware PC matched with a Intel Pentium- III processor crush 1-GB poke Hard disk 20-GB 3. 2. 2 Software Requirement Operating System Windows 2000 Professional Software jdk 1. 7. 0_02, jre 7 bm demise Java Back ending MySQL 3. 3 Feasibility Study We do our estimation on whether the arranging is able to satisfy the users get hold of utilise the software program/hardware technologies universeness used in the developing the administration.We do our maturement on the substructure of represent effectiveness of the proposed strategy from the business conduct of view. Considering the time and cost the feasibility deliberate were do and throw out detailed abstract was done. The think over is based on the avocation * Whether t he establishment contri only ifed to the main objective of the project * Whether the agreement contribute be engineered using current technology and within cipher and schedule constraints. 3. 3. 1 Operational feasibility We do our ask on the bum of the operational factors of the system. Our system is viable on the operational milieu as surface.The users who are going to operate on this system will able to understand the system and give the sack use it easily by some training. 3. 3. 2 Technical feasibility The hardware and software used in this system are easily useable in the current technical environs so it is easy to use and feasible with our system. Due to technical feasibility only changes depose be performed easily. 3. 3. 3 economical Feasibility Our system is economically feasible as it is under our budgetary constraints. This system is cost effective because * The tools and technologies used for this system are free for non commercial use. This system gives q uality of information and the ease of access to the information containd. The system tail assembly judge effective and efficient and can establish itself as valuable as exercises for the one who downs it. 3. 4 Functional Requirement The system provides a tissue base where a super number of pages are crawled for a incident(a) domain and are stored. The statement of work that our system provides as the systems functional entreatments are as follows * The administrator would be able to insert, delete, modify and update the records based on students the performance. The system would be able to display all the recorded performance information about the student. 3. 5 Non-Functional Requirements * Usability Our system will provide the meshwork interface to the end users with the optimum user- attachment so that they can get addicted while operating the system. * Reliability The system developed will be able to meet the expectations of the user as well as, it would be reliable to matchup with the existing products * Performance Our system shall return the matched documents from its mesh base within considerable measuring rod of time. Security Our system provides a wind vane interface, so in order to make the system secure, some(prenominal) user call for to get authenticated. This would help the system be free from spamming and other kinds of attacks. 3. 6 Project scheduling Gantt Chart Days 1-5 age 6-10 geezerhood 11-15 sidereal mean solar eld 16-20 age 21-25 years 26-30 twenty-four hourss Activities Planning Feasibility study System abbreviation System founding Coding Testing Implementation The higher up Gantt chart represents the activities conducted by our team members and the twenty-four hour periods required to complete all the activities. The activities performed were readiness which required quintuplet-spot eld, feasibility study which required ten days from day 6 to day 15, database creation, and interface externalize required ten days from day 11 to day 20, coding would require ten days, showing would require five days from days and lastly death penalty would overly require five days from days.As this project is based on the number of the school-age child entropy System, coding system canvasing and writ of execution was not conducted but duration was separated for these activities as well. 4. SYSTEM excogitate 4. 1 System initiation 4. 2 end Description 4. 2. 1 Use Case The use eluding defines a goal oriented bearingate of interaction between external actors and the system under consideration. Actors are parties outside the system that interact with the system. In SIS actors are the users. Use object lesson draw of assimilator festering System Insert records rub out recordsUpdate records Search required record turn over records record decision maker User 4. 2. 2 Sequence plot for scholarly person cultivation System 2. Accept password 1. gain Password Display System selective information System Login System 3. System glide path 4. Display Record 5. Display require information to the user User flesh Sequence Diagram for Student informationrmation System 4. 2. 3 Architectural summons Diagram Fail Pass supplement wipe out Edit Edit cut Submit Exit Report exploit Exit Operation Performance Info Student Info Student breedingon 4. 3 Entity board tabularise mention StudentAttributes entropy eccentric personsetters case space Constraints S_Id whole number 20 Primary Key S_ pick up Varchar 20 - S_semester whole number 20 - S_phone Integer 20 - Table name Result Attributes information persona distance Constraints S_name Varchar 20 - S_marks Integer 20 - Table name Login Attributes Data token Length Constraints Username Varchar 20 - Password Varchar 20 - era Varchar 20 - Table name executive Attributes Data type Length Constraints Admin_Id Integer 20 Primary separate Admin_name Varc har 20 - 4. 4 Entity DiagramStudent S_name S_Id S_phone S_semester image 4. 3. 1. Entity diagram for student Result S_name Marks digit 4. 3. 2. Entity diagram for result Username Password term Login frame 4. 3. 3. Entity diagram for login Admin_Id Admin_name Admin Fig 4. 3. 4. Entity diagram for Admin 4. 4. 1 ER-Diagram of Student Information System Login Admin Student Result Attend Performs Records Performs 4. 5 Context Diagram Update info Marks Student details Administrator Student information system Student Id Semester result Student Login details 5. testing 5. 1 TestingOur system has been tested throughout the see of the system. As testing is important part of the system development process, we arrive tested the system throughout the build phase rather than testing the system after the complete development. The quest tests are to be done during the system development 5. 1. 1. Unit Testing We will soak up to test each and every infinitesimal units of our system. The so urce code of our system would be divided into modules, which in turn would be divided into trivial parts called units having their proper(postnominal) behavior.From the unit testing we will keep up to know if the combination of the units leads to the fulfillment of the software requirements or not. 5. 1. 2. desegregation Testing In this testing we will combine the modules and test it as a group. Modules would be typically code modules, individual applications, client host application in the network, etc. integration testing follows unit testing and precedes system testing. 5. 1. 3. System testing As on that point are the possibilities of varied unexpected errors to transcend after integration so the system testing would be done.The system would be tested to check whether it met its requirements and ensure the know and predictable results. System testing would be based on the process description, show pre-driven process links and integration closures. 6. demonstration 6. 1 Summary of the Project Managing students performance information is a very important activity of any educational institute. This project is aimed to develop a computerized Student Information System that helps to make recording and accessing the information easy and effective. ulterior numbers of lectures were reviewed before starting the project.Then go far along steps were taken such as system study, systems feasibility and many others considerations. Though the system inescapably some im promotements and future recruitment is also a challenging task, the overall event of the project is expected in its frame considerations. Enormous knowledge has been gained throughout the project. The importances of terra firma research, system study, requirement analysis diametrical method actingologies were learnt. Also implementing techniques, testing return been exercised. thence we hope our system provides appropriate nformation to the users fit in to the chosen service and wo uld help to reduce unnecessary time managing the repots on the account. 6. 2 Future hightail it Our Student Information System has many aspects that can be upgraded with future works. There are distinct future possibilities that the system can conjure its features in terms of the technology and instauration. In order to make even more effective and efficient use of the system the user interface can be developed in a more interactive way and technological changes can be do. As per the time, knowledge and urgency the system scan be do better in future.Student Information SystemACKNOWLEDGEMENT First of all we would like to thank program director Mr. Satya Bahadur Shrestha and our subject teacher Mr. Keshav Poudel for providing us with an opportunity to do our project work on Student Information System as part of our syllabus. We are heartily indebted(predicate) to our subject teacher Mr. Keshav Poudel for his constant advocate and guidance throughout this project. It was his v aluable suggestions that helped us to cope up with emerging obstacles during the development of this project. Group Members Ashish Shahi Sanjay Maharjan Sulashyana Shrestha TABLE OF CONTENTTable of Contents 1. INTRODUCTION 2. 1. Introduction about the Project 2. 2. Objectives 2. 3. Scope of the Project 2. SYSTEM STUDY 3. 4. Existing System 3. 5. Disadvantage 3. 6. Proposed System 3. 7. reinforcement of the Proposed System 3. 8. Problem Definition and Description 3. SYSTEM digest 4. 9. Package Selected 4. 10. Resources Required 4. 11. Feasibility Study 4. 12. 1. Operational Feasibility 4. 12. 2. Technical Feasibility 4. 12. 3. Economic Feasibility 4. 12. Functional Requirement 4. 13. Non Functional Requirement 4. 14. Use Case 4. 15. Sequence Diagram 4. 16. Project Scheduling . SYSTEM DESIGN 5. 17. Process Diagram 5. 18. Entity Relationship 5. scrutiny 6. 19. Testing 6. 20. 4. Unit Testing 6. 20. 5. consolidation Testing 6. 20. 6. System Testing 6. closing curtain 7. 20. Summary of the Project 7. 21. Future Work INTRODUCTION Introduction about the Project Nowadays technology has reached its highest level and is in the phase of developing more with the in the altogether innovations. Students Information System (SIS) is an important aspect of any educational institute. The information about the students overall performance is important as to generate students progress report.Still different colleges record students performance report on the paper. Although records can be recorded on the paper manually, but this process is time consuming activity. With the advancement of technology, computerized techniques are more effectual and consume less time compared to paper work. Hence computerized techniques should be used in colleges to record and access students data which is more effective and efficient to use. The Student Information System is aimed to computerize the record keeping system as to make the job easier for the college administrators. 1. 2 ObjectivesT he main objective of this project is to develop software that helps in easy access of the information about the student, their overall performance in one click. Our system is focused to make a nett based SIS which makes the work of measuring students performance easier and efficient. The main intention is to provide a system with suitable efficiency and accuracy while maintaining its main objective to access students performance report. * Ensures that end users have input the visualize process. * Accomplish project goals and objective within defined budget and time parameters. To implement a computer based program as to make the work effective and efficient. Scope of the Project As discussed preceding(prenominal) this project is based on developing software that is capable of finding students performance report. The system will be able to show students performance report. This system will help to reduce the effort to record the entire students performance data in files. This sys tem will save time and increase efficiency. This project is purely based on the research and along with the study and requirement of this project in academic field. 2. SYSTEM STUDY 2. 1 Existing SystemThe existing system of managing SIS in the college is based on the file recording system. The recording method of this system is totally based on file system and the data about the students are recorded in a file and to search the performance graphical record about a student the files are to be searched according to the students semester. 2. 2 Disadvantage The existing system is very time consuming and is not effective as it is based on the file recording system. To search one students report all the existing files are to be searched. fitting and updating process is hazard, which is time consuming and inefficient. . 3 Proposed System The system we are about to make is a web based system dealing with the Student Information System. Particularly it is based on the activities related to the recording and accessing the students performance report. The proposed system is a computerized system which will be much more effective than the filing system. 2. 4 vantage of the Proposed System As the system is a computerized system, it will reduce the effort to record the students progress report on the files. It will also save time in recording, managing and accessing the students data. 2. 5 Problem Definition and DescriptionIn any academic institute students information is an important aspect as it is related to the institute and the student canvass in it. The students information about their overall performance in their academic career is essential and it is to be recorded in a proper way, so that the necessary information can be access when required. Our system Student Information System (SIS) is focused make a computerized system that records the students performance information. The main intention is to provide a system with suitable efficiency and accuracy while recor ding, managing and accessing the recorded data along with appropriate speed. SYSTEM ANALYSIS 3. 1 Packages Selected The package used in the development of our system is Java acquit Bin. 3. 2 Resources Required 3. 2. 1 Hardware Requirement Hardware PC congenial with a Intel Pentium- III processor RAM 1-GB RAM Hard disk 20-GB 3. 2. 2 Software Requirement Operating System Windows 2000 Professional Software jdk 1. 7. 0_02, jre 7 drift End Java Back End MySQL 3. 3 Feasibility Study We made our estimation on whether the system is able to satisfy the users need using the software/hardware technologies being used in the developing the system.We made our study on the basis of cost effectiveness of the proposed system from the business point of view. Considering the time and cost the feasibility study were made and and detailed analysis was done. The study is based on the following * Whether the system contributed to the main objective of the project * Whether the system can be engineered using current technology and within budget and schedule constraints. 3. 3. 1 Operational feasibility We made our study on the basis of the operational factors of the system. Our system is feasible on the operational environment as well.The users who are going to operate on this system will able to understand the system and can use it easily by some training. 3. 3. 2 Technical feasibility The hardware and software used in this system are easily operable in the current technical environment so it is easy to use and feasible with our system. Due to technical feasibility further changes can be performed easily. 3. 3. 3 Economic Feasibility Our system is economically feasible as it is under our budgetary constraints. This system is cost effective because * The tools and technologies used for this system are free for non commercial use. This system provides quality of information and the ease of access to the information required. The system can prove effective and efficient and can est ablish itself as valuable assets for the one who implements it. 3. 4 Functional Requirement The system provides a web base where a grand number of pages are crawled for a particular domain and are stored. The statement of function that our system provides as the systems functional requirements are as follows * The administrator would be able to insert, delete, modify and update the records based on students the performance. The system would be able to display all the recorded performance information about the student. 3. 5 Non-Functional Requirements * Usability Our system will provide the web interface to the end users with the optimum user- friendship so that they can get given while operating the system. * Reliability The system developed will be able to meet the expectations of the user as well as, it would be reliable to matchup with the existing products * Performance Our system shall return the matched documents from its web base within considerable add of time. Security Our system provides a web interface, so in order to make the system secure, any user unavoidably to get authenticated. This would help the system be free from spamming and other kinds of attacks. 3. 6 Project scheduling Gantt Chart Days 1-5 days 6-10 days 11-15 days 16-20 days 21-25 days 26-30 days Activities Planning Feasibility study System analysis System image Coding Testing Implementation The in a higher place Gantt chart represents the activities conducted by our team members and the days required to complete all the activities. The activities performed were preparation which required five days, feasibility study which required ten days from day 6 to day 15, database design, and interface design required ten days from day 11 to day 20, coding would require ten days, testing would require five days from days and lastly implementation would also require five days from days.As this project is based on the design of the Student Information System, coding system testing and implementation was not conducted but duration was separated for these activities as well. 4. SYSTEM DESIGN 4. 1 System Design 4. 2 Design Description 4. 2. 1 Use Case The use case defines a goal oriented set of interaction between external actors and the system under consideration. Actors are parties outside the system that interact with the system. In SIS actors are the users. Use case diagram of Student Information System Insert records set off recordsUpdate records Search required record positioning records record Administrator User 4. 2. 2 Sequence diagram for Student Information System 2. Accept password 1. assent Password Display System Information System Login System 3. System entrance fee 4. Display Record 5. Display require information to the user User Fig Sequence Diagram for Student Information System 4. 2. 3 Architectural Process Diagram Fail Pass add Delete Edit Edit Delete Submit Exit Report deed Exit Operatio n Performance Info Student Info Student Informationon 4. 3 Entity Table Table name StudentAttributes Data type Length Constraints S_Id Integer 20 Primary Key S_name Varchar 20 - S_semester Integer 20 - S_phone Integer 20 - Table name Result Attributes Data type Length Constraints S_name Varchar 20 - S_marks Integer 20 - Table name Login Attributes Data type Length Constraints Username Varchar 20 - Password Varchar 20 - Time Varchar 20 - Table name Administrator Attributes Data type Length Constraints Admin_Id Integer 20 Primary name Admin_name Varchar 20 - 4. 4 Entity DiagramStudent S_name S_Id S_phone S_semester Fig 4. 3. 1. Entity diagram for student Result S_name Marks Fig 4. 3. 2. Entity diagram for result Username Password Time Login Fig 4. 3. 3. Entity diagram for login Admin_Id Admin_name Admin Fig 4. 3. 4. Entity diagram for Admin 4. 4. 1 ER-Diagram of Student Information System Login Admin Student Result Attend Performs Records Performs 4. 5 Context Diagram Update info Mar ks Student details Administrator Student information system Student Id Semester result Student Login details 5. interrogation 5. 1 TestingOur system has been tested throughout the design of the system. As testing is important part of the system development process, we have tested the system throughout the design phase rather than testing the system after the complete development. The following tests are to be done during the system development 5. 1. 1. Unit Testing We will have to test each and every small units of our system. The source code of our system would be divided into modules, which in turn would be divided into small parts called units having their specialized behavior.From the unit testing we will come to know if the combination of the units leads to the fulfillment of the software requirements or not. 5. 1. 2. Integration Testing In this testing we will combine the modules and test it as a group. Modules would be typically code modules, individual applications, client innkeeper application in the network, etc. Integration testing follows unit testing and precedes system testing. 5. 1. 3. System testing As there are the possibilities of different unexpected errors to pass by after integration so the system testing would be done.The system would be tested to check whether it met its requirements and ensure the know and predictable results. System testing would be based on the process description, accentuate pre-driven process links and integration points. 6. shutting 6. 1 Summary of the Project Managing students performance information is a very important activity of any educational institute. This project is aimed to develop a computerized Student Information System that helps to make recording and accessing the information easy and effective. ulterior numbers of lectures were reviewed before starting the project.Then further steps were taken such as system study, systems feasibility and many others considerations. Though the system ineluct ably some improvements and future enhancement is also a challenging task, the overall resultant role of the project is expected in its design considerations. Enormous knowledge has been gained throughout the project. The importances of background research, system study, requirement analysis different methodologies were learnt. Also implementing techniques, testing have been exercised. thereof we hope our system provides appropriate nformation to the users according to the chosen service and would help to reduce unnecessary time managing the repots on the paper. 6. 2 Future Work Our Student Information System has many aspects that can be upgraded with future works. There are different future possibilities that the system can enhance its features in terms of the technology and design. In order to make even more effective and efficient use of the system the user interface can be developed in a more interactive way and technological changes can be made. As per the time, knowledge and unavoidableness the system scan be made better in future.