OBJECT ORIENTED ANALYSIS

ExNo:1 Date:08.07.10 AIM:

To study the problem statement and requirement analysis using requisite pro for Bio-Informatics.

Problem statement and requirement analysis Using Requisite Pro

PROBLEM STATEMENT:
The Bio-informatics problem statement is given for analysis. The various activities include: 1.ADMIN DETAILS 2.DONOR DETAILS 3.ACCEPTOR DETAILS 4.DOCTOR DETAILS 5. TRANSCATION OF ORGAN DETAILS 6.MATCHING DETAILS
1. EXISTING SYSTEM:

The existing system of maintenance is manual and hence request donor matching is cumbersome and time consuming. Also there is a growing menace of middlemen luring innocent victims for money. The searching operation requires to go through volumes paper files. This process requires lot of skilled labours. So the existing system is slow and expensive. The searching operation requires to feed only very few parameters that too a low skilled labours can maintain the software. This process requires less number of labours. So the proposed system is fast and less expensive. 2. PROPOSED SYSTEM: The proposed system eliminates middlemen and also presents the requests with all the possible donors list very quickly. Since it is web application a donor can send his willingness to donate through web from anywhere in the globe. If we include module to have correspondence with the authorities such as email, chat then the system is fully fledged one.

Hardware interface:
Processor Ram Hard disk Motherboard Components Display Pentium 4 256 MB 40GB Intel 915 chipset Key Board, Mouse attached Color Monitor

Software interface:
Operating System Front end Backend Windows XP ASP.net MS-Access

Memory constraints:
Hard disk 64MB(appx)

Operations:
DONOR REGISTRATION ACCEPTOR REGISTRATION SELECTION MATCHIG

Requirements Analysis:
Basics of requirements engineering; 1.The essential requirements process: Understand the problem: Use data gathering techniques to elicit requirements Eg; interviews, questionnaires, focus groups, prototyping,observation, etc. Model and analyze the problem: Use some modeling methods() Eg: structured analysis, OOA, formal analysis, etc Attain agreement on the nature of the problem: Validation Conflict resolution, negolation

Communicate the problem: Specifications, documentation,review meetings etc. Manage change as the problem events: Requirements continue to evolve throughout software development. Requirements managements-maintain the agreement! Requirements should specify want but not now what refers to a system purpose 1. It is external to the purpose 2. It is a property of the application Requirements only exist in the application domain Distinguish between the machine and the application domain is essential for good requirements engineering Functional and non-functional requirements: Functional requirements: Fundamental functions of the system: E.g.: timing of functions E.g.: handling of exceptional situations Non functional requirements:

Constraints / obligations: E.g.: compatibility E.g.: compliance with interface standards, data formats, communication protocols Quality Requirements (soft goals); E.g.: security, safely, availability, usability, performance, portability, etcmust specified Elicitation techniques: Traditional approaches: o Introspection o Interview/survey o Group elicitation Observational approaches: o Protocol analysis o Participant observation

 Model based approaches: o Goal base: hierarchies of stake holders goals o Scenarios: characterizations of the ways in which the system is used o Use case: specific instances of interaction with the system Exploratory approaches: o Prototyping Structuring principle: 1 Portioning Captures aggregation/ part-of relationship Examples: o Goal is develop a ABP o Partition the problem into parts GUI design Design of application form Database maintenance Database connectivity Note: thus is not a design, it is problem decomposition Actual design might have any no. of components, with no relation to these sub-problems. Structuring principle: 2 Abstraction: A way of finding simulations between concepts by ignoring some details. Focus on the general/specific relationship between phenomena. Classification groups entities with a similar role as members of a single class. Generalizations express similarities between different classes in an is-a association.

Structuring principle: 3 Projection: Separates aspects of the model into multiple view points. Similar to projections used by architects for building. Partitioning defines a part-of relationship. Projection defines a view-of relationship.

 Partitioning assumes the parts are relatively independent.

CONCLUSION: Thus we have studied the problem statement and requirement analysis using requisite pro for Bio-Informatics.

ExNo:2 Date:15.07.10 AIM:

SOFTWARE DESCRIPTION

To study the project software description for Bio-informatics. MODULE DESCRIPTION: This project maintains the following two modules: 1.ADMIN VISIT 2.BROWSER VISIT Again the ADMIN VISIT contains the following sub modules: LOGIN ADMIN NEW ADMIN DELETE ADMIN UPDATE ACCEPTOR FORM DONOR FORM ENQUIRY SELECTION REPORT MATCH DONOR DETAILS ACCEPTOR DETAILS

The activities involved in each module can be explained as follows: 1. Login Module: Administrators are provided a login module to ensure addition of new organs to the bank and provision of storage facilities. 2.Admin New: This module used to add new administrator details to the database. 3.Admin Delete: This module used to delete already existing administrator details to the database. 4.Admin Update: This module used to modify/change made in an administrator details to the database.

5.Donor Registry: This module used enter details are registered along with the details of the organs they are willing to donate. 6.Acceptor Registry: Details are registered along with the details of the organs they are willing to donate. 7.Selection: This module used to find the acceptor details to match to the donor details. 8.Report Match: This module maintain the list of matching reports with acceptor and donor details. 9.Donar Details: This module maintains all the list of eligible volunteer organ donors. 10.Acceptor Details: This module maintains all the list of eligible volunteer organ acceptor. BROWSER VISIT: This module involves the preparation of the following reports. ACCEPTOR REPORT DONOR REPORT MATCHED REPORT

1.Acceptor Report: This modules are used to display and maintain the all acceptor details with organ details from the database. 2.Donor Report: This modules used to maintain and display the all donor details with organ details from the database 3.Matched Report: This modules used to maintain and display the all donor details with organ details from the database OUTPUT DESIGN: 1.LOGIN FORM : This form contain user name and password to enter in to the main project. It also has two command buttons login and cancel. If the user name and password are

correctly submitted then only we can enter in to main project. Even if one of those two things are wrong it shows that the login is failed.

2.MAIN FORM: The main menu contain donor,acceptor details ,transaction details,advance booking,matching details,enquiry,delivery details. It also contains exit button ,if we cick the exit button we can come out of the main fom. 3.ACCEPTOR REGISTRATION FORM: This form contains all details of acceptor such as address,city and name. It also contains DNA, bloodgroup,doctor details such as his address,name and phone number.It also contains the command buttons such as add ,save,clear and delete to enter and modify the acceptor details ,main form button to go back to main form. 4. DONOR REGISTRATION FORM: This form contains all details of donor such as address,city and name. It also contains DNA, bloodgroup,doctor details such as his address,name and phone number.It also contains the command buttons such as add ,save,clear and delete to enter and modify the acceptor details ,main form button to go back to main form. 5.STEM CELL TRANSACTION FORM: This form contains code ,acceptor,donor details ,match blood group,DNA type,good quantity,,status,goods cost,dates of sending and delivery ,services charge,advance and balance labels. This form also contains command buttons to enter and modify the transaction details customers. 6. REPORTS MENU: This menu contains following details ACCEPTOR REPORT DONOR REPORT MATCHED REPORT DOCTOR REPORT

CONCLUSION:

Thus we have studied the Project software description for Bio-Informatics .

ExNo:3 Date:22.07.10 AIM:

Use-case diagram with its specification

To study the Use-case diagram with its specifications for Bio-informatics. Use Case Model The use case model captures the requirements of a system. Use cases are a means of communicating with users and other stakeholders what the system is intended to do. Actors A use case diagram shows the interaction between the system and entities external to the system. These external entities are referred to as actors. Actors represent roles which may include human users, external hardware or other systems. An actor is usually drawn as a named stick figure, or alternatively as a class rectangle with the actor keyword.

Actors can generalize other actors as detailed in the following diagram:

Use Cases A use case is a single unit of meaningful work. It provides a high-level view of behavior observable to someone or something outside the system. The notation for a use case is an ellipse.

The notation for using a use case is a connecting line with an optional arrowhead showing the direction of control. The following diagram indicates that the actor "Customer" uses the "Withdraw" use case.

The uses connector can optionally have multiplicity values at each end, as in the following diagram, which shows a customer may only have one withdrawal session at a time, but a bank may have any number of customers making withdrawals concurrently.

Use Case Definition A use case typically Includes:

Name and description Requirements Constraints Scenarios Scenario diagrams Additional information.

Name and Description A use case is normally named as a verb-phrase and given a brief informal textual description. Requirements The requirements define the formal functional requirements that a use case must supply to the end user. They correspond to the functional specifications found in structured methodologies. A requirement is a contract or promise that the use case will perform an action or provide some value to the system.

