srs document

Smart Phone: Apps Locker 2014

ContentsCONTENTS 1

1. INTRODUCTION 2

1.1 PURPOSES 21.2 DOCUMENT CONVENTIONS 21.3 INTENDED AUDIENCE AND READING SUGGESTIONS 21.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS 21.5 SCOPE 31.6 REFERENCES 3

2. OVERALL DESCRIPTION 3

2.1 PRODUCT PERSPECTIVE 32.2 PRODUCT FUNCTIONS 32.3 USER CLASSES AND CHARACTERISTICS 32.4 OPERATING ENVIRONMENT 32.5 DESIGN AND IMPLEMENTATION CONSTRAINTS 42.6 USER DOCUMENTATION 42.7ASSUMPTIONS AND DEPENDENCIES 4

3. EXTERNAL INTERFACE REQUIREMENTS 4

3.1 USER INTERFACES 43.2 HARDWARE INTERFACES 53.3 SOFTWARE INTERFACES 53.4 COMMUNICATIONS INTERFACES 5

4. SYSTEM FEATURES 5

4.1 SYSTEM FEATURE 1 6 4.1.1 DESCRIPTION AND PRIORITY 6 4.1.2 STIMULUS/RESPONSE SEQUENCES 6 4.1.3 FUNCTIONAL REQUIREMENTS 74.2 SYSTEM FEATURE 2 AND SO ON 7

5. OTHER NON-FUNCTIONAL REQUIREMENTS 7

5.1 PERFORMANCE REQUIREMENTS 75.2 RELIABILITY 85.3 PORTABILITY 8

6. OTHER REQUIREMENTS 8

APPENDIX: GLOSSARY 8

1


1. Introduction1.1 purposesAppLock is the smart phone app which helps you to lock the following apps that mostly installed on your smart phone.

SMS Contacts Gmail Facebook Gallery Market Calls and any app you choose with abundant option protecting your privacy

AppLock can hide your pictures and videos. AppLock empowers you to control photo and videos access. Selected pictures vanish from your photo gallery, and stay, with App Lock only you see your hidden pictures.

1.2 document conventions Main headings: Bold Font size:Heading1(14),Heading(12) bullet points

Main headings: Bold because user can easily distinguish it from others subheadings. Bullets use to identify special information about the app. The rest of the document is written in Times New Roman.

1.3 intended audience and reading suggestions

The SRS document is used to inform the reader for approaching App lock of smart phone application and how he can use it efficiently; the reader will get a general understanding of the product including its functional and non-functional requirements as well and its features.

The different types of audience are Customers: Those who only use the app Developers: Those who both use the app as well as edit the app. Smart Phone Users: Those who only use the app not edit the app.

1.4 definitions, acronyms and abbreviationsLR: Locker RoomAD: App DirectoryASM: App Security Management System

It consists of

Pin code Username Pattern etc

2


1.5 ScopeThis application will run on a mobile platform (Android). And this help will help to protect and secure the important contacts, SMS, videos, pictures and other important applications. App is based on these two aspects.

privacy Security

1.6 Referenceswww.google.comwww.slideshare.com

2. Overall Description

2.1 Product PerspectiveThe Smart Phone APP Locker is intended to provide the extra security for smart phones Apps. We know that security system is by default present in all smart phones but this App locker provides the security to every app that run on the smart phone like Facebook, Antivirus, Google Maps, Messaging, Videos, and Pictures etc. Main purpose is to increase the security Level.

2.2 Product FunctionsSecurity is the main function of This App other then this, it provides these feature as well.

Control the level of protection required. Protect apps via Fake crash only or PIN only or a combination of the two methods.

Fast and smooth user interface with quick search functionality. Completely free! Bonus feature: AppLock features a built-in Fast Uninstaller for quickly uninstalling

multiple apps!

2.3 User Classes and CharacteristicsUsers of this App locker are those who use the Smart Phones like customers, Users, developers, designers etc but they have some special characteristics related to the App.

Customers: Those who only use the app Developers: Those who both use the app as well as edit the app. Designer: Those who edit, use and change the design of app. Smart Phone Users: Those who only use the app not edit the app.

2.4 Operating EnvironmentMart Phone app Locker will run on Android Technology Phones I.e.

Samsung Nokia

3

http://www.slideshare.com/

http://www.google.com/


