Earticle

Research on information systems and software engineering has often neglected behavioral effects, which may play a role in decision making on software development. The current study addresses this issue by empirically investigating the behavioral roots of over-requirement in the context of a software development project via an experiment. The negative phenomenon of over-requirement refers to specifying a software system beyond the actual needs of the customer or the market, which overload the system with unneeded features. The research question addressed here is whether over-requirement is due in part to the emotional involvement of developers with the software features they developed because of behavioral effects. Previous studies have demonstrated that under the endowment, I-designed-it-myself, and IKEA effects, people become emotionally involved and overvalue physical items that they respectively possess, self-design, or self-create. The findings of our experiment show that participants over-valued features they were assigned to be responsible for, to specify, or to construct, thereby confirming that the three behavioral effects play a role in software development decisions and affect over-requirement. Thus, the study contributes to software development research and practice from the behavioral economics perspective, highlighting the roots of over-requirement.

소프트웨어 산업은 아직도 뿌리깊은 문제에 시달리고 있다. 어떻게 보면, 제조업과 같은 보다 성숙한 산업의 모범사례로부터 뭔가를 배워야 할 지 모른다. 제조업에서의 ‘린’ 원칙을 소프트웨어 개발에 적용하는 것도 한방안일 수 있다. 소프트웨어공학 문헌에서 이런 ‘린’ 원칙은 시도해 볼만한 것으로 언급되었다. 그러나 이들 원칙을 실제 어떻게 적용할 수 있을 가에 대한 구체적 방안을 제시한 연구는 별로 없었다. 본 연구는 ‘린’ 원칙을 소프트웨어 개발에 적용하는 방안을 제시하고자 한다. 이 방안의 핵심은 낭비제거라는 린의 관점을 구체화하기 위하여 프로젝트에서의 리드 타임과 결함을 누적 흐름도(Cumulative Flow Diagram)을 통해 관리하는 방법이다. 또한 이 방안을 실제 프로 젝트 사례에 적용함 으로써 타당성을 검증하고 적용 방법에 대한 이해를 돕고자 하였다.

Software industry still has many deep-seated problems. As a natural consequence, it may have to learn from best practices in more mature industry like manufacturing. An example is ‘lean’ software development which is defined as translation of ‘lean manufacturing’ principles to the software development domain. The principles include ‘eliminate waste’ and ‘amplify learning.’ It was much asserted that these principles are worth applying. Not much study, however, was done on how to practically implement these principles into software development practice. In this study we attempt to present a method in which project lead time and software defects are regarded as major targets of management and are visualized using Cumulative Flow Diagram. We further applied this method on actual projects. The result confirms that agile is positively effective on reducing wastes.

정보 기술의 디지털 컨버전스 속에서 기업들은 전략적으로 소프트웨어 개발을 활용하고 있다. 정보 기술의 소프트웨어 개발의 발전 방향도 전사적 데이터 및 비즈니스 프로세스의 통합을 통하여 전 영역에 걸쳐 신기술을 이 용하여 표준화와 통합화로 진보되고 있다. 그러나 점차 세계화가 가속화 되고 있는 기업들의 개발 환경은 각종 혁신 활동에 대한 통제 및 관리와 비용 절감 노력을 하고 있음에도 불구하고 프로젝트에 따라 고객의 요구사항에 표준화 가 되어 있지 못하다. 또한 기존의 시스템과 새로운 시스템과의 연결이 조화롭지 못함에 따라 과도한 소프트웨어 개 발 통합 작업과 관리가 필요하고 있다. 따라서 본 연구에서는 MVC 디자인 패턴을 적용하여 개발 생산성 있는 N-Tiers 플랫폼에서 엔터프라이즈 프레임워크 환경의 프리젠테이션 티어와 미들(비즈니스) 티어 및 데이터(EIS) 티어의 설계를 제안토록 한다.

