MLM PDF

I
Mini Project Report On

MULTI-LEVEL MARKETING
Institute of Computer Science & Technology, Code 107

Affiliated to Dr. A.P.J. Abdul Kalam Technical University,Lucknow
SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF
Master of Computer Application
BY
NEETESH KUMAR SINGH, 1810714905
Under the supervision of

Mr. Vivek Gupta, HOD
TO THE
Dr. A. P. J. Abdul Kalam Technical University, Lucknow
Institute Of Computer Science & Technology, College Code 107

June 2019
I
DECLARATION
I hereby declare that this project report entitled “Multi-Level Marketing” being submitted by
us to the Dr.A.P.J. Abdul Kalam Tchnical University, Lucknow for the award of the degree of
Master of Computer Application is a record of bonafied work carried by me. We worked under
the guidance and Supervision of Mr. Vivek Gupta, Head of Department, CS, ICST,
Varanasi.
The matter embodied in this report has not been submitted to any other university or institute
earlier for the award of any degree or diploma.
Neetesh Kumar Singh Gaurav Pandey
MCA 4th (Sem) MCA 4th (Sem)
(1810714905) (1810714902)
I
ABSTRACT
This document is meant for the describing all the features and procedures that were followed
while developing the system
This document specially mentions the details of the project how it was developed, The primary
requirement, as well as various features and functionalities of the project and the procedures
followed in achieving these objectives.
Multi level marketing, or MLM, is a form of direct sales home business in which independent
representatives sell products or services from a company to an end consumer. The multi-level
aspect refers to each representative's ability to recruit and train other representatives to start their
own business, and earn a commission on their reps' sales.
Income earned in MLM comes from the commission earned on personal sales, as well as a
percentage of the sales earned by other reps recruited by you.
II
ACKNOWLEDGEMENTS
Acknowledgements, truly is an act of sincere thanks giving and indebtedness to them who have
guided and helped in the preparation process of a project as the present one. I take this
opportunity to thank all those who have had a key role in the success of this project. They have
inspired, mentored, directed and seen the project through to its completion.Firstly I would like to
acknowledge Prof. K.P. Pandey (Director, SHEPA) who has provided us enough support and
good environment while making the proxpress heartfelt gratitude to Dr. Anupam Shukla
(Director, ICST) and again humble thanks to Mr. Vivek gupta (H.O.D, Computer Science)
took great pain in going through the entire process and made valuable comments and suggestions
with constant encouragement.
We would like special thanks to our coordinator Mr. Vivek Gupta who provided us with
sample ideas when we got stuck during the project. He also helped us to collect all the relevant
information. We can’t forget to thank to sir who were very helpful to us directly or indirectly
during development of this project.
Last but not the least I would like to thank my parents for their moral support and encouragement
and my friends whose valuable co-operation gave me vast knowledge in computer application.
I am also thankful to all my faculty members, and the people who are directly or indirectly
related to my Project and helped me out for completing my work successfully.
NEETESH KUMAR SINGH
MCA 4TH SEM
ROLL NO.1810714905
PLACE: VARANASI
III
TABLE OF CONTENT
 Introduction
 Topic
 Objective
 Scope
 System Analysis
 Identification of need
 Preliminary Investigation
 Feasibility Study
 Technical feasibility
 Operational feasibility
 Analysis & Designing
 DFD (0-level, 1-level, 2-level)
 E-R diagram
 Table structure
 S/w & H/w requirement specification
 System design Screenshots
 System Coding
 Future Scope of the project
 Conclusion
 References
IV
List of Tables
Table no. Table caption Page no.
1 ACTOR’S GOAL TABLE 15
2 MLM STRUCTURE 30
2 FEEDBACK RECORD TABLE 31
3 NEWS TABLE 32
4 DISTRIBUTER RECORD TABLE 33
5 DOWNLINE TABLE 34
6 AUTHENTICATION TABLE STRUCTURE 35
V
List of Figures
Fig. NO. Figure caption Page No.
1. CASE DIAGRAM OF DISTRIBUTER 13
2. CASE DIAGRAM OF SUPPLIER 14
3. DATA FLOW 17
4. PROCESS 17
5. EXTERNAL ENTITY/ACTOR 18
6. DATA STORE 18
7. 0-LEVEL DFD 20
8. 1-LEVEL DFD 21
9. 2-LEVEL DFD (for Distributer) 22
10. 2-LEVEL DFD (for Supplier) 23
11. STRONG ENTITY SET 24
12. ATTRIBUTES 25
13. KEY ATTRIBUTES 25
14. COMPOSITE ATTRIBUTES 25
15. MULTIVALUED ATTRIBUTES 25
16. RELATIONSHIP 26
17. LINKS 26
18. ONE TO ONE RELATIONSHIP 27
19. ONE TO MANY RELATIONSHIP 27
20. ONE TO MANY RELATIONSHIP 28
21. MANY TO MANY RELATIONSHIP 28
22. ENTITY RELATIONSHIP DIAGRAM 29
VI
List of Abbreviations
HTML HYPERTEXT MARKUP LANGUAGE

AOL AMERICA ONLINE
DBMS DATABASE MANAGEMENT SYSTEM
DBASE DATA BASE
IMS INFORMATION MANAGEMENT SYSTEM
SQL SERVER STRUCTURED QUERY LANGUAGE
RAD RANDOM ACCESS DEVICE
RAM RANDOM ACCESS MEMORY
HDD HARD DISK DRIVE
PIV PENTIUM-4
GHZ GIGAHERTZ
IIS INTERNET INFORMATION SERVICES
WYSIWYG WHAT YOU SEE IS WHAT YOU GET
VBSCRIPT VISUAL BASIC SCRIPT
J SCRIPT JAVA SCRIPT
UML UNIFIEDMODELING LANGUAGE
XML EXTENSIBLE MARKUP LANGUAGE
SMTP SIMPLE MAIL TRANSFER PROTOCOL
COM COMPONENT OBJECT MODE
XSD XML SCHEMA DEFINITION
DLL DYNAMIC LINK LIBRARY
T-SQL TRANSACT-SQL
XQUERY XML QUERY LANGUAGE
TDS TABULAR DATA STREAM
SOAP SIMPLE OBJECT ACCESS PROTOCOL
CLR COMMON LANGUAGE RUNTIME
CTES COMMON TABLE EXPRESSIONS
SQL CLR STRUCTURED QUERY LANGUAGE
MARS MULTIPLE ACTIVE RESULTS SET
DMVS DYNAMIC MANAGEMENT VIEWS
VII
IT INFORMATION TECHNOLOGY
SGML STANDARD GENERALIZE MARKUP LANGUAGE
OLEDB ORACLE DATA BASE
SQLCONNECTION STRUCTURE QUERY LANGUAGE CONNECTION
OLEDBCONNECTION ORACLE DATA BASE CONNECTION
ADO ACTIVE DATA OBJECTS
ROM READ ONLY MEMORY
DFD DATA FLOW DIAGRAM
ERD ENTITY RELATIONSHIP DIAGRAM
GUI GRAPHICAL USER INTERFACE
WWW WORLD WIDE WEB
.APK FILE ANDROID APPLICATION PACKAGE FILE
.DEX FILE DALVIK EXECUTABLE FILE
DDMS DALVIC DEBUG MONITOR SERVICE
AJP APACHE JSERVER PROTOCOL
ANSI AMERICAN NATIONAL STANDARDS INSTITUTE
API APPLICATION PROGRAMMING INTERFACE
BC BEFORE CHRIST
VIII
INTRODUCTION
1
INTRODUCTION
Topic of the project:

Multi level marketing, or MLM, is a form of direct sales home business in which independent
representatives sell products or services from a company to an end consumer. The multi-level
aspect refers to each representative's ability to recruit and train other representatives to start their
own business, and earn a commission on their reps' sales.
Income earned in MLM comes from the commission earned on personal sales, as well as a
percentage of the sales earned by other reps recruited by you.
MLM Terms to Know:
Sponsor: The sponsor is the representative who directly recruits another person into the
business. For example, MLM member A recruits member B into the business. Member A is the
sponsor and is responsible for training member B.
Recruit: A recruit may also be referred to a team member. It's a person brought into the business
by a sponsor as a new member. Recruits are trained by their sponsor or "upline" (see below)
representatives.
Downline: Your downline contains the recruits brought in below you. This can include members
you've recruited as well as those your recruits have brought into the business.
Upline: The upline consists of the representative sponsors who came in before you. For example,
if rep A recruited rep B, who recruited rep C, who recruited you, your upline is C, B, and A.
Network Marketing: Multi-level marketing is sometimes referred to as network marketing as

