case tools lab

STUDY OF CASE TOOLS

VISUAL MODELLING:

Visual modeling is a way of thinking and analyzing about problems using models around real world ideas. A modeling language must include,

Model elements Notations Guidelines

Visual modeling approach is used since a system cannot be comprehended to its entirety. Benefits of visual modeling includes,

Clarity Familiarity Maintenance simplification

UML: Unified modeling language(UML)is a communication standard of visual modeling. The UML provides a smooth transition between the business domain and the computer domain. UML is an object oriented language for specifying, constructing, visualizing and documenting the software system and its components.UML is a graphical language with a set of rules and semantics.UML is a combination of

Data Modeling Business Modeling Object Modeling Component Modeling

UML DIAGRAMS:UML defines graphical diagrams such as,

Class diagram Use case diagram Behavior diagrams Interaction Diagrams

o Sequence Diagramso Collaboration Diagrams

State Chart Diagrams Activity Diagram Implementation Diagrams

o Component Diagramo Deployment Diagrams

USE-CASE DIAGRAMS:Use-case diagrams graphically depict system behavior (use cases).These diagrams present a high level view of how the system is used as viewed from an outsider’s (actor’s) perspective. A use-case diagram may depict all or some of the use cases of a system.A use-case diagram can contain:

Actor’s (“things” outside the system) Use cases(system boundaries identifying what the system should do) Interactions or relationships between actors and use cases in the system including the

associations, dependencies and generalizations.USE CASE: Use case is scenario for understanding system requirements. Every single use case must describe one main flow of events.

ACTOR

Actors represent system users, who provide input to and receive information from the system. An actor is a stereotype of a class and is depicted as a ”stickman” on a use-case diagram. The name of the actor is displayed below the icon. Additional information about the actor can be viewed in the use-case specification.RELATIONSHIPS

You can add relationships to the diagram to show interactions between actors and use cases. Association relationships can be drawn from an actor to a use case. The generalize relationship can be drawn between actors.

Relationships between use case diagrams include Communication Uses Extend

FLOW OF EVENTS A flow of events is a sequence of transaction (or events) performed by the system. They typically contain very detailed information, written in terms of what the system should do, not how accomplish the task.A flow of events should include:

When and how the use case starts and ends Use case/actor interactions Data needed by the use case Normal sequence of events for the use case Alternate or exception flows

USE-CASE REALIZATIONS (SCENARIOS)A use case realization is a graphic sequence of events, also referred to as a scenario or

an instance of a use case. these realization or scenarios are depicted in either a sequence or collaboration diagram.

The two most common scenarios are the typical(or primary)scenario, where all is well and the exception(secondary)scenario, which address the deviations. The exception scenario address the “what if ?” elements of the use case.

ACTIVITY DIAGRAM:An activity represents the performance of task or duty in a workflow. it may also

represent the execution of a statement in a procedure. An activity diagram is activity centric. Transitions connect activities with other model elements and object flows connect activities with objects.

The activity icon appears as a rectangle with rounded ends with name (take order and process order) and a compartment for actions.

The name of an activity must be unique and should declare the activity’s purpose. All activity icons with the name on an activity diagram represent the same activity. You must add actions through the action specification.

Action on activities can occur of four times: On entry On exit Do On event

SEQUENCE DIAGRAMS: Sequence diagram is a graphical view of a scenario that shows object interaction in a

time-based sequence. Sequence diagrams establish the roles objects. Sequence diagrams are normally associated with use cases. Sequence diagrams are closely related to collaboration diagrams and both are alternate representation of an interaction. A sequence diagram has two dimensions: typically, vertical placement represents time and horizontal placement represents different objects. COLLABORATION DIAGRAMS:

A collaboration diagram is an interaction diagram that shows the order of messages that implement an operation or a transaction. Collaboration diagrams show objects, their links, and their messages.

They can also contain simple class instances and class utility instances. Each collaboration diagram provides a view of the interactions or structural relationships that occur between objects and object-like entities in the current model.

SCENARIOS: Scenarios show the different sequence of interaction between actors and system. A

Scenario is an instance of a use case; it is an outline of events that occur during system execution. A scenario can be expressed in text or sequence of steps.

STATE CHART DIAGRAMS:State chart diagrams model the dynamic behavior of individual classes or any other kind

of objects. They show the sequence of states that an object goes through, the events that cause a transition from one state to another, and the actions that result from a state change.

State chart diagrams are state centric; statement diagram is used to model the discrete stages of an object’s lifetime. Each state represents a named condition during the life of an object during which it satisfies some condition or waits for some events. A state chart diagram typically contains one start state and multiple end states. Transitions connect the various states on the diagram. Decisions, synchronizations, and activities may also appear on state chart diagrams.

STEREOTYPES: Stereotype represents built-in extensibility mechanism for UML.Stereotype is new class of modeling element introduced during modeling. General

presentation of stereotype is string with guillemots. Various form of stereotype is

Class stereotypes Association stereotypes Dependency stereotypes Component stereotypes

RATIONAL ROSE:Rational rose is a tool for understanding, analyze and designing of software intensive

system. Model in rational rose is constructed using views and diagrams

The views used are, Use case view Logical view Component view Development view Implementation view Process view

Rational Rose is a GUI environment containing, Browser window Diagram window Diagram window Documentation window Log window Options window

EX.NO: EMPLOYEE PAYROLL SYSTEMDATE:

AIM: To solve Employee payroll System problem using case tools for planning cost estimation,modelling the requirements and configuration management.

SCOPE:

The following subsection describes a scope of a Employee payroll System in terms of its organization and applicable documents.

AUDIENCE:

The intended users are the people responsible for implementing the Employee payroll System.

ORGANIZATION:

The document describes the Employee payroll System requirements in terms of system requirements executive summary analysis and design diagram.

APPLICABLE DOCUMENT:

The following document provide information necessary to understand the document.

SYSTEM REQUIREMENT SPECIFICATION(SRS):

The following subsection describes the Employee payroll System requirement specification interms of problem statement feasibility study.

PROBLEM STATEMENT : The Employee submits the application for creating a new account.The following data’s are needed for an employee to create a record Employee name, Designation, Rate per hour, No. Of working hours, No of days absent, SSS, PAG-IBIG, Phil health, Daily net pay, Total net pay. The system is Designed and implemented using Case Tools.

VERB PARSING:

The payroll system are : Login Entering the employee details Entering the salary details and the total no of working hours Processing Generation of pay slip Viewing details Giving salary

Login

Here the one user is logged in with his name and correct passwords, if the entered name or password does not match with the original password then an appropriate error message is sent to them.

Entering the employee details

The employee has to provide his details.

Processing

Processing is done by the database, it calculates the Daily net pay. Finally the net pay is calculated by subtracting SSS, PAGI-BIG, PHIL HEALTH.

SALARY CALCULATION:

The pay slip is generated by the database after finding the net pay, this slip consists of the employee details and his salary details in brief.

CLASS DIAGRAM:

emp details

namestaff nodeptaddressdojpf

checking()

basicpay

ugpg

calc bp()11

total pay

basicpaydarsianame2

caltp()

11

lop

clbasic paydarsia

callop()

11

grosssal

loptp

calgrsal()11

net sal

gross paypf

calnetpay()111 1 1 1 1 1 1 1 1 1

USE CASE DIAGRAM:

Daily net pay= working hours*rate per hour

Total Net Pay=daily net pay-(SSS-PAGIBIG-PHIL HEALTH)

COLLOBORATION DIAGRAM:

DB

Generating pay slip

Employee

name

designation

LOGIN

Entering details

View slip

LOGOUT

employee emp details basic pay

totalpay

lop

grosssal

netsalsystem

8: netsal=grosssal if no pf

1: retrieve emp details 2: basic pay calc based on ug pg

3: add basic,DA,RSIA

4: if lop not available gs=tp

5: calculation of lop if lop available

6: grosssal=tp-lop

7: netsal calc by deducting pf if any

9: update details

10: intimate the employee

SEQUENTIAL DIAGRAM

employee emp details basic pay totalpay lop grosssal netsal system

retrieve emp details

basic pay calc based on ug pg

add basic,DA,RSIA

if lop not available gs=tp

calculation of lop if lop available

grosssal=tp-lop

netsal calc by deducting pf if any

netsal=grosssal if no pf

update details

intimate the employee

FORM DESIGN:

SOURCE CODE:

FRONT – END (VB 6.0)START PROGRAMS MICROSOFT VISUAL STUDIO 6.0 MICROSOFT VISUAL

BASIC 6.0 OPEN STANDARD EXEFORM 1:Dim con As New ADODB.ConnectionDim rs As New ADODB.RecordsetPrivate Sub cmdOK_Click()If txtUserName.Text = rs.Fields(0) And txtPassword.Text = rs.Fields(1) ThenMDIForm1.ShowMe.HideEnd IfEnd SubPrivate Sub Command1_Click ()Frame1.Visible = TrueEnd SubPrivate Sub Command2_Click ()rs.AddNewrs.Fields(0) = Text1.Textrs.Fields(1) = Text2.Textrs.UpdateMsgBox "Save"Frame1.Visible = FalseEnd SubPrivate Sub Command3_Click ()Form4.ShowMe.HideEnd SubPrivate Sub Form_Activate()Set con = New ADODB.ConnectionSet rs = New ADODB.Recordsetcon.Open "Provider=Microsoft.Jet.OLEDB.4.0; Data Source=" & App.Path & " \pas.mdb;Persist Security Info=False"rs.Open "pas", con, adOpenDynamic, adLockOptimisticFrame1.Visible = FalseText1.Text = ""Text2.Text = ""End Sub

FORM 2: Private Sub Command1_Click ()rs.AddNewrs.Fields(0) = Text1.TextIf Option1 = True And Option2 = False Then

rs.Fields(1) = Option1.Caption Else rs.Fields(1) = Option2.Caption End Ifrs.Fields(2) = Text2.TextText3.Text = rs.Fields(3)rs.Fields(4) = Text4.Textrs.Fields(5) = Text5.Textrs.UpdateMsgBox "added"End SubPrivate Sub Command2_Click()MDIForm1.ShowEnd SubPrivate Sub Command3_Click()Text1.Text = ""Text2.Text = ""Text3.Text = ""Text4.Text = ""Text5.Text = ""End SubPrivate Sub Form_Activate()Set con = New ADODB.ConnectionSet rs = New ADODB.Recordsetcon.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.Path & "\db2.mdb;Persist Security Info=False"rs.Open "personal", con, adOpenDynamic, adLockOptimisticMsgBox "connection successfully"End Sub FORM 3: Dim con As New ADODB.ConnectionDim rs As New ADODB.RecordsetPrivate Sub cmdexit_Click()EndEnd SubPrivate Sub Command1_Click()Text2.Text = ""Text1.Text = ""Text3.Text = ""Combo2.Text = ""

Combo1.Text = ""Combo3.Text = ""

