Selected Submissions to be presented at the Asia Pacific Software Conference
on March 27th and 28th, 2007

• Objective measurable criteria in software testing projects using QUASI framework
  Kirankumar Marri from Independent Validation Solutions from Infosys Technology Limited, Bangalore, India

• An Approach to Exploratory Testing
  Yogeswari Jayaraman from  Motorola Global Software Group, Motorola Multimedia Sdn. Bhd, Malaysia.

• Developing an Enterprise Testing Center of Excellence
  Shirley Tan from Mercury Interactive, Singapore

• Requirements Management, Models and Metrics
  Narendra Kumar Nagaram, Ashok Pantham from Satyam Computer Services, India

• Software Testing Strategy in CMMI Level 5 Organization
  Woi Hin Kee from Motorola Global Software Group, Motorola Multimedia Sdn. Bhd, Malaysia

• Testing Centre of Excellence (TCOE) - a Unique Model to Software Testing Services
  Jayashankar Rajanna from Infosys Techologies Ltd, Mysore, India

• Test Automation and Infrastructure for Network Processor Software                  
  Wong Woon Kiat from Intel Malaysia

• Effective Test Planning
  Ng, Orr Thiak from Motorola Software Group, Singapore Software Centre

• Software Testing and CMMI
  Phil Robinson from Lonsdale Systems, Perth, Australia; Processworks, Singapore 

• Testing for Large Projects
  Shriswaroop H. Joshi from Satyam Computer Services Ltd.

• Test Automation Framework Development
  Sathyem from Ready Test Go, CSS Group

• Test Strategy and Automation for Complex Systems
  Xiaoyan, Wang; Binhua, Zhang; Jiong Li; Wilfred, Soon of Motorola Software Group - Singapore

• Web Test Automation with Selenium
  Vivak Prahlad and Chad Wathington, Thoughtworks, Bangalore

• Performance Testing - Dispensable?
  Helen Ma from NCS Pte. Ltd, Singapore

• Managing Quality of Service Oriented Architecture (SOA) Implementations
  Richard Ko from Mercury Interactive, Singapore

• A Reconnaissance Approach to Support Regression
  Authored and Presented by Suhaimi bin Ibrahim, Centre for Advanced Software Engineering, Universiti Teknologi Malaysia, Kuala Lumpur, Malaysia

• Using ODC Impacts for a Customer Centric Approach to Testing
  Authored by Sasha Selvandrah, Parameswary Namebeley,Chiang Yin Kia, from Motorola Global Software Groups, Malaysia

• Aim, Assess and Improve the Testing Process
  Authored by Narendra Kumar Nagaram & Ashok Pantham, from Satyam Computer Services, India

• Defect Analysis: An Approach to Improve Software Development Life Cycle
  Presented and Authored By Subashini Raghavan, Intel MSC Sdn. Bhd, Cyberjaya, Malaysia

Authored and Presented by KiranKumar Marri, Independent Validation Solutions
Infosys Technology Limited, Bangalore (NASDAQ: INFY)

Abstract:

Sustaining operational efficiencies while managing software testing projects is a challenge in today’s IT industry. In the previous work by the author,  a new framework QUASI was proposed to manage testing projects within a unit (Unit can be a project or group of projects under an account or group of accounts under a division or a group of divisions under a business focused on testing activities).The key driver for QUASI framework was to evaluate the basic unit and consolidate the results to the highest unit in the chain – project to account to division to unit can be an example based on how the organization is structured. This work was predominantly applied to software testing project management function with the focus on recommending a means to measure the effectiveness of test management.

The goal of the current work is to measure the objective criteria (also referred to as Objective Measurable Criteria or OMCs) that integrate metrics within the software testing processes. This helps to reap the benefit of operational efficiencies and derive the right metrics to keep the project on track. This paper focuses on the OMCs that are applicable for different stakeholders throughout the life cycle of a testing project using QUASI framework. The OMCs are grouped and classified under the following key areas:

• Operations OMCs
• Process OMCs
• Strategic OMCs

The classification helps the Test manager and stakeholders to evaluate the different dimensions of testing project. The criticality and relevance of OMCs may vary based on the nature of the project and complexity of testing. To maintain the focus, the paper provides illustrative OMCs to demonstrate its applicability using QUASI framework, while recognizing that it is not possible to cover all measures relevant to the project. The approach is to highlight specific phases of testing life cycle with illustrations on how to manage them optimally.

Some of the focus areas in the paper are:

1. Traditional metrics Vs OMCs
2. Different dimensions of OMCs
3. Usage of QUASI framework in Testing projects and defining OMCs using illustrative case study
4. Insight into deriving OMCs in different phases of testing life cycle
5. Trend analysis using OMCs
6. Analyzing OMCs and interpreting the results and predictability

QUASI Framework: Overview

