Sie sind auf Seite 1von 54

Acknowledgement

It is a great pleasure for us to acknowledge all those who have contributed towards the conception, origin and nurturing of this project that is on System analysis the ATM System. The way cant walk itself. We have to walk on it. or that we must have a guide. !any guides have contributed to the successful completion of the project. We would like to place on record my grateful thanks to each one of them who help us in this project. "efore we get into thick of the thing, we would like to add a few heartfelt words for the people who gave us unending time support whichever and whenever necessary.

#ur grateful thanks go to our $ept., which provides us an opportunity as a project subject in 6th Semester to develop a report work skill in this System analy%ing. We would like to thank our parents & friends for giving us full feedback when we are in trouble. #ur special thanks go to Ms. Kinjal Jadav to give their e'pert guidance to us whenever necessary. (ast but not the least) I heartily thank our *.#.$. Mr. Mahesh Panchal.

PREFACE
+ase study ,Software -ngineering. is a long establishment method of organi%ing, learning, so as to encourage coordination of Subject areas, it aims at closer integration of theory and practical give fundamental basic for student learning and produce, more practical techni/ues. 0roject method in common with other students centered techni/ue help to develop market survey, planning decision making on for e'ample and identifying the critical integrated industrial process for producing e/uipment, a component or a model of process.

123+-345 123+-346

+omputer -ngineering

A S!RAC!
This report attempts to understand the design of an 7utomated Teller !achine ,7T!. system, a device used by bank customers to process account transactions. Typically, a user inserts into the 7T! a special plastic card that is encoded with information on a magnetic strip. The strip contains an identification code that is transmitted to the bank8s central computer by modem. To prevent unauthori%ed transactions, a personal identification number ,0I9. must also be entered by the user using a keypad. The computer then permits the 7T! to complete the transaction) most machines can dispense cash, accept deposits, transfer funds, and provide information on account balances. "anks
123+-345 123+-346

+omputer -ngineering

have formed cooperative, nationwide networks so that a customer of one bank can use an 7T! of another for cash access. Some 7T!s will also accept credit cards for cash advances. The first 7T! was installed in 4:;: by +hemical "ank at its branch in <ockville +entre, 9ew =ork. 7 customer using a coded card was dispensed a package containing a set sum of money.

Project Pro"ile
Project !itle Front End !ool ack End !ool Project Plat"orm Project %&ide 'evelo(ed $ S&1mitted !o # A!M S$tem # !icrosoft >isual Studio 5112 # !icrosoft S?( Server 511@ # 7S0.9-T #Ms. Kinjal K. Jadav #Mr. Kamlesh Korat)*+,CE,-./ Mr. Chirag Korat)*+,CE,-0/ # $epartment of +omputer -ngineering, Aalol Institute #f Technology 123+-345 123+-346

+omputer -ngineering

