Minor project
On
Women Love to herself
A Minor Project Report Submitted to SAGE University, Indore
Towards Partial fulfilment for the award of
Master of Computer Application (MCA) degree
Supervised by
Submitted by
Dr. Sanjay Dubey
Kartikey Upadhyay
(21COA4MCA0237)
Institute of Computer Application
SAGE University, Indore
www.sageuniversity
Sage University, Indore
1
INDEX
S. NO
CONTANTS
PAGE NO.
1
Approval Sheet
1
2
Certificate
4
3
Recommendation
7
4
Acknowledgements
9
5
Candidate Declaration
10
6
Introduction
12
7
Problem Statement/Abstract
13
8
Objectives
15
9
Methodology/ Project Plan
17
10
Software Requirements
18
11
Hardware Requirements
19
12
ER Diagram
22
13
Use Case Diagram / Class Diagram
24
14
Testing
27
15
Limitations
29
16
Future Scope
30
17
Events
32
18
Conclusion
34
Sage University, Indore
2
19
Sage University, Indore
References
35
3
Approval Sheet
The project entitled “WOMEN LOVE HERSELF” submitted by KARTIKEY
UPADHYAY approved as partial fulfilment for the award of the MASTER OF
COMPUTER APPLICATION (MCA) by SAGE University, Indore.
Internal Examiner
Date:
Sage University, Indore
External Examiner
Date:
4
SAGE University, Indore
CERTIFICATE
This is to certify that the project work entitled WOMEN LOVE HERSELF has been
carried out by KARTIKEY UPADHYAY student of MASTERS OF COMPUTER
APPLICATION under our supervision and guidance. They have submitted this project
report towards partial fulfilment for the award of the Master of Computer Application
by SAGE University, Indore.
DR.
DR. LEELADHAR
CHOURASIYA (HOD)
SANJAY
DUBEY
(Supervisor)
DR. PANKAJ DASHORE
(Head of Institute)
Sage University, Indore
5
RECOMMENDATION
The project entitled “WOMEN LOVE HERSELF” submitted by “KARTIKEY
UPADHYAY” is a satisfactory account of the bona fide work done under our supervision
is recommended towards partial fulfilment for the award of the Master of Computer
Application by SAGE University, Indore.
Date:
DR. LEELADHAR
CHOURASIYA (HOD)
Sage University, Indore
DR.
SANJAY
DUBEY
(Supervisor)
6
ACKNOWLEDGEMENTS
First and foremost, we would like to express our thankfulness towards DR. SANJAY
DUBEY of INSTIUTE OF COMPUTER APPLICATION for extending all the facilities
needed to carry out this work, we take pride in saying that we have successfully completed
our Dissertation/ project work under her able guidance. She was a major support to us
throughout projects, being available at odd hours with her ideas, inspiration and
encouragement. It is through her masterful guidance that we have been able to complete
our Dissertation/ project work.
We are also thankful to DR. LEELADHAR CHOURASIYA (HOD), for
giving their guidance throughout the Dissertation/project phase.
We are also thankful to Dr. PANKAJ DASHORE (HOI), SAGE University,
Indore forextending all the facilities needed to carry out this work.
KARTIKEY UPADHYAY
(STUDENT)
Sage University, Indore
7
CANDIDATE DECLARATION
I hereby declare that the work which is being presented in this project report entitled
“WOMEN LOVE HERSELF” in partial fulfilment for the award of Master of
Computer Application is an authentic record of my own work carried out under the
supervision and guidance of DR. SANJAY DUBEY , SAGE University, Indore.
I am fully responsible for the matter embodied in this report and it has not been submitted
elsewhere for the award of any other degree.
Date:
KARTIKEY UPADHYAY
Sage University, Indore
8
INTRODUCTION
A JavaScript web application is in essence an HTML page with JavaScript code and
other resources, such as CSS style-sheets and image files. Program execution is
driven by events in the user’s browser: the page is initially loaded, the user interacts
with the mouse and keyboard, timeouts occur, AJAX response messages are received
from the server, etc. The event handler code reacts by modifying the program state and
the HTML page via its DOM (Document Object Model) and by interacting with the
browser API, for exam-ple to register new event handlers. Compared to other soft-ware
platforms, the state of the art in development of such web applications is rather
primitive, which makes it difficult to write and maintain robust applications.
The goal of our research is to develop static program analysis techniques that can
detect—or show absence of— potential programming errors in JavaScript web applications. We focus on general errors that can be detected with-out the use of applicationspecific code annotations. Exam-ples of such errors are (1) dead or unreachable code,
which often indicates unintended behavior, (2) calls to built-in functions with a wrong
number of arguments or with ar-guments of unexpected types, and (3) uses of the
special JavaScript value undefined (which appears when attempt-ing to read a missing
object property) at dereferences or at function calls. The existence of the undefined
value and im-plicit type coercions in the language means that even minor spelling
errors, for example in a property name, often has surprising consequences at runtime.
With statically typed languages, the type systems provide a strong foundation for
detecting such errors. In contrast, because of the dynamic nature of JavaScript web
application code, our analysis must be capable of reasoning about the flow of control
and data throughout the applications
Sage University, Indore
9
ABSTRACT/ PROBLEM STATEMENT
Developers of JavaScript web applications have little tool support for catching errors
early in development. In com-parison, an abundance of tools exist for statically typed
languages,
including
sophisticated
integrated
development
environments
and
specialized static analyses. Transferring such technologies to the domain of JavaScript
web appli-cations is challenging. In this paper, we discuss the chal-lenges, which
include the dynamic aspects of JavaScript and the complex interactions between
JavaScript, HTML, and the browser
We begin with a brief tour of the technologies involved and explain the central
challenges that exist when develop-ing static analyses for JavaScript web applications.
Expe-rienced JavaScript programmers who are used to reasoning “manually” about the
behavior of their programs will recog-nize the issues brought forth here.
In the earlier time there is no old ways for developing the static landing pages, this is
the problem we are facing before so, here I’m trying to making the static landing page
using new version of HTML5, CSS3 and JS.
With the help of vs code tools for making the coding easier.
Sage University, Indore
10
OBJECTIVES
Enough has been said and discussed the importance of self-love and self-care in
our lives. But it’s very important to discuss these two in the life of a woman.
Women, as we all know, are made by God to be life-givers, nurturers, and
caregivers. They are generally very compassionate, loving and empathetic by
nature. Because of being so loving and caring they often miss to take care of
themselves and feel guilty for sparing even a few minutes for themselves. Why
do we women have this attitude towards ourselves? Why Don’t we realize if we
don’t take care of ourselves, how will we take care of others? In my opinion,
every woman must include self-love and self-care in her dictionary. Let’s find out
some reasons why women underestimate the importance of self-love and selfcare in their lives.
Sage University, Indore
11
HYPOTHESIS
We hypothesize that, for women, being objectified in an interaction by a man
will increase state self-objectification (SSO) within that interaction. (Hypothesis
We hypothesize that people who are high in trait self-objectification (TSO) will
have higher SSO during the interaction than people lower in TSO. (Hypothesis 3)
There will be an interaction of one’s TSO and one’s partner’s objectification,
such that people who are higher in TSO will be even more negatively affected
by their partner’s objectification than those who are lower in TSO. (Hypothesis
4) We hypothesize that SSO will lead to perceiving the interaction as less
comfortable and authentic. (Hypothesis 5) We further hypothesize that higher
perceptions of interaction inauthenticity will lead to reduced cognitive
performance, (Hypothesis 6) reduced career aspirations, and (Hypothesis 7)
reduced anticipated relationship agency.
Sage University, Indore
12
Methodology
The Systems Development Life Cycle (SDLC) provides the foundation for the
processes used to develop an information system. A methodology is a formalized
approach to implementing the SDLC (i.e., it is a list of steps and deliverable). There
are many different systems development methodologies, and they vary in terms of
the progression that is followed through the phases of the SDLC. Some
methodologies are formal standards used by government agencies, while others
have been developed by consulting firms to sell to clients. Many organizations have
their own internal methodologies that have been refined over the years, and they
explain exactly how each phase of the SDLC is to be performed in that company.
Here we will review several of the predominant methodologies that have evolved
over time.
Sage University, Indore
13
Feasibility Study
A feasibility study—sometimes called a feasibility analysis or feasibility report—
is a way to evaluate whether or not a project plan could be successful. A
feasibility study evaluates the practicality of your project plan in order to judge
whether or not you're able to move forward with the project.


 Determine the ability of the present gadget.





Improve the present gadget.

Define the troubles and goals involved.
Avoid the hardware approach.


Apart from this feasibility observe is split into three parts:-


Economic Feasibility


Technical Feasibility

Operational Feasibility
Sage University, Indore



14
FUNCTIONAL REQUIREMENTS


A functional requirement defines a function of the system and its components.
A
function is described as a set of inputs, the behaviour and its outputs. The main
purpose of functional requirements within the requirement specification
document is to define all the activities or operations that take place in the system.
These are derived through interactions with the users of the system.
This
system should allow the users to paste the link.


 This system should allow the users to download the videos





This system will show video format also

This system download the videos other platform too


This system provide functionality direct goes to social sites and copy link
Sage University, Indore
15
NON FUNCTIONAL REQUIREMENTS
In this site given type of non-functional requirements are available:-

Reliability and Availability: - You can use anytime when you want, there is no
 time limit. When you needs download a video and need to watch that, you can


download that time. It's availability all the time.


 Maintenance: - The website in proper condition, care or upkeep is very easy.


Usability: - This site is very easy to use you can easily copy the link and paste

into search box and download the video in your system.





Security: - Security is foremost. This makes your application secure. 
A good
security application is one that hackers cannot hack. By ensuring a safe
environment for your device, paying attention when choosing the source, and
using virus detection software diligently, you can safely download your videos.
You should make sure your browser, operating system, and virus scanner have
the latest security fixes.
Each page load within 2 seconds
Sage University, Indore
16
SOFTWARE REQUIREMENTS


 OS: - Windows 10 Pro






Editor: - VS Code

Terminal: - Command Prompt
Browser:-


• Chrome
• Mozilla Firefox
• Microsoft internet explore




Technology: - Django Framework
Frontend:-


• HTML
• CSS


• JS
Backend:-

• Node.js


 Database:-
• MongoDB
Sage University, Indore
17
HARDWARE REQUIREMENTS




Processor: - Dual Intel core
RAM: - 4 GB
Hard Disk: - 500 GB
Sage University, Indore


18
ER DIAGRAM
Meaning of E-R Diagram-Entity-Relationship Diagram (ERD) is a
data modelling technique that graphically shows the information system entities and
their relationships. ERD is a conceptual and expressive model of the data used to
represent the Entity Framework infrastructure.
Sage University, Indore
19
USE CASE DIAGRAM
Use case diagrams illustrate the high level features and scope of
the system. These figures also show the interaction between the system and its
actors.
Sage University, Indore
20
CLASS DIAGRAM
Sage University, Indore
21
The class diagram containing the active class corresponds to the static process view
of the system
NoSQL databases approach modelling from a different point of view generally.
NoSQL modelling usually begins with asking questions on how the data in the
database is going to be queried, so the main modelling is 'what are the list of
questions that I want to ask of my database', whereas with SQL databases, modelling
usually is a function of what data you have.
Once you have a list of questions, you then need to design a model that will answer
those questions via the NoSQL database. To model it, I typically use Creately which is
an online tool for visually representing models of various kinds.
Another method could be to represent your NoSQL model in JSON format and then
use the wonderful D3.js javascript library to create a data-driven document
Sage University, Indore
22
DATABASE TABLE
Fetching data fromMongoDB Using Node.js and Express --
Sage University, Indore
23
TESTING
A comprehensive landing page testing methodology would look something like the
one below, irrespective of what testing methodology, i.e., A/B, Multivariate, or Split,
is used:

A set of data-driven hypotheses with clear prioritization.

Well-defined and important measurable conversion goals.


Proper testing tools with a variety of testing options.

Calculate the time and traffic required to run the tests.

Create variations of different test elements and document them.

Quality check and deploy tests.

Analyze test results and findings.

Deploy winning variations and discard the losing ones.

Document learnings from the tests





Mature experimentation teams thoroughly analyze their test results across multiple
segments to uncover instances where the losing variation outperforms the winner to
extract more juice out of their testing and increase conversions .
Sage University, Indore
24
LIMITATIONS
5 seconds Rule:
Your Landing page should open within 2-3 seconds. Here you got 5 seconds to
attract the visitors & draw in your consumer. If your landing page does'nt open
immediately your visitor will leave to other pages. Easy to navigate
Bullet Points:
Use Bullets for easy targeting because your online visitors are skimmer and
Scanners. Make it easy to understand your goals & benifits, because people
only look what you are offering.
Images:
As everyone knows Images speaks a lot than Text. Images are the most liked &
shared in Social media sites. Better to use powerful words like Call to action
words in Image so that visitors get attract. Landing page with less or thin
content also
Above the fold:
Place all your call to action or benefits 'above the fold'. Simply make sure that all
your landing page information should be shown in one screen only without
scrolling down.
Sage University, Indore
25
Craft a Perfect CTA:
Crafting an attractive Call to action to your landing page is the main advantage
to get the lead or Impression. Many of the marketers will not give the Call to
actions more than a few minutes because it does'nt matters how rest your
landing page is.
Mobile Friendly:
Mobile Ads are so effective so better to make your Landing page mobile
friendly because they appear to customers like to buy something right now.
The only target is to making the users journey as easy as possible.
Sage University, Indore
26
FUTURE SCOPE
A UI is easy attracted by the user Now we have a lot of tools and
technology. We can develop the best using React.js .There are so many
new features has been developed but now still there is a competition of
best UI.
Sage University, Indore
27
EVENTS
As discussed in Section 2.2, the analysis must be extended to model dynamic
registration, triggering, and removal of event handlers. This can be done with
various levels of pre-cision. We describe our choices in the following and evaluate
the resulting system in Section 5.
First, we extend TAJS’s abstract states again, this time with a collection of set of
references to abstract objects that model the event handler function objects. To
distin-guish between different kinds of events and event objects, we maintain one
such set for each of the following categories of events: load, mouse, keyboard,
timeout, ajax, and other. Ob-ject references are added to these sets either statically,
due to presence of event attributes (onload, onclick, etc.) in the HTML page,
Sage University, Indore
28
CONCLUCION
We have presented the first static analysis that is capable of reasoning precisely
about the control flow and dataflow in JavaScript applications that run in a browser
environment. The analysis has been implemented as an extension of the TAJS tool
and models both the DOM model of the HTML page and browser API. This includes
the HTML element object hierarchy and the event-driven execution model. In the
process we have identified the key areas where modeling the browser is important
for precision and challenging for static analysis.
Our experimental evaluation of the performance of the analysis indicates that (1)
the analysis is able to show ab-sence of common programming errors in the
benchmark pro-grams, (2) the analysis can help detecting potential errors, such as
misspelled property names, (3) the computed call graphs are precise as most call
sites are shown to be monomor-phic, (4) the computed types are precise as many
expressions are shown to have unique types, and (5) the analysis is able to identify
dead code and unreachable functions. Such in-formation can give a foundation for
providing better tool support for JavaScript web application developers.
Sage University, Indore
29
REFERENCE
[1] C. Anderson, P. Giannini, and S. Drossopoulou. Towards type inference for
JavaScript. In Proc. 19th European Conference on Object-Oriented
Programming, ECOOP ’05, volume 3586 of LNCS. Springer-Verlag, July 2005.
[2] G. Balakrishnan and T. W. Reps. Recency-abstraction for heap-allocated
storage. In Proc. 13th International Static Analysis Symposium, SAS ’06, volume
4134 of
LNCS. Springer-Verlag, August 2006.
[3] R. Chugh, J. A. Meister, R. Jhala, and S. Lerner. Staged information flow for
JavaScript. In Proc. ACM SIGPLAN Conference on Programming Language Design
and Implementation, PLDI ’09, June 2009.
[4] ECMA. ECMAScript Language Specification, 3rd edition. ECMA-262.
[5] S. Fink and J. Dolby. WALA – The T.J. Watson Libraries for Analysis.
http://wala.sourceforge.net/.
[6] S. Guarnieri and B. Livshits. Gulfstream: Staged static analysis for streaming
JavaScript applications. In Proc. USENIX Conference on Web Application
Development, WebApps ’10, June 2010.
[7] S. Guarnieri and V. B. Livshits. Gatekeeper: Mostly static enforcement of
security and reliability policies for JavaScript code. In Proc. 18th USENIX
Security Symposium, Security ’09, August 2009.
[8] A. Guha, S. Krishnamurthi, and T. Jim. Using static analysis for Ajax intrusion
detection. In Proc. 18th International Conference on World Wide Web, WWW
’09, May 2009.
[9] A. Guha, C. Saftoiu, and S. Krishnamurthi. Typing local control and state using
flow analysis. In Proc. Programming Languages and Systems, 20th European
Symposium on Programming, ESOP ’11, LNCS. Springer-Verlag, March/April
2011.
[10] D. Jang and K.-M. Choe. Points-to analysis for JavaScript. In Proc. 24th Annual
ACM Symposium on
Sage University, Indore
30
Sage University, Indore
31