CRICKET LEAGUE

A
Mini Project Report
Submitted in partial fulfilment of the
Requirements for the award of the Degree of

BACHELOR OF ENGINEERING

IN

INFORMATION TECHNOLOGY

By

B.MANISHA 1602-20-737-081

V.PAVAN KUMAR 1602-20-737-090

Department of Information Technology

Vasavi College of Engineering (Autonomous)
ACCREDITED BY NAAC WITH 'A++' GRADE
(Affiliated to Osmania University and Approved by AICTE)
Ibrahimbagh, Hyderabad-31
2021-2022
 Vasavi College of Engineering(Autonomous)

Ibrahimbagh, Hyderabad-31

Department of Information Technology

DECLARATION BY THE CANDIDATE

We,B.MANISHA(1602-20-737-081)V.PAVANKUMAR(1602-20-737-090),here by
declare that the Case study report entitled “CRICKET LEAGUE” under the guidance of
Mr. DAVID RAJU SIR, Assistant Professor , Department of Information Technology, VCE,
Hyderabad is submitted in partial fulfilment of the requirement for the course of
Software Engineering-Lab in BE 2/4 (IT) IV-Semester.

This is a record of bonafide work carried out by me and the Design embodied
in this project report has not been submitted by any other.

B.MANISHA
1602-20-737-081

V.PAVAN KUMAR
1602-20-737-090
 VasaviCollegeofEngineering(Autonomous)

Ibrahimbagh,Hyderabad-31
DepartmentofInformation technology

BONAFIDECERTIFICATE

We, B.MANISHA and V.PAVAN KUMAR bearing hallticketnumber,1602-20-737-

081,1602-20-737-090here by declare that the Case study report entitled “CRICKET
LEAGUE” under the guidance of MR. DAVID RAJU, Assistant Professor , Department of
Information Technology, VCE, Hyderabad is submitted in partial fulfilment of the
requirement for the course of Software Engineering-Lab inBE 2/4 (IT) IV-Semester.

This is a record of bonafide work carried out by me and the Design embodied
in this project report has not been submitted by any other.

B.MANISHA
1602-20-737-081
V.PAVAN KUMAR
1602-20-737-090

Mr. DAVID RAJU

Assistant professor, professor &HOD ,Internal
Guide. Dept of IT.
External Examiner
 ABSTRACT

This is a prediction game guided with Graphical User Interface. This can be used/played by anyone
who has basic cricket knowledge. The user must register himself and verify himself with his g-mail
account. The user will be given 500 points for registering himself. The user should select the
available matches. The user should invest his points on the options given. The user has freedom to
invest his money on both the options for the given question. If his options are correct then his points
will be doubled otherwise his invested points on the question will be halved. The project has an
admin login through which the admin sets the match between the teams competing and feeds the
answer for the question after the match has completed. The leaderboard positions will be shown with
all the registered users irrespective of the participation. The questions are quite simple, like more run
getters, more wickets etc., among the players shown as options.

This project is developed to provide fun of betting without investing a penny. We came across this
project looking at various advertisements during the Indian premier league. For doing this project,
we gained some basic knowledge about GUI programming in python. The package tkinter is used in
this project, it will provide the required GUI.
 Software Requirements Specification

(Word World)

1. Problem Statement: To collect software requirements and create software requirement

specification.

SOFTWARE REQUIREMENTS: Ms Word.

1. Introduction
1.1 Purpose Basic Description of Problem

The main purpose is to build an environment where the user can improve their vocabulary or
technical skills by guessing the correct form of word from the jumbled word or by guessing the
correct technical term by looking at given image. The system has two logins, one for the player
and other for admin.

1.2 Scope
The purpose of this specification is to document requirements for a system to manage
the word world application. The specification identifies what such a system is required to do.
The specification is written in a format conforming to the IEEE Standard 830-1984.Subject
to approval , the specification will complete the Requirements phase and will be followed by
detailed design, implementation, and testing.

1.3 Definitions, Acronyms, and Abbreviations

GUI-Graphical User Interface
1.4 References

1. IEEEStd830-
1998:IEEERecommendedPracticeforSoftwareRequirementsSpecification
2. J. Peters, and W. Pedrycz, Software Engineering – An Engineering Approach.
NewYork,NY:Wiley, 2000.
3. D.P.Gilliam,T.L.Wolfe,J.S.Sherif,andM.Bishop,“SoftwareSecurityChecklistfor
the Software Life Cycle,” in
Proc.WETICE’03,2003,pp.243-
248.
4. A.D. Rubin, “Security Considerations for Remote Electronic Voting,”
CACM,vol.45,pp.39-44,Dec.2002.
 1.5 Overview
