A Project Report In An IDP At by Arpita Kapuriya

A Project Report In
An IDP At

by
Arpita Kapuriya (160033107012)
Internal Guide :External Guide :
Prof. Tosal Bhalodiya,Prof. Amit Andipara , Computer Department, Noble Infotech,
A.I.T.S, RajkotRajkot
A Project Submitted
In The Completion Of The Award Of The Degree Of
Bachelor Of Computer Engineering
3084666226496
In Atmiya Institute of Technology and Science, Yogidham Gurukul , Kalawad Road ,
Rajkot , 360005
Gujarat Technological University, Ahmadabad 2018
CANDIDATE’S DECLARATION
I hereby declare that the work presented in this project entitled “All Mobile Scheme Information ” submitted towards completion of project in Seven Semester of B.E. (Computer) at the Noble Infotech, Rajkot , is an authentic record of my original work carried out under the guidance of Prof. Amit Andipara , Project Manager , Noble Infotech, Rajkot.

I have not submitted the matter embodied in this project for the award of any other degree.

Semester: 7th Place : Rajkot
Signature :
Arpita Kapuriya (160033107012)
INDEX
No.

Title Page No.

Certificates I
PMMS Certificate II
Plagiarism Certificate III
Originality of Work V
Acknowledgement VI
Abstract VII
List of Figures VIII
List of Tables IX
List of Abbreviations X
1.0 Introduction 1
1.1 Purpose 2
1.2 Scope 2
1.3 Objective 2
1.4 Technology and Tools 2
2.0 Project Management 9
2.1 Project Planning 10
2.1.1 Project Development Approach and Justification 10
2.1.2 Milestones and Deliverables 11
2.1.3 Roles and Responsibilities 12
2.1.4 Group Dependencies 12
2.2 Project Scheduling 13
2.3 Risk Management 13
2.3.1 Risk Identification 14
2.3.2 Risk Analysis 15
2.4 Estimation 15
2.4.1 Effort Estimation 15
2.4.2 Cost Estimation 15
3.0 System Requirements Study 16
3.1 User Characteristics 17
3.2 Hardware and Software Requirements 17
3.2.1 Server side Hardware Requirement 17
3.2.2 Software Requirements 18
3.2.3 Client side Requirements 18
3.3 Constraints 18
3.3.1 Hardware Limitations 18
3.3.2 Interfaces to Other Applications 19
3.3.3 Reliability Requirements 19
3.3.4 Safety and Security Consideration 19
3.4 Assumption And Dependencies 20
4.0 System Analysis 21
4.1 Study of Current System 22
4.2 Problem and Weaknesses of Current System 22
4.3 Requirements of New System 22
4.3.1 User Requirements 22
4.3.2 System Requirements 23
4.4 Feasibility Study 23
4.4.1 Does the system contribute to the overall objectives of the organization? 23
4.4.2 Can the system be implemented using the current technology and within the given cost and schedule constraints? 23
4.4.3 Can the system be integrated with other
system which are already in place? 24
4.5 Requirements Validation 24
4.6 Features Of New System 25
4.7 Data Flow Diagram 25
4.8 ER Diagram 28
4.9 Selection Of Hardware and Software and
Justification 30
5.0 System Design 31
5.1 Database Design 32
5.2 Input/Output Design 36
5.3 Interface Design 39
5.4 System Structural Design 41
References 42
Appendix A.1 Periodic Progress Report 43
A.2 Ideation Canvas 47
A.4 AEIOU Canvas 48
A.5 Product Development Canvas 49
A.6 Empathy Canvas 50

CERTIFICATE
Date :
This is to certify that the project entitled All Mobile Scheme Information has been carried out by Arpita Kapuriya under my guidance in fulfillment of the degree of Bachelor of Engineering in COMPUTER ENGINEERING (7th Semester) of Gujarat Technological University, Ahmadabad during the academic year 2018-19.

PROF. TOSAL BHALODIYA PROF.TOSAL BHALODIYA
GUIDEHead of CE Department

PLAGARISM CERTIFICATE
UNDERTAKING ABOUT ORIGINALITY OF WORK
We hereby certify that we are the sole authors of this IDP/UDP project report and that neither any part of this IDP/UDP project report nor the whole of the IDP/UDP Project report has been submitted for a degree by other student(s) to any other University or Institution.

We certify that, to the best of our knowledge, the current IDP/UDP Project report does not infringe upon anyone’s copyright nor violate any proprietary rights and that any ideas, techniques, quotations or any other material from the work of other people included in our IDP/UDP Project report, published or otherwise, are fully acknowledged in accordance with the standard referencing practices. Furthermore, to the extent that we have included copyrighted material that surpasses the boundary of fair dealing within the meaning of the Indian Copyright (Amendment) Act 2018, we certify that we have obtained a written permission from the copyright owner(s) to include such material(s) in the current IDP/UDP Project report and have included copies of such copyright clearances to our appendix.

