Schedule Software » projects

QBit Systems is a global IT services provider offering Software Development services to businesses worldwide through its state of the art ISO 9001:2000 certified Offshore Development Center (ODC) in India. We are a Microsoft Gold Certified Partner committed to deliver top level benefits to the end users. Our integrated network of development services is bieng catering IT outsourcing requirements of major international markets such as US, UK and Australia.

(ArticlesBase SC #1120892)

Article Source: http://www.articlesbase.com/ – On the way to Offshore Software Development with novel projects

While Global Development and Delivery (GDD) benchmark has been set, there are no grades as such to measure the competitive edge of the companies in the business of offshore software development. This still remains to be something that you have to figure out from what is plated in front of you. The skill of outsourcing software development offshore is not something that you would hit in one go. It is something that you have to acquire sip by sip as you go. What becomes even more daunting here is going offshore with “first of its kind” projects. Although it seems to be a horror but if done in a right way it can turn out to be a blessing for small budget star-ups. Below are three tips to manage offshore software development of novel projects.

Keep development go programming:

Fresh projects are a work of creativity and surely require tight grip management from in-house. The best thing to do in this case is outsource the coding part only rather then the whole development. Once the design, layout and wireframes are ready outsourcing coding becomes easy for offshore team. The best model to adopt here is onsite and offshore model with the lead team onsite. The onsite lead team should be completely held responsible for handling project management, knowledge transfer and quality assurance.

Well defined work units and procedures:

Well documented work modules and direction all through the development stage is very essential for new projects given offshore for development. Written specification should be well defined into work phases and work cycle as a whole. Formal task decomposition should be done to break the project into manageable chunks. Just remember it is not important that your offshore software development team understands your novel idea but it is should be able to comprehend and execute the coding.

Constant Monitoring:

It is very important to run scheduled consistency checks to verify whether the work is being done in accordance to the formal specification document. Some companies also use web based softwares that track modification and communication requests to trigger management intervention when a project schedule slips. It is also helpful in ruling out the further demand for the know-how and communication. Furthermore monitoring also saves one from the pain of back tracking.

As a conclusion while going for offshore software development of new project following are the things you should keep yourself responsible for:

Defining specifications Design to shape basic structure Documentation Formalizing deadlines, procedures and policies Ensuring and testing whether the code meets requirements

Retrieved from “http://www.articlesbase.com/software-articles/on-the-way-to-offshore-software-development-with-novel-projects-1120892.html”

(ArticlesBase SC #1120892)

Vikas Gupta -
About the Author:

]]>

Rate this Article

1
2
3
4
5

vote(s)
0 vote(s)

Feedback
RSS
Print
Email
Re-Publish

Source: http://www.articlesbase.com/software-articles/on-the-way-to-offshore-software-development-with-novel-projects-1120892.html

Article Tags:
offshore software development, offshore software outsourcing, offshore software development india

Latest Software Articles
More from Vikas Gupta

Outsourcing Dot Net Development

DotNet web application development is the innovatory software platform for enabling developers to develop dynamic .Net applications that has been created to interact to associate with businesses, clients, staffs, and partners in a single loop, using the web services.

By:
Offshore Web Developerl

Internet>
Web Designl
Oct 20, 2010

Hire PHP developers, get the outsourcing benefits

In today’s scenario offshore outsourcing has got the tremendous popular management strategy in India. Apart from cost saving facility, long term competitive advantage with value addition while comparing with output and excellence there is now no substitute for offshore outsourcing!
International companies are now hiring dedicated PHP developers from professional offshore IT
service providers.

By:
Sujoy Chakravartyl

Business>
Outsourcingl
Nov 24, 2009
lComments: 1

Importance of Outsourcing Web Application Development

Outsourcing web application development provides customer the assistance in developing and maintaining enterprise solutions and software applications through most of the web programming languages and technologies at an affordable rates and time.

By:
Offshore Web Developerl

Computers>
Softwarel
Oct 18, 2010

Outsourcing Web Application Development to Affect Enhanced E–Commerce Development

Outsourcing web application development provides an improved corporate image and a customized web application development for creating absolute and effective solutions at an affordable rate.

By:
Offshore Web Developerl

Internet>
Web Designl
Oct 20, 2010

Uncovering the Soft Costs of Outsourcing Offshore

In any offshore outsourcing engagement, besides the direct contract cost, additional ‘soft costs’ are incurred before, during and after the offshore transition. If not factored in at the beginning, these can undermine the success of the engagement. This article analyzes these soft costs that, along with the actual project cost, constitute a project’s Total Cost of Offshoring (TCO). It also highlights some reasons for failure of offshoring engagements and suggests ways to overcome them.

By:
Biplab Sahal

Business>
Outsourcingl
Aug 28, 2009
lViews: 275

