This presentation summarizes a business dashboard system developed for NCC Bank Limited. The system allows employees and administrators to view reports on loan and deposit products. It was developed using an incremental software process model with requirements gathering, design, implementation, and testing phases. Key features include employee management functions for administrators and report generation for both employees and administrators. Testing showed the system allows authorized users to successfully generate reports and manage employee data and permissions as intended.

1. Presentation on
NCC Bank Business Dashboard
for
NCC Bank Limited
Prepared By
Faria Lara
ID# 2015000000204
Program: BSc in CSE
Supervised By
Md. Sohel Babu
Lecturer
of
CSE department
Southeast University

2. Organization overview
.
Product and services
• In house software development
• Software Security maintenance
• Core banking support
• Network maintenance
• Permission regarding access

3. Topics To Be Covered...
❖ Project Overview
❖ Objectives
❖ Requirement Engineering
❖ Software Process model
❖ Analysis
❖ DFD Diagram
❖ Design
❖ Software Demonstration
❖ Testing

4. Project overview
✔ Employee management with role and permission
✔ Employee management
✔ Banking product Management.
✔ Generate report for bank.

5. ► Broad objective
► Develop a user friendly system where employees and admin
can find out the product( Loan and Deposit) growth reports.
► Specific objective
► Improve employee work process.
► Manage employee.
► Reduce time for find out the Loan and Deposit result.
► View Loan and deposit product rules information.
OBJECTIVES

6. Methodology:
For this project in data collection phase I have collected primary data.
► The development process on NCC Bank Business Dashboard System for NCC Bank
Limited, the structure will describe later on Software analysis & design.
Data Source:
► Primary
► Secondary
Primary data are collected through NCC Bank, practical experience and by working
here. Also collected data by facing interview to the employee IT department of this
Organization.
Secondary data Collected from Various source like Google, Youtube, Research papers etc.

7. Requirement Engineering
User requirements
System requirements
Functional requirements
Non-functional requirements

8. User requirements (Admin)
Admin can login
Admin can check the loan product
Admin can check the deposit product
Admin can print the result
Admin can view employee list
Admin can activate employee
Admin can deactivate employee
Admin can add employee
Admin can delete employee
Admin can update employee password

9. User requirements (Employee)
1. Employee can login
2. For login employee have to do registration
3. Employee can check the loan product
4. Employee can check the deposit product
5. Employee can print the result

10. Function Requirement(Admin)
► View all employee information
► Activate or deactivate employee
► Modify employee information
► Add employee
► Modify password
► Generate report
► View Report
► Login

11. Function Requirement(Employee)
► Submit registration form
► View loan and deposit product information
► View loan requirement
► View deposit requirement
► Print out the result
► Login

12. Non –Functional Requirement
► Each employee has his own account.
► Employee have to login with his own password.
► Password will be encrypted.
► Employee name & password for admin, employee saved in database for security
purpose.

13. Feasibility Study
There are three major areas of feasibility study. Those are-
•Technical
•Economic
•Operational

14. Software process model
Analysis Design Code Test
Analysis Design Code Test
Analysis Design Code Test
Analysis Design Code Test
Analysis Design Code Test
Design Code Test
Analysis Design Code Test
Analysis Design Code Test
Analysis Design Code Test
Analysis Design Code Test
Analysis Design
Analysis Design Code Test
Design Code Test
Incremental process model

15. Process Model
There are some reasons for choosing incremental process model. Some situations
where the use of incremental model is most appropriate and the reason is given
below:
► Errors are easy to be recognized.
► In this model user can respond to each built.
► Though the development stages changes can be done.
► Errors are easy to be identified.
► Easier to test and debug
► More flexible.
► Simple manage risk because it handled during its iteration.

16. Project schedule chart

17. Data Flow Diagram(level 0)

18. Data Flow Diagram(level 1)

19. DFD(Level-2) process 1 (Admin Login)

20. DFD(Level-2) process 2 (Employee
Login)

21. DFD(Level-2) process 3 (Employee List)

22. DFD(Level-2) process 4 (LN/DP
selection)

23. DFD(Level-2) process 5 (Employee
Status)

24. ER
diagram

25. Activity
diagram for
Admin

26. Activity
Diagram
for
employee

27. Use case
diagram

28. Sequence
diagram
of
Admin

29. Sequence diagram of
employee

30. Software
Demonstration

31. Testing
Testing scenario
No:1
Scenario Admin Login testing scenario of my system
Input’s Admin unique ID, Unique password of User for Login
Desired Output(s) When enter Admin ID, password then get access level desire.
Actual Output(s) For Admin login system worked correctly.
Verdict Getting result from Desired Output’s and Actual Output’s decided this
system is successful for log

32. Testing scenario No:3
Scenario Employee Registration
Input’s First name, Last name, Phone number, Employee ID, Designation,
Password
Desired Output(s) When entire all basic info new employee eill be registered.
Actual Output(s) Adding employee.
Verdict The process worked correctly and successfully.

33. Testing scenario No:4
Scenario Update and delete employee
Input’s Request to edit and delete employee
Desired output(s) Update and delete from Database
Actual output(s) For update and delete the system work correctly.
Verdict The process successfully.

34. Testing scenario No:5 Employee Status
scenario Admin can control employee Status
Input’s Request to update employee status
Desired output(s) Admin can active or de-active employee status from admin
controller.
Actual output(s) Admin can control hole system.
verdict The process is worked successfully and correctly.

35. Testing scenario No:7 Admin view employee list
scenario Admin can show employee list
Input’s Request admin to login
Desired output Showing the employee list
Actual output For showing employee list
verdict The process is worked successfully and correctly.

36. Testing
Testing scenario No:8 Admin and employee generate report
scenario Admin can generate report
Input’s Request to generate report
Desired output Showing the report output
Actual output For showing report output
verdict The process is worked successfully and correctly

37. Limitations
Client can not access this system .
This system can not access outside off office.

38. Conclusions
► Using NCC Bank Business Dashboard system Employee
can easily generate Loan and Deposit product result which
will be reduce time. And also this system improve
employee work process.