Scheduled System Maintenance:
On Monday, April 27th, IEEE Xplore will undergo scheduled maintenance from 1:00 PM - 3:00 PM ET (17:00 - 19:00 UTC). No interruption in service is anticipated.
By Topic

Software, IEEE

Issue 2 • Date March-April 1999

Filter Results

Displaying Results 1 - 21 of 21
  • Software Engineering Principles

    Publication Year: 1999 , Page(s): 6 - 8
    Cited by:  Papers (4)  |  Patents (1)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (99 KB)  

    First Page of the Article
    View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Finding Perfomance Improvements

    Publication Year: 1999 , Page(s): 61 - 65
    Save to Project icon | Request Permissions | PDF file iconPDF (114 KB)  
    Freely Available from IEEE
  • What Have You Learned Today?

    Publication Year: 1999 , Page(s): 66 - 68
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (87 KB)  

    First Page of the Article
    View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A Book You Can Chew On [Book Review]

    Publication Year: 1999 , Page(s): 91 - 92
    Save to Project icon | Request Permissions | PDF file iconPDF (119 KB)  
    Freely Available from IEEE
  • Pascal to C++ Without Tears

    Publication Year: 1999 , Page(s): 92 - 93
    Save to Project icon | Request Permissions | PDF file iconPDF (174 KB)  
    Freely Available from IEEE
  • Designing For The User

    Publication Year: 1999 , Page(s): 93 - 94
    Save to Project icon | Request Permissions | PDF file iconPDF (178 KB)  
    Freely Available from IEEE
  • Reuse Strategies For Success

    Publication Year: 1999 , Page(s): 95 - 96
    Save to Project icon | Request Permissions | PDF file iconPDF (230 KB)  
    Freely Available from IEEE
  • Ubiquitous Computing Uncorked

    Publication Year: 1999 , Page(s): 97 - 99
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (75 KB)  

    First Page of the Article
    View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Why License Software Engineers

    Publication Year: 1999 , Page(s): 101 - 103
    Save to Project icon | Request Permissions | PDF file iconPDF (95 KB)  
    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The Loyal Opposition - On Design

    Publication Year: 1999 , Page(s): 104 - 103
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (53 KB)  

    First Page of the Article
    View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Harissa: A hybrid approach to Java execution

    Publication Year: 1999 , Page(s): 44 - 51
    Cited by:  Papers (7)  |  Patents (1)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (172 KB)  

    Java provides portability and safety but falls short on efficiency. To resolve this problem, the authors developed Harissa, an execution environment that offers efficiency without sacrificing portability or dynamic class loading View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Self-tuning systems

    Publication Year: 1999 , Page(s): 52 - 60
    Cited by:  Papers (7)  |  Patents (12)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (276 KB)  

    Tuning operating systems helps system administrators improve system performance and efficiency, but it can be time-consuming. These authors propose a mechanism, based on genetic algorithms, to automate this process by running simulations of system performance for various parameter values during the system's idle loop View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Leverage your lessons [project management]

    Publication Year: 1999 , Page(s): 30 - 32
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (92 KB)  

    In today's fast-moving market, software project teams don't have time to make several attempts to meet a customer's requirements. Teams need to be smart about what they do learning from the experiences of colleagues within their own organization and in the industry. In short, teams need to take the time to do things as “right” as they can because they don't have time to do things over. Why do we often have to do things over? Why do we repeat the mistakes of the past? It's related to this: Insanity is doing things the same way we did them before, but expecting different results. It's hard for a team to get better at what it's doing if it doesn't think about its work and how to improve it. Some project teams do, in fact, think about how and why their projects worked. They gather and document lessons learned. Some teams share that information with others in their organization, and a few teams attempt to review what others have learned as they start a new project or new phase of a project. But many teams do none of this. They're the ones that encounter the same problems over and over again, attributing them to bad luck when, in fact, poor project learning and poor organizational learning are the underlying causes View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Reverse-engineering new systems for smooth implementation

    Publication Year: 1999 , Page(s): 36 - 43
    Cited by:  Papers (5)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (164 KB)  

    Reverse-engineering a commercial client-server system from PeopleSoft yielded a valuable resource and proved to be cost-effective. The authors describe the motivations for, approach to, and results of this project, commissioned by the Commonwealth of Virginia's government View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Metrics for small projects: Experiences at the SED

    Publication Year: 1999 , Page(s): 21 - 29
    Cited by:  Papers (6)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (172 KB)  

    An organized, comprehensive metrics program can bring order to the chaos of small-project management and form the foundation for a concerted process improvement effort. The authors describe their experience in applying metrics to one such US Army organization View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Retrain your code czar

    Publication Year: 1999 , Page(s): 86 - 88
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (100 KB)  

    Many software organizations have two classes of technical staff: normal employees and royalty. The royalty-those kings, queens, and czars of software development-initiate central controlling project roles. They see a dire project need and act on it, though no one asked them to. Royalty believe they provide unique project and product skills for the organization. They may, but, in my experience, their controlling actions prevent the project and the team from developing products and cohesive processes. When one team member takes on the royalty role, it prevents the rest of the group from learning what she already knows. The team becomes fragmented and can't work together; the problems that created the royalty become even worse. Royalty delay projects because they interrupt the normal development loop of creating the product, testing it, fixing it, integrating it, and getting feedback. The royalty must stay in their chosen role, because the participants eventually come to believe that the project cannot make any progress without them View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Capturing the benefits of requirements engineering

    Publication Year: 1999 , Page(s): 78 - 85
    Cited by:  Papers (12)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (160 KB)  

    Requirements management has a critical effect on an organization's development costs and software quality. The authors have developed a method that allows incremental, systematic improvement of requirements engineering and builds on existing SPI models and standards, filling in the gaps to improve schedules, budgets, and product quality View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Making sense of measurement for small organizations

    Publication Year: 1999 , Page(s): 14 - 20
    Cited by:  Papers (16)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (184 KB)  

    The key to successful measurement programs is to make the metrics meaningful and tailor them to the organization-however small it might be. Here the author explains how he helped three small companies reduce the time spent handling change requests, correcting errors, and generating system versions and production releases. Both the developers and customers appreciated the improved practices View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Act quickly to avoid losing patents

    Publication Year: 1999 , Page(s): 33 - 35
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (88 KB)  

    “Microsoft Patents Ones, Zeros”, a headline recently announced. Of course, Microsoft did not invent ones and zeros, and neither Microsoft nor anyone else could get a patent covering their use. Nonetheless, the headline firmly underscores the breadth of software patents being issued today. Only a few years ago, the software industry rallied against the famous Compton's NewMedia multimedia patent because of its undue scope. While most software patents aren't met with such fanfare, the US Patent and Trademark Office continues to issue software patents that are often surprisingly broad. In addition to their sweeping scope, software patents are now being issued in record numbers. Only a trickle a few short years ago, software patents now account for as much as 15 percent of the 120,000 patents issued annually. Still, programmers have historically been slow to file their patent applications. Maybe it is because software inventions have only been openly patentable for a few years. Perhaps it is because programmers are too busy testing, documenting, and adding last-minute features to divert attention to patents. Whatever the reason, software inventors often wait until their software is about to be released, or until after it has been released, before filing patent applications View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A method for software quality planning, control, and evaluation

    Publication Year: 1999 , Page(s): 69 - 77
    Cited by:  Papers (23)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (320 KB)  

    Squid is a method and a tool for quality assurance and a control that allows a software development organization to plan and control product quality during development. The Telescience software development project used it to build a remote monitoring and control system based in Antarctica View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Untested software threatens infrastructures

    Publication Year: 1999 , Page(s): 89 - 90
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (76 KB)  

    The public needs access to information infrastructures that are reliable, secure, noninterruptible, and fault-tolerant, but the transition to paperless commerce threatens individual privacy with each transaction. Wholesale payment systems, such as the United States Federal Reserve's FedWire and automated clearing houses, move trillions of dollars over electronic networks daily. With roughly 95 percent of Defense Department communications relying on the commercial infrastructure, the US government is a major stakeholder in the security of commercial systems. The paper discusses the importance of software testing and the assessment of software liabilities View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.

Aims & Scope

IEEE Software's mission is to build the community of leading and future software practitioners. The magazine delivers reliable, useful, leading-edge software development information to keep engineers and managers abreast of rapid technology change

Full Aims & Scope

Meet Our Editors

Editor-in-Chief
Diomidis Spinellis
Athens University of Economics and Business
28is Oktovriou 76
Athina 104 33, Greece
dds@computer.org