Quality of work: Quality of the work done at project level forms the basis of the entire framework for the unit. This covers all aspects of the project – documentation, reviews, competency, training, design etc.
Unit Maturity level: The understanding of process adherence for the project can drive the end deliverable and meeting client expectation. This covers aspects of process, improvements, tracking etc
Adherence to Plan: Meeting the project goals at extended schedules or effort may not be economical for the unit. This covers sub-dimensions like budget forecasting, resource management, schedule, effort, estimation, hardware & software requirements etc
Stakeholder feedback: The 3 sub-dimensions that are considered are client, project team and the senior managers within the unit.
Innovation & Knowledge Management: This dimension focuses on the building the innovation and knowledge management aspect of the unit. The initiatives and solutions build within in the project can help the stakeholders. Repeat business can happen only when the client sees a value-add from the project and team members.

References:

1. KiranKumar Marri, Weighted metric value-added methodology for better project management, PML 2004 Conference, QAI May 2004
2. KiranKumar Marri and Krupa RC, QUASI: A Framework for managing testing projects at Unit level, STEP-IN 2007
3. Infosys Technologies Limited Sources, www.infosys.com

Author & Presented by

KiranKumar Marri, Senior Test Manager, Infosys Technology Ltd.

KiranKumar Marri is currently working as a Senior Test Manager at Infosys Technology Limited, Bangalore (NASDAQ: Infy www.infosys.com ). He is associated with the testing practice - Independent Validation Solutions Unit. He has extensive software experience in the field of Life sciences, Biomedical applications and retail check-out terminal applications. He has about 11 years of experience in the IT industry covering project management, delivery and client relationship roles. He has published & presented several papers in conferences in the field of project management, software testing, clinical data management and biomedical engineering. He won the best paper award in the PML Conference in 2004. His current research interest and publications are primarily in Project Management and Quantitative Test Management. He received his Bachelors in Electronics & Communication engineering from Madras University in 1993 and a Masters by Research in Biomedical Engineering from Indian Institute of Technology Madras, Chennai in 1996. Kiran can be contacted at kirankmr@infosys.com

Authored and Presented by Yogeswari Jayaraman, Global Software Group, Motorola Multimedia Sdn.Bhd.Malaysia

Abstract:

Exploratory Testing (ET) is a fun and powerful approach to software testing. More often than not most of us unconsciously perform ET in testing process. Be it alongside scripted testing or model based automated testing. Yet not many of us study this approach. This approach could be more productive and beneficial then scripted testing. Exploratory Testing can be defined as a combination of test design and test execution. In another word exploratory testers perform all three activities simultaneously, which is learning, test design and test execution. Like the name specifies, in ET, we test while we explore. This is contrast to a process in which all the test cases are designed beforehand and run later. ET put emphasis on creativity and spontaneity. In ET a test case is changed based on something that is learned while the testing was done. ET can be considered as an approach rather than as a technique. Exploration itself is not testing but it modifies testing in order to improve testing to be more productive. ET is simply the skills of testing, applied in the moment. For e.g you turn the radio on but it does not turned on, the thing you do next probably constitute an exploratory testing process. The games like Jigsaw Puzzle and Sudoku are all exploratory activities. In this paper we will discuss when and why do we use ET, a case study on it and how can we benefit from it.

Presented by

Yogeswari Jayaraman, Global Software Group, Motorola Multimedia Sdn.Bhd.Malaysia

Yogeswari Jayaraman is currently a Software Test Engineer for AEMS team in GSG Malaysia. She joined Motorola in December 2005, and working in AEMS Subsystem Verification and Validation team for a year. She graduated from University of Malaya, with a Bachelor's Degree in Computer Science majoring in Computer Systems and Networking and currently doing her Master's in Computer Science majoring in Management Information System also in University of Malaya.

Presented by Shirley Tan, Lead Technical Consultant, Mercury Interactive Singapore

Abstract:

Many companies are gradually consolidating IT services, including software testing. To support enterprise-wide software testing, companies have established Quality Centers of Excellence to conduct quality assurance of the software developed. The successful development of an enterprise level testing Center of Excellence involves changes in infrastructural, people, and processes to support collaboration amongst teams across geographies and timezones. In addition, it is also essential to establish key performance indicators to measure the success of the Quality Center of Excellence.

This topic discusses the infrastructrural, people and process changes required to support the Quality Centers of Excellence and the key performance indicators to measure its success.

Presented By:

Shirley Tan, Lead Technical Consultant, Mercury Interactive Singapore

Shirley is the Technical Lead of Mercury Application Delivery solutions, ASEAN, comprising LoadRunner, Quality Center and QuickTest Professional. She has close to three years of experience with Mercury, and has worked with customers in various industries such as banking and government to establish Quality Centers of Excellence. Prior to Mercury, Shirley has worked as a senior consultant in Deloitte Consulting.

Authored by Narendra Kumar Nagaram & Ashok Pantham
Presented by Narendra Kumar Nagaram & Ashok Pantham

Abstract:

With continuous advancement in the sophisticated applications being used, there is a constant demand for a better output from the customers. This sophistication brings with it, complicity as well as need to have up-to-date marketable features in the applications.  This desire to have the latest features, burdens the project with changes. In addition, there may be changes or addition of new requirements from various stakeholders. These continue till the design phase or sometime even till the implementation phase. Thus affecting the schedules, budgets, and stake holders etc greatly.