Constraints A constraint is a condition or restriction that a use case operates under and includes pre-, post- and invariant conditions. A precondition specifies the conditions that need to be met before the use case can proceed. A post-condition is used to document the change in conditions that must be true after the execution of the use case. An invariant condition specifies the conditions that are true throughout the execution of the use case. Scenarios A Scenario is a formal description of the flow of events that occur during the execution of a use case instance. It defines the specific sequence of events between the system and the external actors. It is normally described in text and corresponds to the textual representation of the sequence diagram. Including Use Cases Use cases may contain the functionality of another use case as part of their normal processing. In general it is assumed that any included use case will be called every time the basic path is run. An example of this is to have the execution of the use case <Card Identification> to be run as part of a use case <Withdraw>.

Use Cases may be included by one or more Use Case, helping to reduce the level of duplication of functionality by factoring out common behavior into Use Cases that are re-used many times. Extending Use Cases One use case may be used to extend the behavior of another; this is typically used in exceptional circumstances. For example, if before modifying a particular type of customer order, a user must get approval from some higher authority, then the <Get Approval> use case may optionally extend the regular <Modify Order> use case.

Extension Points The point at which an extending use case is added can be defined by means of an extension point.

System Boundary It is usual to display use cases as being inside the system and actors as being outside the system.

USECASE DIAGRAM FOR BIO-INFORMATICS:

Login

store the stem cell in pareticular place

Enter the Name and Address

Enter the Age And Sex Donar

System

Verify the above information

Enter the BloodGroup and DNA

Enter the bloodgroup and DNA

Match the blood group and DNA

Display The Details Acceptor

Accept the Stem Cells

CONCLUSION:
Thus the Use-case diagram with its specifications for Bio-Informatics was studied.

ExNo: 4 Date:29.07.10 AIM:

SEQUENCE DIAGRAM

To study the Sequence diagram with its specifications for Bio-Informatics.

Sequence Diagrams
A sequence diagram is a form of interaction diagram which shows objects as lifelines running down the page, with their interactions over time represented as messages drawn as arrows from the source lifeline to the target lifeline. Sequence diagrams are good at showing which objects communicate with which other objects; and what messages trigger those communications. Sequence diagrams are not intended for showing complex procedural logic. Lifelines A lifeline represents an individual participant in a sequence diagram. A lifeline will usually have a rectangle containing its object name. If its name is "self", that indicates that the lifeline represents the classifier which owns the sequence diagram.

Sometimes a sequence diagram will have a lifeline with an actor element symbol at its head. This will usually be the case if the sequence diagram is owned by a use case. Boundary, control and entity elements from robustness diagrams can also own lifelines.

Messages Messages are displayed as arrows. Messages can be complete, lost or found; synchronous or asynchronous; call or signal. In the following diagram, the first message is a synchronous message (denoted by the solid arrowhead) complete with an implicit return message; the second message is asynchronous (denoted by line arrowhead), and the third is the asynchronous return message (denoted by the dashed line).

Execution Occurrence A thin rectangle running down the lifeline denotes the execution occurrence, or activation of a focus of control. In the previous diagram, there are three execution occurrences. The first is the source object sending two messages and receiving two replies; the second is the target object receiving a synchronous message and returning a reply; and the third is the target object receiving an asynchronous message and returning a reply. Self Message A self message can represent a recursive call of an operation, or one method calling another method belonging to the same object. It is shown as creating a nested focus of control in the lifelines execution occurrence.

Lost and Found Messages Lost messages are those that are either sent but do not arrive at the intended recipient, or which go to a recipient not shown on the current diagram. Found messages are those that arrive from an unknown sender, or from a sender not shown on the current diagram. They are denoted going to or coming from an endpoint element.

Lifeline Start and End A lifeline may be created or destroyed during the timescale represented by a sequence diagram. In the latter case, the lifeline is terminated by a stop symbol, represented as a cross. In the former case, the symbol at the head of the lifeline is shown at a lower level down the page than the symbol of the object that caused the creation. The following diagram shows an object being created and destroyed.

Duration and Time Constraints By default, a message is shown as a horizontal line. Since the lifeline represents the passage of time down the screen, when modelling a real-time system, or even a time-bound business process, it can be important to consider the length of time it takes to perform actions. By setting a duration constraint for a message, the message will be shown as a sloping line.

Combined Fragments It was stated earlier that sequence diagrams are not intended for showing complex procedural logic. While this is the case, there are a number of mechanisms that do allow for adding a degree of procedural logic to diagrams and which come under the heading of combined fragments. A combined fragment is one or more processing sequence enclosed in a frame and executed under specific named circumstances. The fragments available are: Alternative fragment (denoted alt) models ifthenelse constructs. Option fragment (denoted opt) models switch constructs.

Break fragment models an alternative sequence of events that is processed instead of the whole of the rest of the diagram. Parallel fragment (denoted par) models concurrent processing. Weak sequencing fragment (denoted seq) encloses a number of sequences for which all the messages must be processed in a preceding segment before the following segment can start, but which does not impose any sequencing within a segment on messages that dont share a lifeline.

Strict sequencing fragment (denoted strict) encloses a series of messages which must be processed in the given order. Negative fragment (denoted neg) encloses an invalid series of messages. Critical fragment encloses a critical section. Ignore fragment declares a message or message to be of no interest if it appears in the current context. Consider fragment is in effect the opposite of the ignore fragment: any message not included in the consider fragment should be ignored. Assertion fragment (denoted assert) designates that any sequence not shown as an operand of the assertion is invalid. Loop fragment encloses a series of messages which are repeated.

The following diagram shows a loop fragment.

There is also an interaction occurrence, which is similar to a combined fragment. An interaction occurrence is a reference to another diagram which has the word "ref" in the top left corner of the frame, and has the name of the referenced diagram shown in the middle of the frame. Gate A gate is a connection point for connecting a message inside a fragment with a message outside a fragment. EA shows a gate as a small square on a fragment frame. Diagram gates act as off-page connectors for sequence diagrams, representing the source of incoming messages or the target of outgoing messages.The following two diagrams show how they might be used in practice. Note that the gate on the top level diagram is the point at which the message arrowhead touches the reference fragment - there is no need to render it as a box shape.

Part Decomposition An object can have more than one lifeline coming from it. This allows for inter- and intra-object messages to be displayed on the same diagram.

State Invariant / Continuations A state invariant is a constraint placed on a lifeline that must be true at run-time. It is shown as a rectangle with semi-circular ends.

A continuation has the same notation as a state invariant, but is used in combined fragments and can stretch across more than one lifeline. SEQUENCE DIAGRAM FOR BIO-INFORMATICS:
dor : n Da s ye : sm St a c pr : ct Aeo

Li on g

Sr t e t mls t e S C o h e e l

E r hDa eis n t eo r t l t e nD a

S e e eis tr t D l o h t a

E r hA eo eis n t e c pr t l t e ct D a

ViyhD is e tee l r f t a

EehB drua D nr e l og pn N t t o o d A

EehB drua D nr e l o o n N t t o Gp d A

M h e l o rua D a t B do n N t h o Gp d A c

D l yhda i p t eeis sa tl

Ae t e t m ls c phS C ct e e l

CONCLUSION: Thus Sequence diagram with its specifications for Bio-Informatics was studied.

Ex No: 5 Date:29.07.10 AIM:

COLLABORATION DIAGRAM

To study the Collaboration diagram with its specifications for Bio-Informatics. UML COLLABRATION DIAGRAM: Collaboration Diagram Sample Similar to Sequence Diagram, the Communication Diagram is also used to model the dynamic behavior of the use case. When compare to Sequence Diagram, the Communication Diagram is more focused on showing the collaboration of objects rather than the time sequence. You don't need to create both diagrams manually because VP-UML allows you to generate it from one to the other.

COLLABORATION DIAGRAM FOR BIO-INFORMATICS:

2: Sto the S m ells re te C 1: L ogin 3: E r the D ar D nte on etails 7: En the Blo gro a D A ter od up nd N d o ar :D n

4 Sto th D ta : re e e ils 6 Ve th D tails : rify e e 9 M tch th B d ro p a d D A : a e loo G u n N

s:Syste m

5: En the A ter cceptor D ils eta 8: Ente th Blo dG p an D A r e o rou d N 10 D lay th d ta : isp e e ils 11: A ccep th Stem C lls t e e

a :Acce pt or

CONCLUSION: Thus the Collaboration diagram with its specifications for Bio-Informatics was studied.

Ex No: 6 Date:12.08.10 AIM:

REFINEMENT OF SEQUENCE DIAGRAM

To study the Refinement of Sequence diagram with its specifications for BioInformatics.

REFINEMENT OF SEQUENCE DIAGRAM

dDn r : oa

sSse : yt m

aAc p r : c e to

Lg o in

S r th S me toe e t Clls e

Ete t eDn rDt ils n r h o a ea

