scholarly journals Software Identifier Naming Conventions & Dictionary

2021 ◽  
Vol 9 ◽  
pp. 125-135
Author(s):  
Dov Benyomin Sohacheski ◽  
Yotam Lurie ◽  
Shlomo Mark

Software developers have been presented with so many tools meant to assist then during the development process. Tools like autocomplete, intelli-sense, linters, and other static analysis solutions. All such tools have one underlying goal, to promote productivity and improve quality. Much research has been conducted on the topic of software quality and its direct benefits both during and after the development cycle. Various methods of measuring and improving quality in software products have been implemented at a grand scale. However, software developers are still left with the choice of implementation details. One such detail is the choice of identifier names in the code written. Few publications have focused on conventions, guides, or best-practices on the topic of identifiers naming choices (not to be confused with coding styles). Much time and energy is misused by developers while choosing an appropriate identifier name, as well as by other developers later on when trying to understand the choice made by their colleagues. By aggregating and compiling a list of readily available identifier names that developers can choose from, will allow them to focus on other keys aspects of development

Author(s):  
Johanna Rothman

Abstract There is general agreement among the experts and practitioners that a crisis exists in Software Engineering. This crisis is in the area of software quality and schedules. How do we better predict product development progress on an ongoing basis? The quick answer is that all project managers need to know these things: • What are the requirements for functionality, cost, and schedule? • Do I have sufficient resources to meet those requirements? • Am I on target to meet those requirements? These questions are particularly critical for companies who produce complex software, such as real-time or process control products. There are ways to ensure that the requirements of schedule, functionality, and cost are met during project development. This paper will discuss project management activities, possible development process, and predictive measurements for project tracking and prediction for complex software products.


Information ◽  
2020 ◽  
Vol 11 (11) ◽  
pp. 533
Author(s):  
Tiago Espinha Gasiba ◽  
Ulrike Lechner ◽  
Maria Pinto-Albuquerque

Cybersecurity vulnerabilities in industrial control systems have been steadily increasing over the last few years. One possible way to address this issue is through raising the awareness (through education) of software developers, with the intent to increase software quality and reduce the number of vulnerabilities. CyberSecurity Challenges (CSCs) are a novel serious game genre that aims to raise industrial software developers’ awareness of secure coding, secure coding guidelines, and secure coding best practices. An important industry-specific requirement to consider in designing these kinds of games is related to the whole event’s duration and how much time it takes to solve each challenge individually—the challenge solve time. In this work, we present two different methods to compute the challenge solve time: one method based on data collected from the CSC dashboard and another method based on a challenge heartbeat. The results obtained by both methods are presented; both methods are compared to each other, and the advantages and limitations of each method are discussed. Furthermore, we introduce the notion of a player profile, which is derived from dashboard data. Our results and contributions aim to establish a method to measure the challenge solve time, inform the design of future challenges, and improve coaching during CSC gameplay.


Author(s):  
Bokolo Anthony Jnr ◽  
Mazlina Abdul Majid ◽  
Awanis Romli

Currently, sustainability is a pertinent issue that should be considered in the software development process; hence it is imperative to recognize how environmental-friendly practices can be applied in the electronic industries that develop and deploy software products. However, sustainability is not fully considered when electronic industries implement modern software systems. Additionally, software developers in electronic industries believe that software is environmental friendly mainly because it is virtual. Conversely, the life cycle process and approaches applied to implement, deploy and maintain software do possess social and environmental impacts that are usually not accounted for by electronic industries. Therefore this study identified the predictors that determine sustainable software practice applications in electronics industries by presenting a model to facilitate sustainable software products development. The identified predictors influence sustainable software practices applications which correlate to environmental, technical, economic, social and individual dimensions of sustainability in electronics industries. Based on the identified predicators, this research developed a set of indicators for survey questions and collected data from 133 respondents from Information Technology (IT), software, environmental and electronic- based industries. The survey data aimed to verify each of the identified predictors that influence sustainable software practice applications. Descriptive and inferential statistical results from the survey data show that each of the predictors is significant and do influence sustainable software development. The finding from this study provides insights to electronic industries in implementing sustainable software practice applications.


Author(s):  
Sindi Dwi Putri S

The need for information systems is increasing every year. The information system of an organization or company is useful for managing data to produce useful and effective information that supports activities and all levels of management that use it. The aspect of software quality is one of the important things in the development of a software. To determine the quality of software products, a measurement is needed. IBSI Education, one of which is a Tutoring Institution that uses “SiWeSi” to support administration, view schedules, see student progress, and so on. The success of the software that is built is based on whether or not the software works according to the objectives to be achieved. In the scientific concept of software engineering, the success of software is not only seen from the suitability of the resulting product to existing needs. The success of the software is also seen from the software development process. This study uses the McCall quality model because this method fulfills many components of the assessment and looks at quality from the user's point of view. The quality model used to measure the quality of SIWESI is determined from the results of the literature study.


2016 ◽  
Vol 8 ◽  
pp. 46-52 ◽  
Author(s):  
Justyna Starostka