We have checked the write up of the present IDP/UDP Project report using anti- plagiarism database and it is in the allowable limit. In case of any complaints pertaining to plagiarism, we certify that we shall be solely responsible for the same and we understand that as per norms, University can even revoke BE degree conferred upon the student(s) submitting this IDP/UDP Project report, in case it is found to be plagiarised.

Team:
Enroll NoNameSignature
160033107012Arpita Kapuriya
Place:Date
Name Of Guide Tosal Bhalodiya
Signature of Guide
Acknowledgement
It is a matter of immense pleasure for me to submit the project entitled Journey Expense live Calculator to the Gujarat Technological University, Ahmedabad for the partial fulfillment of the Bachelors degree in Computer Engineering.

Our institute which is established by H.D.H. Hariprasad Swamiji. has now proved to be a blessing for entire state. His persistent efforts and dedication towards youths has established the recognition of the institute as ‘A place to learn and a chance to grow with divinity’. I owe my sense of gratitude towards him for showering his divine blessing on me to accomplish this herculean task.

I am highly obliged to P. Tyagvallabh Swamiji whose kind words always prove to be a source of inspiration for the student fraternity.

This project has been prepared under the ablest guidance of Prof. Tosal Bhalodiya of Department of Computer Science ,Atmiya Institute of Technology and Science, Rajkot. Without her keen interest and profound knowledge of the subject and constant encouragement this would not have taken shape.

I am also grateful to Prof. Tosal Bhalodiya , Head of the Department and all the faculty members of the Department of Computer Science for their kind support throughout this journey.

I also take the privilege to acknowledge the elite authors of numerous books and papers that I have referred to prepare this report.

I take the opportunity to thank all those who have directly or indirectly helped me to fulfill the challenging mission.

Arpita Kapuriya
ABSTRACT
We are going to create project on android and we want to make project which helps in real life that’s why we choose all mobile scheme information related system because in real life in India there is no application that helps us to find that all mobile scheme in one place all information. If any person wants to take any information about any scheme then they visit different sites that’s scheme available or not?
Using our app that is possible in our application there is mainly two part one is app and one is android, android is for normal user and web for admin, when any new scheme come that record and that record we bind with android app so user can easily find.

This solution would hopefully be used by thousands of mobile users worldwide.

List Of Figure
Figure No.

Fig. 2.2.1 Title
Shows timeline chart Page No.

13
Fig 4.7.1 DFD Level-0 25
Fig 4.7.2 DFD Level-1(Admin) 26
Fig 4.7.3 DFD Level-1(User) 27
Fig 4.8.1 ER-Diagram 29
Fig 5.1.1 Data Dictionary 40
Fig. 5.2.1.1 Home Page 35
Fig. 5.2.1.2 Register Page 37
Fig. 5.2.1.3 Login Page 38
Fig. 5.3.1.1 State Diagram 40
Fig 5.4.1 Data System Design 41
Fig A.2 Ideation Canvas 47
Fig A.3 AEIOU Canvas 48
Fig A.4 PDC Canvas 49
Fig A.5 Empathy Canvas 50
Table No Title Page No.

Table 2.1.2.1 Milestones and Deliverables 11
Table 2.1.3.1 Roles And Responsibilities 12
Table 4.9.1 Hardware Requirements 30
Table 4.9.2 Software Requirements 30
HTML Hyper Text Markup Language
CSS Cascading Style Sheet
XHTML Extensible Hypertext Markup Language
XML Extensible Markup Language
SVG Scalable Vector Graphics
XUL XML User Interface Language
JS JavaScript
PDF Portable Document Format
VM Virtual Machine
IDE Integrated Development Environment
SQL Structured Query Language
RDBMS Relational Database Management System
PHP Hyper Text Processor
JYSON JavaScript Object Notation
DFD Data Flow Diagram
UI User Interface
GUI Graphical User Interface
ER Entity Relation
RAM Random Access Memory
CPU Central Processing Unit
O/P Output
IT Information Technology
BMC Business Model Canvas
PDC Product Development Canvas
PDEPatent Drafting Exercise
HRHuman Resource
SMSShort Message Service
PPRPeriodic Progress Report

Chapter 1
Introduction
Purpose
Scope
Objective
Technology and Tool
INTRODUCTION
PURPOSE :
The purpose of this Document is to present the detailed description of the All Mobile Scheme Information. It will explain the purpose, features, scope and interface of the system.

SCOPE :
Users, along with their mobile, would feed data of their expenses to the system. Later on, conclusion of scheme, exhaustive report about the expenses of the mobile can be generated. This solution would hopefully be used by thousands of mobile users worldwide.

OBJECTIVE:
In All Mobile Scheme Information we are actively working on developing a Web and Phone base application to be used specially for scheme during the course of their mobile.

