Granular Computing in Object-Oriented Software Development Process

2010 ◽  
pp. 351-369
Author(s):  
Jianchao Han
Keyword(s):  
Problem Solving ◽  
Software Development ◽  
Granular Computing ◽  
Development Process ◽  
System Analysis ◽  
Algorithm Design ◽  
Object Oriented ◽  
Software Development Process ◽  
User Requirement ◽  
Problem Solving Strategy

Granular computing as a methodology of problem solving has been extensively applied in a variety of fields for a long history, but the special research interest in granular computing has only been developed in past decades. So far most granular computing researchers address the mathematical foundation and/or the computation model of granular computing. However, granular computing is not only a computing model for computer-centered problem solving, but also a thinking model for human-centered problem solving. Fortunately, some authors have presented the structures of such kind models and investigated various perspectives of granular computing from different application points of views. In this paper we present the principles, models, components, strategies, and applications of granular computing. Our focus will be on the applications of granular computing in various aspects and phases of the object-oriented software development process, including user requirement specification and analysis, software system analysis and design, algorithm design, structured programming, software testing, and system deployment design. Our objective is to reveal the importance and usefulness of granular computing as a human-centered problem solving strategy in object-oriented software development process.

Granular Computing in Object-Oriented Software Development Process

2012 ◽  
pp. 726-741
Author(s):  
Jianchao Han
Keyword(s):  
Problem Solving ◽  
Software Development ◽  
Granular Computing ◽  
Development Process ◽  
System Analysis ◽  
Algorithm Design ◽  
Object Oriented ◽  
Software Development Process ◽  
User Requirement ◽  
Problem Solving Strategy

Granular computing as a methodology of problem solving has been extensively applied in a variety of fields for a long history, but the special research interest in granular computing has only been developed in past decades. So far most granular computing researchers address the mathematical foundation and/or the computation model of granular computing. However, granular computing is not only a computing model for computer-centered problem solving, but also a thinking model for human-centered problem solving. Fortunately, some authors have presented the structures of such kind models and investigated various perspectives of granular computing from different application points of views. In this paper we present the principles, models, components, strategies, and applications of granular computing. Our focus will be on the applications of granular computing in various aspects and phases of the object-oriented software development process, including user requirement specification and analysis, software system analysis and design, algorithm design, structured programming, software testing, and system deployment design. Our objective is to reveal the importance and usefulness of granular computing as a human-centered problem solving strategy in object-oriented software development process.

scholarly journals Tailoring effective requirement's specification for ingenuity in Software Development Life Cycle.

2021 ◽  
Vol 12 (3) ◽  
pp. 3338-3344
Author(s):  
Naveen N Kulkarni Et.al
Keyword(s):  
Best Practices ◽  
Software Development ◽  
Natural Language ◽  
Development Process ◽  
Object Oriented ◽  
Software Development Process ◽  
Software Documentation ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Software Requirement Specification

Software Requirements Engineering (SRE) process define software manuscripts with sustaining Software Requirement Specification (SRS) and its activities. SRE comprises many tasks requirement analysis, elicitation, documentation, conciliation and validation. Natural language is most popular and commonly used to form the SRS document. However, natural language has its own limitations wrt quality approach for SRS. The constraints include  incomplete, incorrect, ambiguous, and inconsistency. In software engineering, most applications are object-oriented. So requirements are unlike problem domain need to be developed. So software  documentation is completed in such a way that, all authorized users like clients, analysts, managers, and developers can understand it. These are the basis for success of any planned project. Most of the work is still dependent on intensive human (domain expert) work. consequences of the project success still depend on timeliness with tending errors. The fundamental quality intended for each activity is specified during the software development process. This paper concludes critically with best practices in writing SRS. This approach helps to mitigate SRS limitation up to some extent. An initial review highlights capable results for the proposed practices

Software Development Process for Automation System of Large Solar Vacuum Telescope

2014 ◽  
Vol 9 (1) ◽  
pp. 87-94
Author(s):  
Alexey Bevzov ◽  
Aleksandr Kurochkin ◽  
Anatoliy Lubkov ◽  
Aleksandr Petukhov ◽  
Pavel Filatov
Keyword(s):  
Software Development ◽  
Operating Systems ◽  
Design Patterns ◽  
Development Process ◽  
Object Oriented ◽  
Object Oriented Programming ◽  
Automated System ◽  
Automation System ◽  
Software Development Process ◽  
System Software