'E!A23 4F C5AP!ERS
-.* 2ntrod&ction
-.- Project S&mmar$ -.0 P&r(ose -.. Sco(e

0.* Project Management


0.- Project Planning and sched&ling 0.-.- Project 'evelo(ment A((roach 0.-.0 Project Plan 0.-.. Sched&le Re(resentation 0.0 Risk Management 0.0.- Risk 2denti"ication 0.0.0 Risk Anal$sis 0.0.. Risk Planning 0.. Estimation 0...- E""ort Estimation

..* S$stem Re6&irements St&d$


..- 7ser Characteristics ..0 5ardware and So"tware Re6&irements ... Constraints 123+-345 123+-346 @ +omputer -ngineering

8.* S$stem Anal$sis


8.- St&d$ o" C&rrent S$stem 8.0 Pro1lem and 9eaknesses o" C&rrent S$stem 8.. Re6&irements o" :ew S$stem 8.8 Feasi1ilit$ St&d$ 8.; Re6&irements <alidation 8.6 F&nctions 4" S$stem 8.6.- 7se Cases= event trace or scenario 8.> 'ata Modeling 8.>.- Flow chart or activit$ design 8.>.0 Class 'iagram? E,R diagrams 8.>.. S$stem Activit$ or 41ject interaction 'iagram 8.>.8 'ata 'ictionar$ 8.+ F&nctional and ehavioral Modeling 8.+.- Conte@t 'iagram 8.+.0 'ata Flow 'iagram )* and - level/ 8.+.. Process S(eci"ication and 'ecision !a1le 8.+.8 Control "low diagram

;.* !esting
;.- !esting Plan ;.0 !esting Strateg$ ;.. !esting Methods ;.8 !est Cases

6.* 3imitation and F&t&re Enhancement >.* Concl&sion and 'isc&ssion

123+-345 123+-346

+omputer -ngineering

-.* 2ntrod&ction

-.- Project S&mmar$

7n automated teller machine ,7T!. or automatic banking machine ,7"!. is a computerised telecommunications device that provides the clients of a financial institution with access to financial transactions in a public space without the need for a cashier, human clerk or bank teller. #n most modern 7T!s, the customer is identified by inserting a plastic 7T! card with a magnetic stripe or a plastic smart card with a chip, that contains a uni/ue card number and some security information such as an e'piration date or +>>+ ,+>>.. 7uthentication is provided by the customer entering a personal identification number ,0I9.. 123+-345 123+-346

+omputer -ngineering

4.5 P&r(ose

Dsing an 7T!, customers can access their bank accounts in order to make cash withdrawals ,or credit card cash advances. and check their account balances as well as purchase cellphone prepaid credit. If the currency being withdrawn from the 7T! is different from that which the bank account is denominated in ,egE Withdrawing Fapanese =en from a bank account containing DS $ollars., the money will be converted at a wholesale e'change rate. Thus, 7T!s often provide the best possible e'change rate for foreign travelers and are heavily used for this purpose as well. 7T!s are known by various other names including 7utomated Transaction !achine, automated banking machine, cashpoint ,in "ritain.,money machine, bank machine, cash machine, hole3in3the3wall, "ancomat ,in various countries in -urope and <ussia., !ultibanco ,after a registered trade mark, in 0ortugal., and 7ny Time !oney ,in India.

-.. Sco(e

The main purpose of the 7T! division and information service is to provide the customers financial fle'ibility, worldwide acceptance and round3the clock convenience. "ank issues only >IS7 +redit +ards, the renowned +redit +ard brand. +ardholders can purchase goodsGservices up to the credit limit and can reuse the credit facility upon repayment. +redit +ard is a safer substitute to cash and is the major mode of payment worldwide. Standard +hartered "ank is the first to introduce the T7A7 +<-$IT +7<$. The card is issued basically to a persons name and the specific person can use the card in anywhere in "angladesh. The business activity of 0remier "ank +redit +ard section is to

123+-345 123+-346

+omputer -ngineering

keep the records of all sales and customers re/uests, the information of cardholders and reports them to necessary documents.

0.* Project management


In this chapter we will discuss about project planning and scheduling. #ur goal is to establish a pragmatic strategy for controlling, tracking, and monitoring a comple' technical project. In project management following things must be done. 0roject 0lanning and Scheduling <isk !anagement -stimation In 0roject planning and scheduling, 0lanning of the project is done. In scheduling different task are schedule according to the deadline of the project.

0.-Project Planning and sched&ling


0roject planning must deals with the following things. Project Com(le@it$# , 0roject comple'ity has a strong effect but is heavily influenced by past practitioner e'perience. Project SiAe# , 7s si%e increases the interdependency of elements also grow. Watch out for scope creep. !he degree o" str&ct&ral &ncertaint$# , the degree to which re/uirements are solidified and the ease of functional decomposition.The purpose of project planning is to ensure that the end result is completed on time, within budget, and e'hibits /ualityH

123+-345 123+-346

+omputer -ngineering

0.-.-Project develo(ment a((roach

The Spiral model is an evolutionary software process model that couples the iterative nature of prototyping with the controlled and systematic aspects of the linear se/uential model. It provides the potential for rapid development of incremental versions of the software. Dsing the spiral model, software is developed in series of incremental release. 7 spiral model is divided into a number of framework activities, also called task regions. There are between three and si' task regions. model that contains si' task regionsE 123+-345 123+-346 +ustomer communication I tasks re/uired to establish effective communication between developer and customer. 41 +omputer -ngineering igure depicts a spiral

0lanning I tasks re/uired to define resources, timelines, and other project related information. <isk analysis I tasks re/uired to assess both technical and management risks. -ngineering I tasks re/uired to build one or more representations of the application. +onstruction and release I tasks re/uired to construct, test, install, and provide user support. +ustomer evolution I tasks re/uired to obtain customer feedback based on evolution of the software representations created during the engineering stage and implemented during the installation stage.

-ach of the regions is populated by a set of work tasks, called a task set, that are adapted to the characteristics of the project to be undertaken. or small projects, the number of work tasks and their formality is low. higher level of formality. In our case, we have to provide medium level of formality for making a good project report. We will take decision about cost, schedule and number of iterations re/uired to complete the software. 0.-.0Project Plan Stages o" So"tware 3i"ec$cle So"tware Re6&irement Anal$sis This is the first stage of the project, which involves interaction with the customer to understand hisGher needs, re/uirements, information, re/uired functions, performance and interfacing in !(! software. or this purpose re/uirement analyst will arrange a meeting for gathering information and additional details for software development. 7fter completing re/uirement 123+-345 123+-346 44 +omputer -ngineering or larger, more critical projects, each task region contains more work tasks that are defined to achieve a

gathering tasks developer team will take a look for understand how re/uirements can be computeri%ed. The re/uirement is documented in the form of a Software <e/uirement Specification ,S<S. which is then presented to the customer for review. 'esign "eginning once software re/uirements have been analy%ed and specified, software design is the first of three technical activities I design, code generation, and test I that are re/uired to build and verify the software. $esign is multi level process which defines following detailsE $ata $esign 7rchitecture $esign Interface $esign +omponent level $esign

'evelo(ment The design must be translated into a machine3readable form. The coding step performs this task. In this stage, the developers will actually code the programs. The specifications arrived at the design stage for each and every function will be converted to code using tools that are finali%ed for the implementation of the Software. 7t this stage the testing methodology to be adopted will be finali%ed. or each program test cases will be prepared and for each of these test cases, test data will also be prepared. The actual developers will do a first cur checking at this stage to see that the programs written by them are error free.

123+-345 123+-346

!esting

45

+omputer -ngineering

In this stages the test group of the development team, using the cases and the test data already prepared will test the programs. #nly after all the functions are tested singularly, an integrated testing will be performed to see that inter3function dependability is satisfied. Separate test cases and test data will be worked out for the integrated testing. Acce(tance !est This round of testing will be performed by the test group formed by the users of !(! software. This test group has to insure that the developed software is working as per their re/uirements. If some problems are found then it should be immediately communicated $evelopment group so that the problem can be looked into and hence rectified. 'ata Creation or software, data is most important part. $ata is information which is handled by software. So before coding software, all master table data will have to be created. 2m(lementation 9ow the implementation of software is to be done by programmers. 7ll the re/uirements and information gathered by the analyst is now take actual image in form of software. 7fter making software it is uploaded in to the system so users, for whom software is developed, can use the software. #nce we e'amine that the project is feasible, we undertake project planning. The table below describes how we planned our project.

0.-..Sched&le Re(resentation

123+-345 123+-346

46

+omputer -ngineering

J
4 5 6 B @ ; C 2

0hases
0roject Summary 0roject 0lan <isk 7nalysis -ffort -stimation System <e/uirement Study easibility Study $ata and function !odeling Testing

Time 0eriod
14G15G5144 12G15G5144 4@G15G5144 4@G15G5144 14G16G5144 12G16G5144 5:G16G5144 5:G16G5144

0.0 Risk Management


0.0.- Risk 2denti"ication $uring the project plan we have consider all the proactive which we have think we will face during the project period. *ere I have listed the risks which we have considered during the project planE 0ossibility that the components are not available during the project period. 0ossibility that products purchased was not compatible. 0ossibility that the hardware resources are not available during the project period. 0ossibility that -thernet connection between robot controller and computer may not occur, to which we have to make the connection might not available. 0ossibility that software inter3compatibility may not be there. 0.0.0 Risk Anal$sis <isk analysis is the important aspect of the project planning, whenever planning the software, programmer always has to consider the risks of the projects which he might face in the future during designing the software. <isks are of two types Risk 2m(act Risk 123+-345 123+-346 4B E""ect +omputer -ngineering 0roactive <isk. <eactive <isk.

0ossibility of getting illness. 0ossibility of component not available. 0ossibility of component not effective. 0ossibilities of hardware resources are not available. 0ossibility of robot controller not available. 0ossibility of communication between systems might not happen on time. Proactive Risk Assessment !a1le

Serious. +atastrophic Serious. +atastrophic. Serious. Serious

This are the proactive risks which we can consider during the project plan period so we can cop up with them easily and we can find the solution easily but we can find other proactive risks which we havent considered in the project planE

Risk 0ossibility that because of some problem we Serious have lost the backup of some days. 0ossibility that because of finance problem in the company we wont get the full +atastrophic resources. 0ossibilities that project !anager leave the Serious project.

E""ect

Reactive Risk Assessment !a1le 0roactive risks are most dangerous risks which we havent considered during the project period and to cop up with them is not easy. These kinds of risks are risks, so programmer must have been active to cop up with them smartly. Risk Estimation <isk estimation attempts to rate each risk in two waysE The likelihood or probability that risk is real and. The conse/uences of the problems associated with the risk should it occurs. The project planner, along with other managers and technical staff, performs four risk projection stepsE

123+-345 123+-346

4@

+omputer -ngineering

-stablish a scale rate that reflects the perceived likelihood of a risk. $elineate the conse/uences of the risk. -stimate the impact of the risk on the project and the product. 9ote the overall accuracy of the risk projection so that there will be no misunderstanding.

The intent if these steps are to consider risks in a manner that leads to prioriti%ation. 9o software team has the resources to address every possible risk with the same degree of rigor. "y prioriti%ing risks, the team can allocate resources where they will have the most impact. 0.0.. Risk Planning 7fter estimating all the risks and risk effects, we will look how to manage this kind of risksE With the kind of proactive risks we will prepare the plan for how to manage these risks, we will think about their options, if their kinds of risks are facing and if they are reactive risks we have to manage them on the spot to avoid their dangerous effectsE Risk 0ossibility of getting illness. Risk Management

We will provide some more time ,appro'. one week. to prepare the software. 0ossibilities of the components are not We will check for other components, which available. have the same effect as those components. We will manage for the new components of 0ossibility of component not effective. that kind. 0ossibilities of hardware resources are not We will manage for optional hardware, while available starting the project. 0ossibility of robot controller not available. We try to arrange a new controller.

0.. Estimation
0...- E""ort Estimation
123+-345 123+-346

4;

+omputer -ngineering

-ffort estimation methods are one of the important tools for project managers in controlling human resources of ongoing or future software projects. The estimations re/uire historical project data including process and product metrics that characteri%e past projects. Software cost and effort estimation will never be an e'act science. Too many variables human, technical, environment, political can affect the ultimate cost of software and effort applied to develop it. *owever, software project estimation can be transformed from a black art to a series of systematic steps that provide estimate with acceptable risk. To achieve reliable cost and effort estimates, a number of options ariseE So"tware SiAing unction point si%ing Standard component si%ing

Pro1lem, ased Estimation (#+ and 0 data are used in two ways during software project -stimationE3 7s an estimation variable to si%e each element of the software and 7s baseline matrices collected from past projects and used in conjunction with estimation variables to develop cost and effort projections.

Sched&les #btain an early view of staffing re/uirements and constraints, and demonstrate the impact of changing deadlines, understaffing, and staff loading. B&alit$ ?uantify the impact on defect rates of building to deadlines or reducing staff. Risk ine tune risk levels for all the major types of riskE si%e, re/uirements, technology, maintenance, systems integration, and defects.

..* S$stem Re6&irements St&d$


..- 7ser Characteristics
123+-345 123+-346

4C

+omputer -ngineering

There are B types of user dealing with the system. Dser 7K 7dministrator 7dministratorE 7dmin is having all the rights on the application. Dser "K -mployee -mployeeE -mployee of the company is one of the B users of this project Dser +K 7nonymous Dser 7nonymous DserE 7nyone who visits website. 7nd any person applying for the posted job on the website. Dser $K +lient +lientE This is the registered user. Who come to know about hisGher projects progress

..0 5ardware and So"tware Re6&irement# 5ardware S(eci"ication# 0rocessor E Intel $ual based system 0rocessor Speed E 4L*% to 5 L*% <7! E 5@;!" to @45 !" *ard $isk E B L" to 61 L" Aeyboard E 41B keys So"tware S(eci"ication# (anguage E F$A 4.; $atabase E #racle :i #perating System E Windows 9TGM0G>ista <7! E @45 !"

... Constraints#
%eneral Constraints 123+-345 123+-346

42

+omputer -ngineering

4. This system will not take care of any virus problem that might occur on the computer with which it is installed. 7voiding the use of piratedGillegal software and ensuring that floppies and other removable media are scanned for viruses before use could minimi%e the possibility of viral infection. 5. <ecovery of data after a system crash will be possible only if backups are taken at regular intervals. 6. !anual interfaces cannot be fully avoided. $ocumented proofs like dates etc. will have to be verified by the concerned staff before entering it into the computeri%ed system 5ardware Constraints The performance of the system will be dependent on the machine conditions. The primary memory ,<7!. and the secondary memory ,*ard $isk Space. re/uirement of the system will be the same as that re/uired by the normal application and the operating system. 7nd the space re/uired storing the data. The space re/uired to store the data would increase as more and more records are added to the system. Ass&m(tions and 'e(endencies a. It is assumed that the user is familiar with the basic computer fundamentals. b. Timely backup of data should be taken to avoid data loss in case of system crash. c. loppies and other removable media should be scanned for viruses before use. d. It is assumed that the maintenance of the database will be assigned to the authori%ed person only. e. #nly authori%ed persons will be allowed inside the system

8.* S$stem Anal$sis


8.- St&d$ o" C&rrent S$stem
123+-345 123+-346

4:

+omputer -ngineering

The #"S 7dministration falls short of controlling the employees activities in analy%ing hisGher strengths and weakness. The decision for appraisal of assigning ne't project to the employee or to train himGher to enhance the skills I where lies with proper projection. *e is not provided with the detailed project information done or to be assigned based on 7pplication G >erticals.

8.0 Pro1lem and 9eaknesses o" C&rrent S$stem


9eed of e'tra manual effort. It used to take much time to find any employee 9ot very much accurate. $anger of losing the files in some cases.

8.. Re6&irements o" :ew S$stem


$ecision in assigning proper skillful hands for the project is an important issue in #"S !odule. The #"S 7dministrator should report with the personal holding the necessary skills re/uired for the project assignment. The decision in making analysis about the employees skills is a prime important before booting in. The proposed system of #"S !odule is the right software to be incorporated into the 7utomation of #"S Software for helping the organi%ation needs with respect to skilful *uman <esource. The proposed system provides detail general information about the employee along with -ducational, +ertification, Skill and 0roject details. It enhances the #"S !anagement in adding, viewing and updating employees details and generates various reports regarding employees skill and e'perience. Suggestions and Lrievances posted by the employees are upheld for taking care of the necessary steps in forwarding companys obligation. . A'<A:!A%ES 4F PR4P4SE' SCS!EM# >ery fast and accurate. 9o need of any e'tra manual effort. 9o fever of data loss. Fust need a little knowledge to operate the system. $oesnt re/uire any e'tra hardware device. 7t last very easy to find the employees.

8.8 FEAS2 232!C S!7'C#


123+-345 123+-346 51 +omputer -ngineering

#nce the problem is clearly understood, the ne't step is to conduct feasibility study, which is high3level capsule version of the entered systems and design process. The objective is to determine whether or not the proposed system is feasible. The t#"See tests of feasibility have been carried out. Technical easibility -conomical easibility #perational easibility

!EC5:2CA3 FEAS2 232!C


In Technical easibility study, one has to test whether the proposed system can be developed using e'isting technology or not. It is planned to implement the proposed system using java technology. It is evident that the necessary hardware and software are available for development and implementation of the proposed system. *ence, the solution is technically feasible.

EC4:4M2CA3 FEAS2 232!C


7s part of this, the costs and benefits associated with the proposed system compared and the project is economically feasible only if tangible or intangible benefits outweigh costs. The system development costs will be significant. So the proposed system is economically feasible. 4PERA!24:A3 FEAS2 232!C It is a standard that ensures interoperability without stifling competition and innovation among users, to the benefit of the public both in terms of cost and service /uality. The proposed system is acceptable to users. So the proposed system is operationally feasible.

8.; Re6&irements <alidation#


<e/uirement >alidation e'amines the specification to ensure that all system re/uirements have been stated unambiguously) those inconsistencies, errors have been detected and corrected and the work products conform to the standard. There are many re/uirements from user perspective and taken care while designing a system, are as followsE $ynamic nature of system. i.e. System change its working depending on situation. +omponent based definition of system. i.e. System is divided into smaller components which will work independently also there combined affort is result into output of system. 123+-345 123+-346 54 +omputer -ngineering

le'ibility of system. i.e. System should work with great ease with different types of documents. le'ible $atabase design should be done to accommodate information about new input. le'ible front3end design so that it can support functionality of all types of input. "ack3end should not affect front3end or vice versa. 7ll $atabase changes should be done by front3end only. Simplicity should be there in system design. Dser friendliness should be achieved. System should be easily !aintainable and 7daptive. $esign for such system is created in such a way that related information is kept in same tables. $ifferent information related to different component is stored in different tables. To make the task of data entry easy various combo bo'es and list The $atabase design should support the accommodation of new component information in a way, such that it should allow to continue the e'isting relationship with the other components and other parts of system. bo'es are designed so that user can have to just select the values from the given options.

8.6 F&nctions o" S$stem# 7se Case#


Dse case is a description of a set of se/uence of actions that a system performs that yields an observable result of value to a particular thing in a model. Lraphically, Dse +ase is rendered as an ellipse with dashed lines, usually including only its name as shown below.

0lace #rder

USE CASE DIAGRAM:-

123+-345 123+-346

55

+omputer -ngineering

8.> 'ata Modeling#

123+-345 123+-346

56

+omputer -ngineering

8.>.- Flow chart or activit$ design# AC!2<2!C '2A%RAM# 7n 7ctivity $iagram is essentially a flow chart showing flow of control from activity to activity. They are used to model the dynamic aspects of as system. They can also be used to model the flow of an object as it moves from state to state at different points in the flow of control. Content# 7ctivity diagrams commonly containE ork, Start & -nd Symbol

ACTIVITY DIAGRAM:-

8.>.0 Class 'iagram? E,R diagrams# 123+-345 123+-346

5B

+omputer -ngineering

+lass diagrams are the most common diagrams found in modeling object3oriented systems. 7 class diagram shows a set of classes, interfaces, and collaborations and their relationships. Lraphically, a class diagram is a collection of vertices and arcs.

CLASS DIAGRAM:-

123+-345 123+-346

5@

+omputer -ngineering

+lass $iagram is a graph that represents the relationship between the classes and represents their semantics. *ere 7T! works as main class. 7ll other classes are related with this class. 7T! does following operationsE - >erifyNpin,. - +heckNbalance,. - +ashNwithdrawal,. - !inistatement,. - 0rintNreceipt,. - 7notherNtransaction,.

7T! card related with 7T! through many to many relationship. It does following operationsE - InsertNcardNintoN7T!,. - InsertN0inNcode,. - <emoveNcardNafterNtransaction,.

7ccount holder related with 7T! through many to many relationship. It performs following operationsE - Withdrawal,. - Transfer,. - "alanceNin/uiry,.

123+-345 123+-346

5;

+omputer -ngineering

7T! server related with 7T! by one or many to one or many relationship. It also performs some task shown as belowE - DpdatingNafterNeachNtransaction,. - +hangingNtheNpinNcode,. - ShowingNe'actNbalanceNafterNeachNtransaction,.

"ank !anager associated with 7T! through one or many to one relationship. 7T! is not related with this class, but dependent on this class. So there is a dependent relationship assigned to them. "ank !anager does following tasksE - !anagingNdifferentNaccounts,. - !aintainingNsufficientNbalanceNinN7T!,. - 7ccessNtoNtheN7T!Nserver,.

*ere, a class "ank not related to any of the class, but some classes are dependent on these classes which are shown as dependent relationship with it. 9ormally this class performs following operationsE - +reateN7ccount,. - 7ccessingN7ccount,. - 0rovidingN7T!Ncard,.

123+-345 123+-346

5C

+omputer -ngineering

8.>.. S$stem Activit$ or 41ject interaction 'iagram# 7n Interaction diagram shows an interaction, consisting of a set of objects and their relationships, including the messages that may be dispatched among them. Interaction diagrams are used for modeling the dynamic aspects of the system. .

INTERACTION DIAGRAM:-

123+-345 123+-346

52

+omputer -ngineering

8.>.8 'ata 'ictionar$# 7 $ata $ictionary is a +atalogue I a repository of element in a system. 7s the name suggest, these elements center around data and the way these are structured to meet the user re/uirement and system needs. In $ata $ictionary we find list of all the elements are data flows, data stores, and process. The $ata $ictionary stores details and description of these elements.

123+-345 123+-346

5:

+omputer -ngineering

If anybody wants to know how many characters are in a data item, by what other names it is referenced in the system, or where it is used in the system, they should be able to find the answer in a property developed data dictionary. The $ata $ictionary is developed during data flow analysis and assists the system development in determining the user re/uirement.

2m(ortance o" 'ata 'ictionar$E3 7nalysis use data dictionary for five important reasonsE -. To manage the detail in large system. 0. To communicate a common meaning for all system elements. .. To $ocument the feature of the system. 8. To acilitates analysis of the details in order to evaluate characteristics and determine where system changes should be made. ;. To (ocate error and omissions in the system.

The ollowing Tables are used within the systemE

1. ATM ::
It provides information about 7T!s "ank, "ranch and +ompany. A!M

123+-345 123+-346

61

+omputer -ngineering

ranchDCode A!MDCode Com(an$

2nteger 2nteger String

Code o" (artic&lar ranch Code o" (artic&lar A!M :ame o" Man&"act&rer o" A!M

2. ATM_Card ::
It provides information about 7T! card, its holder and "ank. A!MDCard CardD:o P2:DCode C&stomerD:ame ankD:ame 2nteger 2nteger String String :o. o" (artic&lar Card Secrete code o" card :ame o" Card 5older :ame o" ank

3. Account_ o!d"r ::
It has all the details about 7T! +ard holder. Acco&ntDholder :ame 123+-345 123+-346 String :ame o" Acco&nt owner

64

+omputer -ngineering

Address Acco&ntD:o PhoneD:o

String 2nteger 2nteger

Address o" Acco&nt owner Acco&nt no. o" card holder Phone no. o" Acco&nt owner

#. ATM_$"r%"r ::
It has detail of 7T!. 7s well as it provides interface between "ank and 7ccount holder. A!MDserver Man&"act&rerDCom(an$ String :ame o" Com(an$ Man&"act&rer

:ameDo"DServer Con"ig&ration

String String

Server name to identi"$ it Con"ig&ration set 1$ Manager ank

&. 'an(_Mana)"r ::
It contains data of managers who set and manage the server of 7T!.

ankDManager

123+-345 123+-346

65

+omputer -ngineering

:ame ranch

String String

:ame o" Manager ranch name manager do work where

*. 'an( ::
It provides detail of "ank to get information about 7ccount of a user.

ank ankD:ame 3ocation ankDCode String String 2nteger :ame o" ank 3ocation o" ank Code o" ank to identi"$ it

8.+.- Conte@t 'iagram


The top3level diagram is often called a Ocontext diagram. It contains a single process, but it plays a very important role in studying the current system. The conte't diagram defines the system that will be studied in the sense that it determines the boundaries. 7nything that is not inside the process identified in the conte't diagram will not be part of the system study. 123+-345 123+-346

66

+omputer -ngineering

8.+.0 'ata Flow 'iagram )* and - level/


7 graphical tool used to describe and analy%e the moment of data t#"Sough a system manual or automated including the process, stores of data, and delays in the system. $ata low $iagrams are the central tool and the basis from which other components are developed. The transformation of data from input to output, t#"Sough processes, may be described logically and independently of the physical components associated with the system. The $ $ is also known as a data flow graph or a bubble chart. 7 graphical tool used to describe and analy%e the moment of data through a system manual or automated including the process, stores of data, and delays in the system. $ata low $iagrams are the central tool and the basis from which other components are developed. The transformation of data from input to output, through processes, may be described logically and independently of the physical components associated with the system. The $ $ is also known as a data flow graph or a bubble chart. !CPES 4F 'A!A F349 '2A%RAMS# $ata low $iagrams are of two types as followsE ,a. 0hysical $ $ ,b. (ogical $ $ 4. P5CS2CA3 'F'# Structured analysis states that the current system should be first understand correctly. The physical $ $ is the model of the current system and is used to ensure that the current system has been clearly understood. 0hysical $ $s shows actual devices, departments, and people etc., involved in the current system.

0. 34%2CA3 'F'# (ogical $ $s are the model of the proposed system. They clearly should show the re/uirements on which the new system should be built. (ater during design activity this is taken as the basis for drawing the systems structure charts.

Data +!o, D-a)ra./0"%"!-12:-

123+-345 123+-346

6B

+omputer -ngineering

This diagram shows the 7utomatic Teller System Software and the hardware that it interacts with. The arrows show the direction and type of data flowing between the software and each hardware element.

E@ternal Entities#,
C4:!R43 SCS!EM This system enables and disables the customer interface and receives customer re/uests and system reports. 7 suitable +ontrol System would be a personal computer linked to a central computer system with access to the 7ccounts $atabase. The customer interface ,keypad, display, 123+-345 123+-346 6@ +omputer -ngineering

etc. is controlled by enabling and disabling the +ard <eader, which is the customer8s entry3point to the system. <e/uests for statements and che/uebooks are posted to the +ontrol System. It also receives status reports for low printer3paper and cash levels. ACC47:!S 'A!A ASE This is a database containing account numbers, balances and other account information. $ata is retrieved from the database when a customer re/uests a balance report or a cash withdrawal. The database is updated after a withdrawal. CAR' REA'ER The +ard <eader receives the customer8s card and retrieves the 0I9 and account number stored on it. This information is transmitted to the software system which enables the +ustomer Aeypad and initiates the 0I9 verification procedure. When business is completed the +ard <eader is instructed to return the card. If the customer enters an incorrect 0I9, a fi'ed number of retries is permitted, after which the +ard <eader is instructed to confiscate the card. C7S!4MER KECPA' The +ustomer Aeypad allows a customer to enter a 0I9 number, select options and enter cash values. The keypad is only enabled when a card is detected in the +ard <eader. C7S!4MER '2SP3AC The +ustomer $isplay presents messages, options and reports to the customer. The display is active at all times. PR2:!47! '2SPE:SER This provides the customer with a printed balance or receipt. The 0rintout $ispenser reports to the system if the paper level is low. CAS5 '2SPE:SER

123+-345 123+-346

6;

+omputer -ngineering

This assembles and delivers cash to the customer. The dispenser receives information about the values and /uantities of notes to dispense ,4 ' P51, 5 ' P@, etc.. The +ash $ispenser reports to the system if the cash levels are low.

Data +!o, D-a)ra./0"%"!-12:-

123+-345 123+-346

6C

+omputer -ngineering

This diagram shows data entering and leaving the system. Input data is received from the hardware elements on the left. >arious types of data are processed by different parts of the software system. #utput data is sent to the elements of hardware on the right. 'F' 3evel - Processes#, 2nteract 9ith 4(erator 123+-345 123+-346

62

+omputer -ngineering

This process deals with commands from the system operator. These are the commands which enable or disable the customer interface by controlling the +ard <eader. The operator may issue these commands from another computer system or by using a switch on a control panel. 2nteract 9ith C&stomer This process handles all interactions with the customer and operates only when a card is detected in the +ard <eader. Input is received initially from the +ard <eader and then directly from the customer via the +ustomer Aeypad. The customer receives output from the +ustomer $isplay, the 0rintout $ispenser and the +ash $ispenser. +ustomer interactions may also involve sending reports to the +ontrol System. The initial step of all customer interactions is to verify the customer8s 0I9 number. 7fter this a menu of options is presented on the display which the customer selects by pressing appropriate keys on the keypad. These options lead to other displays and re/uests for further input. Some options re/uire account details which are retrieved from the 7ccounts $atabase and may also involve updating the database. $uring the final stage of all customer interactions the +ard <eader is instructed to either return or confiscate the card. Pre(are Command This process handles communication with the +ard <eader hardware. The system re/uires that the +ard <eader is able to receive the following commandsE -97"($IS7"(<-TD<9 <-T7I9 !akes the +ard <eader ready to receive a card 0revents the +ard <eader from accepting a card -jects a card from the +ard <eader +onfiscates an unauthori%ed card

The +ard <eader is enabled and disabled by commands from the system operator. 7 card is returned or retained in response to interactions with the customer. 7(date 'is(la$ This process deals with the +ustomer $isplay screen. When no card is in the +ard <eader, the +ustomer $isplay shows general information ,such as 8Insert +ard8.. When a card is detected the display is updated in response to customer interactions. If the system is disabled by the system operator, the display is updated to indicate the system status. The following is a list of screens which are shown on the +ustomer $isplay. Leneral Information 0I9 >erification !ain #ptions 3Insert +ard and other messages 3 -nter 0I9 message 3 Some or all of the following) $isplay "alance,

123+-345 123+-346

6:

+omputer -ngineering

+urrent "alance "alance 0rinted Withdrawal #ptions +ash 7mount +ash $ispensed <eceipt 0rinted Statement #rdered +he/uebook #rdered +ard <eturned +ard <etained

0rint "alance, +ash With <eceipt, +ash Without eceipt, #rder Statement, #rder +he/uebook, <eturn +ard 3+ustomer8s account balance and cleared funds 3Take =our "alance message 30re3defined cash amounts and #ther 7mount 3-nter 7mount for cash withdrawal 3Take =our +ash message 3Take =our <eceipt message 3Statement #rdered message 3 +he/uebook #rdered message 3Take =our +ard message 3+ard <etained message ,for failed 0I9 >erification.

Pre(are Message This process prepares and transmits messages to the +ontrol System. These messages can be re/uests from customers for statements and che/uebooks or reports concerning the levels of printer3paper and cash. Pre(are Printo&t This process prepares and controls the use of the 0rintout $ispenser to produce balance reports and receipts. The customer8s balance is retrieved from the 7ccounts $atabase ,if re/uired.. If the printer3paper level becomes low options which involve printouts are disabled and a warning message is sent to the +ontrol System. Manage 9ithdrawal This process receives re/uests for withdrawals of specific amounts from a certain account and operates the +ash $ispenser. "efore proceeding, the customer8s details in the 7ccounts $atabase are checked. If the re/uest e'ceeds the customer8s balance ,or agreed overdraft. the withdrawal is denied. The system uses a denomination selection algorithm based on the notes available and the amount re/uired. The 7ccounts $atabase is updated after each withdrawal. If the cash level becomes low, options providing cash withdrawals are disabled and a warning message is sent to the +ontrol System.

8.+.. Process S(eci"ication and 'ecision !a1le

123+-345 123+-346

B1

+omputer -ngineering

-. Admin 3ogin If adminNloginQtrue Then give rights to access the application as well as admin functionalities -lse Show error message -nd if 0. 7ser login If userNloginQtrue Then give rights to access the application -lse Show error message -nd if .. Entr$ o" details o" res(ective "orms to save in data1ase If information entered Q valid Then save -lse Show error message -nd if 8. Entr$ o" details to &(date the records in data1ase If information updated Q valid Then do update in database -lse Show error message -nd if ;. %enerate re(orts If parameter for report Q valid Then view the records -lse Show error message -nd if

#.3.# Contro! +!o, D-a)ra.:123+-345 123+-346

B4

+omputer -ngineering

;.* !esting
123+-345 123+-346 B5 +omputer -ngineering

;.- !esting Plan#


7ny system, to be successful, must be thoroughly tested, and well managed test plan should be prepared before actual testing is being performed. O!odulesR have been developed and need to be tested in a manner that can reduce occurring of defects as low as possible. ollowing are the activities we planned to test the system. 4. This system is indeed an evolutionary system so every unit of the system is continuously under testing phase. 5. #ne test activity O"asis 0ath TestingR that will try to cover all paths in the system. This activity identifies all paths that provide different functionality of the system, and also other paths to reach at that functionality. 6. #ther testing activity is R+ontrol Structure TestingR, which will test each and every condition with positive and negative data combination. B. This testing activity will also perform O$ata loe TestingR in which it will be tested how the data re following the system. 7nd will also check whether the data entered from one procedure, is reflected whenever it re/uires or not.

@. 7ll conditions will be tested with O"oundary >alue 7nalysisR where different input will be given to test whether the system is functioning with boundary values or not.

;. 7long with the boundary value analysis, the system is also tested with O<ange >alue TestedR where editable values will be tested with ranges of values.

C. The system is being tested in ODnit TestingR manner where at the completion of one unit that is tested thoroughly with above mentioned testing activities.

2. The integration testing will also be performed to ensure that the integrated unit is working properly with other units or not.

123+-345 123+-346

B6

+omputer -ngineering

;.0 !esting Strateg$#


C4:!E:! !ES!2:%# -rrors in 0roject content can be as trivial as minor typographical error as incorrect information, improper organi%ation or validation of intellectual property laws. +ontent Testing attempt to uncover this and many other problems before the user encounter them. Content !esting 41jectives# There are three types of objectives. 4. To uncover syntactic errors in te't3based documents, graphical representation and other media. 5. To uncover semantic errors in any content object represented as navigation error. 6. To find errors in organi%ation or structure of content that is presented to the end3user 2:!ERFACE !ES!2:% Interface design model is reviewed to ensure that generic /uality criteria established for all user interfaces have been achieved and that application specific interface design issue has been properly addressed. 2nter"ace testing strateg$# The overall strategy for interface testing is to ,4. Dncover error related to specific Interface mechanisms ,5. uncover errors in the way the interface implements the semantics of navigation, Web7pp functionality, or content display. To accomplish this strategy, a number of objectives must be achievedE

Interface futures are tested to ensure that design rules, aesthetics and related visual content are available for the user without error.

Individual interface mechanisms are tested in a manner that is analogous to unit testing or e'ample) tests are designed to e'ercise all forms, client3side scripting, dynamic M!(.

!esting 2nter"ace Mechanisms#,

123+-345 123+-346

BB

+omputer -ngineering

When a user interacts with a system, the interaction occurs through one or interface mechanisms. Forms# , 7t a microscopic level, tests are performed to ensure that

more

4. (abels correctly identified fields within the form and that mandatory fields are identified visually for the user. 5. The server receives all information content within the form and their no data are lost in the transmission between client and server. 6. 7ppropriate defaults are used when the user does not select from a pull down menu or set of buttons. B. "rowsing functions dont corrupt data entered in the form. @. Scripts that perform error checking on data entered work. ;. 0roperly and provide meaningful error message. Client side scri(ting#, "lack bo' tests are conducted to uncover any error in processing as The script is e'ecuted. These tests are coupled with forms testing because script input is often derived from data provided as part of forms processing '$namic EM3#, *ere the data transfer between the systems occurs in the form of 'ml file. The formatting of the M!( file should remain unaltered. +hanges in the internal attribute structure can also lead to an error. *ence for this M!( parsing functionalities are provided on the client side. A((lication s(eci"ic inter"ace mechanismsE3 Test conforms to a checklist of functionality and features that are defined by the interface mechanism.

"oundary test minimum and ma'imum number of item that can be placed in to shopping chart. Test to determine persistence of image capture contents.

123+-345 123+-346

B@

+omputer -ngineering

Test to determine whether the system can be record co3ordinate content at some future date.

7SA 32!C !ES!2:%#, Dsability test may be designed by 0roject engineering team. 4. $efine a set of usability testing categories and identify goal for each. 5. $esign test that will enable each goal to be evaluated. 6. Select participants who will conduct test. B. Instrument participants interaction with system while testing is conducted. @. $evelop a mechanism for assessing the usability of the system.

The following test categories and objective illustrate establish testingE 2nteractivit$, 7re interaction mechanism easy to understand and useK 3a$o&t, 7re navigation mechanism, content and function place in a manner that allows the user to find them /uicklyK Reada1ilit$3 Is the te't well written and clearK Aesthetics, $o layout color, typeface, and related characteristics lead to ease of useK 'is(la$ Characteristics3 $oes the system make optimal use of screen si%e and resolutionK !ime Sensitivit$, +an important features, functions and content be used in a timely mannerK Accessi1ilit$, Is the system accessible to people who have $isabilitiesK

C4MPA!2 232!C !ES!2:%#, 123+-345 123+-346

B;

+omputer -ngineering

0roject must operate within environment that differs from one another. $ifferent computer, display device, #S, browser and network connection speed can have significant on system operation.The 0roject team derives a series of compatibility, validation tests, derived from e'isting interface tests, navigation tests, performance tests and security tests. ;.. !esting Methods# 7naly%e and check system representation such as the re/uirement document, design diagrams and the program source code. They may be applied at all stages of the process.

Unit Testing

Module Testing

Sub-system Testing System Testing

Acceptance Testing

There are different !odels of testing. #n the basis of testing methods there are two types of testingE 123+-345 123+-346

BC

+omputer -ngineering

-. 9hite,1o@ testing. 0. lack,1o@ testing

4.. 952!E, 4E !ES!2:%


White3bo' testing sometimes called glass,1o@ testing, is a test case design method that users the control structure of the procedural design to drive the test case. (ogical errors and incorrect assumption are inversely proportional to the probability that a program will be e'ecuted. -rrors tend to creep into our work we design and implement function, condition or control that is out of the mainstream tends to be well understood. We often believe that a logical path is not likely to be e'ecuted when in fact it may be e'ecuted on a regular basis. The logical flow of a program times counter intuitive.

0/. 3ACK, 4E !ES!2:%E or our project periodically we have tested our software using black3bo' testing. Thinking as a client we have evaluated the software for its easy going and convenience.

7nit !esting#

$uring the programming stages each and every form, modules and class treated unit has been put into the test data. -very module is tested independently. The steps are followsE 4. !anually code is tested like spelling checks, logic and errors. 5. #nce the manual checking is over the complication has been done. Syntactical errors if any have to be corrected. 6. 7fter the clean complication the program, some dummy data, as specification, has been used for testing of the module to see if it works as specified. 2ntegration !esting

123+-345 123+-346

B2

+omputer -ngineering

7fter our individuals modules were tested out we go the integrated to create a complete system. This integration process involves building the system and testing the resultant system for problems that arise from component interaction. Per"ormance !esting 0erformance testing is designed to test the runtime performance of the system within the conte't of the system. These tests were performed as module level as well as system level. Individual modules were tested for re/uired performance. Condition !esting 0erformance testing is a test case design method that e'ercises the logical conditions. 2nter"ace !esting Interface sting is integral part of integration. We e'amined the code to be tested and e'plicitly list each call to an e'ternal component. In the system standards tests for LDIs have been performed, which are as followsE The position and related labels for all controls were checked. >alidations for all inputs were done. 0ull down controls was verified for proper functionality.

Whether the non3editable te't controls disabling and it was also verified that it doesnt e'ceed the ma'imum allowed length.

;.8 !est Cases# )-/2nvalid Parameter Setting. Test +aseE3 If the cameras are calibrated in a wrong manner, then the values derived from the images would be incorrect.

Solution 123+-345 123+-346

B:

+omputer -ngineering

Solution of this case is that we have to check the values from the .+S> file and see to that they are within the permissible range or not. )0/3ight so&rce moves o&t o" the camera (lane. Test +aseE3 If the any user by mistake moves the light source out of the camera plane, the captured image would then not contain any co3ordinate information. Solution Solution of this case is that there is a condition kept when no co3ordinates are e'tracted pass on the value of the origin.

)./2" an$ o" the cameras are not connected. Test +aseE3 If the cameras are disconnected from the computer the initiali%ation of the process will not occur. SolutionE3 Solution of this case is that user has to be aware of all the hardware has been correctly connected to the system before initiali%ation. Dser has to keep a checklist of all the system before initiali%ing the system.

)8/2" a (ro(er 1ase is not ta&ght. Test +aseE3 If the user teaches an invalid base then there remain chances of the robot to collide with the surrounding. Solution Solution of this case is that user is not aware about the base, and then the user should e'ecute the robot motion in T4 testing mode.

);/Comm&nication error 1etween controller and com(&ter. 123+-345 123+-346 @1 +omputer -ngineering

Test +aseE3 If user is unable to connect the computer to the controller, then user would not be able to pass on the co3ordinate values. Solution Solution of this case is that user has to first establish the connectivity by configuring the 7pi+onfig file, and check the connecting -thernet cable. Successful connection can be known by using the 0I9L command.

6.* 3imitation and F&t&re Enhancement


123+-345 123+-346

@4

+omputer -ngineering

3imitation#
7lthough I have tried to add all the related features to this online "us <eservation System but there are also some limitation. This system is stand alone system so data saved during different processes are stored in the machine in which that process was e'ecuted. So there is the problem of distributed database.

F&t&re Enhancement#
7s discussed the limitation of this system, we can implement this as clientGserver system. So all the data will be stored in the single machine, and for any purpose all the data will be retrieved from this central database. So there will be no human work re/uire for the employee. There will be only one person re/uired who will maintain this central database.

Concl&sion

123+-345 123+-346

@5

+omputer -ngineering

"ack in 4:;:, +hemical "ank announced that a new form of banking was being launched. With that, customers were provided with plastic cards designed with a magnetic strip that could be used with a machine built into a wall. Lone were the days of having to stand in line for a teller or not having money on hand after normal banking hours. 7lmost everyone has heard of and used an 7T! machine. Interestingly, some of people feel that 7T! machines are the best thing to happen in the banking world while other people consider them a curse. The main complaint heard about 7T! machines is that while they are convenient, they are e'pensive to use. *owever, if we look at it from a banking perspective, business is business. <egardless of what we think of 7T! machines, there is no doubt that they have changed the world and the way in which we do things. or e'ample, think how many times we have been out somewhere only to discover we have no cash and we are out of checks, ah, but in the corner, there is an 7T! machine. In the blink of an eye, we swipe the card and now have cash on hand. In addition to pulling money out, the 7T! machine also makes it convenient to deposit money, transfer money, and check balances. "est of all, to use an 7T! machine, we do not have to go to the bank. We will find 7T! machines at other banks, grocery stores, shopping malls, along the roadside, "uckingham 0alace, airports, in casinos, and even on the South <im of the Lrand +anyon. or this reason, 7T! machines are e'tremely helpfulH

i1liogra(h$
123+-345 123+-346

@6

+omputer -ngineering

ook Re"erence

undamentals of Software -ngineering $ Raji1 Mall Software -ngineering $ 2an Somerville 7nalysis and $esign of Information Systems $ James Senn

9e1site Re"erence
www.google.com www.ask.com www.microsoft.com www.iit.edu.com

123+-345 123+-346

@B

+omputer -ngineering