TECHNOLOGY AND TOOLS:
Front End: For designing the structure of the project following technologies are used:
HTML:
Hypertext Markup Language (HTML) is the main markup language for creating web pages and other information that can be displayed in a web browser.

HTML is written in the form of HTML elements consisting of tags enclosed in angle brackets (like <html>), within the web page content. HTML tags most commonly come in pairs like <h1> and </h1>, although some tags represent emptyelements and so are unpaired, for example <img>. The first tag in a pair is the start tag, and the second tag is the end tag (they are also called opening tags and closing tags). In between these tags web designers can add text, further tags, comments and other types of text-based content.

The purpose of a web browser is to read HTML documents and compose them into visible or audible web pages. The browser does not display the HTML tags, but uses the tags to interpret the content of the page.

HTML elements form the building blocks of all websites. HTML allows images and objects to be embedded and can be used to create interactive forms. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. It can embed scripts written in languages such as JavaScript which affect the behavior of HTML web pages.

CSS:
Cascading Style Sheets (CSS) is a style sheet language used for describing
the presentation semantics (the look and formatting) of a document written in a markup language. It’s most common application is to style web pages written in HTML and XHTML, but the language can also be applied to any kind of XML document, including plain XML, SVG and XUL.

CSS is designed primarily to enable the separation of document content (written in HTML or a similar markup language) from document presentation, including elements such as the layout, colors, and fonts. This separation can improve content accessibility, provide more flexibility and control in the specification of presentation characteristics, enable multiple pages to share formatting, and reduce complexity and repetition in the structural content (such as by allowing for table less web design). CSS can also allow the same markup page to be presented in different styles for different rendering methods, such as on-screen, in print, by voice (when read out by a speech-based browser or screen reader) and on Braille-based, tactile devices. It can also be used to allow the web page to display differently depending on the screen size or device on which it is being viewed. While the author of a document Typically links that document to a CSS file, readers can use a different style sheet, perhaps one on their own computer, to override the one the author has specified.

CSS specifies a priority scheme to determine which style rules apply if more than one rule matches against a particular element. In this so-called cascade, priorities or weights are calculated and assigned to rules, so that the results are predictable.

The CSS specifications are maintained by the World Wide Web Consortium (W3C).Internet media type (MIME type) text/css is registered for use with CSS by RFC 2318 (March 1998), and they also operate a free CSS validation service.

JavaScript:
JavaScript (JS) is an interpreted computer programming language. As part of web browsers, implementations allow client-side scripts to interact with the user, control the browser, communicate asynchronously, and alter the document content that is displayed. It has also become common in server-side programming, game development and the creation of desktop applications.

JavaScript is a prototype-based scripting language with dynamic typing and has first class functions. Its syntax was influenced by C. JavaScript copies many names and naming conventions from Java, but the two languages are otherwise unrelated and have very different semantics. The key design principles within JavaScript are taken from the Self and Scheme programming languages. It is a multi- paradigm language, supporting object-oriented, imperative, and functional programming styles.

JavaScript’s use in applications outside of web pages—for example, in PDF documents, site-specific browsers, and desktop widgets—is also significant. Newer and faster JavaScript VMs and frameworks built upon them (notably Node.js) have also increased the popularity of JavaScript for server-side web applications.

JavaScript was formalized in the ECMA Script language standard and is primarily used as part of a web browser (client-side JavaScript). This enables programmatic access to computational objects within a host environment
Java:
Java is the foundation for virtually every type of networked application and is the global standard for developing and delivering embedded and mobile applications, games, Web-based content, and enterprise software. With more than 9 million developers worldwide, Java enables you to efficiently develop, deploy and use exciting applications and services.

From laptops to datacenters, game consoles to scientific supercomputers, cell phones to the Internet, Java is everywhere!
Java is a programming language and computing platform first released by Sun Microsystems in 1995. There are lots of applications and websites that will not work unless you have Java installed, and more are created every day. Java is fast, secure, and reliable. From laptops to datacenters, game consoles to scientific supercomputers, cell phones to the Internet, Java is everywhere!
97% of Enterprise Desktops Run Java
89% of Desktops (or Computers) in the U.S. Run Java
9 Million Java Developers Worldwide
#1 Choice for Developers
#1 Development Platform
Billion Mobile Phones Run Java
100% of Blu-ray Disc Players Ship with Java
5 Billion Java Cards in Use
125 million TV devices run Java
5 of the Top 5 Original Equipment Manufacturers Ship Java ME
Android:
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 another million users power up their Android devices for the first time and start looking for apps, games, and other digital content. Android gives you a world-class platform for creating apps and games for Android users everywhere, as well as an open marketplace for distributing to them instantly.

Android has rapidly become the fastest-growing mobile OS. Every day more than 1 million new Android devices are activated worldwide. Android’s openness has made it a favorite for consumers and developers alike, driving strong growth in app. consumption. Android users download more than 1.5 billion apps and games from Google Play each month.

