TABLEOFCONTENTS

SNO DESCRIPTION PAGENO

01 ACKNOWLEDGEMENT

02 INTRODUCTION

03 OBJECTIVES OF THE PROJECT

04 PROPOSED SYSTEM

05 SYSTEM DEVELOPMENT LIFE CYCLE(SDLC)

06 PHASES OF SYSTEM DEVELOPMEN TLIFE CYCLE

07 SOURCE CODE

08 OUTPUT

09 TESTING

10 HARDWARE AND SOFT WARE REQUIREMENTS

11 BIBLIOGRAPHY

1
 PROJECT ON STUDENT LOAN BANK MANAGEMENT SYSTEM

INTRODUCTION

This project is all about software for Employee management system.

It helps to have a full-fledged control over his/her employees. The project

is divided into 2 sections to make the programme easy to understand.

It receives user name and password to log in and register. It keeps

the record of user salary, his department of working, his performance in

the office. It adds a new employee, his salary, department, updates an

existing salary ,list of employee, age and his performance.

OBJECTIVESOFTHEPROJECT

The objective of this project is to let the students apply the programming

knowledge into a real world situation/problem and exposed the student

show programming skills helps in developing a good software.

1. Write programs utilizing modern software tools.

2. Apply object oriented programming principles effectively when

developing small to medium sized projects.

3. Write effective procedural code to solves mall to medium sized

problems.

4. Students will demonstrate a breadth of knowledge in computer

science, asexemplifiedinthe areasofsystems,theoryand

softwaredevelopment.

5. Students will demonstrate ability to conduct a research or applied

Computer Science project, requiring writing and presentation skills

which exemplify scholar lystylein computer science.

2
PROPOSEDSYSTEM

Today one cannot afford to rely on the fallible human beings of be

really wants to stand against today’s merciless competition where not to

wise saying “to err is human” no longer valid, it’s outdated to rationalize

your mistake. So, to keep pace with time, to bring about the best result

without malfunctioning and greaterefficiency so to replace the unending

heaps of flies with a much sophisticated hard disk of the computer.

One has to use the data management software. Software has been

an ascentin atomization various organizations. Many software products

working are now inmarkets, which have helped in making the

organizations work easier and efficiently. Data management initially had

to maintain a lot of ledgers and a lot of paper work has to be done but

now software product on this organization has made their work faster and

easier. Now only this software has to be loaded on the computer and

workcanbe done.

This prevents a lot of time and money. The work becomes fully

automated and any information regarding the organization can be

obtained by clicking the button. Moreover , now it’s an age of computers

of and auto mating such an organization gives the better look.

3
SYSTEMDEVELOPMENTLIFECYCLE(SDLC)

The systems development life cycle is a project management

technique that divides complex projects into smaller, more easily
managed segments or phases. Segmenting projects allows managers to
verify the successful completion of project phases before all resources to
subsequent phases .
Software development projects typically include initiation, planning,
design, development, testing, implementation, and maintenance phases.
However, the phases may be divided differently depending on the
organization involved .
For example, initial project activities might be designated as
request, requirements-definition, and planning phases, orianitiation,
concept-development, and planning phases. Enduser sof the system
under development should be involved in reviewing the output of each
phase to ensure the system is being built to deliver the needed
functionality.

4
PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

INITIATION PHASE

The Initiation Phase begins when a business sponsor identifies a need or

an opportunity.

The purpose of the Initiation Phase is to:

Identify and valid atean opportunity to improve business accomplish

ments of the organization or a deficiency related to a business need.
Identify significant assumptions and constraints on solutions to that
need. Recommend the exploration of alternative concepts and
methods to satisfy the need including questioning the need for
technology ,i.e., will a change in the business process offer a
solution?
Assure executive business and executive technical sponsorship. The
Sponsor designates a Project Manager and the business need is
documented in a Concept Proposal . The Concept Propose a includes
information about the business process and the relationship to the
Agency/Organization.
Infrastructure and the Strategic Plan. A successful Concept Propose
a results in a Project Management Charter which outlines the
authority of the projectmanager to begin
theproject.

Careful oversight is required to ensure projects support strategic

business objectives and resources are effectively implemented into an
organization's enterprise architecture. The initiation phase begins when an
opportunity to add, improve, or correct a system is identified and formally
requested through the presentation of a business case. The business case
should, at a minimum, describe a proposal’s purpose, identify expected
benefits, and explain how the proposedsystem supports one of the
organization’s business strategies. The business case should also identify
alternative solutions and detail as many informational, functional, and
5
network requirements as possible.

