Академический Документы
Профессиональный Документы
Культура Документы
October,2011
Warning This is a hard copy of a document maintained on electronic media. It may not be the latest version. Kindly ascertain the latest version from the Document Master List available with the Project Leader.
This document and any revised pages are subject to document control. Please keep them upto-date using the release notices from the distributor of the document. Approved by: Authorised by: Date: Date:
PREFACE
Purpose of this Document
The purpose of this document is to outline the detailed Functional Requirements of the Account management module of the NSEP's Top-up Program. This document describes the System Requirements Specifications of the National Self Employment Top up program . This document lays down the software requirements for the application that have been captured through a detailed study of the business workflow and the functions.
Intended Audience
This document is intended for use by the designers of the system, and for those who may be required to maintain it. The document will enable them to understand all aspects of the system in detail. It will enable the NSEP to know that TCS has captured all the requirements. The document will also be used by NSEP for carrying out the acceptance testing.
ii
TABLE OF CONTENTS
1. INTRODUCTION..................................................................................................................1 1.1 BACKGROUND.......................................................................................................................1 1.2 SCOPE...............................................................................................................................1 1.3 BUSINESS JUSTIFICATION FOR INVESTMENT..................................................................................2 1.4 PRODUCT PERSPECTIVE..........................................................................................................2 1.5 KEY ASSUMPTIONS, DEPENDENCIES, CONSTRAINTS AND OVERRIDING PRIORITIES.................................2 1. USER CLASSES AND CHARACTERISTICS........................................................................................3 1. HARDWARE AND SOFTWARE PLATFORM........................................................................................4 2. FUNCTIONAL REQUIREMENTS.........................................................................................5 2.1 REQUIREMENT 1..................................................................................................................5 2.2 REQUIREMENT 2..................................................................................................................5 3. USER INTERFACE SPECIFICATIONS................................................................................6 3.1 GUI SCREEN LAYOUTS..........................................................................................................6 3.2 GUI REPORT LAYOUTS........................................................................................................14 4. OTHER REQUIREMENTS..................................................................................................16 4.1 USER ACCESS CONTROL AND SECURITY..................................................................................16 4.2 ARCHIVING AND HOUSEKEEPING..............................................................................................16 4.3 PERFORMANCE REQUIREMENTS..............................................................................................16 5.APPENDIX A: ANALYSIS OBJECT MODEL....................................................................17 Total Number of pages: 24
iii
1. Introduction
1.1 Background
This document outlines the software requirement specification for the National self employment program Application System. It is the outcome of the Analysis Phase during which discussions were held with the users. The objective of this Analysis Phase was to:
Define the scope for the NSEP (NATIONAL SELF EMPLOYEMENT PROGRAM). Serve as the baseline for the design of the NSEP Account management application system.
Any changes to requirements after acceptance of this document will be through appropriate Change Management procedure, as detailed in the contract. Both the user and designer should go through the document carefully in order to ensure that : 1. All the user requirements which need to be supported by the system have been identified and detailed. 2. The document is a clear and unambiguous statement of functionality required from the system for the design and development team. 3. The document can be used as a basis for development of the System Test data. It is essential to identify the problems, if any, with the basic structure of the proposed system at this stage. If these are not taken care of at this stage, it may be difficult to incorporate the desired modifications to overcome the shortcomings at a later stage. Students who wants to participate in the self employement program are benefitted here. They register their name with the NSEP banks , that create an account and also a related NSEP account which is a reccuring deposit one . Here the NSEP carries out the topup, bonus calculation and updates the balance according to the maturity period. Therefore the account module requires NSEP creating both student and NSEP account and carry out basic functionalities and creating defaulters list in case the student doesnt pay the minimum committed amount.
1.2
Scope
The scope of the project is to design and develop the NSEP's Top-up Program System as per the details mentioned in the technical proposal. The main business users for this project are non vocational undergraduate students and their families. This project is to be implemented at a national level. The implementation of this project will greatly benefit students from poor family background. The scope of the project involves detailed Analysis, Design and Development of computer based application for NSEPAccount Management, NSEP, Chennai.
Internal Use Only 1
The design phase consists of the following stages: 1.3 Database design, Screen design, Report painting Preparation of SDD based on the functions specified in SRS Review of SDD
Business Justification for Investment The implementation of this project will greatly benefit NSEP by allowing it to manage all of its operations under one roof. Students can easily access their account details, and Nsep periodically top up the Nsep account of the registered student.
1.4
Product Perspective
The National Self Employment Program for Undergraduate Students (NSEP) Top-up Program is a program to help non-vocational undergraduate students from rural backgrounds to fund their own employment after graduation. The students can also apply for a loan from NSEP which will be sanctioned if it meets the predefined conditions. The targeted families will be informed about the NSEP Top-up Program. The registration process begins by filling out the student registration form online. An acknowledgment number is generated for the student. The student is required to print out the completed form, sign it and submit it at a bank participating in the program. The bank creates a student account and NSEP related account and updates the account details to NSEP. The student then receives his log in credentials and can use these to view and edit his profile on NSEP. Students have to make their monthly savings deposit in the bank to their student account. The details of the deposit will be conveyed to NSEP by the bank and if the deposit satisfies the predefined conditions, NSEP makes the top-up contribution to the related account tagged to that student. Bonus (if applicable) is also deposited in the related account by NSEP. 1.5 Key Assumptions, Dependencies, Constraints and Overriding Priorities
The successful execution of the assignment will depend on the following factors: Assumptions The program will be running on a multi-bank model Single college can have students who have account in multiple banks System will track the individual contribution based on the agreed rule and enable the program to decide on the top-up part Program will permit students to join the program within a pre-defined period of time instead of a particular date/month Regular feed file from the bank with desired data format will be available for processing and reconciliation of the transaction The feed file from the bank will be CSV format 75% top up rate , 3% quarterly rate, 5%annual rates The bank do not calculate any separate interest.
Internal Use Only 2
Dependencies Involvement of the end users in signing off this SRS document. Availability of System Software from the client for development. Availability of installed hardware/System software for implementation.
Constraints Interest calculation (if applicable) for the account will be done by individual banking system Fund availability check at NSEP's master account for Top-up will be outside the scope the system 1. User Classes and Characteristics a) Student account creation Nsep Admin To Create Student Account To Update student account balance To View NonDefaulters Report To View Student Account details collegewise and individually To Inactivate Student Account
b) NSEP account creation Nsep Admin To Create Nsep Account To Calculate Monthly topup To Calculate Quartely Bonus To Calculate Yearly Bonus To Close Nsep account
c) Transaction Entities Nsep Admin To Read CSV file from bank To Update CSV file
Internal Use Only 3
To validate transactions To manually create and delete transactions d)NSEP employee management Nsep admin To create/ Register new employee To view an employee/ view all employees To update employee details To delete an employee
OS: Windows XP and Linux JSP/SERVELET/JAVA Tomcat 6.0 Oracle 10G Web Browser: Internet Explorer 7 and above, Mozilla Firefox 3.5 and above
2. Functional Requirements
Creating student account Creating NSEP related account and calculating bonuses Validating and Viewing Transactions Creating NSEP employee account
2.1 Requirement 1
Creating student account: Student account is created after receiving the personal details from the student Student profile can be viewed and updated by the student Depending on the deposits made by the student the account is updated by Nsep admin On the end of the fixed period the student account is closed
2.2 Requirement 2
Creating NSEP related account: Nsep Admin creates a related Nsep account to each student registered Calculates the Monthly Topup, Quartely bonus and annual bonus Update the Nsep account Deletes the account on the end of the fixed period
2.3 Requirement 3
Validating and Viewing transactions: Reads the CSV from the bank. Uploads the CSV file and Views the Transactions Validates the Transactions for Duplicate records Deletes the Duplicate entries Provision for manually creating and deleting the Transaction
2.4 Requirement 4
creating NSEP employee account: Creates a new NSEP employee account. Views a particular employee and also can view all employee details at a glance. Updates the employee details Deletes a particular employee
next page::
Account Management
1.Create page
next page::
next page::
10
4.delete account
11
12
3.Manual entry
13
Reports on accounts opened(NSEP accounts) with details. Reports on transactions made. Defaulters list Reports on the contribution made to the NSEP account.
Report 2
Account ID
Student ID
Transaction date
Amount
14
NSEP Student Committed Monthly Quarterly Annual Monthly Account ID Amount Deposit Bonus Bonus topup ID
Total balance
MONTHLY PERFORMANCE REPORT COLLEGE ID COLLEGE NAME TOTAL NUMBER OF STUDENT REGISTERED FOR NSEP DEFAULTE R
Defaulters list
STUDENT ID
COLLEGE ID
STUDENT NAME
MONTH
15
4. Other Requirements
Apart from the requirements which we described in the process flow, there are a few which are to be mentioned for better compatibility and maintenance.
Use Case UC1: Create Student Account Level: NSEP Admin's goal. Scope: NSEP Top-Up Program Primary Actor:NSEP admin Stakeholders: Students : Wants to open a bank account for the NSEP top up program. NSEP admin: Wants to store the details provided by the student in the system. Preconditions: Student should have a bank account for the NSEP program. Success Guarantee: Student account is created successfully. Main Success Scenario: 1 .Admin enters the student details 2 .Successfully creates a student account. Extensions: none. Use Case UC2: View non defaulters report Level: NSEP admin's goal. Scope: NSEP Top-Up Program Primary Actor:NSEP admin Stakeholders: NSEP admin: Wants to view the defaulters report. Preconditions: Student should deposit monthly savings. Success Guarantee: Defaulters report is viewed successfully.
Internal Use Only 17
Use Case UC3: Deactivate Student Account Level: NSEP Admin's goal. Scope: NSEP Top-Up Program Primary Actor: NSEP admin Stakeholders: NSEP admin: Wants to close the student's account when the time period expires Preconditions: The time period of the payment should be expired. Success Guarantee: Student account is closed successfully. Main Success Scenario: 1. Student completes his monthly payment/time period expires. 2. Student account is deleted successfully. Extensions: 1a. Invalid account number. 1. System displays an error message.
Use Case UC4: Create NSEP account Level: NSEP admin Scope: NSEP Top-Up Program Primary Actor:NSEP admin Stakeholders: NSEP admin: Wants to create a recurring deposit account and tag it to each individual student. Preconditions: Student should have an account in the bank for the NSEP Top-Up program. Success Guarantee: NSEP account is created successfully. Main Success Scenario: 1. NSEP admin opens the account. 3. Account details are stored in the system. Extensions: 1.Invalid inputs. 1a.System displays an error message. Use Case UC5: Deactivate NSEP account Level: NSEP admin Scope: NSEP Top-Up Program Primary Actor: NSEP admin Stakeholders: NSEP admin: Wants the NSEP account details to be removed from the system.
Internal Use Only 18
Preconditions: NSEP should have an account in the bank for the the Top-Up program. Success Guarantee: NSEP account is deleted successfully. Main Success Scenario: 1. NSEP admindeletes the NSEP account. 2. Account details are removed from the system. Extensions: 1.Invalid account number. 1a.System displays an error message. Use Case UC6: bonus calculation Level: NSEP admin goal. Scope: NSEP Top-Up Program Primary Actor: NSEP admin. stakeholders: NSEP admin Wants to calculate the annual and monthly bonuses . Preconditions: NSEP should have an account in the bank for the the Top-Up program. Success Guarantee: Bonus calculation is performed successfully. Main Success Scenario: 1. NSEP admin views the regularity of payment/amount deposited per month etc. 2. Based on that he performs Bonus/top-up calculations. Extensions: 1.Invalid account number. 1a.System displays an error message. Use Case UC7: View account details Level:NSEP admin goal. Scope: NSEP Top-Up Program Primary Actor: NSEP admin. Stakeholders: NSEP admin: Wants to view account details. Preconditions: NSEP should have an account in the bank for the the Top-Up program. Success Guarantee: NSEP admin views account details successfully. Main Success Scenario: 1. NSEP adminenters the account number.
Internal Use Only 19
NSEP admin views the account details successfully. Extensions: 1.Invalid account number. 1a.System displays an error message.
Deactivate account
20
2.NSEP employee management Use Case UC1: Create NSEP employees Level: NSEP Admin. Scope: NSEP Top-Up Program Primary Actor: NSEP Admin. Stakeholders: NSEP admin: Register new NSEP employees. NSEP employee: Added to the NSEP account management system. Preconditions: none. Success Guarantee: NSEP employees are created successfully. Main Success Scenario: 1. NSEP Admin enters the details of employees. 2. Employees are added to the NSEP account management system successfully. Extensions: none. Use Case UC2: View NSEP employee Details Level: NSEP Admin. Scope: NSEP Top-Up Program Primary Actor: NSEP Admin. Stakeholders: NSEP admin: Wants to view employee details Preconditions: Employee should be registered in the account management system by the admin. Success Guarantee: Admin views the employee details successfully. Main Success Scenario: 1. NSEP Admin enters the employee Id. 2. Employee details are displayed on the system. Extensions: 1.Invalid employee Id. 1a. System displays an error message.
Internal Use Only 21
Use Case UC3: Delete NSEP employee Details Level: NSEP Admin. Scope: NSEP Top-Up Program Primary Actor: NSEP Admin. Stakeholders: NSEP admin: Wants to delete employee details from the system. Preconditions: Employee should be registered in the account management system by the admin. Success Guarantee: Admin deletes the employee details successfully. Main Success Scenario: 1. NSEP Admin enters the employee Id. 2. Employee details are removed from the system. Extensions: 1.Invalid employee Id. 1a. System displays an error message.
Use Case UC4: Update NSEP employee Details Level: NSEP Admin. Scope: NSEP Top-Up Program Primary Actor: NSEP Admin. Stakeholders: NSEP admin: Wants to update employee details Preconditions: Employee should be registered in the account management system by the admin. Success Guarantee: Admin updates the employee details successfully. Main Success Scenario: 1. NSEP Admin enters the employee Id. 2. Employee details are displayed on the system. 3. Admin updates the details. 4. Edited details are stored in the system successfully. Extensions: 1.Invalid employee Id. 1a. System displays an error message.
Internal Use Only 22
Create employees
23
4.Transaction Entities Use Case UC1: Create transactions Entries from the csv Level: Nsep Admin goal. Scope: NSEP Top-Up Program Primary Actor: Nsep Admin Stakeholders: Nsep admin: Get details from the bank and validates the transactions Preconditions: Transactions details are to be sent by the bank Success Guarantee: Validation done successfully. Main Success Scenario: 1. Bank gives the details of the transcations 2. Nsep manager uploads it and validates Extensions: 1.If duplicate entries are found, they are deleted Use Case UC2: provision for entering the transaction manually Level: Nsep Admin Scope: NSEP Top-Up Program Primary Actor: Nsep Admin Stakeholders: Nsep Admin: provides a provision for manual entry Preconditions: none Success Guarantee: transaction entered successfully. Main Success Scenario: 1. Bank person able to include the transactions manually if they were left to be recorded in the csv. Extensions: Transaction entered is saved.
Internal Use Only 24
Use Case UC3: provision for deleting the transaction manually Level: Nsep Admin Scope: NSEP Top-Up Program Primary Actor: Nsep Admin Stakeholders: Nsep Admin: provides a provision for manual entry deletion Preconditions: none Success Guarantee: transaction deleted successfully. Main Success Scenario: 1. Bank person able to delete the transactions manually if they were wrongly recorded in the csv. Extensions: Changes made in the Transactions is saved.
25
CLASS DIAGRAM
26
SEQUENCE DIAGRAMS
1.Student Account Creation
27
28
3.Employee Management
29
4.Transaction entities
30