S r th Dta toe e e ils

Ete th Ac po Dta n r e c e t r e ils

Vr yt eDta eif h e ils

Ete th B o go pa dD A n r e lo d r u n N

Et rth B o G u a dD A ne e lod r p n N o

Mtc th B o G u a dD A a h e lo d r p n N o

D p yt edta is la h e ils

Ac p t eS m e c e t h t Clls e

CONCLUSION: Thus the Refinement of Sequence diagram with its specifications for Bio-Informatics was studied.

Ex No: 7 Date:12.08.10 AIM:

REFINEMENT OF COLLOBORATION DIAGRAM

To study the Refinement of collaboration diagram with its specifications for Bio-Informatics.

REFINEMENT OF COLLOBORATION DIAGRAM

2: S tore the Stem Cells 1: Login 3: E nter the Donar Details 7: E nter the Blood group and DNA d:Donar

4: S tore the Details 6: Verify the Details 9: M atc h the B loodGroup and DNA

s :S yste m

5: E nter the Acc eptor Details 8: E nter the BloodGroup and DNA 10: Display the details 11: A c cept the S tem Cells

a:A ccept or

CONCLUSION: Thus the Refinement of Collaboration diagram with its specifications for Bio-Informatics was studied.

OBJECT ORIENTED DESIGN Ex No: 8 Date:19.08.10 AIM:

To study the Class diagram with its specifications for Bio-Informatics. CLASS DIAGRAM: The class diagram shows the building blocks of any object-orientated system. Class diagrams depict a static view of the model, or part of the model, describing what attributes and behavior it has rather than detailing the methods for achieving operations. Class diagrams are most useful in illustrating relationships between classes and interfaces. Generalizations, aggregations, and associations are all valuable in reflecting inheritance, composition or usage, and connections respectively. The diagram below illustrates aggregation relationships between classes. The lighter aggregation indicates that the class "Account" uses AddressBook, but does not necessarily contain an instance of it. The strong, composite aggregations by the other connectors indicate ownership or containment of the source classes by the target classes, for example Contact and ContactGroup values will be contained in AddressBook.

CLASS DIAGRAM

Classes A class is an element that defines the attributes and behaviors that an object is able to generate. The behavior is described by the possible messages the class is able to understand, along with operations that are appropriate for each message. Classes may also have definitions of constraints, tagged values and stereotypes. Class Notation Classes are represented by rectangles which show the name of the class and optionally the name of the operations and attributes. Compartments are used to divide the class name, attributes and operations

In the diagram below the class contains the class name in the topmost compartment, the next compartment details the attributes, with the "center" attribute showing initial values. The final compartment shows the operations setWidth, setLength and setPosition and their parameters. The notation that precedes the attribute, or operation name, indicates the visibility of the element: if the + symbol is used, the attribute, or operation, has a public level of visibility; if a - symbol is used, the attribute, or operation, is private. In addition the # symbol allows an operation, or attribute, to be defined as protected, while the ~ symbol indicates package visibility.

Interfaces An interface is a specification of behavior that implementers agree to meet; it is a contract. By realizing an interface, classes are guaranteed to support a required behavior, which allows the system to treat non-related elements in the same way that is, through the common interface.

Interfaces may be drawn in a similar style to a class, with operations specified, as shown below. They may also be drawn as a circle with no explicit operations detailed. When drawn as a circle, realization links to the circle form of notation are drawn without target arrows.

Tables Although not a part of the base UML, a table is an example of what can be done with stereotypes. It is drawn with a small table icon in the upper right corner. Table attributes are stereotyped column. Most tables will have a primary key, being one or more fields that form a unique combination used to access the table, plus a primary key operation which is stereotyped PK. Some tables will have one or more foreign keys, being one or more fields that together map onto a primary key in a related table, plus a foreign key operation which is stereotyped FK.

Associations An association implies two model elements have a relationship - usually implemented as an instance variable in one class. This connector may include named roles at each end, cardinality, direction and constraints. Association is the general relationship type between elements. For more than two elements, a diamond representation toolbox element can be used as well. When code is generated for class diagrams, named association ends become instance variables in the target class. So, for the example below, "playsFor" will become an instance variable in the "Player" class.

Generalizations A generalization is used to indicate inheritance. Drawn from the specific classifier to a general classifier, the generalize implication is that the source inherits the target's characteristics. The following diagram shows a parent class generalizing a child class. Implicitly, an instantiated object of the Circle class will have attributes x_position, y_position and radius and a method display(). Note that the class "Shape" is abstract, shown by the name being italicized.

The following diagram shows an equivalent view of the same information.

Aggregations Aggregations are used to depict elements which are made up of smaller components. Aggregation relationships are shown by a white diamond-shaped arrowhead pointing towards the target or parent class. A stronger form of aggregation - a composite aggregation - is shown by a black diamond-shaped arrowhead and is used where components can be included in a maximum of one composition at a time. If the parent of a composite aggregation is deleted, usually all of its parts are deleted with it; however a part can be individually removed from a composition without having to delete the entire composition. Compositions are transitive, asymmetric relationships and can be recursive.

The following diagram illustrates the difference between weak and strong aggregations. An address book is made up of a multiplicity of contacts and contact groups. A contact group is a virtual grouping of contacts; a contact may be included in more than one contact group. If you delete an address book, all the contacts and contact groups will be deleted too; if you delete a contact group, no contacts will be deleted.

Association Classes An association class is a construct that allows an association connection to have operations and attributes. The following example shows that there is more to allocating an employee to a project than making a simple association link between the two classes: the role the employee takes up on the project is a complex entity in its own right and contains detail that does not belong in the employee or project class. For example, an employee may be working on several projects at the same time and have different job titles and security levels on each.

Dependencies A dependency is used to model a wide range of dependent relationships between model elements. It would normally be used early in the design process where it is known that there is some kind of link between two elements, but it is too early to know exactly what the relationship is. Later in the design process, dependencies will be stereotyped (stereotypes available include instantiate, trace, import, and others), or replaced with a more specific type of connector. Traces The trace relationship is a specialization of a dependency, linking model elements or sets of elements that represent the same idea across models. Traces are often used to track requirements and model changes. As changes can occur in both directions, the order of this dependency is usually ignored. The relationship's properties can specify the trace mapping, but the trace is usually bi-directional, informal and rarely computable. Realizations The source object implements or realizes the destination. Realizations are used to express traceability and completeness in the model - a business process or requirement is realized by one or more use cases, which are in turn realized by some

classes, which in turn are realized by a component, etc. Mapping requirements, classes, etc. across the design of your system, up through the levels of modeling abstraction, ensures the big picture of your system remembers and reflects all the little pictures and details that constrain and define it. A realization is shown as a dashed line with a solid arrowhead.

Nestings A nesting is connector that shows the source element is nested within the target element. The following diagram shows the definition of an inner class, although in EA it is more usual to show them by their position in the project view hierarchy.

CLASS DIAGRAM FOR BIO-INFORMATICS:

D:Donar name : String Address : String BloodGroup : String DNA : String Login() Update() Display()

S:System IP address : integer Password : integer Verification() Display() Update() Delete()

A:Acceptor name : String Address : String BloodGroup : String DNA : String Login() Update() Display()

CONCLUSION: Thus the Class diagram with its specifications for Bio-Informatics was studied.

OBJECT ORIENTED TESTING

Ex No: 9 Date:26.08.10 AIM:
To study the Activity diagram and state chart diagram with its specifications for Bio-Informatics. ACTIVITY DIAGRAM: In UML, an activity diagram is used to display the sequence of activities. Activity diagrams show the workflow from a start point to the finish point detailing the many decision paths that exist in the progression of events contained in the activity. They may be used to detail situations where parallel processing may occur in the execution of some activities. Activity diagrams are useful for business modelling where they are used for detailing the processes involved in business activities. An Example of an activity diagram is shown below.

Activity diagram and state chart diagram

The following sections describe the elements that constitute an activity diagram. Activities An activity is the specification of a parameterized sequence of behaviour. An activity is shown as a round-cornered rectangle enclosing all the actions, control flows and other elements that make up the activity.

Actions An action represents a single step within an activity. Actions are denoted by round-cornered rectangles.

Action Constraints Constraints can be attached to an action. The following diagram shows an action with local pre- and post-conditions.

Control Flow A control flow shows the flow of control from one action to the next. Its notation is a line with an arrowhead.

Initial Node An initial or start node is depicted by a large black spot, as shown below.

Final Node There are two types of final node: activity and flow final nodes. The activity final node is depicted as a circle with a dot inside.

The flow final node is depicted as a circle with a cross inside.

The difference between the two node types is that the flow final node denotes the end of a single control flow; the activity final node denotes the end of all control flows within the activity. Objects and Object Flows An object flow is a path along which objects or data can pass. An object is shown as a rectangle

