Site Map
DDC-I, # 1 in Customer Care     · Safety Critical Embedded Software Development
    · Customized Tools & Services Tailored to Fit Your Needs
    · Legacy Software System Modernization
    · Ada Compilers, C Compilers, C++ Compilers, JOVIAL Compilers, FORTRAN Compilers
 



September 2005

Products / Services

 
   
 

Products

 
   
 

 

 
   
 

Custom Services

 
   
 

 

 
 

Spotlight

 
   
 

"We are pleased that this seamless integration is now available for our safety critical customers and look forward to working with them in the future."

Rob Hoffman,
Senior Director Aerospace & Defense,
Wind River Systems
 

 
   
 

 

 
 

Contact the Editor

 
   
 

DDC-I Online News is published by DDC-I, Inc., 400 N. 5th Street #1050; Phoenix, AZ 85004, Editor: Jennifer Sanchez

Comments and submissions of articles are welcome and should be sent to the editor at the above address or by email to editor@ddci.com.

Copyright 2005, DDC-I, Inc. Permission to copy is prohibited. References to other companies and their products use trademarks are owned by the respective companies and are for reference purposes only.

 

 
   
 

 

 
DDC-I Online News
Inside this Issue

 

For Immediate Release

DDC-I Names Bob Morris as President and Chief Executive Officer

September 1, 2005 -- Phoenix, AZ -- DDC-I, a global leader in safety critical software tools for embedded applications announced today the appointment of Bob Morris as President and Chief Executive Officer.

Morris joins DDC-I from LynuxWorks, an embedded operating system and network software company, where he served for almost 5 years as vice president of sales and marketing. Prior to LynuxWorks, Morris was vice president of marketing and business development for Chaparral Network Storage, a fiber channel networking company, and president and chief operating officer of Gambit Automated Design, a software and services company acquired by Synopsys, Inc. He has also served as vice president of marketing at Vanguard Technology (StorNet), a systems integration and internet solutions company; ATG Cygnet, a manufacturer of automated storage solutions, Conner Peripherals, a disk drive and software company; and was the general manager of Fujitsu Computer Products Secondary Storage Division.

"Bob brings proven industry leadership and a deep understanding of our market," said Ole Oest, chief operating officer of DDC-I. "We are very excited about adding his strong experience to the DDC-I team."

About DDC-I, Inc.

DDC-I, Inc. is a global supplier of software development tools, custom software development services, and legacy software system modernization. DDC-I's customer base is an impressive "who's who" in the commercial, military, aerospace, and safety-critical industries. Tools include compiler systems and run-time systems for C, Embedded C++, Ada, JOVIAL and Fortran application development. For more information regarding DDC-I products, contact DDC-I at: 400 North Fifth Street, Phoenix, Arizona 85004; phone (602) 275-7172; fax (602) 252-6054; e-mail sales@ddci.com; or visit www.ddci.com.

[ Back to Top ]

For Immediate Release

New Upgrade Release for TADS Windows
Targeting M680x0 & Mil-Std-1750A - Now Available

Offers upgraded licensing, shared projects and unbundled tools.

August 29, 2005 – Phoenix, AZ – DDC-I, a global leader in safety critical software tools for embedded applications, announces today a new release for the TADS Ada Development System targeting Motorola 68K and Mil-Std-1750A processors.

"This release completes V.6.2.0 upgrades to the entire TADS Windows Development Suite (TADS-i960, TADS-1750A, and TADS-680x0), states Stephen Hunter, Senior Software Engineer. "The upgrades offer our customers a product that is easier to use, from a smooth installation to support for multiple users," Hunter concludes.

Features:

FLEXnet 10.1 supports all of the latest licensing models including triple redundant license servers, MAC address host ID’s, hardware dongles, license borrowing, and a host of other licensing models tailored to the customer's needs.

Distributed TADS for Windows allows a TADS-680x0 or TADS-1750A Universe to be installed on one Universe server, and then to be shared by any number of client installations on other Windows machines. This will allow different users on different machines to easily share projects and libraries making software project management easier to implement.

The Windows installation procedures have been re-engineered to allow for easy re-licensing of the product. The various licensing models supported can easily be changed through the installation procedure without the need to uninstall or reinstall the product.