Enterprises utilize software development strategically within digital convergence of information technology. Software development direction of IT takes advantage of new technology through integration of across-the-board data and business process standardization and integration. But, software development environment of enterprises which globalization is accelerated gradually is doing cost-cutting effort with controls and administration about various reform activity. Nevertheless, have not normalized in customer's requirement according to project, there is visual point that excessive software development integration work and administration are necessary according as connection is not harmonious with new system. Therefore, in this study, to construct these real-time integration environment, do to propose database implementation that have productivity by deent,ing N-Tiers platform for building enterprise framework with development productivity presentation, middle(business) and data(EIS) tier that take advantage of MVC design pattern

Software industry still has many deep-seated problems. As a natural consequence, it may have to learn from best practices in more mature industry like manufacturing. An example is ‘ean’™ software development which is defined as translation of ‘ean manufacturing’principles to the software development domain. The principles include ‘liminate waste’and ‘mplify learning.’™ It was much asserted that these principles are worth applying. Not much study, however, was done on how to practically implement these principles into software development practice. In this study we attempt to present a method in which project lead time and software defects are regarded as major targets of management and are visualized using Cumulative Flow Diagram. We further applied this method on actual projects. The result confirms that agile is positively effective on reducing wastes.

본 연구는 소프트웨어 개발을 위하여 OWASP 상위 10개 보안 지침을 준수하는 과정에서 발생하는 인적 오류를 줄이는데 고급 AI 언어 모델인 GPT-4 Turbo 기술을 활용하는 방안을 제시한다. 특히, GPT-4 Turbo의 텍스트를 이해하고 생성하는 AI의 능력과 개발자의 전문성을 결합해 오류를 줄이는 것을 목표로 한다. 이를 위해 소프트웨어 개발 생명주기(SDLC) 전 과정에 GPT-4 Turbo 기술을 통합하는 방안을 연구하고, 소프트웨어 보안 과 신뢰성을 향상시킬 수 있는 프레임워크를 제안하였다. 제안한 프레임워크는 정기적으로 업데이트되는 OWASP 취약점에 대응하며 인적 오류를 줄이고 소프트웨어 보안을 강화하는데 도움을 제공하기 때문에 경영전략 관점에 서 소프트웨어 개발 및 관리 프로세스를 간소화하여 신속한 의사결정이 가능해진다.

This research introduces a strategy that leverages GPT-4 Turbo, an advanced AI language model, to minimize human errors encountered while complying with the OWASP Top Ten security guidelines in software development. The framework combines the AI's capabilities in text comprehension and generation with developers' expertise to reduce errors. It delves into integrating GPT-4 Turbo across the Software Development Life Cycle (SDLC), proposing a model that enhances both software security and reliability. This framework addresses and adapts to the regularly updated OWASP vulnerabilities, contributing to reduced human errors and improved security measures. Furthermore, it benefits in streamlining processes and accelerating decision-making within business strategy contexts, demonstrating the multifaceted advantages of integrating sophisticated AI solutions in software development and management practices.

The purpose of this paper is to propose a novel modeling approach called Services Ecosystem that applies the concept of ecosystems in ecology to Service-Oriented Software Development and Integration. For this purpose, an ecological system for software systems is proposed for the emerging Service-Oriented Computing paradigm, describing how participants interact with each other within their environments. Three emerging concepts, Service-Oriented Programming, Software Factories, and Service Grid, are employed to explain biotic and abiotic environments. Based upon the Services Ecosystem model, we demonstrate Services Ecosystem Model transformations by using a case example. The Services Ecosystem model is a novel approach for envisioning the Service-Oriented Computing paradigm in terms of an ecosystem in which the roles/perspectives of each participant and their relationships/interactions to environments are clearly described with a holistic view.

