scholarly journals Rancang Bangun Aplikasi Ensiklopedia Kesehatan Berbasis Android

2018 ◽  
Vol 1 (1) ◽  
pp. 1-4
Author(s):  
Ferdiyani Haris
Keyword(s):  
Software Development ◽  
Research Method ◽  
Software Systems ◽  
Development Method ◽  
A Value ◽  
Development Life Cycle ◽  
The World ◽  
The Media ◽  
Software Development Life Cycle ◽  
Software Development Model

In the world of health, many health terms are difficult to understand. The health encyclopedia book is one of the media that presents an explanation of these terms. But in its use, the printed book is less effective and efficient because of limited space and time. So we need a media that explains health terms that are mobile so that they can be used whenever and wherever. This application was designed and implemented for the Android operating system. The system created aims to display definitions and images of health terms. The research method used is the research and development method. While for the development of software systems using the Software Development Life Cycle (SDLC) waterfall software development model. Based on the results of the response to application users conducted with a questionnaire resulting in a value of 88.9% stated very well.

scholarly journals Penerapan Metode Rational Unified Process (RUP) Dalam Pengembangan Sistem Informasi Medical Check Up Pada Citra Medical Centre

2020 ◽  
Vol 2 (1) ◽  
pp. 76-88
Author(s):  
Ririn Perwitasari ◽  
Royana Afawani ◽  
Sri Endang Anjarwani
Keyword(s):  
Software Development ◽  
Development Process ◽  
System Development ◽  
Medical Center ◽  
Development Method ◽  
Development Life Cycle ◽  
Project Risks ◽  
Unified Process ◽  
Software Development Life Cycle ◽  
Time Required

The Rational Unified Process (RUP) method is an iterative and incremental software development method that focuses on architecture. The RUP method will be used in the development of a medical check-up information system on a Citra medical center because this method is proactively able to resolve the project risks associated with the client's evolving requirements requiring careful change request management. Less time is required for integration as the process of integration goes on throughout the software development life cycle and the development time required is less due to using of components over and over. RUP involves The client’s in The system development process, so the result will be accordance with client  wishes. The system built is expected to make it easier for employees to manage patient data from anywhere and anytime.

scholarly journals PENGEMBANGAN MEDIA BELAJAR PUPUH BERBASIS ANDROID

2014 ◽  
Vol 11 (2) ◽  
Author(s):  
Gusti Ngurah Wira Satryawan ◽  
I Gede Mahendra Darmawiguna ◽  
I Made Gede Sunarya
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Unified Modeling Language ◽  
Functional Model ◽  
Modeling Language ◽  
Unified Modeling ◽  
Development Life Cycle ◽  
The Media ◽  
Software Development Life Cycle ◽  
Android Development

Pupuh is one of the four types of songs that exist in Bali. Pupuh is used to express advices, stories of heroism and feelings that usually shown on dramatari which is developedin Bali such as drama gong, arja and Bondres. This Media Belajar Pupuh Berbasis Android is a learning media pupuh with an Android device. This research aims to design andimplement application design Media Belajar Pupuh Berbasis Android.Development of the Media Belajar Pupuh Berbasis Android is using the software development life cycle SDLC (Software Development Life Cycle) with the waterfall model.Features in this application are intended as a learning pupuh for users with an Androiddevice. The features of this application are the theory of pupuh, uger-uger of pupuh, tunings of pupuh, songs of pupuh and recordings of the user.The result of this research is the design and implementation of the Media BelajarPupuh Berbasis Android that has been successfully carried out. The design is done by using a functional model of the UML (Unified Modeling Language). Implemented in Javaprogramming language using the Eclipse editor and ADT (Android Development Tools) plug- ins, and also using AndEngine as additional libraries. The entire functional requirementshave been successfully implemented in accordance with the design.

Problems, Threats in Software Development Life Cycle and Their Analysis

2018 ◽  
pp. 61-82
Author(s):  
Deepika Rana ◽  
Manisha Malhotra
Keyword(s):  
Supply Chain ◽  
Life Cycle ◽  
Software Development ◽  
Knowledge Base ◽  
Software Systems ◽  
Development Face ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Software Services ◽  
Automated Tool

Managerial and commercialization approach that operate software systems continue to look for assurance that software they acquire should have security attributes they hope for. Methods used to assess the security of software development are software design, coding, testing, and support and consideration of security as well. Researchers of software development face many issues which remain constant and very frequent as there was no development in earlier phase of software development to avoid threats and loopholes in the software. Researchers analyze existing methods and their efficiency for software development within an open-source software supply chain. These efforts yielded valuable insights for an automated tool and knowledge base that has the potential for overcoming some of the major and in practice limitations of secure development on a wider scale. As a summarized development of software services along with authenticated approach is mandatory to make its usage on wider expands.

