scholarly journals Anatomy of Model Based Testing

2020 ◽  
Vol 9 (2) ◽  
pp. 999-1002
Keyword(s):  
Life Cycle ◽  
Software Testing ◽  
Test Cases ◽  
Use Case ◽  
Design Development ◽  
Model Based ◽  
Development Life Cycle ◽  
Model Based Testing ◽  
Common Term ◽  
Software Development Life Cycle

In a typical Software Development Life Cycle (SDLC), the software testing life cycle consists of reviewing of the requirements, test planning for design, development and execution. Test designing phase is considered as the most vital and foundational in deriving the test cases against the software or the application to be validate. The known fact is that in order to derive an effective test suite generally consumes a lot of manual efforts and good amount of expertise as well. [1] When the testers validate an application for its correct and required behavior, then that system is known as System Under Test (aka SUT), the most common term used in software testing process. Since, this is purely based on a manual approach and testers may not be able to validate all the possible and required scenarios, there may be risk of putting the system for validation. Because, the application may break under a particular use case. This can be overcome by applying Model Based Testing (MBT).

scholarly journals SISTEM INFORMASI INVENTORY BARANG MENGGUNAKAN METODE WATERFALL

2021 ◽  
Vol 7 (1) ◽  
pp. 93-99
Author(s):  
Sopian Aji ◽  
Dany Pratmanto
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Sequence Diagram ◽  
Use Case ◽  
Activity Diagram ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Microsoft Office ◽  
Use Case Diagram

Pencatatan inventory barang atau produk yakni pencatatan pengeluaran dan pemasukan, pencatatan pengeluaran merupakan transaksi atau pesanan barang sesuai dengan pesan supplier atau customer kemudian dicatatan oleh tugas gudang, sedangkan pencatatan pemasukan merupakan penambahan stok barang atau produk atau produk mentah yang dicatatan oleh tugas gudang. Pada inventory barang yang diteliti oleh penulis ini dimana proses pencatatan pengeluaran dan pemasukan barang yang dilakukan masih manual dengan masih menggunakan microsoft office excel karena karena aplikasi tersebut tidak bisa menyimpan data dan informasi secara terpusat pada suatu database. Untuk mengatasi permasalahan tersebut penulis menggunakan proses yang sebelumnya manual menjadi terkomputerisasi sehingga pencatatan pengeluaran dan pemasukan barang informasi yang dihasilkan lebih tepat dan akurat dengan data ditampilkan secara terpusat sehingga lebih efektif dan efisien. Dalam pengembangan sistem yaitu Software Development Life Cycle (SDLC) dengan metode Waterfall yang berorientasi objek dan berbasis web, perancangan Sistem menggunakan tools desain United Modelling languange (UML) dengan perancangan use case diagram, activity diagram dan sequence diagram, sedangkan perancangan database menggunakan tools desain Logical Record Structure (LRS).

MBTDD: MODEL BASED TEST DRIVEN DEVELOPMENT

2012 ◽  
Vol 22 (08) ◽  
pp. 1085-1102 ◽  
Author(s):  
ALIREZA SADEGHI ◽  
SEYED-HASSAN MIRIAN-HOSSEINABADI
Keyword(s):  
Human Resource Management ◽  
Human Resource ◽  
Systems Development ◽  
Test Cases ◽  
Use Case ◽  
Improved Method ◽  
Test Driven Development ◽  
Writing Test ◽  
Model Based ◽  
Model Based Testing

Test Driven Development (TDD), as a quality promotion approach, suffers from some shortages that discourage its usage. One of the most challenging shortcomings of TDD is the low level of granularity and abstraction. This may lead to production of software that is not acceptable by the end users. Additionally, exploiting of TDD is not applicable in the enterprise systems development. To overcome this defect, we have merged TDD with Model Based Testing (MBT) and suggested a framework named Model Based Test Driven Development (MBTDD). According to TDD, writing test cases comes before programming, and based on our improved method of TDD, modeling precedes writing test cases. To validate the applicability of the proposed framework, we have implemented a use case of Human Resource Management (HRM) system by means of MBTDD. The empirical results of using MBTTD show that our proposed method overwhelms existing deficiencies of TDD.

scholarly journals Review Paper on Various Software Testing Techniques & Strategies

2019 ◽  
pp. 43-49
Author(s):  
Nahid Anwar ◽  
Susmita Kar
Keyword(s):  
Quality Assurance ◽  
Life Cycle ◽  
Software Testing ◽  
Review Paper ◽  
Critical Stage ◽  
Software Bugs ◽  
Software Applications ◽  
Development Life Cycle ◽  
Testing Techniques ◽  
Software Development Life Cycle

Software testing is the process of running an application with the intent of finding software bugs (errors or other defects). Software applications demand has pushed the quality assurance of developed software towards new heights. It has been considered as the most critical stage of the software development life cycle. Testing can analyze the software item to identify the disparity between actual and prescribed conditions and to assess the characteristics of the software. Software testing leads to minimizing errors and cut down software costs. For this purpose, we discuss various software testing techniques and strategies. This paper aims to study diverse as well as improved software testing techniques for better quality assurance purposes.

