Software development: science,craft or racket?

In the past, software development has been variously described as a science, art, craft, trade, racket, etc. Even today opinions vary considerably about how software should he developed and what qualifications are most appropriate for software developers.In the article the problematic state of affairs in the field of software development today is illustrated. The spectrum of possible software worlds of the future is characterized by its three extremes: an audacious (reckless), a backward (reactionary) and a celestial radical) software future.It is argued that the detailed specification, design and development of computer software is by nature an engineering field. In practice, however, software development is too often treated today as patchwork, conducted by underqualified personnel instead of by professionally educated engineers. This is the major cause of many problems and disappointments that we have been and still are experiencing in applying computer systems.     

Software architectures: Blueprint,Literature, Language or Decision?

This study questions the traditional view of software architecture as a specification that needs only be understood by software architects and engineers. Based on an intensive study of three software-producing organizations, we identify multiple metaphors (‘Blueprint,’ ‘Literature,’ ‘Language’ and ‘Decision’) that stakeholders use to understand the term software architecture, which in turn, allows them to effectively participate in its creation and use. Our results point to new research directions that may better encompass a broader view of software architecture.     

Software Development Effort Estimation: Formal Models or Expert Judgment?

Which is better for estimating software project resources: formal models, as instantiated in estimation tools, or expert judgment? Two luminaries, Magne Jørgensen and Barry Boehm, debate this question.     

Ultralarge Systems: Redefining Software Engineering?

The harbingers of ultralarge systems are indeed emerging, although their elements seem contradictory to the "ultralarge" concept. ULS design will have to move beyond computer science and electrical and electronics engineering-based methodologies to include building blocks from seven major research areas: human interaction; computational emergence; design; computational engineering; adaptive system infrastructure; adaptable and predictable system quality; and policy, acquisition, and management. We need to integrate these more novel approaches with the tools and techniques of traditional software engineering, especially with regard to formal methods and to dealing with predictability and uncertainty in high-integrity software systems. Our view is not so much that we are 'redefining' software engineering but rather that we're looking to extend established software engineering tools and techniques in novel and useful ways.     

Evaluating Anti-Virus Software: Which Is Best?

Abstract

A few years ago, computer securitymeant protecting yourself fromviruses and changing passwords.Today, computer security is much morecomplex and viruses have fallen to the back-ground. So how does one chose the bestvirus product today? What does one lookfor? This article provides some insight andsuggestions.     

Software Metrics: Progress after 25 Years?

This article traces the increasing sophistication and use of software measurement over the past 25 years. It highlights four obstacles to more effective use of measurement: dealing with uncertainty, anticipating change, measuring soft characteristics, and developing heuristics.     

Licensing Software Engineers?

To further your professional development, should you aim to become a licensed professional software engineer? The author answers this question, as well as questions about when and where licensing is important.     

Computer Scientist, Software Engineer, or IT Professional: Which Do You Think You Are?

Job titles and functions shift quickly in the IT world, but some broad classifications can be useful for identifying what people do and how they view themselves. In some ways, the category of IT professional is the most broadly encompassing, but many people identify more closely with subspecialties such as software engineer or computer scientist.     

Rechtsrisiko Open Source Software?

Ohne Zusammenfassung     

Software: What's In It and What's It In?

IEEE Software's new series of Impact columns intends to get a better quantitative insight into the impact of software on various businesses. This introduction describes the reasoning behind the columns. All contributors will be asked to quantify the size (in lines of code or another size measure) and volume (number of copies sold per year or another measure) of their projects. This should allow the software developers to position and compare the experiences coming out of the different industries. We hope to publish three to six columns a year and to solicit submissions as momentum grows. Both engineering managers and business managers are encouraged to submit a column. We've already lined up the first columns with submissions from the mobile phone, computer and automotive industries. Our proposal's wide scope should let us accept contributions from large or small programs, low or high volume projects, open or closed source projects, embedded or commercial-off-the-shelf software, and in-house or outsourced software development.     

