A Project Report On

SNAKE AND LADDER

Submitted in Partial Fulfillment of the Requirement for the Degree of Bachelor of Computer Applications

M.J.P. Rohilkhand University, Bareilly Project Guide Mrs. Kazal Singh Mohd. Shakeel Submitted By Swati 10108432
Invertis Institute of Management Studies Bareilly Lucknow Highway, NH-24, Bareilly

ACKNOWLEDGEMENT

ACKNOWLEGDEMENT

I owe a great many thanks to a great many people who helped and supported me during the completion of this seminar report. I express my thanks to the DIRECTOR, Prof Arpan K khastagir of INVERTIS INSTITUTE OF MANAGEMENT AND STUDIES, Bareilly and DEAN ACADEMICS Dr. Mili Sehgal and HEAD OF DEPARTMENT Mr. Ashok Kumar for extending their support. My deepest thanks to Lecturer Mrs Kazal Singh and Mohammad Shakeel the, Guide of the project for guiding and correcting various documents of mine with attention and care. They have taken pain to go through the project and make necessary correction as and when needed. I would also thank my Institution and my faculty members without whom this report would have been a distant reality. I also extend my heartfelt thanks to my family and well-wishers.

Swati 10108432

Index
1.

Introduction of project.........................5 Problem definition .............................8 System Analysis & Feasibility Study..10

2. 3.

4. Scope....................................................16
5.

System Requirements...........................18
a. b.

Hardware Requirements...............19 Software Requirements.................19

i.

Front End...............................19

6. System Logical Design..........................21 7. System Physical Design........................26

8. 9.

Input / Output Screen............................42 Testing ..................................................44 Limitation......................................51 Bibliography..................................53

10. 11.

INTRODUCTION OF PROJECT

Snakes and Ladders is an ancient Indian board game regarded today as a worldwide classic. It is played between two or more players on a game board having numbered, gridded squares. A number of "ladders" and "snakes" are pictured on the board, each connecting two specific board squares. The object of the game is to navigate one's game piece from the start (bottom square) to the finish (top square), helped or hindered by ladders and snakes, respectively. The historic version had root in morality lessons, where a player's progression up the board represented a life journey complicated by virtues (ladders) and vices (snakes). The simplicity and seesawing nature of the contest make the game popular with younger children, but the lack of any skill component makes the game less appealing for older players.

HISTORY :Snakes and Ladders originated in India as part of a family of dice board games, including pachisi (modern day Ludo). It was known as moksha pAtam or vaikunthapaali or paramapadasopaanam (the ladder to salvation). The game made its way to England and was sold as Snakes and Ladders, then the basic concept was introduced in the United States as Chutes and Ladders (an "improved new version of England's famous indoor sport") by game pioneer Milton Bradley in 1943. The game as popularly played in ancient India was known as Moksha Patam, and emphasized the role of fate or karma. A Jain version, Gyanbazi, dates to the 16th century. The game was called Leela and reflected the Hinduism consciousness surrounding everyday life. Impressed by the underlying ideals of the game, a newer version was introduced in Victorian England in 1892.

Moksha Patam was associated with traditional Hindu philosophy contrasting karma and kama, or destiny and desire. It emphasized destiny, as opposed to games such as pachisi, which focused on life as a mixture of skill (free will) and luck. The game has also been interpreted and used as a tool for teaching the effects of good deeds versus bad. The ladders represented virtues such as generosity, faith, and humility, while the snakes represented vices such as lust, anger, murder, and theft. The morality lesson of the game was that a person can attain salvation (Moksha) through doing good, whereas by doing evil one will inherit rebirth to lower forms of life. The number of ladders was less than the number of snakes as a reminder that a path of good is much more difficult to tread than a path of sins. Presumably the number "100" represented Moksha (salvation). In Andhra Pradesh, snakes and ladders is played in the name of Vaikuntapali. In the original game the squares of virtue are: Faith (12), Reliability (51), Generosity (57), Knowledge (76), and Asceticism (78). The squares of vice or evil are: Disobedience (41), Vanity (44), Vulgarity (49), Theft (52), Lying (58), Drunkenness (62), Debt (69), Rage (84), Greed (92), Pride (95), Murder (73), and Lust (99).