Software outsourcing and product development

India’s software outsourcing sector is booming and increasing very fast. Banglore is now world famous as a offshore software hub. Same way, Indian BPO market is also booming.

By:
Rakesh Patell

Computers>
Softwarel
May 03, 2006
lViews: 534

Outsource Autocad Drafting to India at affordable prices

Outsourcing autocad drafting services to India is always a viable option, as you get quality architectural services at affordable prices. We offer various architectural services throughout India.

By:
RaghuavendraCOl
Businessl
Apr 21, 2009
lViews: 377

Beneficial .Net Web Development through Hiring Expert ASP.Net Developers Offshore

The article describes the benefits of leveraging .Net web technology for web development and why ASP.Net programmers and developers offshore stand an ideal choice for .Net web development.

By:
Josh Johnl

Internet>
Internet Marketingl
Sep 11, 2010

Simple Machines Forum

This is an extremely powerful and easy-to-use forum, probably one of the more robust systems I’ve come across. Considering the price — FREE — you can’t beat it.

By:
Aaron Webberl

Computers>
Softwarel
Nov 09, 2010

Document Version Control: How Best To Use In Your Business

No matter your business, things may well become a little bit complex anytime you are hoping to keep up with all the diverse restrictions and requirements. If you are a tiny company or perhaps a massive one, you however have the equivalent restrictions to keep up with, and odds are you do not really have the work force numbers to keep up with anything on your dish. If this relates to your existing condition, then look at employing corrective action software to simplify issues.

By:
Olivia Petersonl

Computers>
Softwarel
Nov 09, 2010

Dynamics GP in Supply Chain Management: WMS, Delivery Route Optimization

Microsoft Dynamics GP is very popular and wide spread mid-market Corporate ERP platform, sometimes referred by its historical name Great Plains Dynamics.

By:
Andrew Karasevl

Computers>
Softwarel
Nov 09, 2010

Illusion Mage Software – The 3D Suite That Doesn’t Burn a Hole in Your Pocket

A quick look at Illusion Mage and how it can help you

By:
Davidl

Computers>
Softwarel
Nov 09, 2010

How To Easily Fix The Dwwin.exe Error – How To Guide

If you keep on having a Dwwin.exe error coming up when you’re using your computer, then this article will give you a heads up as to how you can get through it and stop it from happening. It’s a pretty easy error to fix as it’s really common, so that means that there is a lot of support online.

By:
John Mackyl

Computers>
Softwarel
Nov 09, 2010

How To Easily Fix The Bootmgr Image Is corrupt Error – How To Guide

Are you receiving a Bootmgr image is corrupt error that keeps on plaguing your computer? If this error is common to you then here’s an article that should help you out below. It’s a great little snippet that explains why it happens and how you can fix it easily. Let’s get into it below.

By:
John Mackyl

Computers>
Softwarel
Nov 09, 2010

Did The Windows Update Fail? Here’s How To Automatically Fix The Windows Update Fails Problem

If Windows Update Fails a lot when you are trying to update it then this article will give you some help into how you can fix the problem that is causing it to not work and get your computer updated. Updating your computer is very, very important and you shouldn’t let a program prevent it from happening. Let’s get into it and find out how you can get rid of this problem.

By:
John Mackyl

Computers>
Softwarel
Nov 09, 2010

How To Easily Fix The Dr.Watson Error – How To Guide

Are you running into the Dr.Watson error that is just killing your computer? This article will show you exactly how to get rid of it. Your computer can easily be fixed because this error is so common – it has come to that attention of a lot of developers and easy fixes are currently available for all of us. Let’s get into the article below and find out what causes the error as well as how to fix it.

By:
John Mackyl

Computers>
Softwarel
Nov 09, 2010

Challenges of Offshore Software Development

The upturn of offshore software development has been such an outré that the term is used nearly synonymous with outsourcing. What’s really missing is an insight on the key challenges outlining the big gains of offshore software development Dismissing these challenges by not giving enough thoughts at initial stages is main cause of the most missed deadlines, budget leaps, and fading away of trust and goodwill in relationships.

By:
Vikas Guptal

Computers>
Softwarel
Aug 20, 2009
lViews: 183
lComments: 1

On the way to Offshore Software Development with novel projects

By:
Vikas Guptal

Computers>
Softwarel
Aug 12, 2009

Add new Comment

Your Name: *

Your Email:

Comment Body: *

Verification code:*

* Required fields

Submit

Your Articles Here
It’s Free and easy

Author Navigation

My Home
Publish Article
View/Edit Articles
View/Edit Q&A
Edit your Account
Manage Authors
Statistics Page
Personal RSS Builder

My Home
Edit your Account
Update Profile
View/Edit Q&A
Publish Article
Author Box

Vikas Gupta has 2 articles online