well.
2
SYSTEM
ANALYSIS:
IDENTIFICATION
OF NEED
3
Overgrown Smartphone usage of general public enforces MLM companies to shift perspective
towards MLM Mobile apps. Technology-driven development in the behavior of customers and
prospects foster to make efforts to improve user experience, reliability, and reputation through
MLM software mobile apps. MLM Mobile application allows the users to manage their profile
through mobile or tablet and provides updated information on commission and compensations
and thereby, consequently subdue the burden of using desktop computers throughout the time to
an optimum level. Back in years, we also took part in these advancements through pioneering the
first ever mobile MLM application for MLM business, INFINITE MLM MOBILE APP. From
the inception, our mobile app favors all MLM Companies that focus on expanding their user
experience to Mobile and Tablets platforms. Through these years, Inspirations from the success
and learnings from the failures endeavor us to develop more and more reliable MLM apps, with
the most advanced MLM features on all Smartphone platform that no one can match.
Need of MLM Mobile Apps in Network Marketing Business
Many business models that can be benefited greatly from customized MLM mobile apps that
function as recruiting, product sales, marketing and communication tools. Any ability to improve
communication among sales teams, communicate with your down-line brand representatives and
gamify sales goals through bonuses and special achievement awards are one such way multi-
level marketing mobile apps can help a network marketing business.
Empowering your MLM Business with Infinite MLM Apps
Infinite MLM mobile app is an add-on provided along the Infinite MLM Software to aid
network-marketing companies to outperform its own metrics and empower distributors to run
their business like pros from a Tablet or Smartphone with exceeding simplicity and convenience.
With our MLM Apps, customers can check their incentives, payments, downlines, e-wallet
statements and even register new members.
4
Our MLM apps are the perfect companion for an MLM Business. Multi-level marketing mobile
app favors all MLM Companies that aim at expanding their user experience also to Mobile and
Tablets platforms. The inception of MLM iPhone app has provided impeccable power to
Network marketing business. Both MLM android app & MLM iPhone apps we build are always
scalable and gives a higher level of business for all clients.
Main features in our MLM software Mobile Application
Login: For logging the user using their Distributer ID and Password.
Dashboard: To display the summary of your business including customer details, joining
information, payment details and more options
Funds: Details about various funds such as car fund, house fund & Travel fund.
Bonus: Bonus and new joining information details.
Feedback: To compose, send and read Feedbacks.
Add Member: Allow adding new users to the Downline & generating their Distributer ID.
Points: Shows sales report Points.
Profiles: Shows the user information.
Downline: Shows the distributers joined below the user.
Notification: Shows the Notifications sent to the user from the supplier.
News: Shows the recent news published for all distributers by the Supplier.
Contact: Shows the Contact Details Of the head office.
5
Vouchers: Shows the gained Vouchers On Purchasing.
Company: To explain About & Management informations of the company.
Purchase: Gives the facility to order products online.
Objectives of MLM App
 To Make the Business Digital.

 To help Suppliers as well as the distributers to manage the downline distributers.
 To distribute the bonus information online.
 To make adding new distributers process sophisticated.
 To easily generate the funds of the distributers.
6
FEASIBILITY
STUDY
7
PROBLEM DESCRIPTION & LIMITATION
 The system on which the software will be designed must contains atleast 4 GB RAM to run
the software Android Studio.
 The users cannot change the theme of the application.
 Difficult manage users on a single platform.
 Difficult to add online payment gateways.
8
ANALYSIS
&
DESIGNING
9
CASE DIAGRAM
To model a system, the most important aspect is to capture the dynamic behaviour. Dynamic
behavior means the behavior of the system when it is running / operating.
Only static behavior is not sufficient to model a system rather dynamic behavior is more
important than static behavior. In UML, there are five diagrams available to model the dynamic
nature and use case diagram is one of them. Now as we have to discuss that the use case
diagram is dynamic in nature, there should be some internal or external factors for making the
interaction.
These internal and external agents are known as actors. Use case diagrams consists of actors,
use cases and their relationships. The diagram is used to model the system/subsystem of an
application. A single use case diagram captures a particular functionality of a system.
Hence to model the entire system, a number of use case diagrams are used.
Purpose of Use Case Diagrams
The purpose of use case diagram is to capture the dynamic aspect of a system. However, this
definition is too generic to describe the purpose, as other four diagrams (activity, sequence,
collaboration, and State chart) also have the same purpose. We will look into some specific
purpose, which will distinguish it from other four diagrams.
Use case diagrams are used to gather the requirements of a system including internal and
external influences. These requirements are mostly design requirements. Hence, when a system
is analyzed to gather its functionalities, use cases are prepared and actors are identified.
When the initial task is complete, use case diagrams are modelled to present the outside view.
In brief, the purposes of use case diagrams can be said to be as follows −
 Used to gather the requirements of a system.
 Used to get an outside view of a system.
 Identify the external and internal factors influencing the system.
 Show the interaction among the requirements are actors.

10
Use case diagrams are considered for high level requirement analysis of a system. When the
requirements of a system are analyzed, the functionalities are captured in use cases.
We can say that use cases are nothing but the system functionalities written in an organized
manner. The second thing which is relevant to use cases are the actors. Actors can be defined as
something that interacts with the system.
Actors can be a human user, some internal applications, or may be some external applications.
When we are planning to draw a use case diagram, we should have the following items
identified.
 Functionalities to be represented as use case
 Actors
 Relationships among the use cases and actors.
Use case diagrams are drawn to capture the functional requirements of a system. After
identifying the above items, we have to use the following guidelines to draw an efficient use
case diagram
 The name of a use case is very important. The name should be chosen in such a way so
that it can identify the functionalities performed.
 Give a suitable name for actors.
 Show relationships and dependencies clearly in the diagram.
 Do not try to include all types of relationships, as the main purpose of the diagram is to
identify the requirements.
 Use notes whenever required to clarify some important points.
11
LOGIN
ADDING
DISTRIBUTER
VIEW BUSINESS
POINTS
VIEW INCOME
ORDER FOR
DISTRIBUTER PURCHASE
FEEDBACK
12
LOGIN
MANAGE USER
MANAGE
PRODUCTS
GENERATE ORDER
RECEIPTS
SEND FEEDBACK
RESPONSE
SUPPLIER
UPLOAD NEWS &
ORDERS
VIEW
FEEDBACK
13
ACTOR’S GOAL TABLE
Actors Actor goal table Use case Name
Supplier Manage Distributers User
Supplier Add Products Products
Supplier Posts news News
Supplier Reply Feedback Feedback
Distributer Add new Supplier Downline
Distributer Order Products Purchase
Distributer Read news News
Distributer Send Feedback Feedback
Table: 1
14
DATA FLOW DIAGRAM (DFD)
A data flow diagram (DFD) is a graphical representation of the "flow" of data through
an information system, modelling its process aspects.
Data flow diagram is graphical representation of flow of data in an information system. It is

capable of depicting incoming data flow, outgoing data flow and stored data. The DFD does not
mention anything about how data flows through the system.
There is a prominent difference between DFD and Flowchart. The flowchart depicts flow of
control in program modules. DFDs depict flow of data in the system at various levels. DFD
does not contain any control or branch elements.
A DFD is often used as a preliminary step to create an overview of the system without going
into great detail, which can later be elaborated. DFDs can also be used for
the visualization of data processing (structured design).
The four main parts of the DFD’s are-
 Processes,
 Data Flows,
 Actors, and
 Data Stores
The other parts of the DFD’s are-
 Constraints &
 Control Flows
15
Elements of the DFD
Processes
A process is a business activity or function where the manipulation and transformation of data
takes place. A process can be decomposed to finer level of details, for representing how data is
being processed within the process.
Processes are computational activities that transform data values. A whole system canbe
visualized as a high level process.
Representation in DFD- A process is represented as an ellipse with name written inside.
OR
Data Flows
Data flow represents the flow of data between two Processes. It could be between an actor and a
Process, or between a data store and a process. A data flow represents the flow of information,
with its direction represented by an arrow head that shows at the end(s) of flow connector.
Representation in DFD- A data flow is represented by a directed arc or an arrow, lebelled

with the name of the data item that it carries.
16
Actors
An external entity or an actor can represent a human, system or subsystem. It is where certain
data comes from or goes to. It is external to the system we study, in terms of the business
process. For this reason, people used to draw external entities on the edge of a diagram.
Representation in DFD- An actor is represented by a Rectangle.
Data Stores
A data store represents the storage of persistent data required and/or produced by the process.
Here are some examples of data stores: membership forms, database table, etc. They are use to
store and retrieve the stored data.
Abc or Abc
Representation in DFD- Data stores are represented by two parallel lines containing the name
of the stored data. Each data store is connected to atleast one process. Input arrow shows the
content to modify the data store while the output arrow represents the information retrieved
from the data store.
17
Levels of DFD
 Level 0 - Highest abstraction level DFD is known as Level 0 DFD, which depicts the
entire information system as one diagram concealing all the underlying details. Level 0
DFDs are also known as context level DFDs.
 Level 1 - The Level 0 DFD is broken down into more specific, Level 1 DFD. Level 1
DFD depicts basic modules in the system and flow of data among various modules. Level
1 DFD also mentions basic processes and sources of information.
 Level 2 - At this level, DFD shows how data flows inside the modules mentioned in
Level 1.
Higher level DFDs can be transformed into more specific lower level DFDs with deeper
level of understanding unless the desired level of specification is achieved.
18
19
20
21
22
E-R Diagram
The ER model defines the conceptual view of a database. It works around real-world entities
and the associations among them. At view level, the ER model is considered a good option for
designing databases.
Entity
An entity can be a real-world object, either animate or inanimate, that can be easily identifiable.
For example, in a school database, students, teachers, classes, and courses offered can be
considered as entities. All these entities have some attributes or properties that give them their
identity.
An entity set is a collection of similar types of entities. An entity set may contain entities with
attribute sharing similar values. For example, a Students set may contain all the students of a
school; likewise a Teachers set may contain all the teachers of a school from all faculties. Entity
sets need not be disjoint.
Attributes
Entities are represented by means of their properties, called attributes. All attributes have
values. For example, a student entity may have name, class, and age as attributes.
There exists a domain or range of values that can be assigned to attributes. For example, a
student's name cannot be a numeric value. It has to be alphabetic. A student's age cannot be
negative, etc.
23
Types of Attributes
 Simple attribute − Simple attributes are atomic values, which cannot be divided further.
For example, a student's phone number is an atomic value of 10 digits.
 Composite attribute − Composite attributes are made of more than one simple attribute.