This specification includes a brief product perspective and a summary of the functions
the software will provide. User characteristics are discussed, and any general constraints
or assumptions and dependencies are listed. Requirement statements are categorized as
functional requirements, performance requirements, non-functional requirements, or
design constraints. The rest of the document contains the overall description of the
system, requirements, data model and behavioral description of the system and project
planning.

2. General Description
2.1 Product Perspective
Cricket league is maintained by system where players have easy access to play the
game, even when they have to singly.
3. Specific Requirements
3.1 Functional Requirements
1.User Interface: The user is required to select which company is he interested in amongst the
various companies that have been provided.

2.Asp.net with SQL: As communication with user is performed in C# and data required for
processing is in a Database, a connectivity has to be implemented between the Database

3.2Advantages:

 Helps the users to relax and play for passing the time.
 It is simple and easy to play.
 People will get to know about betting system.
Disadvantages:

 Requires an active internet connection.

UML Introduction:
The UML is a language for specifying, constructing, visualizing, and documenting the software
system and its components. The UML is a graphical language with sets of rules and semantics. The
rules and semantics of a model are expressed in English in a form known as OCL (Object Constraint
Language). OCL uses simple logic for specifying the properties of a system. The UML is not intended
to be a visual programming language. However, it has a much closer mapping to object-oriented
programming languages, so that the best of both can be obtained. The UML is much simpler than
other methods preceding it. UML is appropriate for modeling systems, ranging from enterprise
information system to distributed web-based application and even to real time embedded system.

UML includes nine diagrams:

Use Case Diagram: To illustrate the user intersection with the system

Class Diagram: To illustrate logical structure.

Object Diagram: To illustrate the physical structure of the software.

Deployment Diagram: To shows the mapping of the software- hardware.

Interaction Diagram: To show the collaboration of group of objects.

Sequence & Collaboration:To illustrate behavior.

State Chart & Activity Diagram: To illustrate flow of events

Use-case Diagram: A use case diagram shows interactions of actors with a system interms of
functions called use-case. A use case is description of a functionality that
thesystemprovides.Theactorsareexternaltothesystembutwhointeractswiththesystem;
they maybe external persons, external system and hardware.

Class Diagram: A class diagram shows the static structure of classes in the system.

The classes represent the “things” that are handled in the system. Class can be related to
each other in a number of ways: associated, dependent, specialized or packaged. Class
represents attributes and operations.

Object Diagram: An object diagram is a variant of the class diagram and uses almost
identical notation. The difference between the two is that an object diagram shows a
number of object instances of classes, instead of actual classes. Objects are written in
rectangular box with their names. object diagrams are written in rectangular box with their
names. Object diagrams are not important as class diagrams but show the actual instances
of a class and the relationships.
 State Diagram: A state diagram is typically a component to the description of a class. Its
how all possible states that the object of the class can have, and which events cause the
state to change. An event can be another object that sends a message to it. A change is
called a transition. State diagrams are not drawn for all classes, only for those that have a
number of well-defined states.

State diagram can also be drawn for the system a saw hole.

Sequence Diagram: A sequence diagram shows a dynamic collaboration between a number

of objects and shows an interaction between objects. This diagram shows a number of
objects with vertical lines that represent object lifeline. Messages passing between objects
are shown with arrows. This represents the scenario of functions how they apply.

Collaboration Diagram: It is similar to a sequence diagram however the relationships are

only shown. If time or sequence of events is important then sequence diagrams are more
relevant.

Activity Diagram: An activity diagram shows a sequential flow of activities. This is typically
used to describe the activities performed in an operation.

Deployment Diagram: It represents the processors and devices to develop the system
,its how’s deployment view of the system.

Component Diagram: A component diagram shows the physical structure of the code in terms of
code components. A component can be a source code component, a
binarycomponentoranexecutablecomponent.Acomponentcontainsinformationaboutlogicalclassorcl
assesitimplemented
USECASEDIAGRAM

DEFINITION:

Use case Diagram is a collection of use cases, actors and relationships that
existsbetweenthem.Use-casediagramsgraphicallydepictsystembehavior(usecases).

Thesediagramspresentahigh-levelviewofhowthesystemisused asviewedfromanoutsider’s
(actor’s) perspective. A use-case diagram may depict all or some of the usecases ofasystem.

CONTENTS:
Ause-casediagramcancontain:

1. Actors("things"outsidethesystem):

Actorsrepresentsystemusers.Theyhelpdelimitthesystemandgiveaclearerpictureof whatthe
systemshould do. It is importantto note that an actor interacts with buthasnocontrol over
theusecases.

Anactorissomeoneorsomethingthat:

⮚ Interactswithorusesthesystem
⮚ Providesinputtoandreceivesinformationfromthesystem
⮚ Isexternaltothesystemandhasnocontrolovertheusecases