rs.Fields.Refreshrs.UpdateIf (Text2.Text = "" And Text1.Text = "" And Text3.Text = "" And Combo2.Text = "" And Combo1.Text = "" And Combo3.Text = "") ThenMsgBox "please search your details and modify your details"Elsers.MoveFirstWhile Not rs.EOFIf Text2.Text = rs.Fields(1) ThenMsgBox "ID already exist"Exit SubElsers.MoveNext End IfWendrs.AddNewrs.Fields(0) = Text1.Text rs.Fields(1) = Text2.Textrs.Fields(2) = Text3.Textrs.Fields(3) = Combo1.Textrs.Fields(4) = Combo2.Textrs.Fields(5) = Combo3.Textrs.Fields(6) = Val(Combo3.Text + (Combo3.Text * 12 / 100))rs.UpdateMsgBox "added"Text2.Text = ""Text1.Text = ""Text3.Text = ""Combo2.Text = ""Combo1.Text = ""Combo3.Text = ""End IfEnd SubPrivate Sub Command4_Click()If rs.EOF = False Thenrs.MoveLastText1.Text = rs.Fields(0)Text2.Text = rs.Fields(1)Text3.Text = rs.Fields(2)Combo1.Text = rs.Fields(3)Combo2.Text = rs.Fields(4)

Combo3.Text = rs.Fields(5)

MsgBox "last"ElseMsgBox "no data"End IfEnd SubPrivate Sub Command5_Click()If (rs.BOF = False) And (rs.BOF = True) Thenrs.MoveFirst'If rs.BOF = False ThenText1.Text = rs.Fields(0)Text2.Text = rs.Fields(1)Text3.Text = rs.Fields(2)Combo1.Text = rs.Fields(3)Combo2.Text = rs.Fields(4)Combo3.Text = rs.Fields(5)MsgBox "first"ElseMsgBox "no data"End IfEnd SubPrivate Sub Command2_Click()If (Text2.Text = "" And Text1.Text = "" And Text3.Text = "" And Combo2.Text = "" And Combo1.Text = "" And Combo3.Text = "") ThenMsgBox "please search your details and modify your details"Elsers.Fields(0) = Text1.Text rs.Fields(1) = Text2.Textrs.Fields(2) = Text3.Textrs.Fields(3) = Combo1.Textrs.Fields(4) = Combo2.Textrs.Fields(5) = Combo3.Textrs.Fields(6) = Val(Combo3.Text + (Combo3.Text * 12 / 100))rs.UpdateMsgBox "SUCCESSFULLY"Text2.Text = ""Text1.Text = ""Text3.Text = ""Combo2.Text = ""Combo1.Text = ""Combo3.Text = ""

End IfEnd Sub

Private Sub Command3_Click()'Dim i As Integer'i = 1'For i = 1 To rs.Fields.Count'If (rs.Fields(1) = Text2.Text) Then'If (rs.BOF = False) And (rs.EOF = False) ThenWhile Not rs.EOFIf Trim(UCase(rs.Fields(1))) = Text2.Text ThenText1.Text = rs.Fields(0)Text2.Text = rs.Fields(1)Text3.Text = rs.Fields(2)Combo2.Text = rs.Fields(3)Combo1.Text = rs.Fields(4)Combo3.Text = rs.Fields(5)Exit SubElsers.MoveNextEnd IfWendrs.DeleteMsgBox ("Record Deleted")MsgBox ("no data deleted")'If (rs.BOF = True) And (rs.EOF = True) Then'MsgBox ("no data found")'End If'Else'MsgBox ("no data deleted")'End If'Next iEnd SubPrivate Sub Command6_Click()Command2.Enabled = Trueemployeeid = InputBox("ENTER THE ID")If employeeid = "" ThenExit SubEnd Ifrs.MoveFirstWhile Not rs.EOFIf Trim(UCase(rs.Fields(1))) = Trim(UCase(employeeid)) ThenText1.Text = rs.Fields(0)

Text2.Text = rs.Fields(1)

Text3.Text = rs.Fields(2)Combo2.Text = rs.Fields(3)Combo1.Text = rs.Fields(4)Combo3.Text = rs.Fields(5)Exit SubEnd Ifrs.MoveNextWendMsgBox "No such Record", vbCriticalIf rs.BOF = True Then'Text1.Text = 1Elsers.MoveLast'Text1.Text = Val(rs.Fields(0)) + 1End IfEnd SubPrivate Sub Command7_Click()Text2.Text = ""Text1.Text = ""Text3.Text = ""Combo2.Text = ""Combo1.Text = ""Combo3.Text = ""End SubPrivate Sub Command8_Click()MDIForm1.ShowEnd SubPrivate Sub Form_Activate()Set con = New ADODB.ConnectionSet rs = New ADODB.Recordsetcon.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.Path & "\db1.mdb;Persist Security Info=False"rs.Open "employee", con, adOpenDynamic, adLockOptimisticMsgBox "connection successfully"Text1.SetFocusText2.Text = ""Text1.Text = ""Text3.Text = ""Combo2.Text = ""Combo1.Text = ""

Combo3.Text = ""End Sub

BACK – END DESIGN:

OUTPUT SCREEN:

CONCLUSION Thus the system is developed using object oriented programming approach with the

help of CASE tools.

EX.NO: TEXT EDITORDATE:

AIM: To solve Text Editor problem using case tools for planning cost estimation,modelling the requirements and configuration management.

SCOPE:

The following subsection describes a scope of a new text editor in terms of its organization and applicable documents.

AUDIENCE:

The intended users are the people responsible for implementing the new text editor.

ORGANIZATION:

The document describes the new text editor requirements in terms of system requirements executive summary analysis and design diagram.

APPLICABLE DOCUMENT:

The following document provide information necessary to understand the document.

SYSTEM REQUIREMENT SPECIFICATION(SRS):

The following subsection describes the new text editor requirement system requirement system requirement system requirement specification interms of problem statement feasibility study.

PROBLEM STATEMENT : The new text editor system should allow users &administrator to login for creating a new documents modifying files .the new text editor should allow the users to enter their name &enter the password then perform various operations.in the file users open a document,open a already existing file to another file .help is used to search and know the information about related to text editor by the user edit by the user. In edit user edit the document based on their requirements users view of content unit different layout.users can insert picture ,diagramsymbols page number charts clip arts users format the contents in the document, various formats are font, bullets and numbering ,background and grammer ,language set, word count user insert,draw,delete,and sort the contents in the table .administrator control all activities of text editor and who maintains managing and software installation troubleshooting .with the username and password administrator protect the documents in text editor.the new system is being described so that text editor will always being generated automatically can there will be number need for any manual intervention.

