Table of Contents

Table of Contents ii

1. Introduction 1
1.1 Purpose 1
1.2 Document Conventions 1
1.3 Intended Audience and Reading Suggestions 1
1.4 Product Scope 1
2. Overall Description 2
2.1 Product Perspective 2
2.2 Product Functions 2
2.3 User Classes and Characteristics 2
2.4 Operating Environment 2
2.5 Design and Implementation Constraints 2
2.6 User Documentation 2
3. External Interface Requirements 3
3.1 User Interfaces 3
3.2 Hardware Interfaces 3
3.4 Communications Interfaces 3
4. System Features 4
4.1 Team management 4
4.1.1 Description and Priority 4
4.1.2 Functional Requirements 4

5. Other Nonfunctional Requirements 4

5.1 Safety Requirements 5
5.2 Security Requirements 5
5.3 Software Quality Attributes 5
5.4 Business Rules 5
6 User case 6
7 Design 7
8 Conclusion
1.Introduction:
Whoever out there runs a droid business, free robots and science website
template, Robotics, is your number one tool to give your products an extra shine.
Not just your products but your services, too. All there is you need to make is a
sophisticated website and you are on the right path to attain the goals you have
for your business. It is Robotics template which covers the web design of your
page and makes your grand work beautifully appear online.
Whether robots will ever replace human power entirely is still a mystery, you can
replace building a site from scratch with Robotics. Powered by Bootstrap
Framework, carefully designed, strategically optimized and mobile and browser
compatible, Robotics is all you need.
1.1 Purpose:
As Robots are our upcoming technology in 21st century. As technology increasing
day by day. We decide to introduce to new technology of robotics that there are
many robots introduce in this website its purpose to aware the people to new
technology which provide a facility to the people in their homes, offices and on
more places.
1.2 Document Conventions:
Use the font style as follow:
⦁ Heading Calibri(body)
⦁ Sub-Heading Calibri(body)
⦁ Text Calibri(body), italic
⦁ Font size will be used as follow
⦁ Heading 18
 ⦁ Sub-Heading 14
⦁ Text 14

1.3 Intended Audience and Reading Suggestions:

⦁ Advisers.
⦁ Class Mates.
⦁ Other advisers.
⦁ Head of Department (CS).

1.4 Product Scope :

Community is always in hunger for official communities to entertain people, some
goes on for new technology. So that everyone can have opportunity to enhance
their knowledge about technology so here it is a short kind of website.
This Project is the right way to make them grow by taking this initiative. On
surveys we come to know that the community will adopt such a platform with
happy faces.
2. Overall Description :

2.1 Product Perspective :

Our idea is a newly generated and unique. A self-contained product that solves a
single problem of community which has never been solved before. In a world of
technology, nowadays, there is a huge population which has smart phones or are
connected to technology through any of the devices. We can use it to help
community in many ways and we found less awareness problem in our
community. Here we are providing its solution.

2.2 Product Functions :

⦁ User must be created in the service.
⦁ Information uploading service should be available.
⦁ User should be knowledge of technology.
⦁ Service must let user to upload their requirement request.
⦁ And there must be a information searching option for user of our service.
⦁ A Help section must be provided for the user.
⦁ Last but not the least, their must be a way to get feedback from user.
2.3 User Classes and Characteristics :
⦁ Interested person or people interested in technology will be the user of our
web app.

2.4 Operating Environment:

As our software is a web service, we will provide a website that will be accessible
from any device i.e. Laptop, Mobiles and other personal computers.

2.5 Design and Implementation Constraints:

⦁ A device with working internet connection will be required to run our services.
⦁ Single user can create a single request.

2.6 User Documentation:

Our website itself will declare all the user required information and a complete
help service for the user.

3.External Interface Requirements:

3.1 User Interfaces:

Our project will have a standard website design some of its screen shots are
attached below.
3.2 Hardware Interfaces:
Our project is a software-based website, so no hardware interface is present.
3.3 Communications Interfaces:
For the verification of name and email service will be used.

4. System Features:
Opens APIs that quickly connect to your existing services.
Actionable helps to find the intelligence that automatically find the processes to
optimize.
The adaptive intelligence that learn on the fly.
it gets complete details of how work done.

4.1 Team Management:

To provide people a unique opportunity to learn technical skills in a business
setting.