actor

2·Usecases(systemboundariesidentifyingwhatthesystemshoulddo):
Amoredetaileddescriptionmightcharacterizeausecaseas:

⮚ apatternofbehaviorthesystemexhibits
⮚ asequenceofrelatedtransactionsperformedbyanactorandthesystem
⮚ deliveringsomethingofvaluetotheactor.

Usecasesprovideameansto:

⮚ capturesystemrequirements
⮚ communicatewiththeendusersanddomainexperts
⮚ testthesystem

Use cases are best discovered by examining the actors and defining what the actor
willbeabletodo with thesystem.

use case

2. Interactions or relationshipsbetween actors and use cases in the system

includingtheassociations, dependencies, and generalizations.

Association Relationship: An association provides a pathway for communication.

Thecommunication can be between use cases, actors, classes or interfaces. Associations
arethe most general of all relationships and consequentially the most semantically weak.
Iftwoobjectsareusually consideredindependently,therelationshipisanassociation.

GeneralizationRelationship:

A generalize relationship is a relationship between a more general class or use case

andamorespecificclassorusecase.Ageneralizationisshownasasolid-linepathfromthe
more specific element to a more general element. The tip or a generalization is a
largehollowtriangle pointingtothemore generalelement.

actor1

actor3

actor2

DependencyRelationship:

A dependency is a relationship between two model elements in which a change to

onemodel element will affect the other model element. Use a dependency relationship
toconnect model elements with the same level of meaning. Typically, on class diagrams,
adependency relationship indicates that the operations of the client invoke operations
ofthesupplier.
USE CASE DIAGRAM:

AIM: To draw Use Case Diagram for Cricket League.

REQUIREMENTS:

HARDWARE:PIII Processor,512MBRAM,80GB

SOFTWARE: IBM software

Use cases:
The use cases in our system are Login, leader board, match setup, match bet, match
availability.

Actors involved:
 Player
 Admin
CLASS DIAGRAM

DEFINITION: A class diagram shows the existence of classes and their relationships in the logical
designof asystem. Aclassdiagrammayrepresentallorpartoftheclassstructureofasystem.
CONTENTS:
Aclassdiagramcontains
1. Classes
2. Relationships
3. Interfaces
1) Classes:
A class is a set of objects that share a common structure and commonbehavior (the same
attributes, operations, relationships and semantics). Aclass is an abstraction of real-world items.
When these items exist in therealworld,theyareinstancesoftheclassandarereferredtoasobjects.

class

2) Relationships:
AggregateRelationship
Use the aggregate relationship to show a whole and part relationship betweentwo classes.The
class at the client end of the aggregate relationship is sometimescalled the aggregate class. An
instance of the aggregate class is anaggregate object. The class at the supplier end of the
aggregaterelationship is the part whose instances are contained or owned by the aggregate object.

supplierA client Supplier B

AssociationRelationship

An association provides a pathway for communication. The communication canbe between use
cases, actors, classes or interfaces. Associations are the mostgeneral of all relationships and
consequentially the most semantically weak.
Iftwoobjectsareusuallyconsideredindependently,therelationshipisanassociation

association

class1 class2

DependencyRelationship

Adependencyisarelationshipbetweentwomodelelementsinwhichachangetoonemodel
element will affect the other model element. Use a dependency relationship
toconnectmodelelements with thesame levelofmeaning

GeneralizeRelationship:A generalize relationship between classes shows that the subclass

shares the structureor behavior defined in one or more super classes. Use a generalize
relationship to showa"is-a"relationship betweenclasses.

superclass

subclass1 subclass2
RealizeRelationship

A realization is a relationship between classes, interfaces, components, and

packagesthatconnectsaclientelementwithasupplierelement.Arealizationrelationshipbetween
classes and interfaces and between components and interfaces shows that theclassrealizes
the operations offered bytheinterface.

3) Interfaces

An interface specifies the externally visible operations of a class and/or component, andhas
no implementation of its own. An interface typically specifies only a limited part
ofthebehaviorofaclassorcomponent.

Interfacesbelongtothelogicalviewbutcanoccurinclass,usecaseandcomponentdiagrams.

An interface in a component diagram is displayed as a small circle with a line to

thecomponentthat realizes theinterface:

Adornments

You can further define an interface using the Class Specification. Some
classspecificationfieldscorrespondtoadornmentandcompartmentinformationthatyoucandis
playintheclassdiagram.

DIAGRAM:

AIM:To draw simple Class diagram for Cricket league.

REQUIREMENTS:

HARDWARE: PIII Processor ,512MBRAM,80GB

SOFTWARE:IBM software using Class diagram tools.

