Online Cinema
-
Upload
nimesh-sommanek -
Category
Documents
-
view
1.156 -
download
7
Transcript of Online Cinema
ONLINE MOVIE ZONE
Content At Glance
Acknowledgement
1 1. InIntroduction
1 Project Introduction
2 Project Profile
2. Preliminary Investigation
3 SDLC & Methodologies
4 Project Management
3. Requirement Definition & Specification
5 Requirement Engineering
6 Feasibility Study
7 Function & Non-Functional Requirements
8 Hardware & Software Requirements
4. System Analysis & Design
9 Tools & Technology
10 Software Design
5. Testing & Debugging
11 Validation & Verification
6. User Guide
12 Limitation & Future Enhancements
13 Bibliography
VGEC (6TH I.T. ) 1 2011
ONLINE MOVIE ZONE
PART: 1 INTRODUCTION
PROJECT INTRODUCTION PROJECT SUMMERY
VGEC (6TH I.T. ) 2 2011
ONLINE MOVIE ZONE
CHAPTER: 1 PROJECT INTRODUCTION
DEFINATION: The Online Movie Ticket system is used to make booking movie tickets
just a click away. Everything that can be bought in a movie theatre can easily be done by sitting
in a room at home. There always are two phases in an online system. The client side and the
Administrator side. This system largely reduces physical efforts and watching a movie was never
this comfortable.
If the customer wants to book a ticket of a movie, then one can book it with the help of just
one click. Then the added features are offered such as buying snacks and beverages. The point is
supposed to be noted that purchase of snacks and beverages is an optional step.This system also
provides a feature that enables a normal user to register into the website and become a member of
it. The theatre offers lucrative schemes to registered users.
Then the payment is to be done through credit card method. Here this system appreciates
credit card access from several different banks. After the payment is done, you have now
successfully booked your tickets in the theatre.
The basic flow of the project goes something like this. First of all, in the home page, the
user can have an overview of the movies currently going on. Then the user can select the desired
movie. The system then guides the user to another page where the user decides the area in which
he/she wishes the tickets to be booked. Once the area is decided, the user can now have a look at
the particular seat at which he/she is booked. Once the user has finished booking tickets, he/she
can now go for booking eatables or drinks.
One very important part of any website is the membership registration. Here, when
someone wishes to have an online membership, one has to fill up a form, provide the E-
Commerce identity, and then the transaction that one wishes. Point to be noted here is that the
transaction can only be valid if and only if the system supports it.
VGEC (6TH I.T. ) 3 2011
ONLINE MOVIE ZONE
Now comes the administration part. The administrator has its own user name and passkey.
The administrator can do verifications, updating, etc tasks. Here, the one very important thing the
user has to do is to keep track of the collections. So that when Friday comes, the administrator is
aware of which film to be replaced. The administrator can replace a new movie with an old one,
or can also add a new movie into the screens. The administrator can also make changes in the food
court items.
The E-Commerce must be handled with a lot of precision. Transactions need a lot of caring
while they are done. The database administrator is the one responsible for it. Account verification,
transactions, membership schemes application, etc are areas of the system where you need a lot
precision.
OBJECTIVES:
The main objectives of this project is to largely reduce physical efforts. The aim also is to
eliminate the need to stand in a queue to buy a movie ticket. The goal of enlargement of the
business can also be achieved by developing such a system.
Following are some of the main goals of the designed system:
Easier ticket booking process.
Lucrative offers for registered users.
To eliminate the need to stand in a queue.
To reduce physical efforts.
To save time and energy.VGEC (6TH I.T. ) 4 2011
ONLINE MOVIE ZONE
To save maximum paperwork.
There are some minor, negligible disadvantages of the project as well. It reduces human vacancy.
E-commerce is always full of risks.
SCOPE:
This system is very feasible. The core advantage of this system is that you don’t need to
hire too many people for booking tickets. Fewer people are needed to operate a site than to
operate a physical system. This system will only lead to profits once being implemented. This
system will help the firm owners to reach people’s home very easily. Brand endorsement also can
be done very effectively.
CHAPTER: 2 PROJECT SUMMERY
VGEC (6TH I.T. ) 5 2011
ONLINE MOVIE ZONE
Aim : Report on Online Movie Ticket Booking System.
Definition : ― The Online Movie Ticket system is used to make booking movie tickets just a
click away. Everything that can be bought in a movie theatre can easily be done by sitting in a
room at home. There always are two phases in an online system. The client side and the
Administrator side. This system largely reduces physical efforts and watching a movie was
never this comfortable.
Operating system : Windows 98,XP,2000,NT,Vista,2007,
Linux, Fedora, Red het. sun salaries.
Duration: 12 Weeks.
Report Developers:
Jhaveri Mitul A.( 080170116014) Patel arpit A.( 080170116028)Patel Bharat R.( 080170116029)
Project submitted to: Miss. Sheetal Solanki & Miss. Usha Yogi Vishwakarma Engineering College. IT DEPARTMENT
VGEC (6TH I.T. ) 6 2011
ONLINE MOVIE ZONE
PART: 2 Preliminary Investigation
SDLC & METHODOLOGY PROJECT MANAGEMENT
CHAPTER: 3 SDLC & METHODOLOGY
Sdlc: System development life cycle The Systems Development Life Cycle (SDLC), or Software Development Life Cycle in
systems engineering and software engineering, is the process of creat-ing or altering systems, and VGEC (6TH I.T. ) 7 2011
ONLINE MOVIE ZONE
the models and methodologies that people use to de-velop these systems. The concept generally
refers to computer or information sys-tems.
In software engineering the SDLC concept underpins many kinds of software
development methodologies. These methodologies form the framework for planning and
controlling the creation of an information system: the software development process.
Systems Development Life Cycle (SDLC) is a logical process used by a systems analyst to
develop an information system, includ-ing requirements, validation, training, and user
(stakeholder) ownership. Any SDLC should result in a high quality system that meets or exceeds
customer expectations, reaches completion within time and cost estimates, works effectively and
efficiently in the current and planned Information Technology infrastructure, and is inexpen-sive
to maintain and cost-effective to enhance.
Computer systems are complex and often (especially with the recent rise of Service-
Oriented Architecture) link multiple traditional systems potentially sup-plied by different software
vendors. To manage this level of complexity, a number of SDLC models have been created:
"waterfall"; "fountain"; "spiral"; "build and fix"; "rapid prototyping"; "incremental"; and
"synchronize and stabilize"
VGEC (6TH I.T. ) 8 2011
ONLINE MOVIE ZONE
There are seven step of SDLC:
1. Planning
2. Design
3. Implementation
4. Testing
5. Acceptance
6. Maintenance
7. Disposal
1. Planning –
Everything starts with a concept. It could be a concept of some-one, or everyone.
However, there are those that do not start out with a con-cept but with a question, ―What do you
want? they ask thousands of people in a certain community or age group to know what they want
and decide to create an answer. But it all goes back to planning and conceptualization.
VGEC (6TH I.T. ) 9 2011
ONLINE MOVIE ZONE
It is also essential for developers to know that this stage deals a lot with upper management so if
you are not the owner of the software devel-opment company; you have to deal with them a lot in
this stage.
2. Design –
Once planning and arguing with the manager or the owner about the plan and somehow
convincing them, it is time to design or create a rough plan regarding the software. Developers
will work together and decide the initial specifics of the software to be created.
They will decide what platform or programming language to use, which will take care the
coding of a certain part of the software and even the time frame. This could be conducted by a
project manager along with the developers. The workflow about the project is also laid out. Some
will also treat this stage as planning for the back-end op-erations in developing the software. It is
not only important that developers should have a solid plan; they should at least know that
something will help them achieve to finish the program faster.
3. Implementation –
The first two stages are quite common in all SDLC models. However, things change
starting on this stage. When the design and all the things that you need have been laid out, it is
time to work on the plan. Some developers, especially those that follow the standard plan of
developing soft-ware will work on the plan and present them for approval. Imple-mentation in
some SDLC models is a combination of implementation and testing to a focus group.
4. Testing –
This could mean two things depending on an SDLC model. The first type of testing is the
actual testing by users. This is usually done in mod-els wherein implementation does not go with
pre-testing with users. On the other hand, there are also testing that uses professionals in the field.
This test-ing is aimed in cleaning the software of all the bugs altogether.
For software that are set for public release, the software is first tested by other developers
who were not in charge in creating the software. They will weed out the bugs and suggest fixes if
VGEC (6TH I.T. ) 10 2011
ONLINE MOVIE ZONE
every they find one. Once this stage is completed, it is time to test the software not just to the
develop-ers but to actual users.
5. Acceptance –
When the software is released to be used by a certain company, acceptance means the
software is implemented as an added tool or could be replacing another software that has been
found too wanting after years of use. On the other hand, when the software is implemented to
the public a new software could be an added software for use. It is difficult to change public
software but they are not closing their ears to new software. So developers will always have a
fighting chance in the market as long as they implement good software for public use.
6. Maintenance –
When the software is implemented, it does not mean that the software is good as it is. All
SDLC models include maintenance since there are absolutely no way that a software will be
working perfectly. Someone has to stay in the present software to take a look and ensure the
program works perfectly.
When the software is implemented in public. Software compa-nies either set up a call center
or an e-mail service to address the concerns of the consumer. As we have indicated in previous
chapters, Maintenance is quiet an easy task as long as the right food and product is serve in an ex-
pected time frame. However, it is always a challenge when something goes wrong. The whole
team might not be there to help the developer so addressing a ma-jor concern could never be
answered.
7. Disposal –
Last but not the least, when a software is being outmoded, it is not just all deletion of
files. Project managers should take a look at all the af-fected files of the software and determine
which file to protect and dispose. Disposal will also require an efficient purging of documents so
that no traces of information could be retrieved from memory devices inside the computer.
VGEC (6TH I.T. ) 11 2011
ONLINE MOVIE ZONE
If the company is planning to re-use the company computers that is ok but it is an entirely
different story when the computer and other re-lated equipments is sold.
These are the common steps in SDLC. Although they might have different versions, they
all end up with one thing: creating a software to make the world a better place. These seven steps
could be even bigger or ex-panded depending on the SDLC model that has been followed by
different developers. These strategies were created by the same programmers and they sure know
that something is needed to be done to create better software.
VGEC (6TH I.T. ) 12 2011
ONLINE MOVIE ZONE
Chapter: 4 PROJECT MANAGEMENT
1. Project planning and scheduling:
Project Development Approach
As this product is pure business application the solution, is known. So mapping a
customer’s desires and a firm’s development must not be a bigger issue. So, we keep these factors
in mind and the model of the software development process was derived from other engineering
processes and it is undergoing. As this project is a live project, it is under development process
until and unless customer’s final requirements are known.
The project has to develop from many stages before reaching its final development. It
offers meanings of the developments process more visible. Because from one phase to another.
This model is known as the “Iterative Waterfall Model”.
The waterfall model derives its name due to the cascading effect from one phase to the
other as is illustrated in Figure. In this model each phase is well defined with a starting and an
ending point, with identifiable deliveries to the next phase. This model is sometimes referred to as
the linear sequential model or the software life cycle.
It includes following activities:
Proposal writing.
Project planning and scheduling.
Project costing.
Project monitoring and reviews.
Personnel selection and evaluation.
Report writing and presentations.
VGEC (6TH I.T. ) 13 2011
ONLINE MOVIE ZONE
[ iterative waterfall model]
The model consists of six distinct stages, namely:VGEC (6TH I.T. ) 14 2011
ONLINE MOVIE ZONE
1. Requirements analysis phase
(a) The problem is specified along with the desired service objectives (goals),
(b) The constraints are identified.
2. In the specification phase, the system specification is produced from the detailed definitions
of (a) and (b) above. This document should clearly define the product function.
3. In the system and software design phase, the system specifications are translated into a
software representation. The software engineer at this stage is concerned with:
Data structure
Software architecture,
Algorithmic detail and
Interface representations.
The hardware requirements are also determined at this stage along with a picture of the
overall system architecture. By the end of this stage the software engineer should be able to
identify the relationship between the hardware, software and the associated interfaces. Any
faults in the specification should ideally not be passed ’down stream’.
4. In the implementation and testing phase stage, the designs are translated into the software
domain.
Detailed documentation from the design phase can significantly reduce the coding efforts.
Testing at this stage focuses on making sure that any errors are identified and that the
software meets its required specification.
5. In the integration and system testing phase, all the program units are integrated and tested to
ensure that the complete system meets the software requirements. After this stage the software
is delivered to the customer.
VGEC (6TH I.T. ) 15 2011
ONLINE MOVIE ZONE
6. The maintenance phase is the usually the longest stage of the software. In this phase the
software is updated to:
Meet the changing customer needs,
Adapted to accommodate changes in the external environment,
Correct errors and oversights previously undetected in the testing phases,
Enhancing the efficiency of the software.
Observe that feed back loops allow for corrections to be incorporated into the model. For
example a problem/update in the design phase requires a ‘revisit’ to the specifications phase.
When changes are made at any phase, the relevant documentation should be updated to reflect that
change.
ADVANTAGES:
Testing is inherent to every phase of the waterfall model,
It is an enforced disciplined approach,
It is documentation driven, that is, documentation is produced at every stage.
2.RISK MANAGEMENT
There are four stages to risk management planning:
1. Risk Identification; 2. Risk Quantification; 3. Risk Response; 4. Risk Monitoring and Control Assessment.
RISK IDENTIFICATION:
Risk Identification is the first stage of risk management. It is concern with discovering
possible risks to the project. In principal, these should not be assessed or prioritized at this stage,
although in practice risks with very minor consequences or very low probability risks are not
VGEC (6TH I.T. ) 16 2011
ONLINE MOVIE ZONE
usually considered. During the project development we faced following risk and try to solve them
by best efforts.
Business Impact Risk,
Staff Risk,
Process Risk,
Technology Risk.
RISK ANALYSIS:
Identifying risk and drawing up plans to minimize their effect on the project work is called
Risk Analysis. Risk may threaten the project, the software that is being developed.
Risk analysis and management are a series of steps that help a software team to understand
and manage uncertainty. Many problems can plague a software project. A risk is a potential
problem – it might happen, it might not. But, regardless of the outcomes, its really good idea to
identify it, assess its probability of occurrence, estimate its impact, and establish a contingency
plan should the problem occur.
Business Impact Risk:
This is the risk where concern is that of not being able to create the product that has impact
on clients business. If this project fails then all the future plans depending on this project would
also fail.
Staff Risk:
This risk is dependent on the ability, experience and willingness of the software team
members to create the working product. All team members should put maximum effort to finish
VGEC (6TH I.T. ) 17 2011
ONLINE MOVIE ZONE
the product on time. Employee risk is one of the major risks to be considered while designing the
software.
Process Risk:
Process risk involves risks involving product quality. If the product developed does not
meet the standards set by the customer or the development team then it will be a failure. The
process must be clearly defined and responsibility should be divided among the members. True
business need should be described to avoid risk.
Technology Risk:
Technology risk involves using technology that already is or soon to become obsolete in
the development of the software. Since technology changes rapidly nowadays so a matured
technology should be used in the development of the software. Technology should be selected in
such a way that it is long sustaining and is functional for longer period of time.
RISK PLANNING:
Risk planning process considers each of the key risks which have been identified and
identified strategies to manage the risk. Again there is no simple process, which can be followed
to establish risk management plans. It relies on the judgment and experience of the project
manager.
Risk Strategy
Change to the requirements which
require major design rework are
Derive traceability information to assess
requirement change impact, maximize
VGEC (6TH I.T. ) 18 2011
Project Management
ONLINE MOVIE ZONE
proposed. information hiding in the design.
The requirements are not
understood properly.
Analyze the requirements thoroughly.
The time required to develop the
software is under-estimated.
Allocate one more week than deadline.
There is a lack of training on tools
that are being used.
Allocate more time for proper training on
the tools.
The resources are insufficient. Analyze the tools required prior and
allocate them before hand.
Technology will not meet
Expectations
Developed Proof of Concept
[Table: Risk Planning]
3: ESTIMATION
EFFORT ESTIMATION
The major efforts taken for the development of the portal:
Explored following areas:
o Case Manager Standards for SRS and SDD.
o Java Script and Ajax (Asynchronous Java Script and XML).
o MVC2 (Model View Controller 2).
Implementation of the above.
VGEC (6TH I.T. ) 19 2011
ONLINE MOVIE ZONE
PART 3 Requirement Definition &
Specification
Requirement Engineering
Feasibility Study
Function & Non-Functional Requirements
CHAPTER: 5 Requirement Engineering
Software requirements engineering is the process of determining what is to be produced
in a software system. In developing a complex software system, the re-quirements
VGEC (6TH I.T. ) 20 2011
ONLINE MOVIE ZONE
engineering process has the widely recognized goal of determining the needs for, and the
intended external behavior, of a system design. This process is regarded as one of the most
important parts of building a software system:
" The hardest single part of building a software system is deciding what to build. No other
part of the conceptual work is as difficult a establishing the detailed technical requirements,
including all the interfaces to people, to machines, and to other software systems. No part of the
work so cripples the resulting systems if done wrong. No other part is more difficult to rectify
later" (Brooks, 1987)
Tracing the emergence of significant ideas in software development over the years, one
can observe that in the '60s the attention was on coding, in the '70s on de-sign and in the '80s on
specification. Jawed Siddiqi agrees that requirements engi-neering will be a critical issue in the
'90s (Siddiqi, 1994). Siddiqi challenges that "requirements describe the 'what' of a system, not the
'how'".
However, in the process of requirements engineering it is often difficult to state the real
'what' level of a system because one person's 'how' may be another person's 'what' and conversely.
In this perspective, the requirements engineer faces a complex problem, in meeting the needs of
the customer and at the same time meet-ing the needs of the designer.
Requirements engineering is an important aspect of any software project, and is a general term
used to encompass all the activities related to requirements.
The four specific steps in software requirements engineering are:
Requirements elicitation
Requirements analysis
VGEC (6TH I.T. ) 21 2011
ONLINE MOVIE ZONE
Requirements specification
Requirements validation
Although they seem to be separate tasks, these four processes cannot be strictly separated
and performed sequentially. Some of the requirements are implicit in the working practices, while
others may only arise when design solutions are pro-posed. All four are performed repeatedly
because the needs are often impossible to realize until after a system is built. Even when
requirements are stated initially, it is likely they will change at least once during development, and
it is very likely they will change immediately after development.
Requirements engineering is one of the most important steps in a software engineering
development process, because an effective elicitation process will pro-vide a set of requirements
that can be used by the software development team.
We first examine the participants in a requirements elicitation process. There are three
main categories of participants: the developer, the user and the customer. In addition, a major
requirements elicitation can involve other people such as lawyers, government standards
organizations and so on. From this point of view, this process may be regarded as a negotiation
process, where potential "users" of the system explore and fully understand the requirements,
agreeing on what they want and what they need, while the developers become confident that they
are solving the right problem.
A successful requirements process includes effective ways to encourage part-nerships
between customer and designers and team members. The process gathers information, validates
everyone's understanding of the information gathered and communicates open issues. that there is
a failure to realize that appropriate human communication mechanisms need to be established as
part of the requirements process. If different interest groups do not communicate effectively with
each other, each will seek to exert power and influence over the others.
VGEC (6TH I.T. ) 22 2011
ONLINE MOVIE ZONE
During the requirements discussion phase, answers to questions about re-quirements
provide stakeholders with a deeper understanding of the requirements and help them notice
inconsistencies or missing requirements. The requirements evolution is the phase where the
decisions about changing or freezing a requirement are taken.
In this context, success in meeting the real needs of the software system is contingent upon
the ability of users to clearly specify what their requirements are. For this reason, requirements
definition needs close interaction between developers and end-users of the software. It is critical
that requirements engineering tools must support collaborative development of the software
requirements negotiation. Re-quirements definition should be an iterative process where, through
reflection and experience, users become familiar with the technology and developers become fa-
miliar with the work. For example, scenarios, prototypes or mock-ups which pro-vide the
opportunity for the users to "experience" the new technology and for the developers to
"experience" the work practice.
The characteristics of good requirements are variously stated by different writers, with
each writer generally emphasizing the characteristics most appropriate to their general discussion
or the specific technology domain being addressed. However, the following characteristics are
generally acknowledged
Characteristic Explanation Unitary (Cohesive) The requirement addresses one and only one thing.
Complete The requirement is fully stated in one place with no
missing in-formation.
Consistent The requirement does not contradict any other
requirement and is fully consistent with all
VGEC (6TH I.T. ) 23 2011
ONLINE MOVIE ZONE
authoritative external documentation.
Non-Conjugated (Atomic) The requirement is atomic, i.e., it does not contain
conjunctions. E.g., "The postal code field must
validate Ameri-can and Canadian postal codes"
should be written as two separate requirements: (1)
"The postal code field must validate American postal
codes" and (2) "The postal code field must validate
Cana-dian postal codes".
Traceable The requirement meets all or part of a business need
as stated by stakeholders and authoritatively
documented.
Current The requirement has not been made obsolete by the
passage of time.
Feasible The requirement can be implemented within the
constraints of the project.
Unambiguous The requirement is concisely stated without recourse
to technical jargon, acronyms (unless defined
elsewhere in the Requirements document), or other
esoteric verbiage. It expresses objective facts, not
subjective opinions. It is subject to one and only one
interpretation. Vague subjects, adjectives,
prepositions, verbs and subjective phrases are
avoided. Negative statements and com-pound
statements are prohibited.
Mandatory The requirement represents a stakeholder-defined
VGEC (6TH I.T. ) 24 2011
ONLINE MOVIE ZONE
characteristic the absence of which will result in a
deficiency that cannot be ameliorated. An optional
requirement is a contradiction in terms.
Verifiable The implementation of the requirement can be
determined through one of four possible methods:
inspection, demonstration, test or analysis.
Chapter: 6 Feasibility StudyThere are three types of feasibility.
VGEC (6TH I.T. ) 25 2011
ONLINE MOVIE ZONE
1) Operational Feasibility
2) Technical Feasibility
3) Financial Feasibility
4) Schedule Feasibility
1) Operational Feasibility:
This Web Site may also be used by persons who don‘t have in depth knowledge of the Web
Site Surfing. So, a help file has to be provided ensur-ing that the user is able to use all the
facilities to the full. Care was taken so that the Web Site is user-friendly to the maximum.
This project will fairly after it is developed and installed. It has an in-terface which is fairly
familiar to almost all users who are already using the webs. Also it provides enough security. Like
there is support from the man-agement and from the users also. They will be getting ‗Quality
Service‘. So I make a Site Guide as help which is useful for user as some extant. It also gives
good facilities along with easy-to-use interfaces. So it is operationally feasible.
2) Technical Feasibility:
All the necessary technologies to create this project are quite easily available. All we
require storage and back up media like hard disks & drives etc. The above mentioned storage and
back up media has the technical capac-ity to hold the user data. The flexibility is quite good. It is
possible to expand the service to new Branches.
The project is in PHP/MySQL which is free source & easily available. The system is
accurate, reliable and easy to use and secure, hence technically feasible. This project is
implemented using PHP Programming Language. As it was easily available and had the required
VGEC (6TH I.T. ) 26 2011
ONLINE MOVIE ZONE
knowledge regarding the features of this language, this was relatively feasible field. Also it can
work with any Operating System it is a platform independence project.
3) Financial Feasibility:
Financially also it is feasible because software and all other thing are free of cost available
at market.Just primary finance is needed to have server & domain setup to make site available on
internet. Once it will set up, after that no extra charges require so it also economically feasible. So
all it is fi-nancial feasible.
4) Schedule Feasibility:
Another important feature to be considered during the feasibility study was the time limit:
3 months. The main concern during the schedule feasibil-ity was to cover the wide range of
applications and facilities to be provided with the software during such a short period of time. But
due to technical knowledge about Java, very little difficulty was encountered in deciding the
different modules and implementing the modules.
CHAPTER: 7 FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS
VGEC (6TH I.T. ) 27 2011
ONLINE MOVIE ZONE
7.1 FUNCTIONAL REQUIREMENTS
Analyzing the basic Requirement of the project we concluded that the website should be
such as that allows jobseekers who search the job effectively and efficiently anytime related to
search the job effectively and efficiently any time related to their qualification and requirements
(location, salary etc.)
User can directly apply to particular or number of Companies directly. They can
receivethese jobs requirements by mail to their Email-Ids. Hence all these requirements comprised
and compelled us to the actual definition of project that could satisfy the above needs of
jobseekers.
7.1.1 Identification of Functional Requirements
The high-level functional requirements often need to be identified from an informal
problem description document or from a conceptual understanding of the problem. Each high-
level requirement characterizes a way of system usage by some user to perform some meaningful
piece of work.
7.1.2 Documentation of Functional Requirements
For documenting the functional requirements, I need to specify the set of functionalities
supported by the system. A function can be specified by identifying the state at which the data is
to be input to the system, its input data domain, the output data domain, and the type of processing
to be carried on the input data to obtain the output data.
The whole system requires the continuous sacrifice of an operator.
Power supply is also the main aspect to perform the task accurately.
The transaction must make changes to database of the system.
VGEC (6TH I.T. ) 28 2011
ONLINE MOVIE ZONE
7.2 NON-FUNCTIONAL REQUIREMENTS
7.2.1 Maintainability:
The Application is easily be maintain by the administrator, he will be provided with
password to maintain the description of the thing, the reports etc. On-line resume or clients upload
involves the database to be updated continuously with the corresponding user-ID and password.
7.2.2 Portability:
It is certain to say that this application is very portable, as it is developed in .NET. All .NET
programs are portable. They can be executed on varieties of Operating Systems. It is a platform
independent and also very secure.
7.2.3 Usability
This application is very important in providing a common ground for both the employers
and the employees so both get the best and filtered or cream as they want depending on the
requirement and capability.
7.2.4 Accuracy
As we are developing the application, we must make the system that is very accurate in its
functions. All the data should keep work properly, they getting perfect input, processing it
accurately and producing the perfect output. Accuracy is the most important non-functional
characteristic or requirement of the system.
7.2.5 Interface Issue
The interface of the system should be very user friendly, because I am assuming that our
most of users are non-technical users. Even operators and managers of that system are not aware
of the technical portion. User should find him very comfortable with that interface, though he
might be customer. User could navigate anyway he should be frequently guided through all input
VGEC (6TH I.T. ) 29 2011
ONLINE MOVIE ZONE
processing. He could get the output in which form he or she wants. It is the most attractive part of
the software, from that I can see the satisfaction level of the users.
7.2.6 Constraints
Constraints are the field that software is poor in that field; minimization of constraints is
must in the process of system developments. This system should be solid in those things; it should
pass away all the constraints, such as insertion of text in place of numbers, or say automatic type
casting.
VGEC (6TH I.T. ) 30 2011
ONLINE MOVIE ZONE
PART 4
System Analysis & Design
SOFTWARE DESIGNs
Chapter: 8 SOFTWARE DESIGNS
1) ENTITY RELATIONSHIP( E-R) DIAGRAM
VGEC (6TH I.T. ) 31 2011
ONLINE MOVIE ZONE
2) DATA FLOW DIAGRAMS( DFD) :
Logical Data Flow Diagram [Context Level]:VGEC (6TH I.T. ) 32 2011
ONLINE MOVIE ZONE
Logical Data Flow Diagram [Level-1]:
VGEC (6TH I.T. ) 33 2011
ONLINE MOVIE ZONE
3) FLOW CHART :
VGEC (6TH I.T. ) 34 2011
ONLINE MOVIE ZONE
MAIN MODULES OF THE SYSTEM:
1. Movie Management
VGEC (6TH I.T. ) 35 2011
ONLINE MOVIE ZONE
This is the main module of project Online Ticket Booking System. Here project
development life cycle is followed to develop any project. First the project definition comes to
the Admin from the service users. Project manager will specify the number of modules in the
project and will also specify the hardware and software requirements. Admin can plan whole
project. Such as in how many days the given project should be completed, how many
deliverables should be given to the service users and the list of task and their performers. Admin
can also specify the start date and end date for whole project, as well as for each and every user
story, release or a particular task.
Features of this module:
Allows admin to create new project definition.
Allows admin to distribute work load and task among the project members.
Time Tracking – who is working on which module and for how many hours?
Security schemes.
Allows uploading attachments related to any project.
Discussion forum.
Maintains History.
Project planning.
Service user can monitor the status of project remotely.
2. Ticket Booking
This module also includes Ticket booking. Here any type of user can book tickets or can
get membership by registration. The newly added members are added in the membership list and
they all are provided related ongoing schemes for ticket booking or any other event approach.
User can also select the duration of his/her membership. And can also monitor the status of the
account.
Features of this module:
Allows user to book tickets normally.
Allows user to create new membership account by registration.
VGEC (6TH I.T. ) 36 2011
ONLINE MOVIE ZONE
Allows user to book tickets with added user discounts.
Allows user to give feedbacks.
Discussion forum.
Maintains the history.
User can monitor the status of the account.
3. Transaction/Payment
This is a very important part of the system. Here, a user has to enter his/her valid identities
to finish the transactions. The user can normally pay by the credit cards. Debit cards or shopping
cards are also valid in this system. Validations are put here, so that any false information may get
noticed and rejected. After the payment is done, the database is updated. And thus the bill is paid.
For the registered users, their additional scheme may get deducted (discounts or anything).
After this, the user gets a confirmation about the ticket he/she has booked. This
confirmation can be a ticket itself or it also can be a username or a password.
4. Box Office
The system will keep a track of all the movies and its collections. So that replacing a new
movie by an old one becomes easy for the administrator.
5. Movie Preview
The system provides an overview to the movie. The user, by the help of it can get to know
how the movie might be and it may also help the user to decide among the options. The overview
may contain official trailer of the movie, press conferences by the makers, star cast lists,
interviews, press reports, critic’s reports, etc.
VGEC (6TH I.T. ) 37 2011
ONLINE MOVIE ZONE
Part 5
Testing & Debugging
Validation & Verification
Chapter: 9 Validation & Verification
System testing & VERIFICATION:
VGEC (6TH I.T. ) 38 2011
ONLINE MOVIE ZONE
System testing of software or hardware is testing conducted on a complete,
integrated system to evaluate the system's compliance with its speci-fied requirements. System
testing falls within the scope of black box testing, and as such, should require no knowledge of the
inner design of the code or logic. [1]
As a rule, system testing takes, as its input, all of the "integrated" software compo-
nents that have successfully passed integration testing and also the software system itself
integrated with any applicable hardware system(s). The purpose of integration testing is to detect
any inconsistencies between the software units that are integrated together (called assemblages) or
between any of the assemblages and the hardware. System testing is a more limiting type of
testing; it seeks to detect defects both within the "inter-assemblages" and also within the system as
a whole.
Validation and Verification is the name given to the checking and analysis processes that
ensures that software conforms to its specification and meets the needs of the customers who are
paying for that software.
Validation and Verification is a whole life-cycle process. It starts with requirements
reviews and continues through design reviews and code inspections to product testing.
SR. NO
Validation Verification
1 Validation is the process of determining whether a fully developed system conforms to its requirements specification.
Verification is the process of determining whether the output of one phase of software development conforms to that of its previous phase
VGEC (6TH I.T. ) 39 2011
ONLINE MOVIE ZONE
2 Validation: Are we building right product?
Verification: Are we building the
Product right?
3 Validation ensures that the software meets the expectations of the customers.
Verification involves checking that the software conforms to its specification.
Why System Testing is important?
System Testing is a crucial step in Quality Management Process.
In the Software Development Life cycle System Testing is the first level where the System
is tested as a whole
The System is tested to verify if it meets the functional and technical requirements
The application/System is tested in an environment that closely resembles the production
environment where the application will be finally deployed .
The System Testing enables us to test, verify and validate both the Business requirements
as well as the Application Architecture
Prerequisites for System Testing:
The prerequisites for System Testing are:
All the components should have been successfully Unit Tested
All the components should have been successfully integrated and Integration Testing
should be completed
An Environment closely resembling the production environment should be created.
When necessary, several iterations of System Testing are done in multiple environment.
VGEC (6TH I.T. ) 40 2011
ONLINE MOVIE ZONE
Steps needed to do System Testing:
The following steps are important to perform System Testing:
Step 1: Create a System Test Plan
Step 2: Create Test Cases
Step 3: Carefully Build Data used as Input for System Testing
Step 4: If applicable create scripts to Build environment and to automate Execution of
test cases
Step 5: Execute the test cases
Step 6: Fix the bugs if any and re test the code
Step 7: Repeat the test cycle as necessary
Software Inspection
Analyze and check system representations such as the requirements document, design diagrams and the
program source code. They may be applied at all stages of the process.
VGEC (6TH I.T. ) 41 2011
ONLINE MOVIE ZONE
LEVELS OF TESTING
Black-Box Testing
Black box testing is an approach to testing where the tests are derived from the program or
component specification. Black box testing is also known as “Functional Testing” because the
tester is only concerned with the functionality and not the implementation of the software.
In my project I input all the information that is necessary for it. I also check for validation.
The numeric field does not accept the character type of data or any other type of symbols.
White-Box Testing
White box testing is an approach to testing where the tests are derived from knowledge of
the software’s structure and implementation.This approach is sometimes called “Structural
Testing”, “glass box testing” or “clear-box testing”.In my project I give meaningful name to all
variables and constants, forms, labels, etc.
VGEC (6TH I.T. ) 42 2011
ONLINE MOVIE ZONE
Part 6User guide
Limitation & Future Enhancements conclusion
Bibliography
Chapter: 10 limitation & future enhancement
VGEC (6TH I.T. ) 43 2011
ONLINE MOVIE ZONE
Limitations:
The user must have an E-Commerce identity to be facilitated by this system. A user
cannot use direct cash to buy tickets. Transactions are done virtually, not really.
The online transactions are always full of risks. Your money and information can be
at a risk if u expose it on the network.
A user can not have the tickets at any cost once the show has gone house full. Black
market of ticket is impossible over the network.
Future Enhancements:
The administrator can put a link where the user can download some stuff like songs
of a movie, full movies, wall papers, etc.
Tickets of events other than movies could also be booked through this system in
future.
Chapter : 11 conclusion
This system can largely reduce the physical efforts that are needed to book a ticket of
movie show. The system also has a feature to allow the user to have a sneak peak to the movie.
VGEC (6TH I.T. ) 44 2011
ONLINE MOVIE ZONE
Movie trailers are uploaded, so that making a decision becomes a bit easier for the user. The user
can also have a look at what the critics has to say about the movie. The user can also see the
collection that the user has grossed over a particular period of time. The user can also get the idea
about what the upcoming movies are all about. Trailers, interviews, critic’s reports, and all the
gossips related to that movie.
The above given features are only at a distance of a click. This system makes the user
believe that watching a movie was never this easy. The need to stand in a queue with all the
unease is totally eliminated. This system has all one need.
It is very correctly said that the biggest room in the world is the room of improvement.
Though this project has many exciting features, there always is a scope for enhancement. I have
tried my level best to make this system the best available around. I hope this system pleases not
only the firm in which I made it and the ones whom I need to submit it, but also everyone that
experiences it.
I have spent my most precious time behind the construction of this system. Though, any
suggestions are always welcome.
Chapter: 12 Bibliography
1. www.wikipedia.com
2. www.bigcinemas.com VGEC (6TH I.T. ) 45 2011
ONLINE MOVIE ZONE
3. www.bookmyshow.com
4. Reference books used:
Visual Studio 2008
System Analysis and Design by James McBannot
Software Engineering by Pressman
VGEC (6TH I.T. ) 46 2011