With its partners, Android is continuously pushing the boundaries of hardware and software forward to bring new capabilities to users and developers. For developers, Android innovation lets you build powerful, differentiated applications that use the latest mobile technologies.

Android gives you everything you need to build best-in-class app experiences. It gives you a single application model that lets you deploy your apps broadly to hundreds of millions of users across a wide range of devices—from phones to tablets and beyond.

Android also gives you tools for creating apps that look great and take advantage of the hardware capabilities available on each device. It automatically adapts your UI to look its best on each device, while giving you as much control as you want over your UI on different device types.

For example, you can create a single app binary that’s optimized for both phone and tablet form factors. You declare your UI in lightweight sets of XML resources, one set for parts of the UI that are common to all form factors and other sets for optimizations specific to phones or tablets. At runtime, Android applies the correct resource sets based on its screen size, density, locale, and so on.

To help you develop efficiently, the Android Developer Tools offer a full Java IDE with advanced features for developing, debugging, and packaging Android apps. Using the IDE, you can develop on any available Android device or create virtual devices that emulate any hardware configuration.

Back End : Back End technologies used in the website are:
SQL:
SQL (Structured Query Language) is a special-purpose programming language designed for managing data held in a relational database management system (RDBMS).

Originally based upon relational algebra and tupple relational calculus, SQL consists of a data definition language and a data manipulation language. The scope of SQL includes data insert, query, update and delete, schema creation and modification, and data access control. Although SQL is often described as, and to a great extent is, a declarative language (4GL), it also includes procedural elements. SQL was one of the first commercial languages for Edgar F. Codd’s relational model, as described in his influential 1970 paper “A Relational Model of Data for Large Shared Data Banks”. Despite not entirely adhering to the relational model as described by Codd, it became the most widely used database language.

SQL became a standard of the American National Standards Institute (ANSI) in 1986, and of the International Organization for Standards (ISO) in 1987. Since then, the standard has been enhanced several times with added features. But code is not completely portable among different database systems, which can lead to vendor lockin. The different makers do not perfectly follow the standard, they add extensions, and the standard is sometimes ambiguous.

PHP:
PHP is a server-side scripting language designed for web development but also used as a general-purpose programming language. PHP is now installed on more than 244 million websites and 2.1 million web servers. Originally created by Rasmus Lerdorf in 1995, the reference implementation of PHP is now produced by The PHP Group. While PHP originally stood for Personal Home Page, it now stands for PHP: Hypertext Preprocessor, a recursive acronym
PHP code is interpreted by a web server with a PHP processor module which generates the resulting web page: PHP commands can be embedded directly into an HTML source document rather than calling an external file to process data. It has also evolved to include a command-line interface capability and can be used in standalone graphical applications.

PHP is free software released under the PHP License, which is incompatible with the GNU General Public License (GPL) due to restrictions on the usage of the term PHP. PHP can be deployed on most web servers and also as a standalone shell on almost every operating system and platform, free of charge.

JSON:
JSON (JavaScript Object Notation) is a lightweight data-interchange format. JavaScript Object Notation, is an open standard format that uses human-readable text to transmit data objects consisting of attribute–value pairs. It is used primarily to transmit data between a server and web application, as an alternative to XML.

Although originally derived from the JavaScript scripting language, JSON is a language-independent data format. Code for parsing and generating JSON data is readily available in many programming languages.

The JSON format was originally specified by Douglas Crockford. It is currently described by two competing standards, RFC 7159 and ECMA-404. The ECMA standard is minimal, describing only the allowed grammar syntax, whereas the RFC also provides some semantic and security considerations. The official Internet media type for JSON is application/json. The JSON filename extension is .json.

It is easy for humans to read and write. It is easy for machines to parse and generate.JSON is a text format that is completely language independent but uses conventions that are familiar to programmers of the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. These properties make JSON an ideal data-interchange language.

JSON is built on two structures:
A collection of name/value pairs. In various languages, this is realized as an object, record, struct, dictionary, hash table, keyed list, or associative array.

An ordered list of values. In most languages, this is realized as an array, vector, list, or sequence.

These are universal data structures. Virtually all modern programming languages support them in one form or another. It makes sense that a data format that is interchangeable with programming languages also be based on these structures.

Chapter 2
Project Management
Project Planning
Project Scheduling
Risk Management
Estimation
PROJECT MANAGEMENT
PROJECT PLANNING
Project Planning is concerned with identifying and measuring the activities, milestones and deliverables produced by the project. Project planning is undertaken and completed sometimes even before any development activity starts. Project planning consists of following essential activities:
Scheduling manpower and other resources needed to develop the system.

Staff organization and staffing plans.

Risk identification, analysis, and accurate planning.

Estimating some of the basic attributes of the project like cost, duration and efforts. the effectiveness of the subsequent planning activities is based on the accuracy of these estimations.