SEQUENCEDIAGRAM

A sequence diagram is a graphical view of a scenario that shows object interaction in a time-
basedsequence what happensfirst,what happens next.
Sequencediagramsestablishtherolesofobjectsandhelpprovideessentialinformationtodetermine
classresponsibilities andinterfaces.
Thistypeofdiagramisbestusedduringearlyanalysisphasesindesignbecausetheyaresimpleandeasy
tocomprehend.
Sequencediagramsarenormallyassociatedwithusecases.
Sequencediagramsarecloselyrelatedtocollaborationdiagramsandbotharealternaterepresentationsof
aninteraction.
Therearetwomaindifferencesbetweensequenceandcollaborationdiagrams:

Sequencediagramsshowtime-based objectinteraction

Whilecollaborationdiagramsshowhowobjectsassociatewitheachother.

CONTENTS:

A sequence diagram has two dimensions: typically, vertical placement represents

timeandhorizontalplacement representsdifferentobjects.

Thefollowingtoolslocatedonthesequencediagramtoolboxenableyoutomodelsequencediagrams
:

Object:Anobjecthasstate,behavior,andidentity.Thestructureandbehaviorofsimilar objects are

defined in their common class. Each object in a diagram
indicatessomeinstanceofaclass.Anobjectthatisnotnamedisreferred toasaclassinstance.

If you use the same name for several object icons appearing in the same collaboration
oractivity diagram, they are assumed to represent the same object; otherwise, each objecticon
represents a distinct object. Object icons appearing in different diagrams denotedifferent
objects, even if their names are identical. Objects can be named three differentways:object
name,objectnameandclass,orjustbytheclassnameitself.

MessageIcons:Amessageiconrepresentsthecommunicationbetweenobjectsindicatingthatanacti
onwillfollow.Themessageiconisahorizontal,solidarrowconnectingtwolifelinestogether.Thefoll
owingmessageiconsshowthreedifferent
waysamessageiconcanappearmessageicononly,messageiconwithsequencenumber,andmessage
iconwithsequencenumber and messagelabel.

Each message icon represents a message passed between two objects, and indicates
thedirection of message is going. A message icon in a collaboration diagram can
representmultiplemessages.Amessageiconinasequencediagramrepresentsexactlyonemessage.

FocusofControl:FocusofControl(FOC)isanadvancednotational technique thatenhances

sequence diagrams. It shows the period of time during which an object
isperforminganaction,eitherdirectlyorthroughanunderlyingprocedure.FOCisportrayed through
narrow rectangles that adorn lifelines. The length of an FOC indicates
theamountoftimeittakesforamessagetobeperformed.Whenyoumoveamessagevertically, each
dependent message will move vertically as well. Also, you can move a FOCvertically off of
the source FOC to make it detached and independent. An illustration of
asequencediagramwithFOC notation follows:

MessagetoSelf:AMessagetoSelfisatoolthatsendsamessagefromoneobjectbacktothe same
object. It does not involve other objects because the message returns to the sameobject.The
sender ofamessageisthe same asthereceiver.

Note:Anotecapturestheassumptionsanddecisionsappliedduringanalysisanddesign. Notes may

contain any information, including plain text, fragments of code, orreferences to other
documents. Notes are also used as a means of linking diagrams.
Anoteholdsanunlimitedamountoftextand canbe sized accordingly.
 Notes behave like labels. They are available on all diagram toolboxes, but they are
notconsideredpartofthemodel. Notesmaybedeleted likeanyotheritemonadiagram.

DIAGRAM:

AIM:Todrawsequencediagramfor Cricket league.

REQUIREMENTS:

HARDWARE:PIIIProcessor,512MBRAM,80GB

SOFTWARE:IBM software.
COLLABORATION DIAGRAM

Collaborationdiagramsandsequencediagramsarealternaterepresentationsofaninteraction. A
collaboration diagram is an interaction diagram that shows the order ofmessages that
implement an operation or a transaction. A sequence diagram showsobjectinteraction in
atime-based sequence.

Collaboration diagrams show objects, their links, and their messages. They can alsocontain
simple class instances and class utility instances. Each collaboration diagramprovides a view
of interactions or structural relationships that occur between objectsandobject-like entitiesin
thecurrentmodel.
TheCreateCollaborationDiagramCommandcreatesacollaborationdiagramfrominformationcont
ainedinthesequencediagram.TheCreateSequenceDiagramCommandcreatesasequencediagramf
rominformationcontainedintheinteraction's collaboration diagram. The Go to Sequence
Diagram and Go to CollaborationDiagramcommandstraverse betweenaninteraction's
tworepresentations.
Collaboration diagrams contain icons representing objects. You can create one or
morecollaboration diagrams to depict interactions for each logical package in your
model.Such collaboration diagrams are themselves contained by the logical package
enclosingtheobjects theydepict.

