Download School Account Management System: A Case Study in Information Management and more Thesis Software Engineering in PDF only on Docsity!
SCHOOL ACCOUNT MANAGEMENT SYSTEM
FOR EKTA BOARDING HIGH SCHOOL
BY
Sharad Shrestha
Exam roll no. :7758/
Nepal Commerce Campus
A Software Engineering Project Report Submitted To
Faculty of Management, Tribhuwan University
in partial fulfillment of the requirements for the degree of
Bachelor of Information Management
Mibhawan,Kathmandu
10 September 2019
i
AKNOWLEDGEMENT
I am very grateful with the Department of IT, NCC, for providing us with the opportunity
to expand our knowledge in the form of this project. This document is about the project.
“School Account Management System” written for the Software Engineering Project of
the Nepal Commerce Campus, Minbhawan, Baneshwor, Kathmandu. I am extremely
grateful to our teachers, who has supported and guided us to improve our ideas for the
project in possible way.
I would like to take this opportunity to thank our subject teacher Ms. Manoj Giri for his
valuable guidance and encouragement throughout the project. I would also like to thank
various person helping to complete this project in direct or indirect way.
Finally, I would also like to express our gratitude to our friend’s circle for providing us
valuable suggestions and ideas for the project and encouraging us to do better.
ii
LIST OF FIGURES
- CHAPTER 1................................................................................................................................... ABBRIVIATIONS............................................................................................................................v
- INTRODUCTION...........................................................................................................................
- CHAPTER 2...................................................................................................................................
- TASK AND ACTIVITY PERFORMED................................................................................................
- Chapter 3...................................................................................................................................
- Discussion and Conclusion........................................................................................................
- REFERENCES..............................................................................................................................
- CHAPTER 1............................................................................................................................................... ABBRIVIATIONS........................................................................................................................................v
- INTRODUCTION.......................................................................................................................................
- 1.1 Background Study........................................................................................................................
- 1.2 Problem Statement......................................................................................................................
- 1.3 Objectives of Study......................................................................................................................
- 1.4 Methodology...............................................................................................................................
- 1.4.1 Project of framework...............................................................................................
- 1.4.2 Data and Information..............................................................................................
- 1.4.3 Data collection method...........................................................................................
- CHAPTER 2...............................................................................................................................................
- TASK AND ACTIVITY PERFORMED............................................................................................................
- 2.1 Requirement Specification...........................................................................................................
- 2.1.1 Functional Requirement..........................................................................................
- 2.1.2 Non Functional Requirement..................................................................................
- 2.2 Feasibility Study...........................................................................................................................
- 2.3 System Design..............................................................................................................................
- 2.4 System Development.................................................................................................................
- 2.4.1 Module Description...............................................................................................
- 2.5 Testing of Developed system.....................................................................................................
- Chapter 3...............................................................................................................................................
- Discussion and Conclusion.....................................................................................................................
- 3.1 Discussion..................................................................................................................................
- 3.2 Conclusion.................................................................................................................................
- REFERENCES..........................................................................................................................................
ABBRIVIATIONS
SAMS = School Account Management System
GUI = Graphical User Interface
TU = Tribhuvan University
BIM = Bachelor of Information Management
v
1.2 Problem Statement......................................................................................................................
A school is totally dependent on manual work for storing details of faculty, students etc. This brings lots of problems while managing the data and information related with campus staffs, student’s private information. This not only brings hindrance in managing data, but also when anyone need to search the information about school’s particular notices and faculties information related with hiring new staff and admission for new students, trouble in finding particular faculty members and student’s information when needed.
1.3 Objectives of Study......................................................................................................................
To manage the details of students, teaching and non-teaching staffs. To reduce the time consumption for data management. To ensure the data integrity and authorized access. To maintain data security.
1.4 Methodology...............................................................................................................................
1.4.1 Project of framework...............................................................................................
Project was developed using incremental development model. Incremental Development model is used widely for e-commerce approach, personal and business based application which provides users to give their suggestions, reviews and comments while building any software or system in order to create a stable and updated version of software/system according to environment need.
1.4.2 Data and Information..............................................................................................
Primary data
Primary data is a data which is collected in a first time, whether sample surveys or census surveys, then we can obtain primary data either through observation or through direct communication with respondents in one
form or another through personal interviews. This in other words, means that there are several method of collecting primary data, particularly in surveys and descriptive researches.
Secondary data
Secondary data means data that are already available i.e., they refer the data which have already been collected and analyzed by someone else. Secondary data may either be published data or unpublished data .Usually published data are available in:-(a)various publication of central, state and local government; (b)books, magazines and newspapers; etc.. The sources of unpublished data are many; they may be found in diaries, letters, unpublished biographic etc.
1.4.3 Data collection method...........................................................................................
Questionnaire
Questionnaire is used as a method of data collection. This method of data collection is quite popular, particularly in case of big enquiries. A questionnaire is a research instrument consisting of a series of questions and other prompts for the purpose of gathering information from respondents. A questionnaire consists of numbers of question typed in a definite order on a form or set of forms. It is the most convenient way of collecting the information in a short span of time.
Working environment observation
Observation of school daily activities played vital role for finding out what school exactly needed. This helps in determining the requirements to make the system more accurate based on school current problems in working environment.
Organizational Website
For getting proper information of the schools, many school’s authenticated website was searched. From which all the historic events about the organization’s past, present and what organization was planning to do in future
for providing better educational services to new comers and its students was known.
Contents available in internet
Different websites were preferred for getting the proper information, ideas, thoughts, etc. related with the system that were being used by different other schools. YouTube was preferred to see what others system developer had done while they were developing School Account Management System for many educational institutes too. This had helped a lot while developing System for Nepal Commerce Campus.
2.1.2 Non Functional Requirement..................................................................................
While developing any system non-functional requirements should be handled carefully. Non-functional requirement is the requirements that are not directly concerned with specific function delivered by the system to its user but they concern with emergence system properties such as reliability, availability, response time, security, safety etc. Non functional requirement place or put constraints on how the system will do to achieve the functional requirement and elaborates a performance characteristic of the system. Only authorized users can access the system with the username and password. Availability when needed Better component design to get better performance and easy access at peak time Flexible service based architecture will be highly desirable for future extension Easy to maintain the system in future Security availability for the student, teaching and non-teaching staff details.
2.2 Feasibility Study...........................................................................................................................
The analysis of feasibility concluded that the project is feasible with respect to time and cost. The technology used to develop SAMS are:
Economic Feasibility
This system will help the organization to reduce the cost of book keeping related with fee, salary and information of students and staffs. The economic feasibility assessment is to determine the positive economic benefits to the organization that the proposed system will provide.
Technical Feasibility
Technical analysis is a tool to evaluate securities and attempts to forecast the future movement.
Operational Feasibility
The system “SAMS” can be operated by the person who have basic and general knowledge about the computing. This system is operationally feasible since it has simple GUI and easy system interaction, which will, solves the problem, and takes Advantages of the opportunities identified during scope definition and it satisfies the requirements analysis phase of the system development.
2.3 System Design..............................................................................................................................
The various design techniques of the proposed School Account Management System has been represented through the help of diagrams. With the help these diagrams the system for a school had
been developed. Some of the diagrams are given below: Use case diagram Sequence diagram Class diagram Activity diagram
Figure 2. 2 Sequence diagram
Figure 2.4 Activity diagram
Activity diagram show the sequence of actions involved in processing input data and generating an associated output. It shows the entire sequence of actions that takes place from an initial input being processed to the corresponding output which is the system’s response. Admin
Accountant
2.4 System Development.................................................................................................................
System development consists of various development tools, testing tools and some other system
development life cycle processes. Different feasibility studies have been done such as technical
feasibility, time feasibility, and behavioral feasibility. In this stage an executable software i.e.
desktop application using different development tools. The different tools used are listed below:
2.4.1 Module Description...............................................................................................
This system is developed by integrating different modules such as login module for authentication, product module to manage the products, supplier module to manage the status of supplier and the employee module to manage the employees. Table Modules Module Functionality Login module Login module is concerned with the non-functional requirement in which admin, system users such as school workers and verified users can authenticated through username and password. View Module View module provides the view of different data related with fee, salary and personal information related with specific student, staffs and both respectively. Student Module Student module carries all the information about the students of different semester Teaching staff module Teaching staff module contains information related with all the teaching faculty Non-teaching staff module Non-teaching staff module contains details about non- teaching member of campus
2.5 Testing of Developed system.....................................................................................................
The purpose of testing is to discover errors. Testing is the process of discovering every
conceivable fault or weakness in a work product. Software testing is a process of
executing a program or application with the intent of finding the software bugs. The
purpose of testing is to show that a program performs its intended functions correctly.
This is the final stage where the actual system is tested for verification and validation.
The testing of the system is to establish confidence that the system is ‘fit for purpose’.
During testing phase different errors can be identified that were not identified before.
Unit Testing
Unit testing is the process of taking module and running it in isolation from the rest of the software product by using prepared test cases and comparing actual results with the result predicted by the specifications and design of the module. The following general test cases that have being conducted in the system are:
- Ensuring that admin is able to login.
- Ensuring other verified system users is able to login too.
- Ensuring that admin and system users are able to add students, staffs and accounting details.
- Ensuring that admin and other system users are able to delete students, staffs and their accounting details.
- Ensuring that admin and other system users are able to update students, staffs and their accounting such as fee and salary details.
- Ensuring that admin is able to change login detail.
System Testing
The system testing is testing process conducted over the entire system that has been developed. The system is collection of different types of components with various different functionalities. The completely integrated system has been tested and it meets the requirements. The overall module of system i.e. login module, view module, student module, salary module, fee module and staff module are integrated and tested. like for salary module if salary is paid to staff than their salary will deducted from their account.
