Auto-Generated Specification of Assembly Units by Formalized Requirements for a higher Maturity in the Engineering Process

The objectives of this study were to identify gaps in information provision along the colorectal cancer (CRC) treatment pathway as provided by health services within the North Eastern Metropolitan Integrated Cancer Service in Victoria Australia; to evaluate the information and recommend consistent, high quality health information resources; and to recommend strategies to improve delivery of patient information. A random sample of health professionals (n= 47) from various disciplines at eight health service sites participated in semi-structured interviews regarding the types of information they provided to CRC patients. Information items were mapped against a published CRC patient management framework and evaluated. A total of 193 information items were collected with 24 items specific to CRC. Gaps in information provision were evident in the community, at diagnosis, in clinics, when treatment was determined and when completed. The quality of information delivery to CRC patients across the public health sites was variable. Resources were often unavailable, out of date and inaccessible in other languages. Results indicate a need to improve health information availability and resource delivery to all CRC patients across different health services particularly at diagnosis and after treatment. Further research is required to determine patient preferences for information about CRC.

In Vietnam, great efforts have been made in sexual and reproductive health (SRH) information provision, education, communication, as well as service provision for the adolescent and youth (A&Y) over the last 10 years. This paper aimed to examine the content and implementation of SRH policies for A&Y between 2006 and 2017. Case studies were conducted, including interviews and historical documentation. Qualitative data were collected in Hai Duong, Hue, and Dong Thap provinces through 34 in-depth interviews with representatives of central/provincial agencies and 9 focus group discussions with representatives of communal agencies and beneficiaries. SRH policies for A&Y during 2006 to 2017, along with other related national policies, were developed cohesively, however, the gaps in information provision, education, communication as well as service provision remained unresolved. The contents of policies and program implementation did not cover comprehensively, especially regarding disadvantaged groups such as disabled people, migrants, ethnic minorities, and people aged 10 to 14 years. The A&Y SRH policies and program implementation had faced some challenges relating to governance, service delivery, health workforce, health information system, and health financing. The SRH policy for A&Y in the next period needs to be focused on interventions/services for disadvantaged groups. While the human resource is of great importance for the capacity and feasibility to tackle SRH’s challenges, strengthening the advocacy to ensure policies/programs should be prioritized and committed for effective implementation. An appropriate financing system to run information provision, education, communication, and support services for A&Y must be considered during policy development and implementation.

Introduction. High subscription fees to scholarly research journals provoke researchers to use illegal channels of access to scientific information. Analysis of statistical data on downloads of scholarly research papers by Ukrainian Internet users from illegal web resource can help to define gaps in information provision at the institutional or the state level for each scientific field. Problem Statement. To conduct an analysis of behavior and geography of downloads of scholarly research publications from illegal web resource Sci-Hub by Ukrainian Internet users within the period from September 1, 2015 to February 29, 2016. Purpose. To assess the information needs of Ukrainian researchers who download scientific papers from Sci-Hub. Materials and Methods. The used file is available at public domain and contains complete data of downloads of scholarly research articles from Sci-Hub for the period from September 1, 2015 to February 29, 2016. Inquiries of users with Ukrainian IP-addresses have been selected. Using DOI of downloaded articles enables finding the publishers and journal brands with the help of CrossRef API, whereas using the All Science Journal Classification (ASJC) codes makes it possible to identify the subject. Results. The study has shown that the most documents downloaded related to natural sciences (primarily, chemistry, physics, and astronomy), with Elsevier publications being the most frequently inquired by Ukrainian users of Sci-Hub and Internet users from Kyiv downloading the papers most actively. Conclusion. The obtained data are important for understanding the information needs of Ukrainian researchers and can be used to formulate an optimal subscription policy for providing access to information resources at Ukrainian R&D institutions.