For example, a student's complete name may have first_name and last_name.
 Derived attribute − Derived attributes are the attributes that do not exist in the physical
database, but their values are derived from other attributes present in the database. For
example, average_salary in a department should not be saved directly in the database,
instead it can be derived. For another example, age can be derived from data_of_birth.
 Single-value attribute − Single-value attributes contain single value. For example −

Social_Security_Number.
 Multi-value attribute − Multi-value attributes may contain more than one values. For
example, a person can have more than one phone number, email_address, etc.
These attribute types can come together in a way like −
 simple single-valued attributes
 simple multi-valued attributes
 composite single-valued attributes
 composite multi-valued attributes
Entity-Set and Keys

Key is an attribute or collection of attributes that uniquely identifies an entity among entity set.
For example, the roll_number of a student makes him/her identifiable among students.
 Super Key − A set of attributes (one or more) that collectively identifies an entity in an
entity set.
24
 Candidate Key − A minimal super key is called a candidate key. An entity set may have
more than one candidate key.
 Primary Key − A primary key is one of the candidate keys chosen by the database
designer to uniquely identify the entity set.
Relationship
The association among entities is called a relationship. For example, an employee works_at a
department, a student enrolls in a course. Here, Works_at and Enrolls are called relationships.
Relationship Set
A set of relationships of similar type is called a relationship set. Like entities, a relationship too
can have attributes. These attributes are called descriptive attributes.
Degree of Relationship
The number of participating entities in a relationship defines the degree of the relationship.
 Binary = degree 2
 Ternary = degree 3
 n-ary = degree
Mapping Cardinalities
Cardinality defines the number of entities in one entity set, which can be associated with the
number of entities of other set via relationship set.
25
 One-to-one − One entity from entity set A can be associated with at most one entity of
entity set B and vice versa.
 One-to-many − One entity from entity set A can be associated with more than one
entities of entity set B however an entity from entity set B, can be associated with at
most one entity.
26
 Many-to-one − More than one entities from entity set A can be associated with at most
one entity of entity set B, however an entity from entity set B can be associated with
more than one entity from entity set A.
 Many-to-many − One entity from A can be associated with more than one entity from
B and vice versa.
27
28
29
30
31
32
33
34
Software
&
Hardware
Requirements
35
SOFTWARE & HARDWARE REQUIREMENTS
Front End: Android & XML

Back End: JAVA & Firebase
Software Requirements
For developing...
IDE: Android Studio 3.0
Operating System: Windows 10( 64-bit)
Database: Firebase (Realtime Database)
Server: Firebase own server
For running...
Operating System : Android (Kitkat or above)
Hardware requirements
For Developing...
Laptop / Desktop
Processor: Intel dual core or above
Memory...
RAM: 4 GB minimum
Hard disk: 80 GB minimum
36
For Running...
Mobile Phone
Memory...
Ram: 512 MB minimum
37
Software & hardware Descriptions
Android
Android is a software package and linux based operating system for mobile devices such as
tablet computers and smartphones.
It is developed by Google and later the OHA (Open Handset Alliance). Java language is mainly
used to write the android code even though other languages can be used.
The goal of android project is to create a successful real-world product that improves the mobile
experience for end users.
Android is an open source and Linux-based operating system for mobile devices such as
smartphones and tablet computers. Android was developed by the Open Handset Alliance, led
by Google, and other companies. This tutorial will teach you basic Android programming and
will also take you through some advance concepts related to Android application development.
Android was developed by the Open Handset Alliance, led by Google, and other companies.
Android offers a unified approach to application development for mobile devices which means
developers need only develop for Android, and their applications should be able to run on
different devices powered by Android.
The first beta version of the Android Software Development Kit (SDK) was released by Google
in 2007 where as the first commercial version, Android 1.0, was released in September 2008.
On June 27, 2012, at the Google I/O conference, Google announced the next Android version,
4.1 Jelly Bean. Jelly Bean is an incremental update, with the primary aim of improving the user
interface, both in terms of functionality and performance.
The source code for Android is available under free and open source software licenses. Google
publishes most of the code under the Apache License version 2.0 and the rest, Linux kernel
changes, under the GNU General Public License version 2.
38
Features of Android
Android is a powerful operating system competing with Apple 4GS and supports great features.
Few of them are listed below –
Feature & Description
Beautiful UI
Android OS basic screen provides a beautiful and intuitive user interface.
Connectivity
GSM/EDGE, IDEN, CDMA, EV-DO, UMTS, Bluetooth, Wi-Fi, LTE, NFC and WiMAX.
Storage
SQLite, a lightweight relational database, is used for data storage purposes.
Media support
H.263, H.264, MPEG-4 SP, AMR, AMR-WB, AAC, HE-AAC, AAC 5.1, MP3, MIDI, Ogg
Vorbis, WAV, JPEG, PNG, GIF, and BMP.
Messaging
SMS and MMS
Web browser
Based on the open-source WebKit layout engine, coupled with Chrome's V8 JavaScript engine
supporting HTML5 and CSS3.
Multi-touch
Android has native support for multi-touch which was initially made available in handsets such
as the HTC Hero.
Multi-tasking
39
User can jump from one task to another and same time various application can run
simultaneously.
Resizable widgets
Widgets are resizable, so users can expand them to show more content or shrink them to save
space.
Multi-Language
Supports single direction and bi-directional text.
GCM
Google Cloud Messaging (GCM) is a service that lets developers send short message data to
their users on Android devices, without needing a proprietary sync solution.
Wi-Fi Direct
A technology that lets apps discover and pair directly, over a high-bandwidth peer-to-peer
connection.
Android Beam
A popular NFC-based technology that lets users instantly share, just by touching two NFC-
enabled phones together.
40
Android Applications
Android applications are usually developed in the Java language using the Android Software
Development Kit.
Once developed, Android applications can be packaged easily and sold out either through a
store such as Google Play, SlideME, Opera Mobile Store, Mobango, F-droid and
the Amazon Appstore.
Android powers hundreds of millions of mobile devices in more than 190 countries around the
world. It's the largest installed base of any mobile platform and growing fast. Every day more
than 1 million new Android devices are activated worldwide.
This tutorial has been written with an aim to teach you how to develop and package Android
application. We will start from environment setup for Android application programming and
then drill down to look into various aspects of Android applications.
Second point is that all the required tools to develop Android applications are freely available
and can be downloaded from the Web. Following is the list of software's you will need before
you start your Android application programming.
 Java JDK5 or later version
 Android Studio
Here last two components are optional and if you are working on Windows machine then these
components make your life easy while doing Java based application development.
Android IDEs
There are so many sophisticated Technologies are available to develop android applications, the
familiar technologies, which are predominantly using tools as follows
 Android Studio
 Eclipse IDE(Deprecated)
41
Android Libraries
This category encompasses those Java-based libraries that are specific to Android development.
Examples of libraries in this category include the application framework libraries in addition to
those that facilitate user interface building, graphics drawing and database access. A summary
of some key core Android libraries available to the Android developer is as follows −
 android.app − Provides access to the application model and is the cornerstone of all
Android applications.
 android.content − Facilitates content access, publishing and messaging between

applications and application components.
 android.database − Used to access data published by content providers and includes

SQLite database management classes.
 android.opengl − A Java interface to the OpenGL ES 3D graphics rendering API.
 android.os − Provides applications with access to standard operating system services

including messages, system services and inter-process communication.
 android.text − Used to render and manipulate text on a device display.
 android.view − The fundamental building blocks of application user interfaces.
 android.widget − A rich collection of pre-built user interface components such as

buttons, labels, list views, layout managers, radio buttons etc.
 android.webkit − A set of classes intended to allow web-browsing capabilities to be

built into applications.
Having covered the Java-based core libraries in the Android runtime, it is now time to turn our
attention to the C/C++ based libraries contained in this layer of the Android software stack.
Android Runtime
This is the third section of the architecture and available on the second layer from the bottom.
This section provides a key component called Dalvik Virtual Machine which is a kind of Java
Virtual Machine specially designed and optimized for Android.
42
The Dalvik VM makes use of Linux core features like memory management and multi-
threading, which is intrinsic in the Java language. The Dalvik VM enables every Android
application to run in its own process, with its own instance of the Dalvik virtual machine.
The Android runtime also provides a set of core libraries which enable Android application
developers to write Android applications using standard Java programming language.
Application Framework
The Application Framework layer provides many higher-level services to applications in the
form of Java classes. Application developers are allowed to make use of these services in their
applications.
The Android framework includes the following key services −

Activity Manager − Controls all aspects of the application lifecycle and activity stack.
Content Providers − Allows applications to publish and share data with other
applications.
Resource Manager − Provides access to non-code embedded resources such as strings,
color settings and user interface layouts.
Notifications Manager − Allows applications to display alerts and notifications to the
user.
View System − An extensible set of views used to create application user interfaces.
Android Studio
 Android Studio is the official IDE for android application development.It works based
on IntelliJ IDEA, You can download the latest version of android studio from Android
Studio 2.2 Download, If you are new to installing Android Studio on windows,you will
find a file, which is named as android-studio-bundle-143.3101438-windows.exe.So just
download and run on windows machine according to android studio wizard guideline.
 If you are installing Android Studio on Mac or Linux, You can download the latest version
from Android Studio Mac Download,or Android Studio Linux Download, check the
instructions provided along with the downloaded file for Mac OS and Linux. This tutorial
will consider that you are going to setup your environment on Windows machine having
Windows 8.1 operating system.
43
JAVA
Java is defined by a specification and consists of a programming language, a compiler, core
libraries and a runtime (Java virtual machine) The Java runtime allows software developers to
write program code in other languages than the Java programming language which still runs on
the Java virtual machine. The Java platform is usually associated with the Java virtual machineand
the Java core libraries.
The Java language was designed with the following properties:
 Platform independent: Java programs use the Java virtual machine as abstraction and do not