Unbundled Tools: For TADS-680x0, the Stand-Alone AdaScope (debugger), Link Retargeting Kit, Protocol Retargeting Kit and Runtime Source Kits are now all available as separate shippable packages. For TADS-1750A, The Math Package, Stand-Alone AdaScope (debugger), Emulator Support Kit (PDU), Link Retargeting Kit, Protocol Retargeting Kit, and Runtime Source Kits are also all available as separate shippable packages. Each may be purchased and installed separately or as part of the main development system.

About DDC-I, Inc.

DDC-I, Inc. is a global supplier of software development tools, custom software development services, and legacy software system modernization. DDC-I's customer base is an impressive "who's who" in the commercial, military, aerospace, and safety-critical industries. Tools include compiler systems and run-time systems for C, Embedded C++, Ada, JOVIAL and Fortran application development. For more information regarding DDC-I products, contact DDC-I at: 400 North Fifth Street, Phoenix, Arizona 85004; phone (602) 275-7172; fax (602) 252-6054; e-mail sales@ddci.com; or visit www.ddci.com.

[ Back to Top ]

Tech Talk

SCORE® Gives State-of-the-Art Ada Support to VxWorks


As a standalone product, SCORE® (DDC-I’s Safety Critical Object-oriented Real-time Embedded Software Development Environment) has been able to meet the needs of most of DDC-I’s customers. It’s ability to seamlessly integrate and debug code written in multiple languages ( Ada 95, C, Embedded C++, and FORTRAN ), together with a small-real time kernel has provided a stable platform on which applications are built. Having a small real-time kernel is a significant advantage of SCORE®, but at the same time it’s smallness is a liability to customers wanting more device drivers, communication stacks, disk management, and other middleware functions.

Now SCORE® has been integrated with VxWorks (Wind River’s leading Embedded Real-Time Operating System) - you can get the proven SCORE® code generation ability plus all the rich features and middleware of the top-of-the-line RTOS. Not only has this integration been done on the target, but the development environments are integrated as well. No more launching one tool from another; the entire edit, build, and debug activities are all controlled from within Workbench - the new Wind River Integrated Development Environment (IDE).

Download Entire White Paper in PDF Format

[ Back to Top ]

In The News

Costly Mistakes

By David Mosley

Some people find it entertaining to hear about other people's mistakes. Perhaps not so when the other person is the Federal Bureau of Investigation and the mistake is $104.5 million. As described in the August 15 issue of SD Times in an article by James Shore, the FBI had launched the Trilogy project to update the FBI's IT infrastructure in 2001. There were three parts: the network, the hardware, and the software. Guess which one got the blame. The software, the "Virtual Case File" (VCF), was intended to allow FBI agents to upload information to a centralized database. It was a disaster, and the project was canceled for a loss of $104.5 million.

The loss was avoidable: The FBI made many classic mistakes, and the article looks at three of them from the agile software development point of view. Mistake No. 1: Ignoring the Users. In its 2004 report, the Standish Group cites user involvement as the top project success factor. Despite this, there is no indication that the FBI made the involvement of the actual agents a priority in VCF development. Agile software teams produce working software every month (or even more frequently) for demonstrations and user review. They recruit outside customers to regularly review these releases and provide feedback. Without this feedback from actual users, how can you tell if your software is meeting their needs? Admittedly, the users with the best understanding of what's needed are often the busiest, and although it's tempting to say you don't need them, that is a very risky approach.

Mistake No. 2: Expecting Requirements to Remain Stable. Requirements always change. It's tough for users to imagine what they want without seeing it, so when they do see it, they're going to change their mind. Preventing requirements changes just mean that the software you deliver is less likely to do what your users need. An agile project acknowledges that change is inevitable and puts mechanisms in place to make it possible. There are techniques that make the software more malleable and able to deal with arbitrary changes.

Mistake No. 3: The "Big Bang" Deployment. The FBI decided to develop a full replacement for the old application, switch off the old one, and switch on the new one. This is a foolhardy approach -- it means that you have to have a complete replacement for all of the functionality in the old system, including defects that other systems might rely on. It's an immense undertaking and one that is very difficult to get right. Agile projects already create working software on a frequent basis for their users to review, and they like to deploy frequently, too. An agile team will identify the most valuable features, work on them one at a time, and deploy each one incrementally as soon as its finished. Integration is a big source of risk and doing it in a smaller chunk, sooner, helps mitigate that risk.

