Professional Documents
Culture Documents
Development of Web-Based Coaching Management Solution For
Development of Web-Based Coaching Management Solution For
for
Submitted by
Contents
Introduction...........................................................................................................................................2
Reference Documents............................................................................................................................2
Our Understanding of the Scope.............................................................................................................2
Scope: System Non-Functional Requirements.......................................................................................3
Key Deliverables.....................................................................................................................................3
Proposed solution architecture..............................................................................................................3
Technology Stack....................................................................................................................................3
Deployment Architecture.......................................................................................................................4
Hosting Option.......................................................................................................................................5
Team and Investment.............................................................................................................................5
Ballpark Estimate...................................................................................................................................5
Payment terms.......................................................................................................................................6
Cost escalation.......................................................................................................................................6
Assumptions...........................................................................................................................................6
Possible Risks and Risk Mitigation Plan...................................................................................................8
Agile Software Engineering Process........................................................................................................9
Requirements Discovery.......................................................................................................................... 9
Analysis & Design.................................................................................................................................... 9
Development........................................................................................................................................... 9
Development Stage................................................................................................................................. 9
Appeal and User Experience.................................................................................................................... 9
Easy Navigation....................................................................................................................................... 9
Testing................................................................................................................................................... 10
Release Management............................................................................................................................ 10
Communication Plan............................................................................................................................. 10
End to End Progress monitoring Tool.................................................................................................... 10
Change management/Budget Tracking................................................................................................. 11
Post deployment warranty and maintenance support..........................................................................11
Terms and conditions............................................................................................................................ 11
Lead Time.............................................................................................................................................. 11
Validity.................................................................................................................................................. 11
Introduction
Arcore is on a mission to help clients grow their businesses as a one stop shop for technology
needs of clients.
Arcore has requested Harrier to submit a proposal for the development of web-based coaching
management system. Harrier, because of their expertise and value-added services, is confident
of adding substantial value to Arcore.
Harrier team brings 200+ years of collective IT experience on developing multiple domain-
specific solutions, with a proven delivery track record across the following industries:
Reference Documents
Arcore shared the Software Requirements Specification document with following details, along
with access to the existing system.
1. almjad Academy Design Layout.pdf
c. Maker-checker
Key Deliverables
Following will be the major deliverables for this project:
Initial Project Setup including separate environments for DEV, TEST and PROD
Working Code
API Documentation, if applicable
Technical Architecture and High-level design (HLD), including deployment diagram
Clean Code Review Report using SonarQube tool
A Clean VAPT report
Technology Stack
Below is the proposed tech stack to be used.
Application Technology
Web Application Angular.js, Node.js, Express.js
Backend system Rest API
Database MySQL or PostgreSQL
Hosting AWS
Messaging/notifications AWS SNS for notifications, AWS SES for emails
Design pattern MVC
Code repository Code will be on GitHub private repository
Deployment Architecture
Hosting Option
Client will take care of hosting the system on the cloud with a preferred cloud service provider
like AWS. We shall be happy to assist with this, too. Optionally, Harrier will also be happy to
manage the hosting of the system on AWS if desired.
Ballpark Estimate
Module Effort (FE + BE + QA + Duration (days)
Sec + deploy) (person With parallel
days) work
Environment 10 5
Security, access control, file 44 45
import/export, email, SMS, PG and
delivery integrations
Admin UI system 22 45
Managers UI 22 45
Testing and deployment 30 75
Total 128 75
Estimated duration for delivery of the apps as per the shared designs, is 2-3 months from the
date of the PO. So over the delivery period of 3 months, the total development cost will be
about $20,000.
The configuration of the team may change based on the availability and architecture decided.
The cost may vary based on any changes in the scope or requirements.
Additional cost like hosting, third party tools, software licenses, registration
[one-time/periodic], etc. if required, shall be additional at actuals. Harrier will assist with
these from technology side like setup of the environment, creating a run book (with
environmental setup steps and configuration).
Payment terms
All payments become due immediately on raising invoices by us. Considering the time required
for processing, payments must reach us before 1 week from the date of each invoice received
by you. Payments not received by us within 1 week from the date of each invoice, will be
treated as overdue. A simple interest of 12% is payable on all overdue payments.
Please be informed that payments delayed beyond 1 months from the date of invoice will
encourage us to move the team to another project, resulting in delay of delivery of the system,
depending on the availability of team members after the payment is received.
Cost escalation
We will monitor the cost components relating to the scope changes on this assignment. In case
of variances against its budget for reasons not attributable to us, we will bring this to your
attention. The cost increases will be discussed and agreed upon mutually after we provide due
and reasonable justification for the increase. Payment periods and other conditions for such
invoices will be similar for payments laid out in this proposal.
Assumptions
Designated contact person from Arcore will be available and spend required time for
providing clarifications and for resolving issues related to the system
Hardware – Harrier shall be happy to assist with hosting the system on a cloud
infrastructure like AWS if required.
Arcore will take care of all travel, food, accommodation expenses and daily allowance of
Arcore team members for any onsite work to be done outside Nagpur or India.
Customer Factors
9. Customer involvement risk L
10. Customer experience risk L
11. Customer Acceptance risk L
Schedule Factors
12. Development Schedule risk L Agile development with continuous
integration on cloud
13. Delivery commitment risk L
Development Environment Factors
14. Physical facilities (Hardware, network) L
15. Tools availability risk L
16. Configuration management risk L Well controlled CM process
17. External hardware or software interfaces M Some interfaces to external systems
and will require collaboration with 3rd
party teams
18. Reusable components
Development Process Factors
19. Quality assurance approach risk L Independent QA team at Harrier
20. Communication risk L
21. Backup resources risk L Good backup resources available
Along with an excellent infrastructure and team, Harrier is a process driven organization. We
have delivered several projects using Agile SCRUM methodology for clients where we work
directly with the project manager/SCRUM master from customer’s end.
Requirements Discovery
Business requirements will be provided by Client, in an epic (like SRS but brief) or a story board,
including screen designs as those become available.
Development
Development Stage
The portal & mobile apps will be developed in sprints with daily SCRUMS with Client team.
Appeal and User Experience
We shall work closely with Client to come up with the most appropriate user experience
design keeping in mind ease of use with optimal performance/speed.
Easy Navigation
We’ll provide links to most of the content on the portal & mobile apps on the home page for
either direct access or with maximum 3 clicks.
Testing
Comprehensive testing will be carried out for each of the components developed. We also
perform one round of VAPT every year to ensure the system is secured.
Release Management
The developed portal & mobile apps will be released and deployed in UAT environment. Client
will do the acceptance testing for the system and Harrier will resolve any non-conformity for
each sprint.
Communication Plan
Harrier proposes a single point contact model. One person from client end will be responsible
for entire communication and final acceptance from client and, similarly, one person from
Harrier will be responsible for entire communication from our end and for final acceptance by
Client. We, from our experience, believe that this model helps reduce the communication gaps,
which are major source of problems in software development. Following are the contact details
for representatives from both ends.
Arcore Harrier
Name Sarang Nagmote Manish Sawankar
Email sarangnagmote05@gmail.com Manish.sawankar@harriersys.com
Lead Time
Harrier will commence work within 5 working days of receiving an order confirmation.
Validity
THANK YOU!
www.harriersys.com