PROBLEM DEFINITION

As per my mini projet, I have implemented Snakes and ladders, which is a classic children's board game. It will be played between 2 to 4players on a playing board with numbered grid squares from 1 to 25. On certain squares a number of "ladders" are drawn connecting two squares together, and a number of "snakes" also connecting squares together.The player reaching 25th position first will win the game.

SYSTEM ANALYSIS & FEASIBILITY STUDY

10

SYSTEM ANALYSIS

1.1 INTRODUCTION Systems are created to solve problems. One can think of the systems approach as an organized way of dealing with a problem. In this dynamic world, the subject System Analysis and Design (SAD) , mainly deals with the software development activities. 1.2 OBJECTIVES After going through this lesson, you should be able to 1- Define a system 2- Explain the different phases of system development life cycle 3- Enumerate the components of system analysis 4- Explain the components of system designing 1.3 DEFINING A SYSTEM A collection of components that work together to realize some objectives forms a system. Basically there are three major components in every system, namely .In a system the different components are connected with each other and they are interdependent. For example, human body represent a complete natural system. We are also bound by many national systems such as
11

political system, economic system, educational system and so forth. The objective of the system demands that some output is produced as a result of processing the suitable inputs. A well-designed system also includes an additional element referred to as control that provides a feedback to achieve desired obj . 1.4 SYSTEM LIFE CYCLE System life cycle is an organizational process of developing and maintaining systems. It helps in establishing a system project plan, because it gives overall list of processes and sub-processes required for developing a system. System development life cycle means combination of various activities. In other words we can say that various activities put together are referred as system development life cycle. In the System Analysis and Design terminology, the system development life cycle also means software development life cycle. Following are the different phases of system development life cycle: 1- Preliminary study 2- Feasibility study 3- Detailed system study 4- System analysis 5- System design 6- Coding 7- Testing 8- Implementation 9- Maintenance objectives of the system, input, processing and output. The different phases of system development life cycle is shown in Fig. 1.2 below.
12

FEASIBILITY STUDY
Feasibility study is a test of a system proposal according to its workability, impact on the organization, ability to meet user needs, and effective use of resources. The feasibility study is to serve as a decision document; it must answer the following questions. 1) What are the user's demonstrable needs? 2) Is the problem worth solving? 3) How can the problem be solved? All the successful projects are not necessarily the biggest but rather those that truly meet the user expectations. Three key considerations involved in the feasibility analysis are economic, operational and technical. Economic Feasibility: Economic feasibility is the most frequently used method for evaluating the effectiveness of a candidate system. The procedure is to determine the savings and the benefits from the candidate system and compare with costs. If the benefits outweigh the costs then it is decided to go ahead with the projects. Otherwise, further justification or alterations in the proposed system will have to be made if it is to have a chance of being approved. This is an on-going effort that improves in accuracy at each phase of the system life cycle.
13

Operational Feasibility: People are resistant to change and computers have been known to facilitate change. An estimate should be made of how strong a reaction of the user staff is likely to have an impact towards the development of a computer system. It is common knowledge that computer installations have a lot to do with turnovers, transfers, retaining and changes to employee job status. Therefore it's understandable that the production of the candidate system requires special effort to educate and train the staff on the new way of doing the job. But since ultimately the introduction of a new system will only reduce the staff's workload, they may have no objection to install a computerized system, and of course will be eager to extend their cooperation. Behavioral Feasibility: It relates human behavior in the organization and political aspects. Here we focus on: 1) What changes will be brought with the system 2) What organizational structures are disturbed 3) What new skills will be required Do the existing members have these skills? If not can they be trained in due course of time. It also includes social and managerial aspects that is whether the proposed project will be acceptable to the customer and the management, along with the determination of whether the proposed project considers Act, Status as well as pending Legislations as a part of the legal feasibility Technical Feasibility: Technical feasibility centers on the existing system and to what extent it can support the proposed system. This involves financial considerations to accommodate technical enhancements. If the budget is a serious constraint, then the project is judged not feasible. Now considering the proposed system, our client has been maintaining the records manually at the present. So he has to purchase new computer systems for the automation of the concern. The owner having
14