These weren't the only mistakes the FBI made with the VCF project. There were others. Now they have no choice but to start over with a new acronym.

[ Back to Top ]

Something to Think About

Listen Each Other to a Better Place

By Linda Rising
risingl@acm.org
www.lindarising.org

Many of you know that I have a new book out. The title is Fearless Change: Patterns for Introducing New Ideas. My co-author, Mary Lynn Manns, and I struggled to come up with a good name for our book and finally decided on "Fearless" as a reflection of one of the most important patterns in the collection: Fear Less. This pattern addresses the problem of resistance to the new idea. Our usual reaction to those who are skeptical about our ideas is to treat the resistors as naysayers and avoid them. We don’t want to hear anything critical of our new idea. We tend to surround ourselves with those who agree with us. This means we limit what we can learn about the idea or how to improve the introduction process. We happily go forward believing that all is well—except for "those" negative people who just won’t listen!

The Fear Less pattern advises innovators to listen carefully to those who aren’t initially enthusiastic about the new idea. Listen and learn. As my mother used to say, "Listen hard to what you don’t want to hear." The skeptic who takes the time to tell you what won’t work is offering a gift. Appreciate it.

Often when I talk about this pattern, I tell the story of skeptics who not only gave me the gift of their view points, but when I appreciated them, when I listened, those skeptics became my greatest supporters. They didn’t necessarily sign up wholesale for the idea, but they helped me do the best job possible of bringing the idea to real fruition in the organization. I often thought that maybe no one had ever seriously listened to them before. I wondered what that’s like—not to have anyone listen to you.

Listen to understand

Mary Lynn and I discovered a magical writing technique. When we would get stuck on some part of the book, I would say, "Ask me a question." Then Mary Lynn (she was really good at this!) would say, "Linda, why <important question>?" Then I would start explaining as I would to an audience member who might have asked the same question. Mary Lynn would type furiously to capture what often surprised both of us. This process reminds me of something author E. M. Forster observed, "How do I know what I think until I say it?" It seems that we need someone to "listen us into understanding."

In Barbara Waugh’s book about her experience as a change agent at HP, she proposed:

Instead of a great keynote speaker, what if we have a great keynote listener who can listen us into creating our visions for HP’s future?

Barbara explains that she first heard about the generative power of listening from Nelle Morton, the late feminist theologian and author, who believed that listening is a great and powerful skill that opens the creative floodgates in the person being listened to. The listener’s attentive, unbroken, and receptive silence invites speakers to explore their thoughts and come up with ideas that they’ve never had before. Ideas that literally didn’t exist until they were "listened into speech."

Listen to better health

Listening can have deeper impact for us than helping us understand what we are thinking. I was intrigued by reading an account of an experiment in The Placebo Response. In the mid-80s, several family physicians in Canada, led by Dr. Martin Bass, studied a large group of patients who visited doctors with a wide variety of common symptoms. The investigators asked: What best predicts whether the patient will say that he is better one month later?

Their detailed review of the medical records showed many things that did not predict whether the patient would get better: the thoroughness of the medical history and physical exam, whether the physician did any lab tests or x-rays, and which medications were prescribed. Almost everything physicians are taught turned out to make no difference for this group of patients.

The doctors were able to identify one factor that best predicted whether the patient would report feeling better after one month and that was—whether the patient said that the physician had carefully listened to the patient’s description of the illness at the first office visit.

In a follow-on study, Bass and his colleagues considered a large group of patients who came in with the new onset symptom of headache. After a year, they found that what best predicted an improvement in the headaches was the patients’ report that at the very first visit, they had a chance to discuss their problem fully and felt the physician was able to appreciate what it meant to them. Barbara Starfield of Johns Hopkins University did a similar study of public health clinic patients in Baltimore and reached the same conclusion. The doctors listened their patients into better health.

Listen to reach a better place

I met someone at a conference recently who said: "I want to talk to you about patterns. What’s the big deal? I really don’t like patterns. Why should I? I don’t get it!"

I began my standard "why patterns are great" talk, throwing in everything but the kitchen sink in my attempt to convince my protagonist and "sell" patterns. Finally, I paused and the person said: "But, those patterns <about a particular subject> are worthless!"

Ah, so the problem was not with "patterns" at all, but with "those particular patterns," and, as it happens, I didn’t like them either. As soon as I acknowledged that "those particular patterns" were not very good ones, the speaker was happy and moved on to another topic—enough said.

