SMART PERSONAL ASSISTANCE PALLAVA PRASOON KUMAR VIMAL NITISH KUMAR

TABLE OF CONTENTS 1. ABSTRACT 2.INTRODUCTION 2.1 PROBLEM DEFINITION 3 SYSTEM STUDY 3.1EXISTING SYSTEM 3.2PROPOSED SYSTEM 3.4 SYSTEM REQUIREMENT 3.5 PACKAGES 3.6 SYSTEM ANALYSIS 4 SYSTEM REQUIREMENT 4.1 INPUT REQUIREMENT 4.2 OUTPUT REQUIREMENT 4.3 DATABASE DESIGNATED 4.4 PROCESS DESIGN 5 TESTING 6 IMPLEMENTATION 7 CONCLUSION 8 BIBILIOGRAPHY ABSTRACT SMART PERSONAL ASSISTANT (SPA) PALLAVA PRASOON, KUMAR VIMAL, NITISH KUMAR DEPARTMENT OF COMPUTER SCIENCE, COCHIN UNIVERSITY OF SCIENCE AND TECHNOLOGY,KOCH I pprasoon27@gma il.com kmrvimal@gmail.com Smart Personal Assistance (SPA) is a smartphone application as well as web appli cation intended to be used by every individual. SPA is designed as it is unique of its type as a smartphone application providing tools which enables every user to store its personal and secret information like its bank accounts informatio n, credit card information, insurance and policies etc. and also reminds user of its important dates like next premium date for insurance, next smoke test date for vehicles etc. SPA will be a self-contained application which will be provided free of cost to every android user and it can be proved to be a very useful application . PDA is developed keeping in mind needs of user of every class who requires to store

his/her personal information in safe and secured way which can be accessed con veniently. SPA stores the personal information of every individual which is mainly divided in four sections viz. Finance, Automobile and Secure Vault and Monthly Expenditu re. Finance section includes the bank accounts, insurance and policies. This sec tion facilitates user to store its different bank account type information, info rmation about insurance and also different policies any user have like mutual fu nds, shares etc. Automobile section keeps track of different types of vehicle us er owns and also facilitates user to store information of every vehicle. Secure Vault section allows user to store all its secret information like email account s, web accounts, passport details, credit card details and license details. SPAs monthly expenditure section allows user to estimate his/her monthly expenditure conveniently. SPA pops up reminder of every important date like next premium date of policies, next smoke test date of vehicle and loan payment date etc. Ringtones on phone c an be used for customizability of remainder pop-up tones. 2.Introduction 2.1Problem definition The main purpose of a personal digital assistant (PDA) is to act as an electroni c organizer or day planner that is portable, easy to use and capable of sharing i nformation with your PC. It s supposed to be an extension of the PC, not a repla cement. they manage your personal information, such as contacts, appointments, a nd to-do lists, secure notes, important data, and various other information tod ay s devices can also connect to the Internet, act as global positioning system (GPS) devices, and run multimedia software. What s more, manufacturers have comb ined PDAs with cell phones, multimedia players and other electronic gadgetry. SPA Features Even the most basic PDAs handle standard personal information management (PIM) f unctions, run application software and synchronize with PCs. Here are some addit ional details about these basic features. Handle Standard PIM Functions All PDAs come with some kind of personal information management (PIM) software t hat typically handles the following tasks to keep you organized: Store contact information (names, addresses, phone numbers, e-mail addresses) Make to-do lists Take notes Track appointments (date book, calendar) Remind you of appointments (clock, alarm functions) Perform calculations 1.2 User Panel 1.2.1 User Login 1.2.1.1 Home 1. This consist of the different pop-up menus showing the details of the differe nt task 2. It contain a link to the CUSAT official web-site. 3. It allows the different users to access the registration forms. 4. He can view the Student administration division of the different hostels and also view the notice boards. 1.2.1.2 Registration Form This section provides an online form to the professionals which can be filled by them,and a thus it provides them a space to store their information and activit ies which can be later retrieved 1.2.2 secure vault when the user is connected to the internet and opens the smart personal assistan t credit card page he can perform various various database operations on his cre

