scholarly journals Success Factors and Challenges in Behavior Driven Development

2020 ◽  
Vol 9 (2) ◽  
pp. 858-861
Keyword(s):  
Success Factors ◽  
Development Process ◽  
Implementation Process ◽  
Object Oriented ◽  
Test Case ◽  
Software Development Process ◽  
System Quality ◽  
System Behavior ◽  
Agile Methodology ◽  
The Right

Behavior Driven Development (BDD) is a software development process that combines the general techniques and principles of Test Driven Development (TDD) with ideas from Domain Driven Design (DDD) and Object Oriented (OO) analysis. It describes a cycle of interactions with well-defined outputs, resulting in the deliverable, tested working software. Today, BDD has evolved into an established agile practice. However, compared to other agile methodology frameworks, such as Scrum and Kanban, BDD is a relatively new. Thus, available resources explaining BDD is still limited and the BDD approach is still under development. Based on this observation, this literature review aims to provide the key of success as well as the challenge that lies on the implementation process of BDD in IT Project. We identified 3 success factors and 5 challenges. The success factors are focusing in product value, having a thorough system behavior definition, and using the right BDD supporting tools. Meanwhile, the most challenging part are the difficulties in writing BDD scenario and automating the test case to maintain the system quality.

The Shortest Path Algorithm Dynamic Visualization Realization

2013 ◽  
Vol 694-697 ◽  
pp. 2291-2294
Author(s):  
Xiao Bo Yang ◽  
Bang Ze Chen
Keyword(s):  
Shortest Path ◽  
Implementation Process ◽  
Object Oriented ◽  
Visual Image ◽  
The Other ◽  
Dynamic Visualization ◽  
Object Oriented Method ◽  
Shortest Path Algorithm ◽  
Source Point ◽  
The Right

By using object oriented method design graph vertices into class, and in this foundation to increase visual member, realize from the source point to the other vertex of the shortest path algorithm of dynamic visualization. Around the two sync window animation, the left window with thick lines drawn through the vertices and edges, " revealed the source point to the other vertex of the shortest path " list box display shortest path sequence and path length, the right window demonstration algorithm dynamic implementation process, and in the " S " text box to display the current most find shortest path vertices. The system has friendly interface, visual image.

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.

scholarly journals Test case generation for object-oriented imperative languages in CLP

2010 ◽  
Vol 10 (4-6) ◽  
pp. 659-674 ◽  
Author(s):  
MIGUEL GÓMEZ-ZAMALLOA ◽  
ELVIRA ALBERT ◽  
GERMÁN PUEBLA
Keyword(s):  
Symbolic Execution ◽  
Object Oriented ◽  
Test Case Generation ◽  
Test Case ◽  
Test Cases ◽  
Software Development Process ◽  
Java Programs ◽  
Promising Application ◽  
Account Due ◽  
Imperative Language

AbstractTesting is a vital part of the software development process. Test Case Generation (TCG) is the process of automatically generating a collection of test-cases which are applied to a system under test. White-box TCG is usually performed by means of symbolic execution, i.e., instead of executing the program on normal values (e.g., numbers), the program is executed on symbolic values representing arbitrary values. When dealing with an object-oriented (OO) imperative language, symbolic execution becomes challenging as, among other things, it must be able to backtrack, complex heap-allocated data structures should be created during the TCG process and features like inheritance, virtual invocations and exceptions have to be taken into account. Due to its inherent symbolic execution mechanism, we pursue in this paper that Constraint Logic Programming (CLP) has a promising application field in tcg. We will support our claim by developing a fully CLP-based framework to TCG of an OO imperative language, and by assessing it on a corresponding implementation on a set of challenging Java programs.

scholarly journals Crowdfunding: Financing Ventures in the Digital Era

2017 ◽  
Vol 9 (1) ◽  
pp. 36-41
Author(s):  
Srinivas K. Reddy ◽  
Yee Heng Tan
Keyword(s):  
Success Factors ◽  
Development Process ◽  
Prior Experience ◽  
Success Rates ◽  
Success Stories ◽  
Digital Era ◽  
Realistic Assessment ◽  
The Right ◽  
The Way

Abstract Crowdfunding is a method of raising funds to support a venture, usually by raising small amounts from a large number of investors. Typically, a project creator posts a project on a platform seeking a certain amount of funds for some venture. Potential backers view the project and contribute money if they are convinced of the idea. In most cases, these backers receive something in return. Crowdfunding helps facilitate projects that would otherwise have fallen through the cracks. There are many success stories, but the average success rates are moderate. To succeed, it is necessary to manage the expectations of diverse stakeholders during the entire funding and development process. Success factors range from selecting the right platform to accurate communication all along the way. Prior experience helps, as well as a realistic assessment of the chances, so as not to disappoint the community.

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

scholarly journals Merancang Perangkat Lunak Sistem Penjaminan Mutu Internal (SPMI) Perguruan Tinggi yang Memiliki Daya Adaptasi Terhadap Perubahan Kebutuhan Pengguna secara Cepat dan Sering

2020 ◽  
Vol 5 (3) ◽  
pp. 121
Author(s):  
Acep Taryana ◽  
Ari Fadli ◽  
Siti Rahmah Nurshiami
Keyword(s):  
Software Development ◽  
Development Process ◽  
Method Development ◽  
User Requirements ◽  
Software Development Process ◽  
Application Development ◽  
Software Products ◽  
Rapid Application Development ◽  
Large Step ◽  
The Right

