PDF- -Software Requirements Specification (SRS) Book E-Commerce - Cab Booking System


Guru Gobind Singh Indraprastha University

Software Requirement Specification

For Cab Booking System

Submitted To: Mrs

Nishi Sharma (NIEC)

Submitted by:

Gaurav Deep Mahesh


A study or a project of this volume can never be an outcome or a single person

We our indebted to our mentor Mrs

Nishi Sharma for being the epitome of guidance during the entire project

We are also thankful to our parents for their Encouragement

Without their help this project would not have seen the light of day

We are happy to present a vote of thanks to them for their sincere advice and co-operation that they have lent us unconditionally

CAB BOOKING SYSTEM Problem Statement:Cab booking service is a major transport service provided by the various transport operators in a particular city

Mostly peoples use cab service for their daily transportations need

The company must be a registered and fulfils all the requirements and security standards set by the transport department

Taxi Booking Software is a web based platform that allows your customers to book their taxi's and executive taxi's (such as Limousines) all online from the comfort of their own home or office

The platform should offer an administration interface where the taxi company can manage the content,

and access all bookings and customer information

Usually the platform will include all the required functionality such as hosting,

a domain name (the web address) and,

! In a nutshell your Taxi Booking Software should be able to: o Provide the functionality to make your own bookings o Give your customers the facility to make payments and deposits online with their credit / debit card

o Generate Invoices o Update your web site without the need to get a web designer involved

o Provide the customer with taxi availability o Track your customers

o Engage your customers through interaction such as feedback forms More and more Taxi companies are looking for integrated taxi booking systems as it makes life much easier for a) the customer

From the historic data the taxi firm will be able to look at booking trends of set periods of time,

and future bookings will allow them to budget their staff and taxi routes accordingly

Taxi Booking Software can be built on top of a great looking web site and third party payment providers can be used to provide secure transactions

One factor that may be a stumbling block for Taxi firms is the cost of the taxi booking software

Some vendors offer a shared pricing model that allows certain taxi firms to share the cost of the system

This type of model is known as multi-vendor

As the taxi booking systems are web based this doesn't cause any issues as the software is located on a central web server and the web site front end can be branded in any way required by the taxi company

In today's technological world can your taxi company afford to be without booking software

                

The fare must be economical so that it must be in reach/budget of every person

Cab must be reach on time on the defined destination

There must be a large fleet of cabs (AC/Non AC)

Provide the functionality to make your own bookings Update your web site without the need to get a web designer involved

Provide the customer with taxi availability

Track your customers

Engage your customers through interaction such as feedback forms Easy payment facility must be provided in cab i

Payment bill must be provided by cab driver

Driver’s identification data must be given i

id & photograph at the time of booking of cab

Estimated time for a particular journey must be provided

Details of the route must be provided to the customer

Customers can my take the cab by his/her own route

Customer satisfaction is necessary

The user interface must be friendly so that the user can easily book a cab in few minutes by doing few clicks

Payment modes can be also of prepaid or post-paid

If the payment mode is prepaid then the customer have to provide its full name,

In both prepaid and post-paid customer’s email id must be provided

At the time of booking the web page must have the interface for the starting point,

Night charges are also added to the total fare on the basis of per kilometre

In the end the report must be generated which shows the customer name,

the invoice must be generated If the payment is made at the time of booking i

prepaid then it must be shown in the report

The information must be provided to the customer on its email id and to driver on its job sheet

Use – Case Diagram :-









Use Case Template:1

Source / Destination

Flow of Events :1

User books a cab by providing the details of source and destination

Booking clerk check the database

On successful traveller makes the booking of the cab

Date / Time :- Use case specification 2

Flow of events :2

User checks the availability on website

On successful completion of transaction user makes booking

Questionnaire :The aim of the questionnaire is to collect information on the methods and practices for software development

Your input is extremely important to identify gaps and desired data that will help in driving future tools and methods that may better support your activity

An online version of the questionnaire is also published on the web portal

The information collected is completely confidential

We shall never share or release your private information to an unaffiliated third party

Please specify the type of your institution/company: � Research � Industry � Higher Education Other_____________________________________

Please classify the application area of your institution/company: � Education � Consumer appliances production � Museum � Mechanical Engineering � Electronic engineering � Cultural Heritage � CAD/CAE,