Though testing is an important task, it often does not get its importance due to many factors. This is even more challenging when the requirements keep changing while the implementation is in progress. This creates lots of rework which is includes lot of effort, cost and schedule variance.

Thus, instead of performing testing as a routine task of test case execution to be performed only at the completion of the implementation, it needs to be incorporated from the very beginning of the development cycle. This not only reduces the cost and effort of the bugs to be fixed but also confirms that the requirements are being met. Having the quality assurance in the development life cycle helps by including testing from the very initial phases i.e. from requirement stage.  This mechanism not helps in building the quality product but also helps in managing the changes and having traceability for future enhancements.

Managing of changing requirements though a difficult task, can be controlled if performed using some effective ways. The requirements gathered should base lined and the same should be testable. The models like state diagrams, finite state machines etc helps in testing the requirements at the very gathering phase. These models not only aid in testing of requirements, but also help in creation of test cases which can be applied to the fully implemented application.

This paper deals with techniques for controlling the changes in the requirements and testing using these models/model checkers .The creation of test cases using some basic testing models which are the benefits would be mentioned along with metrics collection mechanisms.

The topic can be considered as intermediate and is aimed for test leads/ test managers/quality analysts who are involved with the quality assurance projects. This would enable the audience to use these concepts by implementing the project in a cost effective way.

Authors & Presenters Profiles:

Narendra Kumar Nagaram

Has been associated for past six years and eight months with Satyam Computer Services Ltd., a SEI-CMM level 5 company, which occupies a significant position in top ten IT companies in India with fortune 500 customers as its clients.  Have experience of working in varied technologies at different phases of the software development life cycle. After completing the graduation in B.E (Computer Science) from Osmania University, had pursued a master’s degree in Software Engineering from BITS, Pilani. Participated in QAI conference during 2004 and 2006.

Ashok Pantham

Has been working for over three years with Satyam Computer Services limited, a SEI-CMM level 5 company, which occupies a significant position in top ten IT companies in India with fortune 500 customers as its clients. A CSTE certified professional with diverse experience in the Software Testing Industry. He has worked extensively in all the phases of Software Testing and on Test Automation and Frameworks.  Holds a master’s degree in computer applications and is an active participant  in many of the internal conferences conducted by Satyam.

Authored by Woi Hin Kee & Ng Pei Ling, Motorola Multimedia Sdn. Bhd., Malaysia
Presented by Woi Hin Kee, Motorola Multimedia Sdn. Bhd., Malaysia

Abstract:

Software testing is a major component in the software development life cycle which plays a major role in lowering cost of quality for software and delivering higher quality software applications to customers. However, software testing is both time consuming and costly regardless of the type of software maintenance that is performed or software testing strategy employed. A complete test cycle has to be repeated each time the software code base is changed. Therefore, strategies to lowering the software testing cost by means of shortening testing cycle and improving testing accuracy, thus giving more merits to test results. In this paper, we will talk about the Software Testing Strategy starting from how the test cases is being created from the requirement specification documents, how the test cases being run, and how the defects is being track.

Presenter:

Woi Hin Kee, Motorola Multimedia Sdn. Bhd., Malaysia

Paper Authors:

Woi Hin Kee

Woi Hin Kee obtained his B.IT (Hons) in Information System Engineering from Multimedia University, Malaysia in 2005. Since then he has been working in Motorola. For the first one and a half year, he is with the iDEN OMC-R Box Test Team of Global Software Group (GSG) in Motorola, Malaysia. Currently, he is with the CDMA Development team majoring in Mediation process. He has contributed technical papers in 3rd Motorola China Technology Symposium, 2006 and 2nd Malaysia Software Engineering Conference, 2006. Besides that, he has presented his paper in 3rd International Conference on Innovation in Information Technology, Dubai 2006.

Ng Pei Ling

Ng Pei Ling received her Bachelor of Information Technology (Majoring in Information Software Engineering) from Multimedia University, Malaysia, in 2005. She joined GSG Malaysia in May 2005 as a software test engineer. For the first one and half year, she was working as a member of UMTS project. Currently, she is working with GSM software testing. In next month, she will be transited to another test team which named as CDMA SST team in GSG Malaysia.

Presented By Jayashankar Rajanna Test Analyst, Infosys Technologies Limited
Authored by Jayashankar Rajanna

Abstract:

Overview

In today’s business world, Competitiion is the order of the day for any organisation across the globe, Be it a Aeronautical Industry or an IT company. Each and every organisation is exploring newer opportunities to increase their topline and bottom line revenue.

Over a last few years Software Testing has taken a greater Momentum in the IT service space. This is mainly due to the fact that the organisation are realising the importance of having software with near -zero defects.

Gone are those days where, Testing is conducted by the development team itself or with only client. Today testing became a such profession service that, many organisation prefers thier software should be tested by a Independent organisation.

Testing Center of Excellence (TCOE) a unique model in the software testing field which is widely recognised as the key differentiater over the traditional model of software testing services. This model uses the concept of integrating all the required testing capabilities at a single place. The successful adoption of this model results in deployment of software in lesster time, quality and cost effective.