access the operating system directly. This makes Java programs highly portable. A Java
program (which is standard-compliant and follows certain rules) can run unmodified on all
supported platforms, e.g., Windows or Linux.
 Object-orientated programming language: Except the primitive data types, all elements in Java
are objects.
 Strongly-typed programming language: Java is strongly-typed, e.g., the types of the used
variables must be pre-defined and conversion to other objects is relatively strict, e.g., must be
done in most cases by the programmer.
 Interpreted and compiled language: Java source code is transferred into the bytecode format
which does not depend on the target platform. These bytecode instructions will be interpreted
by the Java Virtual machine (JVM). The JVM contains a so called Hotspot-Compiler which
translates performance critical bytecode instructions into native code instructions.
 Automatic memory management: Java manages the memory allocation and de-allocation for
creating new objects. The program does not have direct access to the memory. The so-called
garbage collector automatically deletes objects to which no active pointer exists.
The Java syntax is similar to C++. Java is case-sensitive, e.g., variables

called myValue andmyvalue are treated as different variables.
44
JVM
The Java virtual machine (JVM) is a software implementation of a computer that executes
programs like a real machine.
The Java virtual machine is written specifically for a specific operating system, e.g., for Linux a
special implementation is required as well as for Windows.
Java programs are compiled by the Java compiler into bytecode. The Java virtual machine
interprets this bytecode and executes the Java program.
Development process with JAVA
Java source files are written as plain text documents. The programmer typically writes Java source
code in an Integrated Development Environment (IDE) for programming. An IDE supports the
programmer in the task of writing code, e.g., it provides auto-formating of the source code,
highlighting of the important keywords, etc.
At some point the programmer (or the IDE) calls the Java compiler ( javac ). The Java compiler
creates the bytecode instructions. These instructions are stored in .class files and can be executed
by the Java Virtual Machine.
Classpath
The classpath defines where the Java compiler and Java runtime look for .class files to load.
These instructions can be used in the Java program.
For example, if you want to use an external Java library you have to add this library to your
classpath to use it in your program.
45
FIREBASE
Firebase is a backend platform for building Web, Android and IOS applications. It offers real
time database, different APIs, multiple authentication types and hosting platform.
Firebase can power your app's backend, including data storage, user authentication, static
hosting, and more. Focus on creating extraordinary user experiences. We will take care of the
rest. Build cross-platform native mobile and web apps with our Android, iOS, and JavaScript
SDKs. You can also connect Firebase to your existing backend using our server-side libraries or
our REST API.
Firebase Features
 Real-time Database − Firebase supports JSON data and all users connected to it receive
live updates after every change.
 Authentication − We can use anonymous, password or different social authentications.
 Hosting − The applications can be deployed over secured connection to Firebase servers.
Firebase Advantages
 It is simple and user friendly. No need for complicated configuration.
 The data is real-time, which means that every change will automatically update
connected clients.
 Firebase offers simple control dashboard.
 There are a number of useful services to choose.
Firebase Limitations
 Firebase free plan is limited to 50 Connections and 100 MB of storage.
The Firebase data is representing JSON objects. If you open your app from Firebase dashboard,
you can add data manually by clicking on the + sign.
46
It provides the following features for the Development phase
Integration with Cloud Messaging.
Robust Authentication for added security.
Realtime Database for realtime storage of app data.
Storage support for files.
Support for on the fly Remote Configuration.
Test Lab to deliver high quality apps.
Crash Reporting to keep your apps stable and free from bugs.
Adding Firebase based Authentication
To add Authentication using Firebase follow the below steps :
 Go to Firebase Website firebase.google.com and create a firebase account to start with.

Go to Firebase console and Create a New Project by clicking on the “Create New
Project”.
 Give the Project name and country you are currently in, Once you are done click on
“Create Project” button.
 In the next screen choose “Add Firebase to your Android app” and then add the package
details and Debug signing certificate SHA-1 key( This is required if you want to enable
certain features like Dynamic Links, Invites, and Google Sign-In etc. otherwise it is an
optional field).
 This will download the google-services.json file. Download it to your computer. We will
add it to our android app later.
 In the projects dashboard. Click on Auth Menu, then in the SIGN-IN METHOD click on
Email/Password and enable it.
 Once you are done with this, Let’s create the Android Application that will connect to
Firebase for user authentication.
47
SYSTEM
DESIGN
SCREENSHOTS
48
SPLASH SCREEN
49
LOGIN
50
DASHBOARD
51
PROFILE (PERSONAL DETAIL)
52
PROFILE (CONTACT DETAIL)
53
PROFILE (BANK DETAIL)
54
PROFILE (EDIT BANK DETAIL)
55
USER DOWNLINE
56
FUNDS
57
BONUS
58
NOTIFICATION
59
CONTACT
60
FEEDBACK
61
VOUCHER
62
POINTS
63
NEWS
64
COMPANY
65
NEW DISTRIBUTER REGISTRATION
66
MOBILE NO. FOR AUTHENTICATION
67
OTP VERIFICATION
68
SYSTEM
CODING
69
ANDROID MANIFEST.XML
<?xml version="1.0" encoding="utf-8"?>

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="mht.mlm">
<uses-permission android:name="android.permission.INTERNET" />

<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<application
android:allowBackup="true"
android:icon="@drawable/logo"
android:label="@string/app_name"
android:roundIcon="@drawable/logo"
android:supportsRtl="true"
android:theme="@style/AppTheme">
<activity android:name=".Splash">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />

</intent-filter>
</activity>
<service android:name=".MyFirebaseMessagingService">
<intent-filter>
<action android:name="com.google.firebase.MESSAGING_EVENT" />
</intent-filter>
</service>
<service android:name=".MyFirebaseInstanceIdService">
<intent-filter>
70
<action android:name="com.google.firebase.INSTANCE_ID_EVENT" />
</intent-filter>
</service>
<activity android:name=".Home" />

<activity
android:name=".Profile"
android:label="@string/title_activity_profile"
android:theme="@style/AppTheme" />
<activity android:name=".LoginActivity" />
<activity android:name=".VoucherActivity" />
<activity android:name=".FeedbackActivity" />
<activity android:name=".NewsActivity" />
<activity android:name=".PointActivity" />
<activity android:name=".MemberActivity" />
<activity android:name=".ContactActivity" />
<activity android:name=".NotificationActivity" />
<activity android:name=".DownLineActivity" />
<activity
android:name=".CompanyActivity"
android:label="@string/title_activity_company"
<activity android:name=".PhoneActivity" />
<activity android:name=".VerifyActivity" />
<activity
android:name=".FundsActivity"
android:label="@string/title_activity_funds"
<activity android:name=".Bonus" />
<activity android:name=".Purchase" />
<activity android:name=".OrderActivity" />
<activity android:name=".Order1Activity" />
71
<activity android:name=".Level1" />
<activity android:name=".FillActivity" />
<activity android:name=".Level333"></activity>
<activity android:name=".Level444"></activity>
</application>
</manifest>
72
ABOUT FRAGMENT.JAVA
package mht.mlm;
import android.os.Bundle;
import android.support.v4.app.Fragment;
import android.view.LayoutInflater;
import android.view.View;
import android.view.ViewGroup;
/**
* A simple {@link Fragment} subclass.
*/
public class AboutFragment extends Fragment {
public AboutFragment() {
// Required empty public constructor
}
@Override
public View onCreateView(LayoutInflater inflater, ViewGroup container,
Bundle savedInstanceState) {
// Inflate the layout for this fragment
return inflater.inflate(R.layout.fragment_about, container, false);
}
73
BANK DETAIL.JAVA
package mht.mlm;
import android.content.Context;
import android.content.Intent;
import android.content.SharedPreferences;
import android.widget.TextView;
import com.google.firebase.database.DataSnapshot;
import com.google.firebase.database.DatabaseError;
import com.google.firebase.database.DatabaseReference;
import com.google.firebase.database.FirebaseDatabase;
import com.google.firebase.database.ValueEventListener;
/**
*/
public class BankDetail extends Fragment {
public BankDetail() {
}
74
TextView mob,addres,email;
String idaa;
@Override
//the layout for this fragment
View bd= inflater.inflate(R.layout.fragment_bank_detail, container, false);
mob=bd.findViewById(R.id.bn);
addres=bd.findViewById(R.id.bnn);
email=bd.findViewById(R.id.acn);
bd.findViewById(R.id.imageView2).setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {
startActivity(new Intent(getActivity() ,FillActivity.class));
}
});
SharedPreferences sharereferencess = getActivity().getSharedPreferences("L&P",

Context.MODE_PRIVATE);
idaa= sharereferencess.getString("usidno", String.valueOf(0));
FirebaseDatabase database = FirebaseDatabase.getInstance();
DatabaseReference myRef = database.getReference("user");
myRef.addValueEventListener(new ValueEventListener() {
@Override
public void onDataChange(DataSnapshot dataSnapshot) {
// This method is called once with the initial value and again
// whenever data at this location is updated.
75
String value1 = dataSnapshot.child(idaa).child("BN").getValue(String.class);
mob.setText ("Bank Name :"+value1);
String value2 = dataSnapshot.child(idaa).child("BBN").getValue(String.class);
addres.setText("Branch Name :"+value2);
String value3 = dataSnapshot.child(idaa).child("AC").getValue(String.class);
email.setText ("A/C Number :"+value3);
@Override
public void onCancelled(DatabaseError error) {
}
});
return bd;
}
76
BONUS.JAVA
package mht.mlm;
import android.support.v7.app.AppCompatActivity;
import android.widget.ImageView;
public class Bonus extends AppCompatActivity {
TextView pb,db,lb,tp;
String id;
ImageView d;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_bonus);
pb=findViewById(R.id.textView22);
db=findViewById(R.id.textView27);
77
lb=findViewById(R.id.textView28);
tp=findViewById(R.id.textView29);
d=findViewById(R.id.gate);
d.setOnClickListener(new View.OnClickListener() {
@Override
SharedPreferences sharedPreferences = getSharedPreferences("L&P",
SharedPreferences.Editor editor = sharedPreferences.edit();
editor.clear();
editor.commit();
finish();
startActivity(new Intent(Bonus.this,Splash.class));
}
});
SharedPreferences sharereferencess = this.getSharedPreferences("L&P",

id = sharereferencess.getString("usidno", String.valueOf(0));

@Override
String value = dataSnapshot.child(id).child("performance").getValue(String.class);
pb.setText("PERFORMANCE BONUS:"+" "+value);
}
@Override
78
// Failed to read value
}
});
FirebaseDatabase atabase = FirebaseDatabase.getInstance();

