This project is on android OS

1. Personal Assistant
R2D2
By:-
Mohd. Amir Nazim,
Kapil

2. Table of Contents
Table of Contents
1. Introduction 1
1.1 Purpose 1
1.2 Document Conventions 1
1.3 Intended Audience and Reading
Suggestions 1
1.4 Project Scope 1
1.5 References 1
2. Overall Description 2
2.1 Product Perspective 2
2.2 Product Features 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
2.7 Assumptions and Dependencies
3

3. 3. System Features 3
3.1 System Feature 1 3
3.2 System Feature 2 (and so on) 4
4. External Interface Requirements 4
4.1 User Interfaces 4
4.2 Hardware Interfaces 4
4.3 Software Interfaces 4
4.4 Communications Interfaces 4
5. Other Nonfunctional Requirements
5
5.1 Performance Requirements 5
5.2 Safety Requirements 5
5.3 Security Requirements 5
5.4 Software Quality Attributes 5

4. 1. Introduction
• The Project is developed in Java Programming
Language by using the Android Studio,
Integrated Development Environment (IDE).
• We use the Android Software Development
Kit (SDK) which includes a variety of custom
tools that help us develop mobile applications
on the Android platform.
• The most important of these are the Android
Emulator and the Android Development Tools
(ADT) plug-in for Android Studio.

5. 1. Introduction

6. 1. Introduction
1.1) Purpose
Analyze and Monitor the Logical & Reading Abilities.
Help disabled to access the latest technologies.
Improve Efficiency & Effectiveness for users.
To be helpful to the people while driving.

7. 1.2) Document Convention
Font Family-
Calibri(body)
Font Size-
Heading –32 , Paragraph-28
Font Colors-
Content- Dark Grey

8. 1.4) Project Scope
 It contain all the information of ability analyzers
users who are registered on this website.
 It should process and evaluate requests submitted by the
user.
 It should provide Learning Material to enhance students
ability.
 It should process and evaluate requests submitted by user.
 It have an administrator for viewing feedbacks and updating
necessary updates for the test engine.

9. 2.1) Product Perspective
Ability analyzer is not a standalone project and a
self-contained product.
Combination of 5 modules:
 Different modules interact with each other to
facilitate communication via message sending
and document sharing.
 A user may have to visit different portals for
different types of ability analysis, which
becomes a hectic process. This website provides
every component in a single compact and
integrated environment.

10. 2.2) Product Features
The ability analyzer site is a special purpose web site as
discussed above.
The site includes the search engine and advance search
engine which gives the users easy way to find the
material at home.
The site acts as a Test Engine for analyzing the all round
skills of children.

11. 2.4) Operating Environment
Server
Browser : IE 6.0 or later
Database : SQLite
Web server : Internet Information Server (IIS) 7.0
Operating System : Windows
Client
Browser : IE 5.0 or any browser
Operating System : Android
Developer
Browser : IE 6.0 or any browser
IDE : Android Studio
Database : SQLite
Operating System : Window 7 or Higher
Web server : Internet Information Server (IIS) 7.0
Documentation tool : Ms Word, MS power point

12. 2.5) Design & Implementation Constraints
 CO-1 Minimum 512MB RAM is required at server side
 CO-2 Minimum 512MB RAM is required at client side
 CO-3 Must JavaScript as Scripting language since it’s better
compatibility towards Java platform.
 Co-4 Compatibility is only tested and verified for Android
OS.

13. 2.6) User Documentation
 Online Help-
It provides assistance to the end user about the flow of
the system as well as enhance the understandability of
the proposed system.
 Manual-
We also provide manuals to facilitates the end user to
handle over heading .

14. 3. System feature
3.1) Description & Priority
After registration user can give
voice/text commands to the
system as well as give Admin
precious feedback about the
application.
Can view feedback given by the
users and use it to further
enhance the application.
Users
Admin

15. 3.3) Functional Requirement
Sr.N
o.
Req.
No.
Priorit
y
Requirement
1. R1.1 R User Registration & Login
2. R1.2 O Manage Profile
3. R1.3 R User Queries
4. R1.4 O Reply by the Administrator
5. R1.5 R Test Engine Maintenance
6. R1.6 C View Test Records
7. R1.7 O Proper suggestions and feedback
of the users.
8. R1.8 O Reading Material Request
9. R1.9 R Proper updating & modification
10. R1.10 R Proper user records will be
maintained

16. 4. External Interface Requirements
4.1) User Interface

17. 4. External Interface Requirements
4.2) Hardware Interface
Client:
 Processor : P3 866 MHz or later
 RAM : 512 MB
 HDD : 40GB
 Display : 1024 x 768 High