AnObjectSpecificationenablesyoutodisplayandmodifythepropertiesandrelationshipsof
anobject.Theinformationinaspecificationispresentedtextually.Some of this information can
also be displayed inside the icons representing objects incollaborationdiagrams.
Youcanchangepropertiesorrelationshipsbyeditingthespecificationormodifying
the icon on the diagram. The associated diagrams or specifications are automaticallyupdated.

During:Analysis

UseCollaborationDiagrams:ToIndicatethesemanticsoftheprimaryandsecondaryinteractions.

DesignShowthesemanticsofmechanismsinthelogicaldesignofthesystem.
Usecollaborationdiagramsastheprimaryvehicletodescribeinteractionsthatexpressyourdecisions
aboutthe behaviorofthesystem.

Object:

An object has state, behavior, and identity. The structure and behavior of similar objects
aredefined in their common class. Each object in a diagram indicates some instance of a class.An
objectthatis notnamedisreferredto asaclassinstance.
 If you use the same name for several object icons appearing in the same collaboration
oractivity diagram, they are assumed to represent the same object; otherwise, each objecticon
represents a distinct object. Object icons appearing in different diagrams denotedifferent
objects, even if their names are identical. Objects can be named three differentways:object
name,objectnameandclass, orjustbytheclassnameitself.

If you specify the name of the object's class in the Object Specification, the name
mustidentifyaclassdefined inthe model.

GraphicalDepiction

Theobjecticonissimilartoa classiconexceptthatthenameisunderlined:
If you have multiple objects that are instances of the same class, you can modify
theobjecticonbyclickingMultipleInstancesintheObjectSpecification.Whenyouselectthisfield,th
eiconis changedfromoneobject tothree staggeredobjects:

Concurrency

Anobject's concurrencyis definedbytheconcurrencyofitsclass.

YoucandisplayconcurrencybyclickingShowConcurrencyfromtheobject'sshortcutmenu.The
adornmentis displayed atthebottomoftheobjecticon.
DIAGRAM:

AIM: To draw Collaboration diagram for Cricket league.

REQUIREMENTS:

HARDWARE:PIIIProcessor,512MBRAM,80GB

SOFTWARE:IBM software using Collaboration tool.

ACTIVITYDIAGRAM

DEFINITION:
Activity diagrams provide a way to model the workflow of a business process. You canalso use
activity diagrams to model code-specific information such as a class operation.Activity
diagrams are very similar to a flowchart because you can model a workflowfromactivity
toactivity.
An activity diagram is basically a special case of a state machine in which most of thestates are
activities and most of the transitions are implicitly triggered by completion oftheactions in the
source activities. The main difference between activity diagrams and state charts is activity
diagramsareactivitycentric, while state chartsare state centric.

An activity diagram is typically used for modeling the sequence of activities in a

process,whereasastatechartisbettersuitedtomodelthediscretestagesofanobject’slifetime.

CONTENTS:
ActivityDiagramTools
Youcanusethefollowingtoolsontheactivitydiagramtoolboxtomodelactivitydiagrams:

Activities: An activity represents the performance of task or duty in a workflow.

Itmayalsorepresenttheexecutionofastatementinaprocedure.Anactivityissimilartoa state but
expresses the intent that there is no significant waiting (for events) in anactivity. Transitions
connect activities with other model elements and object flowsconnectactivities withobjects.

Decisions: A decision represents a specific location on an activity diagram or statechart

diagram where the workflow may branch based upon guard conditions.
Theremaybemorethantwooutgoingtransitionswithdifferentguardconditions,butforthemost
part, a decision will have only two outgoing transitions determined by a Booleanexpression

End State: An end state represents a final or terminal state on an activity diagram orstate
chart diagram. Place an end state when you want to explicitly show the end of aworkflow on
an activity diagram or the end of a state chart diagram. Transitions canonlyoccurintoanend
state;however, therecan beany
numberofendstatespercontext.

Object: Rational Rose allows objects on activity, collaboration, and sequence diagrams.Specific
to activity diagrams, objects are model elements that represent something youcan feel and touch. It
might be helpful to think of objects as the nouns of the activitydiagram and activities as the verbs
of the activity diagram. Further, objects on activitydiagrams allow you to diagram the input and
output relationships between activities. Inthe following diagram, the Submit Defect and Fix
Defects can be thought of as the verbsand the defect objects as the nouns in the activity diagram
vocabulary. Objects areconnected toactivities throughobject flows.

Object Flow: An object flow on an activity diagram represents the relationship