I was astounded. How many times must I learn this lesson? I get countless numbers of questions in email and during presentations. As soon as I hear a keyword, I’m off and running, assuming that, of course, I can answer that! I am careful to say at the end, "Does that answer your question?" But, of course, many times, I wonder if the questioner is intimidated by the situation and nods out of politeness. If only I would stop and really listen. I could listen the questioners to a better place and go right along with them! If I had only done this with the patterns objections I could have listened him into appreciating patterns, instead of arguing my case.

Now and then, I like seeing old re-runs of the television series MASH. Just a few weeks ago as I was thinking about the power of listening, I saw the episode where a solider killed in battle has trouble realizing that he has died. He tries to communicate with members of the MASH unit, but only Klinger, who is suffering from a high fever, can hear him. The "dead" soldier observes that of all the things that he thought he would miss after death, the worst is that he is talking but no one is listening. No one can listen him to a better place. How many people spend their lives like this?

Listen to our customers

Think of the power of adopting this technique in the workplace! What would happen if we listened to our colleagues and our customers? What would change in our homes, if we listened to the members of our family? Would we all help each other to be in a better place? One of the customer interaction patterns I have written is called Listen, Listen, Listen. It is about helping you and your customer move to a place of better understanding and building a trusting relationship. The keystone of that pattern collection is called It’s a Relationship, Not a Sale.

Let me recommend the free newsletter Good Experience http://www.goodexperience.com/signup.php

A recent issue pointed to a Wall Street Journal article about Vodafone's attempt to make a simpler cell phone (Mobile Phones, Older Users Say, More Is Less):

http://tinyurl.com/a9oqd

Here's an excerpt from that article:

What [Vodafone] heard from consumers aged 35 to 55 shocked executives of the Newbury, England company. Many in that age range didn't know their cell phone numbers or how to use basic functions. One-third, for example, said they didn't know how to tell when they had received a text message. Some thought the envelope icon that signals a message meant their phone bill had arrived...

Many 35- to 55-year-olds also didn't like going into Vodafone retail stores because the young staff -- average age 24 – talked in acronyms they couldn't understand. These consumers said they weren't interested in the cameras, Internet browsers and many of the other features that are becoming standard on the latest cell phones. "Our biggest customer segment turned round and said: ‘You haven't been listening to us,’" says Guy Laurence, the company's consumer-marketing director. "It was an industry for kids."

What a wake-up call! Listening, really listening to your customers can move you to a better understanding of customer needs that your product can satisfy.

Listen to each other

On a personal level, you might try what humorist Loretta LaRoche calls Power Whining. Simply tell a friend that you're stressed and need 2 minutes to unload. The friend’s job is just to listen without interrupting. When you're done, reciprocate. When both of you have finished, wrap up with a 1-minute monologue each, describing the things for which you are most grateful. The last bit puts everything into perspective by reminding you both to be grateful for all the things that aren't stressing you out. We need that kind of reminder to help us stay on an even keel.

Finally, in case you feel that no one listens to you, the best way to solve this problem is to start listening to others. Give someone the gift of your attention and you will probably find that soon others will be listening to you. Could we start a chain reaction that might help a noisy world that needs the silence of personal attention? Let me know if it works for you!

References

Brody, Howard, The Placebo Response, Cliff Street Books, 1997.

Manns, Mary Lynn and Linda Rising, Fearless Change: Patterns for Introducing New Ideas, Addison-Wesley, 2004.

Waugh, Barbara with Margot Silk Forrest, The Soul in the Computer, Inner Ocean, 2001.

 

About the Author
http://www.lindarising.org

risingl@acm.org

Linda Rising has a Ph.D. from Arizona State University in the area of object-based design metrics. Her background includes university teaching as well as work in industry in telecommunications, avionics, and strategic weapons systems. She is the author of numerous articles and has published three books: Design Patterns in Communications, The Pattern Almanac 2000, and A Patterns Handbook. Follow this link for information regarding her latest book "Fearless Change: patterns for introducing new ideas".
http://www.cs.unca.edu/~manns/intropatterns.html

[ Back to Top ]

 

   

©2005, DDC-I, Inc., Phoenix, AZ - All Rights Reserved - Webmaster@ddci.com

DDC-I, Inc. -  USA - Phone: (602) 275-7172