4.1.1 Description and Priority:

In today's world of technology this websites rates on high priority. It makes
people aware to new technology day by day and inspire people from robotics that
how much they can be useful in our lives.
4.1.2 Functional Requirements:
  The robots should be able to go undetected in any situation.
 The robots should be able to control within its specific range of 30m and
video transmitted without any disturbance.
 The program should be able to detect any sort of visibility.
 Some of robots can behave like a human and can understand of things
which are programmed in it.
 Some of functional requirements are the link of website:
1. name
2. address
3. email
4. message

5.Other Nonfunctional Requirements:

Non-functional requirements are security for the control of a robots password
protected and validate robots information about the bombs and human
detection.

5.1 Safety Requirements:

There are the robot cells in which working have been done. Modern robots are
almost silent in operation and very fast. The only way to keep safe the robots is
exclude the people from robots working area. and to keep the web safe from
others we need a specific drive to keep our code safe.

5.2 Security Requirements:

Security requirements is to keep password on the laptop and hardrive or the thing
in which our website is kept safe. our web is ulterly secure. No one can change
the data expect admin. The system should only accept authorized and authentic
user information. Sensitive information of the user should not be accesible to
authorized person. information should not be distorted during its transmission
over the internet.
5.3 Software Dependency:
People have to visit the website and share its link to more and more people.

5.4 Business Rules:

Through this website we can sell our products to other people they can visit our
website and send their messages and requirements about their products it is
beneficial for the people who wants to sell their products to others they can
contact us and we convey their messages through this website.

6.Use Cases Of our project:

Use Case ID: UC-1
Use Case Name: Open The Website
Description: They are able to visit the website.
Primary Actor: User, Admin, Subscriber
Pre-Condition: They should have a device capable to internet browsing. They
can visit the website through laptops.
Post-Condition: Enters the URL to visit the website.
Basic Flow:
1. Actor Action:
⦁ They should have a laptop/computer.
⦁ The device has connectivity to internet.
⦁ Type website URL in address bar.
2.System Action:
⦁ Website gets opens successfully.
Alternate Flow:
⦁ Their device is not connected to internet
⦁ They mistype URL of website. Results in DNS error.

7.Design:
In this section, we provide the design analysis of our modules including the
following designs
⦁ Architecture Diagram
⦁ Data Flow diagram

7.1 Architecture Diagram:

Define the graphical representation of the concepts, their principles, elements
and components that are part of your project.
7.2 Data Flow diagram:
Data flow diagram includes two levels
· The level 0

8. Summary and Conclusion:

 It has been a great pleasure for us to work on this exciting and challenging
project. This project proved good for us as it provided practical knowledge of
programming in PHP and Android and also about all handling procedure related
with our project. It also provides us knowledge about the latest technology used
in developing that will be helpful in future. While working on this project the main
thing we learnt is to stick with your plan. We have also learnt many new tools
which is most exciting thing for us. We have learnt much about software
engineering documentation. Before entering into professional life this project
showed us a way to enhance our communication skills and focus towards the
goal. This would be really very helpful in our future working environment. The
main objective of this application is to enhance business over the internet. The
interface of the application is very user-friendly and even a basic skilled person
can use this with ease. The registered user can perform variety of action on their
phones from any place. And they can keep their phone secure. Moreover, the
layout of application is fully responsive such that the customer will feel ease while
using the application. We have developed our application successfully with
decided features and within time.

USE CASE DIAGRAM:

Use Cases of Robots Details and sale website:

Actors:
• Admin of website

Use Cases:
• Admin manages the website
• Admin Login and Log out.
• Admin can Update profile.
• Admin can Change password.

Description:
Use Case name: Manage the website

Primary Actor: Admin of the website

Goal in context: To manage the website which includes management of Robots,
Order, Customer, Users.
Preconditions: Website can be opened in any electronic device i.e. Mobile
phones, Computers, Laptops etc. having an internet connection.
Trigger: Admin can manage the website.
Scenario:
• Admin opens the website on any device.
 • Admin deals with the management of everything on website.
• upcoming robots
• Customers
• Users
• Orders
• Admin exits from website.

Use Case name: login and log out from website