DatabaseReference yRef = atabase.getReference("user");
yRef.addValueEventListener(new ValueEventListener() {
@Override
String value = dataSnapshot.child(id).child("director").getValue(String.class);
db.setText("DIRECTOR BONUS:"+" "+value);
}
@Override
}
});
FirebaseDatabase tabase = FirebaseDatabase.getInstance();

DatabaseReference myRf = tabase.getReference("user");
myRf.addValueEventListener(new ValueEventListener() {
@Override
String value = dataSnapshot.child(id).child("leadership").getValue(String.class);
lb.setText("LEADERSHIP BONUS:"+" "+value);
}
79
@Override
}
});
FirebaseDatabase databse = FirebaseDatabase.getInstance();

DatabaseReference myReaf = databse.getReference("user");
myReaf.addValueEventListener(new ValueEventListener() {
@Override
String value = dataSnapshot.child(id).child("total").getValue(String.class);
tp.setText("TOTAL PAYABLE:"+" "+value);
}
@Override
}
});
}
}
80
CAR FUND.JAVA
package mht.mlm;
/**
*/
public class CarFund extends Fragment {
public CarFund() {
}
@Override
return inflater.inflate(R.layout.fragment_car_fund, container, false);
}
81
COMPANY ACTIVITY.JAVA
package mht.mlm;
import android.support.design.widget.TabLayout;
import android.support.v4.app.FragmentManager;
import android.support.v4.app.FragmentPagerAdapter;
import android.support.v4.view.ViewPager;
public class CompanyActivity extends AppCompatActivity {
private SectionsPagerAdapter mSectionsPagerAdapter;
private ViewPager mViewPager;

ImageView d;
@Override
setContentView(R.layout.activity_company);
82
mSectionsPagerAdapter = new SectionsPagerAdapter(getSupportFragmentManager());
// Set up the ViewPager with the sections adapter.

mViewPager = (ViewPager) findViewById(R.id.container);
mViewPager.setAdapter(mSectionsPagerAdapter);
TabLayout tabLayout = (TabLayout) findViewById(R.id.tabs);
mViewPager.addOnPageChangeListener(new
TabLayout.TabLayoutOnPageChangeListener(tabLayout));
tabLayout.addOnTabSelectedListener(new
TabLayout.ViewPagerOnTabSelectedListener(mViewPager));
@Override
editor.clear();
editor.commit();
finish();
startActivity(new Intent(CompanyActivity.this,Splash.class));
}
});
} /**
* A placeholder fragment containing a simple view.
*/
public static class PlaceholderFragment extends Fragment {
83
/**
* The fragment argument representing the section number for this
* fragment.
*/
private static final String ARG_SECTION_NUMBER = "section_number";
public PlaceholderFragment() {
}
/**
* Returns a new instance of this fragment for the given section
* number.
*/
public static PlaceholderFragment newInstance(int sectionNumber) {
PlaceholderFragment fragment = new PlaceholderFragment();
Bundle args = new Bundle();
args.putInt(ARG_SECTION_NUMBER, sectionNumber);
fragment.setArguments(args);
return fragment;
}
@Override
View rootView = inflater.inflate(R.layout.fragment_company, container, false);
TextView textView = (TextView) rootView.findViewById(R.id.section_label);
textView.setText(getString(R.string.section_format,
getArguments().getInt(ARG_SECTION_NUMBER)));
return rootView;
}
}
84
/**
* A {@link FragmentPagerAdapter} that returns a fragment corresponding to
* one of the sections/tabs/pages.
*/
public class SectionsPagerAdapter extends FragmentPagerAdapter {
public SectionsPagerAdapter(FragmentManager fm) {

super(fm);
}
@Override
public Fragment getItem(int position) {
Fragment fragment =null;
switch (position){
case 0:
fragment=new AboutFragment();
break;
case 1:
fragment=new ManagementFragment();
}
return fragment;
}
@Override
public int getCount() {
// Show 3 total pages.
return 2;
}
}
85
CONTACT ACTIVITY.JAVA
package mht.mlm;
public class ContactActivity extends AppCompatActivity {
TextView tt;
ImageView d;
@Override
setContentView(R.layout.activity_contact);
tt=findViewById(R.id.textView7);
tt.setText(" ABC,XYZ\n Varanasi,000111\n India");
@Override
86
editor.clear();
editor.commit();
finish();
startActivity(new Intent(ContactActivity.this,Splash.class));
}
});
}
}
87
CONTACT DETAIL.JAVA
package mht.mlm;
/**
*/
public class ContactDetail extends Fragment {
public ContactDetail() {
}
88
TextView mob,addres,email;
String idaa;
@Override
View bd= inflater.inflate(R.layout.fragment_contact_detail, container, false);
addres=bd.findViewById(R.id.dob);
email=bd.findViewById(R.id.emid);
SharedPreferences sharereferencess = getActivity().getSharedPreferences("L&P",

@Override
String value1 = dataSnapshot.child(idaa).child("address").getValue(String.class);

addres.setText("Address :"+value1);
String value2 = dataSnapshot.child(idaa).child("email").getValue(String.class);
email.setText("Email :"+value2);
}
89
@Override
}
});
return bd;
}
90
DOWNLINE ACTIVITY.JAVA
package mht.mlm;
import android.support.v7.widget.CardView;
public class DownLineActivity extends AppCompatActivity {
CardView t1,t2,t3;
TextView lp1,lp2,lp3;
ImageView d;
String id;
@Override
setContentView(R.layout.activity_down_line);
91
@Override
editor.clear();
editor.commit();
finish();
startActivity(new Intent(DownLineActivity.this,Splash.class));
}
});
lp1=findViewById(R.id.l1);


DatabaseReference myRef = database.getReference("Downline").child(id);
@Override
String value = dataSnapshot.child("L1").getValue(String.class);
lp1.setText("ID:"+" "+value);
92
String value1 = dataSnapshot.child("L11").getValue(String.class);
lp2.setText("ID:"+" "+value1);