What is TCOE
      
Testing Center of Excellence(TCOE) is a testing practice which integrates People, Process, Tools, Expertise and Management at one place for providing effective testing services.

TCOE  is like a supermarket  which caters the needs of all testing services. Though it is a Unit, it follows the  principle of managing any organization ie. the internal organisation of the centralized testing team is comprised  meeting requirement of specific LOB or service.

TCOE Framework

• Integration of  all testing capabilities i.e. People, Process, Tools, Exertise and Mangement skills
• Enables the reusability of Artifacts and their by improves the productivity
• Analysis of the process by using various Metrics and enables scope for continuous improvment
• Follows the systematic process and consistancy
• Adopts risk based testing, requirement Traceability and knowledge management techniques to improve testing effectiveness

Conclusion:

Considering the above, one can understoold that TCOE is a better model for the emerging changes in Software Testing Services. Wih the centralized pool of all the required capabilities for software testing, TCOE enables the organisations to gain the maximum benefit both to the vendor and client in testing services This paper will concentrate on Framework/need and the benefits of TCOE to the testing service providers

Presenter Profile:

Jayashankar Rajanna, Test Analyst, Infosys Technologies, Ltd.

He holds Master Degree in Business Administration (MBA) from Bangalore University, He is a Certified Software Tester (CSTE) from Quality Assurance Institute USA and also holds Dipolomo in Financial Services from Chartered Institute of Bankers in Scotland.  

He has more than 8 years of industry experience in the field of  Finance, Capital Market and software testing.

He is associated with Infosys from last two years. In his last assignment he was leading a testing team which delivered applications in the area of Investment Banking for a Major US based Finanancial Service Provider.

Presented by Wong Woon Kiat of Intel, Malaysia

Abstract:

The Infrastructure Software Organization (ISO) team in Intel develops software that shipped together with network processor. Before release, it will go through test cycle to ensure the software works on different combination of hardware and operating systems. The test team developed a testing framework and execution engine to automate the test. Throughout test cycle, it executes about 1000 test cases. The execution engine helps to reduce the test cycle time from 1 week to 2 days.

The testing framework is developed in PERL. This paper explains basic functionalities provided by the framework  like hardware setup, result checking, reporting and other routine tasks. The framework allows testers to rapidly write a test script without worrying about the underlying complexity.

The execution engine manages and optimizes the usage of all hardware resources. This paper will explain the underlying scheduler algorithm that minimize idle hardware and complete all test cases in the shortest time possible. It will also detail the infrastructure setup to accommodate all tests.

In summary, test automation allows the team to response rapidly to changes introduced by the developers. It also helps to reduce error caused by manual testing and free up testers resources to focus on making better test plan to attack developers code. More important, it scales well when test cases increased and more hardware resource available in the future.

Presented By:

Wong Woon Kiat of Intel, Malaysia

Woon Kiat is a software engineer with more than 8 years experience in IT industry. Throughout the years, he experienced in developing Win32 applications with C++, MFC and C#. He worked on manufacturing automation since joining Intel in 2005. For the past 12 months, he switched his role to focus on test automation on Linux platform while picking up PERL.

While not coding, he can be found flexing his muscle on badminton court. Woon Kiat hold a bachelor degree in computing and certified as Microsoft Certified Solution Developer (MCSD & MCSD.Net).

by Ng, Orr Thiak, Motorola Software Group, Singapore Software Centre

Abstract:

Tutorial Objectives:

This paper focuses on demonstrating effective test planning (test strategy, test automation and test management and etc.) for software testing. Proper planning of test processes not only helps in performing test activities efficiently and effectively but also helps in achieving Total Customer Satisfaction.

Who should attend:

• Test/Development Engineers who are looking to create effective test strategy and/or test automation strategy that results in cycle time reduction.
• Test/Development Managers who are looking to create a quantitative test management to improve cycle time reduction.

Detailed Tutorial/ Workshop Outline:

1. Test strategy - How to plan effective test strategies.
2. Test automation planning - How to plan successful test automation.
3. Test management - How effective test management results in on-time delivery and improvements in cycle time reduction

Authored and Presented by:

Ng, Orr Thiak

Ng, Orr Thiak is a Senior Engineer at Motorola Software Group, Singapore Software Centre. She is responsible for software system test and has many years of experience in component test, system test and field test. She has authored more than 10 papers related to software testing that are published within Motorola Symposium.

Authored and Presented by Phil Robinson, Principle Consultant, Lonsdale Systems, Australia

Abstract:

CMMI for Development Version 1.2 is a collection of best practices intended to guide the development of products and services.  Since software is one of the product categories targeted by CMMI, it would be reasonable to assume that at least some of its advice would be specific to software testing.

However, a detailed scan of the text of CMMI reveals that very little of its content is drawn from the common vocabulary of software testing.  For example, “system test” is not mentioned, “test plan” is mentioned twice and “test case” only four times.

Based on this evidence alone, it would be reasonable to assume that the CMMI had no relevance to software testing and thus ignores one of the fundamental disciplines of software engineering.  In reality, this could not be further from the truth.  This paper demonstrates the relevance of CMMI to software testing by mapping the concepts and the language of CMMI to an accepted glossary of software testing terms.

