By Topic

IEEE Software

Issue 1 • Jan.-Feb. 2008

Filter Results

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

    Publication Year: 2008, Page(s): c1
    Request permission for commercial reuse | PDF file iconPDF (2328 KB)
    Freely Available from IEEE
  • John Wiley & Sons [advertisement]

    Publication Year: 2008, Page(s): c2
    Request permission for commercial reuse | PDF file iconPDF (142 KB)
    Freely Available from IEEE
  • Software Editorial Calendar

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

    Publication Year: 2008, Page(s):2 - 3
    Request permission for commercial reuse | PDF file iconPDF (838 KB)
    Freely Available from IEEE
  • So Many Languages, So Little Time

    Publication Year: 2008, Page(s):4 - 6
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (312 KB) | HTML iconHTML

    What's up and coming in the programming language arena? A rudimentary analysis of the 200+ sessions' titles and abstracts at OOPSLA 07 (22nd Int'l Conf. Object-Oriented Programming, Systems, Languages, and Applications) provides a rough idea of what's happening with object-oriented, functional, dynamic, and domain-specific languages. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software Development Tools Call for Papers / Gannon University [advertisement]

    Publication Year: 2008, Page(s): 7
    Request permission for commercial reuse | PDF file iconPDF (162 KB)
    Freely Available from IEEE
  • Morality and the Software Architect

    Publication Year: 2008, Page(s):8 - 9
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (253 KB) | HTML iconHTML

    The author poses the question:is there a moral dimension to developing software? Should software architects have a professional code of ethics? As Bjarne Stroustrup has pointed out, our civilization runs on software. We as a professional community have developed technology that has changed the way individuals live, businesses operate, communities interact, and nations and civilizations thrive and ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Security for the Rest of Us: An Industry Perspective on the Secure-Software Challenge

    Publication Year: 2008, Page(s):10 - 12
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1129 KB) | HTML iconHTML

    While security was once a specialty of interest to only a few programmers, it's now a critical topic for almost all software engineers, project managers, and decision makers. Getting security right is hard because an attacker—having virtually unlimited time—needs to find only one vulnerability in a system to succeed, whereas the defender—constrained in time—must ens... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Java Insecurity: Accounting for Subtleties That Can Compromise Code

    Publication Year: 2008, Page(s):13 - 19
    Cited by:  Papers (5)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (304 KB) | HTML iconHTML

    Conscientious Java developers are typically aware of the numerous coding guidelines that they should follow when writing code, such as validating inputs, minimizing accessibility to classes and members, and avoiding public static nonfinal fields. Java developers follow such guidelines to avoid common programming pitfalls (often called antipatterns), thereby reducing the likelihood of bugs or secur... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Security Requirements for the Rest of Us: A Survey

    Publication Year: 2008, Page(s):20 - 27
    Cited by:  Papers (36)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (429 KB) | HTML iconHTML

    Most software developers aren't primarily interested in security. For decades, the focus has been on implementing as much functionality as possible before the deadline, and patching the inevitable bugs when it's time for the next release or hot fix. However, the software engineering community is slowly beginning to realize that information security is also important for software whose primary func... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Threat Modeling: Diving into the Deep End

    Publication Year: 2008, Page(s):28 - 34
    Cited by:  Papers (8)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (529 KB) | HTML iconHTML

    Optimizing the working relationship between a company's IT security (ITS) group and its internal business customers is difficult at best. Who is responsible for security? What does "responsible" mean? For that matter, what does "security" mean? If ITS is solely responsible for security, as is often the case, then everything across the board will likely receive the same level of protection. In thei... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Cybersecurity Economic Issues: Clearing the Path to Good Practice

    Publication Year: 2008, Page(s):35 - 42
    Cited by:  Papers (13)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (506 KB) | HTML iconHTML

    Software project managers have limited project resources. Requests for security improvements must compete with other requests, such as for new tools, more staff, or additional testing. Deciding how and whether to invest in cybersecurity protection requires knowing the answer to at least two questions: What is the likelihood of an attack, and what are its likely consequences? Security analysts unde... View full abstract»

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

    Publication Year: 2008, Page(s):43 - 45
    Cited by:  Papers (5)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (623 KB) | HTML iconHTML

    Emotional requirements must contain at least two elements: the game designer's intent (that is, the target emotional state) and the means by which the game designer expects (requires) the production team to induce that emotional state in the player. We can consider an emotional state such as happiness as universal, but the way you induce happiness isn't. Emotional requirements need context: classi... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Model-Driven Development in the Enterprise

    Publication Year: 2008, Page(s):46 - 49
    Cited by:  Papers (10)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (240 KB) | HTML iconHTML

    For decades, model-driven development has been the perfect example of software-engineering hype. Just as bees are attracted to honey, we software engineers look for ways of simplifying our work and automating endless change cycles. Today, after many years of experimenting with MDD, mostly in limited-size scientific environments, the three ingredients of methodology, notation, and tools seem to fit... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Ambiguous Business Value Harms Software Products

    Publication Year: 2008, Page(s):50 - 51
    Cited by:  Papers (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (339 KB) | HTML iconHTML

    Business value is something that delivers profit to the organization paying for the software in the form of an increase in revenue, an avoidance of costs, or an improvement in service. This is the dusty IRACIS (increase revenue, avoid costs, improve service) idea from Chris Gane and Trish Sarson's 1977 book Structured Systems Analysis (McDonnell Douglas Information). View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Are You Done Yet?

    Publication Year: 2008, Page(s):52 - 53
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (207 KB) | HTML iconHTML

    The single biggest wedge between programmer and manager is arguing over the schedule. Johanna Rothman provides a managerís perspective on how programmers and managers can collaborate effectively. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Tests and Requirements, Requirements and Tests: A Möbius Strip

    Publication Year: 2008, Page(s):54 - 59
    Cited by:  Papers (13)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (380 KB) | HTML iconHTML

    Writing acceptance tests early is a requirements engineering technique that can save time and money and help businesses better respond to change. We believe that concrete requirements blend with acceptance tests in much the same way as the two sides of a strip of paper become one side in a Mobius strip. In other words, requirements and tests become indistinguishable, so you can specify system beha... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Agile Requirements Engineering Practices: An Empirical Study

    Publication Year: 2008, Page(s):60 - 67
    Cited by:  Papers (77)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (602 KB) | HTML iconHTML

    An analysis of data from 16 software development organizations reveals seven agile RE practices, along with their benefits and challenges. The rapidly changing business environment in which most organizations operate is challenging traditional requirements-engineering (RE) approaches. Software development organizations often must deal with requirements that tend to evolve quickly and become obsole... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Managing Agile Project Requirements with Storytest-Driven Development

    Publication Year: 2008, Page(s):68 - 75
    Cited by:  Papers (10)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1027 KB) | HTML iconHTML

    Storytest-driven development is a complementary form of test-driven development (TDD) applied to overall system development. Using FitLibrary eases storytest-driven development, which brings together requirements and automated testing ideas and practices to support agile software development. Storytest-driven development helps bridge the gap between what organizations really need from a system and... View full abstract»

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

    Publication Year: 2008, Page(s):76 - 77
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (190 KB) | HTML iconHTML

    One of the favorite activities in any of the architecture or design courses is to discuss antipatterns - design ideas hatched with good intentions that prove problematic over time. The few books on antipatterns focus primarily on introducing problems and straightforward solutions, which makes them hard to distinguish from better-known books that present design or programming guidelines or refactor... View full abstract»

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

    Publication Year: 2008, Page(s):78 - 79
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (189 KB) | HTML iconHTML

    Metaprogramming, using programs to manipulate other programs, is as old as programming. From self-modifying machine code in early computers to expressions involving partially applied functions in modern functional-programming languages, metaprogramming is an essential part of an advanced programmer's arsenal. Everyday metaprogramming involves on-the-fly code production. Representative examples inc... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • VIRE: Sailing a Blue Ocean with Value-Innovative Requirements

    Publication Year: 2008, Page(s):80 - 87
    Cited by:  Papers (8)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (530 KB) | HTML iconHTML

    Value-innovative requirements engineering guides software development organizations in creating new markets based on new product values for potential customers. Most requirements-engineering techniques and practices focus on eliciting requirements from existing, known customers. However, these techniques and practices aren't sufficient for surviving in current highly competitive markets. In partic... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Inspecting the History of Inspections: An Example of Evidence-Based Technology Diffusion

    Publication Year: 2008, Page(s):88 - 90
    Cited by:  Papers (5)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (754 KB) | HTML iconHTML

    If we're going to have a column about evidence in software engineering, we're going to need to talk about inspections sooner or later. Inspections are among the most mature and perhaps best-studied practices in software engineering. In short, software inspection was one of those rare software engineering innovations that had the ability to effect real process change. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • No Silver Bullet: Software Engineering Reloaded

    Publication Year: 2008, Page(s):91 - 94
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (606 KB) | HTML iconHTML

    A celebratory panel took place at the 22nd International Conference on object-oriented programming, systems, languages, and applications in Montreal. The occasion was the 20th anniversary of Fred Brooks' paper "no silver bullet: essence and accidents of software engineering." Fred suggested that useful solutions must address inherent complexity observing that object-oriented techniques have come c... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Intuition's Role in Decision Making

    Publication Year: 2008, Page(s): 96
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (192 KB) | HTML iconHTML

    Intuition might be a better decision-making approach for software engineering than you suppose. View full abstract»

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

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