The Purpose of the design phase of this project¶s life cycle is to plan out a system that meets the requirements defined in the analysis phase. In the design phase, the project team defines the means of implementing the project solution-how the product will be created. To do this, the project team uses the inputs and tools to conduct the key activities, create the outputs, and meet the milestones for this phase. The purpose of the design phase is to provide the project team with a means for assessing the quality of the solution before it has been implemented, when changes are still easy to make and are less costly. This phase includes the following elements

2. Overall Description

2.1 Communication Interfaces:
A communication interface is provided for use in a distributed transactional processing environment which allows a program application to be directly written to a resource and provides a communication interface between plural transaction processing systems. The present invention also informs all participating transaction managers of the existence of a transaction and further informs the local transaction manager of all sites which are participating the transaction.


Communication Interface Diagram:

Fig: 2.1 Communication Interfaces Specific communication protocols are defined which allow any type of communication services to be utilized to provide the communication link. Additionally, the transactional and communication management functions are separated, allowing the communication manager to perform functions previously implemented by the transaction manager.

2.2 User Characteristics: 1. User/Client Tasks:
i. ii. iii. Login Loading data Item sets Specification of minimum support count.


the term database design could also be used to apply to the overall process of designing. iii. 3 . 4. not just the base data structures. 3. GUI is only in English. 2.4 Database Design: Database design is the process of producing a detailed data model of a database.user must specify the minimum support count value. In the relational model these are the tables and views. Frequent item sets display. which can then be used to create a database. ii. iv. This logical data model contains all the needed logical and physical design choices and physical storage parameters needed to generate a design in a Data Definition Language. The term database design can be used to describe many different parts of the design of an overall database system. and correctly. In an object database the entities and relationships map directly to object classes and named relationships. 2. 2. Administrative tasks: i. Login Authentication Verify whether Data set document is loaded or not. Pattern transformation to data base. Login and password is used for identification of seeker and there is limited facility for guest.3 Constraints 1.This system is working for single server. but also the forms and queries used as part of the overall database application within the database management system(DBMS). Principally.2. it can be thought of as the logical design of the base data structures used to store the data. A fully attributed data model contains detailed attributes for each entity. However.

Entity Relationship Diagrams (ERDs) illustrate the logical structure of databases. regardless of the underlying hardware and software. and its requirements in a top-down fashion. ER diagrams often use symbols to represent three different types of information. often a relational database. Diagrams created by this process are called entityrelationship diagrams. ER diagrams are very useful as the provide a good conceptual view of any database. Diamonds are normally used to represent relationships and ovals are used to represent attributes. used to produce a type of conceptual schema or semantic data model of a system.ER Diagrams: An entity-relationship model (ERM) is an abstract conceptual representation of data. 4 . Entity-relationship modeling is a database modeling method. An Entity-relationship (ER) diagram is a specialized graphic that illustrates the interrelationships between entities in a database. or ERDs. ER diagrams. Boxes are commonly used to represent entities. It is used frequently to describe the database schema. Entity relationship diagrams are a way to represent the structure and layout of a database.

4 ER Diagram 5 .Fig: 2.

2.5 Assumptions and dependencies: In this context. 3. Specific Requirements: 3. sparse etc. generalization and association relationships 6 . Contents y Use case commonly contain    Use cases Actors Dependency. necessary inspiration could be obtained by analyzing the sequential pattern mining algorithm such some popular algorithm like spade.1 Use case Reports: Use Case Diagram y A use case diagram is a diagram that shows a set of use cases and actors and relationships.

Fig: 3.1 Overall Use case Diagram 7 .

1. by verifying the username and password.Login: Fig: 3.1 Login Use case Description: Every user should login before using the system. Primary Actor : User Secondary Actor: Administrator. 8 . That is administrator will check whether he is authenticated user or not.

1. 4. 2. 3. Load: Fig: 3.2 Load Use case Description: A valid user can search the content by entering a document name. Administrator now checks the status of the file and if available document will be send to user. it gives response as ³Login successfully´. The administrator will check the details and if he is valid. Every person who wanted to use the system could be registered before the login. If the user is not authenticated user then it can give the response as ³Login Fail´. The login phase will verify the username and password entered by the user.Flow of Events: 1. 9 .

a sequence diagram is a table that shows objects arranged along x-axis and messages. The user enters the request for document loading. 3. sequence diagrams may contain notes and constraints. Contents y Sequence diagrams commonly contain the following:  Objects  Links  Messages Link all other diagrams. 3. consisting of a set of objects and their relationships. 10 . ordered in increasing time.2 Sequence and collaboration diagrams: y An interaction diagram shows an interaction. If document ³loading successful´ then administrator give conform message. Flow of Events: 1. 5. along the y-axis. otherwise administrator sends ³loading fail´ message. After entering the document. pre process the initial request. According to the request administrator give response to the user. including the messages that may be dispatched among them. y A sequence diagram is an interaction diagram that emphasizes the time ordering of messages. 2. 4. y Graphically.Primary Actor : User Secondary Actor : Administrator.