dit card information such as creation of new credit card page, modification of d etails The various screen info can be given as follows:1. the user opens the credit card page from home page. 2. There are options for modification updation and deletion of card informa tion 3. the user can search for its credit card information 4. he can also add or update new entries if baught likewise the user can do ample manipulation of various objects such as credit ca rd, passport,license, bank account, web account credential,secure note. 1.2.3 vehicle When the user opens the automobile section he views the details of his automobil e like car, scooter etc. He can perform various functions on to the automobile database like adding new a utomobile information, updating the older one or deleting an automobile if it is sold or thrown away. The various screen information can be designated as follows:1) The user opens the automobile page from his home page. 2) There are options for addition deletion updation of a new entry. 3) He may choose for an addition of a new entry if he has bought a new vehi cle. 4) The user is taken to a new page and thus consecutively can fill the info rmation related to his new vehicle such as a. date of purchase b. date of insurance c. date of pollution testing d. date of next premium 5) He may choose to add this information or may exit to add new. 6) The user also has an option for deletion of an information related to an automobile if its no longer with it. 7) The user can update an information or a set of information related to hi s automobile if there is any changes in it. 8) Now the user can exit to the main page if his work with the automobile s ection is completed. 9) The major feature here is that all the screen can exit to the home page of smart personal assistant. 1.2.4 Insurance information:In this field the user enters the details regarding to his insurance policies it s types and other types of savings or funds. the stored information can also be used for providing regular update on the deadline of policies, the next premium remittance date, year of maturity etc to the customer the various screen information can be described as:1) the customer moves to the insurance page from his home page. 2)in this page he has the option of adding a new policy detail if he has bought so,editing the details of a previously bought policy or delete an exis ting policy if its term is over. 3) In case of addition of a new policy the user is taken to new page where he ha s fields to fill the information related to his new policy viz date of purchase, year of maturity, premium amount etc. 5)In case of deletion of an existing insurance policy the user searches for the required policy and deletes it. 6) Or if he want to review or update a policy he can follow the same procedure 3.System study 3.1 Existing System For the past few years the number of management professional are increasing rapi

dly. Thereby the number of task they perform are also increasing for the sake of their workload. And hence there is a lot of strain on the professional and soft wares are not usually used in this context. This particular project deals with the problems on managing personal information and avoids the problems which occur when carried manually Identification of the drawbacks of the existing system lea ds to the designing of computerized system that will be compatible to the existi ng system with the system which is more user friendly and more GUI oriented. We can improve the efficiency of the system, thus overcome the followi ng drawbacks of the existing system. more human error. more strength and strain of manual labour needed Repetition of the same procedures. low security Data redundancy difficult to handle difficult to update data record keeping is difficult Backup 3.2 proposed system As the security issues are increasing therefore one cannot rely on traditional s ystem of information storage being too tedious and hefty so we need to come up w ith easy and secure information estorage system. This software will be a smartph one application as well as web application intended to be used by every individu al. SPA is designed as it is unique of its type as a smartphone application prov iding tools which enables every user to store its personal and secret informatio n like its bank accounts information, credit card information, insurance and pol icies etc. and also reminds user of its important dates like next premium date for insurance, next smoke test date for vehicles etc. More specifically this application will store each and every information an indi vidual needs to store at a secure and convenient place which can be accessed eas ily whenever needed. The salient features of this system can be interpolated as less human error. low strength and strain of manual labour needed Repetition of the same procedures can be avoided. high data-centered security less Data redundancy easy to handle easy to update data record keeping is efficient Backup can be implemented quite easily. 3.3 System Requirements The sections below describe the system and software requirements for developing Android applications using the Android Development Tools, revision 3. Supported Operating Systems Windows XP (32-bit) or Vista (32- or 64-bit) Mac OS X 10.4.8 or later (x86 only) Linux (tested on Linux Ubuntu Hardy Heron) 64-bit distributions must be capable of running 32-bit applications. For information about how to add support for 32-bit applications, see the Ubuntu Linux installation notes. Supported Development Environments Eclipse IDE Eclipse indigo Note: Eclipse 3.3 has not been tested with the latest version of ADT and support can no longer be guaranteed. We suggest you upgrade to Eclipse 3.4 or 3.5. Recommended Eclipse IDE packages: Eclipse IDE for Java EE

Developers, Eclipse IDE for Java Developers, Eclipse for RCP/Plug-in Developers, or Eclipse Classic (3.5.1+) Eclipse JDT plugin (included in most Eclipse IDE packages) JDK 5 or JDK 6 (JRE alone is not sufficient) Android Development Tools plugin (optional) Not compatible with Gnu Compiler for Java (gcj) Other development environments or IDEs JDK 5 or JDK 6 (JRE alone is not sufficient) Apache Ant 1.6.5 or later for Linux and Mac, 1.7 or later for Windows

