By Topic

Software, IEEE

Issue 6 • Date Nov.-Dec. 1999

Filter Results

Displaying Results 1 - 17 of 17
  • Professional software engineering: fact of fiction? [Guest Editorial]

    Page(s): 13 - 17
    Save to Project icon | Request Permissions | PDF file iconPDF (182 KB)  
    Freely Available from IEEE
  • Program criteria for software engineering accreditation programs

    Page(s): 31 - 34
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (100 KB)  

    The Software Engineering Education Project's objective is to recommend curricula to prepare professionals in software engineering. This article reports on SWEEP's initial progress and its future goals to address undergraduate- and graduate-level accreditation for software engineering and technology programs View full abstract»

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

    Page(s): 109 - 111
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (100 KB)  

    Over the past few decades, the patent laws in many countries have become increasingly alike. From time to time, treaties and conventions have “harmonized” the world's patent laws, creating many fundamental similarities. For example, the patent term length, a “novelty” or “inventive step” requirement, and the recognition of another country's earlier filing date are common provisions, but, just as in other legislative fields besides intellectual property, several noticeable differences still exist View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • An integrated collection of software engineering standards

    Page(s): 51 - 57
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (140 KB)  

    The IEEE Software Engineering Standards Committee has taken deliberate steps to unify and integrate its collection of software engineering standards. Encouraging results are apparent in its latest publication, which is organized around a single architecture for the SESC collection. This article explains the principles of the SESC collection and describes our progress toward integrating the various standards within it View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • It ain't broke, so don't fix it [software engineering]

    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (96 KB)  

    The author considers how setting up a formal licensing mechanism for software engineers (even one limited to those involved in the most safety-critical applications) would be a blunder, doomed to undo its own best intentions. It would be, at best, a dangerous mischief and, at worst, lead us into a positive ethical quagmire View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software engineering programs are not computer science programs

    Page(s): 19 - 30
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (252 KB)  

    Software Engineering programs have become a source of contention in many universities. Computer Science departments, many of which have used that phrase to describe individual courses for decades, claim SE as part of their discipline. Yet some engineering faculties claim it as a new specialty among the engineering disciplines. This article discusses the differences between traditional CS programs and most engineering programs, and argues that we need SE programs that follow the traditional engineering approach to professional education View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Why can't we implement this SDM? [systems development methodology]

    Page(s): 70 - 71, 75
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (104 KB)  

    To cope with the mounting demands for large, complex information system applications, most organizations turn to a systems development methodology. SDMs are logically appealing, offering a flexible framework for the sequence of tasks needed to develop an application, as well as tools and techniques for accomplishing these tasks. By creating an engineering-like development discipline, SDMs provide explicit deliverables and consistency as information systems are built. In its intent, an SDM should reduce the risk associated with shortcuts and mistakes and ensure that quality infuses the software process. On the surface, at least, it would seem that every organization should have an SDM in place. Unfortunately, most IS organizations fail to successfully implement and utilize an SDM. The question is, why? View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The guide to the Software Engineering Body of Knowledge

    Page(s): 35 - 44
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (196 KB)  

    Reporting on the SWEBOK project, the authors-who represent the project's editorial team-discuss the three-phase plan to characterize a body of knowledge, a vital step toward developing software engineering as a profession View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Traditional Japanese architecture blends beauty and rationale [lessons for software engineering]

    Page(s): 101 - 103
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (216 KB)  

    It's hard to find a good instance of harmonization of beauty and rationale in the field of software engineering. We can, however, find it in ancient Japanese architecture which is where we might find the clues we need to achieve our goal. Unfortunately, the software community is relatively young, so there are few such secrets or literatures to use as a basis for our communications. Moreover, because the structure of software is not obvious yet architectural structures are clearly visible-the difficulty we face might be larger and deeper than that of other disciplinary fields. However, by carefully examining ancient architectural methods, we believe that we are stepping in the right direction in our pursuit of the patterns that will realize the harmony of beauty and rationale View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software engineering grows up

    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (328 KB)  

    The author discusses licensing in the software engineering profession. If software professionals do not participate in defining licensing and other regulation mechanisms, they could find themselves at the mercy of laws designed to protect segments of industry or to increase the reach of professional organizations that do not represent them View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Third-party testing and stirrings of the new software engineering

    Page(s): 76 - 79
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (116 KB)  

    As the discipline of software engineering prepares for the ever-increasing development of applications based on preproduced software components, it is time to reflect on the emergence of the engineering profession in the United States. A brief review of bridge construction-one of the earliest engineering endeavors-can help, as bridges are required for interrelationships among people and governments, the growth of commerce, and the proliferation of new ideas View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • What do you mean I can't call myself a software engineer?

    Page(s): 45 - 50
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (172 KB)  

    In June 1998, the Texas Board of Professional Engineers established software engineering as a recognized engineering discipline and established licensing criteria specifically suited to software engineers. The author explains the legal issues involved and how they affect you View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Commercial vs. aerospace worlds: comparing software engineering cultures

    Page(s): 97 - 100
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (160 KB)  

    Two and a half years ago, I retired from the aerospace and defense industry after 35 years. Of those 35 years, I spent the last 20 in software and system engineering, including the last 10 in software process improvement, quality, and related disciplines. I now work in commercial industry, in software quality for a company where that means process development, documentation, and improvement, rather than testing (as it means at many other companies). From this new perspective, I want to compare the software engineering cultures in these two different environments, examine specifics, and see if any general conclusions can be drawn View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Penguins everywhere: GNU/Linux in Antarctica

    Page(s): 90 - 96
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (328 KB)  

    The harsh, remote conditions of the Antarctic ice cap pose formidable challenges to continuous, year-round geophysical data acquisition. The author designed and built a serial data-acquisition engine using the GNU/Linux operating system on a small single-board computer to remotely record earthquakes View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A net practice for software project management

    Page(s): 80 - 89
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (208 KB)  

    Technical and managerial complexity increasingly overwhelm project managers. To rein in that complexity, the authors propose PM-Net, a model that captures the concurrent, iterative, and evolutionary nature of software development. It adopts the basic concepts of Petri nets, graphical models of information flow, with extensions to represent both decisions and artifacts View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Full text access may be available. Click article title to sign in or learn about subscription options.
  • How the new Software Engineering Code of Ethics affects you

    Page(s): 58 - 64
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (144 KB)  

    The Software Engineering Code of Ethics and Professional Practice has recently been approved. This article looks at the immediate and long-term implications: Why does a profession need a code of ethics? How will this code function in an emerging profession like software engineering? What impact will it have on software practitioners? 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
Forrest Shull
Fraunhofer Center for Experimental Software Engineering