color-64-bitSOFTWARE

18. 4. External Interface Requirements
4.3) Software Interface
Client
 Browser : IE 5.0 or any browser
 Operating System : Android O.S.

19. 6. Other Functional requirement
Gantt Chart
January Fabruary march April may
Requirement
Gathering
Design
Coding
Test cases
Testing
Implementation

20. 6. Other Functional requirement
Spiral Model

21. Project Life cycle
• Profile Management System
• User Command Management
• Preferences Management
• History Management
• Storage Management
Modules:

22. User
Admin
0
Personal
Assistant
Database
Feedback
Update Notification
User Info
Commands
login
Verification code
Reviews
DATA FLOW DIAGRAM 0 Level

23. DATA FLOW DIAGRAM
User
AdminUser info
User login
Verified
code User input commands
Custom Command
Change Settings
Settings notification
View History
Save Data
Requested
data
Login
commands
Settings
History
Storage
Management
User records1.0
Profile
Management 2.0
Command
Management
3.0
Preferences
Management
4.0
History
Management
5.0
Storage
Management
1 Level

24. DATA FLOW DIAGRAM
User
User _info
Email activation link
Confirmation_massege
Login
Update user info
User info
1.1
User
Registration
1.2
Login
1.3
Update info
1 Level

25. DATA FLOW DIAGRAM
User
Text commands
Response data
New custom command
commands
Custom
Command
2.1
Command
System
2.2
Custom
Commands
1 Level
Voice Command

26. DATA FLOW DIAGRAM
User
Display Data
Sound data
Network data
mode Data
Settings
3.1
Appearance
Settings 3.2
Sound
Settings
3.3
Network
Settings
3.4
Conversation
Mode
Settings
1 Level

27. DATA FLOW DIAGRAM
User
Save File data
Retrieve File data
User info
Update setting data
Storage
5.1
File Storage
5.2
User profile
Data
5.3
Settings Data
1 Level

28. DATA FLOW DIAGRAM
User
Respond feedback
View Feedback
Send Reviews
Give ratings
Feedback
5.1
Feedback
5.2
Reviews
5.3
Ratings
1 Level
View Reviews
View Ratings
Admin
Respond feedback
View Feedback

29. ENTITY RELATIONSHIP
DIAGRAM
Admin Login
Registered User
Commands
Feedback
History
HAS
Vi
e
w
Manage
VIEW
Perform
Admin id Password
Login id Password
User id email User name Command id
Command
type
History id
History
date
Feedback
id
User name
SEND

30. Table Structure
User Registration:
Attributes Data Type Size Description
_Userid integer 30 Primary key
Email Varchar 40 Email address of the
user.
Username Varchar 50 Use to login.
Password Varchar 64 Used for security.

31. Table Structure
User Commands:
Attributes Data Type Size Description
_Commandid integer 30 Primary key
Command_type Varchar 40 Voice or text
command
Command_name Varchar 40 Predefined
commands

32. Table Structure
Settings:
Attributes Data Type Size Description
_Settingsid integer 30 Primary key
Settings type Varchar 40 Eg.- profile,
network, etc..
Default Settings Varchar 50 Predifined settings

33. Table Structure
Feedback:
Attributes Data Type Size Description
_Feedbackid integer 30 Primary key
User_name Varchar 40 To access/login.

34. User Interface
This is the starting screen of the
application.
It shows the logo of the
application.

35. User Interface
This is the second screen of the
application.
It helps to sign up or sign in to the
application.
This screen appears only once after,
installing of the application

36. User Interface
This is the sign up screen of the
application.
It helps to sign up for the
application.
This screen appears while making
a new id/user to the application.

37. User Interface
This is the sign in screen of the
application.
It helps to sign in to the
application.
This screen appears while signing in
to the application.

38. User Interface
This is the action screen of the
application.
It helps to give voice commands to
the application.

39. User Interface
This is another action screen of the
application.
It helps to give text commands to
the application.

40. Future Scope
• Can further enhance to more easily access
to every function of Android OS systems.
• Handicapped people can use
mobile/tablets more effectively.
• Useful for the users while driving car/bikes.

41. Conclusion
• Based on the fact that R2D2 offers a good
interactivity with existing functionality, I can
assume that it has a good chance to grab many
users.
• By observation I can conclude that R2D2 with no
restriction and good audio support will make
environment for busy and handicapped people.
• This is for making easy access to mobile
functionality where the user can access to the
internet, make calls, send
messages, etc..

42. References
• Trainers.
• Google.
• slideshare.com
• Books.