There are many roles that design can play in organisations. It can be source of good marketing strategy, and designer by himself can be a promotional tool for a company. Thanks to those actions companies can gain publicity, media attention and good PR.On the second level, design can be perceived as ‘process of making things better’. In this case companies can achieve more effective product development process, new tools and technologies.On the third level we have the situation when designer work alongside with company managers with the whole business concept. At this level, designers’ work looks more like a brand consultant, a strategist. In this approach design should be reflecting certain brand name and brand values.As our study presented, Swedish companies operate on those two, higher levels, while Polish still limit the scope of design. We strongly believe, that Polish companies, as they gain more experience with design activities, will be more likely to perceive design in this more mature approach. In the meantime, presenting best practices from companies from other, more mature countries could be a good way of promoting design as a strategic asset rather than promotional tool. We believe that in order to fasten this process, Polish companies should as follows:1. Work more often with external and foreign designers;2. Expand the area of designer responsibilities in companies;3. Place the responsibility for design in hands of professional design managers.


Sensors ◽  
2021 ◽  
Vol 21 (10) ◽  
pp. 3480
Author(s):  
Walter Takashi Nakamura ◽  
Iftekhar Ahmed ◽  
David Redmiles ◽  
Edson Oliveira ◽  
David Fernandes ◽  
...  

The success of a software application is related to users’ willingness to keep using it. In this sense, evaluating User eXperience (UX) became an important part of the software development process. Researchers have been carrying out studies by employing various methods to evaluate the UX of software products. Some studies reported varied and even contradictory results when applying different UX evaluation methods, making it difficult for practitioners to identify which results to rely upon. However, these works did not evaluate the developers’ perspectives and their impacts on the decision process. Moreover, such studies focused on one-shot evaluations, which cannot assess whether the methods provide the same big picture of the experience (i.e., deteriorating, improving, or stable). This paper presents a longitudinal study in which 68 students evaluated the UX of an online judge system by employing AttrakDiff, UEQ, and Sentence Completion methods at three moments along a semester. This study reveals contrasting results between the methods, which affected developers’ decisions and interpretations. With this work, we intend to draw the HCI community’s attention to the contrast between different UX evaluation methods and the impact of their outcomes in the software development process.


2018 ◽  
Vol 27 (1) ◽  
pp. 31-35
Author(s):  
MARA HAJDU-MACELARU ◽  
◽  
IOANA ZELINA ◽  

Just about everything changes, and so should a software quality model in order to provide a better understanding of quality for any software product to which is applied. But how can we develop such a software quality model? A software quality model pattern that can be adapted to different software products, and provide an accurate evaluation of the overall software quality. This paper presents an adaptable software quality model which is intended to be used for the quality evaluation of different software products.


2015 ◽  
Vol 42 (suppl 1) ◽  
pp. 73-75
Author(s):  
Marinho Jorge Scarpi

Objective: To recommend metrics to qualify software production and to propose guidelines for the CAPES quadrennial evaluation of the Post-Graduation Programs of Medicine III about this issue. Method: Identification of the development process quality features, of the product attributes and of the software use, determined by Brazilian Association of Technical Standards (ABNT), International Organization Standardization (ISO) and International Electrotechnical (IEC), important in the perspective of the CAPES Medicine III Area correlate users, basing the creation proposal of metrics aiming to be used on four-year evaluation of Medicine III. Results: The in use software quality perception by the user results from the provided effectiveness, productivity, security and satisfaction that originate from its characteristics of functionality, reliability, usability, efficiency, maintainability and portability (in use metrics quality). This perception depends on the specific use scenario. Conclusion: The software metrics should be included in the intellectual production of the program, considering the system behavior measurements results obtained by users' performance evaluation through out the favorable responses punctuation sum for the six in use metrics quality (27 sub-items, 0 to 2 points each) and for quality perception proof (four items, 0 to 10 points each). It will be considered as very good (VG) 85 to 94 points; good (G) 75 to 84 points; regular (R) 65 to 74 points; weak (W) 55 to 64 points; poor (P) <55 points.


2018 ◽  
Vol 103 (12) ◽  
pp. 4339-4342 ◽  
Author(s):  
Christopher R McCartney ◽  
Clifford J Rosen

Abstract An analysis of the Endocrine Society’s clinical practice guidelines (CPGs) published from 2010 to 2017—presented by Irwig et al. in the current issue of The Journal of Endocrinology and Metabolism—suggested that the Endocrine Society met five of seven National Academy of Medicine (NAM) standards concerning financial conflicts of interest in CPGs. As current contributors to the Endocrine Society’s CPG efforts, we offer additional context related to the 2011 NAM standards and the current environment concerning industry support in medicine, and we comment on the nature of industry support received by the Society’s CPG authors according to Irwig and colleagues’ analysis of the Centers for Medicare and Medicaid Services’ Open Payments database. Perhaps most importantly, we outline the Society’s recent and ongoing efforts to enhance the value of its CPGs. Such efforts include a 2016 revision of CPG author conflict of interest rules—a change that was invisible to the investigatory methods used by Irwig et al.—in addition to other processes designed to enhance CPG objectivity. We conclude our commentary by recognizing that good-faith attempts to enhance transparency and to reduce conflicts of interest (real or apparent) in CPGs will ultimately serve the best interests of patients and providers; we confirm the Endocrine Society’s resolute commitment to providing high-quality, evidence-based clinical guidance via a CPG development process that faithfully accords with current CPG best practices.


Sign in / Sign up

Export Citation Format

Share Document