3.4 Packages These are the Android APIs. android Contains resource classes used by applications included in the platform and defi nes application permissions for system features. android.accessibilityservice The classes in this package are used for development of accessibility service th at provide alternative or augmented feedback to the user. android.accounts android.animation These classes provide functionality for the property animation system, which all ows you to animate object properties of any type. int, float, and hexadecimal co lor values are supported by default. You can animate any other type by telling t he system how to calculate the values for that given type with a custom TypeEval uator. For more information, see the Animation developer guide. android.app Contains high-level classes encapsulating the overall Android application model. 3.5System analysis Systems analysis is the dissection of a system into its component pieces to stud y how those component pieces interact and work. We do a systems analysis to subsequently per form a systems synthesis. Systems synthesis is the re-assembly of a system s com ponent pieces back into a whole system-it is hoped an improved system. Through systems analysis and synthesis, we may add, delete, and modify system co mponents toward our goal of improving the overall system. Moving from the theoretical def inition to something a bit more contemporary, Systems analysis is a term that co llectively describes the early phases of systems development. There has never be en a universally accepted definition. And there has never been agreement on when analysis ends and design begins. To further confuse the issue, some methodologi es refer to systems analysis as logical design. Typically, each organization s m ethodology of choice determines the definition for that organization. In the FAS T methodology, systems analysis is defined as those phases and activities that f ocus on the business problem, independent of technology (for the most part). Spe cifically, we refine our definition of systems analysis as follows. "Systems analysis is (1) the survey and planning of the system and project (2) the study andanalysis of the existing business and information system, a nd (3) the definition of businessrequirements and priorities for a new or impro

ved system. A popular synonym is logical design. "This definition corresponds to the first three phases of FAST. The phase "confi gure a feasible solution" would be considered part of systems analysis by some experts. We prefe r to think of it as an analysis-to-design transition phase. Systems analysis is driven by business concerns, specifically, those of system u sers. Hence, it addresses the DATA, PROCESS, INTERFACE, and GEOGRAPHY building blocks from a system user perspective. Emphasis is placed on business issues, not technical or implementation concerns. A repository is a collection of those places where we keep all documentation ass ociated with the application and project. The repository is normally implemented as some combination of the following: A disk or directory of word processing, spreadsheet, and other computer generat ed files that contain project correspondence, reports, and data. One or more CASE local repositories. -Hard-copy documentation (stored in notebooks, binders, and system libraries). "Hereafter, we will refer to these as making up a singular project repository. "FAST is a repository-based methodology. This means that phases (and activities included in phases) communicate across a shared repository. Thus, the phases and activities are not really sequential! Work in one phase can and should overlap work in another phase, so l ong as the necessary information is already in the repository. This accelerates development and allows FAST to live up to its name. Furthermore, this model permits the developer to backtra ck when an error or omission is discovered. STRATEGIES FOR SYSTEMS ANALYSIS AND PROBLEM SOLVING Traditionally, systems analysis is associated with application development proje cts, that is, projects that produce information systems and their associated computer applicat ions. Your first experiences with systems analysis will likely fall into this category. But syste ms analysis methods can be applied to projects with different goals and scope. In addition to single information systems and computer applications, systems analysis techniques can be applied to strateg ic information systems planning and to the redesign of business processes. There are also many strategies or techniques for performing systems analysis. Th ey include modern structured analysis, information engineering, prototyping, and object-ori ented analysis. These strategies are often viewed as competing alternatives. In reality, certain combinations complement one another. Let s briefly examine these strategies and the scope or goals of the projects to which they are suited. The intent is to develop a high-level underst anding only. Modern Structured Analysis Structured analysis was one of the first formal strategies developed for systems analysis of information systems and computer applications. Modern structured analysis is sti ll one of the most

