Non-Financial/Technical

Proposal for
World-Runner Parcel
Management System

PREPARED BY
Syed Salman Reza
Networld Technology Limited
Software Engineer | Software Solution & Management | Networld | Office: Uday Tower, 57-57A
Gulshan Avenue (South), Circle-1, Gulshan, Dhaka 1212, Bangladesh (Level-4) Phone: +880
967-8288488; EXT-169 | Mobile: +88-01709279556
Email: [email protected]
Website: www.networld-bd.com
Table of Contents:
1. Application Purpose 3
2. Application Scope 3
3. Application Intended Audience 4
4. Application Development Process and Timeline 4
4.1. Development Process and Timeline (in weeks) 5
5. Application Technology Stack 6
6. Application Key Features 6
7. Application Functional Requirements 7
8. Application Actors (User Roles) 7
9. Application Non-Functional Requirements 8
9.1. Scalability 8
9.2. Security 8
9.3. Performance 8
10. Application Data Requirements 9
11. Application Testing Requirements 9
11.1. Unit Testing 9
11.2. Integration Testing 9
11.3. User Acceptance Testing (UAT) 9
12. Application Risks and Assumptions 9
12.1. Risks 9
12.2. Assumptions 10
13. Application Implementation Process and Timeline 10
13.1. Implementation Timeline (in weeks) 10
14. Application Maintenance Policy and Others 10
14.1. 24/7 Technical Support 10
14.2. Service Level Agreement (SLA) 10
14.3. Regular Updates 11
15. Hardware Requirements 11
15.1. Server Specifications 11
15.2. Networking (VPN Tunnel) 11
15.3. End-User Devices 11
16. Software Requirements 11
 16.1. Operating System 11
16.2. Database 11
16.3. Web Server 11
17. Architecture and User Flow Diagram 12
18. Team Structure and Key Personnel 12
18.1 Lead Developer and Project Manager 12
18.2 Assistant Developer, System Tester, UI/UX Designer, Database
Administrator 14

1. Application Purpose
The World-Runner Parcel Management System aims to streamline the process of
managing parcel booking, tracking, and delivery confirmation for banking
documents such as cheques, cards, and other important items. This system
automates the parcel requisition process, ensuring accuracy, security, and
efficiency throughout the parcel lifecycle. By providing a centralized platform for
users to interact with various banking entities, the system simplifies document
dispatch and tracking, significantly reducing manual effort and errors while
improving operational performance.

2. Application Scope
The system will manage the entire lifecycle of parcel transactions within banking
institutions, covering:
 ● Parcel Booking: Users can book parcels related to sensitive documents, such
as banking cards and cheques, for delivery to various branches or customers.
● Tracking and Confirmation: Real-time tracking will allow users to monitor
the status of parcels from dispatch to delivery, ensuring transparency.
● Organization Management: The system will manage multiple banking
organizations, allowing branches to place and track parcel orders efficiently.
● Authentication and Authorization: Secure authentication mechanisms ensure
that only authorized personnel can access parcel-related data and
functionalities.
The system is scalable, with the capacity to support additional functionalities as
required, making it flexible enough to handle a variety of banking requisitions.

3. Application Intended Audience

The primary users of this system are:

● Bank Employees: These include branch managers and administrative staff

responsible for booking and tracking parcel deliveries.
● Logistics Personnel: Staff in charge of managing, dispatching, and
confirming parcel deliveries within the banking institution.
● IT Administrators: Responsible for maintaining the system, including
managing user access, updating the platform, and monitoring security.
● Banking Customers: In some cases, end customers may also be able to track
the delivery of their cheques or cards through an online portal, enhancing
customer satisfaction.

4. Application Development Process and Timeline

The development of the World-Runner Parcel Management System will follow an
Agile methodology, ensuring regular feedback and iterative improvements
throughout the project lifecycle. This will result in a highly responsive and
user-centered platform.
4.1. Development Process and Timeline (in weeks)
Requirement Gathering (2 weeks):
● Stakeholder interviews to gather insights on workflows, pain points, and
specific requirements.
● Conduct workshops to define user stories and use cases.
● Deliverables: Functional and Non-Functional Requirements Document.
System Design (3 weeks):
● Design system architecture including UI/UX wireframes, database schema,
and security protocols.
● Deliverables: Architecture diagram, database schema, wireframes, and
security measures.
Development (6 weeks):

● Develop core system modules for parcel booking, tracking, organization

management, and security.
● Deliverables: Source code, documentation, and working prototypes at the
end of each sprint.
Testing (3 weeks):
● Perform unit and integration testing to validate individual and system-wide
functionalities.
● Conduct User Acceptance Testing (UAT) to ensure the system meets user
requirements.
● Deliverables: Test reports, bug fixes, and UAT feedback.
Deployment (1 week):
● System deployment in a live environment, including server configuration
and user training.
● Deliverables: Fully deployed system with training documentation and
post-deployment support.
5. Application Technology Stack
The World-Runner Parcel Management System will use the following
technologies:
● Front-end: HTML5, CSS3, JavaScript (React or Vue.js)
● Back-end: PHP (Laravel Framework) for robust server-side logic.
● Database: MySQL for data storage, ensuring reliability and scalability.
● Web Server: Apache or Nginx, both known for their high performance and
security features.
● Operating System: Linux (preferred for its security and stability) or
Windows Server.

