Friday, 26 December 2014

UI Developer Online Training

User Interface is the field of human-machine interaction. The goal of user interface design is to make the user’s interaction as simple and efficient. It reduces the gap between requirements and iterative implementation, produces structured systems and associated with code generation method. UI Developer online training will enhance the ability to create browser-based user interfaces and UI web solutions from the requirements stage to deployment onto the production web farm.
HTML & CSS
Topics-
Introduction to the WEB, Introduction to the HTML, HTML Editors, HTML Syntax, Understanding and using the HTML, Advanced Tags in HTML, HTML5 elements, HTML5 Semantics, HTML5 Syntax, HTML forms, HTML Graphics, HTML media, HTML API’s, HTML Examples, Introduction to the CSS, CSS Syntax, CSS Layout, CSS3 Syntax, CSS Work arounds
JavaScript
Topics-
Overview of Java Script, Building a Java Script Program, Reviewing HTML, Basic Syntax Used in Java Script Commands, Variables, Functions, Operators, String Processing, Objects, History Object, Date Object, Using Objects like Arrays, Events, Location Objects, Form Objects, HTTP Cookies, Math Object, Frames, Shopping Cart Application, Form Validation
To Learn More Follow Below link:

Oracle Apps Technical Online Training

Oracle Apps Technical is ERP package (Enterprise Resource Planning) designed on the basis of Generally Acceptable Accounting Principles [GAAP]. Oracle Applications comprise the application software or business software of the oracle corporation. Descriptive Flex Fields capture business information and add attribute columns. Qualifiers identify segments and in QA framework MDS defines the personalization reports.
Enterprise resource planning (ERP) is business process management software that allows an organization to use a system of integrated applications to manage the business and automate back office functions. ERP software integrates all facets of an operation, including product planning, development, manufacturing processes, sales and marketing.
1.    Complete visibility into all the important processes across various departments of an organization (especially for senior management personnel).
2.    Automatic and coherent work-flow from one department / function to another to ensure smooth transition/ completion of processes.
3.    A unified and single reporting system to analyze the statistics/ numbers/ status etc in real-time, across all the functions / departments.
4.    Since same software is used across all departments – this can avoid individual departments having to buy and maintain their own software systems.
5.    Certain ERP vendors can extend their ERP systems to provide Business Intelligence functionalities as well.
6.    Advanced e-commerce integration is possible with ERP systems that can handle web-based order tracking/ processing.
7.    There are various modules in an ERP system like Finance/ Accounts, Human Resource Management, Manufacturing, Marketing / Sales, Supply Chain / Warehouse Management, CRM, Project Management, etc.
8.    Since ERP is a modular software system, its possible to implement either a few modules (or) many modules based on the requirements of an organization. If more modules implemented, the integration between various departments might be better.
9.    ERP systems provide visibility and hence enable better/ faster collaboration across all the departments.
10.  It is possible to integrate other systems (like bar-code reader, for example) to the ERP system through an API (Application Programing Interface).
11.  ERP systems make it easier for order tracking, inventory tracking, revenue tracking, sales forecasting and related activities.
12.  ERP systems are a boon for managing globally dispersed enterprise companies.
1.    The cost of ERP Software, planning, customization, configuration, testing, implementation, etc is too high.
2.    ERP deployments take 1-3 years to get completed and fully functional.
3.    Too little customization may not integrate the ERP system with the business process & too much customization may slow down the project and make it difficult to upgrade.
4.    The cost savings/ payback may not be realized immediately after the ERP implementation & it is quite difficult to measure the same.
5.    The participation of users is very important for successful implementation of ERP projects – So, exhaustive user training and simple user interface might be critical. But ERP systems are generally difficult to use (and learn).
6.    There maybe additional indirect costs like new IT infrastructure, upgrading the WAN links, etc.
7.    Migration of existing data to the new ERP systems is always difficult to achieve as with integrating ERP systems with other stand alone software systems.
8.    ERP implementations are difficult to achieve in decentralized organizations with disparate business processes and systems.
9.    Once an ERP systems is implemented it becomes a single vendor lock-in for further upgrades, customizations etc. 
To Learn More Click on below link:

Wednesday, 24 December 2014

IOS Development Online Training

Introduction to IOS
iOS is the operating system that runs on iPad, iPhone, and iPod touch devices. The operating system manages the device hardware and provides the technologies required to implement native apps. The operating system also ships with various system apps, such as Phone, Mail, and Safari, that provide standard system services to the user.
The iOS Software Development Kit (SDK) contains the tools and interfaces needed to develop, install, run, and test native apps that appear on an iOS device’s Home screen. Native apps are built using the iOS system frameworks and Objective-C language and run directly on iOS. Unlike web apps, native apps are installed physically on a device and are therefore always available to the user, even when the device is in Airplane mode. They reside next to other system apps, and both the app and any user data is synced to the user’s computer through iTunes.
At the highest level, iOS acts as an intermediary between the underlying hardware and the apps you create. Apps do not talk to the underlying hardware directly. Instead, they communicate with the hardware through a set of well-defined system interfaces. These interfaces make it easy to write apps that work consistently on devices having different hardware capabilities.
The implementation of iOS technologies can be viewed as a set of layers, which are shown in Figure I-1. Lower layers contain fundamental services and technologies. Higher-level layers build upon the lower layers and provide more sophisticated services and technologies.






As you write your code, it is recommended that you prefer the use of higher-level frameworks over lower-level frameworks whenever possible. The higher-level frameworks are there to provide object-oriented abstractions for lower-level constructs. These abstractions generally make it much easier to write code because they reduce the amount of code you have to write and encapsulate potentially complex features, such as sockets and threads. You may use lower-level frameworks and technologies, too, if they contain features not exposed by the higher-level frameworks.

To Learn More Click On Below Link:

Performance Testing Online Training

The purpose of this test is to understand the performance of application under load, particularly users.

Types of Performance Testing


Load Testing
Load testing is a type of performance test where the application is tested for its performance on normal and peak usage. Performance of an application is checked with respect to its response to the user request, its ability to respond consistently within accepted tolerance on different user loads.

The key considerations are:
What is the max load the application is able to hold before the application starts behaving unexpectedly?
How much data the Database is able to handle before system slowness or the crash is observed?
Are there any network related issues to be addressed?

Stress testing is the test to find the ways to break the system. The test also gives the idea for the maximum load the system can hold.

Generally Stress testing has incremental approach where the load is increased gradually. The test is started with good load for which application has been already tested. Then slowly more load is added to stress the system and the point when we start seeing servers not responding to the requests is considered as a break point.

During this test all the functionality of the application are tested under heavy load and on back-end these functionality might be running complex queries, handling data, etc.

The following questions are to be addressed:
What is the max load a system can sustain before it breaks down?
How is the system break down?
Is the system able to recover once it’s crashed?
In how many ways system can break and which are the weak node while handling the unexpected load?

Volume Testing
Volume test is to verify the performance of the application is not affected by volume of data that is being handled by the application. Hence to execute Volume Test generally huge volume of data is entered into the database. This test can be incremental or steady test. In the incremental test volume of data is increased gradually.

Generally with the application usage, the database size grows and it is necessary to test the application against heavy Database.  A good example of this could be a website of a new school or college having small data to store initially but after 5-10 years the data stores in database of website 
is much more.

The most common recommendation of this test is tuning of DB queries which access the Database for data. In some cases the response of DB queries is high for big database, so it needs to be rewritten in a different way or index, joints etc need to be included.

=> Is the application capable of meeting business volume under both normal and peak load conditions?
Capacity testing is generally done for future prospects.  Capacity testing addresses the following:
Will the application able to support the future load?
Is the environment capable to stand for upcoming increased load?
What are the additional resources required to make environment capable enough?
Capacity testing is used to determine how many users and/or transactions a given web application will support and still meet performance. During this testing resources such as processor capacity, network bandwidth, memory usage, disk capacity, etc. are considered and altered to meet the goal.
Online Banking is a perfect example of where capacity testing could play a major part.