Product Modelling � Gas,

Oil � Transportation,

Traffic � Geo-Informatics � Simulation � IT Service Provider � IT Software Developer � Web development � Game development � Health (Medical),

Bioinformatics � Management 3

Please specify the user category (or categories) you belong to: � Professional user � Professional IT developer � Scientist � Creator of digital 3D content � End user � Publisher/dealer of 3D repositories � Other _________________________________________________ 4

Institution/Company size: � 0–10 � 11 – 20 � 21 – 50 � 50

GENERAL:             

Is the software is web based or standalone software

Why do we require the software

What is the working of the software

How it is different from manual system

Is the Short Messaging Services(SMS) is provided

How it is useful

What interface we are using at frontend and backend

Interface is of button based or menu driven

What is the compatibility and performance of software

How many modules user want

What are the modules where we want security

What are the number of users

Where can I lodge complaint against any type of grievances in the services of cabs,

on this web site and how do I report the problems on this web site and give suggestions

NEED SPECIFIC: How do I use "cab services"

? Rules / Passenger Services Journey planning Knowing source/destination codes PLEASE NOTE: The site maintenance activities takes place from 0200hrs to 00350 hrs (Indian Standard Time) daily

During this period information may not be available

note that since the system is under maintenance activities status changes might take a larger time place to book a cab during this period

INTERNET BOOKING FACILITY THROUGH CREDIT CARDS: Internet booking facility is available on the web site http://www

wherein you can get the cab booked

For more on bookings click here Internet bookings

Software Requirement Specification :FULL TAXI DISPATCH SYSTEM web-based

Will include:- Geolocalisation ( Client mode on Dreevo ,



) Geolocalization services are provided directly by the satellite to the employees of the company which are provided with the GPS enabled cell phones so that they can track,

heck and automize the services of the cabs

com are available on your mobile phone through SMS facility

For more information on the mobile service providers and the key words to be used on the mobile,

SMS help

Please note that we are giving the backend service only for the SMS queries

For more information and help on key words and SMS facility,

kindly contact the mobile service provider according to the table



The database is maintained with the customer id,

address and telephone numbers of all the customers

When a cab is found then operator must assign its status to busy,

this is done through address search

that the customer can make its own booking on the site,