realized the advantages, benefits and economic feasibility of the new system is ready to afford the expenses for the satisfaction of all the hardware and software requirements. Therefore the project, in question, is technically feasible as well.

15

SCOPE

16

This VISUAL BASIC PROJECT on SNAKE AND LADDER GAME is a high quality graphics and with sound effects.We have used procedure oriented method to design this game. Two to four players can play this game and the player who cross 25th first is the winner.

17

SYSTEM REQUIREMENTS

18

A. HARDWARE SPECIFICATIONS
Processor : Pentium III 400MHz and Above RAM : 128 MB Hard disk : 20 GB FDD : 1.44MB Monitor : 15 inch Mouse : 3 Button scroll3 CD Drive : 52 X Keyboard : 108 keys

B. SOFTWARE REQUIREMENTS
Operating System. : Windows 2000/XP Developing Tool : Visual Basic 6.0 Database : MS Access Front End :Microsoft Visual Basic

FRONT END:
Visual Basic 6.0 VISUAL BASIC is a high level programming language which evolved from the earlier DOS version called BASIC.
19

BASIC means Symbolic Instruction Symbolic Instruction Code . It is a very easy programming language to learn. The code look a lot like English Language. Different software companies produced different versions of BASIC, such as Microsoft QBASIC, QUICKBASIC, GWBASIC ,IBM BASICA and so on. However, people prefer to use Microsoft Visual Basic today, as it is a well developed programming language and supporting resources are available everywhere. Now, there are many versions of VB exist in the market, the most popular one and still widely used by many VB programmers is none other than Visual Basic 6. We also have VB.net, VB2005, VB2008 and the latest VB2010. Both Vb2008 and VB2010 are fully object oriented programming (OOP) language. VISUAL BASIC is a VISUAL and events driven Programming Language. These are the main divergence from the old BASIC. In BASIC, programming is done in a text-only environment and the program is executed sequentially. In VB, programming is done in a graphical environment. In the old BASIC, you have to write program code for each graphical object you wish to display it on screen, including its position and its color. However, In VB , you just need to drag and drop any graphical object anywhere on the form, and you can change its color any time using the properties windows. On the other hand, because the user may click on a certain object randomly, so each object has to be programmed independently to be able to response to those actions (events). Therefore, a VB Program is made up of many subprograms, each has its own program code, and each can be executed independently and at the same time each can be linked together in one way or another.

20

SYSTEM LOGICAL DESIGN

21

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. There is some overlap with the disciplines of systems analysis, systems architecture and systems engineering. If the broader topic of product development "blends the perspective of marketing, design, and manufacturing into a single approach to product development, then design is the act of taking the marketing information and creating the design of the product to be manufactured. Systems design is therefore the process of defining and developing systems to satisfy specified requirements of the user. Until the 1990s systems design had a crucial and respected role in the data processing industry. In the 1990s standardization of hardware and software resulted in the ability to build modular systems. The increasing importance of software running on generic platforms has enhanced the discipline of software engineering. Object-oriented analysis and design methods are becoming the most widely used methods for computer systems design .The UML has become the standard language in object-oriented analysis and design. It is widely used for modeling software systems and is increasingly used for high designing non-software systems and organizations.

DATA FLOW DIAGRAM

A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system, modelling its process aspects. Often they are a preliminary step used to create an overview of the system which can later be elaborated. DFDs can also be used for the visualization of data processing (structured design). A DFD shows what kinds of data will be input to and output from the system, where the data will come from and go to, and where the data will be stored. It does not show information about the timing of processes, or information about whether processes will operate in sequence or in parallel

22

Data flow diagram example.