Articles Categories
All Categories

Advertising
Arts & Entertainment
Automotive
Beauty
Business
Careers
Computers
Education
Finance
Food and Beverage
Health
Hobbies
Home and Family
Home Improvement
Internet
Judaism
Law
Marketing
News and Society
Relationships
Self Improvement
Shopping
Spirituality
Sports and Fitness
Technology
Travel
Writing

Computers

Computer Forensics
Computer Games
Data Recovery
Databases
E-Learning
File Types
Hardware
Information Technology
Intra-net
Laptops
Networks
Operating Systems
Programming
Security
Software

]]>

Need Help?
Contact Us
FAQ
Submit Articles
Editorial Guidelines
Blog

Site Links
Recent Articles
Top Authors
Top Articles
Find Articles
Site Map

Webmasters
RSS Builder
RSS
Link to Us

Business Info
Advertising

Use of this web site constitutes acceptance of the Terms Of Use and Privacy Policy | User published content is licensed under a Creative Commons License.
Copyright © 2005-2010 Free Articles by ArticlesBase.com, All rights reserved.

Six Sigma Training For Software Implementation Projects

Mon, 06 Sep 2010 10:23:55 +0000

The application of Six Sigma in software development projects is well known, but the utility of Six Sigma for software implementation projects is also worth a mention.

Software implementation projects commonly have the recurring problem of going off-track with regard to target implementation dates, as well as other problems. This is the point where Six Sigma concepts can play a critical role.

Common Issues in Software Implementation Projects

As mentioned earlier, the problems that software development teams often face are in understanding customer requirements and adhering to the project schedule estimation.

By using Six Sigma, software professionals will be in a better position to understand the needs of the client, as well as complete the implementation in the stipulated time period.

Software projects are started with the aim of achieving efficiency in various systems, with the desired outcomes represented qualitatively as well as quantitatively. Most of the problems that occur during implementation are an outcome of the realization by the team that they have lost sight of the desired objectives of the customer.

This may be because the client has provided varied input, or because the developers have misunderstood the requirements.

Six Sigma helps sort out this problem. Six Sigma is not just about statistical methods, but a disciplined approach to problem solving. The y to- x trees and cause and effect matrix tools help to identify the software system capability and the business outcome.

-Creating Fact-Based Selection And Prioritization Of Functionality

Six Sigma provides various tools that facilitate prioritization, such as analytical hierarchy process (AHP). These tools can be effective tools for determining utility and providing for the prioritization and decision making process.

DFSS provides for more quantitative, fact-based discussion and decision-making on the CTQs.

-Generating implementation schedule estimates

The software implementation team often goes off-schedule. Software projects have to be completed within a specified time span and budget. Planners often fail to estimate the various matters, such as the size of the software, its location and other surrounding matters.

Six Sigma analytical tools help in factors like the efficiency chart, which can help find the problems faced by each team and its members. This chart may be able to display the time taken to resolve such problems and the systems used to overcome them.

If the Six Sigma teams do not estimate the size of the project, they are bound to make errors in estimating the time it will take to complete, as well as the cost. Six Sigma allows for understanding the characteristics of organizations, such as the number of members, users, locations and the amount of executive involvement. This helps in making implementation estimates more accurate to a larger extent.

Sometimes executives make unreasonably early estimates of implementation dates without considering the realities. Six Sigma modeling helps in changing this scenario to a fact-based estimation of the project to be implemented.

Six Sigma is more about fact-based decision making. By using actual facts, the implementation of software projects becomes more realistic.

Tony Jacowski is a quality analyst for The MBA Journal. Aveta Solution’s Six Sigma Online offers online six sigma training and certification classes for six sigma professionals including, lean six sigma, black belts, green belts, and yellow belts.

Software Implementation Projects And Six Sigma

Mon, 12 Jul 2010 00:16:56 +0000

Six Sigma concepts were originally developed for use in the manufacturing sector, but are now increasingly being used in the services sector as well. Use of Six Sigma concepts in the software industry has become quite common, but what many people do not know is that Six Sigma concepts can also be used in software implementation. People who have experience in software implementation projects know that such projects often do not take off as planned and may be subjected to schedule overruns and recurring problems. This is why many software companies opt for employing Six Sigma concepts during the process of software implementation at a client’s site.

Common Implementation Problems

The two most common problems faced during software implementation projects include customer requirement problems and schedule estimation problems. By employing Six Sigma concepts in software implementation projects, professionals can better understand the needs and business objectives of the client. This way, they can make sure that the software implementation project is successfully completed within the stipulated timeframe. Employing Six Sigma will also ensure that no additional costs are incurred during the implementation process.

Understanding Client Requirements

