PRATHMESH JOSHI [RA2011050010082]

PRATHMESH JOSHI (RA2011050010082)

 Project Management Plan
Focus Area Details
Integration Management
Governance Framework
Project Team Structure
Roles & Responsibilities of Team
Change Management
(Change Control, Issue Management)
Project Closure

Scope Management
Scope Statement
Requirement Management (Gathering, Control, Assumption,
Constraint Stakeholder)
Define Deliverable
Requirement Change Control
Activities and Sub-Tasks

Schedule Management
Define Milestones
Schedule Control
Cost Management
Estimate Effort
Assign Team
Budget Control
Quality Management
Quality Assurance: Quality assurance will be managed
including governance, roles and responsibilities, tools and
techniques and reporting
Quality Control: Specify the mechanisms to be used to measure
and control the quality of the work products
Resource Management
Estimate and Manage the need
People: People & Skills Required
Finance: Budget Required
Physical: Facilities, IT Infrastructure
Stakeholder Identifying, Analyzing, Engaging Stakeholders

Communication Management
Determine communication requirements, roles and
responsibilities, tools and techniques. [Type of Communication,
Schedule, Mechanism Recipient]
Risk Management Identifying, analysing, and prioritizing project risks

Procurement Management Adhering to organization procurement process

Estimation

Project Team Formation

Identification Team members
Name Role Responsibilities
Prathmesh Joshi Key Business User (Product Provide clear business and user
Owner) requirements
Rohit Goyal Project Manager Manage the project
Rohit Goyal Business Analyst Discuss and Document Requirements
Prathmesh Joshi Technical Lead Design the end-to-end architecture
Prince Dalal UX Designer Design the user experience
Prathmesh Joshi Frontend Developer Develop user interface
Prince Dalal Backend Developer Design, Develop and Unit Test
Services/API/DB
Rohit Goyal Cloud Architect Design the cost effective, highly available
and scalable architecture
Prince Dalal Cloud Operations Provision required Services
All Tester Define Test Cases and Perform Testing

Responsibility Assignment Matrix

RACI Matrix Team Members
Activity Name (BA) Name (Developer) Name (Project Key
Manager) Business
User
User Requirement A C/I I R
Documentation
Rohit Goyal Prince Dalal Prathmesh Joshi Rohit Goyal Rohit Goyal
A Accountable
R Responsible
C Consult
I Inform
Timeline Giant Chart
 RISK TABLE- SWOT

1. Faster response time 1. Change in requirements 1. Information at hand 1. Regular crash reporting
2. Simple UI 2. Multiple resouces 2. Vast educational resource
3. Easily accessible technology.
 Work Breakdown Structure:
A work-breakdown structure in project management and systems engineering is
a deliverable-oriented breakdown of a project into smaller components. A work
breakdown structure is a key project deliverable that organizes the team's work
into manageable sections. It singlehandedly integrates scope, cost, and schedule
baselines ensuring that project plans are in alignment. The primary purpose of
the WBS is to plan the schedule for the project. Each task duration is planned in
conjunction with its required predecessors and following tasks. The WBS then
provides an overall plan so that the project manager can see how the project
should progress and manage the workflow appropriately.

Literature
House

NEW USER EXISTING USER

Setting the preferences

of study material
Submission of login form

Giving assignments
to check regular
Attending regular lectures progress
SYSTEM ARCHITECTURE

USE CASE DIAGRAM

CLASS DIAGRAM
ENTITY- RELATIONSHIP DIAGRAM

ER Diagram is known as Entity-Relationship Diagram, it is used to

analyze to the structure of the Database. It shows relationships
between entities and their attributes. An ER Model provides a means
of communication.

This Library ER diagram illustrates key information about the

Library, including entities such as video lectures, readers, books,
publishers, reports, and authentication system. It allows for
understanding the relationships between entities.
DATA FLOW DIAGRAM

Data Flow Diagram (DFD) depicts the flow of information and the
transformation applied when a data moves in and out from a system. The
overall system is represented and described using input, processing and
output in the DFD.

LEVEL 0

Literature House
INFORMATION
Account Details
SYSTE M
Preferences

Payments from Customers

s verify
account
CUSTOMER BANK
Rate the site Payment Receipt

Show the desired info

Transaction Receipt
LEVEL 1
ONETAP

The overall processing unit will contain the following output that a system
will produce or generate:
• Book will be the output as the book demanded by the student will
be given to them.
• Information of demanded book should be displayed by the library
information system that can be used by the student while selecting
the book which makes it easier for the student.
SEQUENCE AND COLLABORATION DIAGRAM
The sequence diagram represents the UML, which is used to
visualize the sequence of calls in a system that is used to perform
a specific functionality.

The collaboration diagram also comes under the UML

representation which is used to visualize the organization of the
objects and their interaction.

Sequence Diagram
Collaboration Diagram
TESTING
Scope of Testing
The scope of a test defines what areas of a customer's product are
supposed to get tested, what functionalities to focus on, what bug
types the customer is interested in, and what areas or features should
not be tested by any means.
If something is in scope, please test it; if something is out of scope, it
should not be tested. Understanding the scope of a test is crucial to be
a successful tester on our platform.

