By Topic

IEEE Software

Issue 4 • Date July-Aug. 2006

Filter Results

Displaying Results 1 - 25 of 25
  • [Front cover]

    Publication Year: 2006, Page(s): c1
    Request permission for commercial reuse | PDF file iconPDF (736 KB)
    Freely Available from IEEE
  • Table of contents

    Publication Year: 2006, Page(s):2 - 3
    Request permission for commercial reuse | PDF file iconPDF (420 KB)
    Freely Available from IEEE
  • Article summaries

    Publication Year: 2006, Page(s): 4
    Request permission for commercial reuse | PDF file iconPDF (35 KB)
    Freely Available from IEEE
  • Passwords and Passion

    Publication Year: 2006, Page(s):5 - 7
    Request permission for commercial reuse | PDF file iconPDF (141 KB) | HTML iconHTML
    Freely Available from IEEE
  • First Virus?

    Publication Year: 2006, Page(s):8 - 10
    Request permission for commercial reuse | PDF file iconPDF (436 KB) | HTML iconHTML
    Freely Available from IEEE
  • Designing for recovery [software design]

    Publication Year: 2006, Page(s):11 - 13
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (451 KB) | HTML iconHTML

    How should you design your software to detect, react, and recover from exceptional conditions? If you follow Jim Shore's advice and design with a fail fast attitude, you won't expend any effort recovering from failures. Shore argues that a "patch up and proceed" strategy often obfuscates problems. Shore's simple design solution is to write code that checks for expected values upon entry and return... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • From small to gargantuan [software development patterns]

    Publication Year: 2006, Page(s):14 - 15
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (117 KB) | HTML iconHTML

    Software development is ultimately an engineering activity, whose primary activity is to deliver executable artifacts in a manner that balances the forces on that system. The forces that swirl around a software-intensive system include not only its purely functional requirements but also a multitude of nonfunctional ones, such as reliability, portability, and scalability. Each of these forces is r... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Take your mobile device out from behind the requirements desk

    Publication Year: 2006, Page(s):16 - 18
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1340 KB) | HTML iconHTML

    Mobile computing devices are everywhere. Recent technological improvements let most wireless devices connect to the Internet and many Web services. This presents exciting new opportunities for requirements analysts. Shouldn't we be able to capture requirements anywhere, anytime using our mobile devices? Why not capture requirements on your mobile telephone and then phone them in? You can do a lot ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Guest Editors' Introduction: Software Testing Practices in Industry

    Publication Year: 2006, Page(s):19 - 21
    Cited by:  Papers (7)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1045 KB) | HTML iconHTML

    Four papers and a roundtable discussion shed light on the current state of software testing practices. Case studies from industry experience address topics including unit-testing practices, agile testing, and automating software testing. Although many of these approaches show promise, software testing is still one of the more neglected practices within the software development life cycle. Suggesti... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A survey of unit testing practices

    Publication Year: 2006, Page(s):22 - 29
    Cited by:  Papers (49)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (138 KB) | HTML iconHTML

    Unit testing is testing of individual units or groups of related units. What are a company's typical strengths and weaknesses when applying unit testing? Per Beremark and the author surveyed unit testing practices on the basis of focus group discussions in software process improvement network (SPIN) and launched a questionnaire to validate the results. This survey is an indication of unit testing ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Agile software testing in a large-scale project

    Publication Year: 2006, Page(s):30 - 37
    Cited by:  Papers (21)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (134 KB) | HTML iconHTML

    Agile software development in general and Extreme Programming (XP) in particular, promote radical changes in how software development organizations traditionally work. We present and analyze new data from a real, large-scale agile project to develop a business-critical enterprise information system for the Israeli Air Force (IAF). Our results offer new evidence that agile testing practices actuall... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Unit tests reloaded: parameterized unit testing with symbolic execution

    Publication Year: 2006, Page(s):38 - 47
    Cited by:  Papers (17)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (202 KB) | HTML iconHTML

    Unit tests are becoming popular. Are there ways to automate the generation of good unit tests? Parameterized unit tests are unit tests that depend on inputs. PUTs describe behavior more concisely than traditional unit tests. We use symbolic execution techniques and constraint solving to find inputs for PUTs that achieve high code coverage, to turn existing unit tests into PUTs, and to generate ent... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Industrial deployment of the TTCN-3 testing technology

    Publication Year: 2006, Page(s):48 - 54
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (127 KB) | HTML iconHTML

    The development of mobile telecommunications systems poses numerous testing challenges that have become more severe over time. We can categorize these challenges as increasing complexity, shorter time to market, and more exacting quality requirements. At Nokia, we expected that the Testing and Test Control Notation 3 (TTCN-3) technology to address such product testing challenges better than other ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software testing and industry needs

    Publication Year: 2006, Page(s):55 - 57
    Cited by:  Papers (3)
    Request permission for commercial reuse | PDF file iconPDF (280 KB) | HTML iconHTML
    Freely Available from IEEE
  • Static code analysis

    Publication Year: 2006, Page(s):58 - 61
    Cited by:  Papers (7)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (500 KB) | HTML iconHTML

    Programmers usually employ static checkers, it checks our programs for errors without executing them, in a process called static code analysis. In this way, it works with a program that has an initial indication of correctness (because it compiles) and try to avoid well-known traps and pitfalls before measuring it against its specifications (when it's tested). We use FindBugs, a popular open sourc... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Choosing a programming language

    Publication Year: 2006, Page(s):62 - 63
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (116 KB) | HTML iconHTML

    This paper evaluates the use of a functional language for implementing domain-specific functionality. The factors we consider when choosing a programming language are programmer productivity, maintainability, efficiency, portability, tool support, and software and hardware interfaces. The choice of programming language is a fine balancing act. Modern object-oriented languages such as Java and C# a... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Evidence-based cost estimation better-quality for software

    Publication Year: 2006, Page(s):64 - 66
    Cited by:  Papers (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (194 KB) | HTML iconHTML

    Our work on COSEEKMO is hardly enough to change experimental methods in the cost estimation community. So, we're also running a new workshop series called PROMISE devoted to repeatable software engineering experiments. Evidence-based reasoning is becoming common in many fields. Evidence-based approaches demand that, among other things, practitioners systematically track down the best evidence rela... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Decision support system for software project management

    Publication Year: 2006, Page(s):67 - 75
    Cited by:  Papers (4)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (178 KB) | HTML iconHTML

    Decision support systems combine individuals' and computers' capabilities to improve the quality of decisions. Usually adopted in manufacturing to design floor plans and optimize resource allocation and performance, DSSs are penetrating increasingly complex application areas, from insurance fraud detection to military system procurement to emergency planning. Although researchers have suggested ma... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • How are Java software developers using the Elipse IDE?

    Publication Year: 2006, Page(s):76 - 83
    Cited by:  Papers (111)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (598 KB) | HTML iconHTML

    The Eclipse integrated development environment continues to gain popularity among Java developers. Our usage monitoring approach allows tool builders to sample how developers are using their tools in the wild. The data gathered about tool use can be used to prevent feature bloat and to evolve the environments according to user needs. Information about how developers work in a development environme... View full abstract»

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

    Publication Year: 2006, Page(s):84 - 92
    Cited by:  Papers (7)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1054 KB) | HTML iconHTML

    A software product "blueprint" let stakeholders view a software project's status at any point in the development. The work on requirements analysis and design when only the designers understand a software project's progress can be frustrating. Although a project leader should give progress presentations to stakeholders before the software is ready for demonstration, a presentation showing fragment... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Global technology transfer infrastructure is maturing

    Publication Year: 2006, Page(s):93 - 96
    Request permission for commercial reuse | PDF file iconPDF (109 KB) | HTML iconHTML
    Freely Available from IEEE
  • Experimental Software Engineering: A New Conference

    Publication Year: 2006, Page(s):98 - 99
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (184 KB) | HTML iconHTML

    An interesting issue facing software engineering relates to the evidence for adopting new techniques, tools, languages methodologies, and so on. We shouldn't always reject new models based on pure argument and logic, but ideally, we should subject such developments to some form of validation. The software engineering community has addressed this issue in part by the establishment of specialist con... View full abstract»

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

    Publication Year: 2006, Page(s):100 - 102
    Request permission for commercial reuse | PDF file iconPDF (68 KB) | HTML iconHTML
    Freely Available from IEEE
  • How Much of the Software Engineering Old Still Remains New?

    Publication Year: 2006, Page(s): 104
    Request permission for commercial reuse | PDF file iconPDF (199 KB) | HTML iconHTML
    Freely Available from IEEE
  • Real-Time Software Engineering, Part 1

    Publication Year: 2006, Page(s): c3
    Request permission for commercial reuse | PDF file iconPDF (35 KB) | HTML iconHTML
    Freely Available from IEEE

Aims & Scope

IEEE Software 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