Application of Design Thinking Methodology to the Various Phases of the Software Development Life Cycle

2022 ◽  
pp. 687-708
Author(s):  
Sahana Prabhu Shankar ◽  
Supriya M. S. ◽  
Naresh E.

Design thinking is often thought of as a creative way of problem solving. People are told to believe what they are told and what they read, and with that is the downfall of creativity. Designers need to see the world through the eyes of a 5-year-old. People needs to give themselves permission to be creative. It takes intelligence to answer a question, but it also takes creativity to answer the question. People have to imagine the world as it never existed before. Design thinking can be termed as “consumer-centric”, “end-user centric” or simply “human-centric” thinking. It works from the perspective of the user in general with user satisfaction being the primary goal. The methodology that I adopted is thinking from the user's perspective and working towards user's satisfaction as the goal. Design thinking is a problem-solving technique evolved in different fields like architecture, engineering, and business. The key element to the success of designing a software system lies in user participation. Therefore, it was basically developed to derive a solution by understanding the user's need.

Author(s):  
Sahana Prabhu Shankar ◽  
Supriya M. S. ◽  
Naresh E.

Design thinking is often thought of as a creative way of problem solving. People are told to believe what they are told and what they read, and with that is the downfall of creativity. Designers need to see the world through the eyes of a 5-year-old. People needs to give themselves permission to be creative. It takes intelligence to answer a question, but it also takes creativity to answer the question. People have to imagine the world as it never existed before. Design thinking can be termed as “consumer-centric”, “end-user centric” or simply “human-centric” thinking. It works from the perspective of the user in general with user satisfaction being the primary goal. The methodology that I adopted is thinking from the user's perspective and working towards user's satisfaction as the goal. Design thinking is a problem-solving technique evolved in different fields like architecture, engineering, and business. The key element to the success of designing a software system lies in user participation. Therefore, it was basically developed to derive a solution by understanding the user's need.


2021 ◽  
Vol 1 (4) ◽  
pp. 542-559
Author(s):  
Muhammad Nurwiseso Wibisono

Abstract: Technological advances in the industrial era 4.0 are currently proceeding rapidly in displaying the information needed by the community. One of the uses of technology commonly used by the community is geolocation-based services, where users can search for information based on the location of an object. These geolocation-based services, such as Google Maps, are used to find information on applications that provide tourist destinations, lodging, delivery of goods, and public transportation. The author designed a prototype called Indonesian Cultural Online Map (PONDASI) to respond to these trends. This prototype was designed by utilizing web-based online map technology to build an information system capable of storing and displaying visual-based information on Indonesian culture. PONDASI ​​is designed by utilizing the Google Maps API to display information on Regional Songs as one of the cultural products in Indonesia. The purpose of designing the PONDASI ​​application is to introduce folk songs to the public by utilizing map technology and creating a sound mapping system to store, process, and display information. The method used in this research is the Software Development Life Cycle (SDLC) method using the Waterfall model. The SDLC method is used in the analysis/requirements gathering, design, implementation, and testing processes. The results showed that the PONDASI ​​application could be used as an information system and learning media for Regional Songs in Indonesia with a user satisfaction level of 90% with a user age range of 18-23 years. Keywords: geolocation, interactive media, folk songs Abstrak: Kemajuan teknologi di era industri 4.0 saat ini kian pesat dalam menampilkan informasi yang dibutuhkan oleh masyarakat. Salah satu penggunaan teknologi yang sudah umum digunakan oleh masyarakat adalah layanan berbasis geolokasi. Pengguna layanan geolokasi  dapat mencari informasi berdasarkan lokasi dari sebuah objek. Layanan berbasis geolokasi seperti Google Maps yang digunakan untuk mengetahui informasi pada aplikasi penyedia destinasi wisata, penginapan, pengiriman barang, dan transportasi umum. Untuk menanggapi tren teknologi tersebut, dirancang Peta Online Budaya Indonesia (PONDASI) dengan memanfaatkan teknologi peta online berbasis web untuk membangun sistem informasi yang mampu menyimpan dan menampilkan informasi kebudayaan Indonesia berbasis visual. PONDASI dirancang dengan memanfaatkan Google Maps API untuk menampilkan informasi Lagu Daerah sebagai salah satu hasil budaya di Indonesia. Tujuan dari perancangan aplikasi PONDASI adalah untuk memperkenalkan lagu daerah kepada masyarakat dengan memanfaatkan kebaruan teknologi serta membangun sistem pemetaan yang baik untuk menyimpan, mengolah, dan menampilkan informasi. Metode yang digunakan dalam penelitian ini adalah metode Software Development Life Cycle (SDLC) menggunakan model Waterfall. Metode SDLC digunakan pada proses analysis/requirement gathering, design, implementation, dan testing.  Hasil penelitian menunjukkan bahwa aplikasi PONDASI dapat digunakan sebagai sistem informasi dan media pembelajaran Lagu Daerah di Indonesia dengan tingkat kepuasan pengguna sebesar 90% dengan kisaran usia pengguna 18-23 tahun. Kata kunci: geolokasi, media interaktif, peta budaya, lagu daerah


Author(s):  
Andriy Lishchytovych ◽  
Volodymyr Pavlenko

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.


Author(s):  
Sampada G.C ◽  
Tende Ivo Sake ◽  
Amrita

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.


Healthcare ◽  
2021 ◽  
Vol 9 (7) ◽  
pp. 854
Author(s):  
Dalia Almaghaslah ◽  
Abdulrhman Alsayari ◽  
Saleh Ali Alyahya ◽  
Rana Alshehri ◽  
Khawlah Alqadi ◽  
...  

Introduction: Design thinking, an innovative problem-solving approach, has gained wide popularity in healthcare disciplines. The aim of this work is to improve outpatients’ experiences in hospital pharmacies in two hospitals in Asir region, Saudi Arabia. Methods: The design thinking approach, adopted from Stanford University’s D-School, was used in this study. Results: Several problems were identified: lack of comfortable environment in the pharmacies’ waiting area, lack of a queue management system, and workflow inefficiencies related to ordering and supplies of medicines. A prototype was proposed to overcome these challenges. Discussion and Conclusion: The design thinking approach helped in identifying end-user (patients visiting outpatient pharmacies) values and desires and provided an understanding of their struggles. It also proposed tailored solutions that could improve patients’ experiences while using the services of the outpatient pharmacies.


2016 ◽  
Vol 685 ◽  
pp. 881-885
Author(s):  
Alexey Ponomarev ◽  
Hitesh S. Nalamwar

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


2021 ◽  
Vol 28 (1) ◽  
Author(s):  
M.A. Adeagbo ◽  
J.E.T. Akinsola ◽  
A.A. Awoseyi ◽  
F. Kasali

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