The Community for Technology Leaders
Green Image
Issue No. 01 - January/February (2007 vol. 24)
ISSN: 0740-7459
pp: 5-7
Hakan Erdogmus , National Research Council Canada
As I step into my new role as editor in chief and reflect on my predecessors' achievements, the realization that I have pretty big shoes to fill is sinking in. The sentiment is a mix of anticipation and exhilaration. All right, I admit, throw some anxiety into the mix as well, but the healthy kind that comes over us when we're about to start something really worthwhile. In my first column, I'd like to give you a glimpse of what to expect in the foreseeable future.
What IEEE Software is about
IEEE Software is in the business of building the community of leading and future software practitioners. It delivers timely, reliable, relevant, and leading-edge content to its target audiences. It also translates software theory into practice. Striving to strike the delicate balance between research and practice, it transfers ideas, methods, and experiences across academic and industrial communities. The magazine has a wide scope spanning multiple levels and perspectives of software development, from programming concepts to process considerations, from technical topics to managerial issues. We address the art, science, and business of software development in the blurry intersection of three intertwined realms: computer science (languages, programming paradigms, and foundations), software engineering (processes, methods, and tools), and software practice (technology, human factors, and economics). What also makes the magazine unique is its ability to bridge and unify these realms.
Who we write for
The magazine targets four distinct audiences. The first is the learner-practitioner—software professionals who want to remain on the leading edge. The learner-practitioner can be anyone participating in software development in any role, from programmers to executives and from small to large organizations. The second audience is the grounded inventor—professionals, consultants, thought leaders, and academics who create new concepts, theories, and techniques. The third is the grounded scholar—academics and researchers who diligently study various aspects of software development. The fourth audience comprises grounded educators who wish to maintain their curriculum's relevance. The grounded inventor, scholar, and educator all have one common characteristic: they care about the learner-practitioner.
To satisfy our target audiences, IEEE Software's Editorial Board, with a lot of input from the Advisory Board and help from the staff, solicits and screens contributions. Together, we engineer the content to be informative, horizon-expanding, accessible, impartial, novel, and sophisticated—all to ensure that readers can continue to count on IEEE Software as their primary source of new ideas, expert opinion, and practical advice.
Themes to look forward to
Alongside timeless, traditional software development topics, current and emerging trends will play a significant role in influencing the content. As Brian Fitzgerald and Michael Lang rightly pointed out in the March/April 2005 issue ("Hypermedia Systems Development Practices: A Survey"), the way we understand and carry out software development has been undergoing a transformation, if not a major paradigm shift. Many of us are revisiting the ivory-tower view of software development as a strictly engineering or purely process-driven discipline; we can observe this view converging with global trends outside the software industry and giving rise to a holistic approach. Some manifestations are integration across and widespread awareness of previously disparate development activities and levels, the dismantling of traditional silos, mixing and consolidation of heavy and lightweight methods, fluidity of roles, and recognition of human, social, and economic factors. The magazine will provide balanced, intelligent perspectives about these ongoing developments that affect our industry.
We'll aim for more down-to-earth content, complementing the traditional process and management focus with technical topics. Thus, another important goal for the next few years will be to reorient the coverage toward issues fundamentally relevant to small and medium-size organizations as well as to individual developers. Revival of nuts-and-bolts topics that promote development of basic skills in coding, testing, design, modeling, and requirements is part of the plan. We'll also cover budding, advancing, and changing software technology, including languages, frameworks, and environments.
On the human-factors side, expect to see contemporary discussions on managing knowledge workers and software teams, software development roles and responsibilities, collaboration, distributed development, and responding to end-user and customer needs.
Of course, alongside all this, we'll continue to address current process and managerial issues as well as business and economic aspects of our industry.
Toward better fulfillment of the magazine's unique role as a bridge between research and practice, we are planning to introduce a new department that summarizes important empirical results from scrutinized studies of software practices, processes, methods, and technologies. The department will primarily offer practical synthesis articles that communicate research findings from multiple studies in a compact, objective, and accessible way.
You'll see articles on the topics we've been addressing in recent theme issues, topics you'll want to stay current in: aspect orientation, model-driven approaches, open source, global software development, requirements engineering, software quality and testing, component-based approaches, integration and inter-operability, and software economics. We're also planning to build on topics we've partially addressed in recent departments—through new feature articles and special issues. These topics include service-oriented approaches, test-driven approaches, software development in small and medium-size enterprises, software teams, lightweight modeling approaches, dynamic languages, frameworks, rapid application development, evolutionary design, quantitative software processes, development infrastructures, and software patterns. Longer-term plans include coverage of software engineering techniques for selected, red-hot domains. Finally, we'll keep our eyes and ears open for opportunities in yet-uncharted territories: given the head-spinning pace of our industry, we'll maintain sufficient flexibility to incorporate unforeseen topics into our calendar as they emerge.
New in this issue
To be able to cover the wide spectrum of topics planned, the Editorial Board will also enjoy an expansion. Incoming associate editors will supplement our pillar areas of requirements, design, quality, and management with new editorial areas. These include social and human factors; processes and practices; programming paradigms and languages; distributed and enterprise software; development infrastructures; and empirical results.
A new column, Not Just Coding, by J.B. Rainsberger debuts this month. J.B. maintains that most "programming" happens while the programmer isn't coding. He refutes the notion that programming is "turning some smart person's specification and design into code." In Not Just Coding, J.B. encourages programmers to reach out beyond writing code to contribute in other ways to the success of their projects and teams. J.B.'s column will appeal to programmers of all levels. By addressing issues that fall outside the traditionally narrow perspective of programming, it will help developers who take pride in their work look at the array of issues and activities that make or break software projects, from conception to delivery and beyond.
Happy reading!
90 ms
(Ver 3.3 (11022016))