Primary Actor: Admin.
Goal in context: To login and log out from website.
Preconditions: Website can be opened in any electronic device i.e. Mobile
phones, Computers, Laptops etc. having an internet connection.
Trigger: Admin log in and logout to website.
Scenario:
• Admin opens the website on any device.
• Admin clicks the log in/sign up button on the home page and the log in/sign
up page loads.
• Admin enters the required details and press log in/ sign up button.
• The homepage opens after login.
• After managing website Admin can logout.

Use Case name: Update profile

Primary Actor: Admin
Goal in context: The goal is to update the profile.
Preconditions: Website can be opened in any electronic device i.e. Mobile
phones, Computers, Laptops etc. having an internet connection.
Trigger: Admin wants to update profile.
Scenario:
• Admin is logged in.
• To update profile, Admin clicks the button “UPDATE PROFILE” to update
the profile.
• Admin enters the required information which he wants to update.
• After updating, Admin can logout.

Use Case name: Change password

Primary Actor: Admin of the website.
Goal in context: Admin can change the password of his/her account.
Preconditions: Our website is opened on the device and the account of Admin
must be logged in.
Trigger: Admin wants to change password of his/her account.
Scenario:
• Admin accesses the website.
• Admin opens his/her account on the website.
• Admin clicks “Change Password” button.
• Admins changes the password of his/her account.
• After that Admin logs out.

Actors:
• User of website

Use Cases:
• User visits the website

Description:
Use Case name: Visit Website
Primary Actor: User of the website
Goal in context: To visit the website which includes searching of robots and detail
of robots and upcoming robots.
Preconditions: Website can be opened in any electronic device i.e. Mobile
phones, Computers, Laptops etc. having an internet connection.
Trigger: User can manage the website.
Scenario:
• User opens the website on any device.
• User logs in.
• User go through the website to search about robots and can place their order
• User exits from website.

Use Case name: Login and Log out from website

Primary Actor: User
Goal in context: To login and log out from website.
Preconditions: Website can be opened in any electronic device i.e. Mobile
phones, Computers, Laptops etc. having an internet connection.
Trigger: User logs in and logs out of website.
Scenario:
• User opens the website on any device.
• User clicks the log in/sign up button on the home page and the log in/sign up
page loads.
• User enters the required details and press log in/ sign up button.
• The homepage opens after login.
• After managing website User can logout.
Use Case name: Update profile
Primary Actor: User
Goal in context: The goal is to update the profile.
Preconditions: Our website has been opened on a computer.
Trigger: User wants to update profile.
Scenario:
• User is logged in.
• To update profile, User clicks the button “UPDATE PROFILE” to update the
profile.
• User enters the required information which he wants to update.
• After updating, User can logout.

Use Case name: Change password

Primary Actor: User of the website.
Goal in context: User can change the password of his/her account.
Preconditions: Our website is opened on the device and the account of User must
be logged in.
Trigger: User wants to change password of his/her account.
Scenario:
• User accesses the website.
• User opens his/her account on the website.
• User clicks “Change Password” button.
• User changes the password of his/her account.
• After that User logs out.

Actors:
• Customer of website
Use Cases:

• Customer Enter their email

• Customer makes order.
• Customer makes payment

Description:

Use Case name: Login and Log out from website

Primary Actor: Customer
Goal in context: To Login and Log out from website.
Preconditions: Our website has been opened on a computer.
Trigger: Customers Logs in and Logs out to website.
Scenario:
• Customer opens the website on any device.
• Customer clicks the log in/sign up button on the home page and the log in/sign
up and webpage loads.
• Customer enters the required details and click log in/ sign up button.
• Then customer place their order.

Use Case name: Change password

Primary Actor: Customer of the website.
Goal in context: Customer can change the password of his/her account.
Preconditions: Our website is opened on the device and the account of Customer
must be logged in.
Trigger: Customer wants to change password of his/her account.
Scenario:
• Customer accesses the website.
• Customer opens his/her account on the website.
• Customer clicks “Change Password” button.
• Customer changes the password of his/her account.
• After that Customer logs out.

Use Case name: Make Order

Primary Actor: Customer of the website.
Goal in context: Customer can make orders of robots.
Preconditions: Website should be opened on the device and the account of
Customer must be enter their email.
Trigger: Customer wants to make orders from his/her account.
Scenario:
• Customer accesses the website.
• Customer opens his/her account on the website.
• Customer clicks “Make Order” button.
• Customer makes the order which he wants.
• After that Customer exists website.