Software products are normally designed for increasing the efficiency of a business process in accordance with the goals and objectives of the client. Most of the problems related to the software arise during the implementation stage when the client finds out that the software is unable to achieve desired objectives. This situation arises when the client passes vague information about requirements to software developers or when developers are unable to clearly comprehend client requirements.

Six Sigma helps in avoiding problems during the software implementation stage by bridging the gap between actual requirements of the client and what is eventually understood by software developers. Many people believe that Six Sigma is only limited to the use of statistical methods. What they do not know is that Six Sigma follows a disciplined approach that can solve any type of problem, whether it is quantitative or qualitative. This is evident from software companies that have successfully employed Six Sigma concepts in solving qualitative problems that arise during software implementation projects.

Generating Schedule Estimates

Schedule estimation is another common problem faced during software implementation. Mistakes in schedule estimation can affect the outcome of an implementation project; as such projects are often required to be completed in a specific timeframe and within available budgets. Implementation projects are often delayed because planners make the implementation schedule without considering indirect factors that might affect the project. Planners often fail to foresee that implementation can get affected due to the size of the software, location where it is being implemented, internal politics, authority, and governance.

Employing Six Sigma concepts in preparing schedule estimations will help planners to effectively include all these factors which may indirectly affect software implementation projects. Based on the past records of the client, Six Sigma statistical tools will generate an efficiency chart, which provides details about all types of problems faced with the client during software implementation projects. The chart displays the time taken to resolve such problems and techniques that were employed to solve such problems.

The chart also displays any additional time or costs that went into the completion of the project. Planners can use the information given in the chart for giving due consideration to all the indirect factors that can affect software implementations. This will help in generating true schedule estimates, necessary for the success of software implementation projects.

Tony Jacowski is a quality analyst for The MBA Journal. Aveta Solution’s Six Sigma Online offers online six sigma training and certification classes for lean six sigma, black belts, green belts, and yellow belts.

Do all successful safety-critical computerization projects have Level 4 automated testing ?

Fri, 04 Jun 2010 10:44:14 +0000

This level has been designated Accidental Automation because the use of any automated tools or techniques comes about almost as if by accident and is not supported by process, planning, or management functions. Products released on the basis of such testing may well be accidents waiting to happen. Testing at this level may be appropriate only for a product that has no potential for harming the patient or user; it is never appropriate for a computerized medical device.

Level 2: Beginning Automation. The second testing level corresponds directly to Level 2Repeatable in the software process maturity model (see Figure 2). There are hundreds of capture-and-replay test tools on the market today that simply repeat the responses of a system under test.5 As in the process model, however, these tools have limited capabilities and lose their economic usefulness quickly as a product changes.

Level 2 testing is still dependent on information locked in the minds of in-house experts, although documentation is beginning to appear in the form of software requirements specifications (SRSs) and test requirements specifications (TRSs). However, in most cases, large portions of these documents are written after the fact and used to meet regulatory requirements rather than to direct the development and test processes. Writing them does, however, provide good practice for moving to level 3.

Level 3: Intentional Automation. At the third level, automated testing becomes both well defined and well managed. The TRSs and the test scripts themselves proceed logically from the SRSs and design documents. Furthermore, because the test team is now part of the development process, these documents are written before the product is delivered for testing. Consequently, schedules become more reliable. Level 3 is appropriate for many medical device manufacturers.

Do all successful safety-critical computerization projects have automated testing ?

Wed, 02 Jun 2010 09:42:02 +0000

Have there been projects where information that should have been available was covered up ?

Mon, 31 May 2010 08:27:20 +0000

The following information on automated testing was published in December 1994. Have there been projects where this or similar information should have been available, but was unaccountably kept hidden ?

(Originally published December 1994
SOFTWARE
A Maturity Model for Automated Software Testing
Mitchel H. Krause)
<

New technology promises to streamline complex projects

Wed, 26 May 2010 08:03:10 +0000

New technology promises to streamline complex projects
Software which could save operators thousands of pounds a day during complex oil and gas projects has been launched by an energy services company in Aberdeen …

How do you manage/organize the many “to-do’s”, projects and events for the growth of a company, your boss’…?

Thu, 13 May 2010 22:29:07 +0000

schedule (and his “to-do’s”) and your own personal life (i.e. payment schedules, phone calls, events, etc.) This is my first year in management and I’ve done “ok” thus far. With the growth of the company, more and more challenges arise. I need to be ale to keep on top of every task and not “drop the ball” is there some special software you use to keep it all in line. Paper and pencil aren’t cutting it any longer, I find it difficult to follow through in Outlook as it really doesn’t have a good way of looking at everything in one big picture. (I hope you understand what I mean by this)

Your opinions are valued. Thank you for your time.
For the love of God…anyone?

Was there “tortious interference” on any software projects in 1994-1995 ?

Wed, 24 Mar 2010 02:35:56 +0000