Data flow diagram. It is common practice to draw the context-level data flow diagram first, which shows the interaction between the system and external agents which act as data sources and data sinks. On the context diagram the system's interactions with the outside world are modelled purely in terms of data flows across the system boundary. The context diagram shows the entire system as a single process, and gives no clues as to its internal organization. This context-level DFD is next "exploded", to produce a Level 0 DFD that shows some of the detail of the system being modeled. The Level 0 DFD shows how the system is divided into sub-systems (processes), each of which deals with one or more of the data flows to or from an external agent, and which together provide all of the functionality of the system as a whole. It also identifies internal data stores that must be present in order for the system to do its job, and shows the flow of data between the various parts of the system. Data flow diagrams were proposed by Larry Constantine, the original developer of structured design, based on Martin and Estrin's "data flow graph" model of computation. Data flow diagrams (DFDs) are one of the three essential perspectives of the structured-systems analysis and design method SSADM. The sponsor of a project
23

and the end users will need to be briefed and consulted throughout all stages of a system's evolution. With a data flow diagram, users are able to visualize how the system will operate, what the system will accomplish, and how the system will be implemented. The old system's dataflow diagrams can be drawn up and compared with the new system's data flow diagrams to draw comparisons to implement a more efficient system. Data flow diagrams can be used to provide the end user with a physical idea of where the data they input ultimately has an effect upon the structure of the whole system from order to dispatch to report. How any system is developed can be determined through a data flow diagram. In the course of developing a set of levelled data flow diagrams the analyst/designers is forced to address how the system may be decomposed into component sub-systems, and to identify the transaction data in the data model.

24

ER DIAGRAM
In software engineering, an entity-relationship model (ERM) is an abstract and conceptual representation of data. Entity-relationship modeling is a database modeling method, used to produce a type of conceptual schema or semantic data model of a system, often a relational database, and its requirements in a top-down fashion. Diagrams created by this process are called entity-relationship diagrams, ER diagrams, or ERDs..

25

SYSTEM PHYSICAL DESIGN

26

MAIN FORM

Dim Dice Private Sub cmdRoll_Click() If cmdRoll.Caption = "ROLL DICE" Then tmDice.Enabled = True Dim OurVoice Dim i i = Int(Rnd * 10) cmdRoll.Caption = "STOP DICE" Else tmDice.Enabled = False If Turn = 1 Then P1 = P1 + Dice If P1 >= 25 Then lblWin.Caption = Player_1 &" Wins" cmdRoll.Enabled = False Timer1.Enabled = True Player1.Top = lbl(25).Top + 360 Player1.Left = lbl(25).Left + 600
27

Else If P1 = 3 Then P1 = 13 If P1 = 6 Then P1 = 12 If P1 = 9 Then P1 = 16 If P1 = 11 Then P1 = 4 If P1 = 14 Then P1 = 22 If P1 = 18 Then P1 = 10 If P1 = 21 Then P1 = 8 If P1 = 24 Then P1 = 7 Player1.Top = lbl(P1).Top + 360 Player1.Left = lbl(P1).Left + 600 End If End If If Turn = 2 Then P2 = P2 + Dice If P2 >= 25 Then lblWin.Caption = player_2 &" Wins" cmdRoll.Enabled = False Timer1.Enabled = True Player2.Top = lbl(25).Top + 360 Player2.Left = lbl(25).Left + 600
28

Else If P2 = 3 Then P2 = 13 If P2 = 6 Then P2 = 12 If P2 = 9 Then P2 = 16 If P2 = 11 Then P2 = 4 If P2 = 14 Then P2 = 22 If P2 = 18 Then P2 = 10 If P2 = 21 Then P2 = 8 If P2 = 24 Then P2 = 7 Player2.Top = lbl(P2).Top + 360 Player2.Left = lbl(P2).Left + 1080 End If End If If Turn = 3 Then P3 = P3 + Dice If P3 >= 25 Then lblWin.Caption = Player_3 &" Wins" cmdRoll.Enabled = False Timer1.Enabled = True Player3.Top = lbl(25).Top + 360 Player3.Left = lbl(25).Left + 600
29

