PRACTICAL TRAINING SEMINAR REPORT

ON

CALCULATOR USING SWING

Submitted to

Rajasthan Technical University, Kota

In Partial Fulfillment of the requirements for the award of the degreeof

Bachelor of Technology

In

“COMPUTER SCIENCE & ENGINEERING”

2014-2015

Submitted To: Submitted By:Mr. YOGESH RATHI Ayush ThakurAsst. Professor 12EYTCS006

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERINGYAGYAVALKYA INSTITUTE OF TECHNOLOGY

Sitapura, Tonk Road Jaipur

1

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERINGYAGYAVALKYA INSTITUTE OF TECHNOLOGY

Sitapura, Tonk Road JaipurSession 2015-2016

CERTIFICATE

This is to certify that Seminar report on “COLLEGE MANAGEMENT SYSTEM” is submitted by Ayush Thakur, student of final year Department of computer Science & Engineering of YAGYAVALKYA INSTITUTE OF TECHNOLOGY, JAIPUR, during the academic year 2014-15, towards the partial fulfillment of the requirements leading to the award of Bachelor of Technology degree in Computer Science & Engineering. Further, to the best of my knowledge, this work is her own completion & presentation.

SUBMITTED TO:Mr. Yogesh RathiAsst. Professor

2

ACKNOWLEDGEMENT

I would like to use this opportunity to thank all who lend their hand for completing my project successfully. First of all I would like to thank Almighty, who drove me through my project with his blessing and providing me with enough support to make it a success.

I would also like to thank to Prof. ANKUR GOYAL SIR, (H.O.D.) and Mr. YOGESH RATHI SIR, department of computer science & engineering and all faculty members of department, who helped and gave me valuable guidance to prepare my PROJECT.

Last but not least, I would like to thank my parents who helped me a lot in gathering different information, collecting data and guiding me from time to time in making this project. Despite of their busy schedules, they gave me a different idea in making this project unique.

AYUSH THAKUR7thSem

(Computer Science)

3

TABLE OF CONTENTS

LIST OF TABLES i

LIST OF CHARTS ii

CHAPTER TITLE PAGE NO.

ABSTRACT 6

I INTRODUCTION

1.1 Profile of the Company 7

II 2.1 Introduction of Project

2.1.1 Purpose

2.1.2 Scope

2.1.3 Feasibility Study

2.1.4 Modules

2.2 Technology Used

2.2.1 Java

8

III OBJECTIVES OF THE STUDY 17

IV S/W & H/W CONFIGURATION

4.1 Hardware Configuration

4.2 Software Configuration

18

V SYSTEM DESIGN

5.1 Logical Design

5.2 Physical Design

5.2.1 User Interface Design

5.2.2 Physical Design

5.3 Tools & Database Design

5.3.1 Data Design

5.3.2 Database Tables

5.3.3 UML Diagrams

19

4

5.3.4 Data Flow Diagram

VI TESTING

6.1 Mode of Testing

6.1.1 Unit Testing

6.1.2 System Testing

6.1.3 Regression Testing

6.1.4 Black Box Testing

6.1.5 White Box Testing

24

VII IMPLEMENTATION 26

VIII MAINTENANCE 27

IX USER MANUAL 28

X CONCLUSION 29

LIST OF FIGURES

5.3.3.2 1-Level DFD 215.3.3.3 2-Level DFD 225.3.4.1 Data Flow Diagram 23

Calculator Layout 28

5

ABSTRACT

Product intends to provide simple and basic interface of calculator to user for performing

mathematical calculations like addition, subtraction, multiplication and division.

6

CHAPTER I

1.1 PROFILE OF THE COMPANY

HP Enterprise Services is the global business and technology services subsidiary of the HP

Enterprise Business strategic business unit. It was formed by the combination of HP's legacy

services consulting and outsourcing business and the integration of acquired Electronic Data

Systems, which had defined the outsourcing business when it was established in 1962 by H. Ross

Perot.

1.1.1 PROVIDE SOLUTIONS FOR

HP Enterprise Services catalogs its services into three service portfolios which are,

Infrastructure Technology Outsourcing (ITO) - includes maintaining the operation of part or

all of a client's computer and communications infrastructure, such as networks, mainframes,

"midrange" and Web servers, desktops and laptops, and printers.

Applications Services - involves the developing, integrating, modernizing, and/or

maintaining of applications software for clients

Industry Services, including Business Process Outsourcing (BPO) - addresses the core