Reliability/Recovery Testing
Reliability Testing or Recovery Testing – is to verify as to whether the application is able to return back to its normal state or not after a failure or abnormal behavior- and also how long does it take for it to do so(in other words, time estimation).
An online trading site if experience a failure where the users are not able to buy/sell shares at a certain point of the day (peak hours) but are able to do so after an hour or two. In this case, we can say the application is reliable or recovered from the abnormal behavior.
In addition to the above sub-forms of performance testing, there are some more fundamental ones that are prominent:

Smoke Test:
How is the new version of the application performing when compared to previous ones?
Is any performance degradation observed in any area in the new version?
What should be the next area where developers should focus to address performance issues in the new version of application?

Component Test:
Whether the component is responsible for the performance issue?
Whether the component is doing what is expected and component optimization has been done?

Endurance Test:
Whether the application will able to perform well enough over the period of time.
Any potential reasons that could slow the system down?
Third party tool and/or vendor integration and any possibility that the interaction makes the application slower.

To Learn More Follow Below Link:

Tuesday, 23 December 2014

Tibco Spotfire Online Training

Spotfire's origins trace back to the Human-Computer Interaction Laboratory at the University of Maryland, College Park where, in the early 1990s, Christopher Ahlberg, a visiting student from Sweden, worked with Ben Shneiderman to develop applications of dynamic queries. Ahlberg returned to Sweden and developed an enhanced UNIX implementation of his visual data analysis tool, the Information Visualization and Exploration Environment (IVEE). Spotfire was launched in mid-1996 by IVEE Development, which was renamed Spotfire
TIBCO Spotfire is an analytics and business intelligence platform allows customers to perform in-depth analysis on data using statistics. It is an enterprise class analytic and data-discovery platform. It's a client application which focus on the creation of data visualization and includes high performance, scalability and security. Spotfire analyst perform compelling adhoc analysis and R scripting. Students will learn advanced visualization methodologies through Tibco Spotfire online training. Also brief explanation of how data will fetch with drill-down and build visualization in server database.
TIBCO Spotfire is a software platform that allows customers to analyze data using statistics. Tibco Spotfire handles data visualization, analytic dashboards and applications, and forward-looking predictive analysis.
With Spotfire enterprise analytics, businesses can create and publish new analytic applications and interactive reports in minutes and share their findings and reports throughout the organization. Spotfire is a powerful tool for consultants, business analysts, or managers seeking to better understand data and gain richer insights.

To Learn More Follow Below Link:


MSBI Online Training

                                                                MSBI
Microsoft Business Intelligence is a power full suite and an ETL (Extract Transform and Load) tool helps to find solutions for BI and data mining queries. It uses visual studio and SQL Server. The three main components of MSBI is SSIS-integration tool, SSAS-analysis tool, SSRS-reporting tool. It will effectively analysis data to drive value to the organization. User can create ad-hoc transactional report and a workspace to share in the spread sheet. This tool facilitates user to access accurate information and work quickly to take better business decisions this enhance business agility.
Note: Simply Business intelligence is a broad category of applications and technologies for gathering, storing, analyzing and providing access to data to help enterprise users make better business decisions.  
BI Applications:    BI applications include the activities of decision support systems, query and reporting, online analytical processing, statistical analysis, forecasting and data mining.   
Dimensional Data Model: Dimensional data model is used in data ware housing systems that means designing facts, dimensions, hierarchy.
§  Dimension table :
The dimension table provides hierarchy and detailed information about the attributes. 
For Example:   Dim product, Dim customer and Dim time etc.
§  Fact table:
A fact table is a table that contains measures. Note: Measure is a numerical value and it is key value to analyze your business data and it also evaluates the performance of the organization.  
Data Ware House Concepts 
Data ware housing is a Relational data  base it has its own characteristics. 
Time variant Integrated Data Base 
TINS Non-volatile Subject Oriented   
(1)   Time Variant: Data ware house is a time variant data base source, the business users perform analysis on their business information with respect to various time period.   
 (2) Integrated Data base: Data ware house is built by integrate the data various operational sources into single data base.   
