End to end security is becoming a prerequisite of the Internet of Things. Data must be managed securely at generation, in flight and at rest to avoid critical enterprise or personal data being intercepted. Privacy becomes paramount as our lives and health become increasingly digital, and devices must evolve to deliver security and robustness while pricing continues to be constrained. This talk will highlight the security requirements of the IoT as outlined by the Dept. of Homeland Security and the UK Centre for Protection of National Infrastructure to counter the emergence of threats ranging from advanced persistent software threats to physical tampering and side channel attacks. Following the definition of the attack threats we will then establish the definition of advanced device security features, system implementation requirements and testability criteria to develop Security by Design within the Internet of Things.

The quality of empirical studies is critical for the success of the Software Engineering (SE) discipline. More and more SE researchers are conducting empirical studies involving the software industry. While there are established empirical procedures, relatively little is known about the dynamics of conducting empirical studies in the complex industrial environments. What are the impediments and how to best handle them? This was the primary driver for organising CESI 2013. The goals of this workshop include having a dialogue amongst the participating practitioners and academics on the theme of this workshop with the aim to produce tangible output that will be summarised in a post-workshop report.

This study summarizes results of a study of the internal, structural quality of 288 business applications comprising 108 million lines of code collected from 75 companies in 8 industry segments. These applications were submitted to a static analysis that evaluates quality within and across application components that may be coded in different languages. The analysis consists of evaluating the application against a repository of over 900 rules of good architectural and coding practice. Results are presented for measures of security, performance, and changeability. The effect of size on quality is evaluated, and the ability of modularity to reduce the impact of size is suggested by the results.

This paper describes lessons learned during the author's five lives in technology transfer. The author's first life came in General Electric's Space Division where he performed research on software metrics and structured programming, and transferred technology to the pages of technical journals. His second life came at ITT's Programming Technology Center where he was responsible for transferring software measurement practices into common use across ITT's worldwide software operations. Some measurement initiatives survived, but most were short-lived. His third life came in MCC's Human Interface Laboratory and Software Technology Program. MCC's member companies were only occasionally able to transfer the advanced technology they challenged MCC to produce. His fourth life came in directing the Software Process Program at the Software Engineering Institute where he led the team that produced the Capability Maturity Model. Although the CMM's transfer was occasionally too rapid to control, the CMM suggested that you should transfer no technology before its time. The author's fifth and current life involves co-founding TeraQuest and helping companies to improve their software development capability. The paper includes twenty-five lessons in technology transfer and one model.

No abstract available.

The data being reported from successful software process improvement projects indicates that the quality of the process is an important predictor of the organization's ability to deliver high quality products on schedule and within budget.Although process improvement does not offer an order of magnitude improvement overnight, it does yield consistent results that accrue steadily over the long term.Software organizations in companies such as Hughes Aircraft, Motorola, Raytheon, Ericsson, and Boeing have undertaken serious software process improvement programs and reported between an average of 6 to 1 returns on their investment in improvement activities.This tutorial will describe the problems these programs are designed to solve.It will provide a brief overview of the Capability Maturity Model which has proven to be a successful improvement model.Methods for conducting successful process improvement programs will be described, and lessons learned horn several such programs will be shared.The tutorial will conclude with a description of the software productivity and quality benefits experienced in successful improvement programs.

The software process movement is described. Organization-wide software processes and the maintenance of defined software processes are considered. It is suggested that the software process movement will find the software maintenance community directly in its mainstream. Even more important, the maintenance community is about to face a double challenge. First, it must struggle to adopt more effective processes, and the Capability Maturity Model offers some guidance in doing so. Second, the software maintenance community must bring its considerable skills and experience to the process community's aid in determining how best to maintain the processes defined for software organizations.>

article Free Access Share on CHI research at MCC Authors: J. Hollan Microelectronics and Computer Technology Corporation Microelectronics and Computer Technology CorporationView Profile , B. Curtis Microelectronics and Computer Technology Corporation Microelectronics and Computer Technology CorporationView Profile Authors Info & Claims ACM SIGCHI BulletinVolume 20Issue SIMarch 1989 pp 147–149https://doi.org/10.1145/67450.67479Published:01 March 1989Publication History 0citation237DownloadsMetricsTotal Citations0Total Downloads237Last 12 Months14Last 6 weeks1 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF

No abstract available.

A verbal protocol study of professional software designers has revealed three design process control strategies. At least one of them, the generation of opportunistic solutions at different levels of detail accompanied by problem domain modeling, had not been observed in previous empirical studies nor had been acknowledged in the software engineering practices. Specific breakdowns (difficulties) were associated with the different design process control strategies. Software tools should be provided to designers to alleviate these breakdowns. Parts of a cognitive model of software design, based on distributed control from specialists such as design schemas, design heuristics, and design methods, are presented to account for the observed control strategies.

No abstract available.

Much of the work in the field of computer human interaction consists of finding out what is wrong with existing interfaces or which of several existing alternatives is better. Over the next few decades, the possibilities for computer human interaction will explode. This will be due to: 1) continued decrease in the costs of processing and memory, 2) new technologies being invented and existing technologies (e.g., handwriting recognition, speech synthesis) being extended, 3) new applications and 4) new ideas about how people can interact with computers.

No abstract available.

Research issues concerning human interaction with computers have become crucial because of dramatic increases in the number of computer users who have no formal mathematical, engineering, or computer science training. This review focuses on the state of the art in Software Psychology--the study of human factors in computer systems. One area of software psychology, the psychology of programming, is picked for an in-depth discussion of research results. This area was selected for its interest to the readers of the PROCEEDINGS OF THE IEEE. The review then discusses the methodological issues involved in performing experimental research in software psychology. Future trends are discussed both for the programming research reviewed here and for the whole field of software psychology. The conclusions identify multidisciplinary training and research as critical to further progress in this field.

This paper presents a partial review of the human factors work on computer programming. It begins by giving an overview of the behavioral science approach to studying programming. Because of space limitations this review will concentrate on cognitive models of programmer problem solving and the experimental research on language characteristics and specification formats. Areas not reviewed include debugging, programming teams, individual differnces, and research methods. The conclusions discuss promising directions for future theory and research.

Three software complexity measures (Halstead's E, McCabe's u(G), and the length as measured by number of statements) were compared to programmer performance on two software maintenance tasks. In an experiment on understanding, length and u(G) correlated with the percent of statements correctly recalled. In an experiment on modification, most significant correlations were obtained with metrics computed on modified rather than unmodified code. All three metrics correlated with both the accuracy of the modification and the time to completion. Relationships in both experiments occurred primarily in unstructured rather than structured code, and in code with no comments. The metrics were also most predictive of performance for less experienced programmers. Thus, these metrics appear to assess psychological complexity primarily where programming practices do not provide assistance in understanding the code.