business challenges of clients in five key industries: healthcare, transportation,

communications, government, and financial services, among others. BPO group is an integral

part of the portfolio, which involves performing a business function for a client, like payroll,

call centers, insurance claims processing, and so forth.

7

CHAPTER II

2.1 INTRODUCTION OF PROJECT

The purpose of developing the project is to easily do basic Mathematical calculations using

simple GUI.

2.1.1 PURPOSE

Purpose of Making calculator is to provide easy access for basic mathematical

solution.

To provide Simple GUI to user.

2.1.2 SCOPE

The different areas where we can use this application are :

• Any education institute can make use of it .

• It can be used in offices and modifications can be easily done according to requirements.

• Can be used in shops .

2.1.3 FEASIBILITY STUDY

A feasibility study is the preliminary study, which investigates the information needs of

prospective users and determines the resources requirement, cost, benefit and feasibility of a

proposed system.

The goal of feasibility study is to evaluate alternatives systems and to propose the most feasible

and desirable systems for the development.

8

2.1.3.1 TECHNICAL FEASIBILITY

Technical feasibility can be demonstrated if reliable hardware and software capable of meeting

the needs of a proposed system can be acquired or developed by the business in the required time.

The proposed system “Calculator Using Swing” is planned to run on Java platform. Thus, this

project is considered technically feasible for the development.

The work for the project can be done with current equipment, existing software technology and

available personal. Hence the proposed system is technically feasible.

2.1.3.2 OPERATIONAL FEASIBILITY

Operational feasibility is the willingness and ability of the management student, staff, records

and others to operate, use and support a proposed system. The system that we proposed really

satisfied all the end users, especially our client and its company authorities because of its rich

GUI interfaces and fast computing ability.

2.1.3.3 ECONOMIC FEASIBILITY

Economic feasibility is concerned with whether expected cost savings, increased revenues,

increased profits and reductions in required investments, and other kinds of benefits will exceed

the costs of developing and operating a proposed system.

Since the required Hardware and Software for developing the system is already available in the

organization, it does not cost much for developing the proposed system.

2.1.4 MODULES

• Single Layout GUI

2.2 TECHNOLOGY USED

• Front end: Core Java(J2SE)

2.2.1 Core JAVA

Java is a general-purpose computer programming language that is concurrent, class-

based, object-oriented and specifically designed to have as few implementation dependencies as

possible. It is intended to let application developers "write once, run anywhere"

(WORA), meaning that compiled Java code can run on all platforms that support Java without the

9

need for recompilation .Java applications are typically compiled to byte code that can run on

any Java virtual machine (JVM) regardless of computer architecture. As of 2015, Java is one of

the most popular programming languages in use, particularly for client-server web applications,

with a reported 9 million developers. Java was originally developed by James Gosling at Sun

Microsystems (which has since been acquired by Oracle Corporation) and released in 1995 as a

core component of Sun Microsystems' Java platform. The language derives much of

its syntax from C and C++, but it has fewer low-level facilities than either of them.

The original and reference implementation Java compilers, virtual machines, and class

libraries were originally released by Sun under proprietary licenses. As of May 2007, in

compliance with the specifications of the Java Community Process, Sun relicensed most of its

Java technologies under the GNU General Public License. Others have also developed alternative

implementations of these Sun technologies, such as the GNU Compiler for Java (byte code

compiler), GNU Class path (standard libraries), and Iced Tea-Web (browser plug-in for applets).

2.2.1.1 Versions of Java

The Java language has undergone several changes since JDK 1.0 as well as numerous additions

of classes and packages to the standard library. Since J2SE 1.4, the evolution of the Java

language has been governed by the Java Community Process (JCP), which uses Java

Specification Requests (JSRs) to propose and specify additions and changes to the Java platform.

The language is specified by the Java Language Specification (JLS); changes to the JLS are

managed under JSR 901.

In addition to the language changes, much more dramatic changes have been made to the Java

Class Library over the years, which have grown from a few hundred classes in JDK 1.0 to over

three thousand in J2SE 5. Entire new APIs, such as Swing and Java2D, have been introduced,

and many of the original JDK 1.0 classes and methods have been deprecated. Some programs

allow conversion of Java programs from one version of the Java platform to an older one (for

example Java 5.0 back ported to 1.4) (see Java back porting tools).

After the Java 7 release, Oracle promised to go back to a 2-year release cycle. However, in 2013,

Oracle announced that they would delay Java 8 by one year, in order to fix bugs related to