widely practiced techniques. Modern structured analysis is a process-centered technique that is used to model business requirements for a system. The models are structured pictures that illustrate th e processes, inputs, outputs, and files required to respond to business events (such as ORDER S). "By process-centered, we mean the initial emphasis in this technique is on the P rocess building blocks in our information system framework. The technique has evolved to also in clude the DATA building blocks as a secondary emphasis. Structured analysis was not only the first popular systems analysis strategy; it also introduced an overall strategy that has been adopted by many of the other techniques-modeldriven development. A model is a representation of reality. Just as "a picture is worth a thousand w ords," most models use pictures to represent reality. Model-driven development techniques emphasize the drawing of models to define bu siness requirements and information system designs. The model becomes the design bluepr int for constructing the final system. Modern structured analysis is simple in concept. Systems and business analysts d raw a series of process models called data flow diagrams that depict the essential processes of a system along with inputs, outputs, and files. Because these pictures represent the logical bu siness requirements of the system independent of any physical technical solution, the models are sai d to be a logical design for the system. Information Engineering (IE) "Today, many organizations have evolved from a structured analysis approach to a n information engineering approach. "Information engineering is a data-centered, but process-sensitive technique tha t is applied to the organization as a whole (or a significant part, such as a division), rather than on an ad-hoc, project-by-project basis (as in structured analysis). "The basic concept of information engineering is that information systems should he engineered like other products. Information engineering books typically use a pyramid frame work to depict information systems building blocks and system development phases. The phases ar e: 1. Information strategy planning (ISP) applies systems analysis methods to exami ne the business as a whole to define an overall plan and architecture for subsequent in formation systems development. No actual information systems or computer applications are developed. Instead, the project team studies the business mission and goals and defines an information systems architecture and plan to optimally align information systems to help the organization achieve its business goals.

2. Based on the strategic plan, business areas are carved out and prioritized. A business area is a collection of cross-organizational business processes that should be highly inte grated to achieve the information strategy plan (and business mission). A business area an alysis (BAA) uses Systems analysis methods to study the business area and define the business requirements for a highly streamlined and integrated set of information Systems and computer applications to support that business area. 3. Based on the business area requirements analysis, information system applicat ions are carved out and prioritized. These applications become projects to which other Systems a nalysis and design methods are applied to develop production systems. These methods may incl ude some combination of structured analysis and design, prototyping, and object-oriented analysis and design. "Information engineering is said to be a data-centered paradigm because it empha sizes the study and definition of DATA requirements before those of PROCESS, INTERFACE, or GEOGRAPHY requirements. This is consistent with the contemporary belief that inf ormation is a corporate resource that should be planned and managed. Since information is a pr oduct of data, data must be planned first! Data models are drawn first. In addition to data mod els, information engineers also draw process models similar to those drawn in structured analysis . "Although information engineering has gradually replaced structured analysis and design as the most widely practiced Strategy for Systems analysis, information engineering act ually integrates all the process models of structured analysis with its data models. That should make sense, since we know that an information system must include both DATA and PROCESS building b locks. Information engineering was the first formal Strategy for synchronizing those bu ilding blocks! Information engineering was also the first widely practiced strategy that consid ered GEOGRAPHY building blocks through application of tools that plan and document th e distribution of data and processes to locations. Prototyping "Another strategy for Systems analysis is prototyping. "Prototyping is an engineering technique used to develop partial but functional versions of a System or applications. When extended to system design and construction, a proto type can evolve into the final, implemented system. "Two flavors of prototyping are applicable to systems analysis: - Feasibility prototyping is used to test the feasibility of a specific technolo gy that might be applied to the business problem. For example, we might use Microsoft Access to b uild a quickbutincomplete prototype of the feasibility of moving a mainframe application to a P C-based

environment. - Discovery prototyping (sometimes called requirements prototyping) is used to d iscover the users business requirements by having them react to a quick-and-dirty implementa tion of those requirements. For example, we might again use Microsoft Access to create sample forms and reports to solicit user responses as to whether those forms and reports truly re present business requirements. (Note: In discovery prototyping, we try to discourage users from w orrying about the style and format of the prototypes; that can be changed during system design !) "In response to the faster pace of the economy in general, prototyping has becom e a preferred technique for accelerating systems development. Many system developers extend th e prototyping techniques to perform what they call rapid application development. Unfortunatel y, some developers are using prototyping to replace model-driven strategies, only to lea rn what true engineers have known for years-you cannot prototype without some degree of more formal design models. Joint Application Development (JAD) "As previously described, modern structured analysis and information engineering both emphasize model-driven development. Prototyping places emphasis on construction of the wor king prototypes. Joint application development (JAD) complements both of these techni ques by emphasizing participative development among system owners, users, designers, and builders. "Joint application development (JAD) uses highly organized and intensive worksho ps to bring together system owners, users, analysts, designers, and builders to jointl y define and design systems. Synonyms include joint application design and joint requirements planning. "A JAD-trained Systems analyst usually plays the role of facilitator for a works hop that will typically run from three to five full working days. This workshop may replace mo nths of traditional interviews and follow-up meetings. "JAD provides a working environment in which to accelerate methodology activitie s and deliverables. It promotes enhanced system owner and user participation in system development. But it also requires a facilitator with superior mediation and negotiation skill s to ensure that all parties receive appropriate opportunities to contribute to the system s developm ent. Business Process Redesign (BPR) "One of the most interesting contemporary applications of systems analysis metho ds is business process redesign. "Business process redesign (also called business process reengineering) is the a pplication of Systems analysis (and design) methods to the goal of dramatically changing and i mproving the