Survey on Prioritizing Test Cases in Various Levels of the Software Development Life Cycle

2021 ◽  
Vol 12 (1) ◽  
pp. 1-28
Author(s):  
Gayatri Nayak ◽  
Mitrabinda Ray
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Test Case ◽  
Test Cases ◽  
Test Case Prioritization ◽  
Research Gaps ◽  
Prioritization Process ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Conclusion Section

Test case prioritization is a technical method to reorder the execution of test cases to reduce regression testing costs. This paper has examined various existing techniques that are widely used and suggests improving test case prioritization process after finding many research gaps. These research gaps are collected after doing a thorough study on 206 papers after surfing 310 papers on test case generation and prioritization techniques. These papers are collected from different electronic databases such as IEEE Explore, Science Direct, ACM Library, Springer, Wiley, and Elsevier. The authors have targeted to make a statistical record to show research contribution on test case prioritization at three levels of software development life cycle. This survey shows that 20.87% of papers are contributing for TCP at the requirement phase, 38.83% of papers are contributing for TCP at the design phase, 40.29% of papers are contributing to TCP at the coding phase. The inference of this study cites many future recommendations for the current researchers in the conclusion section.

Effort Estimation Model for each Phase of Software Development Life Cycle

2012 ◽  
pp. 238-246
Author(s):  
Sarah Afzal Safavi ◽  
Maqbool Uddin Shaikh
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Cost Estimation ◽  
Use Case ◽  
Effort Estimation ◽  
Cost Overrun ◽  
Estimation Model ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
The Cost

The assessment of main risks in software development discloses that a major threat of delays are caused by poor effort / cost estimation of the project. Low / poor cost estimation is the second highest priority risk [Basit Shahzad]. This risk can affect four out of a total five phases of the software development life cycle i.e. Analysis, Design, Coding and Testing. Hence targeting this risk alone may reduce the overall risk impact of the project by fifty percent. Architectural designing of the system is a great activity which consumes most of the time in SDLC. Obviously, effort is put forth to produce the design of the system. It is evident that none of the existing estimation models try to calculate the effort put on designing of the system. Although use case estimation model uses the use case points to estimate the cost. But what is the cost of creating use cases? One reason of poor estimates produced by existing models can be negligence of design effort/cost. Therefore it shall be well estimated to prevent any cost overrun of the project. We propose a model to estimate the effort in each of these phases rather than just relying upon the cost estimation of the coding phase only. It will also ease the monitoring of project status and comparison against planned cost and actual cost incurred so far at any point of time.

Effort Estimation Model for each Phase of Software Development Life Cycle

2011 ◽  
pp. 270-277
Author(s):  
Sarah Afzal Safavi ◽  
Maqbool Uddin Shaikh
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Cost Estimation ◽  
Use Case ◽  
Effort Estimation ◽  
Cost Overrun ◽  
Estimation Model ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
The Cost

The assessment of main risks in software development discloses that a major threat of delays are caused by poor effort / cost estimation of the project. Low / poor cost estimation is the second highest priority risk [Basit Shahzad]. This risk can affect four out of a total five phases of the software development life cycle i.e. Analysis, Design, Coding and Testing. Hence targeting this risk alone may reduce the overall risk impact of the project by fifty percent. Architectural designing of the system is a great activity which consumes most of the time in SDLC. Obviously, effort is put forth to produce the design of the system. It is evident that none of the existing estimation models try to calculate the effort put on designing of the system. Although use case estimation model uses the use case points to estimate the cost. But what is the cost of creating use cases? One reason of poor estimates produced by existing models can be negligence of design effort/cost. Therefore it shall be well estimated to prevent any cost overrun of the project. We propose a model to estimate the effort in each of these phases rather than just relying upon the cost estimation of the coding phase only. It will also ease the monitoring of project status and comparison against planned cost and actual cost incurred so far at any point of time.

scholarly journals Detection of Vulnerability Injection Point in Software Development Lifecycle for Effective Countermeasures

2020 ◽  
Vol 9 (3) ◽  
pp. 2715-2721
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Design Development ◽  
Application Development ◽  
Injection Point ◽  
Attack Tree ◽  
Development Lifecycle ◽  
Development Life Cycle ◽  
Software Development Lifecycle ◽  
Software Development Life Cycle

This paper takes a deeper look at data breach, its causes and the linked vulnerability aspects in the application development lifecycle. Further, the Vulnerabilities are mapped to the software development life cycle (SDLC) involving requirement elicitation, design, development, testing and deployment phases. Being aware of exact SDLC life cycle where the vulnerabilities are injected, suitable security practices (countermeasures) can be adopted in delivery methodology, which can control the eventual data breaches and safeguard the application from security perspective. Our research focuses on Evolution of Vulnerabilities through the application development life cycle, and we have leveraged “Inverted Tree Structure/Attack Tree” and “Affinity Principles” to map the vulnerabilities to right Software Development Life Cycle.

Sign in / Sign up

Export Citation Format

Share Document