Else If P3 = 3 Then P3 = 13 If P3 = 6 Then P3 = 12 If P3 = 9 Then P3 = 16 If P3 = 11 Then P3 = 4 If P3 = 14 Then P3 = 22 If P3 = 18 Then P3 = 10 If P3 = 21 Then P3 = 8 If P3 = 24 Then P3 = 7 Player3.Top = lbl(P3).Top + 840 Player3.Left = lbl(P3).Left + 600 End If End If If Turn = 4 Then P4 = P4 + Dice If P4 >= 25 Then lblWin.Caption = Player_4 &" Wins" cmdRoll.Enabled = False Timer1.Enabled = True Player4.Top = lbl(25).Top + 360 Player4.Left = lbl(25).Left + 600
30

Else If P1 = 3 Then P1 = 13 If P4 = 6 Then P4 = 12 If P4 = 9 Then P4 = 16 If P4 = 11 Then P4 = 4 If P4 = 14 Then P4 = 22 If P4 = 18 Then P4 = 10 If P4 = 21 Then P4 = 8 If P4 = 24 Then P4 = 7 Player4.Top = lbl(P4).Top + 840 Player4.Left = lbl(P4).Left + 1080 End If End If Turn = Turn + 1 If Players = 2 Then If Turn = 3 Then Turn = 1 End If If Players = 3 Then If Turn = 4 Then Turn = 1 End If If Players = 4 Then
31

If Turn = 5 Then Turn = 1 End If cmdRoll.Caption = "ROLL DICE" End If End Sub Private Sub Command1_Click() frmOptions.Show 1 End Sub Private Sub Command2_Click() End End Sub Private Sub Command3_Click() Dim i cmdRoll.Enabled = True Timer1.Enabled = False lblWin.Caption = "" i = sndPlaySound(App.Path& "\welcome.wav", SND_ASYNC) Player1.Top = lbl(1).Top + 360 Player1.Left = lbl(1).Left + 600 Player2.Top = lbl(1).Top + 360 Player2.Left = lbl(1).Left + 1080
32

Player3.Top = lbl(1).Top + 840 Player3.Left = lbl(1).Left + 600 Player4.Top = lbl(1).Top + 840 Player4.Left = lbl(1).Left + 1080 P1 = 0 P2 = 0 P3 = 0 P4 = 0 Turn = 1 End Sub Private Sub Command5_Click() frmSplash.Show End Sub Private Sub Form_Load() Randomize Turn = 1 Players = 4 P1 = 0 P2 = 0 P3 = 0 P4 = 0
33

Player_1 = "Player 1" player_2 = "Player 2" Player_3 = "Player 3" Player_4 = "Player 4" End Sub

Private Sub lnlWin_Click() End Sub Private Sub Timer1_Timer() lblWin.ForeColor = Int(Rnd * 10000000) End Sub Private Sub tmDice_Timer() Dice = Dice + 1 If Dice = 7 Then Dice = 1 pcDice.Picture = LoadPicture(App.Path& "\Dice" & Dice & ".bmp") End Sub Private Sub tmWatch_Timer() lblP1.Caption = " " & Player_1 lblP2.Caption = " " & player_2 lblP3.Caption = " " & Player_3
34

lblP4.Caption = " " & Player_4 lblP1.ForeColor = Player1.BackColor lblP2.ForeColor = Player2.BackColor lblP3.ForeColor = Player3.BackColor lblP4.ForeColor = Player4.BackColor If Turn = 1 Then lblP1.BackColor = &H0& lblP2.BackColor = &H8000000F lblP3.BackColor = &H8000000F lblP4.BackColor = &H8000000F End If If Turn = 2 Then lblP1.BackColor = &H8000000F lblP2.BackColor = &H0& lblP3.BackColor = &H8000000F lblP4.BackColor = &H8000000F End If If Turn = 3 Then lblP1.BackColor = &H8000000F lblP2.BackColor = &H8000000F lblP3.BackColor = &H0&
35

lblP4.BackColor = &H8000000F End If If Turn = 4 Then lblP1.BackColor = &H8000000F lblP2.BackColor = &H8000000F lblP3.BackColor = &H8000000F lblP4.BackColor = &H0& End If End Sub OPTION FORM Private Sub cmdCancel_Click() Unload Me End Sub Private Sub cmdOK_Click() If Option1.Value = True Then Players = 2 frmMain.Player1.Visible = True frmMain.Player2.Visible = True frmMain.Player3.Visible = False frmMain.Player4.Visible = False End If
36