fundamental business processes of an Organization, independent of information te chnology. "The interest in BPR was driven by the discovery that most current information s ystems and applications have merely automated existing and inefficient business processes. Automated bureaucracy is still bureaucracy; it does not contribute value to the business a nd may actually subtract value from the business. BPR is one of many types of projects triggered by the trend we call total quality management (TQM). "BPR projects focus almost entirely on noncomputer processes. Each process is st udied and analyzed for bottlenecks, value returned, and opportunities for elimination or s treamlining. Once the business processes have been redesigned, most BPR projects conclude by exami ning how information technology might best be applied to the improved business processes. This creates new application development projects to which the other techniques described in this section might be applied. Business process redesign is a subject that deserves its own c ourse and book. Object-Oriented Analysis (OOA) "Object-oriented analysis is the new kid on the block. The concepts behind this exciting new strategy (and technology) are introduced here. "For the past 30 years, most systems development strategies have deliberately se parated concerns of DATA from those of PROCESS. The COBOL language, which dominated busi ness application programming for years, was representative of this separation-the DAT A DIVISION was separated from the PROCEDURE DIVISION. Most systems analysis (and design) techniques similarly separated these concerns to maintain consistency with the p rogramming technology. Although most systems analysis and design methods have made signific ant attempts to synchronize data and process models, the results have been less than fully su ccessful. "Object technologies and techniques are an attempt to eliminate the separation o f concerns about DATA and PROCESS. Instead, data and the processes that act on that data ar e combined or encapsulated into things called objects. The only way to create, delete, chan ge, or use the data in an object (called properties) is through one of its encapsulated processes (c alled methods). The system and software development strategy is changed to focus on the "assembly" o f the system from a library of reusable objects. Of course, those objects must be defined, de signed, and constructed. Thus, in the early part of the Systems development process, we need to use objec toriented analysis techniques. "Object-oriented analysis (OOA) techniques are used to *Study existing objects to see ifthey can be reused or adapted for new uses, and to *Define new or modified objects that will be combined with existing objects into a useful business computing application.Object-oriented analysis techniques are

best suited to projects that will implement systems using emerging object techn ologies to construct, manage, and assemble those objects into usefulcomputer app lications. Examples include Smalltalk C++, Delphi and Visual BASIC. "Today, most computer Operating Systems use graphical user interfaces (GUIs) suc h as Microsoft Windows and IBM s OS/2 Presentation Manager. GUIs are built with objec t-oriented (or object-like) technologies. The development of GUI applications can be based on libraries of reusable objects (sometimes called components) that exhibit the same behaviors i n all applications. For example, Delphi and Visual BASIC contain all the necessary objects (called c omponents) 4.System design 4.1 Input Design The system design is divided in to two portions. The Administrator section and t he User section. 4.1.1 Administrator 1. The Administrator allot different spaces to the different fields. 2.He can alter the specifications of storage 3.He can control the schema. 4.He can,t edit the details of the end users records. A process of converting user originated inputs to a computer-based format. Input design is an important part of development process since inaccurate input data are the most common cause of errors in data processing. Erroneous entries can be controlled by input design. It consists of developing s pecifications and procedures for entering data into a system and must be in simple format. The goal of input data design is to make data entry as easy, logical and free from errors as possi ble. In input data design, we design the source document that capture the data a nd then select the media used to enter them into the computer. There are two major approaches for entering data in to the computer. They are Menus. Dialog Boxes. Menus A menu is a selection list that simplifies computer data access or entry. Instea d of remembering what to enter, the user chooses from a list of options. A menu limits a user choice of response but reduce the chances for error in data entry. Dialog Box Dialog boxes are windows and these windows are mainly popup, which appear in res ponse to certain conditions that occur when a program is run. It allows the disp lay of bitmaps and pictures. It can have various controls like buttons, text boxes, list boxes and combo boxes. Using these contr ols we can make a dialog with the program. The proposed system has three major inputs. They are Machine Registration, Machi ne Scheduling and Request Form. 4.2 Process Design Process design plays an important role in project development. In order to under stand the working procedure, process design is necessary. Data Flow Diagram and System Flow chart are the tools used for process design. System Flow Chart is a graphical representation of the system showing the overal l flow of control - System Flow Chart is a graphical representation of the system showing the over all flow of control in processing at the job level; specifies what activities must be done to conver t from a physical to logical model.