Q Mobiles etc

2.5 Design and Implementation Constraints The time allotted for this project will be limited to the end of this semester. The language for the project will be Visual C++ and the development environment will be the

embedded Visual C++ 3.0 environment. All the HTML code for the user manual will conform to the HTML 4.0 standard. Programming is done in JAVA, SQL.

2.6 User DocumentationThe system will provide an online user manual in HTML that describes the functionality and options available to the user on these websites www.slideshare.com and www.google.com.

2.7Assumptions and DependenciesThe database mentioned within this Software Requirements Specification document is previously administered with the correct information needed when your enable protection on any app. You need to ensure that the password you entered in correct and have a backup plan when you lost your password due to some reason. You should have a backup up plan for this.

3. External Interface Requirements

3.1 User Interfaces App Locker provides the security management system for the entire apps that are

running on the smart phone. Touch screen Mobile Users i.e. Samsung, Apple, iphone etc use this app, so the User

interface will be critical.

4

http://www.google.com/

http://www.slideshare.com/


All the modification to apps enabling or disabling done through app locker settings. The User Input should be displayed in the application.

3.2 Hardware InterfacesApp will run on the following smart phone brands

Samsung Q-Mobiles Nokia etc

The app should be extended to the many services if required. (Scalability) The user interface communicates with some specific keypad. The user can use this app without internet connection.

3.3 Software Interfaces Provides security for all the apps running on the phone. For security and protection you need to enable following two things

1. Username2. Password

Username and password can applicable on all app through app locker

3.4 Communications Interfaces Security of Phone is consistent through the use of app locker. The Smartphone App locker will communicate to the database without

Internet; it saves passwords and username in its directory folder. Uninstalling this app will removes all the protection from your apps.

4. System FeaturesAppLock protects selected apps from unauthorized access by faking a crash whenever someone tried to access the protected apps. After you have secured your apps with AppLock, you can gain access to your protected apps by tapping on the fake crash dialog box a preset number of times and entering a secret PIN.

5


4.1 System Feature 1Control the level of protection required. Protect apps via Fake crash only or PIN only or a combination of the two methods.

4.1.1Description and PriorityAuthentication of pin is most important without this it’s useless, so it has a High priority level.

4.1.2Stimulus/Response SequencesOur pictures show the method of protecting and accessing the apps.

6


4.1.3 Functional RequirementsSecurity: The basic purpose for this application is to provide you security form unnecessary access. It asks user for a password to access the locked apps. Its feature includes

Protects any apps using password or pattern Automatic lock at given time Protects your contact lists and your conservations (SMS) and others such as your

gallery, music, videos etc.Hardware requirements: For the hardware requirements this SRS specifies the logical characteristics of each interface b/w the software product and the hardware components. It specifies the hardware requirements like memory restrictions, cache size, the processor, RAM size etc. Required for the application to run.

Minimum Hardware Requirements CPU 830 MHz Internal Capacity (Hard Disk) 512 MB RAM 128 MB Cache 128 KB

Preferred Hardware Requirements CPU 1 GHz Hard disk drive 1 GB RAM 256 MB Cache 512 KB

4.2 System Feature 2 and so on Fast and smooth user interface with quick search functionality. Completely free! Bonus feature: AppLock features a built-in Fast Uninstaller for quickly uninstalling

multiple apps!

5. Other Non-Functional Requirements

5.1 Performance Requirements

User Satisfaction: The application is such that it stands up to the user expectations. Response Time: The response of all the operation is good. This has been made

possible by careful programming. Error Handling: Response to user errors and undesired situations has been taken

care of to ensure that the application operates without nay uncertainty. User friendliness: The application is easy to learn and understand. A native user can

also use the system effectively, without any difficulties. As we provide a step by step tutorials on first use after installation.

7


5.2 ReliabilityThe application is able to avoid or tackle disastrous action. In other words, it should be foul proof. The system safeguards against undesired events, without human intervention.

5.3 PortabilityThe application would not be architecture specific. It would be easily transferable to other different version of androids if needed.

6. Other RequirementsSome other requirements are not covered in the SRS. This might include database requirements, internationalization requirements, legal requirements, reuse objectives for the project, and so on.

Appendix: GlossaryFollowing terms are used in our SRS

LR: Locker RoomAD: App DirectoryASM: App Security Management System

8