This document outlines a proposed student management system. It describes the existing manual system and its drawbacks. The proposed system would allow teachers to easily add, search for, and sort student details electronically. It covers system analysis, feasibility study, input/output design, testing procedures, future enhancements, and software and hardware requirements for the new computerized student management system.

2. INDEX
 INTRODUCTION
 EXISTINGSYSTEM.
 DRAWBAC KS OF EXISTING SYSTEM.
 PROPOSED SYSTEM .
 SYSTEM ANAL
YSIS
 INTRODUCTION TO SYSTEM ANAL
YSIS.
 FEASIBLITY STUDY .
 INPUT& OUTPUT DESIGN.

3.  SYSTEMTESTING’s.
 FORM DESIGN & REPORTS.
 DATADICTIONARY.
 FUTURE ENHANC EMENTS.
 SOFTWERE REQUIRMENTS.
 HARDWERE REQUIRMENTS.

4.  Student Management System is used to
manage all the activities related to a
student. In college/school there are
many students, and keeping their
records in a file and making changes to
these records become very tedious for
the organization. It is also important for
the organizers to keep updated and
correct data of the students. Looking at
these issues we have created this
software application. In this application
a teacher can easily manipulate the
details of the students. With the
automation, organizations just have to
do some clicks to want the desired
results. We have kept in mind, the ease
and user friendliness of this application,
even someone with low technical skills
can easily operate this application. This
system will help the organizations to be
robust for handling student data.
Intoduction
Student Management System

5. Themodules involvedin this
projectare:-
 Maintenance of Student Details.
 Student details adding.
 Search Function for teachers. Tables
the data of students by Id, Name,
Address, Class and Mobile No.
 ItAlso sorts the details of the students.

6. 1.1EXISTING SYSTEM
 The existing system around many colleges or schools which deals with the
recording of the students.
 The data of every student who study in the college or school is written -
 in the register. It is the traditional method.
 If any kind of record is missing then there will problem during the
assessment of a student.
 If any professor or teacher mistakenly put incorrect information of a student,
then it is very tedious to change and make it right.
 If register lost anywhere then the all information about the student can
be lost.

7. 1.2DRAWBACKSOFEXISTING
SYSTEM
 The present system requires of lot of manpower
and there may delay for some work in case of
absence of student.
 Large numbers of student details to be maintained.
 It is very time consuming & tedious work, since all
calculations are to be done manually for every student.
 Lack of Manpower.
 Automatic updating of information is not possible.
 Inconvenience in maintaining of records in cupboards.
 Colleges may find problem in case leaving of some
student.
 It is very hectic and lengthy job to find particular
record as the registers containing that particular
record may be full of thousands of records.

8. 1.3 PROPOSED SYSTEM
 Due to computerization this home services
will enjoy following.This Student
Management System 1.0 is fully integrated system
which has interaction with databasesfor storing
the differenttypesof data. It has separate
partition of Students and their details which
are integrated in one system. It is easy to user to
do the entire task on one system. Hence the
speed of work will improve .

9.  Advantages of this system are as follow :
 Data Entry.
 PaperlessWork.
 Ultra-ModernTechnical Environment.
 Standard OfWorkWill Improve.
 Attractive Representation.
 Helpful In Future Plans.
 Increased Speed OfWork.
 Reduction Of Manpower.
 Easy to Share Data.

10. 2SYSTEMANALISYS
 Requirements are nothing but the ideas in the
mind of the Donors and the Recipients.
 Requirement can also be defined as a condition
of capability needed by the user to solve the
problems or to achieve the objective.
 The requirement phase translates the ideas in the
mind of the client (input) into the document called
"Software Requirement Specifications" (SRS)
output.
 The basic goal of requirement phase is to
produce SRS, which explains the complete
external behavior of the proposed software.
 The process of the software analysis & specification
gives additional ideas to the client about what is
needed from the system.

11.  Need of Software requirement &
specification :
 Any software system starts with the needs of client
afterword's these needs are converted into the
system that used by the end users. There are three
main parties who are interested in the new system
they are as- C lient, Developer, and End- user.
 SRS establishes the base for the
agreement between client & company.
 SRS provides a reference for the validation
of final product. Without proper SRS there is
no way to determine the actual order &
to convince the client that all requirements
have been fulfilled.
 SRS states the goals & objectives of software.