- Data Flow Diagram is the logical representation of the data flow of the projec t. The DFD is drawn using various symbols. It has a source and a destination. Th e process is represented using circles and source and destination are represente d using squares. The data flow is represented using arrows. One reader can easil y get the idea about the project through Data Flow Diagram. SYMBOLS USED IN DATA FLOW DIAGRAM 4.2.1- source rectangle, which defines or destination 4.2.2 -Arrow, which shows dataflow. 4.2.3 -Circle, which represent a process that transforms incoming data into outg oing flow. 4.2.4-Open rectangle, which shows a data store 4.2.1 Data Flow Diagram The data flow diagram represents the flow of data in a system it is a very impor tant concept in transaction analysis 4.3 Database Design The data in the system has to be stored and retrieved from database. Designing t he database is part of system design. Data elements and data structures to be stored have been ident ified at analysis stage. They are structured and put together to design the data storage and retrieval sy stem. A database is a collection of interrelated data stored with minimum redundancy t o serve many users quickly and efficiently. The general objective is to make database access easy, quick, inexpensive and flexible for the user. Relationships are established betw een the data items and unnecessary data items are removed. Normalization is done to get an internal consistency of data and to have minimum redundancy and maxim um stability. This ensures minimizing data storage required, minimizing chances of data inconsistencies and optimizing for updates. The MS Access database has b een chosen for developing the relevant databases. The database design can be shown via code as package de.vogella.android.sqlite.first; import import import import android.content.Context; android.database.sqlite.SQLiteDatabase; android.database.sqlite.SQLiteOpenHelper; android.util.Log;

public class MySQLiteHelper extends SQLiteOpenHelper { public static final String TABLE_COMMENTS = "comments"; public static final String COLUMN_ID = "_id"; public static final String COLUMN_COMMENT = "comment"; private static final String DATABASE_NAME = "commments.db"; private static final int DATABASE_VERSION = 1; // Database creation sql statement private static final String DATABASE_CREATE = "create table " + TABLE_COMMENTS + "( " + COLUMN_ID + " integer primary key autoincrement, " + COLUMN_COMMEN T + " text not null);"; public MySQLiteHelper(Context context) { super(context, DATABASE_NAME, null, DATABASE_VERSION); } @Override

public void onCreate(SQLiteDatabase database) { database.execSQL(DATABASE_CREATE); } @Override public void onUpgrade(SQLiteDatabase db, int oldVersion, int newVersion) { Log.w(MySQLiteHelper.class.getName(), "Upgrading database from version " + oldVersion + " to " + newVersion + ", which will des troy all old data"); db.execSQL("DROP TABLE IF EXISTS " + TABLE_COMMENTS); onCreate(db); } } 4.4 Output Design Designing computer output should proceed in an organized, well throughout manner ; the right output element is designed so that people will find the system wheth er or executed. When we design an output we must identify the specific output th at is needed to meet the system. The usefulness of the new system is evaluated o n the basis of their output. Once the output requirements are determined, the system designer can decide what to include in thesystem and how to structure it so that the require output can be produced. For the proposed software, it is necessary that the output reports be compatible in format with the existing reports. The output must be concerned to the overall performance and the systems working, as it should. It consists of developing specifications and procedures for data preparation, those steps neces sary to put the inputs and the desired output, ie maximum user friendly. Proper messages and appropriate directions can control errors com mitted by users.

