Batch A6

D. Khadga Chaitanya Kumar (691277017) B. Pravallika (691277005) B. DurgaRao (691277003) S.V.S. Gupta (691277018) V. VenkataRao (691277058)

Introduction
Frequent pattern: a pattern (a set of items, subsequences, substructures, etc.) that occurs frequently in a data set One of the most popular data mining approaches is to find frequent itemsets from a transaction Dataset A number of algorithms has been proposed to determine frequent pattern. Apriori algorithm is the first algorithm proposed in this field. With the time a number of changes proposed in Apriori to enhance the performance in term of time and number of database passes. Apriori is a algorithm for finding frequent itemsets using candidate generation In this three different frequent pattern mining approaches (Record filter, Intersection and Proposed Algorithm) are given based on classical Apriori algorithm.

 In these approaches ,

Improvement

Classical Apriori Algorithm

Record filter Algorithm

Intersection approach Algorithm Proposed Algorithm

Therefore, Proposed Algorithm is better than other Frequent Pattern Algorithms

 Frequent pattern are patterns that appear in a dataset frequently. For example, a set of items, such as milk and bread that appear frequently together in a transaction data set is a frequent item set. Frequent patterns are prevalent in real-life data, such as sets of items bought together in a superstore. Frequent pattern mining has been successfully applied to association rule mining, patternbased classification, clustering, finding correlated items, and has become an essential data mining task.

Existing System
The problem is usually decomposed into two sub problems. 1. One is to find those item sets whose occurrences exceed a predefined threshold in the database; those item sets are called frequent or large item sets. 2. The second problem is to generate association rules from those large item sets with the constraints of minimal confidence.

Proposed System
In this new approach, we are presenting an algorithm that uses the concept of both algorithm i.e.
Record filter approach and Intersection approach in Apriori algorithm to count the support of candidate item set.

In this new approach, we use the set theory concept of intersection with the record filter approach.

Proposed System
In proposed algorithm, to calculate the support, we count the common transaction that contains in each elements of candidate set, with the help of the intersect query of SQL. We have applied a constraints that we will consider only those transaction that contain at least k items, not less than k in process of support counting for candidate set of k length. This approach requires very less time as compared to all other approaches.

A Software Requirements Specification (SRS) :

A Software Requirements Specification (SRS) is a complete description of the behavior of the system to be developed. It includes a set of use cases that describe all the interactions the users will have with the software. Use cases are also known as functional requirements. In addition to use cases, the SRS also contains nonfunctional (or supplementary) requirements. Nonfunctional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints).

Functional Requirements For Present Project:

Authentication: Server and Client can enter username and password then only they authenticated. Then both initiate with their port numbers Then communicate with each other.
Non Functional Requirements:

Qualities, that is, non-functional requirements, can be divided into two main categories: 1. Execution qualities, such as security and usability, which are observable at run time. 2. Evolution qualities, such as testability, maintainability, extensibility and scalability, which are embodied in the static structure of the software system

System Requirements
Hardware Requirements For Present Project: VDU: Monitor/ LCD TFT / Projector Input Devices: Keyboard and Mouse RAM: 512 MB Storage: Less than 100 MB of HD space. Software Requirements For Present Project: Operating System: Windows XP or above Run-Time: .Net Framework 4.0 or above

System Design
Systems design is therefore the process of defining and developing a systems to satisfy specified requirements of the user. Systems design is the process or art of defining the architecture, components, modules, interfaces, and data for a system to satisfy specified requirements. Object-oriented analysis and design methods are becoming the most widely used methods for computer system design[citation needed]. The UML has become the standard language used in Objectoriented analysis and design[citation needed]. It is widely used for modeling software systems and is increasingly used for high designing non-software systems and organizations

Use Case Diagram:

A use case diagram in the Unified Modeling Language (UML) is a type of behavioral diagram defined by and created from a Usecase analysis. Its purpose is to present a graphical overview of the functionality provided by a system in terms of actors, their goals (represented as use cases), and any dependencies between those use cases. Use Case diagrams are formally included in two modeling languages defined by the OMG: The Unified Modeling Language (UML) The Systems Modeling Language (SysML)

Sequence Diagram:
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram that shows how processes operate with one another and in what order. It is a construct of a Message Sequence Chart. Sequence diagrams are sometimes called event diagrams, event scenarios, and timing diagrams. A sequence diagram shows, as parallel vertical lines (lifelines), different processes or objects that live simultaneously, and, as horizontal arrows, the messages exchanged between them, in the order in which they occur.

Testing:
Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. Software testing also provides an objective, independent view of the software to allow the business to appreciate and understand the risks at implementation of the software. Software testing can also be stated as the process of validating and verifying that a software program/application/product:
meets the business and technical requirements that guided its design and development; works as expected; and can be implemented with the same characteristics.

Testing Methods :
The box approach White box testing Types of white box testing
API testing (application programming interface) Code coverage Fault injection methods Mutation testing methods Static testing

Test coverage Black box testing Grey box testing

Testing levels:
Unit testing Integration testing System testing System integration testing Regression testing Acceptance testing Alpha testing Beta testing Non-functional testing Software performance testing and load testing Stability testing Usability testing Security testing Internationalization and localization Destructive testing

Test Cases:
Test No. 1. 2. Test Case Invalid entries Valid input Expected Output Actual Output Message showing error invalid Navigation to Navigation to next page next page A dialog to be displayed saying invalid login,Acess Denied. A dialog box is displayed saying invalid login, Access denied. Result Passed Passed

3.

Invalid Login Test By providing invalid user name and password

passed

4.

Valid Login Test: The text screen The text screen passed By providing valid for accepting the for accepting the user name and text to be shown. text to be shown password