SharedPreferences sharedPreferences = getSharedPreferences("Data1",

editor.putString("L1", value);
editor.putString("L11", value1);
editor.commit();
}
@Override
}
});
t1=findViewById(R.id.p1);
t1.setOnClickListener(new View.OnClickListener() {
@Override
startActivity(new Intent(DownLineActivity.this,Level1.class));
}
});
93
@Override
}
});
@Override
}
});
}
}
94
FEEDBACK ACTIVITY.JAVA
package mht.mlm;
import android.text.TextUtils;
import android.widget.Button;
import android.widget.EditText;
import android.widget.Toast;
public class FeedbackActivity extends AppCompatActivity {
EditText na,su,em,mes;
Button subm,res;
String id;
ImageView d;
@Override
setContentView(R.layout.activity_feedback);
@Override
95
editor.clear();
editor.commit();
finish();
startActivity(new Intent(FeedbackActivity.this,Splash.class));
}
});
na=findViewById(R.id.otpchk);
su=findViewById(R.id.tpchk);
em=findViewById(R.id.tphk);
mes=findViewById(R.id.suchk);
subm=findViewById(R.id.button4);
subm.setOnClickListener(new View.OnClickListener() {
@Override
DatabaseReference myRef = database.getReference("Feedback");
String nam=na.getText().toString();
String sub=su.getText().toString();
String email=em.getText().toString();
String mess=mes.getText().toString();
if (TextUtils.isEmpty(nam)) {
Toast.makeText(getApplicationContext(), "Enter Name!",
Toast.LENGTH_SHORT).show();
return;
}
if (TextUtils.isEmpty(sub)) {
Toast.makeText(getApplicationContext(), "Enter Subject!",
96
return;
}
if (TextUtils.isEmpty(email)) {
Toast.makeText(getApplicationContext(), "Enter Email!",
return;
}
if (TextUtils.isEmpty(mess)) {
Toast.makeText(getApplicationContext(), "Enter Message!",
return;
}
myRef.child(id).child("name").setValue(nam);
myRef.child(id).child("sub").setValue(sub);
myRef.child(id).child("email").setValue(email);
myRef.child(id).child("message").setValue(mess);
}
});
res=findViewById(R.id.button5);
res.setOnClickListener(new View.OnClickListener() {
@Override
na.getText().clear();
su.getText().clear();
em.getText().clear();
mes.getText().clear();
}
});
}
}
97
FILL ACTIVITY.JAVA
package mht.mlm;
import android.text.TextUtils;
import android.widget.Button;
import android.widget.EditText;
import android.widget.Toast;
public class FillActivity extends AppCompatActivity {
EditText aa,bb,cc;
Button ot;
String idaa;
@Override
setContentView(R.layout.activity_fill);
aa=findViewById(R.id.ab);
bb=findViewById(R.id.cd);
98
cc=findViewById(R.id.ef);
ot=findViewById(R.id.submitt);
ot.setOnClickListener(new View.OnClickListener() {
@Override
final String bd=aa.getText().toString();
final String bn=bb.getText().toString();
final String bid=cc.getText().toString();
if (TextUtils.isEmpty(bd)) {
Toast.makeText(getApplicationContext(), "Enter Bank Name!",
return;
}
Toast.makeText(getApplicationContext(), "Enter Branch Name!",
return;
}
Toast.makeText(getApplicationContext(), "Enter A/C Number!",
return;
}
SharedPreferences sharereferencess = getSharedPreferences("L&P",

myRef.child(idaa).child("BN").setValue(bd);
99
myRef.child(idaa).child("BBN").setValue(bn);
myRef.child(idaa).child("AC").setValue(bid);
startActivity(new Intent(FillActivity.this,BankDetail.class));
}
});
}
}
100
FUNDS ACTIVITY.JAVA
package mht.mlm;
import android.support.design.widget.TabLayout;
import android.support.v4.app.FragmentManager;
import android.support.v4.app.FragmentPagerAdapter;
import android.support.v4.view.ViewPager;
public class FundsActivity extends AppCompatActivity {
/**
* The {@link android.support.v4.view.PagerAdapter} that will provide
* fragments for each of the sections. We use a
* {@link FragmentPagerAdapter} derivative, which will keep every
* loaded fragment in memory. If this becomes too memory intensive, it
* may be best to switch to a
* {@link android.support.v4.app.FragmentStatePagerAdapter}.
*/
private SectionsPagerAdapter mSectionsPagerAdapter;
/**
* The {@link ViewPager} that will host the section contents.
*/
101
private ViewPager mViewPager;
@Override
setContentView(R.layout.activity_funds);
// Create the adapter that will return a fragment for each of the three
// primary sections of the activity.
mSectionsPagerAdapter = new SectionsPagerAdapter(getSupportFragmentManager());
// Set up the ViewPager with the sections adapter.

mViewPager = (ViewPager) findViewById(R.id.container);
mViewPager.setAdapter(mSectionsPagerAdapter);
TabLayout tabLayout = (TabLayout) findViewById(R.id.tabs);
mViewPager.addOnPageChangeListener(new
TabLayout.TabLayoutOnPageChangeListener(tabLayout));
tabLayout.addOnTabSelectedListener(new
TabLayout.ViewPagerOnTabSelectedListener(mViewPager));
/**
* A placeholder fragment containing a simple view.
*/
public static class PlaceholderFragment extends Fragment {
102
/**
* The fragment argument representing the section number for this
* fragment.
*/
private static final String ARG_SECTION_NUMBER = "section_number";
public PlaceholderFragment() {
}
/**
* Returns a new instance of this fragment for the given section
* number.
*/
public static PlaceholderFragment newInstance(int sectionNumber) {
PlaceholderFragment fragment = new PlaceholderFragment();
Bundle args = new Bundle();
args.putInt(ARG_SECTION_NUMBER, sectionNumber);
fragment.setArguments(args);
return fragment;
}
@Override
View rootView = inflater.inflate(R.layout.fragment_funds, container, false);
TextView textView = (TextView) rootView.findViewById(R.id.section_label);
textView.setText(getString(R.string.section_format,
getArguments().getInt(ARG_SECTION_NUMBER)));
return rootView;
}
}
/**
103
* A {@link FragmentPagerAdapter} that returns a fragment corresponding to
* one of the sections/tabs/pages.
*/
public class SectionsPagerAdapter extends FragmentPagerAdapter {
public SectionsPagerAdapter(FragmentManager fm) {

super(fm);
}
@Override
public Fragment getItem(int position) {
Fragment fragment =null;
switch (position){
case 0:
fragment=new CarFund();
break;
case 1:
fragment=new HouseFund();
break;
case 2:
fragment=new TravelFund();
}
return fragment;
}
@Override
public int getCount() {
// Show 3 total pages.
return 3;
}
}
}
104
HOME.JAVA
package mht.mlm;
public class Home extends AppCompatActivity {
CardView prof,downlin,fund,bonu,notifi,contac,feedbac,vouche,poin,ne,comp,member,pur;
TextView tvv;
String id;
ImageView d;
@Override
setContentView(R.layout.activity_home);
@Override
105
editor.clear();
editor.commit();
finish();
startActivity(new Intent(Home.this,Splash.class));
}
});
tvv=findViewById(R.id.iid);
tvv.setText(id);
prof = (CardView) findViewById(R.id.card1);
downlin = (CardView) findViewById(R.id.card2);
fund = (CardView) findViewById(R.id.card3);
bonu = (CardView) findViewById(R.id.card4);
notifi = (CardView) findViewById(R.id.card5);
contac = (CardView) findViewById(R.id.card6);
feedbac = (CardView) findViewById(R.id.card7);
vouche = (CardView) findViewById(R.id.card8);
poin = (CardView) findViewById(R.id.card9);
ne = (CardView) findViewById(R.id.card10);
comp = (CardView) findViewById(R.id.card11);
member = (CardView) findViewById(R.id.card12);
pur = (CardView) findViewById(R.id.card13);
prof.setOnClickListener(new View.OnClickListener() {
@Override
startActivity(new Intent(Home.this,Profile.class));
106
}
});
downlin.setOnClickListener(new View.OnClickListener() {
@Override
startActivity(new Intent(Home.this,DownLineActivity.class));
}
});
fund.setOnClickListener(new View.OnClickListener() {
@Override
startActivity(new Intent(Home.this,FundsActivity.class));
}
});
bonu.setOnClickListener(new View.OnClickListener() {
@Override
startActivity(new Intent(Home.this,Bonus.class));
}
});
notifi.setOnClickListener(new View.OnClickListener() {
@Override
startActivity(new Intent(Home.this,NotificationActivity.class));
}
});
contac.setOnClickListener(new View.OnClickListener() {
@Override
startActivity(new Intent(Home.this,ContactActivity.class));
}
});
107
feedbac.setOnClickListener(new View.OnClickListener() {
@Override
startActivity(new Intent(Home.this,FeedbackActivity.class));
}
});
vouche.setOnClickListener(new View.OnClickListener() {
@Override
startActivity(new Intent(Home.this,VoucherActivity.class));
}
});
poin.setOnClickListener(new View.OnClickListener() {
@Override
startActivity(new Intent(Home.this,PointActivity.class));
}
});
ne.setOnClickListener(new View.OnClickListener() {
@Override
startActivity(new Intent(Home.this,NewsActivity.class));
}
});
comp.setOnClickListener(new View.OnClickListener() {
@Override
startActivity(new Intent(Home.this,CompanyActivity.class));
}
});
member.setOnClickListener(new View.OnClickListener() {
@Override
108
startActivity(new Intent(Home.this,MemberActivity.class));
}
});
pur.setOnClickListener(new View.OnClickListener() {
@Override
startActivity(new Intent(Home.this,Purchase.class));
}
});
109
HOUSE FUND.JAVA
package mht.mlm;
/**
*/
public class HouseFund extends Fragment {
public HouseFund() {
}
@Override
return inflater.inflate(R.layout.fragment_house_fund, container, false);
}
110
LEVEL 1.JAVA
package mht.mlm;
public class Level1 extends AppCompatActivity {
CardView t1,t2,t3;
ImageView d;
String id;
@Override
111
setContentView(R.layout.activity_level1);
]
SharedPreferences sharereferencess = this.getSharedPreferences("Data1",
id = sharereferencess.getString("L1", String.valueOf(0));
@Override



editor.commit();
}
112
@Override
}
});
@Override
startActivity(new Intent(Level1.this,Level2.class));
}
});
@Override
}
});
@Override
}
});
}
}
113
LEVEL2.JAVA
package mht.mlm;
CardView t1,t2,t3;
ImageView d;
String id;
@Override
114


@Override


@Override
}
});
115
@Override
}
});
@Override
}
});
@Override
}
});
}
}
116
LEVEL3.JAVA
package mht.mlm;
CardView t1,t2,t3;
ImageView d;
String id;
@Override
117


@Override


@Override
}
});
118
@Override
}
});
@Override
}
});
@Override
}
});
}
}
119
LEVEL 4.JAVA
package mht.mlm;
CardView t1,t2,t3;
ImageView d;
String id;
@Override
120


@Override


@Override
}
});
121
@Override
}
});
@Override
}
});
@Override
}
});
}
}
122
LEVEL11.JAVA
package mht.mlm;
CardView t1,t2,t3;
ImageView d;
String id;
@Override


@Override
123


editor.commit();
}
@Override
}
});
@Override
}
});
@Override
}
});
@Override
}
});
}
}
124
LEVEL22.JAVA
package mht.mlm;
CardView t1,t2,t3;
ImageView d;
String id;
@Override


@Override
125


@Override
}
});
@Override
}
});
@Override
}
});
@Override
}
});
}
}
126
LEVEL33.JAVA
package mht.mlm;
CardView t1,t2,t3;
ImageView d;
String id;
@Override


@Override
127

@Override
}
});
@Override
}
});
@Override
}
});
@Override
}
});
}
}
128
LEVEL44.JAVA
package mht.mlm;
CardView t1,t2,t3;
ImageView d;
String id;
@Override