scholarly journals PENGEMBANGAN MEDIA BELAJAR PUPUH BERBASIS ANDROID

2014 ◽  
Vol 11 (2) ◽  
Author(s):  
Gusti Ngurah Wira Satryawan ◽  
I Gede Mahendra Darmawiguna ◽  
I Made Gede Sunarya
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Unified Modeling Language ◽  
Functional Model ◽  
Modeling Language ◽  
Unified Modeling ◽  
Development Life Cycle ◽  
The Media ◽  
Software Development Life Cycle ◽  
Android Development

Pupuh is one of the four types of songs that exist in Bali. Pupuh is used to express advices, stories of heroism and feelings that usually shown on dramatari which is developedin Bali such as drama gong, arja and Bondres. This Media Belajar Pupuh Berbasis Android is a learning media pupuh with an Android device. This research aims to design andimplement application design Media Belajar Pupuh Berbasis Android.Development of the Media Belajar Pupuh Berbasis Android is using the software development life cycle SDLC (Software Development Life Cycle) with the waterfall model.Features in this application are intended as a learning pupuh for users with an Androiddevice. The features of this application are the theory of pupuh, uger-uger of pupuh, tunings of pupuh, songs of pupuh and recordings of the user.The result of this research is the design and implementation of the Media BelajarPupuh Berbasis Android that has been successfully carried out. The design is done by using a functional model of the UML (Unified Modeling Language). Implemented in Javaprogramming language using the Eclipse editor and ADT (Android Development Tools) plug- ins, and also using AndEngine as additional libraries. The entire functional requirementshave been successfully implemented in accordance with the design.

scholarly journals ConE: A Concurrent Edit Detection Tool for Large-scale Software Development

2022 ◽  
Vol 31 (2) ◽  
pp. 1-26
Author(s):  
Chandra Maddila ◽  
Nachiappan Nagappan ◽  
Christian Bird ◽  
Georgios Gousios ◽  
Arie van Deursen
Keyword(s):  
Software Development ◽  
Large Scale ◽  
Daily Basis ◽  
Software Systems ◽  
False Alarms ◽  
Detection Tool ◽  
The World ◽  
Key Concepts ◽  
Pull Request ◽  
Software Development Model

Modern, complex software systems are being continuously extended and adjusted. The developers responsible for this may come from different teams or organizations, and may be distributed over the world. This may make it difficult to keep track of what other developers are doing, which may result in multiple developers concurrently editing the same code areas. This, in turn, may lead to hard-to-merge changes or even merge conflicts, logical bugs that are difficult to detect, duplication of work, and wasted developer productivity. To address this, we explore the extent of this problem in the pull-request-based software development model. We study half a year of changes made to six large repositories in Microsoft in which at least 1,000 pull requests are created each month. We find that files concurrently edited in different pull requests are more likely to introduce bugs. Motivated by these findings, we design, implement, and deploy a service named Concurrent Edit Detector (ConE) that proactively detects pull requests containing concurrent edits, to help mitigate the problems caused by them. ConE has been designed to scale, and to minimize false alarms while still flagging relevant concurrently edited files. Key concepts of ConE include the detection of the Extent of Overlap between pull requests, and the identification of Rarely Concurrently Edited Files . To evaluate ConE, we report on its operational deployment on 234 repositories inside Microsoft. ConE assessed 26,000 pull requests and made 775 recommendations about conflicting changes, which were rated as useful in over 70% (554) of the cases. From interviews with 48 users, we learned that they believed ConE would save time in conflict resolution and avoiding duplicate work, and that over 90% intend to keep using the service on a daily basis.

scholarly journals The Application of a New Secure Software Development Life Cycle (S-SDLC) with Agile Methodologies

Electronics ◽  
2019 ◽  
Vol 8 (11) ◽  
pp. 1218 ◽  
Author(s):  
de Vicente Mohino ◽  
Bermejo Higuera ◽  
Bermejo Higuera ◽  
Sicilia Montalvo
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Software Life Cycle ◽  
Development Environment ◽  
Agile Methodologies ◽  
Development Life Cycle ◽  
Secure Software Development ◽  
Software Development Life Cycle ◽  
Software Development Model ◽  
New Software Development