Flexible manufacturing systems, as a vision of Industry 4.0, depend on the collaboration of domain experts coming from different engineering disciplines. These experts often depend on (interdisciplinary) results from previous engineering phases and require an explicit representation of knowledge on relationships between products and production systems. However, production systems engineering organizations, which are set in a multidisciplinary environment, rather than focusing on process analysis and improvement options ranging over multiple disciplines, focus mostly on one particular discipline and neglect collaborations between several workgroups. In this chapter, we investigate requirements for the product/ion (i.e., product and production process)-aware analysis of engineering processes to improve the engineering process across workgroups. We, therefore, consider the following three aspects: (1) engineering process analysis methods; (2) artifact and data modeling approaches, from business informatics and from production systems engineering; and (3) persistent representation of product/ion-aware engineering knowledge and data. We extend existing work on business process analysis methods and BPMN 2.0 to address their limited capabilities for product/ion-aware process analysis. We evaluate the resulting contributions in a case study with domain experts from a large production system engineering company. We conclude that an improved product/ion-aware knowledge representation facilitates traceable design decisions as foundation for better quality assurance in the engineering process.

work of W. Edwards Deming has convinced industry that must first measure quality and then emphasise process to improve quality. In response to Deming's arguments and in light of perception that software industry is unable to produce quality products on schedule, and within budget, more software development organisations are now emphasising process measurement, monitoring, and assessment. This paper describes what is meant by software process and discusses an approach for its measurement and improvement. INTRODUCTION Unreliable software makes big news, from emergency services disasters to social security payment blunders. Improved software quality is essential to ensure reliable products and services, and gain customer satisfaction. While software development has existed for more than four decades, we failed so far to make as an industry and as an engineering discipline rather than craft. Developing reliable and usable software that is delivered on and within budget still represents difficult endeavour for many organisations. As role of software becomes increasingly critical for businesses as well as for human lives, problems caused by software products that are late, over budget, or that do not work, become magnified. If lives are lost or people inconvenienced due to incapable computer software, news media is there to make big stories. Organisations are realising that their fundamental problems is immaturity of their software process. Robert Lai (1993) proposes that process improvement is second maturity wave of software industry. He states that the first wave of software was developed using waterfall model in 1970's. Today we are Transactions on Information and Communications Technologies vol 8, © 1994 WIT Press, www.witpress.com, ISSN 1743-3517 216 Software Management in midst of second wave maturity movement as we attempt to formally define development process and best ways to continuously improve it (Lai 1993). Taking lead in this area has been Watts Humphrey (Humphrey 1989, 1990, 1991), and Software Engineering Institute (SEI) at Carnegie Mellon University. SEI started in 1986 to develop process maturity framework to help organisations appraise maturity of their software process, and to provide guidance for organisations to improve their software process capability. A brief description of framework was released in September 1987, including maturity questionnaire. SEI evolved model and questionnaire into 5 -Level Capability Maturity Model (CMM) in 1991. In February 1993, released CMM version 1.1 (Paulk et al 1993). This paper discusses software process and describes capability maturity model (CMM). It also shows how CMM can be used as basis to measure maturity of software process of an organisation and plan its improvement. SOFTWARE QUALITY AND PROCESS IMPROVEMENT In his book Quality is Free Phil Crosby states that: Quality is free. It is not gift, is free. What cost money are unqualify of things all actions that involve not doing jobs right first time (Crosby 1980). If such statement is true for many disciplines, is particularly true for evidence is abundant in number of software products which exceeded their budget, were produced late, failed to satisfy user requirements, and are full of bugs. demand for improved software quality is increasing to ensure reliable products and services. benefits of improved quality comes in form of reduction in failure costs. For software projects failure costs include (DTI 1992): • costs of correcting defects, both before and after delivery • overruns against and budget • unnecessary high maintenance costs • indirect costs which users incur due to poor quality software link between process maturity and software quality is expressed in premise that The quality of software system is governed by quality of process used to develop and maintain it. One stumbling block to improving software quality seems to be that not enough attention is paid to overall development process itself. While software professionals typically devote their to developing, testing or documenting software products, no one has prime responsibility for improving software process. Experience has shown that if Transactions on Information and Communications Technologies vol 8, © 1994 WIT Press, www.witpress.com, ISSN 1743-3517 Managing Systems 217 no one is working on software process, orderly improvement is unlikely. process certainly won't improve itself, rather, most likely, will deteriorate over time. Continuous improvement can occur only if process infrastructure is in place. Watts Humphrey argues in an early article published in Datamation, April 1989 that: Without work on process, there will be little or no progress in improving software. THE SOFTWARE PROCESS Adopting process view of software development represents revolutionary change in perspective. A process orientation to software development involves elements of structure, focus, measurement, ownership, skills, and supporting technology. In this section we investigate what is meant by software process. What Is Software Process According to Webster's dictionary, process is a system of operations in producing something .. series of actions, changes, or functions that achieve an end result. Chambers Concise Dictionary defines process as a series of actions or events .. sequence of operations or changes undergone. IEEE defines process as a sequence of steps performed for given purpose. In general business context, process is defined as a structured, measured set of activities designed to produce specified output for particular customer or market (Davenport 1993). These definitions put strong emphasis on HOW work is done, in contrast to product focus's emphasis on WHAT. Accordingly, process can be considered as a specific ordering of work activities across and place, with beginning, an end, and clearly identified inputs and outputs: structure for action. In this paper we will adopt following definitions quoted in (Humphrey 1990, Paulk et al 1993) are intended to encompass software throughout its life, which covers new development, enhancement, and repair. software process is The set of activities, methods, and practices used in production and evolution of software. software engineering process is The total set of software engineering activities needed to transform user's requirements into software. Transactions on Information and Communications Technologies vol 8, © 1994 WIT Press, www.witpress.com, ISSN 1743-3517 218 Software Management People and Software Process Software development is still people-intensive activity. Talented people are most important element in any software organisation. Even if you get best people available, if they do not follow common process, if everyone wrote in different programming languages, used different conventions, or didn't co-ordinate their design and code changes with their peers, results will be chaos. Successful software organisations have learned that even best professionals need structured and disciplined environment in which to do cooperative work. Software organisations that do not establish such disciplines condemn their people to endless hours of repetitively solving technically trivial problems. obvious fact is that attracting best people is vital, but is also essential to support them with an effectively managed software process. Technology and Software Process Another myth is widespread belief that some technologically advanced tool or method will provide magic answer to software crisis. This is not only wrong, but is dangerous. Organisations which jumped on bandwagon of CASE tools, and ended up in failure and wasted and effort have learned their lesson hard way. Just ask yourself before introducing technology: What do I want to automate? In absence of defined, practised, and managed process, introducing automation can lead to increased chaos. There are several factors which limit effective use of software technology: an illdefined process, inconsistent process implementation, and poor process management. Software technology cannot be fully effective until these problems have been properly addressed. Need for Defined Process If no effort is made to define and enhance software development process across whole organisation, each software development project latches on to its own tools, methods, and practices with little guidance available on how to use them. This ad hoc approach will not be sufficient to tackle task of developing complex software systems. goal of software process management is to enable organisations to produce software that meets cost, schedules, and quality objectives. principles are same that underpins statistical process control-principles that have been successfully used in controlling scientific experiments and in high -volume manufacturing operations. Statistical concepts have been found to be just as applicable to software development as they are to production of manufactured goods such as motor cars. Applying such concepts will only be possible if there is defined and managed process. Software Process Models Transactions on Information and Communications Technologies vol 8, © 1994 WIT Press, www.witpress.com, ISSN 1743-3517