An object flow is shown as a connector with an arrowhead denoting the direction the object is being passed.

An object flow must have an object on at least one of its ends. A shorthand notation for the above diagram would be to use input and output pins.

A data store is shown as an object with the datastore keyword.

Decision and Merge Nodes Decision nodes and merge nodes have the same notation: a diamond shape. They can both be named. The control flows coming away from a decision node will have guard conditions which will allow control to flow if the guard condition is met. The following diagram shows use of a decision node and a merge node.

Fork and Join Nodes Forks and joins have the same notation: either a horizontal or vertical bar (the orientation is dependent on whether the control flow is running left to right or top to bottom). They indicate the start and end of concurrent threads of control. The following diagram shows an example of their use.

A join is different from a merge in that the join synchronizes two inflows and produces a single outflow. The outflow from a join cannot execute until all inflows have been received. A merge passes any control flows straight through it. If two or more inflows are received by a merge symbol, the action pointed to by its outflow is executed two or more times.

Expansion Region An expansion region is a structured activity region that executes multiple times. Input and output expansion nodes are drawn as a group of three boxes representing a multiple selection of items. The keyword "iterative", "parallel" or "stream" is shown in the top left corner of the region.

Exception Handlers Exception Handlers can be modelled on activity diagrams as in the example below.

Interruptible Activity Region An interruptible activity region surrounds a group of actions that can be interrupted. In the very simple example below, the "Process Order" action will execute until completion, when it will pass control to the "Close Order" action, unless a "Cancel Request" interrupt is received, which will pass control to the "Cancel Order" action.

Partition An activity partition is shown as either a horizontal or vertical swimlane. In the following diagram, the partitions are used to separate actions within an activity into those performed by the accounting department and those performed by the customer.

ACTIVITY DIAGRAM For BIO-INFORMATICS:

Donar

System

Acceptor

Login

Enter the Name and Addrress

Enter the D onar BloodG roup and D NA

Eter the D etails

Store the Details

Verify the Details

Enter the acceptor BloodG roup and DNA

Match the Blood Group and D NA

D isplay the D etails

Donar Stem cells

Accept the Stem Cell

State Machine Diagram state machine diagram models the behaviour of a single object, specifying the sequence of events that an object goes through during its lifetime in response to events. As an example, the following state machine diagram shows the states that a door goes through during its lifetime.

The door can be in one of three states: "Opened", "Closed" or "Locked". It can respond to the events Open, Close, Lock and Unlock. Notice that not all events are valid in all states; for example, if a door is opened, you cannot lock it until you close it. Also notice that a state transition can have a guard condition attached: if the door is Opened, it can only respond to the Close event if the condition doorWay->isEmpty is fulfilled. The syntax and conventions used in state machine diagrams will be discussed in full in the following sections. States A state is denoted by a round-cornered rectangle with the name of the state written inside it.

Initial and Final States The initial state is denoted by a filled black circle and may be labeled with a name. The final state is denoted by a circle with a dot inside and may also be labeled with a name.

Transitions Transitions from one state to the next are denoted by lines with arrowheads. A transition may have a trigger, a guard and an effect, as below.

"Trigger" is the cause of the transition, which could be a signal, an event, a change in some condition, or the passage of time. "Guard" is a condition which must be true in order for the trigger to cause the transition. "Effect" is an action which will be invoked directly on the object that owns the state machine as a result of the transition. State Actions In the transition example above, an effect was associated with the transition. If the target state had many transitions arriving at it, and each transition had the same effect associated with it, it would be better to associate the effect with the target state rather than the transitions. This can be done by defining an entry action for the state. The diagram below shows a state with an entry action and an exit action.

It is also possible to define actions that occur on events, or actions that always occur. It is possible to define any number of actions of each type. Self-Transitions A state can have a transition that returns to itself, as in the following diagram. This is most useful when an effect is associated with the transition.

Compound States A state machine diagram may include sub-machine diagrams, as in the example below.

The alternative way to show the same information is as follows

. The notation in the above version indicates that the details of the Check PIN submachine are shown in a separate diagram. Entry Point Sometimes you wont want to enter a sub-machine at the normal initial state. For example, in the following sub-machine it would be normal to begin in the "Initializing" state, but if for some reason it wasnt necessary to perform the initialization, it would be possible to begin in the "Ready" state by transitioning to the named entry point.

The following diagram shows the state machine one level up.

Exit Point In a similar manner to entry points, it is possible to have named alternative exit points. The following diagram gives an example where the state executed after the main processing state depends on which route is used to transition out of the state.

Choice Pseudo-State A choice pseudo-state is shown as a diamond with one transition arriving and two or more transitions leaving. The following diagram shows that whichever state is arrived at, after the choice pseudo-state, is dependent on the message format selected during execution of the previous state.

Junction Pseudo-State Junction pseudo-states are used to chain together multiple transitions. A single junction can have one or more incoming, and one or more outgoing, transitions; a guard can be applied to each transition. Junctions are semantic-free. A junction which splits an incoming transition into multiple outgoing transitions realizes a static conditional branch, as opposed to a choice pseudo-state which realizes a dynamic conditional branch.

Terminate Pseudo-State Entering a terminate pseudo-state indicates that the lifeline of the state machine has ended. A terminate pseudo-state is notated as a cross.

History States A history state is used to remember the previous state of a state machine when it was interrupted. The following diagram illustrates the use of history states. The example is a state machine belonging to a washing machine.

In this state machine, when a washing machine is running, it will progress from "Washing" through "Rinsing" to "Spinning". If there is a power cut, the washing machine will stop running and will go to the "Power Off" state. Then when the power is restored, the Running state is entered at the "History State" symbol meaning that it should resume where it last left-off.

Concurrent Regions A state may be divided into regions containing sub-states that exist and execute concurrently. The example below shows that within the state "Applying Brakes", the front and rear brakes will be operating simultaneously and independently. Notice the use of fork and join pseudo-states, rather than choice and merge pseudo-states. These symbols are used to synchronize the concurrent threads.

STATECHART DIAGRAM FOR BIO-INFORMATICS:

ACCEPTOR/DONOR

Login

Transaction

Delivery

Selection

CONCLUSION: Thus the Activity diagram and state chart diagram with its specifications for Bio-Informatics was studied.

Ex.No:10 Date:2.9.10
AIM:

Test Cases and Test plans

To create the test case and test plan for Bio-Informatics.

Test Cases:
Testing Phase: The objective of these activities is to prove that the developed system satisfies the requirements defined in the requirements Document. Several Types of tests will be conducted in this phase. The various components of the system are integrated and tested systematically. Test Plans: Testing is an important phase in project development. Testing phase ensures error free software. Instead of performance testing at the end of coding phase, tests must be done simultaneously while coding the project to avoid complications. Tests must be done to check whether the reports are obtained in expected way. Unit Testing: Unit testing is a dynamic method of verification where the program is actually compiled and executed. In unit tests each and every modules in the software that had give report of the software which are successfully run and there are no errors in the report. Test Name Login password Invalid password Observation Expected Result Enters the password it will Success: Match Occurred be validated. Validation occurs Failure: Match does not occur Fig: Example for Unit testing

Integration Testing: In the integration testing we consider the integrity between the forms inside the module, that check the connection of the forms inside the module if there are any errors in the connectivity ,it will give error

S. No 1

Test Case While reserving in the donor, it checks the number of available DNA,HLA in the specified donor details. If the number of DNA,HLA is less then it rejects the registration. While reserving the stemcells, it checks the DNA,HLA is match for making the transaction of stemcells.

Expected Result Checks the number of DNA,HLA available in the specified donor details.

Actual Results Reserve in the specified donor details.

Check the DNA,HLA Pay the amount number for sufficient for transaction stemcells to make a of stemcells. registration.

Fig: Example for Integration Testing

System Testing: It is the testing which implements the software in the system, how the system reacts while running the project that is how it is taken the memory while doing this we must test the memory. S. No 1 Test Case While reserving in the donor, it checks the number of available DNA,HLA in the specified donor details. If the number of DNA,HLA is less then it rejects the registration. While registering the stemcells, it checks the DNA,HLA is match for making the transaction of stemcells. Expected Result Checks the number of DNA,HLA available in the specified donor details. Actual Results Reserve in the specified donor details.

Check the DNA,HLA Pay the amount number for sufficient for transaction stemcells to make a of stemcells. registration.

Fig: Example for System Testing

Security Testing: This is the testing it will say the security level of the project. Any one person who is unauthorized cant enter into our project. Performance Testing: This testing is done in our project which gives the report of the project had the high or not.

Test Case Choose the enter button for main page Choose the Button to login to the admin page Choose the Operation to do Choose the Particular operation Want to see the next page click link

