SE LAB

NAME – Adhish Deb

REG. NO – 201900087

ROLL NO - 48

SEC - A

Objective

1. To understand software project management plan and software requirement and

specification documenting.

2. To prepare SPMP and SRS for the given project

SPMP

1. Introduction
▪ Objectives: Online banking system is a system which allows the customers

to access various banking facilities at their fingertips like update profile,

funds transfer, balance enquiry, generating statement etc. in a simple and

secured manner.
 ▪ Major Functions:

i. User Authentication
ii. Update Profile

iii. Fund Transfer

iv. Balance Enquiry

v. Statement Generation

▪ Performance Issues:

i. Database must be capable of handling through transactions and

modification i.e. it must be reliable and robust.

ii. System must be correctly optimised for the software to run

properly.

▪ Management & Technical Constraints:

i. Internet connectivity at the area is not very good.

ii. There is only one developer in the development section which

might create monopoly.

2. Project Estimates
▪ Estimation Techniques: COCOMO Model
▪ Effort: 0.3389PM

▪ Cost: $200
▪ Project Duration Estimates: 1.657 Months

3. Project Resources Plan

▪ Hardware:
 i. A computer with at least 4GB RAM and i5 processor

ii. Basic peripherals

▪ Software:

i. GCC Compiler

ii. IDE for C/C++ (most likely CLion)

▪ Special Resources:

i. Internet Connectivity

4. Schedules
▪ Analysis: 10/09/2020

i. Meetings and Discussion with stakeholders

ii. Document current systems

▪ Design: 20/09/2020
i. Design System, Databases, Data flow models

ii. Software Design

iii. Interface Design

▪ Development: 10/10/2020

i. Develop individual system modules

ii. Integrate system modules

iii. Make user-friendly interface

▪ Testing: 10/10/2020

i. Perform system testing

ii. Rectify errors and failures

5. Risk Management Plan
▪ Risk Analysis:

i. Since it is a banking system there is a huge security risk.

ii. In case of failure there might be drastic consequences.

iii. Employees must be trustworthy.

▪ Identification:
i. Security Risk

ii. Risk of Failure/Consistency

▪ Risk Estimation:

i. Security risk is the most critical of all since it can lead to huge loss.

▪ Abatement Procedures:

i. Hiring high profile cyber security engineers.

ii. Hiring trustworthy employees.

iii. Giving administrative control to only the project leads.

6. Project Tracking and Control Plan

▪ Meeting with the stakeholders has been fixed.

▪ Recruitment of developer is complete.

▪ All hardware and software requirements are met.

▪ Design team recruitment is ongoing.

7. Miscellaneous Plans
▪ Process Tailoring:
i. A well-defined structure would be used by the project team.
 ii. Commitment from team members who would create the software.

iii. Efficient use of resources is assured.

▪ Quality Assurance:

i. Each phase will work independently of each other, only interactions

would be by conducting meetings.

ii. It will be made sure that each phase completes the required task in

the estimated time.

iii. An independent internal audit team would be formed for quality

assurance.

SRS

1. Glossary:

i. SRS - Software Requirements Specification

ii. SPMP - Software Project Management Plan

iii. GCC - GNU Compiler Collection

iv. GNU - GNU's Not Unix

2. Specific Requirements:

a. Customer Requirements:

i. User Authentication - A fully functional login system which can

handle incorrect username and password situation.

ii. Update Profile - User should be able to update his/her profile.

 iii. Fund Transfer – Must allow fund transfer from one account to

another within the same bank.

iv. Balance Enquiry – Balance must be displayed as soon as user

selects the account.

v. Statement Generation – User must be able to see an print the

monthly and yearly statement.

b. Functional Requirements:

i. User should have a valid user id and password to login.

ii. If an incorrect password is given five times in succession, that

account will be locked for a set time.

iii. After user login, the list of accounts will be displayed on the screen.

iv. After selecting the desired account, current balance will be

displayed on the screen.

v. User can request details of the last ‘n’ number of transactions

performed.

vi. User can make fund transfers from his account to any other account
with the bank.

vii. User can request for change in address/ transaction report (monthly
and annual).

c. Non-functional Requirement:

i. Those not registered with the system shall not be able to enter it.

ii. The system shall be designed so it can be modified easily when

required.

iii. The system shall be simple to configure and use.

 iv. If access to the system is invalid more than three times then the

user will be locked out for security purposes for a set time.

d. Performance Requirements:

i. The program should perform efficiently consuming minimum time

and resources.

ii. It should be able to handle errors and failures appropriately without

breaking the system.

e. Design Requirements:

i. A computer
ii. A data flow making software (most likely draw.io)

iii. Internet availability

f. Derived Requirements

The system must fulfil the following criteria:

▪ Accuracy

▪ Reliability
▪ Secured

▪ Efficiency

▪ Compatibility

▪ Maintainability
▪ Portability

▪ Usability
g. Allocated Requirements:

i. One computer is allocated to create this piece of software.

ii. The computer is pre-equipped with the all the necessary

requirements which includes –

▪ GCC Compiler
▪ An IDE (most likely CLion)

▪ Environment setup

▪ Internet availability