The software development environment is focused on reaching functional products in the shortest period by making use of the least amount of resources possible. In this scenario, crucial elements such as software quality or software security are not considered at all, and in most cases, the high value offered to the projects is not taken into account. Nowadays, agile models are booming. They are defined by the way they achieve the interaction and integration of everyone involved in the software life cycle, the advantages of the quick reaction to change, and the implementation of artifacts or deliverables which display the level of progress reached at any time. In this context, it seems clearly necessary to define a new software development model, which prioritizes security aspects at any phase of the software life cycle and takes advantage of the benefits of the agile models. The proposed methodology shows that if security is considered from the beginning, vulnerabilities are easily detected and solved during the time planned for the project, with no extra time nor costs for the client and it increases the possibilities of reaching success in terms of not only functionality but also quality.

Computable metrics of personal performance in software development teams

2019 ◽  
Author(s):  
Andriy Lishchytovych ◽  
Volodymyr Pavlenko
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Product Quality ◽  
Performance Indicators ◽  
Key Performance Indicators ◽  
Project Manager ◽  
Development Life Cycle ◽  
Software Product ◽  
Software Development Life Cycle

The present article describes setup, configuration and usage of the key performance indicators (KPIs) of members of project teams involved into the software development life cycle. Key performance indicators are described for the full software development life cycle and imply the deep integration with both task tracking systems and project code management systems, as well as a software product quality testing system. To illustrate, we used the extremely popular products - Atlassian Jira (tracking development tasks and bugs tracking system) and git (code management system). The calculation of key performance indicators is given for a team of three developers, two testing engineers responsible for product quality, one designer, one system administrator, one product manager (responsible for setting business requirements) and one project manager. For the key members of the team, it is suggested to use one integral key performance indicator per the role / team member, which reflects the quality of the fulfillment of the corresponding role of the tasks. The model of performance indicators is inverse positive - the initial value of each of the indicators is zero and increases in the case of certain deviations from the standard performance of official duties inherent in a particular role. The calculation of the proposed key performance indicators can be fully automated (in particular, using Atlassian Jira and Atlassian Bitbucket (git) or any other systems, like Redmine, GitLab or TestLink), which eliminates the human factor and, after the automation, does not require any additional effort to calculate. Using such a tool as the key performance indicators allows project managers to completely eliminate bias, reduce the emotional component and provide objective data for the project manager. The described key performance indicators can be used to reduce the time required to resolve conflicts in the team, increase productivity and improve the quality of the software product.

A Systematic Review and Catalog of Security Metric during the Secure Software Development Life Cycle

2020 ◽  
Vol 13 ◽  
Author(s):  
Sampada G.C ◽  
Tende Ivo Sake ◽  
Amrita
Keyword(s):  
Systematic Review ◽  
Life Cycle ◽  
Software Development ◽  
Software Security ◽  
Security Assessment ◽  
Security Metrics ◽  
Development Life Cycle ◽  
Development Processes ◽  
Secure Software Development ◽  
Software Development Life Cycle

Background: With the advancement in the field of software development, software poses threats and risks to customers’ data and privacy. Most of these threats are persistent because security is mostly considered as a feature or a non-functional requirement, not taken into account during the software development life cycle (SDLC). Introduction: In order to evaluate the security performance of a software system, it is necessary to integrate the security metrics during the SDLC. The appropriate security metrics adopted for each phase of SDLC aids in defining the security goals and objectives of the software as well as quantify the security in the software. Methods: This paper presents systematic review and catalog of security metrics that can be adopted during the distinguishable phases of SDLC, security metrics for vulnerability and risk assessment reported in the literature for secure development of software. The practices of these metrics enable software security experts to improve the security characteristics of the software being developed. The critical analysis of security metrics of each phase and their comparison are also discussed. Results: Security metrics obtained during the development processes help to improve the confidentiality, integrity, and availability of software. Hence, it is imperative to consider security during the development of the software, which can be done with the use of software security metrics. Conclusion: This paper reviews the various security metrics that are meditated in the copious phases during the progression of the SDLC in order to provide researchers and practitioners with substantial knowledge for adaptation and further security assessment.

Software Traceability – A Key to Improve Software Evolution

2016 ◽  
Vol 685 ◽  
pp. 881-885
Author(s):  
Alexey Ponomarev ◽  
Hitesh S. Nalamwar
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Software Evolution ◽  
Software Traceability ◽  
Development Life Cycle ◽  
Methods And Techniques ◽  
Software Development Life Cycle

Software traceability is an important part in software development that is getting more and more attention nowadays from organizations and researchers. The paper outlines the importance, different methods and techniques of software traceability. It also explains the need of automating traceability, problems and drawbacks of existing traceability tools, the ongoing challenges facing implementation of traceability in software development life cycle, and finally the paper discusses whether software traceability should be mandated as a key to improve software evolution

Sign in / Sign up

Export Citation Format

Share Document