Journal Cover
IEEE Software
Journal Prestige (SJR): 0.449
Citation Impact (citeScore): 2
Number of Followers: 222  
 
  Full-text available via subscription Subscription journal
ISSN (Print) 0740-7459
Published by IEEE Homepage  [191 journals]
  • [Front cover]
    • Abstract: Presents the front cover for this issue of the publication.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • IEEE Computer Society Information
    • Abstract: Provides a listing of current committee members and society officers.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • IEEE Job Boards
    • Abstract: Advertisement, IEEE.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • What Should a Software Engineer Know'
    • Authors: Ipek Ozkaya;
      Pages: 3 - 6
      Abstract: A Software Engineer applies the principles of engineering to the design, development, maintenance, testing, and evaluation of a softwareenabled system. While this fundamental understanding of what a software engineer does is commonly shared, the journey to understand what a software engineer should know evolves, mostly as a consequence of the rapid pace of technological changes.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • Staff Listing
    • Pages: 4 - 5
      Abstract: Provides a listing of current staff, committee members and society officers.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • Pervasive Computing Call For Articles
    • Pages: 6 - 6
      Abstract: Prospective authors are requested to submit new, unpublished manuscripts for inclusion in the upcoming event described in this call for papers.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • Software Engineering in Society
    • Authors: Rick Kazman;Liliana Pasquale;
      Pages: 7 - 9
      Abstract: Modern Software Systems pervade our lives. They have become more open and hyperconnected, manage large amounts of our personal data, and are used to support the lives of individuals and communities and the functions of businesses and governments. They are a part of our society and play an important role in shaping it.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • Gender Diversity and Community Smells: Insights From the Trenches
    • Authors: Gemma Catolino;Fabio Palomba;Damian A. Tamburri;Alexander Serebrenik;Filomena Ferrucci;
      Pages: 10 - 16
      Abstract: Given growing attention to gender diversity in software development teams, we asked practitioners if it was a useful tool to mitigate undesirable communication patterns. While many participants didn't consider gender diversity useful in this context, those who did were motivated by their own professional experience.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • Critical Requirements Engineering in Practice
    • Authors: Leticia Duboc;Curtis McCord;Christoph Becker;Syed Ishtiaque Ahmed;
      Pages: 17 - 24
      Abstract: Software can raise issues about ethics, power, politics, and values. We show how Critical Systems Heuristics can be used to structure explorations of early requirements and provide a framework for developing a reflective understanding for justifying the project and system scope.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • IEEE Transactions on Sustainable Computing
    • Pages: 24 - 24
      Abstract: Prospective authors are requested to submit new, unpublished manuscripts for inclusion in the upcoming event described in this call for papers.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • Taking the Middle Path: Learning About Security Through Online Social
           Interaction
    • Authors: Tamara Lopez;Thein T. Tun;Arosha K. Bandara;Mark Levine;Bashar Nuseibeh;Helen Sharp;
      Pages: 25 - 30
      Abstract: Integrating security into software development involves more than learning principles or applying techniques. Security can be integrated into software development practice by following a middle path, through which developers draw together knowledge received through training and software development techniques.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • Bug Bounty Programs for Cybersecurity: Practices, Issues, and
           Recommendations
    • Authors: Suresh S. Malladi;Hemang C. Subramanian;
      Pages: 31 - 39
      Abstract: Drawing upon crowdsourcing, bug bounty programs (BBPs) are entering the mainstream security practice in organizations. We analyze and recommend best practices in five main BBP areas: scoping of BBPs, timing of crowd engagement, submission quality, firm-researcher communication, and hacker motivation.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • A Taxonomy to Assess and Tailor Risk-Based Testing in Recent Testing
           Standards
    • Authors: Juergen Grossmann;Michael Felderer;Johannes Viehmann;Ina Schieferdecker;
      Pages: 40 - 49
      Abstract: This article provides a taxonomy for risk-based testing that serves as a tool to define, tailor, or assess such approaches. In this setting, the taxonomy is used to systematically identify deviations between the requirements from public standards and the individual testing approaches.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • Transactions on Computers Call for Papers
    • Pages: 49 - 49
      Abstract: Prospective authors are requested to submit new, unpublished manuscripts for inclusion in the upcoming event described in this call for papers.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • Games for Requirements Engineers: Analysis and Directions
    • Authors: Fabiano Dalpiaz;Kendra M.L. Cooper;
      Pages: 50 - 59
      Abstract: The requirements engineering (RE) discipline keeps evolving to cope with increasingly complex systems and shorter development cycles. Using a lightweight analysis framework, we review the current landscape of games for RE and provide guidance for the practitioner interested in improving their skills using innovative game-based RE.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • A Tool for Generating Health Applications Using Archetypes
    • Authors: Andre Araujo;Valeria Times;Marcus Silva;
      Pages: 60 - 67
      Abstract: Template4EHR is a to ol for the dynamic creation of data schemas for electronichealth-record storage and user creation and customization of graphical user interfaces. In experimental tests with IT and health professionals, Template4EHR obtained an 81.22% satisfaction rate.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • Transactions on Big Data
    • Pages: 67 - 67
      Abstract: Prospective authors are requested to submit new, unpublished manuscripts for inclusion in the upcoming event described in this call for papers.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • Shu-Ha-Ri for RE' An Agile Approach to Requirements Engineering
           Practitioner Maturity
    • Authors: Sarah Gregory;
      Pages: 68 - 71
      Abstract: An interesting phenomenon occurred a couple of months ago when I elicited thoughts and feedback on meaningful requirements engineering (RE) metrics from a few RE practitioners and peers. Project teams across industry are often expected to put forth some sort of indicators for management indicating that their company's investment in the work of writing requirements provides some sort of payoff in the end. As I began my career in RE, I pored over a study from Raytheon1 that comfortably concluded that yes, it is far better to discover lack of alignment or shared understanding in what a team is to develop early. Defects cost less to fix when the system to be released is still in its definition phases, rather than when development hours have been expended, when potential releases are being tested, and certainly before a product is released to its customers as complete. The cost of quality in the form of better practice is lower than the cost of cleanup later.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • Practices and Tools for Software Start-Ups
    • Authors: Gislaine Camila Lapasini Leal;Rafael Prikladnicki;Christof Ebert;Renato Balancieri;Leandro Bento Pompermaier;
      Pages: 72 - 77
      Abstract: Software start-ups have become increasingly important to the economy and are a key to innovation. However, these companies face many challenges, such as balancing short-term and future needs with respect to technology, processes, and tools.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • Trends in Agile: Business Agility
    • Authors: Rafael Prikladnicki;Casper Lassenius;Jeffrey C. Carver;
      Pages: 78 - 80
      Abstract: The agile conference (http://www.agilealliance.org/agile2019/) is the largest global symposium on agile software development, catering particularly to practitioners. Agile 2019, held 5-9 August in Washington, D.C., drew more than 2,400 participants.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • IEEE Security and Privacy Magazine Subscribe
    • Pages: 80 - 80
      Abstract: Advertisement, IEEE.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • The Five Laws of SE for AI
    • Authors: Tim Menzies;
      Pages: 81 - 85
      Abstract: It is time to talk about software engineering (SE) for artificial intelligence (AI). As shown in Figure 1, industry is becoming increasingly dependent on AI software. Clearly, AI is useful for SE. But what about the other way around' How important is SE for AI' Many thought leaders in the AI industry are asking how to better develop and maintain AI software (see Figure 2).
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • Stay Connected
    • Pages: 86 - 86
      Abstract: Advertisement, IEEE.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • Emerging Trends, Challenges, and Experiences in DevOps and Microservice
           APIs
    • Authors: Uwe Zdun;Erik Wittern;Philipp Leitner;
      Pages: 87 - 91
      Abstract: In August 2019, we organized the second Vienna Software Seminar (VSS) with the topic "DevOps and Microservice APIs."1 Embracing the positive reception of its first iteration in 2017,2 VSS is an opportunity for attendees to discuss recent software technologies, practices, and related research. The seminar's 34 participants included a mix of practitioners and academics, who were invited based on their roles and experiences. The explicit intention of the seminar was to provide ample opportunities for exchange and communication: six themed sessions consisted of one invited keynote and two lightning talks, giving different perspectives on the session's topic and (ideally) sparking ideas for follow-up discussions. After the talks, all participants decided on subtopics for two to three breakout sessions (i.e., informal, self-organized discussions among interested participants). Breakout session topics included microservice security, tooling for application programming interface (API) evolution, serverless programming models, and identification of microservices using domaindriven design. The sessions provided opportunities for detailed discussions and identifying challenges to address in future collaborations. Toward the end of each session, all participants gathered once more to summarize the breakout discussions. Additional opportunities for communication were provided during shared lunch breaks and social events in the evenings.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • Between the Waterfall Wasteland and the Agile Outback
    • Authors: Eltjo Poort;
      Pages: 92 - 97
      Abstract: In the past decade, we have seen a significant shift in attitudes toward the architect’s role. Many organizations now prefer to allocate the responsibility for major design decisions not to an architect but to teams without a named architect. Sometimes the roles on such teams are identified by such terms as pathfinder, master builder, ninja developer, or steward. Some of these roles appear to be merely euphemisms to avoid the (in some circles, dreaded) A-word, but others represent a genuinely different way of looking at architectural responsibilities. In this article, I will share some insights about this shift. These have been gained by a small group of instructors teaching more than 1,400 architects in dozens of organizations across the globe.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • IEEE Computer Society
    • Pages: 97 - 97
      Abstract: Prospective authors are requested to submit new, unpublished manuscripts for inclusion in the upcoming event described in this call for papers.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
  • Justin Richer on OAuth
    • Authors: Gavin Henry;
      Pages: 98 - 100
      Abstract: In Episode 376 of “Software Engineering Radio,” Justin Richer, lead author of OAuth2 in Action and editor of OAuth extensions RFC 7591, 7592, and 7662, discusses the key technical features of the OAuth 2.0 protocol for authorization. Gavin Henry spoke with Richer about browser-based OAuth2, types of tokens, OpenID Connect, PKCE, JavaScript Object Notation Web Token pros and cons, where to store them, client secrets, single-page apps, mobile apps, current best practices, OAuth.XYZ, HEART, MITREid, token validation, dynamic client registration, the decision factors of the various types of authorization grants to use, and what is next for OAuth. To hear the full interview, visit http://www.se-radio.net or access our archives via RSS at http:// feeds.feedburner.com/se-radio.
      PubDate: Jan.-Feb. 2020
      Issue No: Vol. 37, No. 1 (2020)
       
 
JournalTOCs
School of Mathematical and Computer Sciences
Heriot-Watt University
Edinburgh, EH14 4AS, UK
Email: journaltocs@hw.ac.uk
Tel: +00 44 (0)131 4513762
 


Your IP address: 18.206.12.79
 
Home (Search)
API
About JournalTOCs
News (blog, publications)
JournalTOCs on Twitter   JournalTOCs on Facebook

JournalTOCs © 2009-