VERB PARSING:

The new text editor system should allow users and administratorsto login for creating a new document, modifying files. The new text editor system should allow users to enter their name and enter the password then perform various operations. In the file users open a new document. Open a already existing file. Close the files save and send that another file. Help is used to search and know the information about related totext editor by the user. In edit users edit the document based on their requirements,users views the content with different layouts users can insert picture, symbols, pagenumbers, charts, clip arts. User format the contents in the documents,variousFormats are font, Bullets and numbering, background colors, themes, styles andGrammars, language set, word count. User insert, draw, delete and sort the contentsin the table. Administrator control all activities of text editor. And who maintains Managing and software installation, troubleshooting. With the user name and Password administrator protect the documents in the text editor. The new systemis being designed so that the text editor will be number need for any manualintervation.

USE CASE DIAGRAM:

COLLABORATION DIAGRAM:

SEQUENCE DIAGRAM:

SOURCE CODE:

Form 1:Private Sub cmdload_Click()Dim strName As String, strFile As String, strTemp As StringOn Error GoTo ErrHandlerstrName = InputBox("Filename:")Open strName For Input As #1strFile = ""Do Until EOF(1)Line Input #1, strTempstrFile = strFile & strTemp & vbCrLfLoopText1.Text = strFileClose #1ErrHandler:End Sub

Private Sub cmdquit_Click()EndEnd Sub

Private Sub cmdsave_Click()Dim strName As StringOn Error GoTo ErrHandlerstrName = InputBox("Filename:")Open strName For Output As #1Print #1, Text1.TextClose #1ErrHandler:End Sub

FORM DESIGN:

OUTPUT:

RESULT: Thus the Text Editor problem using case tools for planning cost estimation, modelling the requirements and configuration management is developed successfully.

EX.NO: LIBRARY INFORMATION SYSTEMDATE:

AIM:

To solve Library Automation system using case tools for planning cost estimation

modeling the requirement and configuration management.

PROBLEM STATEMENT:

SCOPE:

The following subsection describes a scope of a new library automation system in terms

of its audience, organization and applicable documents.

AUDIENCE:

The intended users are the people responsible for implementing the new library

automation system.

ORGANIZATION :

This document describes the new library automation system requirements in terms of

system requirements, analysis, summary and design diagram.

APPLICABLE DOCUMENTS:

The following documents provide information necessary to understand the document.

System Requirement Specification(SRS):

The following subsection describes a new library automation system requirement

specification in terms of problem statement and feasibility study.

PROBLEM STATEMENT:

The library automation system allow to record the information to update their database

based on number of books taken and number of books returned.

The new library automation system allows entering the ID card information.

The new library automation system allows individual student desktop throughout the

entire college.

Library automation system for the record of security and auditing student can only

access, edit their own id card.

The system must be updated with the information on which the book has taken and when

it has to be returned.

The legacy database of the old system must be retained along with the new system.

The students should return the book in a time period of 15 days otherwise timeout will be

calculated on the basis of number of days.

When the student return the book after paying the fine then the student account is cleared

and then they can take the books up to the limit that they have allocated.

When the student newly joined in the college, their information will be added into the

student account and the information which includes name, department, register number, course

duration.

When the course duration of the student was completed then the student account will be

cleared.

VERB PARSING:

The new library automation system allows entering the ID card information.

The new library automation system allows individual student desktop throughout the

entire college.

The system must be updated with the information on which the book has taken and when

it has to be returned.

The students should return the book in a time period of 15 days otherwise timeout will be

calculated on the basis of number of days.

If the date exceeds the returning date, they must pay the fine. When the student return the

book after paying the fine then the student account is cleared and then they can take the book up

to the limit that they can allocated.

When the student newly joined in the college, their information will be added into the

student account and the information which includes name, department, register number, course

duration.

When the course duration of the student was completed then the student account will be

cleared.

CLASS DIAGRAM:

USECASE DIAGRAM:


SEQUENCE DUAGRAM:

FORM DESIGN:

LOGIN FORM:

MAIN MENU:

BOOK DETAILS FORM:

RETRIEVING FORM:

RETURN FORM:

SOURCE CODE:FRONT – END (VB 6.0)

START PROGRAMS MICROSOFT VISUAL STUDIO 6.0 MICROSOFT VISUAL BASIC 6.0 OPEN STANDARD EXE

LOGIN FORM:

Private Sub cmdcancel_Click()

Unload Me

End Sub

Private Sub cmdok_Click()

If txtusername.Text = "kamalesh" And txtpassword.Text = "cse" Then

frmmenu.Visible = True

frmlogin.Visible = False

Unload Me

Else

MsgBox ("Please Check Your Username and Password")

txtusername.SetFocus

End If

End Sub

MAIN MENU FORM:

Private Sub Command1_Click()

End

Unload Me

End Sub

Private Sub mnubookdetails_Click()

book.Show

frmmenu.Hide

End Sub

Private Sub mnuborrow_Click()

borrow.Show

frmmenu.Hide

End Sub

Private Sub mnureturn_Click()

frmreturn.Show

frmmenu.Hide

End Sub

BOOK DETAILS FORM:

Dim a As VbMsgBoxResult


Text1.Text = ""

Text2.Text = ""

Text3.Text = ""

Text4.Text = ""

Text5.Text = ""

Text6.Text = ""

Text8.Text = ""

Text1.SetFocus

Command3.Enabled = False


End Sub


On Error Resume Next

If Text1.Text = "" Or Text2.Text = "" Or Text3.Text = "" Or Text4.Text = "" Or Text5.Text = ""