Expected Result Enter into the bioinformatics Main menu page Display the admin page Display the main page Display the module page Display the continued operation

Actual Result Result Status To display main Pass page Login to admin page the Pass the Pass the Pass the Pass the Pass the Pass

To display main page To display information To display remaining information Choose Back to Moved to the back To display move to back page page previous page Choose Home to Moved to the home To display move to home page page home page

Fig: Example for Performance Testing

CONCLUSION: Thus the test case and test plan for Bio-Informatics was successfully completed.

Ex. No.: 11 Date Aim: :9.9.10

Validations

To perform the validation testing for the project Bio-Informatics. Validations Performed: A. Module Name Purpose Validations General Login Add new record 3 Search a record : Main menu : To enter the data about transactions. Expected Result Valid id and Actual Result Valid Information Result Status Success. Success.

S. No. 1 2

password Record not exists Record Added in Database and so added. Record present in Database. Record Displayed.

Success.

B.

Module Name Purpose

: Enquiry : To update the transactions and checking it status. . Actual Result Records having displayed. Record updated. Success. Result Status Success.

S. No. 1

Validations Check the Transaction

Expected Result Checks if the DNA,HLA type is entered. Transactions updated in Report record. Transaction is added to database record.

Update transaction.

Add transactions

Transaction added.

Success

CONCLUSION: Thus the Bio-Informatics has been validated successfully.

IMPLEMENTATION

Ex No: 12 Date:16.9.10 AIM:

COMPONENT DIAGRAM

To study the Component diagram with its specifications for Bio-Informatics. COMPONENT DIAGRAM: Component diagrams illustrate the pieces of software, embedded controllers, etc., that will make up a system. A component diagram has a higher level of abstraction than a Class Diagram - usually a component is implemented by one or more classes (or objects) at runtime. They are building blocks so a component can eventually encompass a large portion of a system.

The diagram above demonstrates some components and their interrelationships. Assembly connectors "link" the provided interfaces supplied by "Product" and "Customer" to the required interfaces specified by "Order". A dependency relationship maps a customer's associated account details to the required interface; "Payment", indicated by "Order". Components are similar in practice to package diagrams, as they define boundaries and are used to group elements into logical structures. The difference between package diagrams and component diagrams is that Component Diagrams offer a more semantically rich grouping mechanism. With component diagrams all of the model elements are private, whereas package diagrams only display public items. Representing Components Components are represented as a rectangular classifier with the keyword component; optionally the component may be displayed as a rectangle with a component icon in the right-hand upper corner.

Assembly Connector The assembly connector bridges a components required interface (Component1) with the provided interface of another component (Component2); this allows one component to provide the services that another component requires.

Components with Ports Using Ports with component diagrams allows for a service or behavior to be specified to its environment as well as a service or behavior that a component requires. Ports may specify inputs and outputs as they can operate bi-directionally. The following diagram details a component with a port for online services along with two provided interfaces order entry and tracking as well as a required interface payment.

BIO-INFORMATICS COMPONENT DIAGRAM:

B IO-INFORM A TICS B A S ED ON UM BLICA L CO RD

CONCLUSION: Thus the Component diagram and with its specifications for Bio-Informatics was studied.

Ex No: 13 Date:30.9.10 AIM:

DEPLOYMENT DIAGRAM

To study the Deployment diagram with its specifications for Bio-Informatics. Deployment Diagrams A deployment diagram models the run-time architecture of a system. It shows the configuration of the hardware elements (nodes) and shows how software elements and artifacts are mapped onto those nodes. Node A Node is either a hardware or software element. It is shown as a threedimensional box shape, as shown below.

Node Instance A node instance can be shown on a diagram. An instance can be distinguished from a node by the fact that its name is underlined and has a colon before its base node type. An instance may or may not have a name before the colon. The following diagram shows a named instance of a computer.

Node Stereotypes A number of standard stereotypes are provided for nodes, namely cdrom, cd-rom, computer, disk array, pc, pc client, pc server, secure, server, storage, unix server, user pc. These will display an appropriate icon in the top right corner of the node symbol

Artifact An artifact is a product of the software development process. That may include process models (e.g. use case models, design models etc), source files, executables, design documents, test reports, prototypes, user manuals, etc.

An artifact is denoted by a rectangle showing the artifact name, the artifact keyword and a document icon, as shown below.

Association In the context of a deployment diagram, an association represents a communication path between nodes. The following diagram shows a deployment diagram for a network, depicting network protocols as stereotypes, and multiplicities at the association ends.

Node as Container A node can contain other elements, such as components or artifacts. The following diagram shows a deployment diagram for part of an embedded system, depicting an executable artifact as being contained by the motherboard node.

DEPLOYMENT DIAGRAM FOR BIO-INFORMATICS:

Urnr c s It f e e e a

D Be a a t s a

CONCLUSION: Thus the Deployment diagram and with its specifications for Bio-Informatics was studied.

APPENDIX

A. CODING AIM: To write the ASP.NET code for the Bio-informatics based on Umbilical cord. CODING:
LOGIN NEW: Imports System.Data.OleDb Partial Class loginnew Inherits System.Web.UI.Page Dim conn As New OleDbConnection Dim connread As New OleDbConnection Dim comm As New OleDbCommand Dim commread As New OleDbCommand Dim reading As OleDbDataReader Dim sql As String Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click conn.Open() ' Try label1.Text = "" sql = "select * from admin where NAME='" & TextBox1.Text & "' AND PASS='" & TextBox2.Text & "'" comm = New OleDbCommand(sql, conn) reading = comm.ExecuteReader() If reading.Read Then Response.Redirect("menugeneral.aspx") Else Label1.Text = "Illegal User" End If conn.Close() End Sub Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load conn = New OleDbConnection("Provider=Microsoft.Jet.Oledb.4.0;Data Source=C:\Users\MAYAVATHI\Documents\umbilical.mdb") End Sub End Class

SECRET CODE:

Partial Class SECRETCODE Inherits System.Web.UI.Page Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click If (TextBox1.Text = "*****") Then Response.Redirect("menugeneral.aspx") End If End Sub End Class ADMIN NEW: Imports System.Data.OleDb Partial Class reginew Inherits System.Web.UI.Page Dim conn As New OleDbConnection Dim connread As New OleDbConnection Dim comm As New OleDbCommand Dim commread As New OleDbCommand Dim reading As OleDbDataReader Dim sql As String Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click conn.Open() Dim k As Integer Try sql = "insert into admin values('" sql = sql + TextBox3.Text & "','" sql = sql + TextBox2.Text & "','" sql = sql + ListBox1.Text & "','" sql = sql + ListBox2.Text & "','" sql = sql + TextBox4.Text & "','" sql = sql + TextBox5.Text & "','" sql = sql + TextBox6.Text & "','" sql = sql + ListBox3.Text & "','" sql = sql + TextBox8.Text & "','" sql = sql + TextBox9.Text & "','" sql = sql + TextBox10.Text & "','" sql = sql + TextBox11.Text & "','" sql = sql + TextBox12.Text & "')" comm = New OleDbCommand(sql, conn) k = comm.ExecuteNonQuery() If (k = 1) Then MsgBox("Data Got Inserted") End If Catch eo As Exception

MsgBox("Database may be corrupted contact Admin", MsgBoxStyle.Critical) End Try conn.Close() End Sub Protected Sub form1_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles form1.Load conn = New OleDbConnection("Provider=Microsoft.Jet.Oledb.4.0;Data Source=C:\Users\MAYAVATHI\Documents\umbilical.mdb") Try conn.Open() sql = "select max(trim(code)) from admin" comm = New OleDbCommand(sql, conn) reading = comm.ExecuteReader() Dim codenew As String If reading.Read Then codenew = reading.GetString(0) codenew = CType(Val(codenew) + 1, String) Else MsgBox("Database may be corrupted", MsgBoxStyle.Critical) End If conn.Close() TextBox3.Text = codenew Catch eo As Exception MsgBox("Database may be corrupted contact Admin", MsgBoxStyle.Critical) End Try End Sub Protected Sub Button2_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button2.Click Dim codenew As String codenew = "" Try conn.Open() sql = "select max(trim(code)) from admin" comm = New OleDbCommand(sql, conn) reading = comm.ExecuteReader() If reading.Read Then codenew = reading.GetString(0) codenew = CType(Val(codenew) + 1, String) Else MsgBox("Database may be corrupted", MsgBoxStyle.Critical) TextBox2.Text = ""