If Option2.Value = True Then Players = 3 frmMain.Player1.Visible = True frmMain.Player2.Visible = True frmMain.Player3.Visible = True frmMain.Player4.Visible = False End If If Option3.Value = True Then Players = 4 frmMain.Player1.Visible = True frmMain.Player2.Visible = True frmMain.Player3.Visible = True frmMain.Player4.Visible = True End If Player_1 = Text1 player_2 = Text2 Player_3 = Text3 Player_4 = Text4 Unload Me End Sub Private Sub Form_Load()
37

Text1 = Player_1 Text2 = player_2 Text3 = Player_3 Text4 = Player_4 If Players = 4 Then Option3.Value = True Label1.Enabled = True Label2.Enabled = True Label3.Enabled = True Label4.Enabled = True Text1.Enabled = True Text2.Enabled = True Text3.Enabled = True Text4.Enabled = True End If If Players = 3 Then Option2.Value = True Label1.Enabled = True Label2.Enabled = True Label3.Enabled = True Label4.Enabled = False
38

Text1.Enabled = True Text2.Enabled = True Text3.Enabled = True Text4.Enabled = False End If If Players = 2 Then Option1.Value = True Label1.Enabled = True Label2.Enabled = True Label3.Enabled = False Label4.Enabled = False Text1.Enabled = True Text2.Enabled = True Text3.Enabled = False Text4.Enabled = False End If End Sub Private Sub Option1_Click() Label1.Enabled = True Label2.Enabled = True Label3.Enabled = False
39

Label4.Enabled = False Text1.Enabled = True Text2.Enabled = True Text3.Enabled = False Text4.Enabled = False End Sub Private Sub Option2_Click() Label1.Enabled = True Label2.Enabled = True Label3.Enabled = True Label4.Enabled = False Text1.Enabled = True Text2.Enabled = True Text3.Enabled = True Text4.Enabled = False End Sub Private Sub Option3_Click() Label1.Enabled = True Label2.Enabled = True Label3.Enabled = True Label4.Enabled = True
40

Text1.Enabled = True Text2.Enabled = True Text3.Enabled = True Text4.Enabled = True End Sub

41

INPUT/OUTPUT SCREEN

42

43

TESTING IMPLEMENTATION

44

This document is intended to be used throughout the coding and testing phases of the project. It outlines the procedures used for testing and verification of the code. The document also describes the integration procedures and the order in which modules will be coded, and describes the test procedures and results of testing. This section deals with the details of the classes of tests which must be conducted to validate the functions, performance, and the constraints. This is achieved basically by the means of testing which plays a vital role in the development of the software. The various low level testing which can be grouped on a broader sense are discussed as below: There are three levels of testing: 1. Unit Testing -- Each module will be tested separately to ensure that it is working before being combined with other modules. 2. Integration Testing -- Related modules will be integrated and tested together before being placed into the system. 3. System Testing -- The entire system will be tested together after integration is complete. System testing includes function, acceptance, installation and regression testing. System testing will involve some beta testing by the client. Notes All testing has been carried out using some sample data.

45

Each section in the remainder of this document has lists of test criteria that must be satisfied for the system to have passed that section of testing. In front of the each criterial test Passed or Failed is written. Unit Testing The purpose of unit testing is to uncover errors in the smallest software unit the routine. Each routine will be tested individually using black box-oriented tests. The programmer of each module will design a set of test cases for that module and ensure that the module is fully tested. Important or complex routines will also be tested by at least one other person. Integration Testing This section describes the integration strategy and procedures for the system. It gives the order in which modules will be developed and how they will be integrated. It also describes the specific tests that will be performed on integrated sets of modules. Note: It is important that each module be thoroughly tested as a unit before being integrated with other modules. Integration testing of unit tested modules is necessary to ensure that: modules interface correctly with each other; one module does not have inadvertent, undesirable effects on another module; submodules (routines) combine to produce the desired functions of the major module;
46

 interfaces to, and use of global data structures are consistent. System Testing Functional Requirements Testing The functionality tests should be performed by the application representatives and treat the whole system as a black box using the actual applications or middleware. The aim of these tests is to verify the overall functionality of the system. This will be performed by a section by section walkthrough of the SRS functional requirements section. All functional requirements in the SRS must be fulfilled. Tested the Stock form correct updation Beta Testing Method This will be performed by the client, and by potential users of the system at the Bureau of Meteorology. Users will be given a copy of the system to try out. Any problems with the system will be reported back to the group. Beta Testing To help us achieve the best possible result with our project, we have decided to get as much input as possible from potential users of our system. Bugs. If unexpected events happen while using project,
