Implementing Activity Diagram On Web With Optimization
Implementing Activity Diagram On Web With Optimization
optimization
Unified Modeling Language a standard diagramming notation was introduced in the late 90s, its
primary application was to support the communication among software engineers. UML
provided a standardized way to describe software artifacts. There were only limited and rarely
successful attempts to reuse UML artifacts for the implementation phase of a software product.
Implementation of UML is never a restriction regarding a specific programming language
instead the focus lies on developing UML models based on the requirements and translating
them into an executable software system in general. Activity diagram are used to document the
flow within a use case normally when we create web development we ignore the importance of
it. Software Testing is a time consuming and costly process in software development life
cycle. Automation of this phase may lead to overcome the above problems and also
reduces the human effort in other ways it also helps in detecting the human intended
errors and logical errors as well. With the Activity Diagram it’s easy and fast to test the web
logics and provide better optimization in short.
In this technique gray-box method for test case generation from activity diagram directly can be
used, where the design is reused to avoid the cost of test model creation. Each of the test
scenarios are used to extract the information for test case generation, i.e. input/output sequence
and parameters, the constraint conditions etc.