Types Of Software Development Research Articles

안드로이드 기반의 모바일 앱 개발을 위한 모델링 기법

스마트 폰 2천만 시대가 도래 하면서 향후 모바일 시장의 규모는 엄청나게 거대해질 것으로 전망되고 있다. 이러한 흐름에 동반하여 소프트웨어 개발의 형태도 웹 기반 소프트웨어에서 모바일 기반의 앱 형태나 클라우드 컴퓨팅 기반의 서비스 형태로 변화되고 있다. 현재 전 세계적으로 스마트폰을 위한 플랫폼으로는 구글의 안드로이드와 애플의 IOS가 양대 산맥을 이루고 있다. 이러한 플랫폼 하에서 실행되는 모바일 앱을 개발할 경우 기존의 소프트웨어 모델링 기법을 그대로 적용할 수가 없다. 따라서 본 연구에서는 기존의 소프트웨어 모델링 기법을 안드로이드 기반의 소프트웨어 개발에 맞도록 특화된 모델링 기법을 제안한다. 안드로이드 기반의 모바일 스마트 환경에 필요한 분석 및 설계 기법을 모델링 기법으로 제안한다. We forecast that the scale of mobile market will be large scale according to the twenty million times of smart phone's user is arrived. The type of software development is being transferred into mobile-based App. or cloud computing-based service from web-based software. Currently both Google's android and Apple's IOS are known for two prominent platforms. Existing modeling techniques cannot be applied into the case of mobile application which is executed those platforms. Therefore, we suggest a modeling technique that is customized existing modeling techniques into android-based software development. That is, we propose an analysis and design techniques which are needed into android-based mobile smart environment.

Learning Complex and Ambiguous Style

A distinctive house style allows consumers to reliably identify an organization's products: It can be a source of differentiation and competitive advantage. House style must be open-ended--- complex, and ambiguous---to allow both distinctiveness and innovation. Complex and ambiguous style is difficult to articulate and codify, and thus hard to teach and learn: It can be an operational liability. Based on interview and observational data from high-end avant garde culinary groups in Europe and North America, I describe complex and ambiguous house style and document how members in these groups teach and learn style using rapid-cycle group evaluations of prototypes combined with exemplar-based, outcome-focused feedback norms. I then propose a mechanism---learning through successive approximations---for transmitting complex and ambiguous content in organizations. These findings likely generalize to small innovation organizations in industries producing goods or services which consumers can evaluate only through experience or credence and where repeated consumption of the same version of a good is rare; for instance, consumer product design, some types of software development (such as game design), and fashion.

A systematic review of research on open source software in commercial software product development

Context The popularity of the open source software development in the last decade, has brought about an increased interest from the industry on how to use open source components, participate in the open source community, build business models around this type of software development, and learn more about open source development methodologies. There is a need to understand the results of research in this area. Objective Since there is a need to understand conducted research, the aim of this study is to summarize the findings of research that has ben carried out on usage of open source components and development methodologies by the industry, as well as companies’ participation in the open source community. Method Systematic review through searches in library databases and manual identification of articles from the open source conference. The search was first carried out in May 2009 and then once again in May 2010. Results In 2009, 237 articles were first found, from which 19 were selected based on content and quality, and in 2010, 76 new articles were found from which four were selected. Twenty three articles were identified in total. Conclusions The articles could be divided into four categories: open source as part of component based software engineering, business models with open source in commercial organization, company participation in open source development communities, and usage of open source processes within a company.

Realizing the benefits of the CMMISM with the CeBASE method

AbstractFuture systems will be increasingly software‐intensive, but the type of software development they will need is not well covered by current development and maturity models such as the waterfall model and Software Capability Maturity Model® (CMM®). Future development of software‐intensive systems will need situation‐specific balancing of discipline and flexibility to address such issues as COTS, open source, distribution, mobility rapid change, agents, collaboration support, and simultaneous achievement of rapid development and high dependability. This article shows how the CMMISM's integration of modern systems engineering, software engineering, and integrated process and product development concepts provides a framework for redressing the shortfalls of the Software CMM®, and for enabling projects and organizations to achieve the right balance of discipline and flexibility for their particular situations. But the CMMISM has shortfalls of its own. It provides little guidance on how to define and execute specific processes for a specific project or organization. The article summarizes various process model generators for software intensive systems such as the spiral, the Rational Unified Process (RUP), MBASE, and the CeBASE Method. It concludes that the CeBASE Method best covers the full range of concerns in the CMMISM, resolves its practice‐focus shortfalls, and covers additional best practices not in the CMMISM, such as business case analysis, requirements prioritization, and evolution requirements. © 2002 John Wiley & Sons, Inc. Syst Eng 5: 73–88, 2002; DOI 10.1002/sys.10016

A software inspection process definition language and prototype support tool

Software inspection is a widely used method for finding defects in all types of software development documents. Many process variations exist, each designed for use under certain circumstances or to address some perceived deficiency in other methods. A desirable attribute of inspection is rigour, allowing the use of historical data to predict future performance and to suggest process improvements. Recent work in tool support for inspection is designed to tackle the issue of enforcing rigorous inspection, but these tools concentrate on enforcing a single, usually proprietary, method. This paper investigates existing inspection methods and derives a generic inspection process which can be used to describe any of these methods. This process is then used to determine a notation for describing any inspection process, which can consequently be used as input to an inspection support tool, allowing the support of any inspection method. The paper also demonstrates a system which uses the language to provide support for multiple inspection processes, and describes other desirable features of such a tool. © 1997 by John Wiley & Sons, Ltd.

CommonKADS: a comprehensive methodology for KBS development

The aim of CommonKADS is to fill the need for a structured methodology for KBS projects by constructing a set of engineering models built with the organization and the application in mind. We give a brief overview of the CommonKADS methodology, paying special attention to the expertise modeling-an aspect of KBS development that distinguishes it from other types of software development. We illustrate the CommonKADS approach by showing how aspects of the VT system for elevator design would be modeled. >