An Overview of Recent Researches
Model-based techniques are popular and most researchershave proposed several techniques. One of the reasons whythose model-based techniques are popular is that wronginterpretations of complex software from non-formalspecification can result in incorrect implementations leading totesting them for conformance to its specification standard .A major advantage of model-based V&V is that it can be easilyautomated, saving time and resources. Other advantages areshifting the testing activities to an earlier part of the softwaredevelopment process and generating test cases that areindependent of any particular implementation of the design .The model-based techniques are method to generate testcases from model diagrams like UML Use Case diagram ,, , UML Sequence diagram  and UML State diagram, , , , , , , . There are manyresearchers who investigated in generating test cases fromthose diagrams. The following paragraphs show examples of model-based test generation techniques that have beenproposed for a long time.Heumann  presented how using use cases, derived fromUML Use Case diagram 1.0, to generate test cases can helplaunch the testing process early in the development lifecycleand also help with testing methodology. In a softwaredevelopment project, use cases define system softwarerequirements. Use case development begins early on, so realuse cases for key product functionality are available in earlyiterations. According to the Rational Unified Process (RUP), ause case is used to describe fully a sequence of actionsperformed by a system to provide an observable result of valueto a person or another system using the product underdevelopment." Use cases tell the customer what to expect, thedeveloper what to code, the technical writer what to document,and the tester what to test. He proposed three-step process togenerate test cases from a fully detailed use case: (a) for eachuse case, generate a full set of use-case scenarios (b) for eachscenario, identify at least one test case and the conditions thatwill make it execute and (c) for each test case, identify the datavalues with which to test.Ryser  raised the practical problems in software testingas follows: (1) Lack in planning/time and cost pressure, (2)Lacking test documentation, (3) Lacking tool support, (4)Formal language/specific testing languages required, (5)Lacking measures, measurements and data to quantify testingand evaluate test quality and (6) Insufficient test quality. Theyproposed their approach to resolve the above problems. Theirapproach is to derive test case from scenario / UML Use Casediagram 1.0 and state diagram 1.0. In his work, the generationof test cases is done in three processes: (a) preliminary test casedefinition and test preparation during scenario creation (b) testcase generation from Statechart and from dependency chartsand (c) test set refinement by application dependent strategies.
This section provides the related works used in this paper,prioritize requirement methods. Donald Firesmith addressed the purpose of requirement prioritization as follows:(a) Determine the relative necessity of the requirements.Whereas all requirements are mandatory, some are morecritical than others. For example, failure to implement certainrequirements may have grave business ramifications that wouldmake the system a failure, while others although contractuallybinding would have far less serious business consequences if they were not implemented or not implemented correctly (b)Help programs through negotiation and consensus building toeliminate unnecessary potential “requirements” (i.e., goals,desires, and “nice-to-haves” that do not merit the mandatorynature of true requirements) and (c) schedule theimplementation of requirements (i.e., help determine whatcapabilities are implemented in what increment). Additionally,these researches in 1980-2008 , , , , , reveal that there are many requirement prioritization methodssuch as Binary Search Tree (BST), 100-point method andAnalytic Hierarchy Process (AHP)III.
PROBLEMThis section discusses the details of research issues relatedto test case generation techniques and research problems,which are motivated this study. Every test case generationtechnique has weak and strong points, as addressed in theliterature survey. In general, referring to the literature review,the following lists major outstanding research challenges.The first research problem is that existing test casegeneration methods are lack of ability to identify domainspecific requirements. The study  shows that domainspecific requirements are some of the most criticalrequirements required to be captured for implementation andtesting, such as constraints requirements and database specificrequirements. Existing approaches ignore an ability to addressdomain specific requirements. Consequently, software testingengineers may ignore the critical functionality related to thecritical domain specific requirements. Thus, this paperintroduces an approach to priority those specific requirementsand generates an effective test case.The second problem is that existing black-box test casegeneration techniques aim to generate a large single test suitewith all possible test cases which maximize cover for eachscenario. Basically, they generate a huge number of test caseswhich are impossible to execute given limited time andresources. As a result, those unexecuted test cases are uselessand it is unable to identify suitable test cases for execution.IV.
Test Case Generation Process
This section presents a new high-level process to generate aset of test cases introduced by using the above comprehensiveliterature review and previous works .
Autonomous System Research Laboratory, Faculty of Science andTechnology, Assumption University.
(IJCSIS) International Journal of Computer Science and Information Security,Vol. 8, No. 6, September 201023http://sites.google.com/site/ijcsis/ISSN 1947-5500