Documente Academic
Documente Profesional
Documente Cultură
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. enefits of !isual modeling includes, "larity #amiliarity Maintenance simplification
UML:
$nified modeling language%$M&'is a communication standard of !isual modeling. (he $M& pro!ides a smooth transition between the business domain and the computer domain. $M& is an ob)ect oriented language for specifying, constructing, !isualizing and documenting the software system and its components. $M& is a graphical language with a set of rules and semantics. $M& is a combination of $M& *ata Modeling usiness Modeling +b)ect Modeling "omponent Modeling
UML DIAGRAMS:
defines graphical diagrams such as, "lass diagram $se case diagram eha!ior diagrams ,nteraction *iagrams o -e.uence *iagrams o "ollaboration *iagrams -tate "hart *iagrams Acti!ity *iagram ,mplementation *iagrams o "omponent *iagram o *eployment *iagrams
USE-CASE DIAGRAMS:
$se/case diagrams graphically depict system beha!ior %use cases'.(hese diagrams present a high le!el !iew of how the system is used as !iewed from an outsider0s %actor0s' perspecti!e. A use/case diagram may depict all or some of the use cases of a system. A use/case diagram can contain: Actor0s %1things2 outside the system' $se cases%system boundaries identifying what the system should do' ,nteractions or relationships between actors and use cases in the system including the associations, dependencies and generalizations.
USE CASE:
$se case is scenario for understanding system re.uirements. 3!ery single use case must describe one main flow of e!ents. ACTOR Actors represent system users, who pro!ide input to and recei!e information from the system. An actor is a stereotype of a class and is depicted as a 2stickman2 on a use/case diagram. (he name of the actor is displayed below the icon. Additional information about the actor can be !iewed in the use/case specification. RELATIONSHIPS 4ou 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. (he generalize relationship can be drawn between actors. 5elationships between use case diagrams include "ommunication $ses 36tend FLOW OF EVENTS A flow of e!ents is a se.uence of transaction %or e!ents' performed by the system. (hey typically contain !ery detailed information, written in terms of what the system should do, not how accomplish the task. A flow of e!ents should include: 7hen and how the use case starts and ends $se case8actor interactions *ata needed by the use case Normal se.uence of e!ents for the use case Alternate or e6ception flows USE-CASE REALIZATIONS (SCENARIOS)
A use case realization is a graphic se.uence of e!ents, also referred to as a scenario or an instance of a use case. these realization or scenarios are depicted in either a se.uence or collaboration diagram. (he two most common scenarios are the typical%or primary'scenario, where all is well and the e6ception%secondary'scenario, which address the de!iations. (he e6ception scenario address the 1what if 92 elements of the use case.
ACTIVITY DIAGRAM:
An acti!ity represents the performance of task or duty in a workflow. it may also represent the e6ecution of a statement in a procedure. An acti!ity diagram is acti!ity centric. (ransitions connect acti!ities with other model elements and ob)ect flows connect acti!ities with ob)ects. (he acti!ity icon appears as a rectangle with rounded ends with name %take order and process order' and a compartment for actions. (he name of an acti!ity must be uni.ue and should declare the acti!ity0s purpose. All acti!ity icons with the name on an acti!ity diagram represent the same acti!ity. 4ou must add actions through the action specification. Action on acti!ities can occur of four times: +n entry +n e6it *o +n e!ent
SEQUENCE DIAGRAMS:
-e.uence diagram is a graphical !iew of a scenario that shows ob)ect interaction in a time/based se.uence. -e.uence diagrams establish the roles ob)ects. -e.uence diagrams are normally associated with use cases. -e.uence diagrams are closely related to collaboration diagrams and both are alternate representation of an interaction. A se.uence diagram has two dimensions: typically, !ertical placement represents time and horizontal placement represents different ob)ects.
COLLABORATION DIAGRAMS:
A collaboration diagram is an interaction diagram that shows the order of messages that implement an operation or a transaction. "ollaboration diagrams show ob)ects, their links, and their messages. (hey can also contain simple class instances and class utility instances. 3ach collaboration diagram pro!ides a !iew of the interactions or structural relationships that occur between ob)ects and ob)ect/like entities in the current model.
SCENARIOS:
-cenarios show the different se.uence of interaction between actors and system. A -cenario is an instance of a use case: it is an outline of e!ents that occur during system e6ecution. A scenario can be e6pressed in te6t or se.uence of steps.
STEREOTYPES:
-tereotype represents built/in e6tensibility mechanism for $M&. -tereotype is new class of modeling element introduced during modeling. General presentation of stereotype is string with guillemots. Various form of stereotype is "lass stereotypes Association stereotypes *ependency stereotypes "omponent stereotypes
RATIONAL ROSE:
5ational rose is a tool for understanding, analyze and designing of software intensi!e system. Model in rational rose is constructed using !iews and diagrams (he !iews used are, $se case !iew &ogical !iew "omponent !iew *e!elopment !iew ,mplementation !iew ;rocess !iew 5ational 5ose is a G$, en!ironment containing, rowser window
*iagram window *iagram window *ocumentation window &og window +ptions window
EX.NO: DATE:
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.
PROBLEM STATEMENT:
The Employee submits the application for creating a new account.The following datas are needed for an employee to create a record Employee name, esignation, !ate per hour, "o. #f wor$ing hours, "o of days absent, SSS, %&'()*)', %hil health, aily net pay, Total net pay. The system is esigned and implemented using +ase Tools.
Entering the salary details and the total no of wor$ing hours %rocessing 'eneration of pay slip .iewing details 'iving salary
L %&'
/ere 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.
Pr )e""&'%
%rocessing is done by the database, it calculates the aily net pay. 0inally the net pay is calculated by subtracting SSS, %&')(*)', %/)- /E&-T/. SALARY CALCULATION:
aily net pay1 wor$ing hours2rate per hour Total "et %ay1daily net pay(3SSS(%&')*)'(%/)- /E&-T/4
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:
lop cl basic pay da 1 rsia 1 callop() grosssal lop tp 1 calgrsal() 1 1 calnetpay() net sal gross pay pf
Entering details
#ie$ slip
L G %&
COLLOBORATION DIAGRAM:
0( if lop not a*ailable gs)tp 4( netsal calc by deducting pf if any '( netsal)grosssal if no pf totalpay 2( grosssal)tp3lop system 5( update details netsal 1( calculation of lop if lop a*ailable
lop
SEQUENTIAL DIAGRAM
system
employee
emp details
basic pay
totalpay
lop
grosssal
netsal
retrie*e emp details basic pay calc based on ug pg add basic,D-,./!if lop not a*ailable gs)tp
netsal)grosssal if no pf
update details
FORM DESIGN:
SOURCE CODE:
FRONT END (VB .!) -(A5( ;5+G5AM- M,"5+-+#( V,-$A& -($*,+ <.= M,"5+-+#( V,-$A& A-," <.= +;3N -(AN*A5* 3>3 FORM ": *im con As New A*+* ."onnection *im rs As New A*+* .5ecordset ;ri!ate -ub cmd+?@"lick%' ,f t6t$serName.(e6t A rs.#ields%=' And t6t;assword.(e6t A rs.#ields%B' (hen M*,#ormB.-how Me.Cide 3nd ,f 3nd -ub ;ri!ate -ub "ommandB@"lick %' #rameB.Visible A (rue 3nd -ub ;ri!ate -ub "ommandD@"lick %' rs.AddNew rs.#ields%=' A (e6tB.(e6t rs.#ields%B' A (e6tD.(e6t rs.$pdate Msg o6 E-a!eE #rameB.Visible A #alse 3nd -ub ;ri!ate -ub "ommandF@"lick %' #ormG.-how Me.Cide 3nd -ub ;ri!ate -ub #orm@Acti!ate%' -et con A New A*+* ."onnection -et rs A New A*+* .5ecordset con.+pen E;ro!iderAMicrosoft.Het.+&3* .G.=: *ata -ourceAE I App.;ath I E Jpas.mdb:;ersist -ecurity ,nfoA#alseE rs.+pen EpasE, con, ad+pen*ynamic, ad&ock+ptimistic #rameB.Visible A #alse (e6tB.(e6t A EE (e6tD.(e6t A EE 3nd -ub FORM #: ;ri!ate -ub "ommandB@"lick %' rs.AddNew rs.#ields%=' A (e6tB.(e6t ,f +ptionB A (rue And +ptionD A #alse (hen rs.#ields%B' A +ptionB."aption
3lse rs.#ields%B' A +ptionD."aption 3nd ,f rs.#ields%D' A (e6tD.(e6t (e6tF.(e6t A rs.#ields%F' rs.#ields%G' A (e6tG.(e6t rs.#ields%K' A (e6tK.(e6t rs.$pdate Msg o6 EaddedE 3nd -ub ;ri!ate -ub "ommandD@"lick%' M*,#ormB.-how 3nd -ub ;ri!ate -ub "ommandF@"lick%' (e6tB.(e6t A EE (e6tD.(e6t A EE (e6tF.(e6t A EE (e6tG.(e6t A EE (e6tK.(e6t A EE 3nd -ub ;ri!ate -ub #orm@Acti!ate%' -et con A New A*+* ."onnection -et rs A New A*+* .5ecordset con.+pen E;ro!iderAMicrosoft.Het.+&3* .G.=:*ata -ourceAE I App.;ath I EJdbD.mdb:;ersist -ecurity ,nfoA#alseE rs.+pen EpersonalE, con, ad+pen*ynamic, ad&ock+ptimistic Msg o6 Econnection successfullyE 3nd -ub FORM $: *im con As New A*+* ."onnection *im rs As New A*+* .5ecordset ;ri!ate -ub cmde6it@"lick%' 3nd 3nd -ub ;ri!ate -ub "ommandB@"lick%' (e6tD.(e6t A EE (e6tB.(e6t A EE (e6tF.(e6t A EE "omboD.(e6t A EE "omboB.(e6t A EE "omboF.(e6t A EE rs.#ields.5efresh rs.$pdate
,f %(e6tD.(e6t A EE And (e6tB.(e6t A EE And (e6tF.(e6t A EE And "omboD.(e6t A EE And "omboB.(e6t A EE And "omboF.(e6t A EE' (hen Msg o6 Eplease search your details and modify your detailsE 3lse rs.Mo!e#irst 7hile Not rs.3+# ,f (e6tD.(e6t A rs.#ields%B' (hen Msg o6 E,* already e6istE 36it -ub 3lse rs.Mo!eNe6t 3nd ,f 7end rs.AddNew rs.#ields%=' A (e6tB.(e6t rs.#ields%B' A (e6tD.(e6t rs.#ields%D' A (e6tF.(e6t rs.#ields%F' A "omboB.(e6t rs.#ields%G' A "omboD.(e6t rs.#ields%K' A "omboF.(e6t rs.#ields%<' A Val%"omboF.(e6t L %"omboF.(e6t M BD 8 B=='' rs.$pdate Msg o6 EaddedE (e6tD.(e6t A EE (e6tB.(e6t A EE (e6tF.(e6t A EE "omboD.(e6t A EE "omboB.(e6t A EE "omboF.(e6t A EE 3nd ,f 3nd -ub ;ri!ate -ub "ommandG@"lick%' ,f rs.3+# A #alse (hen rs.Mo!e&ast (e6tB.(e6t A rs.#ields%=' (e6tD.(e6t A rs.#ields%B' (e6tF.(e6t A rs.#ields%D' "omboB.(e6t A rs.#ields%F' "omboD.(e6t A rs.#ields%G' "omboF.(e6t A rs.#ields%K' Msg o6 ElastE 3lse Msg o6 Eno dataE
3nd ,f 3nd -ub ;ri!ate -ub "ommandK@"lick%' ,f %rs. +# A #alse' And %rs. +# A (rue' (hen rs.Mo!e#irst N,f rs. +# A #alse (hen (e6tB.(e6t A rs.#ields%=' (e6tD.(e6t A rs.#ields%B' (e6tF.(e6t A rs.#ields%D' "omboB.(e6t A rs.#ields%F' "omboD.(e6t A rs.#ields%G' "omboF.(e6t A rs.#ields%K' Msg o6 EfirstE 3lse Msg o6 Eno dataE 3nd ,f 3nd -ub ;ri!ate -ub "ommandD@"lick%' ,f %(e6tD.(e6t A EE And (e6tB.(e6t A EE And (e6tF.(e6t A EE And "omboD.(e6t A EE And "omboB.(e6t A EE And "omboF.(e6t A EE' (hen Msg o6 Eplease search your details and modify your detailsE 3lse rs.#ields%=' A (e6tB.(e6t rs.#ields%B' A (e6tD.(e6t rs.#ields%D' A (e6tF.(e6t rs.#ields%F' A "omboB.(e6t rs.#ields%G' A "omboD.(e6t rs.#ields%K' A "omboF.(e6t rs.#ields%<' A Val%"omboF.(e6t L %"omboF.(e6t M BD 8 B=='' rs.$pdate Msg o6 E-$""3--#$&&4E (e6tD.(e6t A EE (e6tB.(e6t A EE (e6tF.(e6t A EE "omboD.(e6t A EE "omboB.(e6t A EE "omboF.(e6t A EE 3nd ,f 3nd -ub ;ri!ate -ub "ommandF@"lick%' N*im i As ,nteger Ni A B N#or i A B (o rs.#ields."ount
N,f %rs.#ields%B' A (e6tD.(e6t' (hen N,f %rs. +# A #alse' And %rs.3+# A #alse' (hen 7hile Not rs.3+# ,f (rim%$"ase%rs.#ields%B''' A (e6tD.(e6t (hen (e6tB.(e6t A rs.#ields%=' (e6tD.(e6t A rs.#ields%B' (e6tF.(e6t A rs.#ields%D' "omboD.(e6t A rs.#ields%F' "omboB.(e6t A rs.#ields%G' "omboF.(e6t A rs.#ields%K' 36it -ub 3lse rs.Mo!eNe6t 3nd ,f 7end rs.*elete Msg o6 %E5ecord *eletedE' Msg o6 %Eno data deletedE' N,f %rs. +# A (rue' And %rs.3+# A (rue' (hen NMsg o6 %Eno data foundE' N3nd ,f N3lse NMsg o6 %Eno data deletedE' N3nd ,f NNe6t i 3nd -ub ;ri!ate -ub "ommand<@"lick%' "ommandD.3nabled A (rue employeeid A ,nput o6%E3N(35 (C3 ,*E' ,f employeeid A EE (hen 36it -ub 3nd ,f rs.Mo!e#irst 7hile Not rs.3+# ,f (rim%$"ase%rs.#ields%B''' A (rim%$"ase%employeeid'' (hen (e6tB.(e6t A rs.#ields%=' (e6tD.(e6t A rs.#ields%B' (e6tF.(e6t A rs.#ields%D' "omboD.(e6t A rs.#ields%F' "omboB.(e6t A rs.#ields%G' "omboF.(e6t A rs.#ields%K' 36it -ub
3nd ,f rs.Mo!eNe6t 7end Msg o6 ENo such 5ecordE, !b"ritical ,f rs. +# A (rue (hen N(e6tB.(e6t A B 3lse rs.Mo!e&ast N(e6tB.(e6t A Val%rs.#ields%='' L B 3nd ,f 3nd -ub ;ri!ate -ub "ommandO@"lick%' (e6tD.(e6t A EE (e6tB.(e6t A EE (e6tF.(e6t A EE "omboD.(e6t A EE "omboB.(e6t A EE "omboF.(e6t A EE 3nd -ub ;ri!ate -ub "ommandP@"lick%' M*,#ormB.-how 3nd -ub ;ri!ate -ub #orm@Acti!ate%' -et con A New A*+* ."onnection -et rs A New A*+* .5ecordset con.+pen E;ro!iderAMicrosoft.Het.+&3* .G.=:*ata -ourceAE I App.;ath I EJdbB.mdb:;ersist -ecurity ,nfoA#alseE rs.+pen EemployeeE, con, ad+pen*ynamic, ad&ock+ptimistic Msg o6 Econnection successfullyE (e6tB.-et#ocus (e6tD.(e6t A EE (e6tB.(e6t A EE (e6tF.(e6t A EE "omboD.(e6t A EE "omboB.(e6t A EE "omboF.(e6t A EE 3nd -ub
OUTPUT SCREEN:
CONCLUSION
(hus the system is de!eloped using ob)ect oriented programming approach with the help of "A-3 tools.
EX.NO: DATE:
TEXT EDITOR
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.
PROBLEM STATEMENT:
The new text editor system should allow users 5administrator to login for creating a new documents modifying files .the new text editor should allow the users to enter their name 5enter 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 $now the information about related to text editor by the user edit by the user. )n 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 ,bac$ground 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 administrators to 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. )n the file users open a new document. #pen a already existing file. +lose the files save and send that another file. /elp is used to search and $now the information about related to text editor by the user. )n 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. 6ser format the contents in the documents,various 0ormats are font, *ullets and numbering, bac$ground colors, themes, styles and 'rammars, language set, word count. 6ser insert, draw, delete and sort the contents in the table. &dministrator control all activities of text editor. &nd who maintains 7anaging and software installation, troubleshooting. 8ith the user name and %assword administrator protect the documents in the text editor. The new system is being designed so that the text editor will be number need for any manual intervation.
COLLABORATION DIAGRAM:
SEQUENCE DIAGRAM:
SOURCE CODE: F r$ *:
%rivate Sub cmdload9+lic$34 im str"ame &s String, str0ile &s String, strTemp &s String #n Error 'oTo Err/andler
str"ame 1 )nput*ox3:0ilename,:4 #pen str"ame 0or )nput &s ;< str0ile 1 :: o 6ntil E#03<4 -ine )nput ;<, strTemp str0ile 1 str0ile 5 strTemp 5 vb+r-f -oop Text<.Text 1 str0ile +lose ;< Err/andler, End Sub %rivate Sub cmdquit9+lic$34 End End Sub %rivate Sub cmdsave9+lic$34 im str"ame &s String #n Error 'oTo Err/andler str"ame 1 )nput*ox3:0ilename,:4 #pen str"ame 0or #utput &s ;< %rint ;<, Text<.Text +lose ;< Err/andler, 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: DATE:
AIM:
To solve -ibrary &utomation system using case tools for planning cost estimation modeling the requirement and configuration management.
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.
PROBLEM STATEMENT:
The library automation system allow to record the information to update their database based on number of boo$s ta$en and number of boo$s returned. The new library automation system allows entering the ) card information. The new library automation system allows individual student des$top throughout the entire college.
-ibrary 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 boo$ has ta$en 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 boo$ in a time period of <= days otherwise timeout will be calculated on the basis of number of days. 8hen the student return the boo$ after paying the fine then the student account is cleared and then they can ta$e the boo$s up to the limit that they have allocated. 8hen the student newly >oined in the college, their information will be added into the student account and the information which includes name, department, register number, course duration. 8hen 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 ) card information. The new library automation system allows individual student des$top throughout the entire college. The system must be updated with the information on which the boo$ has ta$en and when it has to be returned. The students should return the boo$ in a time period of <= days otherwise timeout will be calculated on the basis of number of days. )f the date exceeds the returning date, they must pay the fine. 8hen the student return the boo$ after paying the fine then the student account is cleared and then they can ta$e the boo$ up to the limit that they can allocated. 8hen the student newly >oined in the college, their information will be added into the student account and the information which includes name, department, register number, course duration. 8hen the course duration of the student was completed then the student account will be cleared.
CLASS DIAGRAM:
USECASE DIAGRAM:
COLLABORATION DIAGRAM:
SEQUENCE DUAGRAM:
FORM DESIGN:
LOGIN FORM:
MAIN MENU:
RETRIEVING FORM:
RETURN FORM:
-(A5( ;5+G5AM- M,"5+-+#( V,-$A& -($*,+ <.= M,"5+-+#( V,-$A& A-," <.= +;3N -(AN*A5* 3>3
LOGIN FORM:
%rivate Sub cmdcancel9+lic$34 6nload 7e End Sub %rivate Sub cmdo$9+lic$34 )f txtusername.Text 1 :$amalesh: &nd txtpassword.Text 1 :cse: Then frmmenu..isible 1 True frmlogin..isible 1 0alse 6nload 7e Else 7sg*ox 3:%lease +hec$ ?our 6sername and %assword:4 txtusername.Set0ocus End )f End Sub
ata<.!ecordset3@4 1 TextA.Text ata<.!ecordset3A4 1 TextB.Text ata<.!ecordset3B4 1 Text=.Text ata<.!ecordset3=4 1 TextC.Text ata<.!ecordset3C4 1 TextD.Text ata<.!ecordset.6pdate 7sg*ox 3:!ecord Saved:4 End )f Text<.Text 1 :: Text@.Text 1 :: TextA.Text 1 :: TextB.Text 1 :: Text=.Text 1 :: TextC.Text 1 :: TextD.Text 1 :: +ommand@.Enabled 1 0alse End Sub %rivate Sub +ommandA9+lic$34 #n Error !esume "ext a 1 7sg*ox3:&!E ?#6 S6!EI:, vb?es"o, : E-ETE:4 )f a 1 vb?es Then ata<.!ecordset. elete 7sg*ox 3:!ecord eleted:4 Text<.Text 1 :: Text@.Text 1 :: TextA.Text 1 :: TextB.Text 1 :: Text=.Text 1 :: TextC.Text 1 :: TextD.Text 1 :: Text<.Set0ocus End )f End Sub
%rivate Sub +ommandB9+lic$34 ata<.!ecordset.Edit ata<.!ecordset3H4 1 Text<.Text ata<.!ecordset3<4 1 Text@.Text ata<.!ecordset3@4 1 TextA.Text ata<.!ecordset3A4 1 TextB.Text ata<.!ecordset3B4 1 Text=.Text ata<.!ecordset3=4 1 TextC.Text ata<.!ecordset3C4 1 TextD.Text +ommand@.Enabled 1 True End Sub %rivate Sub +ommand=9+lic$34 6nload 7e frmmenu.Show End Sub %rivate Sub +ommandC9+lic$34 +ommand@.Enabled 1 True Text<.Enabled 1 True Text@.Enabled 1 True TextA.Enabled 1 True TextB.Enabled 1 True Text=.Enabled 1 True TextC.Enabled 1 True TextD.Enabled 1 True ata<.!ecordset.&dd"ew End Sub %rivate Sub +ommandE9+lic$34 Text<.Enabled 1 True Text@.Enabled 1 True TextA.Enabled 1 True TextB.Enabled 1 True Text=.Enabled 1 True
TextC.Enabled 1 True TextD.Enabled 1 True im n9strsearch, e9strsearch &s String im namechec$, edichec$ &s -ong n9strsearch 1 )nput*ox3:Enter the *oo$ "ame to find:, :*oo$ "ame:4 e9strsearch 1 )nput*ox3:Enter the Edition:, :Edition:4 )f n9strsearch 1 :: #r e9strsearch 1 :: Then Exit Sub im n &s )nteger n1< ata<.!ecordset.7ove0irst )f ata<.!ecordset3H4 1 :: Then Exit Sub 8hile n F ata<.!ecordset.!ecord+ount namechec$ 1 )nStr3<, ata<.!ecordset3H4, n9strsearch, vbText+ompare4 edichec$ 1 )nStr3<, ata<.!ecordset3@4, e9strsearch, vbText+ompare4 )f namechec$ G H &nd edichec$ G H Then Text<.Text 1 ata<.!ecordset3H4 Text@.Text 1 ata<.!ecordset3<4 TextA.Text 1 ata<.!ecordset3@4 TextB.Text 1 ata<.!ecordset3A4 Text=.Text 1 ata<.!ecordset3B4 TextC.Text 1 ata<.!ecordset3=4 TextD.Text 1 ata<.!ecordset3C4 +ommandA.Enabled 1 True +ommandB.Enabled 1 True Exit Sub Else n1nJ< ata<.!ecordset.7ove"ext End )f 8end namechec$ 1 )nStr3<, ata<.!ecordset3H4, n9strsearch, vbText+ompare4 edichec$ 1 )nStr3<, ata<.!ecordset3@4, e9strsearch, vbText+ompare4 )f namechec$ G H &nd edichec$ G H Then Text<.Text 1 ata<.!ecordset3H4 Text@.Text 1 ata<.!ecordset3<4
TextA.Text 1 ata<.!ecordset3@4 TextB.Text 1 ata<.!ecordset3A4 Text=.Text 1 ata<.!ecordset3B4 TextC.Text 1 ata<.!ecordset3=4 TextD.Text 1 ata<.!ecordset3C4 +ommandA.Enabled 1 True +ommandB.Enabled 1 True Exit Sub Else 7sg*ox 3:"o records match your search:4 End )f End Sub %rivate Sub 0orm9-oad34 Text<.Enabled 1 0alse Text@.Enabled 1 0alse TextA.Enabled 1 0alse TextB.Enabled 1 0alse Text=.Enabled 1 0alse TextC.Enabled 1 0alse TextD.Enabled 1 0alse +ommand@.Enabled 1 0alse +ommandA.Enabled 1 0alse +ommandB.Enabled 1 0alse End Sub
RETIEVING FORM:
%rivate Sub +ommand<9+lic$34 ata<.!ecordset3H4 1 Text<.Text ata<.!ecordset3<4 1 Text@.Text ata<.!ecordset3@4 1 TextA.Text ata<.!ecordset3A4 1 TextB.Text ata<.!ecordset.6pdate 7sg*ox 3:!ecord updated:4
Text<.Text 1 :: Text@.Text 1 :: TextA.Text 1 :: TextB.Text 1 :: ata<.!ecordset.&dd"ew End Sub %rivate Sub +ommand@9+lic$34 6nload 7e frmmenu.Show End Sub %rivate Sub 0orm9)nitialize34 ata<.!ecordset.&dd"ew Text@.Text 1 0ormat3"ow, :dd(mm(yyyy:4 TextB.Text 1 0ormat3"ow J <=, :dd(mm(yyyy:4 End Sub
RETURN FORM:
#ption Explicit im t9strsearch &s String Sub func34 im to$ennochec$ &s -ong t9strsearch 1 )nput*ox3:Enter The To$en "umber:, :To$en "umber:4 )f t9strsearch 1 :: Then Exit Sub im n &s )nteger n1< im ach$ &s *oolean ach$ 1 0alse borrow. ata<.!ecordset.7ove0irst 8hile n F borrow. ata<.!ecordset.!ecord+ount to$ennochec$ 1 )nStr3<, borrow. ata<.!ecordset3H4, t9strsearch, vbText+ompare4 )f to$ennochec$ G H Then Text<.Text 1 t9strsearch
Text@.Text 1 0ormat3"ow, :dd(mm(yyyy:4 TextA.Text 1 borrow. ata<.!ecordset3A4 TextB.Text 1 borrow. ata<.!ecordset3@4 ach$ 1 True Exit Sub Else n1nJ< borrow. ata<.!ecordset.7ove"ext End )f 8end to$ennochec$ 1 )nStr3<, borrow. ata<.!ecordset3H4, t9strsearch, vbText+ompare4 )f to$ennochec$ G H Then Text<.Text 1 t9strsearch Text@.Text 1 0ormat3"ow, :dd(mm(yyyy:4 TextA.Text 1 borrow. ata<.!ecordset3A4 TextB.Text 1 borrow. ata<.!ecordset3@4 ach$ 1 True Exit Sub End )f )f ach$ 1 0alse Then 7sg*ox 3:)ncorrect to$en number:4 End )f End Sub %rivate Sub +ommand<9+lic$34 6nload 7e frmmenu.Show End Sub %rivate Sub +ommand@9+lic$34 ata<.!ecordset.&dd"ew ata<.!ecordset3H4 1 Text<.Text ata<.!ecordset3<4 1 Text@.Text ata<.!ecordset3@4 1 TextA.Text ata<.!ecordset3A4 1 TextB.Text
ata<.!ecordset.6pdate 7sg*ox 3:!ecords updated:4 Text<.Text 1 :: Text@.Text 1 :: TextA.Text 1 :: TextB.Text 1 :: End Sub %rivate Sub +ommandA9+lic$34 +all func End Sub %rivate Sub 0orm9-oad34 +all func End Sub
OUTPUT SCREEN:
LOGIN FORM:
MAIN MENU:
RETRIEVING FORM:
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: DATE:
BAN%ING SYSTEM
AIM: To solve the ban$ing system problem using +&SE tool for planning cost estimation, modeling the requirements and configuration management. SCOPE: The following subsection describes a scope of a new ban$ing system in terms of its avoidance, organization and applicable documents. AUDIENCE: The intended users are the people responsible for implementing the new ban$ing system. ORGANIZATION: This document describes the new ban$ing system requirements in terms of system requirements, executable summary analysis and design diagram. APPLICABLE DOCUMENTS: The following document provides the information necessary to understand the document. SYSTEM REQUIREMENT SPECIFICATION (SRS): The following subsection describes the new ban$ing system requirement system specification in terms of problem statement and feasibility study. PROBLEM STATEMENT: The new ban$ing 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. 8hile creating a new account the customer should specify the account type whether it is savings account or current account. VERB PRASING: The new ban$ing 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. 8hile creating a new account the customer should specify the account type whether it is savings account or current account.
USECASE DIAGRAM:
*erify edit transaction amount sa*ings account *erify transaction *erify account type manager current account cashier maintain database account creation transaction customer loan saction loan creation deposit by dd $ithdra$ edit account
by che7ue by cash
COLLABORATION DIAGRAM:
G."hecking F.7ithdraw D.*eposit the Amount B."reate Account $ser K. Amount (ransaction -yste m
SEQUENCE DIAGRAM:
$ser
$ser *etails
"reate%'
*eposit%'
alance%'
7ithdraw%'
(ransaction%'
%rivate Sub +ommandA9+lic$34 0ormC.Show 6nload 7e End Sub %rivate Sub +ommandB9+lic$34 End End Sub %rivate Sub +ommandC9+lic$34 0orm<.Show 6nload 7e End Sub %rivate Sub 0orm9-oad34 Set db 1 #pen atabase3:+,K ocuments and SettingsK$iteHLcs<@K es$topK.*.mdb:4 Set rs 1 db.#pen!ecordset3:&ccounts:4 End Sub F r$ 0: im db &s atabase im rs &s !ecordset %rivate Sub +ommand<9+lic$34 0ormA.Show 6nload 7e End Sub %rivate Sub +ommand@9+lic$34 0orm<.Show End Sub %rivate Sub 0orm9-oad34 Set db 1 #pen atabase3:+,K ocuments and SettingsK$iteHLcs<@K es$topK.*.mdb:4 Set rs 1 db.#pen!ecordset3:&ccounts:4 Text<.Enabled 1 0alse Text<.Text 1 rs.0ields3<4 End Sub F r$ 1: im db &s atabase im rs &s !ecordset im a &s )nteger %rivate Sub +ommandB9+lic$34 Text<.Text 1 :: End Sub %rivate Sub +ommandA9+lic$34 rs.Edit a 1 .al3Text<.Text4
rs.6pdate rs.Edit rs3<4 1 rs3<4 J a rs.6pdate 7sg*ox :deposit successfully:, vb#M#nly Text<.Text 1 :: End Sub %rivate Sub +ommand<9+lic$34 6nload 7e 0ormA.Show End Sub %rivate Sub +ommand@9+lic$34 6nload 7e 0orm<.Show End Sub %rivate Sub 0orm9-oad34 Text<.Text 1 :: Set db 1 #pen atabase3:+,K ocuments and SettingsK$iteHLcs<@K es$topK.*.mdb:4 Set rs 1 db.#pen!ecordset3:&ccounts:4 +ommand@.Enabled 1 0alse End Sub %rivate Sub Text<9+hange34 +ommand@.Enabled 1 True End Sub F r$ 2: im db &s atabase im rs &s !ecordset im a &s )nteger %rivate Sub +ommand@9+lic$34 Text<.Text 1 :: End Sub %rivate Sub +ommand<9+lic$34 rs.Edit a 1 .al3Text<.Text4 rs.6pdate rs.Edit rs3<4 1 rs3<4 ( a rs.6pdate 7sg*ox :withdraw successfully:, vb#M#nly Text<.Text 1 :: End Sub %rivate Sub +ommandA9+lic$34
0ormA.!efresh 6nload 7e 0ormA.Show End Sub %rivate Sub +ommandB9+lic$34 6nload 7e 0orm<.Show End Sub %rivate Sub 0orm9-oad34 Set db 1 #pen atabase3:+,K ocuments and SettingsK$iteHLcs<@K es$topK.*.mdb:4 Set rs 1 db.#pen!ecordset3:&ccounts:4 Text<.Text 1 :: +ommand@.Enabled 1 0alse End Sub %rivate Sub Text<9+hange34 +ommand@.Enabled 1 True End Sub
FORM DESIGN:
OUTPUT:
RESULT: Thus the ban$ing system using case tool for planning cost estimation, modeling the requirements and configuration management is developed successfully.
EX.NO: DATE:
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.
APPLICABLE DOCUMENTS:
The following provide information necessary to understand the document.
PROBLEM STATEMENT:
The new online shopping is beneficial for customers to purchase things from their wor$place itself with the help of computer. /ere 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. )n this process distributor also plays a main role. /e will access the details given by the customer and will do some modification to the product details when it is necessary. /e will also generate the product cost. The person called administrator will access all details and edit the information. /e also maintains the database. ¬her actor in this process is the billing system. This system is responsible for the mode of payment. /e 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. )t should allow the distributor to generate the product cost once the product is chosen, edit and access the product details. )t 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
$ser *etails Name of the customer Access No *ebit "ard No ;urchase%' "hecking%'
USECASE DIAGRAM
Distributor
credit cash
COLLABORATION DIAGRAM
G.;urchase F."heck the alance D.-elect the -pecific items from the list B.Adding the &ist of items
$ser
-ystem
SEQUENCE DIAGRAM
$ser ,tem $ser details
Add%'
Add $ser%'
-elect% '
;urchase%'
FORM DESIGN:
FORM #: %rivate Sub %icture<H9+lic$34 7E.Show End Sub %rivate Sub %icture<<9+lic$34 7D.Show End Sub %rivate Sub %icture<@9+lic$34 7L.Show End Sub %rivate Sub %icture@9+lic$34 7<.Show End Sub %rivate Sub %ictureA9+lic$34 7@.Show End Sub%rivate Sub %ictureB9+lic$34 7A.Show End Sub %rivate Sub %ictureC9+lic$34
7B.Show End Sub %rivate Sub %ictureE9+lic$34 7=.Show End Sub
FORM $: %rivate Sub +ommand<9+lic$34 rs.&dd"ew rs.0ields3H4 1 Text<.Text rs.0ields3<4 1 Text@.Text rs.0ields3@4 1 TextA.Text rs.0ields3A4 1 TextB.Text rs.0ields3B4 1 Text=.Text 7sg*ox :?#6! !EN6SE /&.E *EE" S6+ESS06--?: rs.6pdate End End Sub %rivate Sub +ommand@9+lic$34 7&)".Show
End Sub %rivate Sub 0orm9&ctivate34 7sg*ox :con"E+T)#" S6++ES06--?: Set con 1 "ew & # *.+onnection Set rs 1 "ew & # *.!ecordset con.#pen :%rovider17icrosoft.Oet.#-E *.B.HP ata Source1Q,K /EE"&K7? %!#OE+TKS/#%%)"'<.mdbP%ersist Security )nfo10alse: Rcon.#pen 3:%rovider17icrosoft.Oet.#-E *.B.HP ata Source1: J apppath J :7? %!#OE+TKS/#%%)"'<.mdbP%ersist Security )nfo10alse:4 rs.#pen :+ ET&)-S:, con, ad#pen ynamic, ad-oc$%essimistic End Sub
FORM &: %rivate Sub 0orm9-oad34 End Sub %rivate Sub -abel<9+lic$34 ME?<.Show End Sub %rivate Sub -abel<H9+lic$34 7&)".Show End Sub %rivate Sub -abel@9+lic$34 ME?@.Show End Sub
%rivate Sub -abelA9+lic$34 ME?A.Show End Sub %rivate Sub -abelB9+lic$34 ME?B.Show End Sub %rivate Sub -abel=9+lic$34 ME?=.Show End Sub %rivate Sub -abelC9+lic$34 ME?C.Show End 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:
DATE:
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. 3V #er: The intended voters are the people responsible for the online voting. 3E!e)#& ' O44&)&a!": The election officials maintains the candidate list, voters list, analysis and design documents. SApp!&)a5!e ( )-$e'#": The following document provide information necessary to 6nderstand about the online voting.
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 votings. 0or reasons of security, only the voter can access and edit their votes by entering their .oter ) . 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. 0or 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 *etails Name of the Voter Address *ate of b,rth Age -ector *istrict Voter ,d *ri!ing &icense 5ation "ard No ;assport No "hecking%' ;olling%' Add%' 5emo!e%' "andidate details Name of the Voter Address *ate of b,rth Age -ector *istrict -ymbol Name -ymbol 5egister%' 5egister%' ;olling%' 5emo!e%'
USECASE DIAGRAM
#oter
/ubmit id card
8olling officer
#erify !D card
Enter the *ote 9heck the *ote 9omputer -nnouncer 9ount the *ote -nnounces the result
COLLABORATION DIAGRAM
F. ;olling%' D. "andidate registration B. Voter 5egistration
$ser
-ystem
G.5esults %7inner'
SEQUENCE DIAGRAM
$ser Voter *etails "andidate *etails
Add Voter%'
Add "andidate%'
;olling%'
5esults %'
7inner *etails
FORM DESIGN:
#ptionA..alue 1 0alse #ptionB..alue 1 0alse #ption=..alue 1 0alse #ptionC..alue 1 0alse #ptionE..alue 1 0alse #ptionD..alue 1 0alse 7e./ide Exit Sub End )f rs.7ove"ext 8end Exit Sub End )f rs.7ove"ext 8end 7sg*ox :SorryT you are not able to vote:, vb+ritical )f rs.*#0 1 True Then Text<.Text 1 :: Else rs.7ove-ast RText<.Text 1 .al3rs.0ields3H44 J < End )f End )f End )f %rivate Sub cmdprevious9+lic$34 0ormL.Show +ombo<.Text 1 :: Text<.Text 1 :: #ption<..alue 1 0alse #ption@..alue 1 0alse #ptionA..alue 1 0alse #ptionB..alue 1 0alse #ption=..alue 1 0alse #ptionC..alue 1 0alse #ptionE..alue 1 0alse #ptionD..alue 1 0alse 7e./ide End Sub %rivate Sub 0orm9&ctivate34 R7sg*ox :+#""E+T)#" S6++ES06--?: Set con 1 "ew & # *.+onnection Set rs 1 "ew & # *.!ecordset con.#pen 3:%rovider17icrosoft.Oet.#-E *.B.HP ata Source1E,KdrK &T&*&SESKvoterlist.mdbP%ersist Security )nfo10alse:4 rs.#pen :erode:, con, ad#pen ynamic, ad-oc$#ptimistic
End Sub VOTE REGISTER FORM %rivate Sub cmdexit9+lic$34 0ormL.Show 7e./ide #ption<..alue 1 0alse #ption@..alue 1 0alse #ptionA..alue 1 0alse #ptionB..alue 1 0alse #ption=..alue 1 0alse #ption<.Enabled 1 True #ption@.Enabled 1 True #ptionA.Enabled 1 True #ptionB.Enabled 1 True #ption=.Enabled 1 True +ommand<.Enabled 1 True End Sub %rivate Sub +ommand<9+lic$34 +ommand<.Enabled 1 0alse )f #ption<..alue 1 True Then )f rs.0ields3H4 1 :!&O&7&")+M&7: Then rs.0ields3@4 1 .al3rs.0ields3@44 J < rs.0ields.!efresh rs.6pdate 7sg*ox :?#6! .#TE )S S6++ES06--? !E')STE!E : End )f Else )f #ption@..alue 1 True Then )f 3rs<.0ields3H4 1 :%!& EE%:4 Then rs<.0ields3@4 1 .al3rs<.0ields3@44 J < rs<.0ields.!efresh rs<.6pdate 7sg*ox :?#6! .#TE )S S6++ES06--? !E')STE!E : End )f Else )f #ptionA..alue 1 True Then )f 3rs@.0ields3H4 1 :S).&M67&!:4 Then rs@.0ields3@4 1 .al3rs@.0ields3@44 J < rs@.0ields.!efresh rs@.6pdate 7sg*ox :?#6! .#TE )S S6++ES06--? !E')STE!E : End )f Else )f #ptionB..alue 1 True Then
)f 3rsA.0ields3H4 1 :.).EM:4 Then rsA.0ields3@4 1 .al3rsA.0ields3@44 J < rsA.0ields.!efresh rsA.6pdate 7sg*ox :?#6! .#TE )S S6++ES06--? !E')STE!E : End )f Else )f #ption=..alue 1 True Then )f 3rsB.0ields3H4 1 :.E-67&"):4 Then rsB.0ields3@4 1 .al3rsB.0ields3@44 J < rsB.0ields.!efresh rsB.6pdate 7sg*ox :?#6! .#TE )S S6++ES06--? !E')STE!E : End )f End )f End )f End )f End )f End )f End Sub %rivate Sub 0orm9&ctivate34 Set con 1 "ew & # *.+onnection Set rs 1 "ew & # *.!ecordset con.#pen 3:%rovider17icrosoft.Oet.#-E *.B.HP ata Source1E,KdrK &T&*&SESKadminKE!# E+&" ) &TE!ES6-TSKE!# E<.7 *P%ersist Security )nfo10alse:4 rs.#pen :!&O&7&")+M&7:, con, ad#pen ynamic, ad-oc$#ptimistic rs.6pdate rs.0ields.!efresh End Sub ADMINISTRATOR LOGIN FORM im con &s "ew & # *.+onnection im rs &s "ew & # *.!ecordset %rivate Sub cmdchangepass9+lic$34 0orm@B.Show 7e./ide End Sub %rivate Sub +ommand<9+lic$34 0ormL.Show 7e./ide End Sub %rivate Sub 0orm9-oad34 text<.Text 1 ::
text@.Text 1 :: End Sub %rivate Sub cmdenter9+lic$34 )f 33Trim36+ase3rs.0ields3H444 1 Trim36+ase3text<.Text444 &nd 3Trim36+ase3rs.0ields3<444 1 Trim36+ase3text@.Text4444 Then 7 )0orm<.Show text<.Text 1 :: text@.Text 1 :: 7e./ide Else 7sg*ox : password is incorrect: text@.Text 1 :: text@.Set0ocus End )f End Sub %rivate Sub 0orm9&ctivate34 Set con 1 "ew & # *.+onnection Set rs 1 "ew & # *.!ecordset con.#pen :%rovider17icrosoft.Oet.#-E *.B.HP ata Source1E,KdrK &T&*&SESKadminK%&SS8#! S.mdbP%ersist Security )nfo10alse: rs.#pen :& 7)"%&SS8#! :, con, ad#pen ynamic, ad-oc$#ptimistic End 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.