Multiplex Management


Published on

Published in: Education, Technology, Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Multiplex Management

  1. 1. Multiplex ManagementSoftware Engineering.
  2. 2. Group Members YatinPuthran (37) Zalpa Rathod (39)
  3. 3. What are Data FlowDiagrams? A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system. A data flow diagram can also be used for the visualization of data processing (structured design). It is common practice for a designer to draw a context-level DFD first which shows the interaction between the system and outside entities. This context-level DFD is then "exploded" to show more detail of the system being modeled
  4. 4. Data Flow Diagram Symbols There are only four symbols: › Squares representing external entities, which are sources or destinations of data. › Rounded rectangles representing processes, which take data as input, do something to it, and output it. › Arrows representing the data flows, which can either be electronic data or physical items. › Open-ended rectangles representing data stores, including electronic stores such as databases or XML files and physical stores such as or filing cabinets or stacks of paper.
  5. 5. Data Flow Diagram Symbols Process Actions performed on data so that they are transformed, stored or distributed. This can be a computerised Or manual transformation Data Flow E.g. Result of a query to a database, contents of a printed report : data that moves together to common destinations
  6. 6. Data Flow Diagram Symbols Data Store A physical location to hold data e.g. A file folder or notebook etc. Source Origin and/or destination of the data. Often referred to as external entities as they are outside the system. We are only interested in how data flows in to or from the system to
  7. 7. Contd.. Data flow diagrams can be used to provide a clear representation of any business function. The technique starts with an overall picture of the business and continues by analyzing each of the functional areas of interest. This analysis can be carried out to precisely the level of detail required.
  8. 8. Common Modeling Rules All processes must have at least one data flow in and one data flow out. All processes should modify the incoming data, producing new forms of outgoing data. Each data store must be involved with at least one data flow. Each external entity must be involved with at least one data flow. A data flow must be attached to at least one process.
  9. 9. Context or Level 0 Diagram The highest level view of a system. This only has one process which represents the overall function of the system and has no data stores as all the data is stored within the process. Now we demonstrate the Level 0 or Context Diagram for Multiplex Management System.
  10. 10. Level 0 Context Diagram Screens Supplier Order Reels Smoke Alarm Screening Message Smoke/CO Maintenance Status alarm Supply Reels CO alarm Booking Message Online Confirmation Act/DectBooking Multiplex Booking Request Alarm Book Tickets Emergency Issue Tickets In/Out Stock Services Customer Food Stalls
  11. 11. Multiplex ManagementSystem Now we see the Data Flow or Level 1 diagram of the Multiplex Management System
  12. 12. Box office file Level 1DFD Smoke/CO detectors Smoke alarm Message Store Emergency Services Alert CO alarm Message Alert Action Repor Proces t s Details Changes Feedbac Send Supply Unit Owner Report k Invoke Weekly Process Collection Reel Status In/Out Staff Dispatch Stock order Supplier Mainten ance Movie List Cleaning/UpgradesOrder/Supply Food stall Send details Screens Booking Book Seats Availability Box OfficeOnline Booking Confirmation Collection Proces Invoice Issue bill Tickets/ s Coupon Collection Booking Request Tickets s Transactio Book Ticket n Product ticket/coupons Debit/credit card/ Cash Customer
  13. 13. Advantages to Using DFD Data flows and process consequences. ◦ Wherever we start in the process, we can understand the processing steps that the needed to take to complete the relevant transaction(s) and to inform its constituents of the results. Data inputs and outputs. ◦ The DFD also makes it possible to understand what data are needed to provide appropriate inputs to any processing step.
  14. 14. Contd.. Simplifying complexity by isolating process components. ◦ The DFD would make it easier to capture the detail of such data flows. ◦ At the time that DFDs were developed, this shift towards modularizing data flows and processing elements represented a major step forward in enabling systems analysts to add useful structure to process representations rapidly and easily.
  15. 15. Data Dictionary A data dictionary is an integral part of a database, which holds information about the database and the data that it stores, i.e., the meta- data. A data dictionary is a simple yet effective add-on to ensure data consistency. All the information required to create the data dictionary must be identified and recorded in the design documents
  16. 16. Data Dictionary Customer Details: Customer Name = First Name + (Middle Initial) + Last Name Payment=Method of payment +(Credit Card type * Credit Card Number * Expiration Date) Customer Number = (Residence|Mobile|Office) *Integer string length upto 10*
  17. 17. Data Dictionary Ticket Details: Movie_name= *character length upto 20* Screen= digit *1 digit number less than 10* Ticket_info= Movie_name + (Date * Time) Class= Char *char string length upto 10* Seat_no= char + digit + digit *1 character and 2 digit number less than 100* Location= *character string length upto 30*
  18. 18. User Interface The means by which the user and a computer system interact, in particular the use of input devices and software. Provide a means of: Input, allowing the users to manipulate a system, and/or Output, allowing the system to indicate the effects of the users manipulation.
  19. 19. User Interface for Multiplex
  20. 20. ‘Multiplex’ User Interface(contd..)
  21. 21. ‘Multiplex’ User Interface(contd..)
  22. 22. Conclusion References: Data Flow Diagrams Agile Modeling EDrawSoft – Data Flow Diagrams Data flows: Note on Data-Driven Process Modeling