JNTUH B.Tech 4th year (4-1) Case Tools and Software Testing Lab gives you detail information of Case Tools and Software Testing Lab R13 syllabus It will be help full to understand you complete curriculum of the year.
Objectives
- Understand how UML supports the entire OQAD process.
- Become familiar with all phases of OQAD.
- Understand different software testing techniques and strategies.
- Understand the procedure to write test plan and execution.
- Understand different software testing tools and their features
CASE TOOLS LAB
Students are divided into batches of 5 each and each batch has to draw the following diagrams using UML for an ATM system whose description is given below. UML diagrams to be developed are:
- Use Case Diagram.
- Class Diagram.
- Sequence Diagram.
- Collaboration Diagram.
- State Diagram
- Activity Diagram.
- Component Diagram
- Deployment Diagram.
- Test Design.
- Description for an ATM System
The software to be designed will control a simulated automated teller machine (ATM) having a magnetic stripe reader for reading an ATM card, a customer console (keyboard and display) for interaction with the customer, a slot for depositing envelopes, a dispenser for cash (in multiples of Rs. 100, Rs. 500 and Rs. 1000), a printer for printing customer receipts, and a key-operated switch to allow an operator to start or stop the machine. The ATM will communicate with the bank’s computer over an appropriate communication link. (The software on the latter is not part of the requirements for this problem.) The ATM will service one customer at a time. A customer will be required to insert an ATM card and enter a personal identification number (PIN) – both of which will be sent to the bank for validation as part of each transaction.
The customer will then be able to perform one or more transactions. The card will be retained in the machine until the customer indicates that he/she desires no further transactions, at which point it will be returned – except as noted below.
The ATM must be able to provide the following services to the customer
- A customer must be able to make a cash withdrawal from any suitable account linked to the card, in multiples of Rs. 100 or Rs. 500 or Rs. 1000. Approval must be obtained from the bank before cash is dispensed.
- A customer must be able to make a deposit to any account linked to the card, consisting of cash and/or checks in an envelope. The customer will enter the amount of the deposit into the ATM, subject to manual verification when the envelope is removed from the machine by an operator. Approval must be obtained from the bank before physically accepting the envelope.
- A customer must be able to make a transfer of money between any two accounts linked to the card.
- A customer must be able to make a balance inquiry of any account linked to the card.
- A customer must be able to abort a transaction in progress by pressing the Cancel key instead of responding to a request from the machine.
The ATM will communicate each transaction to the bank and obtain verification that it was allowed by the bank. Ordinarily, a transaction will be considered complete by the bank once it has been approved. In the case of a deposit, a second message will be sent to the bank indicating that the customer has deposited the envelope. (If the customer fails to deposit the envelope within the timeout period, or presses cancel instead, no second message will be sent to the bank and the deposit will not be credited to the customer.) If the bank determines that the customer’s PIN is invahd, the customer will be required to re-enter the PIN before a transaction can proceed. If the customer is unable to successfully enter the PIN after three tries, the card will be permanently retained by the machine, and the customer will have to contact the bank to get it back.
If a transaction fails for any reason other than an invalid PIN, the ATM will display an explanation of the problem, and will then ask the customer whether he/she wants to do another transaction.
The ATM will provide the customer with a printed receipt for each successful transaction
The ATM will have a key-operated switch that will allow an operator to start and stop the servicing of customers. After turning the switch to the non”
position, the operator will be required to verify and enter the total cash on hand. The machine can only be turned off when it is not servicing a customer. When the switch is moved to the hoff” position, the machine will shut down, so that the operator may remove deposit envelopes and reload the machine with cash, blank receipts, etc.
Outcomes
- Ability to understand the history, cost of using and building CASE tools.
- Ability to construct and evaluate hybrid CASE tools by integrating existing tools.
- Ability to deliver the product with qualitative.
SOFTWARE TESTING LAB
List of Experiments
- Write programs in ‘C’ Language to demonstrate the working of the following constructs:
i) do…while ii) while….do iii) if…else iv) switch v) for - “A program written in ‘C’ language for Matrix Multiplication fails” Introspect the causes for its failure and write down the possible reasons for its failure.
- Take any system (e.g. ATM system) and study its system specifications and report the various bugs.
- Write the test cases for any known application (e.g. Banking application)
- Create a test plan document for any application (e.g. Library Management System)
Study of any testing tool (e.g. Win runner) - Study of any web testing tool (e.g. Selenium)
- Study of any bug tracking tool (e.g. Bugzilla, bugbit)
- Study of any test management tool (e.g. Test Director)
- Study of any open source-testing tool (e.g. Test Link)
- Take a mini project (e.g. University admission, Placement Portal) and execute it. During the Life cycle of the mini project create the various testing documents* and final test report document.
*Note: To create the various testing related documents refer to the text “Effective Software Testing Methodologies by William E. Perry”
For more information about all JNTU updates please stay connected to us on FB and don’t hesitate to ask any questions in the comment.