Structural Analysis and Design of Foundations: A Comprehensive Handbook for S...
Report on mall automation
1. INDEX
1. Project Introduction
2. Scope of the Project
3. Skill Set Required
4. System Requirements
5. Feasibility Analysis
6. Project Designing
7. Project Coding Details
8. Test Methods Employed
9. Project Implementation Details
10. Limitations
11. Conclusion
12. Appendix-A (Company Profile)
13. Appendix-B (References)
1
2. 1. INTRODUCTION OF THE PROJECT
Mall Automation is an information portal that is proposed to provide information related to
Entertainment Places, other important places such as shopping centers, commercial complexes,
movie theatres etc.
The portal aims to provide complete information using the following three mechanisms:
• Information compiled by the parent company from different sources is to be presented on the
web site after through verification.
• Information to be collected by business owners posted on the portal is to be presented.
• Links of existing websites providing information are to be provided.
The objective of this portal i.e. MALL AUTOMATION providing all information regarding details
of different area in the mall. It includes shops for the people so that they can easily purchase all the
item from the sale place. It also includes restaurant so that people while purchasing can enjoy their
meal moreover, it includes multiplexes for their entertainment as they can watch movies. Users can
also avail the offers announced by the business owners like for example - discount offered by
business owners which really would attract the users. Mall will provide a single roof for various
shops. The mall performs the creation of a set of different shops, such as a book store, a shoe store,
etc. The mall greets an arriving customer, performs authentication for him/her and allocates him/her
the shopping cart. Mall presents the customer with a list of different stores available and allows the
customer to shop at any of stores in the mall.
1.1 MODULES
1.1.1 Search:
Through this module guest user can view information i.e. needed & deals posted by business
owners and can also send reviews to particular owner only after registered him / her.
1.1.2 Login:
In this module Business owner & Registered users enter the User id and password is checked
and only valid user id and password will get entry into their respective zone. This is a
security feature to avoid entry of unauthorized users.
2
3. 1.1.3 Registration Process:
Through this module new Business owners and users can registered. After giving their
details, they will get a user id and password. Then to get entry into Business section they
need to provide this id and password and only poster with valid id and password will get
entry into Business zone and only registered users can avail the deals offered by the business
owners. This is also a security feature to avoid entry of unauthorized user.
1.1.4 Manage Information:
Business owner using this module can provide and manage information, details about their
services and products.
1.1.5 Deals:
Through this module a business owner can post a new deals and offers for the user and can
also update these deals and offers. Business Owner can also check how many users are
showing interest in his deals and can also interact with them.
1.1.6 Administrator:
This is the Administrator’s module by which he keep the eye on whole site and maintain and
upgrade the site’s service for sake of users. Administrator can show banner ads of others,
which help the site in revenue.
3
4. 2. SCOPE OF PROJECT
The solution ease the handling of the management process of mall automatically by minimizing the
manual record keeping up to large extent by having the features of online updation, retrieval & store
data and searching operations and alert messages timely, for the current status transaction occurring.
This project can be further extended for all customers to show their reservation of tickets on the
website, searching of the data with different criteria.
4
5. 3. Skill Set Required
TECHNOLOGY USED
INTRODUCTION TO ASP.NET
ASP.NET offers a novel programming model and infrastructure that facilitates a powerful new class
of applications. ASP.NET is a compiled. NET-based environment, so one can author applications in
any .NET compatible language, including Visual Basic, C# and Jscript.NET. Developers can
effortlessly access the advantage of these technologies, which consist of a managed Common
Language Runtime environment, type safety, inheritance, and so on. With the aid of Microsoft
Visual Studio.NET Web development becomes easier.
Web Forms permits us to build powerful forms-based Web pages. When building these pages, we
can use Web Forms controls to create common UI elements and program them for common tasks.
These controls permit us to rapidly build up a WebForm.
Web services enable the exchange of data in client-server or server-server scenarios, using standards
like HTTP, SOAP (Simple Object Access Protocol) and XML messaging to move data across
firewalls. XML provides meaning to data, and SOAP is the protocol that allows web services to
communicate easily with one another. Web services are not tied to a particular component
technology or object-calling convention. As a result, programs written in any language, using any
component model, and running on any operating system can access Web services.
ASP.NET is Part of the .NET Framework:
The .NET Framework is an integral Windows component that supports building and running
the next generation of applications and XML Web services. The .NET Framework is designed to
fulfill the following objectives:
• To provide a consistent object-oriented programming environment whether object code is
stored and executed locally, executed locally but Internet-distributed, or executed remotely.
• To provide a code-execution environment that minimizes software deployment and
versioning conflicts.
• To provide a code-execution environment that promotes safe execution of code, including
code created by an unknown or semi-trusted third party.
5
6. • To provide a code-execution environment that eliminates the performance problems of
scripted or interpreted environments.
• To make the developer experience consistent across widely varying types of applications,
such as Windows-based applications and Web-based applications.
• To build all communication on industry standards to ensure that code based on the .NET
Framework can integrate with any other code.
The .NET Framework has two main components: the common language runtime and the .NET
Framework class library. The common language runtime is the foundation of the .NET Framework.
You can think of the runtime as an agent that manages code at execution time, providing core
services such as memory management, thread management, and remoting, while also enforcing strict
type safety and other forms of code accuracy that promote security and robustness. In fact, the
concept of code management is a fundamental principle of the runtime. Code that targets the runtime
is known as managed code, while code that does not target the runtime is known as unmanaged
code. The class library, the other main component of the .NET Framework, is a comprehensive,
object-oriented collection of reusable types that you can use to develop applications ranging from
traditional command-line or graphical user interface (GUI) applications to applications based on the
latest innovations provided by ASP.NET, such as Web Forms and XML Web services.
The .NET Framework can be hosted by unmanaged components that load the common language
runtime into their processes and initiate the execution of managed code, thereby creating a software
environment that can exploit both managed and unmanaged features. The .NET Framework not only
provides several runtime hosts, but also supports the development of third-party runtime hosts.
For example, ASP.NET hosts the runtime to provide a scalable, server-side environment for
managed code. ASP.NET works directly with the runtime to enable ASP.NET applications and
XML Web services, both of which are discussed later in this topic.
Internet Explorer is an example of an unmanaged application that hosts the runtime (in the form
of a MIME type extension). Using Internet Explorer to host the runtime enables you to embed
managed components or Windows Forms controls in HTML documents. Hosting the runtime in this
way makes managed mobile code (similar to Microsoft® ActiveX® controls) possible, but with
significant improvements that only managed code can offer, such as semi-trusted execution and
isolated file storage.
6
7. The following illustration shows the relationship of the common language runtime and the class
library to your applications and to the overall system. The illustration also shows how managed code
operates within a larger architecture.
.NET Framework in context:
.NET Framework Class Library:
The .NET Framework class library is a collection of reusable types that tightly integrate with
the common language runtime. The class library is object oriented, providing types from which your
own managed code can derive functionality. This not only makes the .NET Framework types easy to
use, but also reduces the time associated with learning new features of the .NET Framework. In
addition, third-party components can integrate seamlessly with classes in the .NET Framework.
For example, the .NET Framework collection classes implement a set of interfaces that you
can use to develop your own collection classes. Your collection classes will blend seamlessly with
the classes in the .NET Framework.
As you would expect from an object-oriented class library, the .NET Framework types
enable you to accomplish a range of common programming tasks, including tasks such as string
management, data collection, database connectivity, and file access. In addition to these common
tasks, the class library includes types that support a variety of specialized development scenarios.
7
8. For example, you can use the .NET Framework to develop the following types of applications and
services:
• Console applications.
• Windows GUI applications (Windows Forms).
• ASP.NET applications.
• XML Web services.
• Windows services.
For example, the Windows Forms classes are a comprehensive set of reusable types that
vastly simplify Windows GUI development. If you write an ASP.NET Web Form application, you
can use the Web Forms classes.
What's New in Microsoft SQL Server 2005
Microsoft® SQL Server™ 2005 extends the performance, reliability, quality, and ease-of-use
of Microsoft SQL Server version 7.0. Microsoft SQL Server 2005 includes several new features that
make it an excellent database platform for large-scale online transactional processing (OLTP), data
warehousing, and e-commerce applications.
The OLAP Services feature available in SQL Server version 7.0 is now called SQL Server
2005 Analysis Services. The term OLAP Services has been replaced with the term Analysis
Services. Analysis Services also includes a new data mining component. For more information, The
Repository component available in SQL Server version 7.0 is now called Microsoft SQL Server
2005 Meta Data Services. References to the component now use the term Meta Data Services. The
term repository is used only in reference to the repository engine within Meta Data Services. For
more information, .
The What's New topics contain brief overviews of the new features and links to relevant
conceptual topics that provide more detailed information. These conceptual topics provide links to
topics that describe the commands or statements you use to work with these features.
8
9. Working with Named and Multiple Instances of SQL Server 2005
With Microsoft® SQL Server™ 2005, you have the option of installing multiple copies, or
instances of SQL Server on one computer. When setting up a new installation of SQL Server 2005
or maintaining an existing installation, you can specify it as:
• A default instance of SQL Server:
This instance is identified by the network name of the computer on which it is running.
Applications using client software from earlier versions of SQL Server can connect to a default
instance. SQL Server version 6.5 or SQL Server version 7.0 servers can operate as default
instances. However, a computer can have only one version functioning as the default instance at
a time.
• A named instance of SQL Server:
This instance is identified by the network name of the computer plus an instance name, in the
format <computername><instancename>. Applications must use SQL Server 2005 client
components to connect to a named instance. A computer can run any number of named instances
of SQL Server concurrently. A named instance can run at the same time as an existing
installation of SQL Server version 6.5 or SQL Server version 7.0. The instance name cannot
exceed 16 characters. A new instance name must begin with a letter, an ampersand (&), or an
underscore (_), and can contain numbers, letters, or other characters. SQL Server sysnames and
reserved names should not be used as instance names. For example, the term "default" should not
be used as an instance name because it is a reserved name used by Setup.
Single and multiple instances of SQL Server 2005 (default or named) are available using the
SQL Server 2005 Personal Edition, the SQL Server 2005 Standard Edition, or the SQL Server 2005
Enterprise Edition.
9
10. Default Instances:
You cannot install a default instance of SQL Server 2005 on a computer that is also running
SQL Server 7.0. You must either upgrade the SQL Server 7.0 installation to a default instance of
SQL Server 2005 , or keep the default instance of SQL Server 7.0 and install a named instance of
SQL Server 2005 .
You can install a default instance of SQL Server 2005 on a computer running SQL Server
6.5, but the SQL Server 6.5 installation and the default instance of SQL Server 2005 cannot be
running at the same time. You must switch between the two using the SQL Server 2005 vswitch
command prompt utility.
Multiple Instances:
Multiple instances occur when you have more than one instance of SQL Server 2005
installed on one computer. Each instance operates independently from any other instance on the
same computer, and applications can connect to any of the instances. The number of instances that
can run on a single computer depends on resources available. The maximum number of instances
supported in SQL Server 2005 is 16.
When you install SQL Server 2005 on a computer with no existing installations of SQL
Server, Setup specifies the installation of a default instance. However, you can choose to install SQL
Server 2005 as a named instance instead by clearing the Default option in the Instance Name
dialog box. A named instance of SQL Server 2005 can be installed at any time: before installing the
default instance of SQL Server 2005 , after installing the default instance of SQL Server 2005 , or
instead of installing the default instance of SQL Server 2005 .
Each named instance is made up of a distinct set of services and can have completely
different settings for collations and other options. The directory structure, registry structure, and
service names all reflect the specific instance name you specify.
10
11. Database Architecture
Microsoft® SQL Server™ 2005 data is stored in databases. The data in a database is
organized into the logical components visible to users. A database is also physically implemented as
two or more files on disk.
When using a database, you work primarily with the logical components such as tables,
views, procedures, and users. The physical implementation of files is largely transparent. Typically,
only the database administrator needs to work with the physical implementation.
Each instance of SQL Server has four system databases (master, model, tempdb, and msdb)
and one or more user databases. Some organizations have only one user database, containing all the
data for their organization. Some organizations have different databases for each group in their
organization, and sometimes a database used by a single application. For example, an organization
could have one database for sales, one for payroll, one for a document management application, and
so on. Sometimes an application uses only one database; other applications may access several
databases.
It is not necessary to run multiple copies of the SQL Server database engine to allow multiple
users to access the databases on a server. An instance of the SQL Server Standard or Enterprise
Edition is capable of handling thousands of users working in multiple databases at the same time.
Each instance of SQL Server makes all databases in the instance available to all users that connect to
the instance, subject to the defined security permissions.
When connecting to an instance of SQL Server, your connection is associated with a
particular database on the server. This database is called the current database. You are usually
connected to a database defined as your default database by the system administrator, although you
can use connection options in the database APIs to specify another database. You can switch from
one database to another using either the Transact-SQL USE database_name statement, or an API
function that changes your current database context.
SQL Server 2005 allows you to detach databases from an instance of SQL Server, then
reattach them to another instance, or even attach the database back to the same instance. If you have
11
12. a SQL Server database file, you can tell SQL Server when you connect to attach that database file
with a specific database name.
12
13. 4.System Requirements
SOFTWARE AND HARDWARE REQUIREMANTS
SOFTWARE REQUIREMENTS:
1. Client OS with .NET framework 3.5
2. Server OS with .NET framework 3.5
3. MS SQL DBMS (2000 / 2005)
HARDWARE REQUIREMENTS:
1. Pentium IV Processors
2. 256 MB of RAM
3. 5GB of Hard Disk
4. One SQL based server
5. Client Machine
6. One domain name space to implement Web based services.
13
14. 5. FEASIBILITY ANALYSIS
5.1 Meaning of Feasibility Study
A feasibility study looks at the viability of an idea with an emphasis on identifying potential
problems and attempts to answer one main question: Will the idea work and should you proceed
with it?
A feasibility study is an evaluation of a proposal designed to determine the difficulty in carrying out
a designated task. Generally, a feasibility study precedes technical development and project
implementation. In other words, a feasibility study is an evaluation or analysis of the potential
impact of a proposed project.
A study of function, performance and constraints that may affect the ability to achieve an acceptable
system.
Before you begin writing your business plan you need to identify how, where, and to whom you
intend to sell a service or product. You also need to assess your competition and figure out how
much money you need to start your business and keep it running until it is established.
Feasibility studies address things like where and how the business will operate. They provide in-
depth details about the business to determine if and how it can succeed, and serve as a valuable tool
for developing a winning business plan.
Why Are Feasibility Studies so Important?
The information you gather and present in your feasibility study will help you:
• List in detail all the things you need to make the business work;
• Identify logistical and other business-related problems and solutions;
• Develop marketing strategies to convince a bank
• Serve as a solid foundation for developing your business plan.
14
15. 5.2 Meaning of Technical Feasibility
The Technical Feasibility Study assesses the details of how you will deliver a product or service
(i.e., materials, labor, transportation, where your business will be located, technology needed, etc.).
Think of the technical feasibility study as the logistical or tactical plan of how your business will
produce, store, deliver, and track its products or services.
A technical feasibility study is an excellent tool for trouble-shooting and long-term planning. In
some regards it serves as a flow chart of how your products and services evolve and move through
your business to physically reach your market.
5.2.1 Technical Feasibility of Project
5.2.1.1 The Technical Feasibility Study Must Support Your Financial Information
Do not make the mistake of trying to entice investors with your staggering growth projections and
potential returns on their investment that only includes income (revenue) to the business. With any
increase in revenue there is always an increase in expenses. Expenses for technical requirements
(i.e., materials and labor) should be noted in the technical feasibility study.
You should also not strictly rely on feasibility study conclusions to impress an investor. An
experienced investor or lending institution will read your entire report and come to their own
conclusions. Therefore, it is critical that the technical and financial data in your study reconcile. If
other parts of your feasibility study shows growth, you will also have to project labor and other costs
and the technical ability to support that growth.
The technical component serves as the written explanation of financial data because if offers you a
place to include detailed information about why an expense has been projected high or low, or why it
is even necessary. It demonstrates to potential investors and lenders (and in some cases, potential
clients) that you have thought about the long-term needs your business will have as it grows.
15
16. 5.2.1.2 Preparing an Outline for Writing Your Technical Feasibility Study
The order that you present technical information is not as important as making sure you have all the
components to show how you can run your business.
You do not have to include specific financial information in the technical portion of your feasibility
study, but all information in this component must support your financial data represented elsewhere.
Basic things that most businesses need to include in their technical feasibility study include:
• Materials
• Labor
• Transportation or Shipping
• Physical Location
• Technology
5.2.1.3 Calculating Material Requirements
In this section you list the materials you need to produce a product or service, and where you will get
those materials. Include information such as if volume discounts will be available as your business
grows, or if you ever plan to manufacture your own parts at some point in time.
• Things to include in your list of materials:
• Parts needed to produce a product,
• Supplies (glue, nails, etc.), and
• Other materials that are involved in producing or manufacturing your product.
You do not need to include actual financial data in this portion of the study but financial data
supporting your narrative assessment should be included in a separate spreadsheet as an attachment.
5.3 Meaning of Operational Feasibility
A study about the operational aspects of the system.
• Technical Analysis
16
17. During technical analysis, the technical merits of the system are studied and at the same time
additional information about performance, reliability, maintainability and predictability is
collected. Technical analysis begins with an assessment of the technical reliability of the
proposed system.
• What technologies are required for accomplished system function and performance?
• What new materials, methods, algorithms or processes are required and what is their
development risk?
• How will these obtained from technical analysis form the basis for another go/no-go decision
on the test system? If the technical risk is severe, if models indicate that the desired function
cannot be achieved, if the pieces just won’t fit together smoothly, it’s back to the drawing
board.
As the software is vary much economically feasible, then it is really important for it to be technically
sound. The software will be build among:
Front-End: ASP.NET
Logic Development: C#
Back-End: SQL SERVER 2005
5.3.1 Operational Feasibility of Project
The PIECES framework can help in identifying problems to be solved,
and their urgency:
Performance -- Does current mode of operation provide adequate
throughput and response time?
17
18. Information -- Does current mode provide end users and managers with
timely, pertinent, accurate and usefully formatted information?
Economy -- Does current mode of operation provide cost-effective
information services to the business? Could there be a reduction in
costs and/or an increase in benefits?
Control -- Does current mode of operation offer effective controls to
protect against fraud and to guarantee accuracy and security of data
and information?
Efficiency -- Does current mode of operation make maximum use of
available resources, including people, time, flow of forms,...?
Services -- Does current mode of operation provide reliable service? Is
it flexible and expandable?
• How do end-users and managers feel about the problem (solution)?
• It's not only important to evaluate whether a system can work but
also evaluate whether a system will work.
• A workable solution might fail because of end-user or management
resistance.
• Does management support the project?
• How do the end-users feel about their role in the new system?
• What end-users or managers may resist or not use the system?
• People tend to resist change. Can this problem be overcome? If
so, how?
• How will the working environment of the end-users change?
• Can or will end-users and management adapt to the change?
5.3 Meaning of Economic Feasibility:
It is a procedure that gives a picture of the various costs, benefits and rules associated with a
system. To what extent benefits outweigh costs is the function of cost/benefit analysis.
18
19. • Hardware Cost: Various hardware requirements have already been mentioned and the
hardware cost may be ascertained on that basis.
• Operating Cost: No day-to-day costs are involved. However, the application needs to be
registered which is a one time expenditure and the domain name needs to be renewed on
a yearly basis.
• Benefits: A system is also expected to provide benefits. The first task is to identify each
benefit and then assign a monetary value to it. Benefits may be tangible or intangible,
direct or indirect. Some of them are:
• User friendly interface
• Properly organized system
• Proper work flow
• Information will be well used
5.4.1 Economic Feasibility of Project
The bottom line in many projects is economic feasibility.
• During the early phases of the project, economic feasibility
analysis amounts to little more than judging whether the possible
benefits of solving the problem are worthwhile.
• As soon as specific requirements and solutions have been
identified, the analyst can weigh the costs and benefits of each
alternative.
• This is called a cost-benefit analysis.
Cost/Benefit Analysis
• The purpose of a cost/benefit analysis is to answer questions
19
20. such as:
• Is the project justified (because benefits outweigh costs)?
• Can the project be done, within given cost constraints?
• What is the minimal cost to attain a certain system?
• What is the preferred alternative, among candidate solutions?
• Examples of things to consider:
• Hardware/software selection
• How to convince management to develop the new system
• Selection among alternative financing arrangements
(Rent/lease/purchase)
• Difficulties -- discovering and assessing benefits and costs; they
• can both be intangible, hidden and/or hard to estimate, it's also
hard to rank multi-criteria alternatives
20
21. 6. PROJECT DESIGNING
SYSTEM DESIGN
6.1 MEANING OF SYSTEM DESIGN
Systems design is the process or art of defining the architecture, components, modules, interfaces,
and data for a system to satisfy specified requirements. One could see it as the application of systems
theory to product development. There is some overlap with the disciplines of systems analysis,
systems architecture and systems engineering.
If the broader topic of product development "blends the perspective of marketing, design, and
manufacturing into a single approach to product development, then design is the act of taking the
marketing information and creating the design of the product to be manufactured. Systems design is
therefore the process of defining and developing systems to satisfy specified requirements of the
user. Until the 1990s systems design had a crucial and respected role in the data processing industry.
In the 1990s standardization of hardware and software resulted in the ability to build modular
systems. The increasing importance of software running on generic platforms has enhanced the
discipline of software engineering.
Object-oriented analysis and design methods are becoming the most widely used methods for
computer system design. The UML has become the standard language used in Object-oriented
analysis and design. It is widely used for modeling software systems and is increasingly used for
high designing non-software systems and organizations.
The logical design of a system pertains to an abstract representation of the data flows, inputs and
outputs of the system. This is often conducted via modelling, which involves a simplistic (and
sometimes graphical) representation of an actual system. In the context of systems design, modelling
can undertake the following forms, including:
Data flow diagrams
Entity Life Histories
21
22. Entity Relationship Diagram
The physical design relates to the actual input and output processes of the system. This is laid down
in terms of how data is inputted into a system, how it is verified / authenticated, how it is processed,
and how it is displayed as output.
Physical design, in this context, does not refer to the tangible physical design of an information
system. To use an analogy, a personal computer's physical design involves input via a keyboard,
processing within the CPU, and output via a monitor, printer, etc. It would not concern the actual
layout of the tangible hardware, which for a PC would be a monitor, CPU, motherboard, hard drive,
modems, video/graphics cards, USB slots, etc.
6.2 DATA FLOW DIAGRAM
A data-flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system. DFD’s can also be used for the visualization of data processing (structured
design).
On a DFD, data items flow from an external data source or an internal data store to an internal data
store or an external data sink, via an internal process.
A DFD provides no information about the timing or ordering of processes, or about whether
processes will operate in sequence or in parallel. It is therefore quite different from a flowchart,
which shows the flow of control through an algorithm, allowing a reader to determine what
operations will be performed, in what order, and under what circumstances, but not what kinds of
data will be input to and output from the system, nor where the data will come from and go to, nor
where the data will be stored (all of which are shown on a DFD).
It is common practice to draw a context-level data flow diagram first, which shows the interaction
between the system and external agents which act as data sources and data sinks. On the context
diagram (also known as the Level 0 DFD) the system's interactions with the outside world are
modelled purely in terms of data flows across the system boundary. The context diagram shows the
entire system as a single process, and gives no clues as to its internal organization.
This context-level DFD is next "exploded", to produce a Level 1 DFD that shows some of the detail
of the system being modeled. The Level 1 DFD shows how the system is divided into sub-systems
(processes), each of which deals with one or more of the data flows to or from an external agent, and
which together provide all of the functionality of the system as a whole. It also identifies internal
22
23. data stores that must be present in order for the system to do its job, and shows the flow of data
between the various parts of the system.
.
Data-flow diagrams (DFDs) are one of the three essential perspectives of the structured-systems
analysis and design method SSADM. The sponsor of a project and the end users will need to be
briefed and consulted throughout all stages of a system's evolution. With a data-flow diagram, users
are able to visualize how the system will operate, what the system will accomplish, and how the
system will be implemented. The old system's dataflow diagrams can be drawn up and compared
with the new system's data-flow diagrams to draw comparisons to implement a more efficient
system. Data-flow diagrams can be used to provide the end user with a physical idea of where the
data they input ultimately has an effect upon the structure of the whole system from order to dispatch
to report. How any system is developed can be determined through a data-flow diagram. In the
course of developing a set of levelled data-flow diagrams the analyst/designers is forced to address
how the system may be decomposed into component sub-systems, and to identify the transaction
data in the model. Data flow diagram ("bubble charts") are directed graphs in which the nodes
specify processing activities and the arcs specify data items transmitted between processing nodes.
23
24. 6.2.1 CONTEXT- LEVEL DATA FLOW DIAGRAM
Mall Automation
Search Information
View Information
Search for Disc
View disc
Book movie tickets
Registration
Login
Post Disc schemes
Update &maintain
details
Handle Tickets
ADMINISTRATOR
EditInformation
ViewRegd.Users
PostInformation
USER B. OWNER
24
27. 6.3 ALGORITHM
Algorithm 1: Admin
Step 1: START
Step 2: Login to admin
Step 3: Admin can check/edit/ delete profile of shopkeeper, restaurant and
Theatre owner.
Step 4: Can approve or reject shopkeeper.
Step 5: Can edit/change the password and profile.
Step 6: Stop.
Algorithm 2: User
Step 1: START
Step 2: If already registered
Step 3: Then LOGIN.
Step 4: If email ID or password is correct then goto HOME PAGE.
Step 5: If user category is shopkeeper/ theatre/restaurant owner then can
Check own profile and can edit/change password.
Step 6: Else if not registered then go to registration form.
Step 7: If user category is user then go to step 3.
Step 8: Else wait for approval of admin.
Step 9: If admin accepts it then go to step 3. Else go to registration form.
Step 10: STOP.
Algorithm 3: Shopping
Step 1: START
Step 2: If LOGIN.
Step 3: Then check if it is login as a user/theatre/restaurant owner.
Step 4: Then he /she can visit/buy/search products by discount/price limit or
By Category.
Step 5: Else if it is LOGIN as admin then he/she can visit/buy/search
products or Can also edit/read products at any shopkeeper end.
Step 6: Else if it is LOGIN as shopkeeper then he can check/edit or delete
Own Products or can upload new products.
Step7: If visitor is not LOGIN then he can only visit/search products by
Category/price limit
Step 8: To buy the products go to step 2.
Step 9: STOP.
Algorithm 4: Theatre
Step 1: START
Step 2: If LOGIN then if login as user/shopkeeper/theatre owner.
Step 3: Then he can check current upcoming movie also can book tickets in
Advance.
Else if it is admin/theater owner then he can change upcoming
Current movie and also can change show timings.
Step 4: If not LOGIN then he can check upcoming/current movie in theatre.
Step 5: To book the tickets first LOGIN.
27
28. Step 6: STOP.
Algorithm 5: Restaurant
Step 1: START
Step 2: If LOGIN then if login as user/shopkeeper/restaurant owner.
Step 3: Then he can check/order dishes and also book tables in
Advance.
Else if it is admin/restaurant owner then he can check booking
Of the tables or delete/edit dishes.
Step 4: If not LOGIN then can check dishes in the restaurant.
Step 5: To buy dishes or book table go to LOGIN.
Step 6: STOP.
7.4 FLOWCHART
28
29. 29
START
If visitor
Login
If
user/a
dmin
Shopping Theatre Restaurant
C D E
If already
registered
Registration
form
Login
If user
category is
user
If email-id
and
password
are correct
Home page
If
user/shopkeep
er/restaurant,
theatre owner
Can check own profile,
can edit, change
password
Admin
dmin
Can check/edit/delete the proflile of
shopkeeper/user/theatre,restaurant
owner with password.
Can approve new
shopkeeper or can reject.
Can view/edit on profile
and change password.
STOP
A
Shopping
If
login
Can visit product, search
product by category
/price limit. if
login=user/re
staurant,thea
tre owner
To buy
Login=adm
in/shopkee
per
Can visit/buy/ search
product by discount/price
limit or by category.
Shopkeeper can check
edit or delete own
products can upload
new products.
Can visit/buy/search
product. Can edit/delete
product of any
shopkeeper.
C
A
31. `
Logi
n
Theatre
Can check upcoming/
current movie in theatre.
For book ticket.
Login=user/sh
opkeeper/resta
urant owner
Can check current/upcoming
movie can book ticket in
advance.
A
31
D
Can change upcoming/ current
movie, can change theatre
show timing.
32. LOGI
N
Can check dishes in
the restaurant.
Login= user
/shopkeeper
, theatre
owner.
To buy dishes or
book table.
A
Can check/delete
dishes in restaurant.
Can edit dishes.
Can check/order
dishes in restaurant.
Can book table
in advance.
32
E
Restaurant
62. TESTING
MEANING OF TESTING
Testing is an investigation conducted to provide stakeholders with information about the quality of
the product or service under test. Software testing also provides an objective, independent view of
the software to allow the business to appreciate and understand the risks at implementation of the
software. Test techniques include, but are not limited to, the process of executing a program or
application with the intent of finding software bugs.
Software testing can also be stated as the process of validating and verifying that a software
program/application/product:
• Meets the business and technical requirements that guided its design and development;
• Works as expected; and
• Can be implemented with the same characteristics.
Software testing, depending on the testing method employed, can be implemented at any time in the
development process. However, most of the test effort occurs after the requirements have been
defined and the coding process has been completed. As such, the methodology of the test is
governed by the software development methodology adopted.
Different software development models will focus the test effort at different points in the
development process. Newer development models, such as Agile, often employ test driven
development and place an increased portion of the testing in the hands of the developer, before it
reaches a formal team of testers. In a more traditional model, most of the test execution occurs after
the requirements have been defined and the coding process has been completed.
A primary purpose for testing is to detect software failures so that defects may be uncovered and
corrected. This is a non-trivial pursuit. Testing cannot establish that a product functions properly
under all conditions but can only establish that it does not function properly under specific
conditions. The scope of software testing often includes examination of code as well as execution of
that code in various environments and conditions as well as examining the aspects of code: does it
do what it is supposed to do and do what it needs to do. In the current culture of software
development, a testing organization may be separate from the development team. There are various
roles for testing team members. Information derived from software testing may be used to correct the
process by which software is developed.
62
63. Although variations exist between organizations, there is a typical cycle for testing. The sample
below is common among organizations employing the Waterfall development model.
• Requirements analysis: Testing should begin in the requirements phase of the software
development life cycle. During the design phase, testers work with developers in determining
what aspects of a design are testable and with what parameters those tests work.
• Test planning: Test strategy, test plan, test bed creation. Since many activities will be carried
out during testing, a plan is needed.
• Test development: Test procedures, test scenarios, test cases, test datasets, test scripts to use
in testing software.
• Test execution: Testers execute the software based on the plans and test documents then
report any errors found to the development team.
• Test reporting: Once testing is completed, testers generate metrics and make final reports on
their test effort and whether or not the software tested is ready for release.
• Test result analysis: Or Defect Analysis, is done by the development team usually along with
the client, in order to decide what defects should be treated, fixed, rejected (i.e. found
software working properly) or deferred to be dealt with later.
• Defect Retesting: Once a defect has been dealt with by the development team, it is retested
by the testing team. AKA Resolution testing.
• Regression testing: It is common to have a small test program built of a subset of tests, for
each integration of new, modified, or fixed software, in order to ensure that the latest delivery
has not ruined anything, and that the software product as a whole is still working correctly.
• Test Closure: Once the test meets the exit criteria, the activities such as capturing the key
outputs, lessons learned, results, logs, documents related to the project are archived and used
as a reference for future projects.
8.4.2 TEST CASES OF THE PROJECT
63
64. S.No. Test Cases Expected Value Actual Value
1. If incorrect user name and
password are entered
Error message should
be displayed
Displayed
2. If user Login Then logout is to be
displayed
Displayed
3. On selected menu item The item should be
highlighted
The item
highlights
4. If state, city, country not
selected
Error message should
be displayed
It displayed
5. Email-id should be in proper
format
It should be in proper
format
It is in proper
format
6. On view of site by visitor All the information
get displayed
It displayed
7. When user login Then he/she is able to
view his /her profile
only not admin’s
profile.
View hi/her
profile but cant
view admin
profile.
8. On submit button List of the user details
get submitted in
database
Get stored in
database
9. If user wants to get his table
reserved
Possible only if it has
login id and password
displayed
10. Admin can view all details of
restaurant/ theatre owner,
Full details is shown displayed
11. A simple
user/shopkeeper/theatre,returant
owner can search the products
search is available Displays all
items.
12. A user can also change
password
Password can be
changed
changed
64
65. 9. IMPLEMENTATION
A crucial phase in the system life cycle is the successful implementation of the new system
design. Implementation includes all those activities that take place to convert from the old system to
the new one. The new system may be completely new, replacing an existing manual system or it
may be major modification to an existing system. There are no clear separating lines between these
phases and in many cases, one phase will start before the previous one is completed. But the logical
order is followed. In either case, proper implementation becomes necessary so that a reliable system
based on the requirements of the organization can be provided.
Successful implementation may not guarantee improvement in the organization using the
new system, but improper installation will prevent it. It has been observed that even the best system
cannot show good result if the analysts managing the implementation do not attend every important
details. This is an area where the system analysts need to work with utmost care.
This unit discusses the aspects of implementation:
• Training personnel
• Post-implementation review
Training of Personnel Involved With System:
Even well designed system can succeed or fail because of the way they are operated and
used. Therefore, the quality of training received by the personnel involved with the system in various
capacities helps or hinders and even prevents the successful implementation of application. Those
who are directly related with the system development work must know in details what their roles
will be, how they can make efficient use of the system and what the system will not do for them.
Both systems operators and users need training. In most of the cases, user training deals with the
operation of the system itself, with proper attention given to data handling techniques. It is
imperative that users be properly trained in methods of inserting, deleting or modifying of records.
No training is complete without familiarizing users with simple system maintenance activities.
65
66. Weakness in any respect of training may lead to awkward situations that create user frustration and
errors.
Post Implementation Review:
After the system is implemented and conversion is complete, a review should be conducted
to determine whether the system is meeting expectations and where improvements are needed. A
post implementation review measures the systems performance against pre-defined requirements. It
determines how well the system continues to meet performance specifications. It also provides
information to determine whether major re-design or modification is required.
A post implementation review is an evaluation of a system in terms of the extent to which the
system accomplishes stated objectives and actual project costs exceed initial estimates. It is usually a
review of major problems that need converting and those that surfaced during the implementation
phase.
The post implementation study begins with the review team, which gathers and reviews
requests for evaluation. Unexpected change in the system that affects the user or system performance
is a primary Factor that prompts system review. Once request is filed, the user is asked how well the
system is functioning to specification or how well the measured benefits have been realized.
Suggestions regarding changes and improvements are also asked for.
.
66
67. 10.LIMITATIONS
LIMITATIONS OF THE SYSTEM
10.1.1 Admin cannot send Mail: - We do not have the facility to send E-mail to
shopkeeper who wants to get registered.
10.1.2 Forgot Password: - If user forgets the password, then there is no facility to
remind him. If at first time some password is entered by user then he or she has to
remember it forever.
10.1.3 Captcha code: - On registration no captcha code is given.There should
be prorer security given to user.
10.1.4 No date wise Registration: - Administration cannot view stored record date
wise. If he wants to see the date of registration of any thing date wise then this
facility is not given to him.
10.1.5 User cannot post reviews: - User cannot add comments to it.
67
68. CONCLUSION
Our system will deal with all the aspects of CRM (Customer Relationship Management) starting
from Customer’s Problem entry, processing, complaint resolution, tracking of complaints as
well as report generation.
On the basis of the work done in dissertation entitled “Customer call tracking system”,
Conclusions emerges:
1. This project has achieved the objective of replacing/augmenting the conventional system of
arranging manpower as could be conducted by a typical Tracking System Deptt.
2. The development of this package has been achieved by using VB.NET, which is very
conductive to develop the package with regard to time and specific need to the user.
3. This package is highly user friendly, required an optimal minimal input from user while
providing highly relevant and focused outputs.
4. Fully automated, avoiding human intervention. Hence it provides a very rapid cost effective
alternative to the conventional manual operation/procedures; the visual outputs are more
reliable than the audio forms of manual communication.
68
69. References
BOOKS REFFERED
1 BEGINNING ASP.NET WITH C# (WROX PUBLICATION)
2 ASP.NET.3.5.Unleashed –Sams
3 Mastering ASP.NET with C#
4 Wrox.Professional.ASP.NET.3.5.In.C.Sharp
WEBSITES REFFERED
1 . www.westfield.com
2 . www.shoppingmall.com
69