The output design is the key to the success of any system. Output is the key bet ween the user and the sensor. The output must be concerned to the systems working , as it should. Output design consists of displaying specifications and procedures as data prese ntation. User never left with the confusion as to what is happening without appr opriate error and acknowledges message being received. Even an unknown person can operate the system without knowing anything about the system. Chapter 5 SYSTEM TESTING System testing is the stage of implementation, which is aimed at ensuring that t he system works accurately and efficiently before live operation commences. Testing is the process of execu ting the program with the intent of finding errors and missing operations and also a complete verification to det ermine whether the objectives are met and the user requirements are satisfied. The ultimate aim is quality ass urance. Tests are carried out and the results are compared with the expected document. I n the case of erroneous results, debugging is done. Using detailed testing strategies a test plan is car ried out on each module. The various tests performed in Network Backup System are unit testing, integration tes

ting and user acceptance testing. 5.1 Unit Testing The software units in a system are modules and routines that are assembled and i ntegrated to perform a specific function. Unit testing focuses first on modules, independently of one another, to locate errors. This enables, to detect errors in coding and logic that are contained within each module. This testing includes entering data and ascertaining if the value matches to the type and size support ed by java. The various controls are tested to ensure that each performs its act ion as required. 5.2 Integration Testing Data can be lost across any interface, one module can have an adverse effect on another, sub functionswhen combined, may not produce the desired major functions . Integration testing is a systematic testing to discover errors associated with in the interface. The objective is to take unit tested modules and build a progr am structure. All the modules are combined and tested as a whole. Here the Serve r module and Client module options are integrated and tested. This testing provi des the assurance that the application is well integrated functional unit with s mooth transition of data. 5.3 User Acceptance Testing User acceptance of a system is the key factor for the success of any system. The system under consideration is tested for user acceptance by constantly keeping in touch with the system users at time of developing and making changes whenever required. CHAPTER 6 IMPLEMENTATION Implementation is the stage in the project where the theoretical design is turne d into a working system and is giving confidence on the new system for the users that it will work efficiently and effectively. It involves careful planning, investigation of the current system and its constraints on imp lementation, design of methods to achieve the change over, an evaluation of chan ge over methods. Apart from planning major task of preparing the implementation are education and training of users. The implementation proce ss begins with preparing a plan for the implementation of the system. According to this plan, the activities are to be carried out, discussions made regarding the equipment and resources and the additional equipment has to b e acquired to implement thenew system. In network backup system no additional re sources are needed. Implementation is the final and the most important phase. Th e most critical stage in achieving a successful new system is giving the users confidence that the new system will work and be e ffective. The system can be implemented only after thorough testing is done and if it is found to be working according to the specification. This method also offers the greatest security since the old system can take over if the errors are found or inability to handle certain type of transactions whi le using the new system. 7.1 User Training After the system is implemented successfully, training of the user is one of the most important subtasks of the developer. For this purpose user manuals are pre pared and handled over to the user to operate the developed system. Thus the users are trained to operate the developed system . Both the hardware and software securities are made to run the developed systems successfully in future . In order to put new application system into use, the following activities were taken care of: Preparation of user and system documentation . Conducting user training with demo and hands on Test run for some period to ensure smooth switching over the system The users are trained to use the newly developed functions. User manuals describ ing the procedures for

using the functions listed on menu are circulated to all the users. It is confir med that the system is implemented up to users need and expectations. 7.2 Security and Maintenance Maintenance involves the software industry captive, typing up system resources . It means restoring something to its original condition. Maintenance follows conv ersion to the extend that changes are necessary to maintain satisfactory operati ons relative to changes in the users environment. Maintenance often includes mino r enhancements or corrections to problems that surface in the systems operation. Maintenance is also done based on fixing the problems reported, changing the int erface with other software or hardware enhancing the software. Any system developed should be secured and protected against possible hazards. S ecurity measures are provided to prevent unauthorized access of the database at various levels. An uninterrupted power supply should be so that the power failur e or voltage fluctuations will not erase the data in the files. Password protection and simple procedures to prevent the unauthorized access are provided to the users .The system allows the user to enter the system only thro ugh proper user name and password. Chapter 8 Conclusion To conclude the description about the project : The project, developed using jav a and android based on the requirement specification of the user and the analysi s of the existing system, with flexibility for future enhancement. The expanded functionality of todays software requires an appropriate approach to wards software development. This personal information management software is des igned for people who want to manage various activities in their life. For the pa st few years the number of credential has increased rapidly and hence there is a lot of strain on the professionals this particular project deals with the prob lems on managing information and avoids the problems which occur when carried manually. Identification of the drawbacks of the existing system leads to the designing of computerized system that will be compatible to the existing system with the sys tem which is more user friendly chapter 9 BIBILIOGRAPHY w3school.com vogella.com wikipedia eclipse