The paper starts by identifying which CMMI process areas are relevant to software testing.  It then moves on to explain how the Risk Management (RSKM) process area can be applied to the development of test plans and concludes by describing how the Causal Analysis and Resolution (CAR) process area can guide an analysis of test incident reports.

Keywords

Causal analysis, CMMI, risk analysis, risk-based testing, software process, software testing, test planning

Presenter Profile:

Phil Robinson, Principle Consultant, Lonsdale Systems, Australia

Phil Robinson has worked with information technology for more than thirty years.  During his lengthy career, he has been involved in the planning, analysis and implementation of a diverse range of business, engineering, scientific and technical information systems.

Phil is an experienced workshop facilitator and has led numerous workshops in the course of his consulting assignments.  He has extensive training experience, earning a reputation as a lucid and knowledgeable presenter.  Phil has presented training courses for clients in Australia, India, Indonesia, Hong Kong, Malaysia, Philippines, Singapore Taiwan and Thailand.

As well as presenting courses, Phil has authored numerous courses for industry and three University units.  Earlier in his career, he wrote two books on programming Apple computers.  The books were published in a number of countries including the USA, UK and as translations in Germany and France.  More recently, Phil has co-authored two award-winning articles describing an original organisational theory and a chapter for a book on enterprise architecture.

Phil has a degree in Electrical Engineering and has trained as a Group Work Leader.

Authored and Presented By Shriswaroop H. Joshi, Satyam Computer Services Ltd.

Abstract:

Testing for large scale web-based projects poses unique challenges for the organizations.  In this paper the author describes the pitfalls faced in one of the large testing projects and the measures taken to bring it back on track.

While testing for one of the large projects the project team encountered several challenges such as difficulty in freezing the requirements and UI documents, need for a strong change management process, training for the functionality, changing test case design process etc.  This led to test execution defects in system testing (which were not application defects) and consequent reworking of the test cases. 

An analysis of the root cause indicated that a strong change management process, sound communication between the project and the testing team would have helped reduce the re-work of test cases for the testing organization. Similarly training the analysts on the functionality of the application would have helped speed up the test case design.

In addition use case path based testing would ensure that the development and the testing teams are on the same page and would help the test organization get a better idea about the status of a planned component delivery.

In summary this paper emphasizes the need for commonly known testing/project management practices and use case path based testing.

Author and Presenter Profile:

Shriswaroop H. Joshi, Satyam Computer Services Ltd.

Shriswaroop H. Joshi holds Master degree in Computer Application. He is also Certified Software Tester. He is a Sr. Quality Engineer and has been with Satyam for last 3 years. He has 5 years of Industry Experience. He is currently associated with HCU-Quality (Qedge) and is working for one of the largest Insurance Company in USA.

Authored and Presented by: Sathyen from Ready Test Go, CSS Group

Abstract:

• Introduction
  
• Why Framework?
  
• Challenges
  
• Tool Recommendation Approach
  
• Design and Development Approach
  
• Key-Benefits
  
• Q & A
  
  

Business Needs

Software Testing has gained significant importance in the recent past and the industry expects a market of 13 Billion USD in 2006. Business shower of today is such that IT organizations are asked to do more with fewer resources, reduced time and without reduction in the quality of the product that is being delivered. This scenario calls for the following factors:

• Identify a best suited tool for my application
  
• Test automation of my multi technology product suite(for ex: containing a UI based application and SOA based web services)
  
• Cost-effective approach
  
  

Solution Topics

A phased approach considering different factors would provide a solution to this approach. Proposed topic would cover:

• Need for a framework and the challenges for creating a framework.
  
• Different phases involved in framework development
  
• For tool recommendation: types of tool and factors to be considered
  
• Factors to be considered, while creating a framework
  
• Components to be included in designing the framework
  
• How to design a prototype for input data files?
  
• Key- benefits of framework
  
  

End-User Benefits

Business user will be benefited, by understanding different factors involved in the test automation framework and the key-benefits and ROI in future

Technical users will know how to design a customized framework for different application and propose a cost-effective solution.

Project managers would come to know about, what needs to be considered only for estimation of framework development.

Presenter Profile:

Sathyen from Ready Test Go, CSS Group

As a Senior Technical Analyst at ReadyTestGo, Satyan has been working on various test automation projects, providing tool extensibility solutions and test automation framework design. With more than 6 years of work experience in the IT industry he specializes in providing a consultative approach for test automation solutions. Satyan has designed 15+ test automation frameworks for major clients. He also conducts research on different technologies which includes SOA testing, emulator based testing, and Web Testing and MFC based application testing. He holds a Masters degree in Computer Applications from the University of Madras, also holds a Microsoft certification on .net architecture.

Authored By Xiaoyan, Wang; Binhua, Zhang; Jiong Li; Wilfred, Soon of Motorola Software Group - Singapore

Abstract:

Software testing is an integral, costly and time-consuming activity in the software development life cycle. This presentation closely examines the product life cycle, test scope, test environments and tools used in each specific testing phase.  These includes the use of traceability metrics to track test coverage, the quality goal set for next testing for smooth test transition as well as controlling the defect escaped by metrics chart which helps to monitor test effectiveness.

Using this test strategy, focus will be placed on the opportunities for test automation in the implementation phase. This paper will introduce the basic notion of automation methodology for requirements mapping, results verification and UML model validation as far as component tests. By using the automated tools, time and efforts savings are significantly high resulting in early detection of faults and optimize the effort for defect resolution. The highlight of this presentation will be on how these automation tools enhances early test phases based on simple test approach and through this, defining the test strategy that helped to reduce overall project effort, improve product quality and ensure on time delivery.

Author Profiles:

Li Jiong

Li Jiong, Software Engineering Section Manager in Motorola Global Software Group Singapore, has 15 years of Software design, systems development and integrations experience in wide variety of industries including Manufacturing, Telecommunications, and Engineering and Retail industries.

Currently Li Jiong is a program manager of CDMA OMCR MIB development team. She went through 9 releases of OMCR CDMA system. She worked as technical lead in different function areas like UI, Agent (CMIP) and MIB, involved from requirement gathering to testing every phase of development circle. She worked as the program manager in OMCR MIB development for release 19 and 20, each release developed 10+ customer feature, involving more than 100 SM development effort, and 40K+ LOC. OMC-MIB development release 18 & 19 passed CMMI level 5 audit in 2005.

Zhang Binhua

Zhang Binhua is a Senior Software Engineer in Motorola Software Group. Binhua’s 5 years experience includes Level 4 Development support for Sub Systems Testing, Feature development and on site support in United States for System Integration tests. Binhua holds the role of Feature Development Leader and is overseeing multiple development work. Binhua has actively participated in Network Management Technology group which innovates the modern day networking technology.

Dhamodharan Malini

Dhamodharan Malini is a Senior Software Engineer working in Motorola Software Group - Singapore, for the past 6 years. She is currently the technical lead of the team involved in software development for the configuration management functional area of Network Management software in CDMA Telecommunication RAN system. She is involved in requirements gathering, design, coding, and component testing phases of the software development lifecycle. Malini has been actively participating in CMMI SCAMPI Class A assessment in MSG - Singapore, as a representative for her project.

Wang Xiaoyan

Wang Xiaoyan, a current development Feature Lead has been with Motorola Software Group - Singapore for past 3 years as a Software Engineer. His current role involved in feature / MOL development and testing in the Motorola CDMA 1X Network Management software. Xiaoyan. As a feature lead, Xiaoyan oversees the technical aspects of a feature team which includes preliminary requirements inspections, high and low level design phases, coding and testing cycle.

Wilfred Soon

Wilfred Soon is a Software Engineer with Motorola Software Group since 2003 and have had been involved in multiple telecommunications projects such as Motorola mobile handsets C350V, V80 and Motorola CDMA RAN Operations and Maintenance - Radio (OMC-R) applications development and testing.

Authored and Presented By Vivak Prahlad and Chad Wathington, Thoughtworks, Bangalore

Abstract:

Selenium is a popular open source toolkit for web test automation.  Selenium tests run directly in a browser, just as real users do, and they run in Internet Explorer, Mozilla and Firefox on Windows, Linux,  
and Macintosh. No other test tool covers such a wide array of platforms.

This presentation will:

• Give an overview of the framework and how it works.
• Show case the different ways of using Selenium, through FIT-style tables or Selenium RC in Ruby and Java.
• Work through a couple of example test scripts
• Explain the limitations of Selenium, where it can be applied, where it can't, what problems it has.
• Finally a demo.
  
  

Presenter and Author Profiles:

Vivek Prahlad, Director of Innovation, Thoughtworks, Bangalore

Vivek Prahlad is an IT professional with 7 years of industry experience.  He joined ThoughtWorks Inc. in 2003 after a stint at i2 Technologies, where he lead the development of i2’s scheduling products. He currently leads the development team for ThoughtWorks testing software products. The team is charged with taking test automation to the next level.