Miscellaneous plans like quality assurance plan, configuration management plan, etc.

Project management involves planning, monitoring and control of the people, process, and the events that occurs as the software evolves from a preliminary concept to an operational implementation. Cost estimation is a relative activity that is concerned with the resources required to accomplish the project plan.

Project Development Approach And Justification:
A Software process model is a simplified abstract representation of a software process, which is presented from a particular perspective. A process model for software engineering is chosen based on the nature of the project and application, the methods and tools to be used, and the controls and deliverables that are required. All software development can be characterized as a problem-solving loop which in four distinct stages is encountered:
Requirement analysis
Design
Coding
Testing
Deployment
Milestones And Deliverables:
Management needs information. As software is tangible, this information can only be provided as documents that describe the state of the software being developed without this information it is impossible to judge progress at different phases and therefore schedules cannot be determined or updated.

Milestone is an end point of the software process activity. At each milestone there should be formal output such as report that can be represented to the management. Milestones are the completion of the outputs for each activity. Deliverables are the requirements definition and the requirements specification.

Milestone represents the end of the distinct, logical stage in the project. Milestone ` may be internal project results that are used by the project manager to check progress. Deliverables are usually Milestones but reverse need not be true. We have divided the software process into activities for the following milestone that should be achieved
Software Process Activity Milestone
Project Plan Project schedule
Requirement Collection User requirements, System Requirements
Data flow analysis DFD, System flow
Design
Database design
User Interface design System Design Document
Implementation
Code for giving security
Code for reports Access Rights Reports Generation
Testing Setting validations and error messages
Table 2.1.2.1 Milestones and Deliverables
Roles And Responsibilities :
This phase defines the role and responsibilities of each and every member involved in developing the system. To develop this system there was only one group with two members working on the whole application. Each member was responsible for each and every part of developing the system. Each of the group members has sufficient knowledge in several programming languages. Our team structure is of mixed control team organization as it consists of both democratic and chief programmer organization.

Task Identification :
Task Person Name
Analysis, Analysis review Arpita Kapuriya
Design, Design Review Arpita Kapuriya
Implementation Arpita Kapuriya
Documentation Arpita Kapuriya
Table 2.1.3.1 Roles And Responsibilities
Group Dependencies :
The structure chosen for the system is the chief programmer structure.

In this system, Chief Programmer team structure is used because in the organization, a senior engineer provides the technical leadership and is designated as the chief programmer. The chief programmer partitions the task into small activities and assigns them to the team members. He also verifies and integrates the products developed by different team members and they work under the constant supervision of the chief programmer. For this system reporting entity represents myself and the role of chief programmer is played by my internal guide.

PROJECT SCHEDULING
The scheduling is the peak of a planning activity, a primary component of software project management. When combined with estimation methods and risk analysis, scheduling establishes a roadmap for project management. The characteristics of the project are used to adapt an appropriate task set for doing work.

Fig. 2.2.1 Timeline chart
RISKMANAGEMENT
Risk management consists of a series of steps that help a software development team to understood and manage uncertain problems that may arise during the course of software development and can plague a software project.

Risks are the dangerous conditions or potential problems for the system which may damage the system functionalities to very high level which would not be acceptable at any cost. so in order to make our system stable and give its 100% performance we must have identify those risks, analyze their occurrences and effects on our system and must prevent them to occur .

Risk Identification :
Risk identification is a first systematic attempt to specify risks to project plan, scheduling resources, project development. It may be carried out as a team process using brainstorming approach.

Technology risk:Technical risks concern implementation, potential design, interfacing, testing, and maintenance problems.

Database Corruptness
Garbage Collection
People Risks:These risks are concerns with the team and its members who are taking part in developing the system.

Leaking an important data
Failure of the administration
Lack of knowledge
Lack of clear product vision.

Technical staff conflict.

Poor communication between people.

Tools Risks:These are more concerned with tools used to develop the system
Tools containing virus.

General Risks:General Risks are the risks, which are concerned with the mentality and resources.

Rapidly changing requirements.

Lack of resources can cause great harm to efficiency and timely productivity.

Changes in requirements can cause a great harm to implementation, designing and schedule of developing the system.

Insufficient planning and task identification.

Decision making conflicts.

Risk Analysis:
“Risk analysis = risk assessment + risk management + risk communication. ? Risk analysis is employed in its broadest sense to include:
Risk assessment
Involves identifying sources of potential harm, assessing the likelihood that harm will occur and the consequences if harm does occur.

For this project It might be:- System Crash.

Risk management
Evaluates which risks identified in the risk assessment process require management and selects and implements the plans or actions that are required to ensure that those risks are controlled.

Precautions taken to make risks minimal are as under:-
Periodical backups are taken to avoid major loss in case of system crash.

Risk communication
Involves an interactive dialogue between stakeholders and risk assessors and risk managers which actively informs the other processes.

Steps taken for risk communication is as under:- Probability of certain risks is negotiated with client.

All the possible risks are listed out during communication and project is developed taking care of that risks.

ESTIMATION
Effort Estimation:
Effort associated with this project is period of our training (i.e. of 9 months).

Cost Estimation:
Estimation of Cost is not provided and not discussed to us as it is against the policy of company and due to some security reason

Chapter 3
SYSTEM REQUIREMENT STUDY
User Characteristics
Hardware and Software Requirements
Constraints
Assumptions and Dependencies
SYSTEM REQUIREMENT STUDY
USER CHARACTERISTIC
User:
How user will interact with the system.

Register
Login
Search
View
Logout
Admin
Login
Manage User
Update Information
Overall Management
HARDWARE AND SOFTWARE REQUIREMENT SPECIFICATION
This shows minimum requirements to carry on to run this system efficiently.

Hardware Requirements:
The major hardware requirements are as follows:
Monitor screen:
The software shall display information to the user via the monitor screen.

Mouse:
The software shall interact with the movement of the mouse and the mouse buttons. The mouse shall activate input and output, command buttons and select options from menus.

Keyboard:
The software shall interact with the keystrokes of the keyboard. The keyboard will input data into the active areas of the GUI.

Power Backup:
The power backup is required for uninterrupted and stabilized power supply.

Phone:
The Phone is required with android operating system with minimum requirement as specified in our project.

Software Requirements:
The major hardware requirements are as follows:
Microsoft Windows XP/Vista/7/8
PHP myAdmin
MySQL
Android Studio
Java Development Kit.

CONSTRAINTS
Hardware Limitations:
The major hardware limitations faced by the system are as follows:
If the original document is not mounted properly, the quality of the image will suffer.

If wrinkle is developed due to folding, then it may blur the image.

If the glass of scanner is not clean the scanning quality may be inferior.

If the scanned image is not appropriately clear the recognition may be erroneous.

If the computer does not support the required software then the system can’t be used.

Interfacing with other systems:
The text file generated as the output of the character recognition should be capable of using it along with other applications as their input.

The functionality of the system should be such that it can be used as sub module of some larger applications.

Reliability Requirements:
Since many users can access the server simultaneously, load on the server becomes very high. Hence, the server should be of enough high configurations. There should be high back up storage and management of huge data for disaster management. For this, proper disaster recovery plan and backup strategies have been made , which has been mentioned in risk management.

The Reliability requirements are the validations used to protect the system against one or more incorrect activities. Without proper validation of the system, the failure possibilities of it grow higher so it is must to understand the proper validation of the system and must implement them. All the required validator controls spend very good role to keep the system secure from any unauthorized or incorrect information.

In all these validation actions if system found one or more entries violating validation rules then user will be warned by proper error messages and the details or the record is not going to be saved until corrections are made to them.

Safety and Security Considerations Safety:
The Safety of the system is about organization part of concern as the system is going to be used in there but the solution for the safety of the system , the source of this website will be kept at more than one place with User Id , password and also in the developer’s backup in case of system crash.

Security:
As a developer of the system we are responsible for providing the system a higher level of security as we all know that either it is a web application or any android application, system must be given a great level of security so that system will be used long last.

User’s information will be kept confidential and hence security was a great part to concentrate for us. We have tried to secure the system from any unauthorized access by providing different users a different user id as per his or her designation. If user is Admin (Top Management), he/she will have all the access, privileges and constraints to use this system. He / She can access the entire database details. He/she is able to modify or delete any record or details from the database. Other users have limited access according to their designation in the organization. Because of limited privileges these other users will not be able to modify or delete other details or records of organization.

ASSUMPTIONS AND DEPENDENCIES
Dependencies :
The entire project depends on end-users operation. They should possess enough knowledge to work with the system.

Assumptions :
End-User is the person having enough knowledge for the project operation.

The PC on which this software is used must meet its minimum requirements in terms of hardware and software.

Only Administrator person has all the privileges.

Supervisor is only allowed to manage his/her own Pop Region information.

The database is correct and up-to date every Time.

The availability and reliability of the system is at the level what user wants in.

The user of the system must beware about the various functionalities of the system and all the operations of it

Chapter 4
System Analysis
Study of Current System
Problem and Weaknesses of Current System
Requirements of New System
Feasibility Study
Requirements Validation
Features Of New System
Data Flow Diagram
ER Diagram
Selection Of Hardware and Software and Justification
SYSTEM ANALYSIS
STUDY OF CURRENT SYSTEM
Current system provides the facility of new scheme of mobile with the help of different web application and android application.

PROBLEMS AND WEAKNESS OF CURRENT SYSTEM
The current system is undoubtedly well-designed for mobile scheme information but it has some following limitations:
Lake of awareness of this system.

Available on different web application and android application so everybody cannot perfectly understand.

Some security related issues may be created.

Current system is not providing all expense categories together.

Current systems do not support both web and phone operating system.

REQUIREMENTS SPECIFICATION
Requirements specification adds further information to the requirements definition.

User Requirements :
Here two types of user can use this project
Admin:
Admin users manage the entire project
Users:
These users can create the profile, view all scheme of different mobile.

System Requirements:
Usability:
The interface should use terms and concepts, which are drawn from the experience of the people who will make most of the system. For example, basic social networking concepts are followed.

Efficiency:
The system should provide easy and fast access.

FEASIBILTIY STUDY
Animportantoutcomeofthepreliminaryinvestigationisthe determination that the system is feasible or not. The main aim of the feasibility study activity is to determine whether it would be financially and technically feasible to develop a project .The feasibility study activity involves the analysisof he problem and collection of all relevant information relating to the product such as the different data items which would be input to the system, theprocessing required to be carried out on these data, the output required to beproduced by the system as well as the various constraints on the behaviour of the system.

Does the system contribute to the overall objectives of the organization?
The main aim of behind development of this system is to provide a web application that all mobile scheme and can be used for practical purposes. So that managing of the all mobile scheme become easy task.

Can the system be implemented using the current technology and within the given cost and schedule constraints?
The system can be easily implemented using existing technology. The technology uses is PHP which is user friendly and freeware. After seeing the functionality that system provides the cost of developing the application does not matter.

Taking the schedule constraints in consideration the time available is approximately 9 months. The time period is enough to develop the system.

Can the system be integrated with other system which is already in place?
Yes, The system can be integrated with other system which is already in place. If other system wants to use our functionality it can be easily integrate.

REQUIREMENT VALIDATION
A requirements validation is concerned to check whether the requirements actually define the system, which the customer wants? Requirements validation is important because errors in requirements document can lead to extensive rework costs when they are subsequently discovered.

We have performed the following validation checks
Validity checks
Check whether the information entered is in valid format.

Consistency checks
A requirement in a document is not conflicting.

Completeness checks
The requirements document includes requirement, which define all functions, and constraints intended by the system user.

Realism checks
Using knowledge of existing technology, the requirements are checked to ensure that they could actually be implemented.

Verifiability
The requirements are given in verifiable manner (e.g.: Using quantifiable measures) to reduce disputes between client and developer.

FEATURES OF NEW SYSTEM
New system is operable on both web and android application.

New system can provide the user`s activities on their websites.

