Domain-Specific Visual language (DSVL) meta-tool has managed to help and assist end-user to create DSVL. With a pre-built function and numerous graphical representations to choose from, it has reduced end-user dependency for application development team. Despite that, it still lacks in term of verification and validation process, as testing is still done manually inside these meta-tools. We propose a high level visual test specification model that is embedded inside DSVL meta-tool. This will allow end-user to self validate their DSVL using model provided. 1. Introduction Recent advancement in DSVL meta-tool applications has significantly increased the number of end-user using meta-tools to create DSVL. Tools flexibility and good support from tools provider have boost end-user confidence toward to the tools. Tools like Marama [1] and Microsoft DSL [2] are two good examples for meta-tool. Marama is a set of tools built on top of Eclipse. It is an open source project that provides a set of meta-tools to specify complex diagram-based meta-models, shapes and connectors and views. Meanwhile, Microsoft DSL is an extension from Microsoft Visual Studio where you can define a modeling language and describes the user interface easily. It then will generate code from descriptions provided by end-user. If previously end-user needs to rely on application developer to create DSVL, now they can do it on their own. Meta-tool provide a specific platform for a specific task in a given problem domain. A same problem domain can contain multiple DSVL solution that fit each end-user needs. Customization on modeling tools is the main feature of DSVL meta-tools. Overall, all meta-tools provide a graphical user interface where user can specify the... ... middle of paper ... ...ogy: New Generations, 2009. ITNG '09. Sixth International Conference on. 2009. 16. Romero-Mariona, J., Secure and Usable Requirements Engineering, in IEEE/ACM International Conference on Automated Software Engineering. 2009, IEEE: Auckland, New Zealand. p. 4. 17. Güldali, B., et al., Semi-automated Test Planning for e-ID Systems by Using Requirements Clustering, in IEEE/ACM International Conference on Automated Software Engineering. 2009, IEEE: Auckland, New Zealand. p. 11. 18. Ernits, J., et al. Requirements-driven model-based testing of the IP multimedia subsystem. in Electronics Conference, 2008. BEC 2008. 11th International Biennial Baltic. 2008. 19. Neag, I.A., D.F. Tyler, and W.S. Kurtz. Visual programming versus textual programming in automatic testing and diagnosis. in AUTOTESTCON Proceedings, 2001. IEEE Systems Readiness Technology Conference. 2001.
Information and Software Technology Years 7–10: Syllabus. (2003, June). Retrieved April 10, 2014, from http://www.boardofstudies.nsw.edu.au/syllabus_sc/pdf_doc/info_soft_tech_710_syl.pdf
Mr I Langdon, “CE811-7-SP: DEVELOPMENT OF LARGE SOFTWARE SYSTEMS”, Soft-ware Testing lecture, Spring Semester’10, University of Essex, UK.
Hull, E., Jackson, K. and Dick, J. (2010) Requirements Engineering. 3rd ed. London: University of Ulster.
Santana, E., Tanaka, S., Guerra, e., Fernandes, C. and Silveira, F. (2009) “Towards a Practical Approach to Testing Pointcut Descriptors With JQuati”, In Latin American Workshop on Aspect-Oriented Software Development, 3, Fortaleza.
There are many solutions to these problems, but none of them are easily implemented. Each area of testing should be heavily modified. In math, for example, there is a str...
Gautham, R. N. (2009). Testing processes in business-critical chain software lifecycle. Software Engineering, 2009. WCSE '09. WRI World Congress on (Volume:4 ) , 5.
Abstract— Software testing is very important element in various product accuracy. Software testing is set of activities conducted with the intent of finding errors in software. It also verifies and validate whether the program is working correctly with no bugs no not. There are basically three levels of testing- Unit, Integration and System. Unit testing referred to as testing in small whereas Integration and System testing are referred to as testing in large. Various testing techniques available for designing of test cases. This paper basically deals with various techniques available to design software testing test cases.
Testing is one of the important methods to boost the confidence of the developers in the reliability of software. Sometimes, programs that are not properly tested perform correct for few months and even years too before some input sets shows the presence of critical errors. Incorrect application that is released to public without fully tested could result in client dissatisfaction and moreover it is important for software in applications that it is free of software faults which might lead to heavy economic loss or even endanger lives. In the past durations, systematic ways to software testing procedures and tools have been developed to avoid many problems. Testing is the most usual technique for fault detection in today’s organization. Main aim of application testing is to boost one's confidence in the correctness of the program being tested.
Software prototyping is becoming very popular as a software development model, as it enables to understand customer requirements at an early stage of development. It helps get valuable feedback from the customer and helps software designers and developers understand about what exactly is expected from the product under development.
After performing validation test, the next phase is output test of the system, since no system code be useful if it does not produce the desired output in desired format. By considering the format of the report/output, output/report is generated or displayed and tested. Here output format is considered in two ways, one is on the screen and other is on printed form.
Automatic test case generation from UML models focusing on structural and behavioral design in test case generation process. Furthermore coping up interaction faults and scenario faults.
UML (Unified Modeling Language) is a universal modeling language in the field of software engineering. It is designed to provide a standard way to visualize the design of a system allowing the programmer to visually see what is required for the software he/she is working on. Many people believe that UML is not important to learn. That it is simply just a time consuming task, and in some cases that is true. But while UML can be time consuming, it can help multiple people understand the essence of a program that is being created. It allows everyone to be on the same page of what the end goal is and of the means to reach the end.
...een made in the analysis of software systems using colored Petri nets. According to G.Rozenberg[10], Colored Petri net is a useful language for the specification, design, simulation, analysis and verification of large software systems. V. Pinci and M. Shapiro[10] describe an integrated software development procedure based on hierarchical colored Petri nets, where analysis is done through automatic translation from SADT diagrams into colored Petri nets for formal analysis and then into an executable code.
While DTDs are still in use for XML validation, it has several major limitations. First, it is not written in XML syntax; therefore, we have to learn a new syntax to develop a DTD. Second, DTD does not support namespace, limiting its extensibility, as we discussed earlier. In addition, there are no restrictions imposed character data type (such as date, time). In order to solve these problems, an XML Schema is a W3C recommendation for XML validation update document format.
...lect vital information about the capabilities and attributes of software and to help expose potential issues.