In order to buffer the randomness failure of automated production car body shop is growing tendency to set buffer between lines to solve this problem. Then how to design the buffer capacity is the problem. This article did analysis of the basic planning data of body shop, then provides how to build simulation model and how to design the buffer capacity base on different planning phases through simulation analysis.

Network teaching is to use computer equipment and Internet technology in the virtual space, through a certain method to implement the teaching method on the network, the perfection of the network teaching system can directly replace the traditional teaching method in the whole process of teaching. In order to solve the problem of system development, this paper carries out the demand analysis. First, the use of data flow graph technology, depicting information flow and data from the input to the output of the process of transformation; and then, the use of data dictionary technology, defining the relevant elements of the data flow diagram; finally, the use of tree structure diagram is represented by the administrator subsystem, teacher subsystem and student subsystem structure of the system. The requirement analysis system design the bridge of analysis and software, has laid a foundation for the system development.

The rapid development and expansion of network based applications have changed the computing world in the last decade. However, this overwhelming success has an Achilles’ heel: almost every software controlled system faces threats from potential adversaries both from internal and external users of the highly connected computing systems. These software systems must be engineered with reliable protection mechanisms, while still delivering the expected value of the software to their customers within the budgeted time and cost. The principal obstacle in achieving the above two different but interdependent objectives is that current software engineering processes do notprovide enough support for the software developers to achieve security goals. In this chapter, we reemphasize the principal objectives of both software engineering and security engineering, and strive to identify the major steps of a software security engineering process that will be useful for building secure software systems. Both software engineering and security engineering are ever evolving disciplines, and software security engineering is still in its infancy. This chapter proposes a unification of the process models of software engineering and security engineering in order to improve the steps of the software life cycle that would better address the underlying objectives of both engineering processes. This unification will facilitate the incorporation of the advancement of the features of one engineering process into the other. The chapter also provides a brief overview and survey of the current state of the art of software engineering and security engineering with respect to computer systems.

