Batch 21(14,64,66)

6,531 views
6,114 views

Published on

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
6,531
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
265
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Batch 21(14,64,66)

  1. 1. Modeling case study Submitted in partial fulfillment of the requirements For the Case Tools Lab in III year ofBACHELOR OF TECHNOLOGY IN Information Technology By Name of the student & roll no.: D.L.N.SWETHA 08BQ1A1214 ********** Department of Information Technology Vasireddy Venkatadri Institute of Technology
  2. 2. VASIREDDY VENKATADRI INSTITUTE OF TECHNOLOGY NAMBUR (V), PEDAKAKANI (M), GUNTUR-522 508 Tel no: 0863-2118036, URL: www.vvitguntur.com Approved by AICTE and affiliated to JNTUK DEPARTMENT OF Information Technology CERTIFICATE Certified that this is a bonafied record of practical work done by________________________________of____________ B. Tech____Semester in the________________________________Lab of Department of _________________________________duringthe academic year _____________No. of experiments done and certified:Signature of the In charge Head of the Department A. Sudarshan Reddy
  3. 3. ACKNOWLEDGEMENT I would like to express my deep sense of gratitude andindebtedness to my esteemed institute “Vasireddy Venkatadri Instituteof Technology”, which has provided me an opportunity to fulfill the mostcherished desire to reach my goal. I owe project to Mr. V. Ramachandran, Assoc. Prof., who hasbeen my project’s guide. I sincerely thank him for the support andguidance which he has given me. Signature of candidate INDEX
  4. 4. Sno Topic Page no1. INTRODUCTION TO UML2. INTRODUCTION TO VISUAL PARADIGM3. CASE STUDY-1 UNIFIED LIBRARY SYSTEM APPLICATION USE CASE DIAGRAM CLASS DIAGRAM STATE CHART ACTIVITY DIAGRAMS SEQUENCE DIAGRAM COLLBRATION DIAGRAM4. CASE STUDY-2 SYSTEM-POINT OF SALE USE CASE DIAGRAM CLASS DIAGRAM STATE CHART ACTIVITY DIAGRAMS SEQUENCE DIAGRAM COLLBRATION DIAGRAM5. CASE STUDY -3 ONLINE RAILWAY RESERVATION USE CASE DIAGRAM CLASS DIAGRAM STATE CHART ACTIVITY DIAGRAMS COMPONENT DIAGRAM DEPLOYMENT DIAGRAM SEQUENCE DIAGRAM COLLBRATION DIAGRAM6. BIBLIOGRAPHY7. CONCLUSION INTRODUCTION TO UML
  5. 5. Definition of UML: The Unified Modeling Language (UML) is used tospecify, visualize, modify, construct and document the artifacts of an object-oriented software intensive system under development. UML offers a standardway to visualize a systems architectural blueprints, including elements such as: actors business processes (logical) components activities programming language statements database schemas, and reusable software components The UML represents the culmination of bestpractical object oriented modeling. The UML is the product of several years ofhardworking which we focused on bringing about a unification of the methodsused around the world, the adoption of good ideas from many quarters of theindustry and above all, effort to make things simple.Goals of UMLThe primary goals in the design of the UML were: Provide users with a ready-to-use, expressive visual modeling language so they can develop and exchange meaningful models. Provide extensibility and specialization mechanisms to extend the core concepts. Be independent of particular programming languages and development processes.
  6. 6. Provide a formal basis for understanding the modeling language. Encourage the growth of the OO tools market. Support higher-level development concepts such as collaborations, frameworks, patterns and components. Integrate best practices.SCOPE OF UML: The Unified Modeling Language (UML) is a graphicallanguage for visualizing, specifying, Constructing and documenting the aircraftsof a software intensive system. The UML specifies a modeling language thatincorporates the object oriented communities consensus on core modelingconcepts. It allows deviations to be expressed in terms of extension mechanisms.The UML provides the following:  Semantics and notation to address a wide variety of contemporary modeling issues in a direct and economical fashion.  Semantics to address certain expected future modeling issues, specifically related to component technology, distributed computing, frame works and excitability.  Extensibility mechanisms so individual projects can extend the Meta model for their application at low cost.  Extensibility mechanisms so that future modeling approaches could be grown on the top of the UML.  Semantics to facilitate the model interchange among variety of tools.  Semantic to specify the interface to repositories for the sharing and storage of model aircrafts.
  7. 7. There are several new components included in UML: Extensibility mechanisms Threads and process Distribution and concurrency Patterns / collaboration Activity diagrams Refinement Interface and components A constraint language Introduction to Visual Paradigm Visual Paradigm for UML (VP-UML) is a powerful, cross-platform and yet the most easy-to-use visual UML modeling and CASE tool. VP-UML provides software developers the cutting edge development platform tobuild quality applications faster, better and cheaper! It facilitates excellentinteroperability with other CASE tools and most of the leading IDEs whichexcels your entire Model-Code-Deploy development process in this one-stop-shopping solution.UML modelingYou can draw all kinds of UML 2.x diagrams in VP-UML, which include: Class diagram Use case diagram Sequence diagram Communication diagram State machine diagram Activity diagram Component diagram Deployment diagram Package diagram
  8. 8. Object diagram Composite structure diagram Timing diagram Interaction overview diagramRequirement modelingCapture requirements with SysML Requirement Diagram, Use Case Modeling,Textual Analysis, CRC Cards, and create screen mock-up with User Interfacedesigner.Database modelingYou can draw the following kinds of diagrams to aid in database modeling: Entity Relationship Diagram ORM Diagram (visualize the mapping between object model and data model)You can model not only database table, but also stored procedure, triggers,sequence and database view in an ERD.Besides drawing a diagram from scratch, you can reverse engineer a diagramfrom an existing database.Apart from diagramming, you can also synchronize between class diagram andentity relationship diagram to maintain the consistency between them.SQL generation one execution feature is available for producing and executingSQL statement from model instantly.Business process modelingYou can draw the following kinds of diagrams to aid in business processmodeling: Business process diagram Data flow diagram Event-drive process chain diagram Process map diagram Organization Chart
  9. 9. You can also export Business process diagram to BPEL.Object-Relational mappingObject-Relational Mapping enables you to access relational database in an objectrelational approach when coding. VP-UML generates object-relational mappinglayer which incorporates features such as transaction support, pluggable cachelayer, connection pool and customizable SQL statement.Team collaborationFor users that work as a team, team collaboration support lets you performmodeling collaboratively and concurrently with any one of the following tools ortechnologies: VP Teamwork Server (Need to buy Visual Paradigm Teamwork Server additionally) CVS Subversion PerforceInteroperability: The interoperability support allows you to exchange model datawith other tools.Exploring VP-UML diagrams : VP-UML utilizes diagrams as views of the information in a model.Once developed, VP UML automatically maintains consistency between thediagram and its specifications. The following key diagrams are used: Use case diagrams: Analysts and developers use these to capture user requirements by graphically depicting how the system works. During the design phase of the project, Rose allows you to actually specify the system behavior (what Rose calls use cases). The use case diagram therefore
  10. 10. graphically represents the system boundary. Typically, a use case diagram consists of (1) actors or things outside the system, (2) use cases, and (3) relationships between actors. Creating a use case diagram Right click Use Case Diagram on Diagram Navigator and select New Use Case Diagram from the pop-up menu.. Class diagrams: Rose uses class diagrams to graphically describe generic descriptions of the system you’re going to build. Class diagrams contain icons that represent classes and interfaces and their relationships to one another.Creating class diagramRight click Class Diagram on Diagram Navigator and select New ClassDiagram from the pop-up menu to create a class diagram.
  11. 11. Statechart and Activity diagrams: Rose allows users to use state chart diagrams (which are state-driven) to model the dynamic behavior of individual classes or objects. Statechart diagrams are very similar to activity diagrams (which are activity-driven). Basically, these diagrams show you (1) the sequence of states that an object will go through, (2) the events that cause a transition from one activity to another, and (3) any actions that result from the state or activity change. Creating state machine diagramRight click State Machine Diagram on Diagram Navigator and select New StateMachine Diagram from the pop-up menu to create a state machine diagram.
  12. 12. Interaction diagrams: Rose uses interaction diagrams as a collective name for collaboration and sequence diagrams, which, in essence, graphically represent interactions. Collaboration diagrams show how objects are associated with each other, whereas sequence diagrams show time-based interactions between objects.Creating sequence diagramRight click Sequence diagram on Diagram Navigator and select NewSequence Diagram from the pop-up menu to create a sequence diagram.
  13. 13. Component diagrams: Rose uses component diagrams to clearly reflectthe physical dependency relationships between components (i.e., mainprogram, subprogram, packages, and tasks) and their arrangement in agraphical manner.  Creating component diagram  Right click Component Diagram on Diagram Navigator and select New Component Diagram from the pop-up menu to create a component diagram.
  14. 14. Deployment diagrams: Using the deployment diagram, Rose allows usersto graphically show the connections between processors, devices, andconnections..  Creating deployment diagram  Right click Deployment Diagram on Diagram Navigator and select New Deployment Diagram from the pop-up menu to create a deployment diagram.
  15. 15. CASE STUDY-1 UNIFIED LIBRARY APPLICATIONINTRODUCTION Unified Library Application System emphasizes on the online reservation,issue and return of books. This system globalizes the present library system.Using this application the member can reserve any book from anywhere in theworld. Still in nascent stages, this application soon revolutionizes present librarysystem.Let us just have an overview of the unified library application system: · Librarian lends books and magazines · Librarian maintains the list of all the members of library · Borrower makes reservation online · Borrower can remove reservation online · Librarian issues books to the borrower · Librarian calculates dues to be paid by the borrower · Borrower issues/returns books and/or magazines · Librarian places order about the requirements to the master librarian · Librarian updates system · Master librarian maintains librarians .TEXTUAL ANALYSIS(a)ACTORS i. Librarian ii. Borrower iii. Catalog iv. Master Librarian(b)VERBS i. Borrower: 1. Logs into the system 2. Browses/searches for books or magazines 3. Makes/removes reservation
  16. 16. 4. Views results and reports from the unified library application systemii. Librarian: 1. Manages and validates members 2. View reports from the system 3. Issues books 4. Calculates dues 5. Takes books 6. Places orders to the master librarian 7. Maintains list of books and magazineiii. Master Librarian1. Maintains other librarians.
  17. 17. USECASE DIAGRAM
  18. 18. CLASS DIAGRAM
  19. 19. STATE CHART DIAGRAMLIBRARY ADMINISTRATORLIBRARIAN
  20. 20. MEMEMEMBER
  21. 21. ACTIVITY DIAGRAM
  22. 22. SEQUENCE DIAGRAM
  23. 23. COLLABORATION DIAGRAM
  24. 24. CASE STUDY 2-POINT OF SALEINTRODUCTION Shops are the integral part of any civilization. They are present inevery culture since ages. This application emphasizes on the transaction goingon between the customer and shop keeper during sale of product. The customer approaches the shop keeper/ sales boy and places hisorder. The shop keeper forwards the order to sales boy who fetches the requiredgoods from inventory. Then the shop keeper calculates bill and issues to thecustomer. The customer on paying the bill takes goods from the shop keeper. Inturn, shop keeper fetches goods from supplierLet us just have an overview of point of sale: · Customer places order to the shop keeper/sales boy · Sales boy collects goods and forwards them to shop keeper · Shop owner calculates bill and forwards to the customer · Customer on paying the bill receives goods from shop keeper · Shop keeper places order to supplier and receives goodsTEXTUAL ANALYSIS(a)ACTORS i. Customer ii. Shop Owner iii. Sales boy iv. Supplier(b)VERBS i. Customer: 1. Places order to shop owner/sales boy 2. Receives bill from shop owner 3. Pay the bill
  25. 25. 4. Receive goodsii. Shop Owner: 1. Receives order from customer 2. Forwards order to sales boy 3. Receive goods from sales boy 4. Calculates bill 5. Receives payment 6. Places orders to supplier 7. Maintains inventoryiii. Supplier 1. Receives order from shop owner 2. Delivers goods to shop owner
  26. 26. USECASE DIAGRAM
  27. 27. CLASS DIAGRAM
  28. 28. SEQUENCE DIAGRAM
  29. 29. STATE-CHART DIAGRAMCUSTOMERSUPPLIER
  30. 30. SHOP OWNER
  31. 31. SALES BOY
  32. 32. ACTIVITY DIAGRAM
  33. 33. COLLABORATION DIAGRAM
  34. 34. CASE STUDY 3 - ONLINE MOVIE TICKETS BOOKING SYSTEMINTRODUCTION This project is aimed at developing an online ticket reservation system for aCinema Hall. The Ticket Reservation System is an Internet based application thatcan be accessed throughout the Net and can be accessed by anyone who has a netconnection. This application will automate the reservation of tickets. This online ticket reservation system provides a website for a cinema hallwhere any user of internet can access it. ThisExisting system: The existing system has two ways of booking tickets for a movie: One is to book tickets at the ticket counter of respective cinema hall and theother one is through phone called as “Tele booking”. Former is one of the hecticprocesses where one should stand in long queues for hours. Tele booking wasintroduced keeping in view the user’s comfort while booking tickets.Proposed system: The proposed system is a web based application where one can buy ticketswith just one click go. An internet user can buy tickets at any time of day or night.He will be guided with all the necessary steps to book tickets and collect tickets atthe ticket counter in the website. Also in the proposed system, customers can cancel seats at a suitable time (2days before the show to 1hour before the show). If the customer wishes to cancelhis tickets he will be given a confirmation details regarding his cancellations. Asthe customer buys tickets online through his credit card, on cancellation of tickets
  35. 35. the refunded amount (30% of the amount will be charged for service charges) willbe added back to his credit card account. To enhance the refund function, all thecustomers have to register and become a member before buying tickets so that hefaces no problem while accessing the website.TEXTUAL ANALYSIS(a)ACTORS USER ADMIN DATABASE(b)VERBS 1. USER Searching for a ticket Enters username and password Enters details Books a ticket 2. ADMIN Enter in to the system Select operation Enter ID and Password Enter the details in the form 3. DATABASE Ask for ID and Password Verify the Password Check the availability of tickets Asks to enter the credit info Gives the receipt/ticket
  36. 36. USE DIAGRAMONLINE MOVIE TICKET RESERVATION
  37. 37. SEQUENCE DIAGRAMLOGIN
  38. 38. MOVIE INFIRMATION
  39. 39. THEATRE INFIRMATIONTICKET INFIRMATION
  40. 40. PAYMENT
  41. 41. CLASS DIAGRAMONLINE MOVIE TICKET RESERVATION
  42. 42. COLLABORATION DIAGRAMLOGINMOVIE INFIRMATION
  43. 43. THEATRE INFIRMATIONTICKET INFIRMATION
  44. 44. PAYMENT
  45. 45. STATE CHART DIAGRAMONLINE MOVIE TICKET RESERVATION
  46. 46. ACTIVITY DIAGRAMSLOGIN
  47. 47. MOVIE INFIRMATION
  48. 48. THEATRE INFIRMATION
  49. 49. TICKET INFIRMATION
  50. 50. PAYMENT
  51. 51. COPONENT DIAGRAMONLINE MOVIE RESERVATION
  52. 52. DEPLOYMENT DIAGRAMONLINE MOVIE RESERVATION
  53. 53. CONCLUSION This system provides a big advantage that to book tickets throughonline in some of the big cities.This also tells about the information about numberof theatres, movies running in them because it’s a time taking process to go to thetheatre and book the tickets. Updation is a major constraint in developing the present systems . If we don’t automize the booking system this may lead to confusion.So we have to update the database every time after a ticket is booked. This is an easy and simple way that most of the people followingnow-a-days.
  54. 54. REFERENCES(a) OBJECT-ORIENTED ANALYSIS AND DESIG With applications SEECOND EDITION Grady Booch Rational Santa Clara, California(b) Applying UML and Patterns An introduction to Object Oriented Analysis and design and the Unified Process (II edition) Craig Larman(c) UML Distilled: A Brief Guide to the Standard Object Modeling Language, Third Edition By Martin Fowler

×