This action might not be possible to undo. Are you sure you want to continue?
(Affiliated to Andhra University) R.T.O Office Road, Ayodya Nagar, Kakinada-533003 Ph no. 0884-2346661
CASE STUDY ON
ONLINE MOVIE RESERVATION SYSTEM BY Ch.Srinivas U.SriDivya Sk.Mastan Shareef
III MCA I SEMESTER Under the Esteemed Guidance of Mrs.Aruna Lecturer in Computer Science
DEPARTMENT OF COMPUTER SCIENCE ADITYA INSTITUTE OF POST GRADUATE STUDIES KAKINADA-533003 (2008-2011)
ADITYA INSTITUTE OF P.G STUDIES
(Approved by A.I.C.T.E. New Delhi) (Affiliated to Andhra University) Under the Management of Aditya Academy KAKINADA-533003,ph:2376662
DEPARTMENT OF COMPUTER SCIENCE CERTIFICATE
This is certify that it is a bonified record of the Case Study work entitled "ONLINE MOVIE RESERVATION SYSTEM" done by Srinivas, SriDivya, Sk.Mastan Shareef during the period 2010-2011 in partial fulfillment of the requirements for the award of Degree "Master Of Computer Applications" in the Department of Computer Sciences, Aditya Institute of Post Graduate Studies, kakinada.
(Mrs.Aruna) Internal Guide
(Mrs.D.BEULAH) Head of the dept. Department of Comp.Sc.
We avail this opportunity to express our deep sense of gratitude and hearty thanks to Mrs.Aruna who is the internal guide of this problem for his constant guidance ,keen interest open-minded discussions on his encouragement given during this period during this period and preparation of case study. It gives us immense pleasure he express pleasure our deeply felt gratitude to words Mr.N.SeshaReddy,honourable chairman,AIPS,Kakinada.We also thank Mr.Nagendra Kumar , principal and Mrs. D. Beulah, Head of the Department of Computer Science for their co-operation and for providing excellent lab facilities. We are very much thankful to the faculty members of our college ,and also to the lab technicians and Classmates for their continuous support and co-operation during this case study. Although a leaflet title "Acknowledgements cannot represent our true feelings for all these persons" ,we feel very much thankful to all of them and also to our parents for encouraging us,giving us all the moral support requires and to all people who making these endeavour a reality.
U.SriDivya Ch.Srinivas Sk.Mastan Shareef
We have by declare that the case study entitled " ONLINE MOVIE RESERVATION SYSTEM " has been developed by us under the super vision of Mrs.Aruna faculty of AIPS, and submitted to AIPS, kakinada in partial fulfillment for the requirements for the case study.
Ch.Srinivas U.SriDivya Sk.Mastan Shareef
1 . Online booking 3 . Availability of tickets on mentioned date and time in specified city . This procedure involves via phone conferences . An alternative mechanism also exists for people who doesn’t have a bank card . It is a concept of developing a web portal . This requires possession of bank’s credit or debit card with customer .The transfer of tickets is also done immediately . \ -5- . 2 . Special offers The provision for money transactions are portal . where a customer can make movie tickets in theatres that are made available in the site .ABSTRACT The system is a Online movie reservation System development for the Theatres. Information of shows running in theatres 4 .
Problem Statement 3.2.1.INDEX 1.System Models 4. Requirement Analysis Document 220.127.116.11.18.104.22.168.Functional Testing 5.1. Testing Specifications 5.Introduction 4.1.1. System Design document 4. Introduction 2.Proposed System 3.Current Software Architecture 4.List of Test Cases 5.Introduction 5.2.4.Introduction 5.3.2.Proposed Software Architecture 5.Structural Testing 5.List of Test Cases -6- .2.Introduction 3.Current System 3.
He is not provided with the detailed project information done or to be assigned based on Application / Verticals. DRAWBACKS IN EXISTING SYSTEM: Need of extra manual effort. For issuing the tickets need the extra manual effort and take much time to receive the tickets . The managers of Theatres falls short of controlling the issuing of tickets . -7- .REQUIREMENTS ANALYSIS DOCUMENT EXISTING SYSTEM . It used to take much time to receive Tickets Wastage of time will be high . . The decision for appraisal of next show tickets in advance is difficult .
1 . 2 . No fever of data loss. Doesn’t require any extra hardware device. Just need a little knowledge to operate the system. ADVANTAGES OF PROPOSED SYSTEM: Very fast and accurate. Online booking 3 . At last very easy to receive the tickets. This procedure involves via phone conferences . No need of any extra manual effort. where a customer can make movie tickets in theatres that are made available in the site . It is a concept of developing a web portal . -8- . An alternative mechanism also exists for people who doesn’t have a bank card . The system is a Online movie reservation System development for the Theatres. Information of shows running in theatres 4 . Availability of tickets on mentioned date and time in specified city . Special offers The provision for money transactions are portal .PROPOSED SYSTEM .The transfer of tickets is also done immediately . This requires possession of bank’s credit or debit card with customer .
At the time of project we may create many modules and finally we combine them to form a system. login id.etc.. current projects in his account etc. Theatre Management Module: This module deals with the management of the Theatre related with the movies that were past dealt. Movie Information Module: This module deals with the management of the movie information such as the hiring of the movie. Importance of modules in any software development side is we can easily understand what the system we are developing and what its main uses are.MODULE DISCRIPTION: The list of modules incorporated with “ONLINE MOVIE RESERVATION SYSTEM” is Customer Info Module Theatre Management Module Movie Information Module Manager Reports Customer Info Module : This module deals with the management of the customers information such as the personal details-his name. password . Manager Reports Module: This module is specified for the purpose of the report generation for the Manager on his desired requests. its information maintenance etc. payments criteria. -9- .
it will delete from the dabase. Concurrency Response times or processing times define how fast requests would be processed. but absolutely unacceptable for getting a web page in a customer portal. Throughput 3. . Acceptable response times should be defined in each particular case. Response time 2. Then non functional requirements would be the input for performance testing and capacity planning. Ticket Transactions: This functionality maintains the information of ticket transactions. A time of 30 minutes can be excellent for a big batch job. it just means that they exists in heads of administrators. Cancellation of Tickets : If the user want to cancel the reserved tickets he can cancel the tickets . If there is written performance requirements. These are the 3 classes of performance requirements: 1. this will handle through the sub module which is update customer master and whenever we don’t require the details of customer. but nobody bothered to write them down and made sure that everybody agrees with them. but it has to be done with in the given time . Bill Payments: This module maintains payment information of each customer for a movie.10 - . • • • Non-Functional Requirements: These are necessary for system design and development. It maintains the information of tickets has been taken by each customer and also which tickets are available.Functional Requirements • Customer Master: It deals with customer details that are entering the details of customer when customer login into the organization and whenever changes are required.
Concurrency. • Performance: Fast retrieval of employee’s information required by the Central Management from the database through SQL. but not active.Throughput is the rate at which incoming requests are completed. So the organization can implement this project easily. Availability: This project has been tested successfully which needs all requirements as specified and giving accurate output as needed. Even if users are connected. It is also helpful in optimum utilization of time. they still hold the same resources. is important too.11 - . • • . we are providing the security to the employee information and authoring data to only Central Management and allowing effective retrieval of data. Reliability: In the Current System. the number of users or threads working simultaneously. Throughput defines load on the system and is measured in operations per a time unit. It may be the number of transactions per second .
although optimally it should be used in a use case driven. It is a very expressive language addressing all the views needed to develop and then deploy such systems. construct. and incremental. iterative. Learning to apply the UML effectively starts with forming a conceptual model of the language. the UML is not difficult to understand and to use. . A modeling language such as the UML is thus a standard language for software blueprints.Introduction to UML The Unified Modeling Language is a standard language for writing software blueprints. The UML may be used to visualize. Even though it is expressive.12 - . and document the artifacts of a software intensive system. which requires three major elements: the UML’s basic building blocks. specify. The UML is only a language and so is just one part of a software development method. architecture-centric. and some common mechanisms that apply throughout the language. the rules that dictate how these building blocks may be put together. The UML is a language which provides a vocabulary and the rules for combining words in that vocabulary for the purpose of communication. A modeling language is a language whose vocabulary and rules focus on the conceptual and physical representation of a system. The UML is process independent. The UML is appropriate for modeling systems ranging from enterprise information systems to distributed Web-based applications and even to hard real time embedded systems.
That’s the role of software development process. design and implementation decisions that must be made in developing and deploying a software-intensive system. but they don’t tell us what models they should create and when we should create them. A well defined process will guide us in deciding what artifacts to produce. . No one model is ever sufficient. Rather. Things that are best expressed graphically are done so in the programming language. In this manner. this requires a language that addresses the different views of a system’s architecture as it evolves throughout the software development lifecycle. The UML is not a visual programming language. or even another tool. The reverse is also possible. This means that it is possible to map from a model in the UML to a programming language. This mapping performs forward engineering: The generation of code from a UML model into a programming language. one developer can write a model in the UML. information is lost when moving from models to code. For software intensive systems. behind each symbol in the UML notation is a well-defined semantics. The UML is more than just a bunch of graphical symbols. The vocabulary and rules of a language such as the UML tells us how to create and read well formed models.UML addresses the specification of all the important analysis. what activities and what workers to use to create them and manage them. and another developer. we often need multiple models that are connected to one another in software development in order to understand anything but the most trivial system.13 - . can interpret that model umambigously. Unless we encode that information in the implementation. and how to use those artifacts to measure and control the project as a whole.Modeling yields an understanding of a system. but its models can be directly connected to a variety of programming languages. Rather.
the structure and behavior of a patient healthcare system. Rational was sold for US$2. Combining these two paths of forward code generation and reverse engineering yields roundtrip engineering. meaning the ability to work in either a graphical or textual view. it is expressive enough to model non-software systems. such as workflow in the legal system. the UML is sufficiently expressive and unambiguous to permit the direct execution of models. Rational Machines was founded by Paul Levy and in 1981 to provide tools to expand the use of modern software engineering practices.Reverse engineering thus supports tool support with human intervention. and the instrumentation of running systems. In addition it this direct mapping.14 - . The UML is intended primarily for software-intensive systems. and design of hardware. In fact. the simulation of systems. while tools keep the two views consistent. It has been used effectively for such domains as • Enterprise information systems • Banking and financial services • Telecommunications • Transportation • Defense/aerospace • Retail • Medical electronics • Scientific • Distributed web based services The UML is not limited to modeling software. particularly explicit modular architecture and iterative development.1 billion a tailorable process that guided .
I have found that these interfacing capabilities are poorly documented.development tools that automated the application of that accelerated adoption of both the process and the tools. such as by adding new tools. allowing the specification of the artifacts of design from many perspectives and for different objectives during the computer engineering lifecycle. as I think it is a valuable platform in which to explore research ideas in design and analysis methods. modifying existing ones and adding whole new complementary conceptual design methods into the Rose toolset. This allows tool functionality to be extended in a number of different directions.15 - . They should do a better job of documenting this capability and making the information more widely available. I have found UML and Rose to be useful in a wide range of modeling situations. and typically will use it to simply organize the concepts of a domain I am studying. Most of these notations are directly supported through the Rose tool set. so that it is easier for me to organize and retain a basic comprehension of the information in that domain— leveraging the mind’s ability for “chunking” information into organized . UML has a number of different notations. Rose is an operational tool set that uses UML as it means for facilitating the factor of domain semantics and architecture/design intent. Rational Rose is a tool ser produced and marketed by Rational Software Corporation (now owned by IBM). The complete fabric of UML and its realization in the Rose set of components is made available to the user/engineer. One of the unique characteristics of rose is its ability to be extended through use of its “Add-in” capability.
Use case diagrams are one of the five diagrams in the UML for modeling the dynamic aspects of systems. Use cases provide a way for developers to come to a common understanding with your system’s end users and domain experts. Use case diagrams are central to modeling the behavior of a system. subsystems and classes approachable and understandable by presenting an outside view of how those elements may be used in context. without having to specify how that behavior is implemented. Use case diagrams are also important for testing executable systems through forward engineering and for comprehending executable systems through reverse engineering. Use case diagrams are important for visualizing.structures to more easily manage complexity and enhance retention of knowledge structure. these use cases are realized by collaborations whose elements work together to carry out each use case. a subsystem or a class. Each one shows a set of use cases and actors and their relationship. including variants that a system performs to yield an observable result of value to an actor. specifying and documenting the behavior of an element. In addition. Use case diagram: A use case specifies the behavior of a system or a part of a system and is a description of a set of sequences of actions. We apply use cases to capture the intended behavior of the system we are developing. As we implement our system. They make systems.16 - . . use cases serve to help validate your architecture and to verify your system as it evolves during development.
This view primarily supports the behavior of a system-the outwardly visible services that the system provides in the context of its environment. Here we will apply use case diagrams to specify the desired behavoiur of the system. a use case diagram lets you view the whole system as a black box. In this manner. 1. but you can’t see how that system works on the inside. you will typically apply use case diagrams in one of two ways. you can see what’s outside the system and you can see how that system reacts to the things outside.A use case diagram is a diagram that shows a set of use cases and actors and their relationships. To model the context of a system Modelling the context of a system involves drawing a line around the whole system and asserting which actors lie outside the system and interact with it. independent of how that system should do it.17 - . To model the requirements of a system Modelling the requirements of a system involves specifying what that system should do. We apply use case diagrams to model static use case view of a system.a name and graphical contents that are a projection into a model. When we model the static use case view of a system. . A use case diagram is just a special kind of diagram and shares the same common properties as do all other diagrams. 2.
Use cases diagrams depict: • Use cases: A use case describes a sequence of actions that provide something of measurable value to an actor and is drawn as a horizontal ellipse.18 - . The arrowheads are typically confused with dataflow and as a result I avoid their use. organization. The arrow head is often used to indicate the direction of initial invocation of the relationship or to indicate the primary actor within the use case. . • Actors: An actor is a person. Theatre manager allocate some extra tickets to Customers. Theatre manager maintain movie information like addition. Use case templates: Participating actors: • Theatre manager • Customer Flow of events: • • • • The Theatre manager entered through login After login Theatre manager check the availability of tickets. • Associations: Associations between actors and use cases are indicated in use case diagrams by solid lines. or external system that plays a role in one or more interactions with your system. These are modeled as lines connecting use cases and actors to one another with an optional arrowhead on one end of the line. updation and deletion. An association exists whenever an actor is involved with an interaction described by a use case. Actors are drawn as stick figures.
Theatre manager removes movie details if it is not necessary.19 - . USECASE Diagram of Online Movie Reservation System: Use Case Templates for Manager.• Customer can also entered through login . Exceptional flow of events: • • • Invalid customer check. After login check the availability of tickets . Customer master removes customer details if he is not available.Custmer login: .
(ii)Manager or customer checks the required details. Manager doing all the tasks successfully. Manager must know their user id and password.Use case name Participating Flow of events Manager or customer Login Manager. Entry condition Exit condition Use Case Templates for AddMovieDetails: Use case name Participating Flow of events AddMovie Details Manager (i)Manager enters his/her identity number and password to login the system.20 - . (ii)Manager checks the required movie details. Manager or customer must know their user id and password. (iii)Manager enters the details in the form and submit the form. customer (i)Manager or customer enters his/her identity number to login the system. Manager or customer doing all the tasks successfully . Entry condition Exit condition Use Case Templates for CheckAvailabilityDetails: .
(ii)Customer checks the required details. Entry condition Exit condition . Manager (i)Customer enters his/her identity number to login the system. Customer doing all the tasks successfully and Manager doing all the tasks successfully.Use case name Participating Flow of events CheckSAvailabilityDetails Customer. Customer or Manager must know their user id and password.21 - .
22 - .CLASS DIAGRAM : .
23 - .Fig Showing the overall representation of class diagram SEQUENCE DIAGRAM .
Message: A message can be simple. a simple message has a two-line arrowhead. asynchronous. Time: . If an object sends a synchronous message. Extending downward from each object is dashed line called object's lifeline. it waits for an answer to the message before it proceeds with its business. If an object sends asynchronous message. a synchronous message has a half-arrowhead. it doesn't wait for an answer before it proceeds. and time placed on the vertical axis. with interaction such as events. Objects: The objects are laid out near the top of the diagram from left to right. operations. A simple message is a transfer of control from one object to another. Message represented as solid line arrow and time required by vertical lines. The objects represented in usual way as named rectangle.. A sequence diagram shows an interaction arranged in time sequence. A sequence diagram describes how objects interact with each other and how message are sent and received between the objects. In the sequence diagrams. The sequence diagram shows how objects communicate with one another. Along the lifeline is narrow rectangle called an activation that represents an execution of an operation the object carries out. synchronous. Instance of these design component appear on the horizontal axis of the diagram. A line separates concurrent sub states. Sequence sub state occur one after the other. Extending a line from object is called life time. The arrow lines gives the interaction among the object takes places in a specified sequence and the sequence takes time to go from beginning to end.Sequence diagram describes the interactions between design components and environment.24 - . The objects are at top of the diagram from left to right. The instance participating in the interaction.
Time starts at the top and progresses towards the bottom.25 - . Fig Showing the overall representation of sequence diagram COLLABORATION DIAGRAM . A message that's closer to the top occurs earlier in time than a message that's closer to the bottom.
………… To show nesting messages you will use decimal numbers i.A collaboration diagram represents the organization of objects that participate in an interaction.increasing monotonically for each messages in the flow of control i. You form a collaboration diagram by first placing the objects that participate in the interaction.Next you represent with links that connect these objects as the arcs.3…………. .3..1.1.1. Collaboration diagram have 2 features that distinguish from sequence diagram: There is a path to indicate how one object is linked to another.you prefix these messages with a number(start with 1). There is a sequence number to indicate the time order of messages.2.you can attach a stereotype to the far end of link with <<local>> and <<global>>.e 2.e 1.26 - .Finally you can represent these links with the messages that object send and receive.
27 - .Fig Showing the overall representation of Collabration diagram .
It shows steps. Like the state diagram. It is an extension of the state diagram. An arrow represents the transaction from one activity to the next. and branches. The state diagram shows the state of an object and represents activities as arrows connecting the state. decision point. .28 - .STATE CHART DIAGRAM : ACTIVITY DIAGRAM : ACTIVITY DIAGRAM An activity diagram in much similar to a flowchart. The activity diagram highlights the activities. the activity diagram has a starting point represented by a filled-in circle. and an endpoint represented by a bull's eye. Each activity is represented as rounded rectangle. more oval in appearance that the state icon.
29 - .Fig Showing the overall representation of Activity diagram .
30 - .System Design Document Introduction .
Ordinary methods for communications in an organization. Subsystem decomposition: Human resource management System is decomposed into registration. logout all these details entered into the database. :WindowsHost Register DataBase :WindowsHost :compensation details database Login Logout :WindowsHost apc:pc :Iexplorer :training detail s database Hardware and Software Mapping(Deployment Diagram): :WindowsHost emp personal details database . we can create an effective communication media between two or more persons of an organization which is very fast in nature.purpose of the system: Online Movie reservation system is used to create new user and easily he can reserve the tickets by login into the organization . login.31 - . Design Goals: Using this system. Current Software Architecture: Proposed Software Architecture: II.
32 - .:WebServer Figure: Deployment Diagram: Persistent Data Management: .
Capabilities: A capability associates a(class. access is denied. a. Every time an object is accessed. b. class.33 - . Procedural driven control b. Access control list Capabilities Global Access table: It represents explicitly every cell in the matrix as a(Actor. a. If no such tuple is defined. operation) pair with an actor. Operation) pair with each class to be accessed. Access Control list: It associates a list of(Actor. c. In object-oriented systems sequential actions include which operation should be executed in which order.Access Control and Security: Providing Access Control: In access control mechanisms different actors have access to different functionalities and three approaches. There are three possible control flow mechanisms. its access list is checked for the corresponding actor and operation. Operation). This access table determines if an actor has access to a specific object requires looking up to the corresponding tuple. c. c. A allows an actor access to an object of the class described in the capabilities. a. Designing Global control flow: Control flow is the sequence of actions in a system. Event driven control Threads . Global access table b. Empty cells are discarded.
c. b.e to decide how the system is started. Software fault. each thread corresponding to different threads.e the system can create an arbitrary number of threads.34 - . Exception handling: • • • Exception handlings are by three different resources. Procedural driven control: The operations wait for input whenever they need data from an actor. which use cases are destroyed. Hardware failure. This Kind of control flow is mostly used in systems in procedural languages. In general we identify the boundary use cases by examining each subsystems and each persistent data. Identifying boundary conditions: We need to examine the boundary conditions of a system i. we examine which use cases are created. changes in the OS environment. . we add three different use cases i. power outages. network outages. Boundary Condition: We try to keep security to the data and all functionalities. start. shutdown and configure the components.a. In every system deal with major failures which has data corruption. it is dispatched to the objects mostly the events are associated with based on information. Whenever the event becomes available. Startup and shutdown: For each component. If a thread needs additional data. initialized and shutdown. Threads: Threads are concurrent variations of procedure driven control i.e. Configuration: For each persistent object. software errors. Event driven control: A main loop waits for an external event. it waits for input from an actor.
35 - ..
OBJECT DESIGN DOCUMENTATION Introduction Object design tradeoffs One of the design criteria for any software development is buy Vs build. • Com(For JDBC Speciation which is in MySql) • Test • User details . field and patterns with noun phrases. The following are the packages in the Ravindra system. Packages: A UML grouping concepts denoting that a set of objects or classes are related. • Classes are named with singular nouns • Methods are named with verb phrases. However the system needs a special solution for managing the transactions done in backing the following are the naming conventions.36 - . of use cases and concepts. That can improve communications between developers during object design. The following are the used in Client Provisioning object design. • Name of the functions which is used to create details should be end with the word details name of the buttons that are used to take decisions should use the words like accepting or satisfying Interface documentation guidelines: Interface documentation guidelines and coding conventions are the single most important factors. • Error status is written via an exception only and not a return value. Packages are used in use case and class diagram dealt with the complexity associated with large no.
37 - ..
Client Need Accepting Testing Requirements System Testing Design Integration Testing Code Unit testing System Testing The philosophy behind testing is to find errors. A strategy employed for system is code testing. To follow this method we developed some test . Testing plays a critical role in quality assurance for software.TESTING Testing is the major quality control measure used during software development.38 - . Testing is used for detecting these errors. The code testing examines the logic of the program. In addition to detecting the error introduced during the coding phase. Test cases are devised with this in mind. Testing is a dynamic method for verification and validation. The basic levels of testing are. design and requirements faults also appear in the code. from which the presence of faults can be reduced. LEVELS OF TESTING In order to uncover the errors present in different phases we have the concept of levels of testing. The basic function is to detect errors in the software. where the system to be tested is actually executed and behavior of the system. Due to the limitation of the verification methods for the previous phases.
Using the detailed design and the process specifications testing is done to uncover errors with in the boundary of the module. LIST OF TEST CASES PREPARED I tested step wise every peace of code.39 - . taking care that every statement in this executed at least once. STRUCTURAL TESTING (WITH BOX) INTRODUCTION White box testing are also called as unit testing focuses verification effort on the smallest unit of software i.data that resulted in executing every instruction in the program and module i. rather than an error associated only with the specific . Types of Testing * Unit Testing * Link Testing Unit testing focuses on verification effort on the smallest unit of software i.e the module. During the uncover errors with in the boundary of the module. the number of additional test cases that much be designed to achieve reasonable testing. sample data. 1. The white box testing is also called Glass box testing. I have generated a list of test cases. All the modules must be successful in the unit test before the start of integration testing. FUNCTIONAL TESTING (BLACK BOX) INTRODUCTION The testing method considers a module as a single unit and checks the unit at interface and communication with other modules rather getting in to details at statement level. To ensure that the coding is perfect two types is performed or for that matter is performed on all systems.e the module. Test cases that tell us some thing about the presence or absence of lessons of errors.e every path is tested. 2. LIST OF TEST CASES PREPARED Test cases that reduce by a count that a greater than one. Systems are not designed as entire nor are they tested as single systems. This is used to check all possible combinations of execution paths through the code at every module level. Here the module will be treated as a black box that will take some input and generate output. Output for a given set of input combinations are forwarded to other modules.
BIBILIOGRAPHY 1.Bernd Bruegge. Lethbridge & Robert Laganiere. 2. CONCLUSION We can conclude that project is very essential and useful for any Organization to manage its resources effectively and plan for future projects. Object Oriented Software Engineering .test at hand. Object Oriented Software Engineering: Practical software development using UML & Java Timothy C.Dutoite. Allen H. It is very effective and low-cost communication with high reliability.40 - . .
41 - ..
This action might not be possible to undo. Are you sure you want to continue?