• KSII Transactions on Internet and Information Systems (TIIS)
• /
• 제13권8호
• /
• pp.4191-4211
• /
• 2019

Software product lines (SPLs) are complex software systems by nature due to their common reference architecture and interdependencies. Therefore, any form of evolution can lead to a more complex situation than a single system. On the other hand, software product lines are developed keeping long-term perspectives in mind, which are expected to have a considerable lifespan and a long-term investment. SPL development organizations need to consider software evolution in a systematic way due to their complexity and size. Addressing new user requirements over time is one of the most crucial factors in the successful implementation SPL. Thus, the addition of new requirements or the rapid context change is common in SPL products. To cope with rapid change several researchers have discussed the evolution of software product lines. However, for the evolution of an SPL, the literature did not present a systematic process that would define activities in such a way that would lead to the rapid evolution of software. Our study aims to provide a requirements-driven process that speeds up the requirements engineering process using social network sites in order to achieve rapid software evolution. We used classification, topic modeling, and sentiment extraction to elicit user requirements. Lastly, we conducted a case study on the smartwatch domain to validate our proposed approach. Our results show that users' opinions can contain useful information which can be used by software SPL organizations to evolve their products. Furthermore, our investigation results demonstrate that machine learning algorithms have the capacity to identify relevant information automatically.

• 한국컴퓨터정보학회논문지
• /
• 제21권5호
• /
• pp.119-126
• /
• 2016

Software maintenance becomes extremely difficult, especially caused by multiple versions in project-based or customer-oriented software development methodology. For reducing the maintenance cost, reengineering to software product line can be a solution to the software which either is a family of products nevertheless little different functionalities or are customized for each different customer's requirement. At an initial stage of the reengineering, the most important activity in software product line is feature extraction with respect to commonality and variability from the existing system due to verifying functional coverage. Several researchers have studied to extract features. They considered only a single version in a single product. However, this is an obstacle to classify the commonality and variability of features. Therefore, we propose a method for systematically extracting features from source code and its change history considering several versions of the existing system. It enables us to represent functionalities reflecting developer's intention, and to clarify the rationale of variation.

• 정보처리학회논문지D
• /
• 제13D권6호
• /
• pp.807-814
• /
• 2006

임베디드 소프트웨어의 응용범위 확대, 요구기능의 복잡성 증가, 그리고 제품개발의 신속성이 요구됨에 따라 소프트웨어 개발업체에서는 기존의 개발 환경에서 진화하여 제품계열공학에 근거한 소프트웨어 생산 환경으로의 전환을 시도하고 있다. 이를 위해서는 대상 시스템에 대한 소프트웨어 아키텍처의 개발이 필수적으로 요구되는데, 본 연구에서는 개발업체가 기존의 소프트웨어 자산으로 보유하고 있는 구조적 모델을 소프트웨어 아키텍처 모델로 변환하기 위해 요구되는 방법 및 지원 도구를 제안한다. 제안하는 아키텍처 변환기는 기존 임베디드 소프트웨어 개발 환경에 대한 큰 변화 없이 제품계열공학의 소프트웨어 개발환경으로 접근할 수 있도록 지원한다.