TextBox3.Text = codenew TextBox4.Text = "" TextBox5.Text = "" TextBox6.Text = "" TextBox8.Text = "" TextBox9.Text = "" TextBox10.Text = "" TextBox11.Text = "" TextBox12.Text = "" End If Catch eo As Exception MsgBox("Database may be corrupted contact Admin", MsgBoxStyle.Critical) TextBox2.Text = "" TextBox3.Text = codenew TextBox4.Text = "" TextBox5.Text = "" TextBox6.Text = "" TextBox8.Text = "" TextBox9.Text = "" TextBox10.Text = "" TextBox11.Text = "" TextBox12.Text = "" End Try End Sub End Class ACCEPTOR REGISTRATION: Imports System.Data.OleDb Partial Class Default2 Inherits System.Web.UI.Page Dim conn As New OleDbConnection Dim connread As New OleDbConnection Dim comm As New OleDbCommand Dim commread As New OleDbCommand Dim reading As OleDbDataReader Dim sql As String Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load conn = New OleDbConnection("Provider=Microsoft.Jet.Oledb.4.0;Data Source=C:\Users\MAYAVATHI\Documents\umbilical.mdb") End Sub Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click conn.Open() Dim sex As String sql = "insert into acceptor values('"

sql = sql + TextBox1.Text & "','" sql = sql + TextBox2.Text & "','" If (CheckBox1.Checked = True) Then sex = "Male" Else sex = "Female" End If sql = sql + sex & "','" sql = sql + TextBox3.Text & "','" sql = sql + ListBox1.Text & "','" sql = sql + ListBox2.Text & "','" sql = sql + TextBox4.Text & "','" sql = sql + TextBox5.Text & "','" sql = sql + TextBox6.Text & "','" sql = sql + TextBox7.Text & "','" sql = sql + ListBox3.Text & "','" sql = sql + TextBox11.Text & "','" sql = sql + TextBox8.Text & "','" sql = sql + TextBox10.Text & "','" sql = sql + ListBox4.Text & "','" sql = sql + ListBox5.Text & "','" '==================================== Dim hla1 As String Dim hla2 As String Dim hla3 As String Dim hla4 As String Dim hla5 As String Dim hla6 As String '======================================= If RadioButton1.Checked = True Then hla1 = "A" End If If RadioButton2.Checked = True Then hla1 = "B" End If If RadioButton3.Checked = True Then hla1 = "C" End If '====================================== If RadioButton4.Checked = True Then hla2 = "A" End If If RadioButton5.Checked = True Then hla2 = "B" End If If RadioButton6.Checked = True Then hla2 = "C" End If '==================================== If RadioButton7.Checked = True Then

hla3 = "A" End If If RadioButton8.Checked = True Then hla3 = "B" End If If RadioButton9.Checked = True Then hla3 = "C" End If '==================================== If RadioButton10.Checked = True Then hla4 = "A" End If If RadioButton11.Checked = True Then hla4 = "B" End If If RadioButton12.Checked = True Then hla4 = "C" End If '==================================== If RadioButton13.Checked = True Then hla5 = "A" End If If RadioButton14.Checked = True Then hla5 = "B" End If If RadioButton15.Checked = True Then hla5 = "C" End If '==================================== If RadioButton16.Checked = True Then hla6 = "A" End If If RadioButton17.Checked = True Then hla6 = "B" End If If RadioButton18.Checked = True Then hla6 = "C" End If '=====B L O O D================ Dim group As String If RadioButton19.Checked = True Then group = "APLUS" End If If RadioButton20.Checked = True Then group = "AMINUS" End If If RadioButton21.Checked = True Then group = "BPLUS" End If If RadioButton22.Checked = True Then

group = "BMINUS" End If If RadioButton23.Checked = True Then group = "AB" End If If RadioButton24.Checked = True Then group = "O" End If If RadioButton24.Checked = True Then group = "OPLUS" End If sql = sql + hla1 & "','" sql = sql + hla2 & "','" sql = sql + hla3 & "','" sql = sql + hla4 & "','" sql = sql + hla5 & "','" sql = sql + hla6 & "','" sql = sql + group & "')" comm = New OleDbCommand(sql, conn) comm.ExecuteNonQuery() conn.Close() MsgBox("INSERTED SUCCESSFULLY") End Sub Protected Sub Button2_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button2.Click Response.Redirect("first.aspx") End Sub Protected Sub Button3_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button3.Click TextBox1.Text = "" TextBox2.Text = "" TextBox3.Text = "" TextBox4.Text = "" TextBox5.Text = "" TextBox6.Text = "" TextBox7.Text = "" TextBox8.Text = "" TextBox10.Text = "" TextBox11.Text = "" RadioButton1.Checked RadioButton2.Checked RadioButton3.Checked RadioButton4.Checked RadioButton5.Checked RadioButton6.Checked RadioButton7.Checked RadioButton8.Checked RadioButton9.Checked

= = = = = = = = =

False False False False False False False False False

RadioButton10.Checked = False End Sub End Class DONOR REGISTRATION: Imports System.Data.OleDb Partial Class Default2 Inherits System.Web.UI.Page Dim conn As New OleDbConnection Dim connread As New OleDbConnection Dim comm As New OleDbCommand Dim commread As New OleDbCommand Dim reading As OleDbDataReader Dim sql As String Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load conn = New OleDbConnection("Provider=Microsoft.Jet.Oledb.4.0;Data Source=C:\Users\MAYAVATHI\Documents\umbilical.mdb") End Sub Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click conn.Open() Dim sex As String sql = "insert into donor values('" sql = sql + TextBox1.Text & "','" sql = sql + TextBox2.Text & "','" If (CheckBox1.Checked = True) Then sex = "Male" Else sex = "FeMale" End If sql = sql = sql = sql = sql = sql = sql = sql = sql = sql = sql = sql = sql = sql sql sql sql sql sql sql sql sql sql sql sql sql + + + + + + + + + + + + + sex & "','" TextBox3.Text & "','" ListBox1.Text & "','" ListBox2.Text & "','" TextBox4.Text & "','" TextBox5.Text & "','" TextBox6.Text & "','" TextBox7.Text & "','" ListBox3.Text & "','" TextBox11.Text & "','" TextBox8.Text & "','" TextBox10.Text & "','" ListBox4.Text & "','"

sql = sql + ListBox5.Text & "','" '==================================== Dim hla1 As String Dim hla2 As String Dim hla3 As String Dim hla4 As String Dim hla5 As String Dim hla6 As String '======================================= If RadioButton1.Checked = True Then hla1 = "A" End If If RadioButton2.Checked = True Then hla1 = "B" End If If RadioButton3.Checked = True Then hla1 = "C" End If '====================================== If RadioButton4.Checked = True Then hla2 = "A" End If If RadioButton5.Checked = True Then hla2 = "B" End If If RadioButton6.Checked = True Then hla2 = "C" End If '==================================== If RadioButton7.Checked = True Then hla3 = "A" End If If RadioButton8.Checked = True Then hla3 = "B" End If If RadioButton9.Checked = True Then hla3 = "C" End If '==================================== If RadioButton10.Checked = True Then hla4 = "A" End If If RadioButton11.Checked = True Then hla4 = "B" End If If RadioButton12.Checked = True Then hla4 = "C" End If '==================================== If RadioButton13.Checked = True Then hla5 = "A"

End If If RadioButton14.Checked = True Then hla5 = "B" End If If RadioButton15.Checked = True Then hla5 = "C" End If '==================================== If RadioButton16.Checked = True Then hla6 = "A" End If If RadioButton17.Checked = True Then hla6 = "B" End If If RadioButton18.Checked = True Then hla6 = "C" End If '=====B L O O D================ Dim group As String If RadioButton19.Checked = True Then group = "APLUS" End If If RadioButton20.Checked = True Then group = "AMINUS" End If If RadioButton21.Checked = True Then group = "BPLUS" End If If RadioButton22.Checked = True Then group = "BMINUS" End If If RadioButton23.Checked = True Then group = "AB" End If If RadioButton24.Checked = True Then group = "O" End If If RadioButton24.Checked = True Then group = "OPLUS" End If sql = sql + hla1 & "','" sql = sql + hla2 & "','" sql = sql + hla3 & "','" sql = sql + hla4 & "','" sql = sql + hla5 & "','" sql = sql + hla6 & "','" sql = sql + group & "')" comm = New OleDbCommand(sql, conn) comm.ExecuteNonQuery() conn.Close() MsgBox("INSERTED SUCCESSFULLY")