본 연구는 소프트웨어 개발과 성과에 대한 연구를 조사하였다. 소프트웨어의 생산성과 품질 성과 크게 두 측면으로 조사되었다. 소프트웨어에 대한 기존 연구를 통하여 많은 연구들이 진행되어 왔지만 생산성과 품질에 대한 전체적인 영향요인을 포괄적으로 다룬 연구는 매우 적은편이다. 본 연구는 20개국에서 13년 동안 수행된 프로젝트의 성과를 대상으로 영향요인을 조사하였다. 영향요인은 다음과 같다. 소프트웨어 개발 형태, 개발 플랫폼, 개발 기술, 개발 언어, DBMS, 방법론, 방법론 획득 방식, CASE 툴, 총 개발투입 시간, 인적자원 참여 수준, 최대 팀 사이즈가 조사되었다. 본 연구결과 펑션 포인트, 코드 라인 수, 소프트웨어 결함(치명적, 중요, 작은)각 품질과 생산성을 대표하는 변수로 측정되었고 제시된 영향요인과 관련이 있음이 조사되었다. 따라서 소프트웨어 개발에 있어 성과와 품질에 영향을 미치는 요인들이 각각 틀리며 이와 같은 이유 때문에 개발에 참여한 소프트웨어 개발자들은 두 가지 측면에 요인을 균형있게 고려해야 할 것이다.

Performance of software development is measured by two major criteria – roductivity and quality. Although the criteria is empirically tested in software engineering research, they often present with a limited way under consideration of a few factors or contexts for developers to focus on the either productivity facets or quality facets. Analyzing data on software development performance collected over a 13-year period from 20 countries, we investigated how major software development factors – development type, development platform, development technique, language type, DBMS, methodology, methodology acquisition, CASE,, summary of work effort, resource level, max team size, affect the performance of software development. The results suggest that productivity and quality of software development are affected by different factors and context: function points, line of code, extreme defects, major defects, or minor defects. This research provides the empirical evidence that the two performance criteria require for software developer to have careful attention to find the optimal balance between the two performance criteria.

The dramatic increase in cyberattacks targeting government agencies, critical infrastructure, and defense contractors has revealed the inefficiencies of traditional software development life-cycle (SDLC) models. Most SDLC models do not indicate security explicitly, hence secure software development practices need to be infused into each phase so as to limit the exploitation of security loopholes and safeguard the security of high‑security systems. This document puts forward SSDF‑HS, a secure software development framework for high‑security organizations. The comparative study of various hypothetical projects reveals that SSDF‑HS significantly decreases vulnerability density and mean time to remediate while also enhancing compliance scores. The mathematical risk‑reduction model illustrates the lowering of residual risk when security is integrated early (shift‑left). The framework assists high‑security organizations in writing software that is inherently secure and can withstand future threats.

핀테크에 적용되는 소프트웨어의 규모 추정은 매우 난해하며, 오랜 시간이 소요되는 작업이기에 발주 기업 과 개발 업체들이 정확하게 소프트웨어 개발 규모를 산정하기 어려운 상황이다. 일반적으로 프로젝트 관리자들의 경험과, 일반적인 기능 점수 방식에 의하여 규모를 추정하고 있다. 본 논문에서는 기능 점수 모형을 사용자 관점에 서 요구 기능들을 정량적으로 산정하고, 규모를 측정하여, 실시간으로 규모를 산정하여 핀테크 개발 프로젝트에 적용할 수 있는 모델을 제안한다. 제안 모델을 통하여 개발 전에 업무량을 예상하여 규모를 측정할 수 있으며, 레이어 별 프로그램 목록을 기준으로 M/M 및 견적 금액을 산출할 수 있다. 향후 연구에서는 기존 핀테크 프로젝 트의 규모 산정 데이터를 다량 확보하여 정확한 규모 산정에 대한 연구가 필요하다.

Estimation on SW Sizing applied to fintech is very difficult, a task requiring long time, it is difficult for client companies and developer companies to accurately calculate the size of software development. The size is generally estimated based on the experience of project managers and the general functional scoring method. In this paper, propose a model that can be applied to fintech development projects by quantitatively calculating the required functions from the user's point of view, measuring the scale, and calculating the scale in real time. Through the proposed model, the amount of work can be estimated prior to development and the size can be measured, and the M/M and the estimated quotation amount can be calculated based on the program list by each layer. In future studies, by securing size computation data on existing the Fintech Project in mass, research on accurate size computation would be required.