6. Application Key Features

Parcel Booking:
● Users can initiate and manage parcel bookings for banking documents like
cheques and cards.
● Automated workflows for handling large volumes of bookings efficiently.
Tracking and Confirmation:
● Real-time updates on the status of parcels.
● Delivery confirmation upon receipt of the parcel by the recipient.
Organization Management:
● Administrative control over multiple banking organizations.
● Tools for managing internal logistics, branch interactions, and parcel
distribution.
Authentication and Authorization:
● Secure login system with role-based access control.
● Different levels of permissions based on user roles (Admin, Logistics, Bank
Staff).
7. Application Functional Requirements
Parcel Booking Process:
● Users will submit parcel booking requests with customer and banking
document details.
● The system will verify document types and availability before processing the
request.
Parcel Tracking:
● The system will update the parcel’s journey at every checkpoint, providing
real-time updates to users.
Delivery Confirmation:
● Upon delivery, users can confirm receipt, and the system will update the
parcel's status to “Delivered.”
Organization Management:
● Multiple branches or departments within a bank can use the platform,
allowing centralized parcel management across locations.

8. Application Actors (User Roles)

Admin:
● Manage users, roles, permissions, and system configurations.
● Oversee system maintenance and audit trails for compliance.
Logistics Personnel:
● Responsible for processing, dispatching, and confirming parcel deliveries.
● Manage parcel statuses and provide updates.
Bank Staff (User Role):
● Initiate and track parcel bookings.
● Receive notifications on parcel status updates and confirmations.
9. Application Non-Functional Requirements
● Scalability: The system will handle growing numbers of users and
transactions as more branches adopt the platform.
● Security: Data encryption, role-based access, and audit trails to ensure
sensitive data is handled securely.
● Performance: Fast response times and efficient handling of high transaction
volumes.

9.1. Scalability
● Horizontal Scalability: Adding more servers to distribute the load and
enhance performance.
● Vertical Scalability: Ability to upgrade the server hardware to accommodate
increased demand.

9.2. Security
● Role-Based Access Control (RBAC): Permissions assigned based on user
roles to prevent unauthorized access.
● Encryption: SSL encryption for data in transit and AES encryption for data
at rest.

9.3. Performance
● Response Time: The system must respond to user actions (e.g., submitting a
parcel request, tracking) within 2 seconds under normal load.
● Throughput: Capable of handling hundreds of transactions per minute during
peak usage times.
10. Application Data Requirements
● User Data: Information such as login credentials, roles, and permissions.
● Parcel Data: Details about each parcel, including sender, recipient, and
tracking history.
● Banking Documents Data: Information about the documents being shipped
(e.g., cheque books, banking cards).

11. Application Testing Requirements

11.1. Unit Testing

Each individual component (e.g., parcel booking, tracking) will be tested to ensure
it performs as expected.

11.2. Integration Testing

Testing the interaction between different components to ensure smooth data flow
and functionality across modules.

11.3. User Acceptance Testing (UAT)

End users (bank staff, logistics personnel) will test the system in a real-world
environment to confirm that it meets their needs and requirements.

12. Application Risks and Assumptions

12.1. Risks
Requirement Changes: Unforeseen changes in system requirements could lead to
delays.
Data Migration: Issues could arise during the migration of legacy parcel records.
12.2. Assumptions
Stakeholder Involvement: It is assumed that stakeholders will provide timely
feedback.
Infrastructure: The bank’s IT infrastructure will support the system without major
upgrades.

13. Application Implementation Process and Timeline

The system will be deployed in phases to minimize disruptions to existing
operations.

13.1. Implementation Timeline (in weeks)

● Installation (1 week): Set up the system on the bank’s servers.
● Data Migration (2 weeks): Migrate any legacy parcel data to the new system.
● Integration (1 week): Ensure the system integrates with the bank’s existing
tools, such as email systems.
● Training (1 week): Train key users (admins, logistics personnel, bank staff).
● Go-Live (1 week): Launch the system with IT support for immediate issue
resolution.

14. Application Maintenance Policy and Others

14.1. 24/7 Technical Support

A helpdesk will be available for users to report technical issues or seek assistance.

14.2. Service Level Agreement (SLA)

● Critical Issues: Resolved within 4 hours.
● Major Issues: Addressed within 12 hours.
● Minor Issues: Fixed within 48 hours.
14.3. Regular Updates
Monthly updates including security patches and minor enhancements to keep the
system secure and up-to-date.

15. Hardware Requirements

15.1. Server Specifications

4 CPU cores, 16 GB RAM, and 500 GB SSD storage recommended for optimal
performance.

15.2. Networking (VPN Tunnel)