New system is providing all scheme categories together.

New systems do generate report of schemes.

DATA FLOW DIAGRAM
Level-0:
A level 0 DFD, also called a fundamental system model or context diagram represents the entire software element as a single bubble with input and output data indicated by incoming and outgoing arrows, respectively.

Fig. 4.7.1 DFD Level-0
Level-1:
This level of DFD provides more detailed structure. It provides a detailed view of requirements and flow of data from 1 bubble to another.

Admin Side:

Fig. 4.7.2 DFD Level-1(Admin)
User Side:

Fig. 4.7.3 DFD Level-1(User)
ER DIAGRAM
An entity-relationship diagram (ERD) is a data modeling technique that graphically illustrates an information system’s entities and the relationships between those entities. An ERD is a conceptual and representational model of data used to represent the entity framework infrastructure.

The elements of an ERD are:
Entities
Relationships
Attributes
Steps involved in creating an ERD include:
Identifying and defining the entities
Determining all interactions between the entities
Analyzing the nature of interactions/determining the cardinality of the relationships
Creating the ERD

Fig. 4.8.1 ER-Diagram
SELECTIONOFHARDWAREANDSOFTWAREANDITS JUSTIFICATION
The Tables 4.9.1 and 4.9.2 below give idea of the hardware and software required for the system.