(3)  Non – Volatile: Once the source data is inserted into the data ware housing it doesn’t reflect the changes since it is static or read only data.    
(4) Subject Oriented Data ware house is a subject oriented data base and it stores specific data about specific department in the complete organization. It is also known as data mart.     
Note :- Data mart is also known as HPQS (High Performance Query Structures) Data warehousing Architectures: In designing data models for data ware houses or data marts, the most commonly used schema types are,
1.    Star schema
2.    Snowflake Schema
The star schema data ware housing design contains at least one fact table and surrounded by dimension tables like a star tech dimension is represented as a single table. The primary key in each dimension table is related to foreign key in the fact table. Note:
1.    A simple star schema consists of one fact table and a complex star schema have more than have more than one fact table.
2.    All measures in the fact table are related to all the dimension tables.
The Snow Flake schema is an extension to star schema, where each point of the star schema explodes or divides into more points. In star schema each dimension is represented by  a single dimension  table, where as in a snow flake schema the dimension table is normalized into multiple look up tables, each representing a level in the dimensional hierarchy.    
In the above data ware housing schema example, we have three lookup tables (Dim category, Dim product sub category and Dim address type).
To Learn More Click On Below Link:


Monday, 22 December 2014

Oracle Financials Online Training

Oracle E-Business Suite consists of various applications.
Manufacturing, Supply Chain Management, Customer Relationship Management, Projects, Human Resources, Financials etc.
Oracle Financials consists of mainly five modules that are Accounts Payables, Accounts Receivables, Fixed Assets,General Ledger and Cash Management. These five modules are stand alone applications cater to the specific requirements and together they called as Oracle financials. Likewise each area such as Manufacturing, Supply Chain Management, Projects, and Human Resources etc consists of various standalone modules and all put together called as Oracle E – Business Suite. In Oracle environment each application are called as modules.
An Organization at the outset has to deal with external entities / parties like Suppliers (Vendors), Customers, Banks.
Accounts Payables module used to manage our Suppliers and what we purchased from them, how much we paid them, whether we paid in time to avail the discount and what is the payment method we are using etc.
Accounts Receivables used to manage our Customers, sales to them, are they paid; follow up to receive the payment from them, what is the credit limit etc.
Oracle Fixed Assets used to manage the Assets of the company, like cost of the assets, location and user of the assets, what is the depreciation expenses for individual assets, life and depreciation methods used, accumulated depreciations etc.
Cash Management module used to reconcile with the bank statement at the end of the month and also tells you the status of the bank accounts and whether it syncs with our books of accounts are not, besides it helps to plan and monitor the cash flow and funds flow.
General Ledger and most important module used to maintain the accounting of the company. We can call it as a central repository of all accounting information of the organization. At the end of the day all business transaction are translated into debits & credits and flowing into General Ledger and accounted. General Ledger module is capable enough to Classify, summaries, allocate to concern accounts in order to report as required by statutory authorities, management and share holders.
Accounting is nothing but quantitative measurement of business events that are taking place. How much purchased, sales made, expenses incurred, profit you have made and how much assets and liabilities you have at point in time or in a period . All the accounting information flows into GL in the form of JE from other modules, imported and posted into respective accounts. All the financial reports are run out of GL module and show the financial position and health of the company.
The strength of E-Business Suite is modules talk each other and information flows from one module to other, besides shared entities like Suppliers, Customers, Banks Accounts, Employees, Items are used by all the modules wherever needed but defined only once, which prevents the redundancy, that is where the strength comes.
To Learn More Follow Below Links: