Software Engineering Research Papers Summaries for Post Graduate Student : Software Engineering Research Paper Summery for MS...

Software Engineering Research Papers Summaries for Post Graduate Student : Software Engineering Research Paper Summery for MS...: Note : it is only summery with mix author and our understanding Thither are many requirements prioritization techniques and choosing the...

Read More

Software Engineering Research Paper Summery for MS

Note : it is only summery with mix author and our understanding

Thither are many requirements prioritization techniques and choosing the most appropriate one is a decision problem in its own rights. Thither is a closer look at the six requirement prioritization techniques and lay them in a controlled experiment with the aim of understanding differences regarding ease of use, total time taken, sociability, accuracy, and total number of comparisons required to reach determinations. These five criteria combined will indicate which technique is more suited. The outcome of the experiment shows that Value oriented Prioritization (VOP) yields an exact solution, can scale upward, and takes the least quantity of time. 

Reference: M. Khari and N. Kumar, comparison of six prioritization techniques for software requirements: 4^th edition, January 2013.

Read More

Software Engineering Research Paper Summery A UML-Based Approach to System Testing

Note : This is only own words summery of above paper

...................................................................................................................................................................

Along the base of specification system testing is concerned with testing an integral arrangement. In OOP, UML development means that system test requirements are derived from UML analysis artifacts such as use cases, their conforming sequence and collaboration diagrams, class diagrams. We are working to hold up the derivation of functional system test requirements, that all changed test cases, test driver once we have detailed design data. We discussed testability and automation issues, as the final goal is to support system testing activities with the high skill tool. TOTEM (Testing Object-orienTed systems with the unified Modeling language) functional test methodology, drive test requirements  from early artifacts produced at the final stage of analysis stage.

Authors: Briand, Lionel and Labiche, Yvan

.................................................................................................

Read More

Software Engineering Research Paper Summery Systematic Review of Automatic Test Case Generation by UML Diagrams

Note: That sentences are only own words summery of original paper

...................................................................................................................................................................

The most significant activity in SDLC is software testing. By time passing the monetary value of manual test cases and also steadfastness of the software researchers and followers have projected many automated test generation techniques but still have a work. This study showed a systematic view of the study performed in the area of automated test generation of test case, particularly related to UML based automated test case generation. The aim of this survey was to collect an adequate data to apprehend and gain deeper visions into the nature of the various testing techniques available and possibility of the best. Foremost we need to get the existing technique that, what were they were getting along already. Thither are a great number of techniques for test generation usecase. Hence a deeper concentration on the existing techniques required. We require to better take in those techniques, their differences and explore novel methods to explore them well. The new methods need will arise from driven study. Unified modeling language has at once become a de facto standard in the area of software testing. New techniques for test case generation from UML needs to be researched. 

................................................................................................................................................................................

 Authors:  Kaur, Arvinder and Vig, Vidhi

Read More

Software Engineering Research paper Summery A Systematic Literature Review of Test Case Generator for Embedded Real Time System

Note: that is only the summery by own words of given paper .
cheers !

...................................................................................................................................................................

Critical and high demand areas nowadays mostly applied by real embedded system. Software quality is an important component to enhance the dependability of the system. Software testing is important in order to sure the software quality. UML is mostly is mostly used and become more useful in software testing. Bu using UML models it is easy to create a test cases. The UML model enables testing to perform in initial form which can assist coders to check software failure at an early point and can salvage time and cost. In this report we provide a systematic review on current problems in software testing and also to improve software testing, focus on UML usage to get test cases based on previous study. Concluding that there is a lack of work, how can we demonstrate the effectiveness of automated test generation because current test cases are not relevant to the testing. Grounded on this work we found that included SLR, we found that not all the test case generation applied to real time encryption system (RTES) because the system accepts their own criteria in order to obtain efficiency.

...........................................................................................................

Authors : Bahrin, Nabilah Kamarul and Mohamad, Radziah

Read More

Software Engineering Research Paper Summery A TEST GENERATION METHOD BASED ON STATE DIAGRAM

Note : This is only summery of above paper

by : NICHA KOSINDRDECHA, 2JIRAPUN DAENGDEJ

In generally software testing phase takes 40-70% of the fourth dimension and cost during the software development life cycle. Thither are many researchers who found many test case generation methods to lessen the price and time, there are still a number of important research publication. The motivation for this study is to chomp a great quantity of time and cost to automatically generate tests from the diagram, with a large size of test and less test code coverage. We presented an effective test sequence generation technique to minimize time, cost, size of the tests while maximizing test coverage. Our anticipated technique target to see and generate tests from the state chart diagram. The diagram mostly used to excuse the conduct of the system, also discuss and determine the best effective test generation methods that derive tests from the diagram. Concluding that existing techniques since 1990, this paper introduces a new “3S” classification of test case generation techniques, which are: specification base technique, sketch diagram base technique and source based technique. Also, this paper's purpose a new “2S” classification of existing test data generation as follows: specification based technique and source code based technique. Specification base approach used input and production with pre-condition that is generated from requirement specification. The source code based technique aims to design test data using control flow graph and source code as well. As a result this work found that TGFMMD method is the best to produce the smaller size of test cases, with minimum total time and hatch all 100% nodes in the state chart diagram

Read More

Software Engineering Static Analysis Implementation in Automated test Generation its code flowchart

Static Analysis 

code step 1 : suppose we have code like this 

int twic (int v) {

return 2*v;

}

void testme (int x  int y) {

z= twic(y);

if (z==x) {

if(x>y+10) {

error}

}

}

Step 2 : Make a flow graph of the program 

Step 3: Write them into mathematically form

after step 2 you have to write your diagram into math form like

suppose  sign like your code

$(sigma type sign) : {x->xo  y->yo}       path condition Pc : true

if yes    $ : {x->xo  y->yo   z->2*yo}                   (pc : true)^(2*yo=xo)

if false  $ : {x->xo  y->yo   z->2*yo}                   (pc : true)^(2*yo!=xo)

Inner loop if True

$ : {x->xo  y->yo   z->2*yo}                   (pc : true)^(2*yo=xo)^xo>yo+10

Inner loop if False

$ : {x->xo  y->yo   z->2*yo}                   (pc : true)^(2*yo=xo)^xo<=yo+10

at the end valuse after solution 

xo=2

yo=1

and hence .

Contact Me for any help 

cheers !

              

Read More