betweenanactivityand theobjectthatcreates it(asanoutput)orusesit(asaninput).
RationalRosedrawsobjectflowsasdashedarrowsratherthansolidarrowstodistinguish them from
ordinary transitions. Object flows look identical to
dependenciesthatappearonotherdiagramtypes.

Start State: A start state (also called an "initial state") explicitly shows the beginning ofa
workflow on an activity diagram or the beginning of the execution of a state machineon a
state chart diagram. You can have only one start state for each state
machinebecauseeachworkflow/executionofastatemachine beginsinthesameplace.

Normally, only one outgoing transition can be placed from the start state. However,multiple
transitions may be placed on a start state if at least one of them is labeled withacondition. No
incomingtransitions areallowed.

States: A state represents a condition or situation during the life of an object duringwhich it
satisfies some condition or waits for some event. Each state represents
thecumulativehistoryofits behavior.

Swim lanes: Swim lanes are helpful when modeling a business workflow because
theycanrepresentorganizationalunitsorroleswithinabusinessmodel.Swimlanesareverysimilarto
anobjectbecausetheyprovideawaytotellwhoisperformingacertainrole. Swim lanes only appear
on activity diagrams. You should place activities withinswim lanes to determine which unit is
responsible for carrying out the specific activity.Formore informationonswim lanes, lookat
theswim lanesample.

When a swim lane is dragged onto an activity diagram, it becomes a swim lane
view.Swimlanesappearassmalliconsinthebrowserwhileaswimlaneviewsappearbetweenthethin,
verticallineswithaheaderthatcanberenamedandrelocated.

Synchronizations: Synchronizations enable you to see a simultaneous workflow in

anactivity diagram or state chart diagram. Synchronizations visually define forks and
joinsrepresentingparallelworkflow.
 Transitions:A state transition indicates that an object in the source state will performcertain
specified actions and enter the destination state when a specified event occurs
orwhencertainconditionsaresatisfied.Astatetransitionisarelationshipbetweentwostates,two
activities, or between an activityandastate.

Youcanshowoneormorestatetransitionsfromastateaslongaseachtransition

isunique.Transitionsoriginatingfromastatecannothavethesameevent,unlessthereareconditions
on the event.

DIAGRAM:
AIM:TodrawActivitydiagramfor Cricket league.

REQUIREMENTS:

HARDWARE:PIIIProcessor,512MBRAM,80GB
SOFTWARE: IBM software .
 COMPONENTDIAGRAM

Componentdiagramsprovideaphysicalviewofthecurrentmodel.Acomponentdiagramshowstheo
rganizationsanddependenciesamongsoftwarecomponents,includingsourcecodecomponents,bin
arycodecomponents,andexecutablecomponents. These diagrams also show the externally
visible behavior of the componentsby displaying the interfaces of the components. Calling
dependencies among
componentsareshownasdependencyrelationshipsbetweencomponentsandinterfacesonotherco
mponents. Note that the interfaces actually belong to the logical view, but they can
occurbothin classdiagramsandincomponentdiagrams.

Componentdiagramscontain:

Componentpackages:Componentpackagesrepresentclustersoflogicallyrelated components,
or major pieces of your system. Component packages parallel theroleplayedby
logicalpackagesfor classdiagrams.Theyallowyoutopartitionthephysicalmodel ofthesystem.

Components: A component represents a software module (source code,

binarycode,executable,DLL,etc.)withawell-
definedinterface.Theinterfaceofacomponentisrepresentedbyoneorseveralinterfaceelementsthat
thecomponentprovides.Components are used to show compiler and run-time dependencies, as
well as interfaceand calling dependencies among software modules. They also show which
componentsimplementaspecific class.

Asystemmaybecomposedofseveralsoftwaremodulesofdifferentkinds.Eachsoftware module is
represented by a component in the model. To distinguish
differentkindsofcomponentsfromeachother,stereotypes are used.
 Interfaces:Aninterfacespecifiestheexternally-visibleoperationsofaclassand/orcomponent, and

has no implementation of its own. An interface typically specifies only alimited

partofthebehaviorofaclassorcomponent.
·Dependencyrelationships:Adependencyisarelationshipbetweentwomodelelements in which
a change to one model element will affect the other model
element.Useadependencyrelationshiptoconnectmodelelementswiththesamelevelofmeaning.Ty
pically,onclassdiagrams,adependencyrelationshipindicatesthattheoperationsof theclientinvoke
operationsofthesupplier.

You can create one or more component diagrams to depict the component packages
andcomponents at the top level of the component view, or to depict the contents of
eachcomponent package. Such component diagrams belong to the component package
thattheydepict.