Something stopped the following from happening in some projects in 1994-1995.
What might that have been ?

Originally published December 1994

SOFTWARE
A Maturity Model for Automated Software Testing
Mitchel H. Krause

Aside from their mandate to provide a safe and reliable product, manufacturers of computerized medical devices may have three very practical reasons for automating their software testing program: their product is too complicated to test manually, the time devoted to manual testing is cutting into potential profits, and current FDA requirements will be easier to satisfy with automated testing and documentation. If any of these factors motivates your company, this article will help you to sort out the issues to be considered and options available. Then, when the automated test program is in place, safer and more reliable products will follow.1 The sorting instrument presented is a maturity model that plots four levels of testing maturity in terms of the resources required to move from one level to the next. The model can be used to determine the level that best fits your company and its products.

THE SOFTWARE TESTING MATURITY MODEL

The software testing maturity model, shown in Figure 1, is similar to a software process maturity model that is familiar to many software engineers. It has been described by Watts S. Humphrey in his book Managing the Software Process,2 and has been cited by Frank Houston, a former FDA staffer, and Steven Rakitin in presentations to the Health Industry Manufacturers Association.3,4 The version shown here as Figure 2 is adapted from Rakitin's presentation. The process model adapts well to automated software testing because effective software verification and validation programs grow out of development programs that are well planned, executed, managed, and monitored. A good software test program cannot stand alone; it must be an integral part of the software development process.

Level 1: Accidental Automation. The first level of the software testing model--like level 1 in the software process model-- is characterized by ad hoc, individualistic, chaotic attempts to get the job done. Important information (for example, what to test) is not documented and must be extracted from in-house experts. Test plans are sketchy. Test results are not documented consistently. Schedules slip. Either products are delayed or testing becomes a cursory, poorly documented exercise. Management is uninvolved or uninformed.