The paper describes experience of software development for automated system for Large Solar Vacuum Telescope. Most attention is given to the work evolution on the different stages of this process. Automated system software has been developed using Object-Oriented Programming, Design Patterns and Qt tools to achieve reusable code, that can be used in other telescopes and be portable to different operating systems

scholarly journals Enhancing Software Feature Extraction Results Using Sentiment Analysis to Aid Requirements Reuse

Computers ◽  
2021 ◽  
Vol 10 (3) ◽  
pp. 36
Author(s):  
Indra Kharisma Raharjana ◽  
Via Aprillya ◽  
Badrus Zaman ◽  
Army Justitia ◽  
Shukor Sanim Mohd Fauzi
Keyword(s):  
Feature Extraction ◽  
Software Development ◽  
Sentiment Analysis ◽  
Development Process ◽  
System Analysis ◽  
Similarity Measures ◽  
Software Development Process ◽  
User Reviews ◽  
Elicitation Process ◽  
Positive Sentiment

Recently, feature extraction from user reviews has been used for requirements reuse to improve the software development process. However, research has yet to use sentiment analysis in the extraction for it to be well understood. The aim of this study is to improve software feature extraction results by using sentiment analysis. Our study’s novelty focuses on the correlation between feature extraction from user reviews and results of sentiment analysis for requirement reuse. This study can inform system analysis in the requirements elicitation process. Our proposal uses user reviews for the software feature extraction and incorporates sentiment analysis and similarity measures in the process. Experimental results show that the extracted features used to expand existing requirements may come from positive and negative sentiments. However, extracted features with positive sentiment overall have better values than negative sentiments, namely 90% compared to 63% for the relevance value, 74–47% for prompting new features, and 55–26% for verbatim reuse as new requirements.

Automatic Generation of Object-Oriented Code from the ReLEL Requirements Model

2021 ◽  
Vol 1 (1) ◽  
pp. 36-47
Author(s):  
Andrianjaka Miary Rapatsalahy ◽  
Hajarisena Razafimahatratra ◽  
Thomas Mahatody ◽  
Mihaela Ilie ◽  
Sorin Ilie ◽  
...  
Keyword(s):  
Software Development ◽  
Development Process ◽  
Unified Modeling Language ◽  
Central Element ◽  
Object Oriented ◽  
Automatic Generation ◽  
Software Development Process ◽  
Efficient System ◽  
Unified Modeling ◽  
Model Driven

The final executable code should no longer be considered as a central element in a software development process but rather a naturally important component that results from a model transformation. The objective of the MDA (Model Driven Architecture) approach is to lift the lock of software development automation from the CIM (Computation Independent Model) requirements until the code of an application is obtained. Therefore, we have proposed in the framework of MDA an approach that consists of automatically generating object-oriented code from the CIM model represented by ReLEL (Restructuring extended Lexical Elaborate Language). ReLEL is a natural language-oriented model that represents both the client requirements and the conceptual level of a system. However, the MDA framework does not recommend the type of UML model that corresponds to each business activity. Consequently, automating the software development process from the CIM model specified by ReLEL becomes a complex task. Our strategy in this paper includes the instantiation of the ReLEL model in the Praxeme methodology, which models each of the company's concerns, grouped in a homogeneous whole, using the UML (Unified Modeling Language) and which considers the articulation of these aspects by adopting the MDA principle. To do this, we propose to automate the articulation that covers the intentional, semantic, logical, and software aspects of Praxeme. To validate our approach, we measure the coupling and cohesion of the UML class diagram obtained from the Java code generated from this article using the slicing technique. The results show that the coupling is weak, and the cohesion is strong. It can be deduced that the method proposed in this paper can produce a more reliable and efficient system. 

Object Oriented Testing in Software Development

2011 ◽  
pp. 43-57
Author(s):  
Samuel K.A. Agyemang
Keyword(s):  
Software Development ◽  
Development Time ◽  
Development Process ◽  
Object Oriented ◽  
Final Analysis ◽  
Software Development Process ◽  
Object Oriented Technology ◽  
Development Processes ◽  
Software Object ◽  
The Cost