A Component Package Specification enables you to display and modify the properties ofa
component package. Similarly, a Component Specification and a Class Specificationenables
you to display and modify the properties of a component and an interface,respectively. The
information in these specifications is presented textually. Some of thisinformation can also be
displayed inside the icons representing component
packagesandcomponentsincomponentdiagrams, and interface sin class
diagrams.Youcanchangepropertiesof,orrelationshipsamong,componentpackages,components,
and interfaces by editing the specification or modifying the icon on
thediagram.Theaffecteddiagramsorspecificationsareautomaticallyupdated.

DIAGRAM:
AIM:TodrawComponentdiagram and for Cricket league.
REQUIREMENTS: HARDWARE :PIIIProcessor,512MBRAM,80GB.
SOFTWARE : IBM software.
STATE CHART DIAGRAM

AIM:TodrawState chart diagramforStock market analysis

REQUIREMENTS:

HARDWARE :PIIIProcessor,512MBRAM,80GB

SOFTWARE : IBM software.

DESCRIPTION:

The state chart diagram contains the states in the rectangle boxes and starts in indicated by the dot
and finish is indicated by dot encircled. The purpose of state chart diagram is to understand the
algorithm in the performing method. State diagram describes the flow of control from one state to
another state. States are defined as a condition in which an object exists and it changes when some
event is triggered.

• As the name suggests, it describes different states of a Object in a system.

• State Diagrams show the sequences of states an object goes through during its life cycle.
• State diagram describes the flow of control from one state to another state. States are defined
as a condition in which an object exists and it changes when some event is triggered.
• The states are specific to a component/object of a system.
• Objects in the system change status in response to events. Used to model dynamic nature of a
system.
Diagram:
 DEPLOYMENTDIAGRAM

Adeploymentdiagramshowsprocessors,devices,andconnections.Eachmodelcontainsasingled
eploymentdiagramwhichshowstheconnectionsbetweenitsprocessorsand devices,and
theallocation ofitsprocessesto processors.

Processor Specifications, Device Specifications, and Connection Specifications enableyou

to display and modify the respective properties. The information in a
specificationispresentedtextually;someofthisinformationcanalsobedisplayedinsidetheicons.

Youcanchangepropertiesorrelationshipsbyeditingthespecificationormodifyingthe icon on
the diagram. The deployment diagram specifications are automaticallyupdated.

CONTENTS:

Processor:-Aprocessorisahardwarecomponentcapableofexecutingprograms.

Devices:
Adeviceisahardwarecomponentwithnocomputingpower.Eachdevicemusthaveaname.
Devicenamescanbegeneric, such as"modem"or"terminal."

Connections:
A connection represents some type of hardware coupling between two entities. Anentity
is either a processor or a device. The hardware coupling can be direct, such asan RS232
cable, or indirect, such as satellite-to-ground communication. Connectionsareusuallybi-
directional.
DIAGRAM:

AIM:TodrawDeploymentdiagramforWord world.

REQUIREMENTS:

HARDWARE :PIIIProcessor,512MBRAM,80GB

SOFTWARE:IBM software using Deploymentdiagramtools.

 Application and web modelling

Aim: To generate a java code from a UML class diagram for Passport Automation System
Software Tools used: Rational Software Architect
Description: Software development is a process by which standalone or individual software is
created using a specific programming language. Software development may also be called
application development and software design.
Application development is basically the process of creating a computer program or set of
programs that can assist the daily functionalities of the user or business.
This is the “original” type of programming. These are ‘standard’ applications that perform their
duties on traditional desktop operating systems, such as Windows, Mac, or Linux. It’s often
considered a programme, executed on demand by the user, that opens its interface in the confines
of the OS that it’s running in.
Java, VB.NET, C/C++,C#, Python.
Procedure:
1. Open RSA:File->New->Project
2. Select a wizard as UML Project
3. Enter Project Name
4. Under Create new UML Model Template Blank Model
5. Click Finish.
6. Design a class diagram/Select Existing Model and the Save the diagram.
7. Select Blank model
8. Go to menu bar :Modeling ->Transfer -> New Configuration.
9. Enter file name of transformation
10. Under forward Transformation IBM Rational Transformations
11. Select UML to Javav5.0next
12. Under source and target
13. Select your project from source
14. Project name->models->Blank model
15. Click create new target container.
16. Enter Java code Project Name(Passport Java)-->Next
17. Java Settings-->Finish, then(observe Target as Project Name Java)
18. Click Next
19. UML to Java Options-->Next
20. Collections click Next
21. Mapping-->Next
22. Common->Next
23. Select Transformation Options as create source to target relationship.
24. Click Finish.
25. From the Project Explorer ,select Passport UML to JavaCode.tc->Right click->Transform->
UML to Javav5.0
26. From Explorer:- Expand Passport Java Folder->Expand default package->See your
classes,Java files
27. Double Click filename.Java file you can see Java Code.
 CONFIGURATION MANAGEMENT