Overall Sequence Diagram: Fig: 3.2.1 Sequence diagram 11 .

User generates pattern on the basis of the Prefix and suffix based 9. 8. 5. 7.User load the datasets in to database.Messages: 1. 3. Administrator verifies the document if it is valid. Now the user enters the required document for loading. 2.User generates Max to Min pattern database. User Can login to the system after validating the user details by Administrator. 4. 10.User processing to the further step can process the final resultant frequent item sets. the Database 12 .Adminstrator can display the results. Then it gives the messages as ³Login successfully´.Adminstrator generates the results. 6.

.Login: Fig: 3.  The user can login to the system is the initial step.2 Sequence Diagram for Login Messages:. 13 .  Administrator will validate the user.  Data base Manager will check the details.2.  And he give response the Administrator.  Finally the Administrator will send message as ³Login Successful´ to indicate the valid login.

 Administrator give response to the input.2.  Then finally it gives loading complete message.3 Sequence Diagram for load Messages:  User can initiate the request initially.  Input is loaded in to the database. 14 .Load: Fig: 3.

such as a classifier or an operation.Collaboration Diagram: . 15 . interfaces.Collaboration is a society of classes. sequence diagrams may contain notes and constraints. and other elements that work together to provide some cooperative behavior that¶s bigger than the sum of all its parts. .Collaboration is also the specification of how an element. Contents Collaboration diagrams commonly contain the following:    Objects Links Messages Like all other diagrams. is realized by a set of classifiers and associations playing specific roles used in a specific way.

4 Collaboration Diagram 16 .User Collaboration: Fig: 3.2.

Login Collaboration: Fig: 3.5 Login Collaboration 17 .2.

6 Load Collaboration 18 .Load Collaboration: Fig: 3.2.

which is made up of executable atomic computations that result in a change in state of the system or the return of a value. An activity is an ongoing non-atomic execution within a state machine.3 Activity Diagram: y An activity diagram shows the flow from activity to activity.3. activity diagrams may contain notes and constraints. 19 . Activity diagram commonly contain Activity Diagram is essentially a flow chart showing flow of control from one activity to activity. y Activities ultimately result in some action.  Activity states and action states  Transitions  Objects Like all other diagrams. An activity is an ongoing non-atomic execution with in a state machine. Overall Activity Diagram: The following Overall Activity Diagram shows the flow from activity to activity.

Fig: 3.1 Overall Activity Diagram 20 .3.

2 Login Activity Diagram In the login phase the user enters id and password if they are valid id and password then login is successful so that they get provided Services effectively.Login: Fig: 3. If they are not valid then ends.3. 21 .

22 . then user sends loading valid.3. The Administrator will preprocess the request.Load: Fig: 3. Verifies the document if the document dataset is valid.3 Load Activity y y In loading. y Finally the administrator will send results to the user. the user enters document. Otherwise sends that loading is fail.

With detailed modeling the classes of the conceptual design are often split in a number of sub classes. which helps to determine the statical relations between those objects. and for detailed modeling translating the models into programming code.4 Class Diagram: The Class diagram is the main building block in object oriented modeling. and The bottom part gives the methods or operations the class can take or undertake In the conceptual design of a system a number of classes are identified and grouped together in a class diagram. The Classes in a class diagram represent both the main objects and or interactions in the application and the objects to be programmed. They are being used both for general conceptual modeling of the systematics of the application. Fig: 3. In the class diagram these classes are represented with boxes which contain three parts:    The upper part holds the name of the class The middle part contains the attributes of the class.3.4 Class Diagram 23 .

In component-based development (CBD). Fig: 3. Component diagrams allow an architect to verify that a system¶s required functionality is being implemented by components.5 Component Diagram 24 . component diagrams offer architects a natural format to design modeling a solution.3. thus ensuring that the eventual system will be acceptable.5 Component Diagram: The component diagram¶s main purpose is to show the structural relationships between the components of a system.

A deployment diagram is a diagram that shows the configuration of run time processing nodes and the components that live on them. -Like all other diagrams.3.6 Deployment Diagram: . deployment diagrams may contain notes and constraints.Graphically. both of which are used to group elements of your model into larger chunks. -Deployment diagrams may also contain packages or subsystems. a deployment diagram is collection of vertices and arcs. . Fig: 3. each of which must live on some mode. Contents -Deployment diagram commonly contain the following things y y Nodes Dependency and association relationships. -Deployment diagrams may also contain components.6 Deployment Diagram 25 .

Sign up to vote on this title
UsefulNot useful