Or Text6.Text = "" Or Text7.Text = "" Then

a = MsgBox("RECORDS NOT SAVED.. PLS COMPLETE..", vbCritical, "WARNING")

Text1.Text = " "

Text1.SetFocus

ElseIf Text1.Text <> "" Or Text2.Text <> "" Or Text3.Text <> "" Or Text4.Text <> "" Or

Text5.Text <> "" Or Text6.Text <> "" Or Text7.Text <> "" Then

Data1.Recordset(0) = Text1.Text







Data1.Recordset.Update

MsgBox ("Record Saved")

End If

Text1.Text = ""

Text2.Text = ""

Text3.Text = ""

Text4.Text = ""

Text5.Text = ""

Text6.Text = ""

Text8.Text = ""


End Sub


On Error Resume Next

a = MsgBox("ARE YOU SURE?", vbYesNo, "DELETE")

If a = vbYes Then

Data1.Recordset.Delete

MsgBox ("Record Deleted")

Text1.Text = ""

Text2.Text = ""

Text3.Text = ""

Text4.Text = ""

Text5.Text = ""

Text6.Text = ""

Text8.Text = ""

Text1.SetFocus

End If

End Sub


Data1.Recordset.Edit








Command2.Enabled = True

End Sub


Unload Me

frmmenu.Show

End Sub



Text1.Enabled = True







Data1.Recordset.AddNew

End Sub









Dim n_strsearch, e_strsearch As String

Dim namecheck, edicheck As Long

n_strsearch = InputBox("Enter the Book Name to find", "Book Name")

e_strsearch = InputBox("Enter the Edition", "Edition")

If n_strsearch = "" Or e_strsearch = "" Then Exit Sub

Dim n As Integer

n = 1

Data1.Recordset.MoveFirst

If Data1.Recordset(0) = "" Then Exit Sub

While n < Data1.Recordset.RecordCount

namecheck = InStr(1, Data1.Recordset(0), n_strsearch, vbTextCompare)

edicheck = InStr(1, Data1.Recordset(2), e_strsearch, vbTextCompare)

If namecheck > 0 And edicheck > 0 Then

Text1.Text = Data1.Recordset(0)









Exit Sub

Else

n = n + 1

Data1.Recordset.MoveNext

End If

Wend

namecheck = InStr(1, Data1.Recordset(0), n_strsearch, vbTextCompare)

edicheck = InStr(1, Data1.Recordset(2), e_strsearch, vbTextCompare)

If namecheck > 0 And edicheck > 0 Then










Exit Sub

Else

MsgBox ("No records match your search")

End If

End Sub

Private Sub Form_Load()

Text1.Enabled = False










End Sub

RETIEVING FORM:







MsgBox ("Record updated")

Text1.Text = ""

Text2.Text = ""

Text3.Text = ""

Text4.Text = ""


End Sub


Unload Me

frmmenu.Show

End Sub

Private Sub Form_Initialize()


Text2.Text = Format(Now, "dd-mm-yyyy")

Text4.Text = Format(Now + 15, "dd-mm-yyyy")

End Sub

RETURN FORM:

Option Explicit

Dim t_strsearch As String

Sub func()

Dim tokennocheck As Long

t_strsearch = InputBox("Enter The Token Number", "Token Number")

If t_strsearch = "" Then Exit Sub

Dim n As Integer

n = 1

Dim achk As Boolean

achk = False

borrow.Data1.Recordset.MoveFirst

While n < borrow.Data1.Recordset.RecordCount

tokennocheck = InStr(1, borrow.Data1.Recordset(0), t_strsearch, vbTextCompare)

If tokennocheck > 0 Then

Text1.Text = t_strsearch


Text3.Text = borrow.Data1.Recordset(3)


achk = True

Exit Sub

Else

n = n + 1

borrow.Data1.Recordset.MoveNext

End If

Wend

tokennocheck = InStr(1, borrow.Data1.Recordset(0), t_strsearch, vbTextCompare)

If tokennocheck > 0 Then

Text1.Text = t_strsearch




achk = True

Exit Sub

End If

If achk = False Then

MsgBox ("Incorrect token number")

End If

End Sub


Unload Me

frmmenu.Show

End Sub








MsgBox ("Records updated")

Text1.Text = ""

Text2.Text = ""

Text3.Text = ""

Text4.Text = ""

End Sub


Call func

End Sub


Call func

End Sub


OUTPUT SCREEN:

LOGIN FORM:

MAIN MENU:

BOOK DETAILS FORM:

RETRIEVING FORM:

RETURN FORM:

Fig 4.5 Return Form

RESULT: Thus the library automation system using case tools for planning cost estimation, modelling the requirement and configuration management is developed successfully.

EX.NO: BANKING SYSTEM

DATE:

AIM:

To solve the banking system problem using CASE tool for planning cost estimation, modeling the requirements and configuration management. SCOPE:

The following subsection describes a scope of a new banking system in terms of its avoidance, organization and applicable documents.

AUDIENCE:

The intended users are the people responsible for implementing the new banking system.

ORGANIZATION:

This document describes the new banking system requirements in terms of system requirements, executable summary analysis and design diagram.


The following document provides the information necessary to understand the document.

SYSTEM REQUIREMENT SPECIFICATION (SRS):

The following subsection describes the new banking system requirement system specification in terms of problem statement and feasibility study.

PROBLEM STATEMENT:

The new banking system should allow the customer to create account, withdraw and deposit money, enquire and request for loan. The system should provide privileges for the manager to verify transaction, account creation, maintain database and sanction loan. The system should also provide privilege for the cashier to overview the transaction. The transaction may be of any one of the following way by cash, by dd, by cheque. So the system should provide the corresponding option. While creating a new account the customer should specify the account type whether it is savings account or current account.

VERB PRASING:

The new banking system should allow the customer to create account, withdraw and deposit money, enquire and request for loan. The system should provide privileges for the manager to verify transaction, account creation, maintain database and sanction loan. The system should also provide privilege for the cashier to overview the transaction. The transaction may be of any one of the following way by cash, by dd, by cheque. So the system should provide the corresponding option. While creating a new account the customer should specify the account type whether it is savings account or current account.

USECASE DIAGRAM:

verify transaction

maintain database

loan sactionloan creation

by dd

by cash

by cheque

customer

transaction

current account

savings account

verify account type

deposit withdraw

edit account

manager

account creation

verify

cashier

edit transaction amount


SEQUENCE DIAGRAM:

4.Checking3.Withdraw

2.Deposit the Amount1.Create Account

User System

5. Amount Transaction

Banking system:Source code:Form 1:Private Sub Command1_Click()Form2.ShowUnload MeEnd Sub


User User Details

Create()

Deposit()

Balance()

Withdraw()

Transaction()

EndEnd Sub

Form 2:Private Sub Command1_Click()If (Text1.Text = "1234") ThenForm3.ShowUnload MeElseIf (Text1.Text = "") ThenMsgBox ("Enter your Pincode")ElseMsgBox ("Incorrect pincode pls enter correctly")Text1.Text = ""End IfEnd Sub

Private Sub Command2_Click()Form1.ShowEnd Sub

Form 3:Dim db As DatabaseDim rs As RecordsetPrivate Sub Command1_Click()Form4.ShowUnload MeEnd Sub

Private Sub Command2_Click()Form5.ShowUnload MeEnd Sub


Private Sub Command4_Click()EndEnd Sub


Private Sub Form_Load()Set db = OpenDatabase("C:\Documents and Settings\kite09cs12\Desktop\VB.mdb")Set rs = db.OpenRecordset("Accounts")End Sub

Form 4:Dim db As DatabaseDim rs As RecordsetPrivate Sub Command1_Click()Form3.ShowUnload MeEnd Sub

Private Sub Command2_Click()Form1.ShowEnd Sub

Private Sub Form_Load()Set db = OpenDatabase("C:\Documents and Settings\kite09cs12\Desktop\VB.mdb")Set rs = db.OpenRecordset("Accounts")Text1.Enabled = FalseText1.Text = rs.Fields(1)End Sub

Form 5:Dim db As DatabaseDim rs As RecordsetDim a As Integer

Private Sub Command4_Click()Text1.Text = ""End SubPrivate Sub Command3_Click()rs.Edita = Val(Text1.Text)rs.Updaters.Editrs(1) = rs(1) + ars.UpdateMsgBox "deposit successfully", vbOKOnlyText1.Text = ""End Sub

Private Sub Command1_Click()Unload MeForm3.ShowEnd Sub



Text1.Text = ""Set db = OpenDatabase("C:\Documents and Settings\kite09cs12\Desktop\VB.mdb")Set rs = db.OpenRecordset("Accounts")Command2.Enabled = False

End Sub

Private Sub Text1_Change()Command2.Enabled = TrueEnd Sub

Form 6:Dim db As DatabaseDim rs As RecordsetDim a As IntegerPrivate Sub Command2_Click()Text1.Text = ""End SubPrivate Sub Command1_Click()rs.Edita = Val(Text1.Text)rs.Updaters.Editrs(1) = rs(1) - ars.UpdateMsgBox "withdraw successfully", vbOKOnlyText1.Text = ""End Sub

Private Sub Command3_Click()Form3.Refresh

Unload MeForm3.ShowEnd Sub


Private Sub Form_Load()Set db = OpenDatabase("C:\Documents and Settings\kite09cs12\Desktop\VB.mdb")Set rs = db.OpenRecordset("Accounts")Text1.Text = ""Command2.Enabled = FalseEnd Sub

Private Sub Text1_Change()Command2.Enabled = True

End Sub

FORM DESIGN:

OUTPUT:

RESULT:

Thus the banking system using case tool for planning cost estimation, modeling the requirements and configuration management is developed successfully.

EX.NO: ONLINE SHOPPING SYSTEMDATE:

AIM:To solve web based online shopping using case tools for planting cost elimination

handling the requirements and configuration management.

SCOPE:

The following subsection describes a scope for new online shopping system in terms of its customer, distributor and applicable documents.

CUSTOMER:

The intended users are the people responsible for implementing the online shopping system.

DISTRIBUTOR:

This system describes the new online shopping requirements in term of system requirement, executive summary, and analysis and design diagram.


The following provide information necessary to understand the document.

SYSTEM REQUIREMENT SPECIFICATION (SRS):

The following subsection describes the online shopping requirement system requirement specification in terms of problem statement and feasibility study.

PROBLEM STATEMENT:

The new online shopping is beneficial for customers to purchase things from their workplace itself with the help of computer. Here the customer should submit his details including his phone number, card number, address etc. he should also have the permission to edit and access his details. In this process distributor also plays a main role.

He will access the details given by the customer and will do some modification to the product details when it is necessary. He will also generate the product cost. The person called administrator will access all details and edit the information. He also maintains the database. Another actor in this process is the billing system. This system is responsible for the mode of payment. He will access these details and conclude the result.

VERB PARSING:

The online shopping system should allow the customer to submit, edit and access their details. It should allow the distributor to generate the product cost once the product is chosen, edit and access the product details. It should also allow the administrator to edit information, access it and maintain a database. The billing system is responsible for collecting amount using the different mode of payment.

CLASS DIAGRAM

Item Details User Details

Name of the itemItem IDCost

Name of the customerAccess NoDebit Card No

Add()Remove()

Purchase()Checking()

USECASE DIAGRAM

edit customer details

submit customer details

customer

edit information

access distributor

maintain data base

administrator

Access customer details

Edit product details

Access product details

Distributor

billing system

generate product cost

E-cash

debit cash

credit cash