@Override
129


@Override
}
});
@Override
}
});
@Override
}
});
@Override
}
});
}
}
130
LEVEL111.JAVA
package mht.mlm;
CardView t1,t2,t3;
ImageView d;
String id;
@Override


@Override

131

editor.commit();
}
@Override
}
});
@Override
}
});
@Override
}
});
@Override
}
});
}
}
132
LEVEL222.JAVA
package mht.mlm;
CardView t1,t2,t3;
ImageView d;
String id;
@Override


@Override
133


@Override
}
});
@Override
}
});
@Override
}
});
@Override
}
});
}
}
134
LEVEL333.JAVA
package mht.mlm;
CardView t1,t2,t3;
ImageView d;
String id;
@Override


@Override
135


@Override
}
});
@Override
}
});
@Override
}
});
@Override
}
});
}
}
136
LEVEL444.JAVA
package mht.mlm;
CardView t1,t2,t3;
ImageView d;
String id;
@Override


@Override
137


@Override
}
});
@Override
}
});
@Override
}
});
@Override
}
});
}
}
138
VOUCHER_ACTIVITY.JAVA
package mht.mlm;
import com.cooltechworks.views.ScratchTextView;
public class VoucherActivity extends AppCompatActivity {
ScratchTextView scratchTextView;
ImageView d;
@Override
setContentView(R.layout.activity_voucher);
@Override
editor.clear();
editor.commit();
finish();
startActivity(new Intent(VoucherActivity.this,Splash.class));
}
});
scratchTextView = findViewById(R.id.text);
assert scratchTextView != null;

scratchTextView.setRevealListener(new ScratchTextView.IRevealListener() {
@Override
public void onRevealed(ScratchTextView scratchTextView) {
}
});
}
}
139
ACTIVITY_LOGIN.XML

<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
tools:context=".LoginActivity">
<TextView
android:id="@+id/textView"
android:layout_width="119dp"
android:layout_height="40dp"
android:layout_above="@+id/teip"
android:layout_alignStart="@+id/teip"
android:text="Login"
android:textColor="#0a0909"
android:textSize="25dp"
android:textStyle="bold" />
android:id="@+id/teip"
android:layout_above="@+id/teip1"
android:layout_centerHorizontal="true"
android:background="#66fcfcff">
<EditText
android:id="@+id/usrid"
android:layout_height="wrap_content"
android:layout_marginBottom="10dp"
android:hint="User id"
android:textSize="20dp" />
</android.support.design.widget.TextInputLayout>
<android.support.design.widget.TextInputLayout
android:id="@+id/teip1"
android:layout_alignParentBottom="true"
<EditText
android:id="@+id/pass"
140
android:hint="password"
<Button
android:id="@+id/loogin"
android:background="#00f"
android:text="Login"
android:textColor="#eeeef2"
android:textStyle="bold"
android:typeface="monospace" />
<ImageView
android:id="@+id/imageView"
android:layout_alignParentTop="true"
android:layout_marginTop="42dp"
app:srcCompat="@mipmap/ic_launcher" />
</RelativeLayout>
141
ACTIVITY_HOME.XML
tools:context=".Home">
<android.support.v7.widget.CardView
android:id="@+id/tit"
android:layout_height="50dp">
<RelativeLayout
android:layout_height="match_parent">
<TextView
android:id="@+id/iid"
android:layout_width="wrap_content"
android:layout_toStartOf="@+id/gate"
android:text="textview"
android:textAlignment="center"
<ImageView
android:id="@+id/gate"
android:layout_marginRight="10dp"
android:layout_alignParentEnd="true"
android:src="@drawable/ic_exit_to_app_black_24dp" />
<TextView
android:layout_marginLeft="10dp"
android:text="Home"
android:layout_height="match_parent" />
</RelativeLayout>
</android.support.v7.widget.CardView>
142
<ScrollView
android:layout_below="@+id/tit"
android:layout_centerHorizontal="true">
<RelativeLayout
android:orientation="vertical" >
<LinearLayout
android:id="@+id/la1"
android:orientation="horizontal"
android:layout_height="wrap_content">
android:id="@+id/card1"
app:cardCornerRadius="5dp"
<RelativeLayout
android:background="#efefef"
<android.support.v7.widget.AppCompatImageView
android:layout_alignParentStart="true"
android:src="@drawable/profile" />
<TextView
android:text="Profile" />
</RelativeLayout>
143
<RelativeLayout
android:src="@drawable/network"
<TextView
android:text="Downline" />
</RelativeLayout>
<RelativeLayout
android:src="@drawable/fund"
<TextView
android:text="Funds" />
144
</RelativeLayout>
</LinearLayout>
<LinearLayout
android:layout_below="@+id/la1"
<RelativeLayout
android:src="@drawable/bonus"
<TextView
android:text="Bonus" />
</RelativeLayout>
<RelativeLayout
145
android:src="@drawable/notification"
<TextView
android:text="Notification" />
</RelativeLayout>
<RelativeLayout
android:src="@drawable/contact"
<TextView
android:text="Contact" />
</RelativeLayout>
</LinearLayout>
<LinearLayout
146
android:orientation="horizontal">
app:cardCornerRadius="5dp">
<RelativeLayout
android:background="#efefef">
android:src="@drawable/feedback" />
<TextView
android:text="Feedback"
</RelativeLayout>
<RelativeLayout
147
android:src="@drawable/gift" />
<TextView
android:text="Voucher"
</RelativeLayout>
<RelativeLayout
android:src="@drawable/points" />
<TextView
android:text="Point"
</RelativeLayout>
</LinearLayout>
<LinearLayout
148
<RelativeLayout
android:src="@drawable/news"
<TextView
android:text="News" />
</RelativeLayout>
<RelativeLayout
android:src="@drawable/logo"
<TextView
149
android:text="Company" />
</RelativeLayout>
<RelativeLayout
android:src="@drawable/person"
<TextView
android:text="Add member" />
</RelativeLayout>
</LinearLayout>
<LinearLayout
150
<RelativeLayout
android:src="@drawable/purchase"
<TextView
android:text="Purchase" />
</RelativeLayout>
</LinearLayout>
</RelativeLayout>
</ScrollView>
</RelativeLayout>
151
ACTIVITY_VOUCHER.XML

tools:context=".VoucherActivity">
<RelativeLayout
<ImageView
<TextView
android:text="Voucher"
</RelativeLayout>
android:layout_marginStart="18dp"
android:layout_marginTop="110dp">
<RelativeLayout
152
<com.cooltechworks.views.ScratchTextView
android:id="@+id/text"
android:text="MHT"
</RelativeLayout>
</RelativeLayout>
153
ACTIVITY_LEVEL1.XML

tools:context=".Level1">
android:id="@+id/p1"
<RelativeLayout
<TextView
android:id="@+id/l1"
</RelativeLayout>
android:layout_below="@+id/p1"
<RelativeLayout
<TextView
</RelativeLayout>
android:layout_below="@+id/p2"
<RelativeLayout
154
<TextView
</RelativeLayout>
</RelativeLayout>
155
ACTIVITY_SPLASH.XML

tools:context=".Splash">
<ImageView
android:background="@drawable/logo" />
<ProgressBar
android:id="@+id/progressBar"
style="?android:attr/progressBarStyle"
android:layout_marginBottom="94dp" />
</RelativeLayout>
156
ACTIVITY_PURCHASE.XML

tools:context=".Purchase">
<RelativeLayout
<ImageView
<TextView
android:text="Purchase"
</RelativeLayout>
android:id="@+id/item1"
157
android:layout_below="@+id/tit"
<RelativeLayout
<ImageView
android:background="@drawable/shec"/>
<TextView
android:id="@+id/til"
android:textColor="#020202"
android:text="Shepa College"
android:layout_height="wrap_content" />
<TextView
android:layout_below="@+id/til"
android:text="Price : Rs 51"
</RelativeLayout>
android:id="@+id/itemd2"
android:layout_below="@+id/item1"
<RelativeLayout
158
<ImageView
android:background="@drawable/hostf"/>
<TextView
android:id="@+id/til1"
android:textColor="#020202"
android:text="Shepa Boys Hostel"
android:layout_height="wrap_content" />
<TextView
android:text="Price : Rs 21"
android:layout_below="@+id/til1"
</RelativeLayout>
</RelativeLayout>
159
ACTIVITY_FEEDBACK.XML

tools:context=".FeedbackActivity">
<RelativeLayout
<ImageView
<TextView
android:text="Feedback"
</RelativeLayout>
android:id="@+id/teip"
160
android:layout_marginEnd="11dp"
<EditText
android:id="@+id/otpchk"
<TextView
android:id="@+id/textView9"
android:layout_alignBottom="@+id/teip"
android:text="Name :"
android:id="@+id/tip"
<EditText
android:id="@+id/tpchk"
<TextView
161
android:layout_alignBottom="@+id/tip"
android:layout_alignStart="@+id/textView9"
android:text="Subject :"
android:id="@+id/eip"
<EditText
android:id="@+id/tphk"
<TextView
android:layout_centerVertical="true"
android:text="Email :"
android:id="@+id/sbip"
162
<EditText
android:id="@+id/suchk"
<TextView
android:text="Message :"
<Button
android:id="@+id/button4"
android:background="#00ff2f"
android:textColor="#ffffff"
android:text="Submit" />
<Button
android:background="#424342"
android:textColor="#ffffff"
android:layout_alignTop="@+id/button4"
android:text="Reset" />
</RelativeLayout>
163
ACTIVITY_MEMBER.XML