<p><em>Abstrak</em> – <strong>Salah satu permasalahan mendasar proses pengembangan perangkat lunak adalah kebutuhan yang tidak tertangkap lengkap saat awal pengembangan, atau abstraksi kebutuhan pengguna yang kurang terpetakan secara sistematis, runut oleh pengembang. Ketidaksempurnaan pengungkapan kebutuhan pengguna tersebut dapat mengakibatkan produk perangkat lunak yang kurang lengkap bahkan bisa tidak sesuai dengan kebutuhan pengguna. Ketidaksesuaian baru dapat diamati oleh pengguna setelah pengembang menyelesaikan setiap rilis produk. Pada paper ini akan ditunjukkan bagaimana sebuah perangkat lunak SPMI dirancang, diterima oleh pengguna, diberikan masukan oleh pengguna atas masukan perbaikan pada kurun waktu tertentu. Metode yang digunakan dalam proses pengembangan perangkat lunak adalah metode DevOps yang memiliki kemampuan untuk mensinkronkan kebutuhan pengguna dengan pengembangan aplikasi yang berkelanjutan, cepat selama pengembangan dan pengoperasian berlangsung. Metode DevOps tidak hanya mengelola bagian pengembangan tetapi juga mengelola bagian pengoperasian. Hasil perancangan menunjukkan bahwa DevOps menjadi pendekatan tepat agar perangkat lunak pengembangan SPMI dikembangkan dari kecil menjadi besar, <em>step by step</em> tetapi tanpa kehilangan penelusuran antara rilis produk. Dan yang lebih mendasar, DevOps mampu memperkecil gap antara pengembang dengan pengguna aplikasi SPMI-PT. Melalui metode DevOps, pengembangan dan pengoperasian memiliki keterhubungan sebagai timbal balik antara pengembangan dengan pengoperasian maupun sebaliknya.</strong></p><p><em>Abstract</em> – <strong>One of the fundamental problems of the software development process is the requirement that is not completely captured at the beginning of development, or the abstraction of user requirements that are less systematically mapped out, by the developer. Imperfections in disclosing the requirements of these users can result in incomplete software products that may not even match the user's needs. New nonconformities can be observed by users after the Developer completes each product release. In this paper, we will show how an SPMI software is designed, accepted by the user, given input by the user for input improvement in a certain period time. The method used in the software development process is the DevOps method which can synchronize user requirements with rapid, rapid application development during development and operation. The DevOps method not only manages the development part but also manages the operation part. The design results show that DevOps is the right approach so that SPMI development software is developed from small to large, step by step but without losing traces between product releases. And more fundamentally, DevOps can reduce the gap between developers and SPMI-PT application users. Through the DevOps method, development and operation have a relationship as a trade-off between development and operations and vice versa.</strong></p><strong><em>Keywords</em></strong> – <em>Software engineering, Devops, Continuous improvement</em>

scholarly journals Software Development Technique for the Betterment of End User Satisfaction using Agile Methodology

TEM Journal ◽  
2020 ◽  
pp. 992-1002
Author(s):  
Lalband Neelu ◽  
D. Kavitha
Keyword(s):  
Customer Satisfaction ◽  
Software Development ◽  
Present State ◽  
User Satisfaction ◽  
Development Process ◽  
Software Development Process ◽  
End User ◽  
Traditional System ◽  
Agile Methodology ◽  
User Priority

Agile methodology mainly focuses on the end user priority during the each and every stage of software development process. There is a huge scope in this technique in order to alter the major/minor modifications at each stage of software development for attaining the customer satisfaction. The main aim of the present work is to compare agile methodology with the traditional system methodologies. The present state of using the agile technologies for customer satisfaction at every phase by delivering valuable software continuously is also discussed in the present work. Based on the pitfalls in the existing models, a new model is proposed here in the present study.

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

A CRITICAL ANALYSIS AND COMPARISON OF AGILE WITH TRADITIONAL SOFTWARE DEVELOPMENT PROCESS

2017 ◽  
Vol 5 (4) ◽  
pp. 88-93
Author(s):  
Priyanka Kataria ◽  
Shweta Shrivas ◽  
Ishita Shukla ◽  
A. Hemlata
Keyword(s):  
Software Development ◽  
Creative Thinking ◽  
Development Process ◽  
Software Development Process ◽  
Agile Methodology ◽  
Short Period ◽  
Marginal Prices ◽  
Agile Software ◽  
New Software Development

During the past years, new software development approaches were introduced to suit within the new trend of the software development corporations. Most Software Corporation’s today aim to provide valuable software in short period of time with marginal prices and among unstable, ever-changing environments. Agile methodology focuses on the challenges of unpredictability of the real world by relying on individuals and their creative thinking instead of method. In this paper we tend to explore about the current agile methods, strengths and weaknesses of agile strategies and numerous problems with their relevancy. We have conjointly enclosed comparison between traditional software development process and agile software development process. This paper also includes brief discussion about the benefits and problems associated with these methodologies by performing case study of two corporations.

Sign in / Sign up

Export Citation Format

Share Document