mode of payment

COLLABORATION DIAGRAM

4.Purchase3.Check the Balance

2.Select the Specific items from the list1.Adding the List of items

UserSystem

SEQUENCE DIAGRAM

User Item User details

Add()

Add User()

Select()

Retrieve the User Details()

Purchase()

FORM DESIGN:



FORM 1:

Private Sub Command1_Click()Unload MeEndEnd SubPrivate Sub Picture1_Click()End SubPrivate Sub Picture2_Click()KEYBOARD.ShowEnd SubPrivate Sub Picture3_Click()DIGITALCAM.ShowEnd SubPrivate Sub Picture4_Click()LAPTOP.ShowEnd SubPrivate Sub Picture5_Click()MOBILE.ShowEnd Sub

FORM 2:Private Sub Picture10_Click()M7.ShowEnd SubPrivate Sub Picture11_Click()M8.ShowEnd SubPrivate Sub Picture12_Click()M9.ShowEnd SubPrivate Sub Picture2_Click()M1.ShowEnd SubPrivate Sub Picture3_Click()M2.ShowEnd SubPrivate Sub Picture4_Click()M3.ShowEnd SubPrivate Sub Picture6_Click()

M4.ShowEnd SubPrivate Sub Picture7_Click()M5.ShowEnd Sub

FORM 3:Private Sub Command1_Click()rs.AddNewrs.Fields(0) = Text1.Textrs.Fields(1) = Text2.Textrs.Fields(2) = Text3.Textrs.Fields(3) = Text4.Textrs.Fields(4) = Text5.TextMsgBox "YOUR REQUSED HAVE BEEN SUCESSFULLY"rs.UpdateEndEnd SubPrivate Sub Command2_Click()MAIN.ShowEnd SubPrivate Sub Form_Activate()MsgBox "conNECTION SUCCESFULLY"Set con = New ADODB.ConnectionSet rs = New ADODB.Recordsetcon.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=Z:\DHEENA\MY PROJECT\SHOPPING1.mdb;Persist Security Info=False"'con.Open ("Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" + apppath + "MY PROJECT\SHOPPING1.mdb;Persist Security Info=False")rs.Open "CDETAILS", con, adOpenDynamic, adLockPessimisticEnd Sub

FORM 4:Private Sub Form_Load()End SubPrivate Sub Label1_Click()KEY1.ShowEnd SubPrivate Sub Label10_Click()MAIN.ShowEnd SubPrivate Sub Label2_Click()KEY2.ShowEnd Sub

Private Sub Label3_Click()KEY3.ShowEnd SubPrivate Sub Label4_Click()KEY4.ShowEnd SubPrivate Sub Label5_Click()KEY5.ShowEnd SubPrivate Sub Label6_Click()KEY6.ShowEnd Sub


OUTPUT SCREEN:

RESULT:

Thus the web based online shopping using case tools for planning cost estimation handling, the requirements and configuration management is created successfully.

EX.NO: ONLINE VOTING SYSTEMDATE:

AIM: To solve online voting system using case tools for planning cost estimation, modelling the requirement and configuration management.

SCOPE:

The following subsection describes a scope of a online voting system in terms of its voter, election officials and applicable documents.

→Voter: The intended voters are the people responsible for the online voting.

→Election Officials: The election officials maintains the candidate list, voters list, analysis and design documents.

→Applicable documents: The following document provide information necessary to Understand about the online voting.

SYSTEM REQUIREMENT SPECIFICATION:

The following subsection describes the online voting system requirement specification in terms of problem statement and feasibility study.

PROBLEM STATEMENT:

The online voting should allow the voters to register the vote automatically through system. The new system should allow voters to enter their vote, and view the current progress of voting’s. For reasons of security, only the voter can access and edittheir votes by entering their Voter ID. The system should have the election officials togenerate the result based on the number of votes recorded. The votes are stored in the database of the system. The documentation manager should document the statistics of the election. There are chances of occurrence of error while registering or while documenting the details. For this purpose the system should be provided with a bug-report manager.

The new system is being designed so that on entering the vote and the results be generated and published on the due date.

VERB PARSING:

The online voting should allow the voters to register the vote automatically through system. The new system should allow voters to enter their vote, and view the current progress of voting’s. For reasons of security, only the voter can access and edittheir votes by entering their Voter ID. The system should have the election officials to generate the result based on the number of votes recorded. The votes are stored in the database of the system. The documentation manager should document the statistics of the election. There are chances of occurrence of error while registering or while documenting the details. For this purpose the system should be provided with a bug-report manager. The new system is being designed so that on entering the vote and the results be generated and published on the due date.

CLASS DIAGRAM

Voter Details Candidate details

Name of the VoterAddressDate of bIrthAgeSectorDistrictVoter IdDriving LicenseRation Card NoPassport No

Name of the VoterAddressDate of bIrthAgeSectorDistrictSymbol NameSymbol

Checking()Polling()Add()Remove()

Register()Register()Polling()Remove()

USECASE DIAGRAM

Submit id cardVerify ID cardPolling officer

Check the vote

Count the vote

Announcer Announces the result

Enter the ID card

Computer

Voter

Enter the vote

COLLABORATION DIAGRAM

3. Polling()2. Candidate registration

1. Voter Registration

User System

4.Results (Winner)

SEQUENCE DIAGRAM

User Voter Details Candidate Details

Add Voter()

Add Candidate()

Polling()

Retrieve the Candidate

Details()

Results ()

Winner Details

FORM DESIGN:



MAIN FORMDim con As New ADODB.ConnectionDim rs As New ADODB.RecordsetPrivate Sub Label2_Click()EndEnd SubPrivate Sub lbadmin_Click()Form1.ShowEnd SubPrivate Sub lbvoter_Click()Form2.ShowEnd Sub

VOTER VERIFICATION FORM