Level 4: Advanced Automation. The highest testing maturity level is a practiced and perfected version of level 3 with one major addition: postrelease defect tracking. Defects are trapped and sent directly back through the fix, test creation, and regression test processes. The software test team is now an integral part of product development, and testers and developers work together to build a product that will meet test requirements. Any software bugs that do occur are caught early, when they are much less expensive to fix. When testing i
. When testing is performed at this level, an FDA inspector can pick up any piece of product documentation and trace the development process all the way from the SRS that describes the feature to the test results that validate it.
A Checklist of Issues. How can these software testing maturity levels help a company to plan and implement an automated software test program? The answer to that question comes from careful consideration of four issues:
* What is the profile of your company and its products?
* What processes do you need to implement as part of an automated testing program?
* What kind of people do you need in order to create and run a testing program?
* Which automated software test products fit your profile and process?
Significantly, price is not on the list. That is because the cost of any one component, especially the test tool, becomes insignificant when it is compared with the potential payback. A well-planned and well-executed software test automation
process will pay for itself many times over by ensuring fewer bugs and field fixes, shortening product development cycles, and providing labor savings. And, if you keep your ultimate goal in mind when defining processes, choosing staff, and buying test tools, your testing program will continue to yield a good return as you advance from one level of maturity to the next.
PROFILE: RANKING YOUR COMPANY'S PRODUCTS
Most computerized medical devices can benefit from some type of automated testing. In fact, Boris Beizer, who is probably the most well known expert in the field of software testing, has said, "As far as I'm concerned, manual testing is ludicrous and self-contradictory. It's based upon a fallacy. Anybody who thinks they can test manually, doesn't take into account the error rate in manual test execution."5 However, knowing what level of automation is appropriate requires a good understanding of your company's products.
The exercise described below will help you to create a
test-level profile of your company and its products. The profile is a guide to how your company may benefit from an investment in processes, people, and automated software test products. The point scores at the end of each section provide a rough estimate of the level of software testing maturity you should strive to meet.
How Large Are Your Software Projects? As software projects increase in size, the resulting products become harder to test and at some point manual testing can no longer cover enough functionalities to ensure safe and reliable products. There are many ways to measure the scope of a software project, but a simple line count is a start:
* Score 1 if your product has fewer than 10,000 lines of code.
* Score 2 if your product has between 10,000 and 30,000 lines of code.
* Score 3 if your product has between 30,000 and 70,000 lines of code.
* Score 4 if your product has more than 70,000 lines of code.
How Complex Is Your Product? Systems with multiple inputs
and outputs, graphics screens or printers, embedded processors, or multiple microprocessors are all candidates for the controlled sophistication of automated testing. If two or more interactive processors are used, the product probably presents integration and timing issues that cannot be tested manually. Similarly, if the product has an embedded processor, it may have functionalities that cannot be tested manually. In other cases, it may simply be impractical to test the system manually. Printers are one example of a common peripheral that is hard to test by hand. They not only accept commands and data from a software system, they also send back status and error signals to which the system must respond correctly. It is slow, inconvenient, and sometimes impossible for a tester to follow test plans that try to duplicate all the combinations of acknowledgment, system-busy, paper-out, baud rate, error, select, sensor, and other signals the printer might return. The input simulation
provided by a sophisticated automatic test system can both speed up this process and make it traceable and reproducible.
Even testing of that seemingly ubiquitous input device, a keyboard or keypad, can benefit from using an automated test tool with simulation capabilities. Timing issues, especially, are nearly impossible to test manually. The fatal accidents in the mid 1980s that involved a radiation therapy machine are a good example of the kinds of problems that can occur. This particular machine had both therapy and diagnosis modes, and operators entered a series of keystrokes to switch the system from a high-energy to a low- energy mode. If the keystrokes were typed in too fast, however, the high-energy mode would remain in effect even though the operator would assume the change had been made. Later, when the system was activated, it sent a damaging and sometimes lethal dose of radiation into the patient.6 An automated test tool with simulation capabilities could have detected
this problem early, before any harm was done. Keyboard simulations could have been set up to test the effect of varying keyboard input speeds. (The actual resolution of the problem involved many factors in addition to keyboard input speed; the report cited gives a full account of these accidents and their outcome.)
System outputs may also be tested more efficiently using automated methods. After an 8-, 10-, or 12-hour day, even the most conscientious human tester will fail to notice some errors or forget to document them. Other outputs either cannot be monitored manually or the testing may require nonintegrated measurement devices that may be difficult to set up and monitor. Finally, some potentially fatal software flaws may never show up during functional (black-box) testing. Detecting these problems requires an automated system that can use white-box test methods to look inside the system.1
* Score 1 if your product has a single processor and simple inputs and outputs.
* Score 2 if a malfunction or failure of your product presents a small but acceptable risk to the financial health of your company.
* Score 3 if a malfunction or failure of your product presents an unacceptable risk to the financial health of your company.
* Score 4 if a malfunction or failure of your product would cause irreparable harm to your company.
What Risk Does Your Product Pose for the Patient and Operator? Although concerns about size, complexity, and financial risk are important in all software projects, the bottom line for a medical device company is risk to patients and health-care providers. Medical products must be both safe and effective. That is, they must do what they are designed to do and, when something does go wrong, the malfunction or failure must cause no harm. The product's FDA classification and hazard analysis results may determine if automated testing should be implemented. If a computerized medical device is categorized as Class II or Class III,
an automated software test program may be necessary to provide both the testing and documentation required. Similarly, if the product presents software-related hazards, an automated test program might help your company to verify, validate, and document the measures taken to mitigate those hazards.
* Score 1 if your product is FDA Class I and a hazard analysis has shown there is no possibility of its software causing harm to a patient or operator.
* Score 2 if your product is FDA Class I and a hazard analysis has shown there is a remote possibility of its software causing harm to a patient or operator.
* Score 3 if your product is FDA Class II.
* Score 4 if your product is FDA Class III.
Evaluating Your Scores. In its "Reviewer Guidance for Computer-Controlled Medical Devices," FDA supplies an approach to evaluating the scores assigned in this exercise: "When a level of concern is assigned for each functioning component of the software, the highest level of concern generated
is that assigned to the software aspect of the device."7 Thus, if you want to ensure the long-term success of your company, aim for the level of automated software testing equal to your highest score in any category.
PROCESS: CONTROLLING TEST POLICIES AND PROCEDURES
If any one word sums up the regulatory demands being placed on medical device manufacturers, it is process. No matter how much effort goes into designing, testing, and manufacturing a product, an auditor will not be satisfied if the process is not written down, followed, and documented. Process-related expenses will be incurred regardless of the testing level achieved or whether or not the software test process is automated; however, they can vary significantly across the testing levels.
Level 1 Process Costs. When software testing is at level 1, process costs are hidden. They arise from not having a defined process and can be very high, indeed. Such costs can include those incurred by delayed product introductions,
the need for frequent field fixes, and a generally ineffective product development effort.
Level 2 Process Costs. Surprisingly, process costs can be highest for a company that is testing at level 2, especially one that is contemplating a move to level 3 in the foreseeable future. The costs are high because at level 2 the company is probably just starting to evaluate its software testing needs and to put standardized procedures in place. It may have to experiment, hire consultants, and establish or expand job areas, such as regulatory affairs.
Process Costs at Levels 3 and 4. Although the two major forces behind process improvement--FDA regulation and the need for ISO 9000 certification--may affect any company, those testing at levels 3 or 4 almost certainly need to meet FDA software test requirements. Such compliance is expensive and time-consuming, but the good news is that creating and documenting procedures for an automated testing program is no more expensive than doing so for
a manual one. In fact, use of an automated test tool with scripting, test identification, and automatic documentation capabilities can reduce costs by providing some of the framework and content required.
The FDA "Reviewer Guidance for Computer-Controlled Medical Devices Undergoing 510(k) Review" states that "FDA is focusing attention on the software development process to assure that potential hazardous failures have been addressed, effective performance has been defined, and means of verifying both safe and effective performance have been planned, carried out, and properly reviewed."8 In order to get marketing approval for any product, its manufacturer must prove to FDA that the product does what it is supposed to do and that it is safe. The way to do that is not only through clinical trials but also by documenting the process that was followed to make the product eligible for such trials.
In contrast, ISO 9000 certification is based on process alone. Because the products
themselves are not certified, the certification authority is concerned solely with whether the process that created the product is traceable, repeatable, and documented. When the process is proven, the site responsible for making the product is certified. An ISO 9000 certification audit costs about $10,000 to $20,000, but that is only the barest tip of the iceberg. The total cost includes the resources required to evaluate the company's needs, get the appropriate procedures in place, have them audited and approved, and motivate personnel to use them.
If established procedures are being revised to accommodate automation, existing regulatory affairs and quality assurance personnel may need to devote two to four weeks each to the project. In addition, it may take a technical writer about a month to rewrite the policy and procedure manuals. Finally, occasional technical support will be required from software developers and test engineers.
PEOPLE: CHOOSING QUALIFIED TESTERS
No matter what type of testing a company does, manual or automated, experienced people are needed to create the test plans and write test scripts.
Level 1 People Costs. At test maturity level 1, testing is often limited to debugging. A programmer writes and debugs the product's software until everything seems to work correctly. Because only the programmer is involved, testing costs are hidden in the cost of development. Likewise, the potential benefits of better test practices are hidden in field-support and product- upgrade costs. Thus, level 1 people costs are essentially unknown.
Level 2 People Costs. In software testing programs at level 2, testing is recognized as a separate function. Test plans and scripts are generally written by an experienced product user or support person who may or may not have programming experience. In any case, the person performing this task must understand the SRSs and design specifications well enough to write a comprehensive test plan and test
scripts. The scripts are then given to testers who run them and record the results. One option is to hire a group of low-paid, inexperienced users; another is to recruit testers in-house. Whoever the testers are, they must understand that their job is to try to break the system as well as to make sure it works right. Level 2 people costs may also include one or more high-level support people to coordinate test writing, supervise the testers, and edit the results. Also, since the labor that goes into setting up a capture-and-replay tool is not reusable, the cost of one test cycle must be multiplied by the number of test cycles expected.
People Costs at Levels 3 and 4. Automated testing plans are most often written by a software test engineer, who should also participate in product development meetings with design engineers to help build testability into the product. The test engineer's programming background combined with a familiarity with the product will ensure the creation of
efficient tests that attack the weakest parts of the product. If the test tool has white-box test capabilities, the test engineer uses his or her knowledge of system internals to specify tests for functions that cannot be tested manually.
The test plan is then used to write the test script programs. This work can be done by the test engineer or given to application programmers. The level of programming experience required to write test scripts depends on the test tool used. Generally, the most versatile tools run on scripts written in some version of a common programming language, such as C. Other tools use simplified languages. In any case, at least one member of the test team must have some familiarity with writing a structured set of instructions. Because the automated testing tool runs the tests and creates the documentation, no costs are added for hiring testers or diverting in-house personnel to perform and document the tests.
PRODUCTS: CHOOSING THE RIGHT TESTING TOOL
The requirements of the product and process determine the selection of an automated testing tool. However, medical device manufacturers should beware of confusing development aids with automated software test tools. Companies can spend large sums on many kinds of debugging tools and in-circuit emulators and still not have an automated test program. A software development aid has done its job when the product, or product component, is debugged and seems to work. Automated test tools, on the other hand, are designed not only to verify the system, but also to stress it to the point that it will break in the lab before it can fail in the field and harm a patient or operator.
Level 1 Tool Costs. Although development aids such as debugging programs and in-circuit emulators may be used in level 1 test programs, no automated test tools are used. Therefore, there are no tool costs at this level.
Level 2 Tool Costs. Level 2 testing is the domain of simple capture-and-replay tools that employ
rudimentary scripting capabilities and are often used to verify operator interfaces. Prices for such tools start at about $200 and can reach $5000 or more for the more-sophisticated models. The less-expensive, software-only versions are often intrusive; that is, they run on the same computer as the software application being tested. Because the tool and product occupy the same space, product timing and performance can undergo unpredictable changes. Even if no problems show up during testing, the product shipped is never exactly the same as the product tested. Capture-and-replay tools with integral capture hardware eliminate the problems associated with intrusiveness but retain another problem characteristic of such systems--inflexibility.
Because a capture-and-replay test suite for a graphic user interface (GUI) can contain thousands of captured screen images and consume megabytes of memory, the time it takes to gather these images is significant. Timing variations and the fact that
GUI displays are seldom static can add even more time. Most significant, however, is the amount of time needed to recapture, integrate, and retest the inevitable changes caused by debugging and last-minute product upgrades. Thus, capture-and-replay tools should be used only for the simplest of products.
Tool Costs at Levels 3 and 4. High-level test tools can include several advanced capabilities in addition to capture and replay. The following are features to look for when purchasing tools:
* Scripting. The tool's test script language should be as functional as a high-level computer language, permitting the inclusion of files, libraries, loops, and conditional statements. It also should include aids to help debug the scripts themselves.
* Monitoring. A choice of intrusive software monitoring, such as that used in capture- and-replay tools, or nonintrusive hardware monitoring of system outputs may be available. An added high-level feature in the most sophisticated systems is
direct-processor monitoring. With direct-processor monitoring, a connector similar to an in-circuit emulator pod is mounted on the processor and monitors the activity of the product under test. The test tool is nonintrusive because the connector never sends signals to the application being tested. It is also quite fast and accurate because it works at the processor level.
* Black-Box Simulation and Stimulation. A high-level tool should be able to emulate the actions of a human tester. Hardware is available that can simulate such product stimulations as keys being pressed, printers responding, tones being generated, relays opening and closing, and other analog or digital inputs. In short, advanced simulation capabilities should enable tests to run unattended.
* White-Box Simulation and Stimulation. The test tool should also be able to simulate and monitor the internal workings of the product tested. Such white-box testing capabilities permit testing of timing, integration, and
and resource issues that cannot be tested manually.
* Documentation. Automated test tools can log both test parameters and test results. If integrated into the software development process, a sophisticated system should be able to produce much of the documentation required by regulatory agencies.
Test tools suitable for testing at levels 3 and 4 cost from $15,000 to $75,000.
CONCLUSION
As described above, once you determine your company profile, perfect your processes, establish test specialists, and give the team members appropriate testing tools, your company can realize the benefits of automated software testing. When compared with manual programs, automation properly applied will result in higher-quality products, lower risks to your company and the patients you serve, faster regulatory approvals, and decreased time to market. The higher level you reach on the automated software testing maturity model, the more benefits you will realize. Whatever level you choose,
however, keep in mind a major lesson of the last 30 years of computing: No matter what tools you buy, your largest investment by far will be in the processes and people you put in place to use those tools. Purchase automated software testing tools based on how they can maximize your investments in processes and people, not on the price of the tools themselves.>>
(for author’s references – see author’s original paper)