In Korea, software education is being strengthened. As a result, the polarization in software education is getting worse due to the private education craze. Fortunately, there is room in South Korea to narrow the gap through after-school schools. However, the ability of after-school instructors and the acquisition of information are also important, so this study developed model textbooks. Model textbooks have recently applied Nobel Engineering, which has been gaining attention in South Korea. Through the developed model textbooks, we hope to help with fun software education by applying it to the school site after school.

In recent years, embedded systems have become so complex and the development time to market is required to be shorter than before. As embedded systems include more functions for new services, embedded software gradually grow in size, and development costs and time are increasing. In order to overcome this serious matter, we need a customized design and test technique for embedded software. In this paper, we present a software architecture style for embedded software. It facilitates the composition of reusable functions and helps developers to reduce development time. Because the costs associated with revealing errors of embedded software in applications are rising. we propose a test method and tools for target environments.

본 논문에서는 NICE(National Initiative for Cybersecurity Education)의 사이버보안 인력양성 프레임워 크에서 권고하는 보안 소프트웨어 개발 직무에 필요한 기술과 역량을 중심으로 연구하였다. 본 논문에서는 보안 소 프트웨어의 개발 직무에 어떤 보안기술이 필요하고 어떤 보안 역량을 보유해야 하는지에 대해 살펴보았다. 본 논문 의 초점은 보안 소프트웨어의 개발 직무에 필요한 보안기술(핵심기술과 특화기술)과 국내 서울에 위치한 정보보호 관련 학과의 교육과정 사이의 일치성을 분석하는데 있다. 이 분석을 하는 이유는 서울에 위치한 5개 대학의 정보보 호 관련 학과에서 실시하는 교육과정이 보안 소프트웨어 개발 직무를 수행하는데 얼마나 적합한 교육체계를 갖추고 있는지를 살펴보기 위함이다. 결론적으로, 만일 연구된 5개의 관련 학과가 보안 소프트웨어의 개발 직무 개발자를 집중적으로 양성하고자 한다면, 공통적으로 보안 테스팅과 소프트웨어 디버깅, 시큐어 소프트웨어 개발 방법, 위험관 리, 개인정보식별과 프라이버시, 정보보증에 대한 교육이 필요하다.

In this paper, the technology and capabilities required for the job of developing security software recommended by the Cybersecurity Human Resources Development Framework of the National Initiative for Cybersecurity Education (NICE) were studied. In this paper, we describe what security skills are needed for the task of developing security software and what security capabilities should be held. The focus of this paper is to analyze the consistency between security technologies (core and specialized technologies) required for security software development tasks and the curriculum of information protection-related departments located in Seoul, Korea. The reason for this analysis is to see how the curriculum at five universities in Seoul is suitable for performing security software development tasks. In conclusion, if the five relevant departments studied are to intensively train developers of development tasks for security software, they are commonly required to train security testing and software debugging, how secure software is developed, risk management, privacy and information assurance.

The major concern of the study was to develop android - mobile application software for teaching web systems and technologies for the Bachelor of Science in Information Technology students of the College of Information & Communications Technology of Bulacan State University. It made use Instructional System Design (ISD) model, which consists of five phases: (1) analysis; (2) design; (3) development; (4) implementation; and (5) evaluation and revision. The topics included in the courseware were based on the scope of the course syllabus of IT393 - Web Systems and Technologies, enabling the students to learn principles of the subject in unique approach with seven conceptualized units. Significantly, the AMAS has the following advantages: (1) Learner Control; (2) Motivation; (3) Increased interaction; (4) Individualization; (5) Lesson Integrity; (6) Immediate feedback; and (7) Ease of record keeping. Its acceptability was assessed in five dimensions: (1) subject matter content; (2) Readability; (3) Instructional design; (4) Software Operation; and (5) Usability. Moreover, considering the advantages of the software and the acceptability of the android - mobile application software approach, it was recommended that this new mode of instruction be implemented in teaching web systems and technologies.