Automated 3D Model Generation and Programming of Robot Assembly Cells based on Neutral Files

What happened to software engineering? What happened to the promise of rigorous, disciplined, professional practices for software development, like those observed in other engineering disciplines? What has been adopted under the rubric of "software engineering" is a set of practices largely adapted from other engineering disciplines: project management, design and blueprinting, process control, and so forth. The basic analogy was to treat software as a manufactured product, with all the real "engineering" going on upstream of that - in requirements analysis, design, modeling, etc.

The Software Engineering Institute (SEI) is a federally funded research and development center situated as a college‐level unit at Carnegie Mellon University with facilities in Pittsburgh, PA and Arlington, VA. The SEI was created in 1984 by the U.S. Department of Defense to mature and transition new technology to industry so that the government could acquire software‐intensive systems from a broader, more capable contractor base. The SEI works to transform software engineering from an ad‐hoc, labor‐intensive activity to a managed, technology‐supported engineering discipline. The SEI's objectives are to accelerate the introduction and widespread use of high‐payoff software engineering practices and technology by identifying, evaluating, and maturing promising or underused technology and practices; maintain a long‐term competency in software engineering and technology transition; enable government and industry organizations to make measured improvements in their software engineering practices by working with them directly; and foster the adoption and sustained use of standards of excellence for software engineering practice. The institute explores promising solutions to potentially significant problems, selects the best candidate solutions, and works on them to determine their value. In some cases, the SEI works to overcome the limitations that prevent a solution from being of general use in the software community. Finally, the SEI moves mature solutions of proven value into widespread use; examples include the Capability Maturity Model® for Software (SW‐CMM®), and a model curriculum for a master's degree program in software engineering that has been adopted by universties across the country. SEI activities are grouped into two principal areas: software engineering management practices and software engineering technical practices.

Software Engineering is important for the students majored in computer science and technology. This curriculum is intended to provide students with an overall view over Software Engineering as an engineering discipline and with insight into the processes of software development. Creating software Engineering curriculum faces several challenges: (1) Software Engineering has wide coverage, but teaching time is limited. So it is difficult to make in-depth education. (2) Some introductory Software Engineering courses present the principles in isolation from practice. Teaching the lectures seems to focus on philosophy and methodology level, which leads to difficulty for students having no practical experience to understand. (3) Due to the lack of software project practice, students can hardly apply appropriate software engineering methods and technologies to solve problems. (4) How can Software Engineering curriculum satisfy the various needs of different levels? This paper focuses on the challenges above, and introduces how to try to solve them by a case study on the construction of Software Engineering curriculum at Peking University. Finally, this paper gives the future direction for the construction of Software Engineering curriculum.

Patients’ experiences and perspectives of post-hospital follow-up care to improve physical recovery for intensive care survivors: A Systematic Review of Qualitative Research