Scope of testing may vary by

Test environment
First things first – The URL given in the Access section at the top of
the test overview page defines what website or app should be tested.
Any other websites or apps are not under test (unless stated differently
in the test description)
Each test contains at least one of what we call features. A feature can
describe an area of a product, e.g. a landing page, product overview
page or product detail page of a webshop, it can describe a process
like the checkout process of a website or an app, or it can even be a
particular functionality that should be tested.

Major objective for software testing are:

1.To prevent errors
2.To make sure that end result meet the user requirement
3.Finding the defects that may be created by programmer during
developing process
4. To maintain the quality of the product.
5. To verify requirements
Testing methodologies
The goal of utilizing numerous testing methodologies in your
development process is to make sure your software can successfully
operate in multiple environments and across different platforms.
These can typically be broken down between functional and non-
functional testing. Functional testing involves testing the application
against the business requirements.

Functional

• Unit testing
• Integration testing
• System testing
• Acceptance testing
Non-functional testing methods incorporate all test types focused on
the operational aspects of a piece of software. These include:

• Performance testing
• Security testing
• Usability testing
• Compatibility testing

Tools required
• Test management tool.
• Bug tracking tool.
• Automated testing tool.
• Performance testing tool.
• Cross-browser testing tool.
• Integration testing tool.
• Unit testing tool.
 TEST CASES
Functional Test Cases
Test Test Test Case Execution Expected Actual Status Remarks
ID Scenario Steps Outcome Outcome
(#)
Verify that Accept 1. User User pass Pass / success
valid name Valid clicks on should be Failure
and password name and login taken to
are entered or password button the main
not 2. Enter the interface
name and of the
password website
on the text
box
3. Click
login
button

Verify User Don’t

Registration Accept
from India invalid
entries

Non-Functional Test Cases

Test Test Test Execution Expected Actual Status Remarks

ID Scenario Case Steps Outcome Outcome
(#)
Performance If time is User Pass pass successful success
testing: less than enters
application 5 sec per his/her
load time 1000 user credentials
testing Time to
If time is load
more website is
than 5sec less than 5
sec

failure
Re enter
the
credentials
REPORT:

Testing Input Description Result/current status

Login and Sign up Specified ids Pass

Load up Time Website on Local Testing website with Pass
opening and host
performing
simultaneously on
system
Database Test Test cases Implementing test and Pass
verifying
output
Attributes used Filling form By filling the Pass
registration form in
sign up page

Hurdles are the part of the every process it gives us opportunity to improve and be more
perfect

Present obstacles are how to make page more user friendly and efficient so that user can get
best experience to achieve this currently we are working

1.How to reduce the load up time of the website

2. maintaining the privacy of the user is our highest priority so we are currently working how
to keep user data safe and secure

3. we are facing some difficulty to manage the payment gateway.

4. there is some issue in incorporating certain courses videos on our website

We are working on the hurdles and very soon with the joint efforts of our team and support
form stakeholders we will overcome them.

Category Progress Against Plan Status

Functional Testing
Interface testing green completed
Database server amber inprogress
Non-Functional Testing
Crowd testing amber Inprogress
Browser compatiblity green Completed
Security testing red Inprogress
Interface testing- Three areas here are-Application, Web and Database Server Application
Test requests are sent correctly the Database and output at the client side is displayed
correctly. if any must be caught by application and must be only shown to the administrator
and not the end Web Server: Test Web server is handing all application requests without any
service denial.

Database Server: Make sure queries sent to the database give expected results. Test system
response when connection between the three lap Application, Web and Database) cannot be
shed and agent

Crowd Testing: You will select a large number of people (crowd) to execute tests which
other-wise would have been executed a select group of people in the company. Crowd
sourced testing is an interesting and upcoming concept and helps unravel many a unnoticed
defects

Security testing: Security Testing is vital for e-commerce website that store sensitive customer
in formation like credit cards. Testing Activities will include Test unauthorized access to
secure pages should not be permitted.

Functional Test Case Coverage Status

(%)
Server/ database 60% In progress
(Backend)
Frontend(UI/UX) 90% Completed
IMPLEMENTATION, PROGRAM & DESIGN
Screen shorts
CONCLUSION

Website development process

To over come these issues we have developed this website. The development
process for this website is characterized by the efforts made by whole team and It
also requires lots hardware and software infrastructures. The hardware may include
PC with core i7 processor, 16 GB RAM and Graph – IC Card at least MX150, and
software like HTML,CSS ,JAVASCRIPT Etc.
The integration effort Comprises not only the design and realization of interfaces,
but also test of those interfaces. The more complex the subsystem are, the more-
effort is required for the interface test since the necessary test drivers stubs should
be equally complex.

REFERENCES

https://www.wikipedia.org/wiki/main_page
htps://openlibrary.com
https://www.reactjs.org/tutorial
https://www.youtube.com