12.  Componentsof SRS
SRS is the primary documentwhichis generated
after customer communication in order to be
complete any SRS should have following
 Components
 Functionality requirements
 Reference requirements
 Design constraints
 External interface

13. 2.1 FEASIBLITY STUDY
The feasibility study is made to see if the project on
completion will serve the purpose of the organization for
the amount of work, effort, and time that spend on it. A
feasibility study lets the developer to see the future of the
project and the usefulness. A feasibility study of a system
proposal is according to its work ability, which is the
impact on the organization, ability to meet their user, and
effective use of resources.Thus when a new application is
proposed it normally goes through a feasibility study
before it is approved for development.
The document provides the feasibility of the project that
is being designed and lists various areas that were
considered very carefully during the feasibility study of
this project such as Technical, Economic, and Operational
feasibilities.

14.  Features are as follows :-
 TechnicalFeasibility.
 Economic Feasibility.
 BehavioralFeasibility.

15. Technical Feasibility
 The system must be evaluated from the technical
point of view first.Theassessment of this
feasibility mustbe based on an outline design of
the system requirementin the terms of input,
output, programs, and procedures.Having an
identified outline system, the investigation must
go on to suggestthe type of equipment, required
method developing the system, of running the
system once ithas been designed.
 Technical issues raised during the investigation
are:
 Does this technology sufficient for the
suggested one?
 C an the system expand in future use?

16.  The project should be developed such that the necessary
functions and performance are achieved within the
constraints.
 The project is developed with the latest technology. Through
the technology may become out of date after some period of
time, due to the fact thatnewer versionof same software
supports olderversions, the system may still be used.
 So there are minimal constraints involved with this project.
The system has been developed using AngularJStheproject is
technically feasible for development.

17. Economic Feasibility
 The developing system must be justifiedthe
cost. C riteria to ensure that effortis
concentrated on the project, whichwill givethe
best, return at the earliest. One of the factors,
which affectthe developmentof a new system,
is the costit would require.
 Some of the important financial questions asked
during the preliminaryinvestigation:
 The costs conducta full system investigation.
 The cost of the hardware and software.
 The benefits in the form of reduced costs
or fewer costlyerrors.

18. Behavioral Feasibility
 Is there sufficientsupportfor the users?
 Will the proposed system cause any harm?
The projectwould be beneficial because it satisfies
the objectives when developed and
installed.Allbehavioral aspects are considered
carefully and conclude that the projectis behaviorally
feasible.

19. 3.4Input &Output Design
Design is the first step into the development phase for any
engineered product or system. It is a creative process. A good
design is a key to an effective system. The term “design” is defined
as “the process of applying various techniquesand principles for
the purpose of defining a process or a system in sufficient detail to
permit its physical realization”. It may be defined as a process of
applying various techniques and principles for the purpose of
defining a device, a process, or a system in sufficient detail to
permit its physical realization. Software design sits at the technical
kernel of the software engineering process and is applied
regardless of the development paradigm that is used. The system
design develops the architectural detail required to build a system
or product. As in the case of any systematic approach, thissoftware
has undergone the best possible design phase fine-tuning all
efficiency, performance, and accuracy levels. The design phase is a
transition from a user- oriented document to a document to the
programmers or database personnel. System design goes through
two phases of development: Logical and Physical Design.

20.  InputDesign
The design of inputfocuses on controlling the
amountof inputrequired, controlling the errors,
avoiding delay,avoiding extra stepsand keeping the
process simple. The inputis designed in such a way
so that it provides securityand ease of use with
retainingthe privacy.Input Designconsidered the
following things:
 Whatdata should be given as input?
 How the data should be arranged or coded?
 Methodsfor preparing input validations
and steps to follow when errors occur
.

21.  OutputDesign
Quality outputis one, which meets the requirements
of the end-user and presents the
information clearly. In outputdesign, itis determined
how the information is to be displaced for
immediate need and also the hard copy output.It is
the most important and direct source of information
to the user. Efficient and intelligent output design
improves the system’s relationship to help user
decision-making.

22. Designing computer outputshould proceed in an
organized,well-thought-out manner;the right output
must be developedwhile ensuringthat each output
element is designed so thatpeople will find the
system can use easily and effectively
.When analysis
design computer output,they should have the
following process :
 Identify the specific outputthatis
