Search

White Papers from Foliage are your source for information on the latest technology developments that affect the medical industry.

Published: Jun 28, 2006
Author: Tim Bowe, Co-CEO; Norm Delisle, Engineering Vice President; Hoyt Lougee, Engineering Manager

Leading companies in the medical industry have a long history of using mergers and acquisitions as an alternative method of advancing their product offerings. The acquisition strategy has been used as an alternative to already large R&D budgets, and as a bulwark against the increasingly long product development cycles under which many companies function. This paper examines the factors that are critical in aligning business and technology strategies to extract the most market leverage and top-line growth from combined or restructured product lines.

Published: Feb 16, 2006
Author: Karl Aeder, Principal Software Engineer

Many of today’s embedded device control systems require some amount of deterministic software device control. Real-time deterministic control software poses unique technical challenges. By employing proven software architectural approaches, real-time software development project risks can be reduced significantly. In addition, through these approaches organizations can realize significant reductions in time to market and engineering costs across the initial development, enhancement, and maintenance of the software over its lifetime.

Published: Feb 07, 2006
Author: Tim Bosch, Chief Architect, Medical Division

This white paper defines “integration” and “interoperability”, and presents best approaches to each based on real world experience. These practical steps will help you meet expectations and successfully achieve the integration and interoperability that you desire.

Published: Sep 15, 2005
Author: Timothy Bosch, Technical Director; Timothy Bowe, Co-CEO

This new white paper from Foliage discusses the important assessment steps that any medical company should take before investing in a next generation software product development effort. This paper describes a very low investment, high return method to evaluate your existing software-based product where the end result is guaranteed alignment of your business, product and technology goals.

Published: Apr 27, 2005
Author: George Iglesias, Principal Software Engineer; Tim Bosch, Technical Director; Timothy Bowe, Co-CEO

All too often, the ‘sellability’ features of a product get stripped away during the product development stages of requirements and architecture development. Trade-offs are made that may improve configurability and functionability, or shorten schedules, but unwittingly at the cost of usability. This Foliage white paper describes the methods and importance to preserving the intent of meeting your end user needs.

Published: Oct 13, 2004
Author: Timothy Bosch, Technical Director, Medical Division, Tim Bowe, Co-CEO, George Plourde, Engineering Director, Medical Division

You can gain control of your software budget, schedule, and quality from definition through verification in a way that will help ensure customer acceptance and a prosperous product life by embracing four critical strategies: Align Business and Technology Goals; Manage Requirements; Formulate an Effective Architecture; and Drive Successful Development.

Published: May 25, 2004
Author: Timothy Bosch, Technical Director, Medical Division, John Cadigan, General Manager, Medical Division

This paper discusses the importance of evaluating system architectures at the earliest stage of system definition, using quantifiable assessments of system suitability and value to guide and inform business decisions. We present a case study to highlight and explore how these assessment techniques are applied to a real world medical product.

Published: Feb 09, 2004
Author: Tim Bowe, Co-CEO, Hoyt Lougee, Engineering Director, Jim Everett-Wilson, Technical Director, John Cadigan, Medical Practice Director

We show that long software development cycles are frequently a symptom of a larger issue - a dynamic that includes the corporate product strategy, the product focus, and requirements development. By approaching the product requirements process in a more structured fashion, it is possible to shorten the development process.

Published: Dec 01, 2003
Author: Kevin Platt, Principal Software Engineer

This presentation compares the major technology choices available (user-, role-, and context-based systems) and identifies the objectives they satisfy and the objectives they don't. The architecture for a context-based authentication and authorization system is then presented and evaluated in more depth to identify the areas of risk, which components are necessary for the architecture to satisfy the objectives identified earlier, and the tradeoffs between the available choices.

Published: Nov 11, 2003
Author: Tim Bowe, Co-CEO; Charlie Alfred, Technical Director; John Cadigan, Medical Practice Director

This paper discusses the development of product line architectures from the perspective of executives and managers. We look at what does and does not constitute a product line and we show how ineffectively executing a product line architecture strategy can have serious and long-term ramifications for the organization.

Published: May 13, 2003
Author: John Cadigan, Medical Practice Director; Hoyt Lougee, Engineering Director

This paper discusses the importance of medical software time-to-market, key attributes of high-performance teams, and an improved strategy to engage such teams without incurring the risk, cost, and delay required to build one.

Published: Oct 29, 2002
Author: John Cadigan, Medical Division Manager Jim Everett-Wilson, Technical Director, Norm Delisle, Engineering V.P.

If you are facing a complete product redevelopment, you may not have to rewrite the entire program. This paper discusses some low-cost, easy-to-learn formal software architecture evaluation methods that can be used to help you save millions of dollars per year in software maintenance costs. Additionally, these methods can help you gain the ability to quickly develop new products off your software code base to capitalize on new product opportunities.