Java security.

JDK Alpha and Beta (1995)

Alpha and Beta Java public releases had highly unstable APIs and ABIs. The supplied Java web

browser was named Web Runner.

10

JDK 1.0 (January 23, 1996)

Originally called Oak. Initial release the first stable version, JDK 1.0.2, is called Java 1.

JDK 1.1 (February 19, 1997)

Major additions included:

an extensive retooling of the AWT event model

inner classes added to the language

JavaBeans

JDBC

RMI

Reflection which supported Introspection only, no modification at runtime was possible.

JIT (Just In Time) compiler on Microsoft Windows platforms, produced for JavaSoft by

Symantec

J2SE 1.2 (December 8, 1998)

Codename Playground. This and subsequent releases through J2SE 5.0 were rebranded

retrospectively Java 2 and the version name "J2SE" (Java 2 Platform, Standard Edition) replaced

JDK to distinguish the base platform from J2EE (Java 2 Platform, Enterprise Edition) and J2ME

(Java 2 Platform, Micro Edition). This was a very significant release of Java as it tripled the size

of the Java platform to 1520 classes in 59 packages. Major additions included:

strictfp  keyword

the Swing graphical API was integrated into the core classes

Sun's JVM was equipped with a JIT compiler for the first time

Java plug-in

Java IDL, an IDL implementation for CORBA interoperability

Collections framework

J2SE 1.3 (May 8, 2000)

Codename Kestrel. The most notable changes were:

Hotspot JVM included (the Hotspot JVM was first released in April 1999 for the J2SE 1.2

JVM)

RMI was modified to support optional compatibility with CORBA

Java Naming and Directory Interface (JNDI) included in core libraries (previously available

as an extension)

Java Platform Debugger Architecture (JPDA)

11

Java Sound

Synthetic proxy classes

