Home > Computer science essays > Process to handle student loans in an accurate and convenient way

Essay: Process to handle student loans in an accurate and convenient way

Essay details and download:

  • Subject area(s): Computer science essays
  • Reading time: 8 minutes
  • Price: Free download
  • Published: 28 August 2019*
  • Last Modified: 23 July 2024
  • File format: Text
  • Words: 2,279 (approx)
  • Number of pages: 10 (approx)

Text preview of this essay:

This page of the essay has 2,279 words.

Chapter 1
Introduction
This project is a very efficient process to handle student loans in a very accurate and convenient way. It provides a very reliable and convenient form for every loan and EMI related transaction and their related details. It also generates a very customer friendly and understandable form for their transaction information as the receive form after a transaction.
1.1 Preamble
Education Loan project is very helpful for the deserving student for studying their higher education In India ,Education loan would be giving to student who obtained admission to carrier oriented course.
1.2 Motivation
The online Education loan website is also very useful because the students who are pursing the higher education. Our intention is to provide the education loan for the deserving student for studying their higher education In India, our education loan website aim to be the important tool that will enable them to reach their goals in life.
1.3 Goal and Objectives of the Project Report
• To develop general purpose tool to maintain loan details to view and apply via online.
• This project intends to introduce more user friendliness in the various activities such as applying the loan and searching loan status .
• Accepting student details and accepting or rejecting the form..
• Authentication of administrative users is done using proper student name and password. So that other user cannot retrieve administrative data.
1.4 Problem Statement
• In an existing System, all process are Handled manually. The admin should refer all the records kept for years ago to simply know the details. This is time consuming.
• This process is very difficult when the number of users increases. There are many limitations for the existing systems. In manual Placement system all the work is done by human intervention due to which there are maximum chances of errors.
• Lists are produced for each guide and tourist had to regularly travel in to review the tour details.
• The files were not stored in hierarchical format. Hence searching was big problem.
1.5 Scope of the Dissertation Report
As the growing demands and heterogeneity of applications are continuously challenging the architectural aspects of the Internet, it becomes necessary to devise an architecture which is flexible in terms of any modification or update of applications or protocols.
• No data duplication
• No Paper Work Required
• Time Efficient
• Cost Efficient
• Automatic data validation
• User friendly environment
• Data security and reliability
• Fast data insertion & retrieval
• Easy performance check
• Format report generation
1.6 Outline of Dissertation Report
The Project Report is contain with six chapters in total and it is organized as follows:
Chapter – 1: Introduction:
Explicates motivation of the research work, the scope of the study, goal & objectives of the Project Report and also tried to present a brief overview of Project Report including from where to start reading? In addition to different textual formats used for expressing the author’s feelings.
Chapter – 2: Literature Survey:
Determine the relevant background information such as the Internet design goals & principles, initiative towards the OSI reference model, architectural principles, a critical review of Internet dealing with its limitations and issues, future research approaches, and finally the need of net- work architecture.
Chapter-3: Requirement Analysis:
The main goal of the requirements phase is to produce the software requirements specification(SRS), which accurately captures the client’s requirement and forms the basis of the software development and validation. The main basic activity in the requirements phase is requirement analysis.
Chapter -4: System Design:
Deciding which module are needed for the system, the specification of these module should be interconnected is called “SYSTEM DESIGN”. System design is also called Top Level design. The design of a system is a plan for solution for the system here we consider a system to be set of components with clearly defined behavior that interact with each in a fixed manner to produce some behavior.
Chapter-5: Implementation:
Implementation forms an important phase in the system development life cycle. It is a stage of the project work that transforms the design into a work module.
Chapter-6: Testing:
Testing can be stated as the process of validating and verifying that a software program/application is behaving just as expected during the designing phase. Track the errors to understand their causes and any patterns that may exist.
Chapter 2
Literature Survey
Literature survey is a text of a scholarly paper, which includes the current knowledge including substantive findings, as well as theoretical and methodological contributions to a particular topic.
Literature survey use secondary sources and do not report new or original experimental work.
Visited websites
• www.gimt-guwahati.ac.in
• www.ksrce.ac.in
• www.fresherworld.com
• www.btechguru.com
These are the educational service company with the core objective of serving students in higher educational institutions by providing affordable, high quality knowledge based services to catalyze effective and efficient learning.
Advantages of those sites
• Used languages and platforms
• Techniques used for user interactions
• Provided information
Disadvantages of visited sites
• Lengthy Modules
• User accessibility
• User security
Chapter 3
Hardware and software Requirements
3.1 Requirement Analysis
Software Requirement Specification is a technical specification of requirements for the software products. SRS represents an overview of products, features and summarizes the processing environment for development operation and maintenance of the product.
Software Requirement Specification completely describes what the proposed software is supposed to do, without explaining what it actually does. It contains all the basic requirements that are needed for the development of the software.
The main purpose for preparing this document is to give a general insight into the analysis and requirements of the existing system or situation and for determining the operating characteristics of the system. An SRS provides a reference for validation of the final product. The Online Tours and Travels website is useful for the customers who like to book the Ticket online without going to booking office and dealing face to face. It provides the facility to the customers or the users to have complete information about the Tours and Travels at one place.
3.1.1 Software Requirement Specification
• Windows 7 Ultimate, Windows 8
• Browser like Google Chrome, Microsoft Internet Explorer 4.0 or later.
• Visual Studio 2010 or later
• .Net as front end.
• SQL Server 2005 and above
3.1.2 Hardware Requirement Specification
• 256 MB of RAM or more.
• 2GB of hard disk space.
• VGA or higher monitor resolution.
• Mouse or other pointing devices.
• Network interface card or Modem.
• LAN Network.
• Processor Intel core i3 and above.
• Communication Devices wifi
Chapter 4
System Design Architecture
Deciding which module are needed for the system, the specification of these module should be interconnected is called “SYSTEM DESIGN”. System design is also called Top Level design. The design of a system is a plan for solution for the system here we consider a system to be set of components with clearly defined behavior that interact with each in a fixed manner to produce some behavior.
4.1 E-R Diagram
An ER model is an abstract way to describe a database. Describing a database usually starts with a relational database, which stores data in tables. Diagrams created to design these entities and relationships are called entity–relationship diagrams or ER diagrams. E-R diagram depicts the various relationships among entities, considering each object as entity. Peter Chen developed ERDs in 1976.
4.2.1 Entity-Relationship Diagram Notation:
Entity: An entity is an object or concept about which you want to store information.
Weak Entity: A weak entity is an entity that must defined by a foreign key relationship with another entity as it cannot be uniquely identified by its own attributes alone.
Key attribute: A key attribute is the unique, distinguishing characteristic of the entity. For example, an employee’s social security number might be the employee’s key attribute.
Figure 4.1: E-R Diagram
4.2 Data Flow Diagram
A data flow diagram (DFD) is a graphical representation of the “flow” of data through an information system, modelling its process aspects. Often they are a preliminary step used to create an overview of the system which can later be elaborated. DFDs can also be used for the visualization of data processing (structured design).
A DFD shows what kinds of information will be input to and output from the system, where the data will come from and go to, and where the data will be stored. It does not show information about the timing of processes, or information about whether processes will operate in sequence or in parallel.
4.2.1 Description of the Documents
The notations used in the diagram are:
Process:
A process transforms incoming data flow into outgoing data flow.
Data Store:
Data stores are repositories of data in the system. They are sometimes
also referred to as files.
External Entity:
External entities are objects outside the system, with which the system
Communicates. External entities are sources and destinations of the
system’s inputs and outputs.
Dataflow:
Dataflow are pipelines through which packets of information flow. Label
the arrows with the name of the data that moves through it .
Level 0:
Fig 4.2: DFD Level 0
Level 1:
Fig 4.3: DFD Level 1
Level 2 User:
Fig 4.4: DFD Level to User
Level 2 Admin:
Fig 4.5: Level 2 DFD of Admin
4.3 Class Diagram
Fig 4.6: Class Diagram
4.4 Sequence Diagram
Fig 4.7: Sequence Diagram
4.5 UseCase Diagram
Fig4.8: Use Case for Admin
Fig4.9: Use Case for User
Chapter 5
Implementation
5.1 Home Page
5.2 Emi calculator:
5.3 Application Page:
5.4 Course details form:
5.5 Admin form:
Applicat Search form:
Chapter 6
Testing
Software testing is the process of executing a program or system with the intent of finding errors. Software testing is any activity aimed at evaluating an attribute or capability of a program or system and determining that it meets its required results. Although crucial to software quality and widely deployed by programmers and testers, software testing is still an art, due to limited understanding of the principles of software. Testing is more than just debugging. The purpose of testing can be quality assurance, verification and validation or reliability estimation. Testing can be used as a generic metric as well. Correctness testing and reliability testing are two major areas of testing.
6.1 Testing approach
Testing is the penultimate step of software development. While testing is done, errors are noted and correction is made. Both hardware and software securities are made to run the developed system successfully.
System testing is aimed at ensuring the system works accurately before the live operation commences. Testing is vital to the system. System testing makes a logical assumption that if all parts of the system are correct, the goal will be successfully achieved. A series of testing are performed for the proposed system before the system is ready for user acceptance testing.
Normally, testing of any large systems will be in two parts: The functional verification and validation against the indicated requirements. Testing activity is involved right from the beginning of the project.
Characteristics of a Good test:
• Tests are likely to catch bugs
• No redundancy
• Not too simple or too complex
6.2 System Testing
When a system is developed, it is hoped that it performs properly. The main purpose of testing and information system is to find the errors and correct them.
The main objectives of system testing are:
• To ensure during operation the system will perform as per specification.
• To make sure that the system meets user’s requirements during operation.
• To verify that the controls incorporated in the system function as intended.
• To see that when correct inputs are fed to the system the outputs are correct.
• To make sure that during operation incorrect input and output will be deleted.
System testing is the process of checking if the developed system is working according to the original objectives and requirements.
6.3 Types of testing
Clearly, the success of testing is revealing errors in programs depend critically on the test cases. The two basic approaches are:
• Black box or Functional testing
• White box or Structural testing
6.3.1 Black box or Functional testing
A software testing technique whereby the internal workings of the item being tested are not known by the tester. The tester does not ever examine the programming code and does not need any further knowledge of the program other than its specifications.
6.3.2 White box or Structural testing
White box testing includes analyzing data flow, control flow, information flow, coding practices and exception and error handling within the system to test the intended and unintended software behavior.
6.4 Test Cases
6.4.1 Admin Page:
Table6.1: Change Password Test case
6.4.2 Login:
Conclusion :
The software for Education Loan management System is now designed and it is ready to apply the loan for student through online and maintaining the same. The system is user friendly and can be operated by any user with minimal amount of training.
Using the proposed system:
• Efficiency is improved
• Storage and maintenance of database is easy
• Paper work is reduced.
Future Enhancement :
• New modules can be added without affecting the existing model
• The existing modules can be reused in future projects
• Can be upgraded to include all the tourist places in entire Mangalore and also in India
• Can be moved our vision through National Level
• This Project can be extended with regional language support.
• New modules can be easily added as it requires only an addition of a new package on button click.
• In the short time of period we are going to provide our dear user online AIR TICKETS & RAILWAY TICKETS.
• They can book every kind of ticket on online. They can know all the fares and time table and schedule.
• We are going to arrange the INTERNATIONAL TOURS in the very short time of period and that work is under progress.
Bibliography:
[1] McGraw Bart De Smet: C# 4.0 Unleashed, Pearson Education- SAMS Series
[2] Hebert Shildt: Programming in C# 4.0, Tata Hill
[3]An Integrated Approach to Software Engineering by PankajJalote.
[4] http://www.functionx.com/sqlserver
[5] www.stackoverflow.com
[6] http://www.w3c.com
[7] www.gimt-guwahati.ac.in
[8] www.ksrce.ac.in
[9] www.fresherworld.com
[10] www.btechguru.com
[11] www.w3schools.com
[12] www.tutorialspoint.com

About this essay:

If you use part of this page in your own work, you need to provide a citation, as follows:

Essay Sauce, Process to handle student loans in an accurate and convenient way. Available from:<https://www.essaysauce.com/computer-science-essays/process-to-handle-student-loans-in-an-accurate-and-convenient-way/> [Accessed 19-01-25].

These Computer science essays have been submitted to us by students in order to help you with your studies.

* This essay may have been previously published on EssaySauce.com and/or Essay.uk.com at an earlier date than indicated.