Aim: To configure the multiple users for assigning project - Passport Automation System
Software Tools used: IBM Rational Quality Manager
Description: Configuration management is a comprehensive engineering process which keeps track
and logs of all the changes which are made on the software by the different users until the product
goes live. This process aids the software developers to encounter and fix any fault which occur
during the development or testing phase. Every development team maintains a software
configuration and maintenance document to manage the projects in the most efficient manner.

Procedure:
To Create new user -

Step 1 : click on Admin

Step 2 : Select Jazz User Administration

Step 3 : Click on Create User

Step 4:Complete the page as needed and Save

 Username,UserID, Email ID
 Go to Client Access Licenses in the same
o Select Rational Quality Manager-Quality Manager
o Select Rational Quality Manager-Connector

Step 5: Now Go to Active Users list and check the user id created or not.

To Assign a project to the new user –

Step 1 : click on Admin

Step 2 : Select Jazz Project Administration

Step 3: select a project

Step 4: click on add in the member menu

Step5:give username to which you to assign the project

Step 6:save

Step 7:Login with the new user id and password in Quality manager

Step 8:The tool must provide only the project to which the user has got assigned.

Output:
 TESTCASES

A good TestCasetemplate maintains test artifact consistency for the test teamand makes it
easy for all stakeholders to understand the test cases. Writing testcase in a standard format
lessen the test effortand the error rate. Test
casesformataremoredesirableincaseifyouarereviewingtestcasefromexperts.
TestCaseField Description

TestcaseID: · Each test case should be represented by a

uniqueID.Toindicatetesttypesfollowsomeconventionlik
e"TC_UI_1"indicating"UserInterfaceTestCase#1."

TestPriority: · Itisusefulwhileexecutingthetest.

o Low

o Medium

o High

Name of ·Determinethenameofthemainmoduleorsub-
modulebeingtested
theModule:

TestDesignedby: ·Tester'sName

Date of ·Datewhentestwasdesigned

testdesigned:

TestExecutedby: ·Whoexecutedthetest-tester

Date of the ·Datewhentestneedstobeexecuted

TestExecution:

NameorTestTitle: ·Titleofthetestcase
Description/ ·Determinethesummaryortestpurposeinbrief
SummaryofTest:

Pre-condition: ·Anyrequirementthatneedstobedonebeforeexecution of this

test case. To execute this testcaselist all pre-conditions

Dependencies: · Determine any dependencies on

testrequirementsorother testcases

TestSteps: · Mention all the test steps in detail and write in theorder
in which it requires to be executed.
Whilewritingteststepsensurethatyouprovideasmuchdeta
ilasyou can

TestData: ·Useoftestdataasaninputforthetestcase.Deliverdifferentdata
setswithprecisevaluestobeused asaninput

ExpectedResults: ·Mentiontheexpectedresultincludingerrorormessagethat
shouldappearonscreen
 Post-Condition: ·Whatwouldbethestateofthesystemafterrunningthe test case?

ActualResult: ·Aftertestexecution,actualtestresultshouldbefilled

Status(Fail/Pass): ·Markthisfieldasfailed,ifactualresultisnotasperthe estimated

result

Notes: ·Iftherearesomespecialconditionwhichisleftinabovefield

Output:

38
 FUNCTIONALITY TESTING

AIM – To Test the Functionality of the project using Rational Functional Tester.

TOOLS REQUIRED – IBM Software Delivery Platform(Rational Functional Tester).

Functional Testing :Functional Testing is a testing technique that is used to test the
features/functionality of the system or Software, should cover all the scenarios.
Functional testing is a way of checking software to ensure that it has all the required
functionality that's specified within its functional requirements.

Create Functional TesterProject-

STEP 1 – Click on IBM Software Delivery platform

STEP 2 - Click on Rational Functional Tester

STEP 3 - Click on Java Scripting

STEP 4 – Create a workspace

STEP 5 -click on File ->New ->Functional Tester Project

Enable Environments for the project to test

STEP 1 – Click on Configure

STEP 2 - Click on Enable environment to test

STEP 3 - Click on finish

Steps for Functional Testing:

STEP 1 – Click on Configure

STEP 2 - Click on Configure application for testing

STEP 3 – select application

Step 4 -run

Application starts

STEP 5 -Minimize the application window and tool window

39
STEP 6 – click on record icon to record the script

STEP 7 -Select project and select Script, click Next and Finish

STEP 8- Run the application for a while and click on Stop button on Recording window

STEP 9 -Click on Run Test script button to play the recorded Functionality testin

To check log record:

Step1:Go to project folder ->Project_logs

40