J2SE 1.4 (February 6, 2002

Codename Merlin. This was the first release of the Java platform developed under the Java

Community Process as JSR 59. Major changes included:

Language changes

assert  keyword (Specified in JSR 41.)

Library improvements

regular expressions modeled after Perl regular expressions

exception chaining allows an exception to encapsulate original lower-level exception

Internet Protocol version 6 (IPv6) support

non-blocking IO (named New Input/output, NIO) (Specified in JSR 51.)

logging API (Specified in JSR 47.)

image I/O API for reading and writing images in formats like JPEG and PNG

integrated XML parser and XSLT processor (JAXP) (Specified in JSR 5 and JSR 63.)

integrated security and cryptography extensions (JCE, JSSE, JAAS)

Java Web Start included (Java Web Start was first released in March 2001 for J2SE 1.3)

(Specified in JSR 56.)

Preferences API (java.util.prefs)

Public support and security updates for Java 1.4 ended in October 2008. Paid security updates for

Oracle customers ended in February 2013. [11]

J2SE 5.0 (September 30, 2004)

Codename Tiger. Originally numbered 1.5, which is still used as the internal version number.

The number was changed to "better reflect the level of maturity, stability, scalability and security

of the J2SE."[12] This version was developed under JSR 176.

J2SE 5.0 entered its end-of-public-updates period on April 8, 2008; updates are no longer

available to the public as of November 3, 2009. Updates were available to paid Oracle customers

until May 2015.[13]

Tiger added a number of significant new language features:[14][15]

Generics: Provides compile-time (static) type safety for collections and eliminates the need

for most typecasts (type conversion). (Specified by JSR 14.)

12

Metadata: Also called annotations; allows language constructs such as classes and methods to

be tagged with additional data, which can then be processed by metadata-aware utilities.

(Specified by JSR 175.)

Autoboxing/unboxing: Automatic conversions between primitive types (such as  int )

and primitive wrapper classes (such as  Integer ). (Specified by JSR 201.)

Enumerations: The  enum  keyword creates a typesafe, ordered list of values (such

as  Day.MONDAY ,  Day.TUESDAY , etc.). Previously this could only be achieved by non-

typesafe constant integers or manually constructed classes (typesafe enum pattern).

(Specified by JSR 201.)

Varargs: The last parameter of a method can now be declared using a type name followed by three dots (e.g.  void drawtext(String... lines) ). In the calling code any number of parameters

of that type can be used and they are then placed in an array to be passed to the method, or

alternatively the calling code can pass an array of that type.

Enhanced  for each  loop: The  for  loop syntax is extended with special syntax for iterating

over each member of either an array or any  Iterable , such as the standard  Collection  classes.

(Specified by JSR 201.)

Improved semantics of execution for multithreaded Java programs. The new Java memory

model addresses issues of complexity, effectiveness, and performance of previous

specifications.

Static imports

There were also the following improvements to the standard libraries:

Automatic stub generation for RMI objects.

Swing: New skinnable look and feel, called synth.

The concurrency utilities in package java.util.concurrent.

Scanner class for parsing data from various input streams and buffers.

Java 5 is the last release of Java to officially support the Microsoft Windows 9x line (Windows

95, Windows 98, Windows ME),  while Windows Vista is the newest version of Windows that

J2SE 5 was supported on prior to Java 5 going end of life in October 2009.

Java 5 Update 5 (1.5.0_05) is the last release of Java to work without any problems on Windows

NT 4.0.

Java 5 is the default version of Java installed on Apple Mac OS X 10.5 (Leopard). Java 6 can be

installed and set as the default to be used on 64-bit (Core 2 Duo and higher) processor machines.

Java 6 is also supported by 32-bit machines running Mac OS X 10.6 (Snow Leopard).

13

Java SE 6 (December 11, 2006)

Codename Mustang. As of this version, Sun replaced the name "J2SE" with Java SE and

dropped the ".0" from the version number.Internal numbering for developers remains 1.6.0. This

version was developed under JSR 270.

During the development phase, new builds including enhancements and bug fixes were released

approximately weekly. Beta versions were released in February and June 2006, leading up to a

final release that occurred on December 11, 2006.

Major changes included in this version:

Support for older Win9x versions dropped; unofficially, Java 6 Update 7 was the last release

of Java shown to work on these versions of Windows. This is believed to be due to the major

changes in Update 10.

Scripting Language Support (JSR 223): Generic API for tight integration with scripting

languages, and built-in Mozilla JavaScript Rhino integration

Dramatic performance improvements for the core platform, and Swing.

Improved Web Service support through JAX-WS (JSR 224)

JDBC 4.0 support (JSR 221).

Java Compiler API (JSR 199): an API allowing a Java program to select and invoke a Java

Compiler programmatically.

Upgrade of JAXB to version 2.0: Including integration of a StAX parser.

Support for pluggable annotations (JSR 269).

Many GUI improvements, such as integration of SwingWorker in the API, table sorting and

filtering, and true Swing double-buffering (eliminating the gray-area effect).

JVM improvements include: synchronization and compiler performance optimizations, new

algorithms and upgrades to existing garbage collection algorithms, and application start-up

performance.

Java 6 reached the end of its supported life in February 2013, at which time all public updates,

including security updates, were scheduled to be stopped. Oracle released one more update to

Java 6 in March 2013, which patched some security vulnerabilities.

Java SE 7 (July 28, 2011)

Java 7 (codename Dolphin[96]) is a major update that was launched on July 7, 2011[97] and was

made available for developers on July 28, 2011.[98] The development period was organized into

thirteen milestones; on June 6, 2011, the last of the thirteen milestones was finished.[99][100] On

average, 8 builds (which generally included enhancements and bug fixes) were released per

milestone. The feature list at the Open JDK 7 project lists many of the changes.

14

Additions in Java 7 include:

JVM support for dynamic languages, with the new invoke dynamic byte code under JSR-292,

following the prototyping work currently done on the Multi Language Virtual Machine

Compressed 64-bit pointers (available in Java 6 with -XX:+UseCompressedOops)

These small language changes (grouped under a project named Coin):

Strings in switch

Automatic resource management in try-statement

Improved type inference for generic instance creation, aka the diamond operator

Simplified varargs method declaration

Binary integer literals

Allowing underscores in numeric literals

Catching multiple exception types and rethrowing exceptions with improved type

checking

Concurrency utilities under JSR 166

New file I/O library (defined by JSR 203) adding support for multiple file systems, file

metadata and symbolic links. The new packages are java.nio.file, java.nio.file.attribute

and java.nio.file.spi

Timsort is used to sort collections and arrays of objects instead of merge sort

Library-level support for elliptic curve cryptography algorithms

An XRender pipeline for Java 2D, which improves handling of features specific to

modern GPUs

New platform APIs for the graphics features originally implemented in version 6u10 as

unsupported APIs

Enhanced library-level support for new network protocols, including SCTP and Sockets

Direct Protocol

Upstream updates to XML and Unicode

Java Deployment Rulesets

Lambda (Java's implementation of lambda functions), Jigsaw (Java's implementation

of modules), and part of Coin were dropped from Java 7, and released as part of Java 8

(except for Jigsaw, which will be in Java 9).

Java 7 was the default version to download on java.com from April 2012 until Java 8 was

released.

15

Java SE 8 (March 18, 2014)

Java 8 was released on 18 March 2014, and included some features that were planned for Java 7

but later deferred.

Work on features was organized in terms of JDK Enhancement Proposals (JEPs).

JSR 335, JEP 126: Language-level support for lambda expressions (officially, lambda

expressions; unofficially, closures) under Project Lambda and default methods (virtual

extension methods)  which make multiple inheritance possible in Java. There was an ongoing

debate in the Java community on whether to add support for lambda expressions. Sun later

declared that lambda expressions would be included in Java and asked for community input

to refine the feature. Supporting lambda expressions also allows the performance

of functional-style operations on streams of elements, such as MapReduce-inspired

transformations on collections. Default methods allow an author of API to add new methods

to an interface without breaking the old code using it. It also provides a way to use multiple

inheritance, multiple inheritance of implementation more precisely.

JSR 223, JEP 174: Project Nashorn, a JavaScript runtime which allows developers to embed

JavaScript code within applications

JSR 308, JEP 104: Annotation on Java Types

Unsigned Integer Arithmetic

JSR 337, JEP 120: Repeating annotations

JSR 310, JEP 150: Date and Time API

JEP 178: Statically-linked JNI libraries

JEP 153: Launch JavaFX applications (direct launching of JavaFX application JARs)

JEP 122: Remove the permanent generation

Java 8 is not supported on Windows XP but as of JDK 8 update 25, it can still be installed and run

under Windows XP.[192] Previous updates of JDK 8 could be run under XP, but had to be installed

after a forced installation by directly unzipping files from the installation executable.

From October 2014, Java 8 has been the default version to download from the official website.

16

CHAPTER III

3.1 OBJECTIVES OF THE STUDY

1. To design a user-friendly GUI which user can understand easily.

2. To perform basic mathematical calculations.

3. To save cost and time.

17

CHAPTER IV

SOFTWARE AND HARDWARE CONFIGURATION

4.1 HARDWARE CONFIGURATION

● Processor Name: Dual Core

● Processor Speed: 3.2 GHz

● RAM: 1 GB

● Hard Disk Capacity: 80 GB

● Display Device: 14’ to 19’ Inch Monitor

● Keyboard Type: PS2 or USB

● Mouse Type: PS2 or USB

4.2 SOFTWARE CONFIGURATION

For Calculator:

● Technology Implemented: NETBEANS IDE 8.0.2

● Language Used: Java 8

● User Interface Design: AWT ,SWING

Software Product:

● Operating System: Windows XP/ Windows 7

● Programming Language: Java 8

● Software: Net Beans

18

CHAPTER V

SYSTEM DESIGN

System Design involves the analysis, design, and configuration of the necessary hardware and

software components to support your solution's architecture. Systems design is the process of

defining the architecture, components, modules, interfaces, and data for a system to satisfy

specified requirements. One could see it as the application of systems theory to product

development.

5.1 LOGICAL DESIGN

The logical design of a system pertains to an abstract representation of the data flows, inputs

and outputs of the system. This is often conducted via modeling, using an over-abstract (and

sometimes graphical) model of the actual system. In the context of systems design are included.

5.2 PHYSICAL DESIGN

The physical design relates to the actual input and output processes of the system. This is laid

down in terms of how data is input into a system, how it is verified/ authenticated, how it is

processed, and how it is displayed as output. Put another way, the physical portion of systems

design can generally be broken down into three sub-tasks:

5.2.1 USER INTERFACE DESIGN

Concerned with how users add information to the system and with how the systems presents

information back to them. Data Design is concerned with how the data is represented and

stored within the system. Finally, Process Design is concerned with how data moves through the

system, and with how and where it is validated, secured and/or transformed as it flows into,

through and out of the system. At the end of the systems design phase, documentation

describing the three sub-tasks is produced and made available for use in the next phase.

19

5.2.2 PHYSICAL DESIGN

In this context, does not refer to the tangible physical design of an information system. To use

an analogy, a personal computer's physical design involves input via a keyboard, processing

within the CPU, and output via a monitor, printer, etc.

5.3.3 UML DIAGRAM

UML Diagram helps to represent the complex system by separating the aspect that are

unimportant from those that are important and helps to easily visualize the system. UML

diagrams are independent of any of the programming languages and the development process.

5.3.1 DATA FLOW DIAGRAM

DFD is one of the most important modeling tools. It is used to model the system components.

These components are the system process, the process, an external entity that interacts with the

system, uses the data and the information flows in the system.

DFD shows how the information moves through the system and how it is modified by a series of transactions. It is a graphical technique that depicts information flow and that information that is

applied as data moves from input to output.

.

20

Fig :- 5.3.3.1 0-Level DFD

21

Fig :- 5.3.3.2 1-Level DFD

22

Fig :- 5.3.3.3 2-Level DFD

23

CHAPTER VI

TESTING

Software Testing is the process used to help identify the correctness, completeness, security and

quality of developed computer software. Testing is a process of technical investigation,

performed on behalf of stakeholders, that is intended to reveal quality-related information about

the product with respect to the context in which it is intended to operate. In general, software

engineers distinguish software faults from software failures.

Acquire And Study The Test Strategy

Determine When The Testing Should Occur

Build The System Test Plan

Build The Unit Test Plan

Select The Mode of Test

6.1 MODE OF TESTING

It is necessary to select the test mode in which the testing method to be carried out. The two

different modes are manual and automated tool. The real time projects needs frequent

interactions. So, it is impossible to carry out the testing process by means of automated tool. Our

project uses manual testing.

6.1.1 UNIT TESTING

This phase examines the techniques, assessment and management of unit testing and analysis.

Testing and analysis strategies are categorized according to whether they goal is functional or

structural or combination of these. It will assist a software engineer to define, conduct and

evaluate unit tests and to assess new unit test techniques.

6.1.2 SYSTEM TESTING

Once the entire system has been built then it has to be tested against the "System Specification"

to check if it delivers the features required. In essence System Testing is not about checking the

individual parts of the design, but about checking the system as a whole.

24

6.1.3 REGRESSION TESTING

This involves assurance that all aspects of an application system remain functional after testing.

The introduction of change is the cause of problems in previously tested segments. It is retesting

unchanged segments of the application system

6.1.4 Black Box Testing

In a black box, the test item is treated as “black” since its logic unknown: all that is known is

what goes in and what comes out, or the input and output. In black box testing you try various

inputs and examine the resulting outputs, you can learn what the box does but nothing more about

how its conversion is implemented. Black box testing works very nicely in the testing objects in

an object oriented environment.

6.1.5 White Box Testing

White box testing assumes that the specific logic is important and must be tested to guarantee the

system’s proper functioning. The main use of the white box testing is in error based testing. It is

predict on close examination of procedural detail logical providing test cases that exercise

specific sets of conditions and/or loops tests path enough the software

25

CHAPTER VII

IMPLEMENTATION

Implementation includes all those activities that take place to convert from old system to new.

The new system may be totally new replacing an existing manual or automated system, or it may

be major modification to an existing system. In other case, proper implementation is essential to

provide a reliable system to meet organization requirements.

A well-designed system, if not operated and used properly could fail. Training the users is

important, as if not done well enough could prevent the successful implementation of an

information system. Through the systems development life cycle the user has been involved.

By this stage the analyst should possess an accurate idea of the users they need to be trained.

They must know what their roles will be, how they can use the system and what the system will

do and will not do. Both system operators and users need training.

During their training, they need to be given a trouble-shooting list that identifies possible

problems and identifies remedies for the problem. They should be advised of the common mal-

functions that may arise and how to solve them.

26

CHAPTER VIII

MAINTENANCE

Inevitably the system will need maintenance. Software will definitely undergo change once it is delivered to the customer. There are many reasons for the change. Change could happen because

of some unexpected input values into the system. In addition, the changes in the system could directly affect the software operations. The software should be developed to accommodate

changes that could happen during the post implementation period.

27

CHAPTER IX

USER MANUAL

The user manual is a catalog or a guide for a user to look up at, when he has a problem with the

system or is lost in something and needs a way to get out of there. It does can be a flowchart

explaining the user how to move within the system and how to make the best of it.

Fig: Calculator GUI

28

CHAPTER X

CONCLUSION

Using this project user can easily access basic operations of calculation like addition, subtraction, multiplication and division.

Basic and simple GUI Interface gives ease of access to user. Providing efficient working.

29

ANNEXURE I

BIBLIOGRAPHY

WEB SITE

1. www.wikipedia.com

2. www.stackoverflow.com

3. www.w3schools.com

30