Hardware Selection
Hardware Items Requirements Justification
CPU Intel Core3 Duo It Process faster compare to other processor
Memory Minimum 4GB Ram It is the minimum memory required to run website
Display
Minimum 720px display For Output Purpose
Android Phone Memoryforphone
Minimum 512 MB RAM Minimum require to run
application on the phone
Table 4.9.1 Hardware Requirements
Software Selection
Software Items Requirements Justification
Operating System Microsoft XP/7/8 Windows PHP script Can run on this os
Operating System Android 2.3 or high Minimumrequire
application on phone to Run
Table 4.9.2 Software Requirements

Chapter 5
System Design
Database Design
Input/output Design
Interface Design Diagram
System Structural Design
SYSTEM DESIGN
DATABASE DESIGN
As a system data model is derived, many named entities, relationships and so forth will be identified. The names given to the entities should be chosen to give the reader some clues to their meaning. However, further description of the named entities is usually needed to make the model understandable. The description can be informal of the formal, whether which approach is used. It is always worth collecting all the descriptions in a single repository or data dictionary.

A data dictionary is simplistically a list of names used by the system, arranged alphabetically. As well as the name, the dictionary should include a description of the named entity and if the name represents a composite object, there may be a description of the composition. Other information such as the date of creation, the creator, and the representation of the entity may also be included depending on the type of the model which is being developed.

