Custom Web Portal
Scope of Work
For
Custom Web Platform
Custom Web Portal
1. Introduction of Project
This document covers the understanding of Project “Custom Web Portal” based on requirement gathered from the
client.
Deliverables: -
• User Portal
• Admin Panel
2. Requirement
2.1 Targeted Region
Suggested by client – India
2.2 Required Third Party API’s
• SMS Gateway for OTP verification and password recovery (msg91)
• Domain
• SSL Certificate
2.3 Web portal Language
• English
3. Key Modules
1. Homepage
• Engaging hero section with a compelling tagline.
• Overview of services (e.g., course selection guidance, admissions consulting, career counselling).
• Call-to-action buttons (e.g., "Book a Consultation," "Explore Courses").
2. Course Listings
• Search and filter options for courses (by category, location, duration, etc.).
• Detailed course descriptions, fees, and eligibility.
• Links to apply or inquire.
3. Services Section
• Course selection assistance (guidance on choosing the right course).
• University admissions consulting (help with applications, essays, interviews).
4. About Us
• Information about the consultancy, mission, and expertise.
• Profiles of consultants and experts.
• Testimonials from past clients.
5. Booking & Contact
• Online consultation booking
• Contact form and WhatsApp for quick inquiries.
Custom Web Portal
7. Student Success Stories
• Case studies of students who successfully got into their dream courses/universities.
4. Development Platforms/Environment
The client will provide application server detail. Tekniko
Global will use its development servers while application
is being created. Client is required to submit application
Project/Application Server
server credentials once design is approved from the
client’s end. There are 2 instances created. One is for the
staging and second one is for the Production.
Server Environment LAMP/WAMP
Client needs to inform Project Manager regarding any
existing deployment environment before commencing
Deployment Environment the project. Project Manager would also suggest the
deployment environment as per the requirement and
need of project.
5. Design Tools
Process Tool
Wire framing/Blueprinting Figma
Mockups/Prototyping Figma
Screen Designing Figma
Front End Web Designing PHP/ React
Color Schemes/Fonts Coolers
Custom Web Portal
6. Development Tools:
Platforms Tools
Programming Language PHP/ Node
IDE Sublime, Visual studio
Supporting OS Windows, Linux, Ubuntu, Mac Os
Web Services/API Pilot
Databases MY SQL/ Mongo DB
Cloud Server
Amazon Web Services/ Digital Ocean
Technologies
Load Balancer Apache, NGINX
Server CI/CD Jenkins
7. Components to be included in Delivery:
Components In-Scope
Consulting – Wire framing Yes
Design Yes
Web portal for users Yes
Admin Panel Yes
Source Code Yes
Custom Web Portal
8. Cost & Estimation:
Web Development
EST.
Product Coding Language EST. Time Remarks
Cost
PHP 20 Working days 45,000
Customer (Web),
25 Working
Super Admin Panel Node & React JS 65,000
Days
SMS API
Hosting Server
Shared by client
SSL Certificate
Domain
• Bug Fixing Warranty -03 Month
• Working Days- Monday to Friday (Except Central Govt. Holidays)
• Development time may vary due to any change in development process
• GST- 18% ON Est. Amount
• Development start date will count after approval of User Interface design from customer side by email.
• Pilot Run Time: - 7 Days after development
9. Development Phases:
PHASE 1: PRE-PLANNING FOR HOW TO BUILD AN APP
The first phase of any project is often the most important. When building a mobile app, it’s critical to take the time to go
through the necessary planning steps.
Step 1: Define the project and create use cases. Create a written definition of your app idea that clearly spells out what it
will do, who the users are and why they will care about it. Make sure you can answer the question “why does this app
need to exist?” What unique problem does it solve? Will the app simplify payment transactions for customers? Will it
increase productivity for field agents? What is the business case? Use this information to create use cases to guide the
project.
Step 2: Do your research. Is there already an app on the market similar to the one you are thinking to build? If so, how
can you do it better?
PHASE 2: MENTAL PROTOTYPING / DISCOVERY
A mental prototype is a brainstorm to help define a concept in visual terms. It’s the first opportunity to start to see how
the app might evolve…and to get a reality check.
Step 3: Involve the development team or technical architect. Ideally, the development team is involved at the beginning
of the project, but if the technical people who are actually going to build your mobile app aren’t already on board, now’s
the time to bring them in. This is when you can determine if your idea is feasible, can be successful and what expectations
you should have for time and budget.
Custom Web Portal
Step 4: Storyboard. With the use cases you created in Phase 1, create rough sketches of the idea on a sketchpad,
whiteboard, or template tiles. This is the first visual representation of all the screens and will help uncover usability issues
PHASE 3: TECHNICAL FEASIBILITY ASSESSMENT
It’s not enough to have cool interactions and an understanding of the visuals. You need to consider whether the back-end
systems will actually support the app’s functionality. For basic assessment of technical feasibility, you must do the
following:
Step 5: Get access to the data. Your mobile app needs to access usable data. Figuring this out could be as simple as
sourcing a Public APIs or as complicated as building your own abstraction layer.
Step 6: Determine what devices you are building your app for. An app will have different requirements depending on its
platform as well as the format (Smartphone, tablet, wearables, etc.).
Step 7: Refine project definition and establish go-to-market strategy. By the end of this phase, the team may have new
ideas for the app or have determined that some of the initial functionality isn’t feasible. At this point, take some time to
brainstorm, ask questions and review the status.
PHASE 4: TACTILE REFINEMENT OF USE CASES
It’s very difficult to define the touch experience without being able to touch the app and experience how it works and
flows. Phase 4 is about just that.
Step 8: Build a rapid prototype. “Rapid” is the operative word – build a prototype that gets the app concept into a user’s
hands as quickly as possible so you can see how it works for the most common use case. Use rough, not exhaustive,
wireframes. Bring your users in to touch the prototype to garner feedback as early as possible.
PHASE 5: DESIGN YOUR APP AND PREPARE FOR DEVELOPMENT
Now is when the real work begins:
Step 9: Design for the user experience. Before you dive into code, you must design. A User Experience (UX) Designer can
create the interaction architecture of the design elements. A User Interface (UI) Designer for mobile solutions can create
the look and feel of your app. This is a multistep process with its own review stages. The end result is visual direction and
blueprints that inform your engineers of the envisioned final product and how interaction should feel, move and flow.
PHASE 6: BUILD YOUR MOBILE APP WITH AGILE PRACTICES
The strategy is complete, the stage is set, and you have your design. It is now time to build an app!
Step 10: Agile Development. Agile is the preferred approach for mobile development due the importance of
collaboration, transparency, and rapid iteration to adapt to change. These practices of adapting to change are critical to
finding success in the ever-evolving mobile channel.
PHASE 7: TEST YOUR MOBILE APP
Congratulations! You have built an app. Now it’s time to get some of your target users to help you test it.
Step 11: UAT testing. User acceptance testing is a process to discover whether your mobile app works for users. In other
words, put your app in the hands of a few people in your target audience. Once your app has passed the UAT test, you
know that the solution “works”.
Custom Web Portal
Step 12: BETA testing. Make your app available for a beta trial, either through an open solicitation for participants or the
enrollment of previously identified groups. Feedback from beta users will help you determine whether or not the app’s
functions are operating well in a real-world environment.
PHASE 8: LAUNCH –YOU BUILT AN APP!
Your app is complete and ready to submit. Pick a day and key up a formal launch. Congratulations! You have learned how
to build an app!