Object oriented technology is still growing and has not yet matured. Many articles have been written on object oriented software development processes, particularly in the area of testing. Most of the publications seem to agree with the fact that object oriented testing is a challenging aspect of the software development process. The main reason for this view seems to revolve around the fact that the objects and the code are inseparable and also, the idea of inheritance. Despite these views, the publications all seem to agree on one aspect, that object oriented when successfully tested leaves a better-maintained product compared to the traditional non-object oriented software. Object oriented software makes better maintainable software; it also has an added advantage over traditional software development because in the final analysis, it will cost less by shortening the development time as well as cutting down the cost of maintenance.

scholarly journals Teknik Representasi Kebutuhan Pengguna Menggunakan User Persona (Studi Kasus: Relasi antara Presensi dengan Kemampuan Kompetensi)

2021 ◽  
Vol 8 (2) ◽  
pp. 245
Author(s):  
Wahyu Andhika ◽  
Muhammad Iqbal ◽  
Munifah Nur ◽  
Rizkhi Dwi Nugroho
Keyword(s):  
Problem Solving ◽  
Software Development ◽  
Development Process ◽  
User Involvement ◽  
Software Development Process ◽  
Basic Requirement ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
System User

<p class="Abstrak">Elisitasi kebutuhan dalam proses pengembangan perangkat lunak adalah fase yang sangat penting dalam <em>Software Development Lifecycle</em>. Karena dalam tahap ini ditentukan dengan tepat mengenai apa yang akan dibuat. Sebuah sistem baiknya memenuhi kebutuhan dari pengguna. Oleh karena itu, melibatkan pengguna dalam elisitasi kebutuhan menjadi salah satu fase yang sangat berguna dalam menentukan kualitas <em>persona</em><em> experience</em> dalam suatu sistem. Keterlibatan pengguna membuat pengembang harus memahami dengan baik apa saja yang akan menjadi kebutuhan pengguna. Pendekatan yang efektif dibutuhkan untuk mengenali pengguna dan merangkum kebutuhannya dengan baik dengan segala keunikan pada setiap individu yang mungkin terjadi. Menggunakan metode <em>persona</em>, penelitian ini akan menyelesaikan permasalahan berupa informasi dari pengguna yang tidak menggambarkan kebutuhan secara lengkap. Metode ini akan membantu menggambarkan seorang pengguna secara mendalam mulai dari kepribadian, kemampuan hingga perilaku pengguna terhadap suatu masalah. Dokumen mengenai pengguna secara detail kemudian disimpulkan agar didapatkan sebuah kebutuhan dasar untuk diimplementasikan menjadi sebuah sistem. Selain menggunakan metode <em>persona</em><em> </em>dalam meningkatkan elisitasi kebutuhan, penelitian ini juga berfokus pada nilai kualitatif informasi tersebut dengan menambahkan implementasi teori iteratif. Teori ini digunakan untuk meningkatkan akurasi penyelesaian masalah, yang mana pada setiap tahapnya akan menghasilkan informasi yang akan memudahkan pengembang dalam mendesain perangkat lunak yang berorientasi pada pengguna.</p><p class="Abstrak"> </p><p class="Abstrak"><em><strong>Abstract</strong></em></p><div><p><em>Elicitation of needs in the software development process is a very important phase in the Software Development Lifecycle. Because in this stage it is precisely determined what will be made. A good system meets the needs of personas. Therefore, involving personas in the elicitation of needs is one phase that is very useful in determining the quality of persona experience in a system. User involvement makes the developer must understand well what will be the persona's needs. An effective approach is needed to recognize the persona and summarize his needs well with all the uniqueness in each individual that might occur. By using the persona method, this research will solve problems in the form of information from personas who do not describe the needs in full. This method will help describe a persona in depth ranging from personality, ability to persona behavior towards a problem. The detailed persona document is then concluded in order to obtain a basic requirement to be implemented into a system. In addition to using the persona method in increasing the elicitation of needs, this research also focuses on the qualitative value of the information by adding iterative theory implementation. This theory is used to improve the accuracy of problem solving, which at each stage will produce information that will facilitate developers in designing persona-oriented software.</em></p></div><p class="Abstrak"><em><strong><br /></strong></em></p>

Sign in / Sign up

Export Citation Format

Share Document