6
SYSTEMCONCEPTDEVELOPMENT PHASE

The System Concept Development Phase begins after a business need or

opportunity is validated by the Agency/Organization Program Leadership
and theAgency/OrganizationCIO.

The purpose of the System Concept Development Phase is to:

Determine the feasibility and appropriateness of the

alternatives.Identify systeminterfaces.
Identify basic functional and data requirements to satisfy the
business need. Establish system boundaries ; identify goals,
objectives, critical success factors, and performance measures.
Evaluate costs and benefits of alternative approaches to satisfy the basic
functional requirements
Assess project risks
Identify and initiate risk mitigation actions, and Develop high-level
technical architecture, process models, data models, and a concept
of operations. Thisphase explores potential technical solutions
within the context of the businessneed.
It may include several trade-off decisions such as the decision to
use COTS software products as opposed to developing custom
software or reusing software components, or the decision to use an
incremental delivery versus a complete, onetime deployment.
Construction of executable prototypes is encouraged to evaluate
technology to support the business process. The System Boundary
Document serves asa important reference document to support the
Information Technology Project Request (ITPR)process.
The ITPR must be approved by the State CIO before the project can
move forward.

7
PICTORIALREPRESENTATION OF SDLC:

PLANNING PHASE

The planning phase is the most critical step in completing

development, acquisition, and maintenance projects. Careful planning,
particularly in the early stages of a project, is necessary to coordinate
activities and manage project risks effectively. The depth and formality of
project plans should become mensurate with the characteristics and risks
of a given project. Project plans refine the information gathered during the
initiation phase by further identifying the specific activities and resources
required to complete a project.
A critical part of a project manager job is to coordinate discussions
between user, audit, security, design, development, and network
personnel to identify and document as many functional, security, and
network requirements as possible. During this phase, a plan is developed
that documents the approach to be used and includes a discussion of
methods, tools, tasks, resources, project schedules, anduser input.
Personnel assignments, costs, project schedule, and target dates are
established.
A Project Management Plan is created with components related to

8
acquisition planning, configuration management planning, quality
assurance planning, concept

9
Of operations, system security, verification and validation, and systems
engineering management planning.

REQUIREMENTS ANALYSIS PHASE

This phase formally defines the detailed functional user

requirements using high-level requirements identified in the Initiation,
System Concept, and Planning phases. It also delineates the requirements
in terms of data, system performance, security, and maintain ability
requirements for the system. The requirements are defined in this phase
to a level of detail sufficient for systems design to proceed. They need to
be measurable, testable, and relate to the business need or opportunity
identified in the Initiation Phase. The requirements that will be used to
determine acceptance of the system are captured in the Test and
Evaluation Master Plan.

The purposes of this phase are to:

Further define and refine the functional and data requirements and
document the min the Requirements Document,
Complete business process reengineering of the functions to be
supported(i.e., verify what information drives the business process,
what information is generated, who generates it, where does the
information go, and who process sit),
Develop detailed data and process models (system inputs, outputs, and
the process.
Develop the test and evaluation requirements that will be used to
determine acceptable system performance.

DESIGN PHASE

The design phase involves converting the informational, functional,

and network requirements identified during the initiation and planning
phases into unified design specifications that developers use to script
programs during the development phase. Program designs are
constructed in various ways. Using a top-down approach, designers first
10
identify and link major program components and interfaces, then expand
design layouts as they identify and link smaller subsystems and

11
connections. Using a bottom-up approach, designers first identify and link
minor program components and interfaces, then expand design layouts as
they identify and link larger systems and connections. Contemporary
design techniques often use prototyping tools that build mock-up designs
of items such as application screens, data base layouts, and system
architectures. Endusers, designers, developers, data base managers, and
network administrators should review and refine the prototyped designs in
an iterative process until they agree on an acceptable design. Audit,
security, and quality assurance personnel should be involved in the review
and approval process. During this phase, the system is designed to satisfy
the functional requirements identified in the previous phase. Since
problems in the design phase could be very expensive to solve in the later
stage of the softwaredevelopment, a variety of elements are considered in
the design to mitigate risk. These include:

Identifying potential risks and defining mitigating design

features. Performing a security risk assessment.
Developing a conversion plan to migrate current data to the new
system. Determining the operating environment.
Defining major subsystems and their inputs and
outputs. All processes to resources.
Preparing detailed logic specifications for each software module.
The result isa draft System Design Document which captures the
preliminary design for the system.
Everything requiring user input or approvalis documented and
reviewed by the user. Once these documents have been approved
by the Agency CIO and Business Sponsor, the final System Design
Document is created to serve as the Critical/Detailed Design for the
system.
This document receives a rigorous review by Agency technical and
functional representatives to ensure that it satisfies the business
requirements. Con current with the development of the system
design, the Agency Project Manager begins development of the
Implementation Plan, Operations and Maintenance Manual, and the
12
Training Plan.

13
DEVELOPMENT PHASE

The development phase involves converting design specifications

into executable programs. Effective development standards include
requirements that programmers and other project participants discuss
design specifications before programming begins. The procedures help
ensure programmers clearly understand program designs and
functional requirements. Programmers use various techniques to
develop computer programs. The large transaction oriented programs
associated with financial institutions have traditionally been developed
using procedural programming techniques. Procedural programming
involves theline-by-line scripting of logical instructions that are
combined to form a program. Effective completion of the previous
stages is a key factor in the success of the Development phase. The
Development phase consists of:

Translating the detailed requirements and design into system

components. Testing individual elements(units)for usability.
Preparing for integration and testing of the IT system.

INTEGRATION AND TEST PHASE

Subsystem integration, system, security, and user acceptance

testing is conducted during the integration and test phase. The user,
with those responsible for quality assurance, validates that the
functional requirements, as defined in the functional requirements
document, are satisfied by the developed or modified system. OIT
Security staff assess the system security and issue a security
certification and a credit a prior to installation/implementation.

Multiple levels of testing are performed, including:

Testing at the development facility by the contractor and possibly

supported by end users
14
 Testing as a deployed system with end users working together with
contract personnel

Operational testing by the end user alone performing all functions.

Requirements are traced throughout testing, a final Independent
Verification & Validation evaluation is performed and all
documentation is reviewed and accepted prior to acceptance of the
system.

IMPLEMENTATION PHASE

This phase is initiated after the system has been tested and
accepted by the user. In this phase, the system is installed to support the
intended business functions. System performance is compared to
performance objectives established during the planning phase.
Implementation includes user notification, user training, installation of
hardware, installation of software onto production computers, and
integration of the system into daily work processes. This phase continues
until the system is operating in production in accordance with the defined
user requirements.

OPERATIONS AND MAINTENANCE PHASE

The system operation is ongoing. The system is monitored for

continued performance in accordance with user requirements and needed
system modifications are incorporated. Operations continue as long as the
system can be effectively adapted to respond to the organization’s needs.
When modifications or changes are identified, the system may reenter the
planning phase.

The purpose of this phase is to:

Operate, maintain, and enhance the system.

Certify that the system can process sensitive information.
15
Conduct periodic assessments of the system to ensure the
functional requirements continue to be satisfied.
Determine when the system needs to be modernized, replaced, or
retired.

16
 SOURCE CODE

class StudentLoan:
def __init__(self, loan_amount, annual_interest_rate,
loan_term):
self.loan_amount = loan_amount
self.annual_interest_rate = annual_interest_rate
self.loan_term = loan_term

def calculate_monthly_payment(self):
rate = self.annual_interest_rate / 100 / 12
months = self.loan_term * 12
if rate == 0: # No interest loan
return self.loan_amount / months
payment = self.loan_amount * rate * (1 + rate) ** months /
((1 + rate) ** months - 1)
return payment

def total_payment(self):
return self.calculate_monthly_payment() * self.loan_term *
12

def main():
print("Welcome to the Student Loan Calculator!")
try:
loan_amount = float(input("Enter the loan amount ($): "))
annual_interest_rate = float(input("Enter the annual
interest rate (%): "))
loan_term = int(input("Enter the loan term (years): "))

loan = StudentLoan(loan_amount, annual_interest_rate,

loan_term)

monthly_payment = loan.calculate_monthly_payment()
total_payment = loan.total_payment()

print("\nLoan Summary:")
print(f"Loan Amount: ${loan_amount:,.2f}")
print(f"Annual Interest Rate: {annual_interest_rate}%")
print(f"Loan Term: {loan_term} years")
print(f"Monthly Payment: ${monthly_payment:,.2f}")
print(f"Total Payment: ${total_payment:,.2f}")
except ValueError:
print("Invalid input. Please enter numeric values.")

if __name__ == "__main__":
main()

17
OUTPUT

18
19
 TESTING

Software Testing is an empirical investigation conducted to provides

take holders with information about the quality of the productor service
undertest[1]
, with respect to the context in which it is intended to operate. Software
Testing also provides an objective, independent view of the software to
allow the business to appreciate and understand the risk sat
implementation of the software. Test techniques include, but are not
limited to, the process of executing a program or application with the
intent of finding software bugs.
It can also be stated as the process of validating and verifying that
a software program/application/product meets the business and technical
requirements that guided its design and development, so that it works as
expected and can be implemented with the same characteristics.
Software Testing, depending on the testing method employed, can be
implemented at any time in the development process, however the most
test effort is employed after the requirements have been defined and
coding process has been completed.

TESTING METHODS
Software testing methods are traditionally divided into black box
testing and white box testing. These two approaches are used to
describe the point of view that a test engineer takes when designing test
cases.

BLACKBOX TESTING
Black box testing treats the software as a "black box," without any
knowledge of internal implementation. Black box testing methods include:
equivalence partitioning, boundary value analysis, all-pairstesting, fuzz
testing, model-based testing, trace ability matrix, exploratory testing and
specification-based testing.

20
SPECIFICATION-BASED TESTING

Specification-based testing aims to test the functionality of software

according to the applicable requirements.[16] Thus, the tester inputs data
into, and only sees the output from, the test object. This level of testing
usually requires thorough test

21
 cases to be provided to the tester, who then can simply verify that for a
given input, the output value (or behaviour), either "is" or "is not" the
same as the expected value specified in the test case. Specification-based
testing is necessary, but it is in sufficient to guard against certain risks

ADVANTAGES AND DISADVANTAGES

The black box tester has no "bonds" with the code, and a tester's
perception is very simple: a code must have bugs. Using the principle,
"Ask and you shall receive," black box testers find bugs where
programmers don't. But, on the other hand, black box testing has been
said to be "like a walk in a dark labyrinth without a flashlight," because
the tester doesn't know how the software being tested was actually
constructed.
That's why there are situations when (1) a black box tester writes
many test cases to check something that can be tested by only one test
case, and/or (2) some parts of the back end are not tested at all.
Therefore, black box testing has the advantage of "an unaffiliated
opinion," on the one hand, and the disadvantage of blind exploring, on the
other.

WHITE BOX TESTING

White box testing, by contrast to black box testing, is when the

tester has access to the internal data structures and algorithms (and the
code that implement these)
Types of white box testing :-
The following types of white box testing exist:
Testing of the application using Public and Private APIs.Code
coverage- creating tests to satisfy some criteria of code coverage.
For example, the test designer can create tests to cause all statements
in the program to be executed at least once.
fault injection
methods.mutationtesti
ngmethods.
22
static testing-White box testing includes all static testing.

23
CODE COMPLETENESSE VALUATION

White box testing methods can also be used to evaluate the

completeness of a test suite that was created with black box testing
methods. This allows the software team to examine parts of a system that
are rarely tested and ensures that the most I import an function points
have been tested.

Two common forms of code coverage are:

Function Coverage: Which reports on functions executed and
Statement Coverage: Which reports on the number of lines
executed to complete the test.
They both return coverage metric, measured as a percentage

24
 HARDWARE AND SOFTWARE REQUIREMENTS

HARDWARE REQUIREMENTS:

I.OPERATINGSYSTEM : WINDOWS 7 AND ABOVE

II. PROCESSOR : PENTIUM OR AMD PROCESSOR

III. MOTHER BOARD : 1.845OR915,995FORPENTIUM0RMSI

K9MM-V VIA K8M800+8237R

PLUS CHIP SET

FORAMDATHALON

IV. RAM : 512MB+

V. Hard disk : SATA40GBORABOVE

VI. CD/DVDr/wmultidrivecombo: (Ifbackuprequired)

VII. FLOPPYDRIVE1.44MB : (IfBackuprequired)

VIII. MONITOR 14.1or15-17inch

IX. Keyboardandmouse

X. Printer : required

SOFTWAREREQUIREMENTS:

I. WindowsOS
II. Python

25
 BIBLIOGRAPHY

1.Computer science With Python -Class XI & XII

By: Sumita Arora
2. Head-FirstPython’(2ndEdition)By:PaulBarry
3. Python Programming: An Introduction to
Computer Science (3rd Edition)By John
Zelle
4.Website:https://www.w3resource.com

*****************

26