End Sub Protected Sub Button2_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button2.Click Response.Redirect("FIRST.ASPX") End Sub Protected Sub Button3_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button3.Click TextBox1.Text = "" TextBox2.Text = "" TextBox3.Text = "" TextBox4.Text = "" TextBox5.Text = "" TextBox6.Text = "" TextBox7.Text = "" TextBox8.Text = "" TextBox10.Text = "" TextBox11.Text = "" RadioButton1.Checked = False RadioButton2.Checked = False RadioButton3.Checked = False RadioButton4.Checked = False RadioButton5.Checked = False RadioButton6.Checked = False RadioButton7.Checked = False RadioButton8.Checked = False RadioButton9.Checked = False RadioButton10.Checked = False End Sub End Class MATCHING DETAILS: Imports System.Data.OleDb Partial Class Default2 Inherits System.Web.UI.Page Dim conn As New OleDbConnection Dim connread As New OleDbConnection Dim comm As New OleDbCommand Dim commread As New OleDbCommand Dim reading As OleDbDataReader Dim sql As String Dim regi_match As String Dim pre As Integer Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load

conn = New OleDbConnection("Provider=Microsoft.Jet.Oledb.4.0;Data Source=C:\Users\MAYAVATHI\Documents\umbilical.mdb") Label1.Text = "" End Sub Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click conn.Open() sql = "select * from acceptor where regno = '" & TextBox1.Text & "'" MsgBox(sql) comm = New OleDbCommand(sql, conn) reading = comm.ExecuteReader() If reading.Read Then MsgBox("Reading" + reading.GetString(0)) TextBox1.Text = reading.GetString(0) TextBox2.Text = reading.GetString(1) TextBox3.Text = reading.GetString(2) TextBox4.Text = reading.GetString(3) TextBox5.Text = reading.GetString(4) TextBox6.Text = reading.GetString(5) TextBox7.Text = reading.GetString(6) TextBox8.Text = reading.GetString(7) TextBox9.Text = reading.GetString(8) TextBox10.Text = reading.GetString(9) TextBox11.Text = reading.GetString(10) End If conn.Close() Dim Dim Dim Dim Dim Dim Dim HA1 As String HA2 As String HA3 As String HA4 As String HA5 As String HA6 As String BA As String

HA1 = TextBox33.Text HA2 = TextBox34.Text HA3 = TextBox35.Text HA4 = TextBox36.Text HA5 = TextBox37.Text HA6 = TextBox38.Text BA = TextBox39.Text conn.Open() sql = "select * from donor" where TextBox1.Text & "'" comm = New OleDbCommand(sql, conn) reading = comm.ExecuteReader() regno = '" &

If reading.Read Then TextBox17.Text = TextBox18.Text = TextBox19.Text = TextBox20.Text = TextBox21.Text = TextBox22.Text = TextBox23.Text = TextBox24.Text = TextBox25.Text = End If conn.Close()

reading.GetString(0) reading.GetString(1) reading.GetString(2) reading.GetString(3) reading.GetString(4) reading.GetString(5) reading.GetString(6) reading.GetString(7) reading.GetString(8)

Dim MAX As Integer Dim ACTUAL As Integer Dim flag_out As Integer Dim previous As Integer previous = 0 MAX = 6 ACTUAL = 0 Dim HD1 As String Dim HD2 As String Dim HD3 As String Dim HD4 As String Dim HD5 As String Dim HD6 As String Dim BD As String conn.Open() sql = "select * from donor" 'where TextBox1.Text & "'" comm = New OleDbCommand(sql, conn) reading = comm.ExecuteReader() Dim regi As String While (reading.Read) regi = reading.GetString(0) HD1 = reading.GetString(16) HD2 = reading.GetString(17) HD3 = reading.GetString(18) HD4 = reading.GetString(19) HD5 = reading.GetString(20) HD6 = reading.GetString(21) If (HA1 = HD1) Then ACTUAL = ACTUAL + 1 End If If (HA2 = HD2) Then ACTUAL = ACTUAL + 1 End If If (HA3 = HD3) Then ACTUAL = ACTUAL + 1 End If

regno = '" &

If (HA4 = HD4) Then ACTUAL = ACTUAL + 1 End If If (HA5 = HD5) Then ACTUAL = ACTUAL + 1 End If If (HA6 = HD6) Then ACTUAL = ACTUAL + 1 End If If ((ACTUAL > 0) And (ACTUAL >= previous)) Then regi_match = regi previous = ACTUAL End If ACTUAL = 0 End While pre = ACTUAL conn.Close() '================================================ ====================================== sql = "select * from donor where regno = '" & regi_match & "'" comm = New OleDbCommand(sql, conn) conn.Open() reading = comm.ExecuteReader() If reading.Read Then TextBox17.Text = reading.GetString(0) TextBox18.Text = reading.GetString(1) TextBox19.Text = reading.GetString(2) TextBox20.Text = reading.GetString(3) TextBox21.Text = reading.GetString(4) TextBox22.Text = reading.GetString(5) TextBox23.Text = reading.GetString(6) TextBox24.Text = reading.GetString(7) TextBox25.Text = reading.GetString(8) TextBox26.Text = reading.GetString(9) TextBox27.Text = reading.GetString(10) End If Label1.Text = " The maximum Possible match is displayed, If interested press save!!" conn.Close() '================================================ ===================================== End Sub Protected Sub Button3_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button3.Click conn.Open() sql = "insert into selection values('" sql = sql + TextBox1.Text & "','"

sql = sql + sql = sql + sql = sql + sql = sql + sql = sql + sql = sql + sql = sql + sql = sql + sql = sql + MsgBox(sql)

TextBox2.Text & "','" TextBox17.Text & "','" TextBox18.Text & "','" TextBox33.Text & "','" TextBox34.Text & "','" TextBox35.Text & "','" TextBox36.Text & "','" TextBox37.Text & "','" TextBox38.Text & "','"

comm = New OleDbCommand(sql, conn) comm.ExecuteNonQuery() conn.Close() End Sub Protected Sub TextBox14_TextChanged(ByVal sender As Object, ByVal e As System.EventArgs) Handles TextBox14.TextChanged End Sub Protected Sub Button2_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button2.Click Response.Redirect("FIRST.ASPX") End Sub Protected Sub Button4_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button4.Click TextBox1.Text = "" TextBox2.Text = "" TextBox3.Text = "" TextBox4.Text = "" TextBox5.Text = "" TextBox6.Text = "" TextBox7.Text = "" TextBox8.Text = "" TextBox9.Text = "" TextBox10.Text = "" End Sub End Class

ACCEPTOR REPORT:

Imports Imports Imports Imports Imports

System.Data.OleDb System.Data.DataColumn System.Data.DataRow System.Data.DataTable System.Data

Partial Class report Inherits System.Web.UI.Page Dim conn As New OleDbConnection Dim comm As New OleDbCommand Dim commread As New OleDbCommand Dim reading As OleDbDataReader Dim sql As String Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load conn = New OleDbConnection("Provider=Microsoft.Jet.Oledb.4.0;Data Source=C:\Users\MAYAVATHI\Documents\umbilical.mdb") End Sub Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click Dim MYDT As New DataTable Dim MyRow As DataRow ====================================================== ==================== Dim Regi As String Dim Name As String Dim sex As String Dim City As String Dim Email As String Dim HLA_A As String Dim HLA_B As String Dim HLA_C As String Dim HLA_DR As String Dim HLA_DQ As String Dim HLA_DD As String Dim blod As String Dim drcode As String Dim drname As String '-------------------------------------------------------------------------MYDT.Columns.Add(New DataColumn("Regi No.", GetType(String))) MYDT.Columns.Add(New DataColumn("Name", GetType(String))) MYDT.Columns.Add(New DataColumn("Sex .", GetType(String)))

MYDT.Columns.Add(New DataColumn("City", GetType(String))) MYDT.Columns.Add(New DataColumn("Email", GetType(String))) MYDT.Columns.Add(New DataColumn("HLA-A", GetType(String))) MYDT.Columns.Add(New DataColumn("HLA-B", GetType(String))) MYDT.Columns.Add(New DataColumn("HLA-C", GetType(String))) MYDT.Columns.Add(New DataColumn("HLA-DR", GetType(String))) MYDT.Columns.Add(New DataColumn("HLA-DQ", GetType(String))) MYDT.Columns.Add(New DataColumn("HLA-DD", GetType(String))) MYDT.Columns.Add(New DataColumn("BLOOD GR", GetType(String))) MYDT.Columns.Add(New DataColumn("DR .", GetType(String))) MYDT.Columns.Add(New DataColumn("DR NAME", GetType(String))) conn.Open() sql = "select * from acceptor" ' where REGNO='" & TextBox1.Text + "'" comm = New OleDbCommand(sql, conn) reading = comm.ExecuteReader() While (reading.Read) Regi = reading.GetString(0) Name = reading.GetString(1) sex = reading.GetString(2) City = reading.GetString(4) Email = reading.GetString(7) HLA_A = reading.GetString(16) HLA_B = reading.GetString(17) HLA_C = reading.GetString(18) HLA_DR = reading.GetString(19) HLA_DQ = reading.GetString(20) HLA_DD = reading.GetString(21) blod = reading.GetString(22) drcode = reading.GetString(8) drname = reading.GetString(9) MyRow = MYDT.NewRow() MyRow(0) = Regi MyRow(1) = Name MyRow(2) = sex MyRow(3) = City MyRow(4) = Email MyRow(5) = HLA_A MyRow(6) = HLA_B MyRow(7) = HLA_C

