for Journals by Title or ISSN
for Articles by Keywords
help
Followed Journals
Journal you Follow: 0
 
Sign Up to follow journals, search in your chosen journals and, optionally, receive Email Alerts when new issues of your Followed Journals are published.
Already have an account? Sign In to see the journals you follow.
Journal Cover
IEEE Software
Journal Prestige (SJR): 0.449
Citation Impact (citeScore): 2
Number of Followers: 162  
 
  Full-text available via subscription Subscription journal
ISSN (Print) 0740-7459
Published by IEEE Homepage  [191 journals]
  • Recognizing Excellence in High Performance Computing Nominations are
           Solicited for the Seymour Cray Sidney Fernbach & Ken Kennedy Awards
    • Abstract: Presents the guideilnes for the Seymour Cray Sidney Fernback and Ken Kennedy Awards.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • IEEE Computer Society
    • Abstract: Prospective authors are requested to submit new, unpublished manuscripts for inclusion in the upcoming event described in this call for papers.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • myCS
    • Abstract: Advertisement, IEEE.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • Being a Software Developer
    • Authors: Diomidis Spinellis;
      Pages: 4 - 7
      Abstract: If you want to be a professional developer, you'll need to continuously invest substantial time to acquire highly specialized knowledge and develop diverse cognitive and interpersonal skills. A university can kindle your passion and provide incentives to expand your horizons, and your employer may support specialized training. But in the end, becoming a professional software developer is your decision and responsibility.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • What Flows through a Software Value Stream'
    • Authors: Mik Kersten;
      Pages: 8 - 11
      Abstract: Most enterprise IT organizations don't have a well-defined productivity measure for what flows through their software production process. No clear consensus exists from academia or industry thought leaders on what constitutes software development productivity. Organizations know it when they see it-for example, through products that drive market adoption faster than others. But correlating development activities to those results has been more of an opaque art than a disciplined activity. To define productivity in a value stream, we must first define what flows.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • “It Depends”: Heuristics for Common-Enough Requirements
           Practice
    • Authors: Sarah Gregory;
      Pages: 12 - 15
      Abstract: How much diversity is permissible in requirements practices in a large corporation' Can different project teams legitimately use different elicitation methods, specification techniques, standards and checklists for reviews, and databases to manage content' Or is allowing any difference at all only inviting trouble' This instalment of the Requirements department shares how requirements specialists at Intel approach these questions through training, with a few examples of what they teach to better enable individuals and teams to continually improve their requirements engineering (RE) practice. It also discusses why practitioner engagement with the broader RE community is critical.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • Digital Transformation
    • Authors: Christof Ebert;Carlos Henrique C. Duarte;
      Pages: 16 - 21
      Abstract: This instalment of the Software Technology department discusses how the digital transformation is affecting software technology and the software industry.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • Software Engineering for Sustainability: Find the Leverage Points!
    • Authors: Birgit Penzenstadler;Leticia Duboc;Colin C. Venters;Stefanie Betz;Norbert Seyff;Krzsztof Wnuk;Ruzanna Chitchyan;Steve M. Easterbrook;Christoph Becker;
      Pages: 22 - 33
      Abstract: We as software engineers are responsible for the long-term consequences of the systems we design-including impacts on the wider environmental and societal sustainability. However, the field lacks analytical tools for understanding these potential impacts while designing a system or for identifying opportunities for using software to bring about broader societal transformations. This article explores how the concept of leverage points can be used to make sustainability issues more tangible in system design. The example of software for transportation systems illustrates how leverage points can help software engineers map out and investigate the wider system in which the software resides, such that we can use software as an effective tool for engineering a more sustainable world. This article is part of a theme issue on Process Improvement.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • Code Reviewing in the Trenches: Challenges and Best Practices
    • Authors: Laura MacLeod;Michaela Greiler;Margaret-Anne Storey;Christian Bird;Jacek Czerwonka;
      Pages: 34 - 42
      Abstract: Code review has been widely adopted by and adapted to open source and industrial projects. Code review practices have undergone extensive research, with most studies relying on trace data from tool reviews, sometimes augmented by surveys and interviews. Several recent industrial research studies, along with blog posts and white papers, have revealed additional insights on code reviewing “from the trenches.” Unfortunately, the lessons learned about code reviewing are widely dispersed and poorly summarized by the existing literature. In particular, practitioners wishing to adopt or reflect on an existing or new code review process might have difficulty determining what challenges to expect and which best practices to adopt for their development context. Building on the existing literature, this article adds insights from a recent large-scale study of Microsoft developers to summarize the challenges that code-change authors and reviewers face, suggest best code-reviewing practices, and discuss tradeoffs that practitioners should consider. This article is part of a theme issue on Process Improvement.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • 2019 IEEE-CS Charles Babbage Award
    • Pages: 43 - 43
      Abstract: Presents the guideilnes for the 2019 IEEE-CS Charles Babbage Award.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • Software-Intensive Product Engineering in Start-Ups: A Taxonomy
    • Authors: Eriks Klotins;Michael Unterkalmsteiner;Tony Gorschek;
      Pages: 44 - 52
      Abstract: Software start-ups are new companies aiming to launch an innovative product to mass markets fast with minimal resources. However, most start-ups fail before realizing their potential. Poor software engineering, among other factors, could be a significant contributor to the challenges that start-ups experience. Little is known about the engineering context in start-up companies. On the surface, start-ups are characterized by uncertainty, high risk, and minimal resources. However, such a characterization isn't granular enough to support identification of specific engineering challenges and to devise start-up-specific engineering practices. The first step toward an understanding of software engineering in start-ups is the definition of a Start-Up Context Map-a taxonomy of engineering practices, environment factors, and goals influencing the engineering process. This map aims to support further research on the field and serve as an engineering decision support tool for start-ups. This article is part of a theme issue on Process Improvement.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • Process Improvement Archaeology: What Led Us Here, and What’s
           Next'
    • Authors: Michael Unterkalmsteiner;Tony Gorschek;
      Pages: 53 - 61
      Abstract: While in every organization corporate culture and history change over time, intentional efforts to identify performance problems are of particular interest when trying to understand the current state of an organization. The results of past improvement initiatives can shed light on the evolution of an organization and represent, with the advantage of perfect hindsight, a learning opportunity for future process improvements. The opportunity to test this premise occurred in an applied research collaboration with the Swedish Transport Administration, the government agency responsible for the planning, implementation, and maintenance of long-term rail, road, shipping, and aviation infrastructure in Sweden. This article is part of a theme issue on Process Improvement.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • What We Know about Testing Embedded Software
    • Authors: Vahid Garousi;Michael Felderer;Çağrı Murat Karapıçak;Uğur Yılmaz;
      Pages: 62 - 69
      Abstract: To cost-effectively test embedded software, practitioners and researchers have proposed many test techniques, approaches, tools, and frameworks. However, obtaining an overview of the state of the art and state of the practice in this area is challenging for practitioners or new researchers. In addition, owing to an inadequate overview of what already exists in this area, some companies often reinvent the wheel by designing a test approach that's new to them but already exists. To address these problems, the authors conducted a systematic literature review of this area that covered the testing topics, testing activities, test artifacts, and industries on which the studies focused. The results can benefit both practitioners and researchers by serving as an index to the vast body of knowledge in this important, fast-growing area.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • A Framework for Determining Blockchain Applicability
    • Authors: Brian A. Scriber;
      Pages: 70 - 77
      Abstract: Researchers analyzed 23 blockchain implementation projects, each tracked for design decisions and architectural alignment showing benefits, detriments, or no effects from blockchain use. The results provide the basis for a framework that lets engineers, architects, investors, and project leaders evaluate blockchain technology's suitability for a given application. This analysis also led to an understanding of why some domains are inherently problematic for blockchains. Blockchains can be used to solve some trust-based problems but aren't always the best or optimal technology. Some problems that can be solved using them can also be solved using simpler methods that don't necessitate as big an investment.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • Software Analysis, Evolution, and Reengineering, and ICT Sustainability
    • Authors: Jeffrey Carver;Birgit Penzenstadler;Alexander Serebrenik;
      Pages: 78 - 80
      Abstract: This issue’s article reports on papers from the IEEE 25th International Conference on Software Analysis, Evolution, and Reengineering (SANER 18) and 5th International Conference on Information and Communications Technology for Sustainability (ICT4S 18).
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • What Do We (Really) Know about Test-Driven Development'
    • Authors: Itir Karac;Burak Turhan;
      Pages: 81 - 85
      Abstract: Test-driven development (TDD) involves more than just testing before coding. This article examines how (and whether) TDD has lived up to its promises. Test-driven development (TDD) is one of the most controversial agile practices in terms of its impact on software quality and programmer productivity.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • Design with Your Team, Not for Your Team
    • Authors: Michael Keeling;
      Pages: 86 - 88
      Abstract: There are two popular creation myths about software architectures: the Solitary Architect and the Emergent Architecture. These myths need to be replaced with new ones: the Architect as Coach and the Architect as Player-Coach.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • A Comet Revisited: Lessons Learned from Philaes Landing
    • Authors: András Balázs;
      Pages: 89 - 93
      Abstract: The Philae lander, part of the Rosetta program, was the first to land on and explore a comet. This article explores the lessons learned from the Philae team's experiences with problems that occurred in the hardware and software and in mission operations control.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • Connect on Interface
    • Pages: 94 - 94
      Abstract: Prospective authors are requested to submit new, unpublished manuscripts for inclusion in the upcoming event described in this call for papers.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • Blockchain-Enabled E-Voting
    • Authors: Nir Kshetri;Jeffrey Voas;
      Pages: 95 - 99
      Abstract: Blockchain-enabled e-voting (BEV) could reduce voter fraud and increase voter access. Eligible voters cast a ballot anonymously using a computer or smartphone. BEV uses an encrypted key and tamper-proof personal IDs. This article highlights some BEV implementations and the approach's potential benefits and challenges.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • One membership. Unlimited knowledge.
    • Pages: 100 - 100
      Abstract: Advertisement, IEEE.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
  • Nate Taggart on Serverless
    • Authors: Kishore Bhatia;
      Pages: 101 - 104
      Abstract: In this excerpt from Software Engineering Radio, Nate Taggart, cofounder and CEO of Stackery, discusses serverless—the ability to purchase function as a service in which the cloud provider assumes responsibility for providing a server and an execution environment on demand to run a piece of code. To hear the full interview, visit www.se-radio.net or access our archives via RSS at feeds.feedburner.com/se-radio.
      PubDate: July/August 2018
      Issue No: Vol. 35, No. 4 (2018)
       
 
 
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
Fax: +00 44 (0)131 4513327
 
Home (Search)
Subjects A-Z
Publishers A-Z
Customise
APIs
Your IP address: 54.80.83.123
 
About JournalTOCs
API
Help
News (blog, publications)
JournalTOCs on Twitter   JournalTOCs on Facebook

JournalTOCs © 2009-