Web Project Management Software Keeps Team And Projects On Schedule

Thu, 18 Mar 2010 14:21:35 +0000

The objective of the Web project management software is to support your company team collaboration, stay on the track, keeps your projects budget within limit and effectively completes your projects in a scheduled time. Online project management system helps you deal with all the complex projects of your business without interruptions from uncertain roles, communication gap, complicated tasks and lack of responsibility.

Web Project Management Software and collaboration software provides many services. Let us discuss some of the popular services provided by them.

Team collaboration: Forget about office conference rooms and late night meetings. No need to travel to different locations for discussions and demos. Your team as well as clients can collaborate online by accessing them through net. It helps in saving valuable time and keeps your team as well as clients update about latest information.

Flexibility: Web project management software provides flexibility to company projects. Online Project software provides updated dashboards for quickly viewing the summary of latest happening regarding projects. Online collaboration software keeps everyone in your team on the same page for latest information of your projects, making sure each group or resource knows what others are doing. This lets project managers assign tasks, to-do lists monitor progress, schedule deadlines, achieves milestones and much more.

Accountability: Web based collaboration software increases personal and financial accountability that guide toward projects success. Most of the online projects managing system provide graphs, feedback, time sheets, milestones and task assignment. The top also monitors projects costing, check expenses, regulates resources and give estimates about future projects expenditure.

Organize Resources in Better Way: Successful resource management is equal being flexible. Project managing system manages all resources-employees, talents, budget and time. Sometimes knowing your team potential and successfully implementing their skills can make the difference between failure and success. Rightful resource management will let you build flourishing team.

World-Wide Communication: Web based project management software lets team members collaborate directly with clients from any location of the world. Online collaboration software has remote applications to smart-phones, and even manages global schedules; regardless of the time zone and physical boundaries, projects are completed on time.

I have listed few advantages of using Web Project Management Software and collaboration software. List is endless of course. What your perception about web project management software? Do discuss with me

With ProofHub web project management software and collaboration software you can manage multiple projects with ease and collaborate with team as well as clients world wide.