needed to meetthe requirements.
 Select methods for presentingthe information.
 C reate document, report, or other formats that
contain information produced by the system.

23. 4System Testing
Testing is the process of executing a program with
the interestof finding an error. A good testis one that
has a high probabilityof finding the yet undiscovered
error. Testing should systematically uncover different
classesof errors in a minimum amount of time with a
minimum amountof effort.
Twoclassesof inputs are provided to test
the process :
 A software configuration thatincludes a
software requirement specification,a
design specification, and source code.
 A software configurationthatincludesa test
plan and procedure, any testing tooland test
cases,and their expected results.

24.  Testing is divided into several distinctoperations :-
 UnitTesting.
 IntegrationTesting.
 ValidationTesting.
 RecoveryTesting.
 SecurityTesting.
 StressTesting.
 Black-BoxTesting.
 TestData Output.

25. 4.1Unit testing
 The unittestcomprisesof a settests performed
by an individual program to the
integrationof the unit into a large system. A
program unitis usually the smallestfree-
functioning part of the whole system. Module unit
testing should be as exhaustive as possible to
ensure that each representation handled by each
module has been tested. All the units that make
up the system must be tested independently to
ensure thatthey work as required.
 During unit testing, some errors were raised
and all of them were rectified and handled well.
The result was quitesatisfactory and it worked
well.

26. 4.2Integration testing
 Integration testing is a systematic technique for
constructing the program structure while at the same time
conducting tests to uncover errors associated with
interfacing.
 The objective is to take unit-tested modules and build a
program structure that has been dictated by design. Bottom-
up integration is the traditional strategy used to integrate the
components of a software system into a functioning whole.
 Bottom-up integration consists of unit tests followed by
 testing of the entire system. A sub-system consists of several
modules that communicated with other defined interfaces.
 The system was done with the integration testing. All the
modules were tested for their compatibility with other
modules. The test was almost successful. All the modules
coexisted very well, with almost no bugs. All the modules
were encapsulated very well so as to not hamper the
execution of other modules.

27. 4.3Validation testing
 After validation testing,the software is
completelyassembled as a package,interfacing
errors that have been uncoveredand corrected,
and the final series of software test.
 Steps taken during software design and testing
can greatly improve the probabilityof successful
integrationin the larger system.System testing is
actuallya series of different testswhose primary
purpose is to fully exercise the computer–based
system.

28. 4.4 Recovery testing
 It is a system thatforces the software to fail
in a variety of ways and verifies that the
recovery is properlyperformed.
5. Security testing
 It attempts to verify that protection mechanisms
built into a system willin fact protect it from
improper penetration.Thesystemssecurity must
of coursebe tested from vulnerability from frontal
attack.

29. 4.6Stress testing
 Stress tools are designed to confront programs
with abnormal situations.Stress testing executes
a system in a manner that demands resources in
abnormal quantityand volume.

30. 4.7Black-Box testing
 Black box testing is done to find outthe
following information as shown in below :-
 Incorrector missing functions.
 Interface errors.
 Errors or database access.
 Performance error.
 Terminationerror.
The mentioned testing is carried outsuccessfully
for this system according to the user’s requirement
specification.

31. 4.8Test data Output
 After preparing testdata, the system under study
is tested using the testdata.While testing the
system, errors are again uncovered and
corrected by using this testing and corrections
are also noted for future use.

32. SystemView

33. 7Future Enhancements
 We Can Update This System Into Fully
Functionally Online System AlsoWith The
Help Of Network Component’s.
 Here The Teachers Daily WorkWe Can Add In Future
 Updates.
 The Bugs And Some Logical Errors Will Solved
InThe Next Update.
 The Best Security AlsoWe Can Provide In Next Update

34. 8Software Requirements
 Operating System :
 Windows XP (Any Service Pack).
 Windows 7, 8, 8.1, 10 (32-Bit& 62-BitAny).
 Office :
 MicrosoftOffice 2007& above.
 Programming language: Angular JS
 C onnectionType :
 ADODC

35. 9Hardware Requirement
 Processor :
 Intel C ore – I3 or Above.
 RAM & ROM :
 Min. 500Mb for system.
 ROM More than 50G B more than 1G b free space
required.
 Screen Resolution :
 800 x 600, Min. 256C olor .
 For Installation :
 CD & USB