Moving or Merging IT Departments? The Hardware and Software are the Easy Parts

Although the technical complications in moving or merging a data or telecom department are considerable, it is the human considerations that are most important and critical to the success of the change. This article shows several methods for handling these issues, with real world examples, in order to prevent problems with the change.Eric Klein has an MS degree in information systems and a BBA degree in management information systems, both from Pace University, New York, USA. He has taught classes at both the undergraduate and graduate level at Pace University in New York, USA, the Academic College of Tel Aviv-Yaffo, Israel, and Polytechnic University, Israel in Practical Networking.His practical experience in management consulting is from his experiences at Moran Stahl & Boyer in New York, and as a Senior Technical Consultant for MCI. He is a member of the ISOC, the IETF (IPv6, Evolution of SNMP, SNMP Version 3, and IPv6 Operations working groups where he is co-author of, draft-ietf-v6ops-nap-01.txt in the IPv6 OPS) and the IEC.     

余额宝:包容or取缔? 放任or监管?

正在包容、支持的政策下,重视监管层面的改革与创新,相信互联网金融将迎来健康发展的光明前景。一石激起千层浪,余额宝引发大论战近期,央视证券资讯频道执行总编辑兼首席新闻评论员钮文新发表名为《取缔余额宝》的文章。在文章中,钮文新表示,余额宝不仅冲击银行,更冲击全社会的融资成本和国家经济安全。"当余额宝和其前端的货币基金将2%的收益放入自己兜里,而将4%到6%的收益分给成千上万的余额宝客户的时候,整个中国实体经济、也就是最终的贷款客户将成为这一成本的最终买单人。"与此同时,他将余额宝和银行做比较,表示银行是通过经营贷款风险之后才获得的风险收益;而余额宝"睡着觉就可以从240亿元的收益中分走80亿元,而且风险比打劫还小。"     

Must Software Research Stand Divided?

A not-so-subtle divide separates empirical and constructionist software research. Constructionists maintain that software research should be about creating technologies, devising new methods. Empiricists are interested in studying and understanding existing approaches. The antagonism between the two camps does not serve our industry well—it needs both modes of research.     

Software — A performing science?

Technical issues are important for software work, but so are personal disciplines, teamworking skills, and application‐domain knowledge. Also, much like an artistic performance, first‐class software engineering requires constant practice, good technique, and effective coaching. The challenge of producing high‐quality large‐scale software products is substantial today and will be even more demanding in the future. Without concerted action, we cannot expect software organizations' capabilities to improve. To address these problems, the Software Engineering Institute (SEI) has developed the Personal Software Process (PSP) and the Team Software Process (TSP). This paper addresses the problems of software engineering and discusses the intellectual nature of software work. It then reviews the characteristics of this kind of work and describes the principal conditions for effective software performance. In the conclusion, the author makes some observations about the challenges ahead and the future actions required. This revised version was published online in June 2006 with corrections to the Cover Date.     

Concepts: Stored or Created?

Are concepts stable entities, unchanged from context to context? Or rather are they context-dependent structures, created on the fly? We argue that this does not constitute a genuine dilemma. Our main thesis is that the more a pattern of features is general and shared, the more it qualifies as a concept. Contextualists have not shown that conceptual structures lack a stable, general core, acting as an attractor on idiosyncratic information. What they have done instead is to give a contribution to the comprehension of how conceptual structure organized around such a stable core can produce contextually appropriate representations on demand.     

公有云:美酒or毒药?

<正>几大国际巨头争相布局,公有云市场变幻莫测,而无论这块市场是美酒还是毒药,他们都在翘首期盼。随着"双11"的胜利落幕,关于公有云的争论又甚嚣尘上,好像"得公有云者得天下",今天还没有跳入公有云的I T厂商好像都是"痴汉"。到底公有云的真实机会在哪里?公有云到底是美酒还是毒药?自从几大公有云巨头开始布局中国市场,包括亚马逊、微软、阿里巴巴、