Private Sub cmdcontinue_Click()If Combo1.Text = "Erode" ThenIf Option3.Value = True Then

Password = InputBox("ENTER YOUR PASSWORD")If Password = "" ThenExit SubEnd IfVOTERID = InputBox("ENTER THE ID")If VOTERID = "" ThenExit SubEnd Ifrs.MoveFirstWhile Not rs.EOFIf Trim(UCase(rs.Fields(10))) = Trim(UCase(Password)) Thenrs.MoveFirstWhile Not rs.EOFIf Trim(UCase(rs.Fields(4))) = Trim(UCase(VOTERID)) ThenText1.Text = rs.Fields(0)Form4.Showrs.Deleters.UpdateCombo1.Text = ""Text1.Text = ""Option1.Value = FalseOption2.Value = FalseOption3.Value = FalseOption4.Value = FalseOption5.Value = FalseOption6.Value = FalseOption7.Value = FalseOption8.Value = FalseMe.HideExit SubEnd Ifrs.MoveNextWendExit SubEnd Ifrs.MoveNextWendMsgBox "Sorry! you are not able to vote", vbCriticalIf rs.BOF = True ThenText1.Text = ""Elsers.MoveLast'Text1.Text = Val(rs.Fields(0)) + 1End IfEnd If

End IfPrivate Sub cmdprevious_Click()Form9.ShowCombo1.Text = ""Text1.Text = ""Option1.Value = FalseOption2.Value = FalseOption3.Value = FalseOption4.Value = FalseOption5.Value = FalseOption6.Value = FalseOption7.Value = FalseOption8.Value = FalseMe.HideEnd SubPrivate Sub Form_Activate()'MsgBox "CONNECTION SUCCESFULLY"Set con = New ADODB.ConnectionSet rs = New ADODB.Recordsetcon.Open ("Provider=Microsoft.Jet.OLEDB.4.0;Data Source=E:\dr\DATABASES\voterlist.mdb;Persist Security Info=False")rs.Open "erode", con, adOpenDynamic, adLockOptimisticEnd Sub

VOTE REGISTER FORMPrivate Sub cmdexit_Click()Form9.ShowMe.HideOption1.Value = FalseOption2.Value = FalseOption3.Value = FalseOption4.Value = FalseOption5.Value = FalseOption1.Enabled = TrueOption2.Enabled = TrueOption3.Enabled = TrueOption4.Enabled = TrueOption5.Enabled = TrueCommand1.Enabled = TrueEnd SubPrivate Sub Command1_Click()Command1.Enabled = FalseIf Option1.Value = True ThenIf rs.Fields(0) = "RAJAMANICKAM" Thenrs.Fields(2) = Val(rs.Fields(2)) + 1

rs.Fields.Refreshrs.UpdateMsgBox "YOUR VOTE IS SUCCESFULLY REGISTERED"End IfElseIf Option2.Value = True ThenIf (rs1.Fields(0) = "PRADEEP") Then rs1.Fields(2) = Val(rs1.Fields(2)) + 1rs1.Fields.Refreshrs1.UpdateMsgBox "YOUR VOTE IS SUCCESFULLY REGISTERED"End IfElseIf Option3.Value = True ThenIf (rs2.Fields(0) = "SIVAKUMAR") Then rs2.Fields(2) = Val(rs2.Fields(2)) + 1rs2.Fields.Refreshrs2.UpdateMsgBox "YOUR VOTE IS SUCCESFULLY REGISTERED"End IfElseIf Option4.Value = True ThenIf (rs3.Fields(0) = "VIVEK") Then rs3.Fields(2) = Val(rs3.Fields(2)) + 1rs3.Fields.Refreshrs3.UpdateMsgBox "YOUR VOTE IS SUCCESFULLY REGISTERED"End IfElseIf Option5.Value = True Then If (rs4.Fields(0) = "VELUMANI") Then rs4.Fields(2) = Val(rs4.Fields(2)) + 1rs4.Fields.Refreshrs4.UpdateMsgBox "YOUR VOTE IS SUCCESFULLY REGISTERED"End IfEnd IfEnd IfEnd IfEnd IfEnd IfEnd SubPrivate Sub Form_Activate()Set con = New ADODB.ConnectionSet rs = New ADODB.Recordset

con.Open ("Provider=Microsoft.Jet.OLEDB.4.0;Data Source=E:\dr\DATABASES\admin\ERODECANDIDATERESULTS\ERODE1.MDB;Persist Security Info=False")rs.Open "RAJAMANICKAM", con, adOpenDynamic, adLockOptimisticrs.Updaters.Fields.RefreshEnd Sub

ADMINISTRATOR LOGIN FORM

Dim con As New ADODB.ConnectionDim rs As New ADODB.RecordsetPrivate Sub cmdchangepass_Click()Form24.ShowMe.HideEnd SubPrivate Sub Command1_Click()Form9.ShowMe.HideEnd SubPrivate Sub Form_Load() text1.Text = "" text2.Text = ""End SubPrivate Sub cmdenter_Click()If ((Trim(UCase(rs.Fields(0))) = Trim(UCase(text1.Text))) And (Trim(UCase(rs.Fields(1))) = Trim(UCase(text2.Text)))) Then MDIForm1.Show text1.Text = "" text2.Text = "" Me.HideElse MsgBox " password is incorrect" text2.Text = "" text2.SetFocusEnd IfEnd SubPrivate Sub Form_Activate()Set con = New ADODB.ConnectionSet rs = New ADODB.Recordsetcon.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=E:\dr\DATABASES\admin\PASSWORDS.mdb;Persist Security Info=False"rs.Open "ADMINPASSWORD", con, adOpenDynamic, adLockOptimisticEnd Sub


OUTPUT SCREEN:

RESULT: Thus the online voting system using case tools for planning cost estimation, modelling the requirement and configuration management is developed successfully.