+ All Categories
Home > Documents > practical-4.docx

practical-4.docx

Date post: 02-Jun-2018
Category:
Upload: sanket-shah
View: 212 times
Download: 0 times
Share this document with a friend

of 17

Transcript
  • 8/10/2019 practical-4.docx

    1/17

    A0IM: Upload a doc file containing Description of your project, scope, limitations,

    functional and non functional requirements, different UML diagrams and TIME Line and

    antt c!art"

    #"# $lass Diagram

    The class diagram is a static diagram. It represents the static view of an application. Class

    diagram is not only used for visualizing, describing and documenting different aspects of a

    system but also for constructing executable code of the software application. The class diagram

    describes the attributes and operations of a class and also the constraints imposed on the system.

    Manager

    +Name: Char+Id:Integer+Tel_No: Integer+Address:Char

    +Complain_Record()+Purchase_Stock()

    Stock

    +Name: Char+Status: Char

    rder!""#

    $

    Chef

    +Id: Integer+Name: Char+Tel_No: Integer+Address: Char

    +Take_rders()

    Customers

    +Id: Integer

    +Name: Char+Tel_No: Integer+Address: Char+RoomNo: Integer

    +Check_in()+Check_out()+Pa%_ &ill()+rder_'ood_Item()

    Room

    +Room_No: Integer+ocation: Char

    Receptionalist

    +Id: Name+Name: Char+Tel_No: Integer+Address: Char

    +Check_room_aaila*ilit%()+&oo_room()+enerate_&ill()+Take_Customer_'eed*ack()

    Food Items

    +Id: Integer+Name: Char

    +,ake -elier%() Hotel Attendant

    +Id: Integer+Name: Char

    Bill

    +&ill_No: I nteger+Customer_Name: Char

    Take 'eed &ack

    $""#

    $

    &ook

    &ook

    enerate

    !""#

    $

    Pa% &ill

    $

    $

    ,akes

    $""#

    $""#rder

    -elier

    [Fig a! Class "iagram#

  • 8/10/2019 practical-4.docx

    2/17

    #"% Use case Diagram

    $se case diagrams are considered for high level re%uirement analysis of a system. &o when

    the re%uirements of a system are analyzed the functionalities are captured in use cases.

    &o we can say that uses cases are nothing but the system functionalities written in an

    organized manner. 'ow the second things which are relevant to the use cases are the actors.

    (ctors can be defined as something that interacts with the system.

    The actors can be human user, some internal applications or may be some external

    applications. &o in a brief when we are planning to draw an use case diagram we should have

    the following items identified.

    Functionalities to be represented as an use case

    (ctors

    )elationships among the use cases and actors.

  • 8/10/2019 practical-4.docx

    3/17

    S%stemCheck Room Availibility

    Book Return

    Received ayment

    Cancel Bookig

    Reception

    Receiving order

    lace order for tea! cofee

    Ask for room

    Cancel Booking

    Chec" in

    Check"out

    Customer

    #ake rovide Room

    $eliver the order

    Sta%

    &enerate Report

    Maintain AccountAccount

    [Fig b! $se case "iagram#

  • 8/10/2019 practical-4.docx

    4/17

    #"& 'tate Diagram

    &tate chart diagram is one of the five $*+ diagrams used to model dynamic nature of a

    system. They define different states of an obect during its lifetime. (nd these states are

    changed by events. &o &tate chart diagrams are useful to model reactive systems. )eactive

    systems can be defined as a system that responds to external or internal events.

    &tate chart diagram describes the flow of control from one state to another state. &tates are

    defined as a condition in which an obect exists and it changes when some event is triggered.

    &o the most important purpose of &tate chart diagram is to model life time of an obect from

    creation to termination.

    &tate chart diagrams are also used for forward and reverse engineering of a system. -ut the

    main purpose is to model reactive system.

    Following are the main purposes of using &tate chart diagrams

    To model dynamic aspect of a system.

    To model life time of a reactive system.

    To describe different states of an obect during its life time.

    "efine a state machine to model states of an obect.

  • 8/10/2019 practical-4.docx

    5/17

    [Fig c! lms/Issue state "iagram#

  • 8/10/2019 practical-4.docx

    6/17

    [Fig c! lms/return state "iagram#

  • 8/10/2019 practical-4.docx

    7/17

  • 8/10/2019 practical-4.docx

    8/17

    [Fig d! lms/Issue se%uence "iagram#

  • 8/10/2019 practical-4.docx

    9/17

  • 8/10/2019 practical-4.docx

    10/17

    [Fig d! lms/return se%uence "iagram#

    #") Acti*ity Diagram

    The basic purposes of activity diagrams are similar to other four diagrams. It captures the

    dynamic behavior of the system. 2ther four diagrams are used to show the message flow

    from one obect to another but activity diagram is used to show message flow from one

    activity to another.

    (ctivity is a particular operation of the system. (ctivity diagrams are not only used for

    visualizing dynamic nature of a system but they are also used to construct the executable

    system by using forward and reverse engineering techni%ues. The only missing thing in

    activity diagram is the message part.

    It does not show any message flow from one activity to another. (ctivity diagram is some

    time considered as the flow chart. (lthough the diagrams loo3s li3e a flow chart but it is not.

    It shows different flow li3e parallel, branched, concurrent and single.

    &o the purposes can be described as

    "raw the activity flow of a system.

    "escribe the se%uence from one activity to another.

    "escribe the parallel, branched and concurrent flow of the system.

  • 8/10/2019 practical-4.docx

    11/17

  • 8/10/2019 practical-4.docx

    12/17

  • 8/10/2019 practical-4.docx

    13/17

    [Fig e! lms/issue (ctivity "iagram#

  • 8/10/2019 practical-4.docx

    14/17

    [Fig f! lms/return (ctivity "iagram#

  • 8/10/2019 practical-4.docx

    15/17

    #"+ antt $!art

    ( 4antt chartis a type of bar chart, which graphically shows the progress of a proect or

    wor3 effort, against a proect schedule or timeline. 4antts visually illustrate when proect

    wor3 is due to start, how much of it has been completed so far, and how much more needs to

    be done. The power of a 4antt chart is that it is graphical, unli3e a text list or 5xcel table,which ma3e them impactful for proect reviews to clients and management.

    [Fig g! lms gantt "iagram#

    http://en.wikipedia.org/wiki/Gantt_charthttp://en.wikipedia.org/wiki/Gantt_chart
  • 8/10/2019 practical-4.docx

    16/17

    #"+ antt $!art

    Timeline charts are $ser Itemsthat create a chart where a series of events are arranged on a

    bar graph. 5ach event can be a single point in time or a date range.

    [Fig g! lms Timeline "iagram#

    http://ss.johncardinal.com/secuseritems.htmhttp://ss.johncardinal.com/secuseritems.htm
  • 8/10/2019 practical-4.docx

    17/17


Recommended