47

Alterations. If there is anything missing from the system, that you would like to see there, we would also like to know about it. Most likely we will not be able to implement the changes to the current system (due to time restraints), but when the full system is written next year, it will most likely be present. All Comments... Can be sent to us in various ways. Please include your name and email address in any correspondence. Results Comments received from the customers: Alpha testing - prototype 2 of system Performance and Stress Testing A set of tests have been developed for performance and stress testing. Performance tests will ensure that the system responds in a reasonable time to user input (as defined in the SRS). The aim of stress testing is to try to break the program by giving it abnormal or extreme input quantity, frequency or volume. Performance testing will be performed at the client's site after installation. According to the SRS: The system must respond to all reports within 10 seconds on an Pentium IV computer with a load average less than 1. Performance criteria satisfied.
48

Stress testing with extreme and abnormal input cases has been been performed where necessary on individual routines in the Unit Testing section. Stress testing satisfied. Acceptance Testing Acceptance testing consists of a suite of tests to be performed in the presence of the client before he accepts the system. It will consist of the function tests, performance tests (at the client's site), a walk-through of the user manual and the final demonstration. Function tests accepted. Performance tests accepted. User manual walkthrough accepted. Will be held performed along with Installation Testing. Final demonstration accepted. Installation Testing Installation tests will check the installation and configuration procedure as well as any missing dependencies. Installation tests test the installation and configuration procedures. These tests are a set of scripts that automatically download all necessary packages and install them. Acceptance testing will be repeated after installation of the system at the Customer Place. This is to ensure that the system works correctly in the Customer Place.
49

Note: System has not been installed for the client yet. Will be installed this week. Some specific points that also need to be tested are: 1. Directory paths for data and help files are set up correctly and can be found by the system. 2. Check for necessary third party controls. 3. All IDL library functions can be found by the system. 4. All fonts for the text tool can be found and loaded -- beta testing uncovered some problems loading some fonts. 5. Check Printer drivers are installed properly. Regression Testing The selective retesting of a software system that has been modified to ensure that any bugs have been fixed and that no other previously working functions have failed as a result of the reparations and that newly added features have not created problems with previous versions of the software. Also referred to as verification testing, regression testing is initiated after a programmer has attempted to fix a recognized problem or has added source code to a program that may have inadvertently introduced errors. It is a quality control measure to ensure that the newly modified code still complies with its specified requirements and that unmodified code has not been affected by the maintenance activity. Regression testing was not usually necesary, because most of the errors detected were verylocalised, and did not affect other functions in an adverse manner.

50

LIMITATIONS

51

The limitation of this game is that it cannot be used online.

As it name implies ,the entire process of developing an application using a visual development environment is visual . Thus it is having less security feature. Visual basic has no feature to store password. Visual developing environment requires computer of a higher configuration in compare to other programming tool. 1-Larger capacity harddisk. 2-More RAM. 3-Faster processor. Programmes written in visual basic on window cannot run on operating system. We cannot create webbase project.

52

BIBLIOGRAPHY

53

Books
A Complete Guide to Programming in Visual Basic .Net A Complete Visual Basic 6 Training Course: How to Programme: Advanced Programming Using Visual Basic: Version 6.0 Access 2003 Power Programming with VBA Advanced MS Visual Basic

Package

Site Address

www.associatedcontent.com www.members.tripod.com www.vbcodesource.com

54