Advantages of using a data dictionary are:
It is a mechanism for name management. Many different people who have to invent names for entities and relationships may develop a large system model. These names should be used consistently and should not clash with their meanings. The data dictionary software can check for the name uniqueness and tell requirements analyst of the name duplications.

It serves as a store of organizational information which can link analysis, design, implementation and evolution. As the system is developed, information is taken to inform the development. New information is added to it. All information about an entity is in one place.

All system names, whether they are names of entities, types, relations, attributes or services should be entered in the dictionary. Support software should be available to create, maintain and interrogate the dictionary. This software might be integrated with other tools so that dictionary creation is partially automated
Database Tables:
Admin:

City:

Company:

Mobile_Scheme:

Scheme_Type:

User:


Fig. 5.1.1 Data Dictionary
INPUT / OUTPUTDESIGN
Design for Website:
Home Page:

Fig. 5.2.1.1 Home Page
Signup Page:

Fig 5.2.1.2 Register Page
Login Page:

Fig 5.2.1.3 Login Page
INTERFACE DESIGN
State-Transition Diagram :
State diagrams show the dynamic behaviour of a system. The diagram shows the various states that an object can get into and the transitions that occur between the states.

Graphical Notation
State:
The state object is a snapshot of an object at a particular point in its life. A state may have an activity describing the function being performed.

Initial State:
3216910930187The initial state is the starting state of the object with reference to the Behaviour that the diagram explains. Each state diagram should have only one initial state.

Final State:
Each final state is the ending state of the object with reference to the behaviour that the diagram explains. There may be multiple final states for an object.

Transition:
The transition link represents the relationship between different states of an object. The transition guard is a condition which limits the cases in which a transition can occur. The transition action is performed during the transition and cannot be interrupted

Fig. 5.3.1.1 State Diagram
DATA SYSTEM DESIGN

Fig. 5.4.1 Data System Design
REFERENCES
Bibliography:
Wrox Press Beginning Android 4 Application Development (2012)
Beginning PHP, Apache, MySQL Web Development by Michael K. Glass, Yann Le Scouarnec, Elizabeth Naramore, Gary Mailer, Jeremy Stolz, Jason Gerner
Web Application Development by Drematech Publication.

Web bibliography:
www.wikipedia.orgwww.w3shools.comwww.google.comwww.designsparkle.comwww.jqueryui.comwww.stackoverflow.comAPPENDIX I
Periodic Progress Report I
Arpita Kapuriya`s:
Project: All Mobile Scheme Information
Status: Reviewed (Freeze)
What Progress you have made in the Project?
Currently we are learning regarding bootstrap and how to make good design.

What challenge you have faced?
We don’t know about bootstrap so it is little bit to understand the all class of bootstrap.

What support you need?
Nothing
Which literature you have referred?
www.google.com and www.w3shools.org Comment by Internal Guide:
Done.

Periodic Progress Report II
Arpita Kapuriya`s:
Project: All Mobile Scheme Information
Status: Reviewed
What Progress you have made in the Project?
currently we are learning regarding java script and how to make secure by script language and platform compatibility check.

What challenge you have faced?
We don’t know about java script so it is little bit to understand the lots of different actions that can be performed and those actions can be combined in many different ways.

What support you need?
Nothing
Which literature you have referred?
www.google.com and www.w3shools.org and www.codecademy.com.

Comment by Internal Guide:
Done.

Periodic Progress Report III Arpita Kapuriya`s:
Project: All Mobile Scheme Information
Status: Reviewed
What Progress you have made in the Project?
Currently we are learning regarding php script and how to make server-side dynamic content.

What challenge you have faced?
we don’t know about phpscript so it is little bit to understand the connectivity with database and also operation with database like insert, update, delete, search, etc.

What support you need?
Nothing.

Which literature you have referred?
www.google.com www.w3shools.org.

Comment by Internal Guide:
Done.

Periodic Progress Report IV Arpita Kapuriya`s:
Project: All Mobile Scheme Information
Status: Reviewed
What Progress you have made in the Project?
Currently we are creating registration page , login page , home page , etc with database connectivity.

What challenge you have faced?
We don’t know about how to move from one page to another page and also connect with database and perform operation with database
What support you need?
Nothing.

Which literature you have referred?
www.google.com and www.w3shools.org
Comment by Internal Guide:
Done.

APPENDIX II
IDEATION CANVAS:

Figure A.2 Ideation Canvas
APPENDIX III
AEIOU CANVAS:

Figure A.3 AEIOU Canvas
APPENDIX IV
PRODUCT DEVELOPMENT CANVAS:

Figure A.4 Product Development Canvas
APPENDIX V
EMPATHY CANVAS:

Figute A.5 Empathy Canvas