1 Gbps network speed for fast data transmission.

15.3. End-User Devices

Intel i5 processor, 8 GB RAM, and a modern web browser required for smooth
operation.

16. Software Requirements

16.1. Operating System

Linux (preferred for security) or Windows Server.

16.2. Database
MySQL for reliable and scalable data storage.

16.3. Web Server

Apache or Nginx for serving web content efficiently.
17. Architecture and User Flow Diagram
The system architecture will consist of multiple layers:

● User Interface Layer: Handles interactions between users and the system.
● Application Logic Layer: Manages business rules, parcel booking, tracking,
and organization management.
● Database Layer: Stores all parcel, user, and banking document data.
● External Services Layer: Integrates with email servers and other external
services to enable notifications and reporting.

18. Team Structure and Key Personnel

The project team will consist of experienced professionals who will manage the
development, implementation, and maintenance of the CBRMS. Key personnel
include:

18.1 Lead Developer and Project Manager

Syed Salman Reza – Software Engineer Role: Lead Developer and Project
Manager

Job Description: The development and implementation of the Cheque Book

Requisition Management System (CBRMS) will be managed by Syed Salman
Reza, will be lead the project from start to finish, ensuring all stages, responsible
for designing/updating the system architecture, writing the core application logic,
ensuring that the system from requirement gathering to deployment, are completed
efficiently and meet the client’s requirements.
Experience: Over 2 years of experience as a Software Engineer and Full-Stack
Developer, specializing in PHP (Laravel) and .NET frameworks. Skilled in
designing and maintaining backend systems and successfully managing full project
lifecycle for various software applications, including CI/CD pipeline
implementations and cloud/local server deployment, also certified in various
Oracle Cloud technologies, including Data Management and Cloud Infrastructure

Education: Currently pursuing an MS in Computer Science & Engineering

(MSCSE) from North South University, Dhaka, with a completed BSc in Computer
Science and Engineering from the same institution.

Key Skills:
● Programming Languages: PHP (Laravel), Python (Django, Flask), C++, C#
(.NET), Java, JavaScript, and TypeScript.
● Web Development: Expertise in full-stack web development, with
experience in cloud deployment, database management, and API integration.
● Project Management: Extensive experience in managing the end-to-end
software development process, from system design and database architecture
to deployment and support.
● Database Management: Skilled in MySQL database design, optimization,
and management, ensuring high performance and data integrity including
Data Management.
● API Development: Proficient in developing and integrating RESTful APIs,
enabling seamless communication between systems.
● Tools: Proficient in using VS Code, Git, Postman, and other essential
development and testing tools.

Professional Experience:
● Networld Technology Limited (October 2022 – Present): Developed and
maintained backend systems using the .NET framework for banking
applications. Managed the full project lifecycle, from development to
deployment on IIS servers using PHP (Laravel).
● With a strong background in software engineering, project management, and
banking applications, Syed Salman Reza is fully equipped to lead the
CBRMS project, ensuring a successful and timely deployment.
18.2 Assistant Developer, System Tester, UI/UX Designer, Database
Administrator

MD Zihadul Islam – Software Engineer

Role: Assistant Developer, System Tester, UI/UX Designer, Database

Administrator

Job Description: The Cheque Book Requisition Management System (CBRMS)

development team will be supported by MD Zihadul Islam, who will serve as an
Assistant Developer. He will handle multiple roles within the project, including
system testing, UI/UX design, and database administration. Zihadul will assist the
lead developer and ensure the system's functionality, usability, and performance are
maintained throughout the project lifecycle.

Experience: With a solid foundation in front-end development using Vue.js,

Nuxt.js, HTML, CSS, and JavaScript, MD Zihadul Islam has hands-on experience
in designing and testing web applications. He is also certified in various Oracle
Cloud technologies, including Data Management and Cloud Infrastructure, making
him adept at handling complex system testing and cloud-based database
administration.

Education: Bachelor of Science in Computer Science and Engineering (BSc. CSE)

from the American International University Bangladesh (AIUB), graduating in
2023.

Key Skills:
● Programming Languages: Proficient in C, C++, Java, Vue.js, PHP, and
Nuxt.js.
● UI/UX Design: Skilled in designing user-friendly interfaces using HTML,
CSS, Bootstrap, and Tailwind.
 ● Database Management: Familiar with database systems and cloud
infrastructure, with expertise in Oracle Cloud solutions and MySQL.
● System Testing: Experience in testing web applications for functionality,
usability, and performance using a range of tools and methodologies.
● Tools and Technologies: Proficient in GitHub, Trello, Slack, Google Colab,
BitBucket, and other collaboration tools.

Professional Experience:
Software Engineer – Networld Technology Limited (Nov 2023 – Present):
● Working as a frontend developer using Vue.js and Nuxt.js for web
applications.
● Contributed to UI/UX design and collaborated with cross-functional teams
to deliver optimized user interfaces.
● Engaged in testing activities to ensure the stability and performance of the
applications during development.