Introduction and Vision I am honored to be taking over as Editor in Chief of the IEEE Transactions of Software Engineering (TSE). Jeff Kramer will be a hard act to follow, but I am immensely grateful to him for handing over the journal in such a healthy state, and for helping me learn the new job to ensure a smooth transition. It goes without saying that my primary goal as Editor is to maintain the journal’s reputation and standing as the leading forum for publishing the highest quality of research in software engineering. However, these are exciting and changing times in the world of publishing and in the discipline of software engineering, and I believe that TSE must lead the way by finding innovative ways to disseminate software engineering research and by contributing to setting and reflecting the research agenda in the field. To this end I have three medium term goals for my tenure as Editor: 1. To reemphasize the broad scope of the journal, encouraging the publication of multidisciplinary research as well as specialization in software engineering. 2. To engage with the software engineering community at large, including other journals, about the software engineering discipline, using not only the journal itself as a forum but through other professional outlets such as conferences and the web. 3. To support a debate on the nature of scholarly discourse in software engineering, such as the kind and length of papers published in the journal, or the different forms of peer review and discussion around what is published. Tactics The length of papers published in TSE has on occasion been a topic for some discussion. I do not propose to change the policy in this area but to clarify it, as I think it hides a number of issues within it. TSE publishes papers of any length, as long as their length is appropriate for the content presented. The discussion has often centered around what to do if accepted papers are over the IEEE Computer Society’s recommended length of 15 pages. However, there is an equally interesting discussion to be had for short papers. My view is this: There is nothing sacred about the length of a software engineering research contribution. Substantial pieces of work may need lengthy and detailed accounts of techniques, or of empirical studies or other kinds of evidence; but equally valuable results may be published in short papers. Indeed, other disciplines manage to publish seminal results in four pages. I will continue to be guided by my associate editors as to what constitutes an appropriate length for any particular contribution. I believe that we, as a community, have largely won the battle of persuading our deans and managers that publishing in conferences is a respectable form of publication. However, in a world of economic difficulties, carbon footprint consciousness, and fast internet-time publication, there is a strong case to be made that we need to redress the balance and publish more of our research in journals. Indeed, I would go as far as saying that many research students now go through their entire doctoral studies publishing in workshops and conferences only, and think that all research contributions can fit into the 2-column, 10-page format of IEEE conference publications. As a result, other than their PhD dissertations, these students do not get an opportunity to publish their work in an archival journal format. Of course, the frequency of conference reviewing has also had an impact on the nature of reviews that referees are asked to write. With little scope for improving conference papers before publication and heavy referee review loads, reviews tend to be short critiques of papers, rather than substantive engagements with the content that authors are trying to present. I therefore believe that journal reviews and revision allow for better quality work to be produced incrementally and then published. Of course, the journal publication process is not without cost to authors, referees, and editors, and we need to acknowledge this and tackle it head on. I was very taken by the discussion by Crowcroft et al. [1] on the varying incentives of the different stakeholders in the publication process: authors, referees, and editors. For TSE, the kind of behavior I would like to incentivize is for authors to submit innovative, rigorous, and well-presented accounts of their research and not overload the system with half-baked ideas or very small increments on previous work. I would like to incentivize referees to agree to review papers and to produce rigorous, thoughtful reviews. And, I would like to incentivize editors to seek and encourage submission of a wider range of contributions that will serve our research and practitioner community better. I have no magic to generate these incentives. However, in a year’s time TSE will make a number of awards to authors, referees, and (associate) editors to acknowledge the quality of research, feedback, and editing. I welcome feedback from the community on the specification of such awards.

With the rapid development of science and technology, database programming technology has become more mature and perfect, and it has been widely used in the field of computer software engineering, laying a good foundation for the development of computer software engineering and the whole society. Based on this, this paper briefly introduces the database file generation process in computer software engineering, and then summarizes the database programming technology in computer software engineering. Based on this, it analyzes the importance of database programming technology in computer software engineering, discusses the application points of database programming technology in computer software engineering, and provides support for better application of database programming technology.