and can be seen by the operator and the screen with automatic dispatch to available cars and with alert ( SMS,

with CHAT and IM in direct with the drivers on the road ( through the client : Dreevo,



and cancellation on various types of booking namely

The different types of readers are: (a)

Customers (b)

Developers (c)

Management people Specifically,

Passengers 1

Acronyms,and Abbreviation: Following abbreviation has been used throughout this document: CBS:Cab booking system

PDA: Personal Digital Assistant IVRS:Voice Response System  Cab Details  Booking Form  Billing  Cancellation 1

Improved and Optimized service 1

more easily managed segments or phases

Segmenting projects allows managers to verify the successful completion of project phases before allocating resources to subsequent phases

Software development projects typically include initiation,


the phases may be divided differently depending on the organization involved

For example,

initial project activities might be designated as request,

End users of the system under development should be involved in reviewing the output of each phase to ensure the system is being built to deliver the needed functionality

PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE Initiation Phase The Initiation Phase begins when a business sponsor identifies a need or an opportunity

The purpose of the Initiation Phase is to Identify and validate an opportunity to improve business accomplishments of the organization or a deficiency related to a business need

Identify significant assumptions and conscabts on solutions to that need

Recommend the exploration of alternative concepts and methods to satisfy the need including questioning the need for technology,

will a change in the business process offer a solution

? Assure executive business and executive technical sponsorship

The Sponsor designates a Project Manager and the business need is documented in a Concept Proposal

The Concept Proposal includes information about the business process and the relationship to the Agency/Organization Infrastructure and the Strategic Plan

A successful Concept Proposal results in a Project Management Charter which outlines the authority of the project manager to begin the project

Careful oversight

is required to ensure projects support strategic business objectives and resources are effectively implemented into an organization's enterprise architecture

The initiation phase begins when an opportunity to add,

or correct a system is identified and formally requested through the presentation of a business case

The business case should,

and explain how the proposed system supports one of the organizations business strategies

The business case should also identify alternative solutions and detail as many informational,

and network requirements as possible

System Concept Development Phase The System Concept Development Phase begins after a business need or opportunity is validated by the Agency/Organization Program Leadership and the Agency/Organization CIO

The purpose of the System Concept Development Phase is to: Determine the feasibility and appropriateness of the alternatives

Identify system interfaces

Identify basic functional and data requirements to satisfy the business need

Establish system boundaries identify goals,

Evaluate costs and benefits of alternative approaches to satisfy the basic functional requirements

Assess project risks

Identify and initiate risk mitigation actions,

and Develop high-level technical architecture,

This phase explores potential technical solutions within the context of the business need

It may include several trade-off decisions such as the decision to use COTS software products as opposed to developing custom software or reusing software components,

or the decision to use an incremental delivery versus a complete,

Construction of executable prototypes is encouraged to evaluate technology to support the business process

The System Boundary Document serves as an important reference document to support the Information Technology Project Request (I TPR)

The I TPR must be approved by the State CIO before the project can move forward

PICTORIAL REPRESENTATION OF SDLC:Requirements Analysis Phase: This phase formally defines the detailed functional user requirements using high-level requirements identified in the Initiation,

System Concept,

It also delineates the requirements in terms of data,

and maintainability requirements for the system

The requirements are defined in this phase to a level of detail sufficient for systems design to proceed

They need to be measurable,

and relate to the business need or opportunity identified in the Initiation Phase

The requirements that will be used to determine acceptance of the system are captured in the Test and Evaluation Master Plan

The purposes of this phase are to: Further define and refine the functional and data requirements and document them in the Requirements Document,

Complete business process reengineering of the functions to be supported (i

verify what information drives the business process,

what information is generated,

where does the information go,

Develop detailed data and process models (system inputs,

Develop the test and evaluation requirements that will be used to determine acceptable system performance

Design Phase: The design phase involves converting the informational,

and network requirements identified during the initiation and planning phases into unified design specifications that developers use to script programs during the development phase

Program designs are constructed in various

Using a top-down approach,

designers first identify and link major program components and interfaces,

then expand design layouts as they identify and link smaller subsystems and connections

Using a bottom-up approach,

designers first identify and link minor program components and interfaces,

then expand design layouts as they identify and link larger systems and connections

Contemporary design techniques often use prototyping tools that build mock-up designs of items such as application screens,

End users,

and network administrators should review and refine the prototyped designs in an iterative process until they agree on an acceptable design

and quality assurance personnel should be involved in the review and approval process

During this phase,

the system is designed to satisfy the functional requirements identified in the previous phase

Since problems in the design phase could be very expensive to solve in the later stage of the software development,

a variety of elements are considered in the design to mitigate risk

These include: Identifying potential risks and defining mitigating design features

Performing a security risk assessment

Developing a conversion plan to migrate current data to the new system

Determining the operating environment

Defining major subsystems and their inputs and outputs

Allocating processes to resources

Preparing detailed logic specifications for each software module

The result is a draft System Design Document which captures the preliminary design for the system

Everything requiring user input or approval is documented and reviewed by the user

Once these documents have been approved by the Agency CIO and Business Sponsor,

the final System Design Document is created to serve as the Critical/Detailed Design for the system

This document receives a rigorous review by Agency technical and functional representatives to ensure that it satisfies the business requirements

Concurrent with the development of the system design,

the Agency Project Manager begins development of the Implementation Plan,

Operations and Maintenance Manual,

Development Phase: The development phase involves converting design specifications into executable programs

Effective development standards include

requirements that programmers and other project participants discuss design specifications before programming begins

The procedures help ensure programmers clearly understand program designs and functional requirements

Programmers use various techniques to develop computer programs

The large transaction-oriented programs associated with financial institutions have traditionally been developed using procedural programming techniques

Procedural programming involves the line-byline scripting of logical instructions that are combined to form a program

Effective completion of the previous stages is a key factor in the success of the Development phase

Integration and Test Phase: Subsystem integration,

and user acceptance testing is conducted during the integration and test phase

The user,

with those responsible for quality assurance,

validates that the functional requirements,

as defined in the functional requirements document,

are satisfied by the developed or modified system

Security staff assesses the system security and issue a security certification and accreditation prior to installation/implementation

Multiple levels of testing are performed,

including: Testing at the development facility by the contractor and possibly supported by end users

Testing as a deployed system with end users working together with contract personnel

Operational testing by the end user alone performing all functions

Requirements are traced throughout testing,

a final Independent Verification & Validation evaluation is performed and all documentation is reviewed and accepted prior to acceptance of the system

Implementation Phase: This phase is initiated after the system has been tested and accepted by the user

In this phase,

the system is installed to support the intended business functions

System performance is compared to performance objectives established during the planning phase

Implementation includes user notification,

installation of software onto production computers,

and integration of the system into daily work processes

This phase continues

until the system is operating in production in accordance with the defined user requirements

Operations and Maintenance Phase: The system operation is ongoing

The system is monitored for continued performance in accordance with user requirements and needed system modifications are incorporated

Operations continue as long as the system can be effectively adapted to respond to the organizations needs

When modifications or changes are identified,

the system may reenter the planning phase

The purpose of this phase is to: Operate,

Certify that the system can process sensitive information

Conduct periodic assessments of the system to ensure the functional requirements continue to be satisfied

Determine when the system needs to be modernized,

Overall description: It enables us to maintain the cab details like this

and booking billing and canceling the cab

2Hardware Interface:

System requirements Minimum system requirements for Cab Management:

Processor: Intel Core 2Duo or AMD equivalent,

2Gz or better RAM: 2GB HDD: 160 GB,

or Windows Remote Desktop Connectivity

Other suggested components

Minimum system requirements for CMS Mobile:

Operating system Windows Mobile 6 Touchscreen GPS Module GPRS Data Plan

Communication Interfaces The website www

com offeres CBS enquiries on the internet availability,

Mobile telephone based SMS inquiry service

Setting up of voice response system

4Operating Environment: The OS types are:  Windows NT  Windows XP  Windows Vista  Windows 7 2

 One form for single booking

 Booking is done through pre defined logic

2Product Functions: It tells the short note about the product

1Cab Details: Customers may view the cab timing at a date their name and their type of booking

2Booking: After checking the number of cab available the customers books a cab or number of cabs according to their requiremnets

3Billing: After reserving the required cab,

the customer pays the amount in advance (optional)

4Cancelation: If the customer want to cancel the cab then 10% of the amount per person is deducted if the booking is cancelled before 30 mins of the service time

Conscabts  Less than 1 sec for local transactions

 3 sec for network transaction

SOFTWARE CONSCABTS: Designing->Rational Rose 3



Booking Terminals Interactive voice Response System

PERFORMANCE REQUIREMENTS: It is available during all 24 hours

Offered through Air conditioned or non Air conditioned Cabs

About 1600 cabs run daily

Types of concerns and complexities: Special 10 % discount is given to corporate customers for their advance monthly bookings

Document Approval The bill passed on any proposal related to cab management needs approval of the top level management


user interface design and implementation are complete

The system now is tested for its functionality,

In order to test the system,

a wide variety of tests are conducted to make sure that the system matches the entire identified user requirements and conscabts

This chapter focuses on testing the developed systems using different test strategies in order to verify its correctness and user acceptance

Testing is a process of executing a program with the intent of finding an error

A good test case is one that has a high probability of finding an as yet undiscovered error

A successful test is one that uncovers an as yet undiscovered error

The development of software systems involves a series of production activities where opportunities for injection of human fallibility are enormous

Errors may begin to occur at the very inception of the process where the objectives may be enormously or imperfectly specified,

as well as in later design and development stages

Because of human inability to perform and communicate with perfection,

software development is accompanied by a quality assurance activity

Software testing is a critical element of software quality assurance and represents the ultimate review of specification,

And it needs to be done in almost every phase of product development life cycle not just before a product is handed to a customer

The following are some attributes of a good test: 

A good test has a high probability of finding an error

To achieve this goal the tester must understand the software and attempt to develop a mental picture of how the software may fail

Ideally the classes of failure are probed

A good test is not redundant: testing time and resources are limited

There is no point in conducting the test that has the same purpose as another test

Every test should have a different purpose

A good test should be best of breed

In a group of tests that have a similar intent time and resource limitations may militate for the execution of only a subset of these tests

In such cases the tester that has the highest likelihood of uncovering a whole class of errors should be used

A good test should be neither too simple nor too complex: although it is sometimes possible to combine a series of tests into one test case,

the possible side effects associated with this approach may mask errors

In general each test should be executed separately

sometimes called glass box testing is a test case design method that uses the control structure of the procedural design to derive test cases

Using white box testing methods,

the software engineer can derive test cases that :    

Guarantee that all independent paths within a module have been exercised at least once

Exercise all logical decisions on their true and false sides

Execute all loops at their boundaries and within their operational bounds

Exercise internal data structure to assure their validity

White box testing was performed at all levels of development of i-Admit

The coding team took all care to test the code and guarantee that it meets all the specifications as well as logically correct

All loops were tested and all internal data structures evaluated and verified

It focuses on the functional requirements of the software

That is black box testing enables the software engineer to derive sets of input conditions that will fully exercise all functional requirements for a program

Black box testing is not an alternative to white box techniques

Rather it is a complementary approach that is likely to uncover a different class of errors than white box methods

Black box testing attempts to find errors in their following categories  

Incorrect or missing functions Interface errors

Errors in data structures or external data base access Performance errors Initialization and termination errors

Unlike white box testing,

which is performed early in the testing process,

black box testing is to be applied during later stages of testing

Black box testing was performed with the application code of the software being developed to verify that it is functionally correct and gives appropriate output at different situations of inputs

It was also verified that the software takes a good care of exceptional conditions and errors are handled well and that the software does not crash

A strategy for software testing integrates software test case design methods into a well-planned series of steps that result in the successful construction of software

In many ways,

testing is an individualistic process,

and the number of different types of tests varies as much as the different development approaches

Using the procedural design description as a guide,

important control paths are tested to uncover errors within the boundary of the module

The module interface is tested to ensure that information properly flows into and out of the program unit under test

The local data structure is examined to ensure that data stored temporarily maintains its integrity during all steps in algorithmic execution

Boundary conditions are tested to ensure that the module operates properly at boundaries established to limit or restrict processing

All independent paths (bases paths) through the control structure are exercised to ensure that all elements in a module have been executed at least once

And finally all error-handling paths are tested

Application interface of our system was unit tested at all levels of implementation,

right from start of code writing,

to integrating the code with other modules

Every module was tested fully to check its syntax and logical correctness

Error handling was implemented into relevant modules so that the code doesn’t crash on errors

while conducting test to uncover errors associated with interfacing,

the objective is to take unit tested modules and build a program structure that has been dictated by design

User interface of i-Admit was developed in modules

All of them were joined together to make the complete running application

While integrating these modules,

integration testing was performed on them to verify that they meet all interfacing requirements and that they pass relevant information among themselves

In the end the complete program structure was tested to ensure interoperability of all the modules

Validation can be defined in many ways,

but a simple definition is that validation succeeds when software functions in a manner that can be reasonably expected by the customer

Software validation is achieved through a series of Black Box tests that demonstrate conformity with requirements

When custom software is built for one customer a series of acceptance tests are conducted to enable the customer to validate all requirements

A customer conducts the alpha test at the developer site

The software is used in a natural setting with the developer “looking over the shoulder” of the user and recording errors and usage problem

Alpha tests are conducted in a controlled environment

Alpha tests were performed at our development site with the help of our friends,

who were called and asked to run the program in the manner they like,

without our guidance and errors and usage problems were noted and code was updated to remove all of them

Unlike alpha testing the developer is generally not present

Therefore the beta test is a live application of the software in an environment that cannot be controlled by the developer

The customer records all problems that are encountered during beta testing and reports these to the developer at regular intervals

As a result of problems reported during beta test the software developer makes modification and then prepares for the release of software product to the entire customer base

Beta testing of our system is not performed as the product is not yet fully developed and has not been installed at the user site as it still is in the development phase

Beta testing will be performed when the software is deployed at the user’s site

information) and a series of system,

integration and validation tests are conducted

It is actually a series of different tests whose primary purpose is to fully exercise the computer-based system

Although each test has a different purpose all work to verify that all system elements have been properly integrated and perform allocated functions

System testing of this system was performed at the development lab of this system by integrating the functional systems to imitate the actual work environment

Since no special hardware was needed for this purpose,

the testing proceeded and succeeded with no errors

In some cases a system must be fault tolerant that is processing faults must not cause overall system function to cease

Recovery testing is a system test that forces the software to fail in a variety of ways and verifies that recovery is properly performed

If recovery is automatic,

and restart are each evaluated for correctness

If recovery requires human intervention the meantime to repair is evaluated to determine whether it is within acceptable limits

Security is provided for each user by giving them login name and password

Security testing was done,

as any other anonymous user can’t log in with a user password if the user is already logged in

Performance Testing is designed to test run time performance of software within the context of an integrated system

Performance Testing occurs throughout all steps in the testing process

Performance tests are often coupled with stress testing and often require both hardware and software instrumentation

That is it is often necessary to measure resource utilization in an exacting fashion

External instrumentation can monitor execution intervals,

and sample machines take on a regular basis

By instrumenting a system the tester can uncover situations that lead to degradation and possible system failure

Context Diagram

Reserve Cab

Customer Info Request to cancel/ Reserve a cab



Cab Status Cancel Booking Customer List Report

LEVEL 1 DFD Operator

Customer Payme nt

Cab Info

Cab Info

User Entry

Type of Payment

Customer Info

Cab Customer Choice Login


Customer Choice Cab

Driver Info

Driver Info

Guest user id

View Reports,Bills etc


Cab Menu



Cab Driver

Display Menu Enter Cab no &distance

Entered Enter Source & Destn Entered Enter Dept & Arr Time

Submit Details


Get Details Verify detail

Add/Delete/Modify Cab

Error / success Message

Add/Delete/Modify Update Cab Detail


Reservation Reservation Menu



Display Menu Enter details,name,contactno,gender etc

Submit Details


Verify Data

Success/Error Message Display

Reserve Cab Do Payment Get Payment Display Cab & Reservation

Update Reservation Info


Cancellation Cancellation Menu



Display Menu Enter details,name,contactno,gender etc

Submit Details


Verify Data

Success/Error Message Display

Cancel Cab Booking Refund All Charges Get Payment Display Cancellation no

Update Info



Check for Reservation

CAB Dept

If available

Do / Check Minimum level

Do/Send Request

If not available Reserve Cab Cancelled

Do/Maintain Database

Book CAB Do Payments



Verification Selection

Delete Customer/Cab Data

If Not Exist Enter/Verify Details

Do/Select operation

Add customer/CAB data Conformation

Verification Enter/VerifyDetails

Do/conform ADD


Update Do/Update Database

Do/Update Database



If correct user id,passwd,guest id

Do/login checker

Transfer TrTTRA Do/initiate welcome screen

Not Correct


Welcome Screen


Check for Booked Cab


If booked do/u want to cancel



If not booked


Delete Booking Do/maintain database


Generate Report

Cab_no Fare Source : Destination Deptr_time Arri_time Class_type

Transport Dept


Show_cabdetail() Add_cab()


Service prov_name Service_city Service_state Service_country

Show Driver_detail()


Show_service_detail( )

Login 1 2 Customer Cust_name Cust_age Cust_gender Cust_phn _no Cust_id Cab_no Grp_discount

Ticket cancelled Login User_id Psswd Sign_in()








Generate report 1



1 PrintTkt

Report Genrate_Report()


Cancellation Cab_no Date_of_cancel Cancel_charge Show_details()



Activity Diagram


Cancel Booking

If not exist Verification

If exist

Display Details

Cancel Booking

Deduct cancellation charges

Refund charges

Activity diagram

Enter id & psswd,

guest login If not exist Verification

If exist

Successfully Login

Activity diagram


Enter Details

Not exist Verification

If exist

ADD Customer

Delete Customer

Display Details

Modify customer

Activity diagram


Enter Details

Not exist Verification

If exist


Delete Cab

Display Details

Modify Cab

Activity Diagram


Generate report

Print Ticket

Activity Diagram


Generate report

Print Ticket

ADVANTAGES OF CAB BOOKING SYSTEM Now one can easily plan the journey comfortably as the process is efficient and fast with being easy to access

Bookings can be made through the cab booking site or by the phone call

This being a big step in terms of improvement in the cab system it is widely accepted across the country

which can be issued from any station to any station

can be made effective immediately with the appropriate contingency handling

This feature facilitates defining different advance booking periods for different cabs

and presentation of the summarised data in the form of visual analytics from the operational system's information store

The data aggregation is done incrementally,

and standard cab business rules are incorporated in the form of data instead of being part of the logic

Conclusions Information Technology plays a vital role not only in a particular field,

it provides various kinds of solutions and services to the various problems prevailing in many fields

Cabs exploits information technology at the maximum extent

It uses the information technology in an efficient way for providing better passenger services

The online booking system helps to solve the every day problems of the world biggest Indian

CABAHUG_laborCases: Contract with fixed period/ fixed term Employment

securities and exchange commission - San Miguel Food and

PDF ERC Case No 2011 128RC Power Sector Assets and Liabilities psalm gov ph Application 20dtd 2014 20Sept 202011 20 20ERC 20Case 20No 202011 PDF Untitled Philippine Ports Authority

Cabala 2014 - Chesed a Sephira de Júpiter

Rosicrucian Digest Vol 92 No 1 2014 Martinism - Rackcdncom

PDF Kabbalah, Symbolism and Metaphysics in Russian Dialnet dialnet unirioja es descarga articulo 5156952 pdf PDF Approaching the Kabbalah of Maat Hermetic Kabbalah digital brilliance contributed Karr Maat AKM pdf PDF KABBALAH You are walking

Cabala Curso Amorc Ver2

APOCALIPSIS DE JUAN C - libroesotericocom

libroesoterico biblioteca RosaCruz AMORC Cabala sin LA CABALA NUMERO 1 F INTRODUCCION PAGINA 1 Si a usted le gustan lo misterioso y las cosas sobrenaturales que la mente humana ha podido desarrollar en un esfuerzo para aclarar los misterios de la vida, encontrará interesante y de

Cabala e Ghematria

NUMEROLOGIA BIBLICA - digilanderliberoit

libroesoterico biblioteca Cabala Gematria Gematria pdf personajes importantes de la historia de Israel e incluso especificando la dirección de los canales que unen a las diez sefirot) El Notaricón, por último, «lee entre líneas» reveladas las respuestas que el lenguaje divino mantiene ocultas para un lector no

Cabala Geburah - A Shepira de Marte - Regente de 2015

La legitimidad de la felicidad en la mística - McGill University

PDF El reino de los dioses De "Glosario Teosófico" oceanodeteosofia uploads EL REINO DE LOS DIOSES pdf PDF La legitimidad de la felicidad en la mística McGill Universitydigitool library mcgill ca thesisfile110408 pdf


The Study of Christian Cabala in English: Addenda - Hermetic

LA CÁBALA DE LA MERKAVÁ Una vía universal de Mística”, al cual se remite En mi segunda obra, “Senderos en el jardín de la conciencia Manual de traditions, now known as Kabbalah was the Sefer Yetzirah To this day, the sections

Cabala Mineralis Manuscript

arcana et curiosa - mazaher

bnam IMG pdf cabalamineralis2 pdf Cabala mineralis manuscript (Images are in High Resolution so you may zoom in for greater detail) magia metachemica uploads 1 0 6 2 10624795 Cabala mineralis manuscript The sprout of Mercury The water of life

Cabala Mistica

El proceso místico en Del templo de su cuerpo, poemario - SciELO

Cabala Mística Dion Fortune Instituto Cultural Quetzalcoatl samaelgnosis net 3 PRIMERA PARTE CAPITULO I EL YOGA DEL OCCIDENTE Son muy  Alan Richardson INICIACIÓN EN LA CABALA MÍSTICA Cuarta edición Ediciones Lidiun BUENOS AIRES Director

Cabala Pratica Charles Fielding

para pesquisar: use ctrl + f - Etec de Sapopemba

PDF Livro ABNC Final rev1 indd Academia BNC academiabnc br material curso n cabalistica basico 04 1 pdf PDF A MAGIA ENTRE OS CRISTÃOS NOVOS Nilton Bruno Feitosa snh2011 anpuh 1406694938

Home back Next