scholarly journals Sistem Informasi Fasilitas di DKI Jakarta berbasis Android dengan Algoritma Floyd Warshall

2020 ◽  
Vol 4 (1) ◽  
pp. 9-14
Author(s):  
Ali Rachman ◽  
Henny Leidiyana
Keyword(s):  
Operating System ◽  
Life Cycle ◽  
Software Development ◽  
Mobile Application ◽  
Inaccurate Information ◽  
Public Facilities ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Android Operating System ◽  
Fire Stations

Mobile devices, especially the Android operating system, are very easy to use to provide information related to work or location precisely and accurately, especially searching for the location of facilities in DKI Jakarta, such as hospitals, fire stations, restaurants, hotels, and other places. But so far the problem is often encountered related to inaccurate information reports where reports take the form of images and text without a real location statement. For this reason, it is necessary to design a mobile application that can provide detailed information about the location of several public facilities in DKI Jakarta using the Software Development Life Cycle (SDLC) method. Applications that are made can provide information that has several features including image information, title, description, location, and weather.

scholarly journals Architecture Evaluation of Mobile Application: Whatsapp

2019 ◽  
Vol 8 (10) ◽  
pp. 1253-1256
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Mobile Application ◽  
Life Quality ◽  
Stage Of Development ◽  
Development Life Cycle ◽  
Architecture Evaluation ◽  
Software Development Life Cycle ◽  
The One

Software become an unavoidable in every once life. Quality of the software is an import aspect in the software development life cycle. Quality for a software is represented in terms of functional and non-functional requirement. Software architecture is used to represent the using set of components and is connectivity as a relationship between these components. To assure the development process meet the requirement given by the user, the Software Evaluation is used. Early detection of error protect the software development producing the defect software. ATAM is the one of the method used to detect the risk, non-risk, scenarios and tradeoff in the earlier stage of development life cycle. Here in this paper security scenarios for mobile application has been elicited and compared with the scenarios extracted from the whatsapp application. Comparison shows few scenarios need to added with existing scenarios in order to improve / ensure full security for the metadata.

scholarly journals The Characteristics of Big Data in Successful of Software Development Life Cycle for Mobile Application

2019 ◽  
Vol 8 (2S9) ◽  
pp. 848-852
Keyword(s):  
Big Data ◽  
Life Cycle ◽  
Software Development ◽  
Mobile Application ◽  
Digital Content ◽  
Development Life Cycle ◽  
Digital Contents ◽  
Software Development Life Cycle ◽  
System Analyst ◽  
Capacity Data

This paper aims to software development life cycle for big data, software development and mobile application for the new environment of the real world. The big data is a new design in the world for the Internet devices to connected life in new environment. The paper reviews 6Vs such as (Volume, Variety, Velocity, Variability, Veracity and Value) for big data an environment application used in the mobile application for students and instructors in university. In fact, for the digital content is to efficiency and effectively for accessed the contents with anytime and everywhere to capture the speeding and capacity data. Current research on software development on application for students and instructors is limited to readiness and awareness. This research extends the need for empirical findings from system analyst and top management of digital contents for big data approach.

Mobile application of BTS tower search build upon location based service (LBS)

2019 ◽  
Vol 36 (3) ◽  
pp. 1-6
Author(s):  
Akbar Siddieq ◽  
Ida Nurhaida
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Mobile Application ◽  
Design Methodology ◽  
Software System ◽  
Location Based Service ◽  
Content Type ◽  
Development Life Cycle ◽  
Analysis Design ◽  
Software Development Life Cycle

Purpose Referring the phenomenon, the researchers create an application to deal with problems faced by the technician team and the vendor in searching the location of BTS tower. Design/methodology/approach This application uses the Software Development Life Cycle (SDLC) methodology which is the process of developing or changing a software system. One of the models owned by SDLC is the waterfall technique. It provides a sequential software flow approach starting from analysis, design, coding, testing and supporting stages. Findings There are some of the technician team and the vendor find difficulties in looking for the position of the BTS tower. As a solution, a facility which enables them to access the location in searching the BTS tower is needed. Originality/value The following is a display of the design results and the implementation of writing code in applications that have been made previously.

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

Project Implementation Decision Using Software Development Life Cycle Models: A Comparative Approach

2021 ◽  
Vol 28 (1) ◽  
Author(s):  
M.A. Adeagbo ◽  
J.E.T. Akinsola ◽  
A.A. Awoseyi ◽  
F. Kasali
Keyword(s):  
Life Cycle ◽  
Comparative Analysis ◽  
Software Development ◽  
Cost Estimation ◽  
Comparative Approach ◽  
Project Implementation ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Waterfall Model ◽  
Spiral Model

Selection of a suitable Software Development Life Cycle (SDLC) model for project implementation is somewhat confusing as there are a lot of SDLC models with similar strengths and weaknesses. Also, the solutions proffered among the researchers so far have been the  qualitative comparative analysis of SDLC models. Hence, this paper proposes a comparative analysis of SDLC models using quantitative approach in relation to strengths and weaknesses of SDLC models. The study adapted comparative analysis and Software Development Life Cycle (SDLC) models features’ classification using ten characteristics such as project complexity, project size, project duration, project with risk, implementation/initial cost, error discovery, associated cost, risk analysis, maintenance and cost estimation. A quantitative measure that employs online survey using experts in software design and engineering, project management and system analysis was carried out for the evaluation of SDLC models. Purposeful Stratified Random Sampling (SRS) technique was used to gather the data for analysis using XLSTAT after pre-processing, taking into consideration both benefit and cost criteria. The overall performance evaluation showed that Spiral-Model is the best followed by V-Model and lastly Waterfall Model with comparative values of 38.63%, 35.76% and 25.61% respectively. As regards cost estimation, Waterfall Model is the most efficient with value of 41%, then V-Model with 31% and lastly Spiral Model with 28%. V-Model has great error recovery capability with value of 45% which is closely followed by Spiral Model with 37% and lastly Waterfall Model with 18%. The study revealed that, a model with efficient risk assurance does not guarantee efficient cost management. In the future work, more characteristics regarding SDLC models shall be considered.

Sign in / Sign up

Export Citation Format

Share Document