MyRow(8) = HLA_DR MyRow(9) = HLA_DQ MyRow(10) = HLA_DD MyRow(11) = blod MyRow(12) = drcode MyRow(13) = drname MYDT.Rows.Add(MyRow) End While dg1.DataSource = MYDT dg1.DataBind() conn.Close() End Sub End Class DONOR REPORT: Imports Imports Imports Imports Imports System.Data.OleDb System.Data.DataColumn System.Data.DataRow System.Data.DataTable System.Data

Partial Class report Inherits System.Web.UI.Page Dim conn As New OleDbConnection Dim comm As New OleDbCommand Dim commread As New OleDbCommand Dim reading As OleDbDataReader Dim sql As String Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load conn = New OleDbConnection("Provider=Microsoft.Jet.Oledb.4.0;Data Source=C:\Users\MAYAVATHI\Documents\umbilical.mdb") End Sub Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click Dim MYDT As New DataTable Dim MyRow As DataRow Dim Regi As String Dim Name As String Dim sex As String Dim City As String Dim Email As String Dim HLA_A As String Dim HLA_B As String Dim HLA_C As String Dim HLA_DR As String Dim HLA_DQ As String Dim HLA_DD As String

Dim blod As String Dim drcode As String Dim drname As String '-------------------------------------------------------------------------MYDT.Columns.Add(New DataColumn("Regi No.", GetType(String))) MYDT.Columns.Add(New DataColumn("Name", GetType(String))) MYDT.Columns.Add(New DataColumn("Sex .", GetType(String))) MYDT.Columns.Add(New DataColumn("City", GetType(String))) MYDT.Columns.Add(New DataColumn("Email", GetType(String))) MYDT.Columns.Add(New DataColumn("HLA-A", GetType(String))) MYDT.Columns.Add(New DataColumn("HLA-B", GetType(String))) MYDT.Columns.Add(New DataColumn("HLA-C", GetType(String))) MYDT.Columns.Add(New DataColumn("HLA-DR", GetType(String))) MYDT.Columns.Add(New DataColumn("HLA-DQ", GetType(String))) MYDT.Columns.Add(New DataColumn("HLA-DD", GetType(String))) MYDT.Columns.Add(New DataColumn("BLOOD GR", GetType(String))) MYDT.Columns.Add(New DataColumn("DR .", GetType(String))) MYDT.Columns.Add(New DataColumn("DR NAME", GetType(String))) conn.Open() sql = "select * from DONOR" ' where REGNO='" & TextBox1.Text + "'" comm = New OleDbCommand(sql, conn) reading = comm.ExecuteReader() While (reading.Read) Regi = reading.GetString(0) Name = reading.GetString(1) sex = reading.GetString(2) City = reading.GetString(4) Email = reading.GetString(7) HLA_A = reading.GetString(16) HLA_B = reading.GetString(17) HLA_C = reading.GetString(18) HLA_DR = reading.GetString(19) HLA_DQ = reading.GetString(20)

HLA_DD = reading.GetString(21) blod = reading.GetString(22) drcode = reading.GetString(8) drname = reading.GetString(9) MyRow = MYDT.NewRow() MyRow(0) = Regi MyRow(1) = Name MyRow(2) = sex MyRow(3) = City MyRow(4) = Email MyRow(5) = HLA_A MyRow(6) = HLA_B MyRow(7) = HLA_C MyRow(8) = HLA_DR MyRow(9) = HLA_DQ MyRow(10) = HLA_DD MyRow(11) = blod MyRow(12) = drcode MyRow(13) = drname MYDT.Rows.Add(MyRow) End While dg1.DataSource = MYDT dg1.DataBind() conn.Close() End Sub End Class

MATCHING REPORT: Imports System.Data.OleDb Partial Class MATCHING Inherits System.Web.UI.Page Dim conn As New OleDbConnection Dim connread As New OleDbConnection Dim comm As New OleDbCommand Dim commread As New OleDbCommand Dim reading As OleDbDataReader Dim sql As String Dim regi_match As String Protected Sub Button2_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button2.Click conn.Open() sql = "select * from selection where acceptorcode = '" & TextBox2.Text & "'" MsgBox(sql) comm = New OleDbCommand(sql, conn) reading = comm.ExecuteReader() If reading.Read Then

MsgBox("Reading" + reading.GetString(0)) Label1.Text = reading.GetString(0) Label2.Text = reading.GetString(1) Label3.Text = reading.GetString(2) Label4.Text = reading.GetString(3) Label5.Text = reading.GetString(4) Label6.Text = reading.GetString(5) Label7.Text = reading.GetString(6) Label8.Text = reading.GetString(7) Label9.Text = reading.GetString(8) Label10.Text = reading.GetString(9) Label11.Text = reading.GetString(10) Label12.Text = reading.GetString(11) End If conn.Close() End Sub Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load conn = New OleDbConnection("Provider=Microsoft.Jet.Oledb.4.0;Data Source=C:\Users\MAYAVATHI\Documents\umbilical.mdb") End Sub Protected Sub Button3_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button3.Click Response.Redirect("FIRST.ASPX") End Sub Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click Response.Redirect("USERRMENUL.ASPX") End Sub End Class

CONCLUSION: Thus the coding for Bio-Informatics based on Umbilicalcord was written successfully.

B.SCREEN SHOTS

INTRODUCTION:

MAIN MENU:

ADMIN MENU:

LOGIN FORM:

ADMIN REGISTRATIONS:

ADMIN NEW FORM:

ADMIN UPDATE:

ACCEPTOR REGISTRATION:

DONOR REGISTRATION:

MATCHING REPORT:

CONCLUSION: Thus the Screen Shots of the Bio-informatics was shown successfully.

C. PROCEDURE FOR GENERATING UML DIAGRAMS USING RATIONAL ROSE

How to constructs simple UML class with Rose Open Rational Rose Enterprise Edition. Cancel the window that offers all the Java, VB etc frameworks.

Open Logical View and double click on Main, which is a class diagram window. First of all save your model as Circle.mdl in a folder called UML exercises in your network account. Then click on the class icon in the toolbar, and next click somewhere on the class diagram window. Type in the class name Circle straightaway, to get something like:

Adding attributes to Circle In the browser window, right click on the Circle class and select New/Attribute from the popup menu. Key in the attribute name there and then, namely: r.

Another way to create attributes Right click on the circle class in the class diagram main (not the browser window), and select New Attribute. Type in the name x, to get:

Third way to add an attribute Right click on the circle class either in the browser or class diagram windows, and select Open Specification to get:

Select the Attributes tab of the Circle specification window; right click for the popup menu on the clear area where the attributes are listed, select Insert and key in the attribute name y, to get:

Adding an Operations or MethodsWhile the specification window is still open, select the Operations tab, right click the clear area and again select Insert and key in the method name area. Then close the specification window. Should have been like:

Second and third ways to create a new method Same approach as in creating the first 2 attributes r and x above. Either right clicks on the circle icon in the browser window, selecting New / Operation; or right clicks on the circle class in the class diagram window and select New Operation. Either way it amounts to the same thing. Add methods: perimeter, set Radius and set Origin to get:

Adding Types to the Attributes You will next want to specify the types or signatures of the attributes. One way to do this is: right click on the r attribute of Circle in the browser window and select Open Specification. This open the specification of r as opposed to that of Circle. In the Type textbox, key in int (alternatively, it may be available in the drop down choice menu). Click Apply to get:

Another way. Setting the Type for x Right click on the Circle class and select Open Specification. Then select Attributes tab, select the x attribute, click once or twice on its Type field as indicated in diagram until the drop down choice box appears, and key in int to get:

Third way. Setting the Type for attribute y.

In the same window, right click on y, select Specification.. And key int into the Type textbox to get Close various specification windows then.

Adding Signatures to the Methods First right click on the class icon in the class diagram window, enable Options/Show Operation Signature, making sure that operation signature or typing is enabled. Then open the Circle class specification, select Operations and give a return type of double to area() and perimeter() methods as in:

We next want to add arguments as well as return type to the methods. Open the specification for set Radius () operation. You can get at this in couple of ways. In the General tab, set the return type to void. Then switch to the Detail tab, and insert an argument (or parameter) named red of type int to get:

Do something similar for the set Origin () method, giving it 2 parameters and 2 default values of 0 to get:

Finally save your Rose model as Circle.mdl in a folder called UML Exercises