tools:context=".MemberActivity">
<RelativeLayout
<ImageView
<TextView
android:text="Member"
</RelativeLayout>
<ScrollView
164
<RelativeLayout
<EditText
android:hint="Upline Id*" />
<Button
android:id="@+id/button"
android:typeface="monospace"
android:text="VALIDATE" />
<EditText
android:hint="First Name*" />
<EditText
165
android:layout_below="@+id/textView3"
android:hint="Last Name" />
<EditText
android:hint="DOB*(DD/MM/YYYY)" />
<EditText
android:hint="Email ID" />
<EditText
android:hint="Address*" />
<EditText
166
android:hint="Password*" />
</RelativeLayout>
</ScrollView>
<Button
android:text="Next"
android:typeface="monospace" />
</RelativeLayout>
167
ACTIVITY_FILL.XML

tools:context=".FillActivity">
<EditText
android:id="@+id/ab"
android:hint="Enter Bank Name"
/>
<EditText
android:id="@+id/cd"
android:hint="Enter Branch Name"
android:layout_marginTop="90dp" />
<EditText
android:id="@+id/ef"
android:hint="Enter A/C Number"
168
android:layout_marginTop="161dp" />
<Button
android:id="@+id/submitt"
android:textColor="#f1f1f4"
android:background="#5aff3d"
android:text="Submit" />
</RelativeLayout>
169
ACTIVITY_PROFILE.XML

<android.support.design.widget.CoordinatorLayout
xmlns:android="http://schemas.android.com/apk/res/android"
android:id="@+id/main_content"
android:fitsSystemWindows="true"
tools:context=".Profile">
<RelativeLayout
<TextView
android:text="Profile"
</RelativeLayout>
<android.support.design.widget.TabLayout
android:id="@+id/tabs"
android:background="#1f1f21"
app:tabTextColor="#fdfdfd"
app:tabIndicatorColor="#5b5bff"
app:tabIndicatorHeight="5dp"
app:tabSelectedTextColor="#fafafa"
170
<android.support.design.widget.TabItem
android:id="@+id/tabItem"
android:icon="@drawable/ic_person_black_24dp"
android:text="Personal Details" />
android:id="@+id/tabItem2"
android:icon="@drawable/ic_account_box_black_24dp"
android:text="Contact Details" />
android:icon="@drawable/ic_perm_contact_calendar_black_24dp"
android:text="Bank Details" />
</android.support.design.widget.TabLayout>
<android.support.v4.view.ViewPager
android:id="@+id/container"
app:layout_behavior="@string/appbar_scrolling_view_behavior" />
</android.support.design.widget.CoordinatorLayout>
171
ACTIVITY_FUNDS.XML

<android.support.design.widget.CoordinatorLayout
xmlns:android="http://schemas.android.com/apk/res/android"
android:id="@+id/main_content"
android:fitsSystemWindows="true"
tools:context=".FundsActivity">
<RelativeLayout
<TextView
android:text="Profile"
</RelativeLayout>
<android.support.design.widget.TabLayout
android:id="@+id/tabs"
android:background="#1f1f21"
app:tabTextColor="#fdfdfd"
app:tabIndicatorColor="#5b5bff"
app:tabIndicatorHeight="5dp"
app:tabSelectedTextColor="#fafafa"
172
android:id="@+id/tabItem"
android:text="Car Fund" />
android:text="House Fund" />
android:text="Travel Fund" />
</android.support.design.widget.TabLayout>
<android.support.v4.view.ViewPager
android:id="@+id/container"
app:layout_behavior="@string/appbar_scrolling_view_behavior" />
</android.support.design.widget.CoordinatorLayout>
173
FUTURE SCOPE OF THE PROJECT
The scope of this project will be limited to the following:-
 Distributers profiles:
 Automatically generated business points:
 Application Management :
 Sending feedback :
 Veryfying New distributer using OTP:
 Getting Vouchers:
 Getting Bonus details:
 Improve the marketing strategy:
 Easy for online shoping:
 Getting connected with the supplier:
174
CONCLUSION
175
CONCLUSION
After this much analysis we can say that this application is not an ordinary but it will help both, a
Distributer as well as the Supplier to manage and work properly that will helpful for the
Marketing Business.
 It will help distributers manage their downlines.

 It will help suppliers to manage distributers.
 It will also help suppliers to sell their products online.
 Helps to grow business.
176
REFERENCES
177
REFERENCES
 “Database system concept” by Abraham Silberschatz, Henry Korth & S.

Sudarshan.
 WWW.TUTORIALSPOINT.COM
 WWW.ANDROIDDEVELOPERS.COM
 WWW.JAVATPOINT.COM
 “Software Engineering” by P. Jalot.
 Sharing Knowledge from my Co-ordinator.
178
CURRICULUM
VITAE
179
CURRICULUM VITAE
Neetesh Kumar Singh
Add: 1015/b2, Naibasti, alinagar
Pin code: 232101
Mobile No.: - 7651897693
Email ID: nitesh.singh1015@gmail.com
CAREER OBJECTIVE
To build career in a growing organisation, where I can get the opportunities to prove my abilities
by accepting challenges, fulfilling the organisational goals & climb the career ladder through
continuous learning and commitment.
ACADEMIC QUALIFICATION
 10th Passed from Adarsh Vidya Niketan Sr. Sec. school, Faridabad, CBSE Board.
 12th Passed from Gandhi Rashtriya Inter College, Sadalpura, Mughalsarai, UP Board.
 Graduation with BCA from Institute of Computer Science & Tech., SHEPA, Varanasi,
MGKVP university.
 Pursuing MCA from Institute of Computer Science & Tech., SHEPA, Varanasi, AKTU
Lucknow.
EXTRA QUALIFICATION
 “EICS (Effective Industrial Communication Skills)” from Society for higher Education &
Practical Application (SHEPA), Varanasi.
 “CCA (Certificate in computer application)” from soft-tech development solution.
 “DICHN (Diploma in Computer Hardware & Networking)” from Soft-tech Development
Solution.
1
PROJECTS
Built a helpline Android application named “Parivartan (Ek Salah)” during my academic
Session.
INDUSTRIAL TRAINING & SEMINAR
 6 Months training on “Internet Technology” in “DEE Development Engineers Ltd.”, Prithala,

Haryana.
 Attended a seminar on “IOT (Internet of Things)” by Dr. Neelendar Badal (Professor) KNIT,
Sultanpur.
SPECIALIZATION
HTML & CSS, Computer Fundamentals, MS-Office, JAVA, Android.
PERSONAL SKILLS
 Honesty
 Team spirit
 Accepting Challenges
PERSONAL PROFILE
 Father’s Name Om Prakash Singh

 Date of Birth 23 July 1996
 Sex Male
 Marital Status Unmarried
 Language Known English & Hindi
 Nationality Indian
2
DECLARETION
I solemnly declare that all the above information herein is correct to the best of
my knowledge and belief.
Date:
Place: (NEETESH KUMAR SINGH)

MLM PDF

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

MLM PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

I

Mini Project Report On

Institute of Computer Science & Technology, Code 107

SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF

Master of Computer Application

NEETESH KUMAR SINGH, 1810714905

Under the supervision of

Dr. A. P. J. Abdul Kalam Technical University, Lucknow

Institute Of Computer Science & Technology, College Code 107

Neetesh Kumar Singh Gaurav Pandey

MCA 4th (Sem) MCA 4th (Sem)

NEETESH KUMAR SINGH

MCA 4TH SEM

Table no. Table caption Page no.

1 ACTOR’S GOAL TABLE 15

2 FEEDBACK RECORD TABLE 31

4 DISTRIBUTER RECORD TABLE 33

6 AUTHENTICATION TABLE STRUCTURE 35

Fig. NO. Figure caption Page No.

1. CASE DIAGRAM OF DISTRIBUTER 13

2. CASE DIAGRAM OF SUPPLIER 14

9. 2-LEVEL DFD (for Distributer) 22

10. 2-LEVEL DFD (for Supplier) 23

11. STRONG ENTITY SET 24

13. KEY ATTRIBUTES 25

14. COMPOSITE ATTRIBUTES 25

15. MULTIVALUED ATTRIBUTES 25

18. ONE TO ONE RELATIONSHIP 27

19. ONE TO MANY RELATIONSHIP 27

20. ONE TO MANY RELATIONSHIP 28

21. MANY TO MANY RELATIONSHIP 28

22. ENTITY RELATIONSHIP DIAGRAM 29

HTML HYPERTEXT MARKUP LANGUAGE

Topic of the project:

MLM Terms to Know:

Network Marketing: Multi-level marketing is sometimes referred to as network marketing as

Need of MLM Mobile Apps in Network Marketing Business

Empowering your MLM Business with Infinite MLM Apps

Main features in our MLM software Mobile Application

Bonus: Bonus and new joining information details.

Feedback: To compose, send and read Feedbacks.

Points: Shows sales report Points.

Profiles: Shows the user information.

Downline: Shows the distributers joined below the user.

Contact: Shows the Contact Details Of the head office.

Company: To explain About & Management informations of the company.

Purchase: Gives the facility to order products online.

Objectives of MLM App

 To Make the Business Digital.

Purpose of Use Case Diagrams

In brief, the purposes of use case diagrams can be said to be as follows −

 Used to gather the requirements of a system.

 Used to get an outside view of a system.

 Identify the external and internal factors influencing the system.

 Show the interaction among the requirements are actors.

 Functionalities to be represented as use case

 Relationships among the use cases and actors.

 Give a suitable name for actors.

 Show relationships and dependencies clearly in the diagram.

 Use notes whenever required to clarify some important points.

Supplier Manage Distributers User

Supplier Add Products Products