As the Director of Innovation, he is charged with helping to create an environment where Innovation and Open Source can thrive. Vivek is the author of Frankenstein (http://www.openqa.org/frankenstein), an Open Source testing tool for Swing applications.

During his career, Vivek has worked as a Technical Lead, Agile Coach, and Project Manager.  He has worked in various software industry verticals, including supply chain management, manufacturing, financial services, and embedded systems.

Education, Bachelor of Technology, Metallurgical Engineer from The Institute of Technology, Banaras Hindu University, Varanasi.

Master of Business Administration (Finance and Systems), Indian Institute of Management, Calcutta.

Chad Wathington, Product Manager – Testing Software, Thoughtworks, Bangalore

Chad Wathington  is an IT professional with 7 years of industry experience.  He joined ThoughtWorks Inc. in 2004 after a stint in strategic consulting at the Boston Consulting Group.  In his current assignment, he provides the strategic vision and commercial director for some of ThoughtWorks testing software products. He is charged with developing ways to reinvent test automation in the enterprise.

During his career, Chad has had experience as a business analyst, quality assurance analyst, and project manager.  Through his career, he has worked in various software industry verticals including manufacturing, healthcare, financial services, and consumer services.  Chad’s test design experience has spanned from manual test planning to extensive automation with both commercial and open source tools.

Chad is a Caterpillar Corp. trained Six Sigma Black Belt.

Education
Bachelor of Economics from Harvard University, Cambridge MA.

Authored and Presented by Helen Ma, NCS Pte. Ltd, Singapore

Abstract:

The presentation will provide a broad understanding of performance testing, what it encompasses, its importance, its benefits and its place in the overall system implementation.  The speaker will also offer her personal insights into the myths surrounding this oft misunderstood cousin of functional testing.

Presenter and Author Profile:

Helen Ma,  Test Manager, NCS Pte. Ltd.

Helen is a well respected practitioner in software performance testing in Asia.  Having spent 8 years in application development and database administration, she accidentally stumbled upon the fascinating world of performance testing.  Over the last five years, she has lead, managed and executed enterprise wide performance testing of complex systems; from bespoke to COTs implementations; with a myriad of 3rd party products on heterogenous environments; for systems that serves user base as large as 60,000.  Her zealous passion for this art has won over many sceptics and has made her an evangelist of performance testing.

Presented by Richard Koh, Technical Consultant with Mercury Interactive Singapore

Abstract:

Organizations adopt SOA implementations to lower IT costs through reuse and improve their responsiveness to the needs of the business, so that business can be more “agile.”  However, SOA introduces a huge degree of risk if it's not done right.  And the risk is not just IT risk - it's a real risk to the business.

SOA implementations need to encompass a quality assurance focus, and IT needs to build and manage a QA process to ensure sustained quality.  Quality objectives must be carefully defined with centralized quality assurance and test automation to optimize the use of IT resources in supporting services.  To ensure that services will scale in a production environment, organizations must manage service quality and conformance across multiple projects.

The focus of this topic is on optimizing the quality and performance of SOA implementations through quality management and test automation.  The successful deployment of services requires the ability to manage the quality of these services so organizations can optimize the use of IT resources and reuse services across multiple applications to enhance business agility.

Presenter Profile:

Richard Koh, Technical Consultant, Mercury Interactive Singapore

Richard is Technical Consultant with Mercury Interactive Singapore.  He is responsible for all Application Delivery solutions which includes functional, performance testing and test management.

Richard has more than 4 years of experience in software testing and quality assurance.  Prior to Mercury, he has led teams in requirements, design, and development and testing for enterprise project implementations.

Authored and Presented by Suhaimi bin Ibrahim, Centre for Advanced Software Engineering, Universiti Teknologi Malaysia, Kuala Lumpur, Malaysia

Abstract:

Software regression testing requires an existing program to be retested against some test cases as a result of code modification.  The result needs to be analyzed to identify which parts of the code have been affected by the test cases.  In this paper, we present a reconnaissance approach to support regression testing for C++. Software reconnaissance was originally inspired by industrial maintainers about the need for better ways of locating software features in large systems. This paper presents our experience in using software reconnaissance techniques with the help of a tool package we developed and applied it to an embedded software project, called the OBA system. The work observes the ability to identify the impacted components of test scenarios that can lead to a better change impact estimation, design decision and program comprehension.

Author's Profile:

Suhaimi bin Ibrahim, Centre for Advanced Software Engineering, Universiti Teknologi Malaysia, Kuala Lumpur, Malaysia

Suhaimi Ibrahim is a senior lecturer of computer science attached to the Centre for Advanced Software Engineering (CASE), faculty of Computer Science and Information System, Universiti Teknologi Malaysia, Kuala Lumpur. He involved in several short term and National research schemes on software development and maintenance projects. He obtained a B.Sc computer science (Stratchlyde, 1986), M.Sc computer science UTM, 1990 and PhD computer science (UTM, 2006). His research interests include software testing, reverse engineering, change impact analysis and software quality.

Authored by Sasha Selvandrah, Parameswary Namebeley, Chiam Yin Kia from Motorola Global Software Groups, Malaysia

Abstract:

Orthogonal Defect Classification (ODC) by definition is a method for capturing and classifying defect information. Once the defect information is categorized, the information is then typically used to improve the quality of the software product. This paper intends to describe a new process whereby the Impact Category of the ODC Opener Section is used as a preliminary guideline for the planning, development and testing of a software product. The logical approach introduced by this paper will help to better anticipate and identify the potential problem areas in a customer environment, help ensure that all details and aspects of the customer’s needs are covered and drive down the monetary cost resulting from the escape of defects from our development and testing phases to the end user.  

Author Profiles:

Sasha Selvandrah

Sasha Selvandrah received a BEng degree in Communications and Electronics Engineering from the University of Northumbria, Newcastle in 2001. Following 2 years as a Transmissions Engineer with Measat Broadcast Network Systems, she entered the University of Westminster, London and received an MSc in Mobile, Personal and Satellite Communications in 2004. In 2005, she joined Motorola Multimedia Software Center where she worked on various 3G feature testing. She is currently part of Motorola’s GSM Test Team.

Parameswary Namebeley

Parameswary Namebeley is currently a Software Test Engineer for GSM team in GSG Malaysia. She joined Motorola in April 2005, and worked in UMTS Subsystem Verification and Validation team for one and half year. She graduated from University Malaya, with a Bachelor of Computer Science (Majoring in Software Engineering).

Chiam Yin Kia

Chiam Yin Kia is currently a Software Test Engineer for GSM team in GSG Malaysia. She joined Motorola in November 2005, and worked in UMTS test team for 8 months. She received her Master Degree from Malaysia University of Science and Technology in November 2005. Her first degree is graduated from University of Malaya, with a Bachelor of Computer Science (Majoring in Software Engineering).

Authored by Narendra Kumar Nagaram & Ashok Pantham from Satyam Computer Services, India

Abstract:

Off the late, testing has gained an unexpected and as much importance as developments task. With this boom, it is being taken up as a separate life cycle than as a part of development cycle and, the organizations have started managing the testing projects/ testing team as separate tasks in project management. Not only within the organization but there are many organizations which provide services exclusively for testing. This demand increases competition as well as burden to maintain a process and quality for the services provided.

Nevertheless, the number of process for testing has equivalently come up. Similar to the CMMI, Six Sigma for the development process, we have TMM, TPI, TOI etc for the testing processes. Though CMMI , six sigma focus on the validation aspects, the testing process aim exclusively for the testing, The increasing focus on the usability, security, portability, performance etc of an application for disposal, testing is no more confined to just meeting the requirements. Thus, these processes help in establishing a testing process for an organization for any type of testing service. 

The very mention of “process” relates to the documentation to the developers and testers. The goal or aim in having a process is to ease the tasks than to burden in addition to the day-to-day activities. Thus, in a situation when an organization still does not have a testing process, here are few steps or practices, which aims in establishing, maintaining and improving the existing one. At a final stage, when all the involved stake holders are confident for the real “assessment” then it is easy to achieve one. This is definitely useful for the small venture organizations or for those, which have complex stakeholder hierarchy for approvals to attain one.

In this paper, we deal with understanding the basic testing activities and formulating them into different groups. The process if followed without major problems can be mapped to the process areas of the TMM and use the TPI model for improvements.  Then they can enhance to achieve the missing process areas.

Target Audience

The topic can be considered as Basic or Intermediate and is aimed for test leads/ test managers/quality analysts who are involved with the quality assurance projects. This would enable the audience to use these concepts by implementing the project in a cost effective way.

Author Profiles:

Narendra Kumar Nagaram

Has been associated for past six years and eight months with Satyam Computer Services Ltd., a SEI-CMM level 5 company, which occupies a significant position in top ten IT companies in India with fortune 500 customers as its clients.  Have experience of working in varied technologies at different phases of the software development life cycle. After completing the graduation in B.E (Computer Science) from Osmania University, had pursued a master’s degree in Software Engineering from BITS, Pilani. Participated in QAI conference during 2004 and 2006.

Ashok Pantham

Has been working for over three years with Satyam Computer Services limited, a SEI-CMM level 5 company, which occupies a significant position in top ten IT companies in India with fortune 500 customers as its clients. A CSTE certified professional with diverse experience in the Software Testing Industry. He has worked extensively in all the phases of Software Testing and on Test Automation and Frameworks.  Holds a master’s degree in computer applications and active  participant  in many of the internal conferences conducted by Satyam.

Presented and Authored By Subashini Raghavan, Intel MSC Sdn. Bhd, Cyberjaya, Malaysia

Abstract:

The key drive for software testing is capturing defects. In software development reducing defects has been substantially important. There are many approaches that can be taken to reduce the number of defects captured in testing or later phase of testing.

This paper discusses on one of the approach called defect analysis. Defect analysis defined as analyzing each defect captured and transfers the learning back to the project life cycle. The two main categories of classifying the defects for analysis are called ‘Originated in Phase’ and the other as ‘Should be detected’. Originated in phase means to identify the phase of the software development life cycle during which the defect originated. Meanwhile, should be detected means to identify the correct test phase or phases in software development life cycle during which the defect should have been captured.

This effort is to provide focus for the area of improvement within software development life cycle by developing action plan or corrective plan. This will also improve validation process in various test phases within the software development life cycle thru developing action plan to take corrective action for continuous process improvement in the overall validation process.

In summary, defect analysis helps project and test teams to keep on learning from past defects thru the action plan or corrective plan. It also helps to reduce repeating same mistakes causing defects in various similar projects. Thus this helps to reduce the testing cycle, increase product quality and achieve earlier product releases to customer.

Presenter Profile:

Subashini Raghavan of Intel MSC Sdn. Bhd, Cyberjaya, Malaysia

Subashini is a software test engineer with more than 6 years experience in IT industry. She worked as test lead and tester on small to complex manufacturing automation projects since joined Intel in 2001. She is involved in testing framework and testing life cycle definition in her organization. Currently she plays coach and mentor for new test leads in the organization.

She holds a Master Degree in Information Technology from University of Science Malaysia