PART – A Software Testing LABORATORY WORK
1. Design, develop, code and run the program in any suitable language to solve the commission problem. Analyze it from the perspective of dataflow testing, derive at least 10 different test cases, execute these test cases and discuss the test results.
2. Design, develop, code and run the program in any suitable language to solve the NextDate problem. Analyze it from the perspective of decision table-based testing, derive at least 10 different test cases, execute these test cases and discuss the test results.
3. Design, develop, code and run the program in any suitable object-oriented language to solve the calendar problem. Analyze it from the perspective of OO testing, derive test cases to test the method that increment the date and the method that increments the month., execute these test cases and discuss the test results.
4. Design, develop, code and run the program in any suitable object-oriented language to solve the currency converter problem. Analyze it from the perspective of use case-based system testing, derive appropriate system test cases, execute these test cases and discuss the test results.
5. Design, develop, code and run the program in any suitable language to implement an absolute letter grading procedure, making suitable assumptions. Determine the basis paths and using them derive different test cases, execute these test cases and discuss the test results.
6. Design, develop, code and run the program in any suitable language to implement the binary search algorithm. Determine the basis paths and using them derive different test cases, execute these test cases and discuss the test results
PART – B ADBMS LABORATORY WORK
Note:
The following experiments may be implemented on MySQL/ORACLE or any other suitable RDBMS with support for Object features
1. Develop a database application to demonstrate storing and retrieving of BLOB and CLOB objects.
a. Write a binary large object (BLOB) to a database as either binary or character (CLOB) data, depending on the type of the field in your data source. To write a BLOB value to the database, issue the appropriate INSERT or UPDATE statement and pass the BLOB value as an input parameter. If your BLOB is stored as text, such as a SQL Server text field, pass the BLOB as a string parameter. If the BLOB is stored in binary format, such as a SQL Server image field, pass an array of type byte as a binary parameter.
b. Once storing of BLOB and CLOB objects is done, retrieve them and display the results accordingly.
2. Develop a database application to demonstrate the representation of multi valued attributes, and the use of nested tables to represent complex objects. Write suitable queries to demonstrate their use.
Consider Purchase Order Example: This example is based on a typical business activity: managing customer orders. Need to demonstrate how the application might evolve from relational to object-relational, and how you could write it from scratch using a pure object-oriented approach.
a. Show how to implement the schema -- Implementing the Application under the Relational Model -- using only Oracle's built-in data types. Build an object-oriented application on top of this relational schema using object views
3. Design and develop a suitable Student Database application by considering appropriate attributes. Couple of attributes to be maintained is the Attendance of a student in each subject for which he/she has enrolled and Internal Assessment Using TRIGGERS, write active rules to do the following:
a. Whenever the attendance is updated, check if the attendance is less than 85%; if so, notify the Head of the Department concerned.
b. Whenever, the marks in an Internal Assessment Test are entered, check if the marks are less than 40%; if so, notify the Head of the Department concerned.
Use the following guidelines when designing triggers:
• Use triggers to guarantee that when a specific operation is performed, related actions are performed.
• Use database triggers only for centralized, global operations that should be fired for the triggering statement, regardless of which user or database application issues the statement.
• Do not define triggers that duplicate the functionality already built into Oracle. For example, do not define triggers to enforce data integrity rules that can be easily enforced using declarative integrity constraints.
• Limit the size of triggers (60 lines or fewer is a good guideline). If the logic for your trigger requires much more than 60 lines of PL/SQL code, it is better to include most of the code in a stored procedure, and call the procedure from the trigger.
• Be careful not to create recursive triggers. For example, creating an AFTER UPDATE statement trigger on the EMP table that itself issues an UPDATE statement on EMP causes the trigger to fire recursively until it has run out of memory.
1. Design, develop, and execute a program to implement specific Apriori algorithm for mining association rules. Run the program against any large database available in the public domain and discuss the results.
Association rules are if/then statements that help uncover relationships between seemingly unrelated data in a relational database or other information repository. An example of an association rule would be "If a customer buys a dozen eggs, he is 80% likely to also purchase milk.”
Course Outcomes
The students should be able to:
• Assess Software Testing and ADBMS at the practical level
• Compare and pick out the right type of software testing process for any given real world problem
• Experiment software testing process in efficient way
• Determine a quality environment as specified in standards for developing quality software
• Examine real world data using object oriented database
• Choose, design and implement recent applications database for better interoperability