This document proposes an optimization approach to automatically generate test cases for object-oriented software using state chart diagrams. It presents a methodology to:
1) Derive a state transition graph from a state chart diagram.
2) Extract information like states, transitions, and events from the state chart diagram.
3) Generate test cases that satisfy transition path coverage, path coverage, and action coverage criteria.
4) Minimize the set of test cases by calculating node coverage and removing redundant test cases.
The methodology is demonstrated through a case study on an Automatic Ticket Machine system.
Minimal Testcase Generation for Object-Oriented Software with State Chartsijseajournal
Today statecharts are a de facto standard in industry for modeling system behavior. Test data generation is
one of the key issues in software testing. This paper proposes an reduction approach to test data generation
for the state-based software testing. In this paper, first state transition graph is derived from state chart
diagram. Then, all the required information are extracted from the state chart diagram. Then, test cases
are generated. Lastly, a set of test cases are minimized by calculating the node coverage for each test case.
It is also determined that which test cases are covered by other test cases. The advantage of our test
generation technique is that it optimizes test coverage by minimizing time and cost. The present test data
generation scheme generates test cases which satisfy transition path coverage criteria, path coverage
criteria and action coverage criteria. A case study on Railway Ticket Vending Machine (RTVM) has been
presented to illustrate our approach.
IJCER (www.ijceronline.com) International Journal of computational Engineerin...ijceronline
The document discusses various UML-based approaches to software testing. It provides an overview of using use cases and other UML diagrams like sequence diagrams, activity diagrams, and state diagrams to generate test cases at different stages of the software development lifecycle. The key advantages mentioned are that testing can begin early since the same models used for design are leveraged for testing. Different algorithms and techniques are surveyed that have been applied to automatically generate test cases from UML models.
Application Of UML In Real-Time Embedded Systemsijseajournal
The UML was designed as a graphical notation for use with object-oriented systems and applications.
Because of its popularity, now it is emerging in the field of embedded systems design as a modeling
language. The UML notation is useful in capturing the requirements, documenting the structure,
decomposing into objects and defining relationships between objects. It is a notational language that is
very useful in modelling the real-time embedded systems. This paper presents the requirements and
analysis modelling of a real-time embedded system related to a control system application for platform
stabilization using COMET method of design with UML notation. These applications involve designing of
electromechanical systems that are controlled by multi-processors.
MINIMIZING THE RISK OF ARCHITECTURAL DECAY BY USING ARCHITECTURE-CENTRIC EVOL...IJCSEA Journal
Software systems endure many noteworthy changes throughout their life-cycle in order to follow the evolution of the problem domains. Generally, the software system architecture cannot follow the rapid evolution of a problem domain which results in the discrepancies between the implemented and designed architecture. Software architecture illustrates a system’s structure and global properties and consequently determines not only how the system should be constructed but also leads its evolution. Architecture plays an important role to ensure that a system satisfies its business and mission goals during implementation and evolution. However, the capabilities of the designed architecture may possibly be lost when the implementation does not conform to the designed architecture. Such a loss of consistency causes the risk of architectural decay. The architectural decay can be avoided if architectural changes are made as early as possible. The paper presents the Process Model for Architecture-Centric Evolution which improves the quality of software systems through maintaining consistency between designed architecture and implementation. It also increases architecture awareness of developers which assists in minimizing the risk of architectural decay. In the proposed approach consistency checks are performed before and after the change implementation.
This document provides an overview of system modeling. It discusses that system modeling involves developing abstract models of a system from different perspectives, and is commonly done using the Unified Modeling Language (UML). It also describes various UML diagram types used in system modeling like use case diagrams, class diagrams, and state diagrams. Finally, it gives examples of modeling different views of a mental health case management system, including contextual models, interaction models, structural models, and behavioral models.
Formal Specification in Software Engineering SE9koolkampus
This document discusses formal specification techniques for software. It describes algebraic techniques for specifying interfaces as abstract data types and model-based techniques for specifying system behavior. Algebraic specifications define operations and their relationships, while model-based specifications represent the system state using mathematical constructs like sets and sequences. Formal specification finds errors earlier and reduces rework, though it requires more upfront effort. The document also provides an example of formally specifying an air traffic control system and insulin pump.
The document discusses several object-oriented methodologies for software design including Rumbaugh's Object Modeling Technique (OMT), Booch methodology, and Jacobson's Object-Oriented Software Engineering (OOSE) methodology. It also covers the generic components of object-oriented design, the system design process, and the object design process. Key aspects covered include class diagrams, use case modeling, partitioning analysis models into subsystems, and inter-subsystem communication.
A novel methodology for test scenario generation based on control flow analys...eSAT Publishing House
This document presents a novel methodology for generating test scenarios from UML 2.x sequence diagrams. It proposes constructing an intermediate control flow graph called a Sequence Control Flow Graph (SCFG) by analyzing the control flow in UML sequence diagrams. It also proposes a test scenario generation algorithm called STSGA that systematically generates test scenarios from the SCFG to test software in the early design phase and help testers later in the development cycle. The approach aims to address the challenges of fragments like alt, loop, break, par, and opt in UML sequence diagrams.
Minimal Testcase Generation for Object-Oriented Software with State Chartsijseajournal
Today statecharts are a de facto standard in industry for modeling system behavior. Test data generation is
one of the key issues in software testing. This paper proposes an reduction approach to test data generation
for the state-based software testing. In this paper, first state transition graph is derived from state chart
diagram. Then, all the required information are extracted from the state chart diagram. Then, test cases
are generated. Lastly, a set of test cases are minimized by calculating the node coverage for each test case.
It is also determined that which test cases are covered by other test cases. The advantage of our test
generation technique is that it optimizes test coverage by minimizing time and cost. The present test data
generation scheme generates test cases which satisfy transition path coverage criteria, path coverage
criteria and action coverage criteria. A case study on Railway Ticket Vending Machine (RTVM) has been
presented to illustrate our approach.
IJCER (www.ijceronline.com) International Journal of computational Engineerin...ijceronline
The document discusses various UML-based approaches to software testing. It provides an overview of using use cases and other UML diagrams like sequence diagrams, activity diagrams, and state diagrams to generate test cases at different stages of the software development lifecycle. The key advantages mentioned are that testing can begin early since the same models used for design are leveraged for testing. Different algorithms and techniques are surveyed that have been applied to automatically generate test cases from UML models.
Application Of UML In Real-Time Embedded Systemsijseajournal
The UML was designed as a graphical notation for use with object-oriented systems and applications.
Because of its popularity, now it is emerging in the field of embedded systems design as a modeling
language. The UML notation is useful in capturing the requirements, documenting the structure,
decomposing into objects and defining relationships between objects. It is a notational language that is
very useful in modelling the real-time embedded systems. This paper presents the requirements and
analysis modelling of a real-time embedded system related to a control system application for platform
stabilization using COMET method of design with UML notation. These applications involve designing of
electromechanical systems that are controlled by multi-processors.
MINIMIZING THE RISK OF ARCHITECTURAL DECAY BY USING ARCHITECTURE-CENTRIC EVOL...IJCSEA Journal
Software systems endure many noteworthy changes throughout their life-cycle in order to follow the evolution of the problem domains. Generally, the software system architecture cannot follow the rapid evolution of a problem domain which results in the discrepancies between the implemented and designed architecture. Software architecture illustrates a system’s structure and global properties and consequently determines not only how the system should be constructed but also leads its evolution. Architecture plays an important role to ensure that a system satisfies its business and mission goals during implementation and evolution. However, the capabilities of the designed architecture may possibly be lost when the implementation does not conform to the designed architecture. Such a loss of consistency causes the risk of architectural decay. The architectural decay can be avoided if architectural changes are made as early as possible. The paper presents the Process Model for Architecture-Centric Evolution which improves the quality of software systems through maintaining consistency between designed architecture and implementation. It also increases architecture awareness of developers which assists in minimizing the risk of architectural decay. In the proposed approach consistency checks are performed before and after the change implementation.
This document provides an overview of system modeling. It discusses that system modeling involves developing abstract models of a system from different perspectives, and is commonly done using the Unified Modeling Language (UML). It also describes various UML diagram types used in system modeling like use case diagrams, class diagrams, and state diagrams. Finally, it gives examples of modeling different views of a mental health case management system, including contextual models, interaction models, structural models, and behavioral models.
Formal Specification in Software Engineering SE9koolkampus
This document discusses formal specification techniques for software. It describes algebraic techniques for specifying interfaces as abstract data types and model-based techniques for specifying system behavior. Algebraic specifications define operations and their relationships, while model-based specifications represent the system state using mathematical constructs like sets and sequences. Formal specification finds errors earlier and reduces rework, though it requires more upfront effort. The document also provides an example of formally specifying an air traffic control system and insulin pump.
The document discusses several object-oriented methodologies for software design including Rumbaugh's Object Modeling Technique (OMT), Booch methodology, and Jacobson's Object-Oriented Software Engineering (OOSE) methodology. It also covers the generic components of object-oriented design, the system design process, and the object design process. Key aspects covered include class diagrams, use case modeling, partitioning analysis models into subsystems, and inter-subsystem communication.
A novel methodology for test scenario generation based on control flow analys...eSAT Publishing House
This document presents a novel methodology for generating test scenarios from UML 2.x sequence diagrams. It proposes constructing an intermediate control flow graph called a Sequence Control Flow Graph (SCFG) by analyzing the control flow in UML sequence diagrams. It also proposes a test scenario generation algorithm called STSGA that systematically generates test scenarios from the SCFG to test software in the early design phase and help testers later in the development cycle. The approach aims to address the challenges of fragments like alt, loop, break, par, and opt in UML sequence diagrams.
A framework to performance analysis of software architectural stylesijfcstjournal
Growing and executable system architecture has a significant role in successful production of large and
distributed systems. Assessing the effect of different decisions in architecture design can decrease the time and cost of software production, especially when these decisions are related to non-functional properties of system. Performance is a non-functional property which relates to timing behaviour of system. In this paper
we propose an approach for modelling and analysis of performance in architecture level. To do this,we follow a general process which needs two formal notations for specifying architecture and performance models of system. In this paper we show how Stochastic Process Algebra (SPA) in the form of PEPA language can be used for performance modelling and analysis of software archi
tectures modelled using Graph Transformation System (GTS). To enable architecture model for performance analysis, equivalent PEPA model should be constructed with transformation. Transformed performance model of the
architecture has been analysed through PEPA toolkit for some properties like throughput, sensitivity analysis, response time and utilisation rate. The analysis results have been explained with regard to a realistic case study.
Unit 4- Software Engineering System Model Notes arvind pandey
This document discusses system modeling techniques used in software engineering. It covers context models, behavioral models, data models, object models, and CASE workbenches. Different types of models present the system from external, behavioral, and structural perspectives. Common model types include data processing, composition, architectural, and classification models. The document provides examples of context models, state machine models, data flow diagrams, and object models. It also discusses semantic data models, object behavior modeling with sequence diagrams, and components of analysis and design workbenches.
The document discusses object-oriented analysis and design concepts like refinement, extensibility, and design for reusability. It provides details on different types of extensibility like white-box, black-box, and gray-box extensibility. It also discusses object-oriented database management systems and compares relational databases with object-oriented databases.
This summary provides an overview of the key concepts discussed in the document:
1. The document discusses various object-oriented analysis and design concepts including use case modeling, the Unified Modeling Language (UML), activity diagrams, associations, aggregation, and composition.
2. It provides descriptions and examples of these concepts, such as defining use cases, actors, and use case diagrams. Activity diagrams are described as showing workflows and processes.
3. The document also discusses UML notation for modeling associations, including binary and ternary associations, and modeling cardinality ratios between associated classes.
Testing and verification of software model through formal semantics a systema...eSAT Publishing House
This document summarizes research on automated testing and verification of software models through formal semantics. It discusses various approaches for transforming UML diagrams into other representations to enable verification. The most widely used technique is model-based testing using use case, class, and state diagrams. Formalizing UML diagrams with other formal languages allows verification of properties. Automating test case generation from UML models can improve efficiency and effectiveness of software testing.
CS8592 Object Oriented Analysis & Design - UNIT V pkaviya
This document discusses object-oriented methodologies for software development. It describes the Rumbaugh, Booch, and Jacobson methodologies which were influential in the development of the Unified Modeling Language. The Rumbaugh Object Modeling Technique focuses on object models, dynamic models, and functional models. The Booch methodology emphasizes class diagrams, state diagrams, and other modeling tools. Jacobson's methodologies like Objectory emphasize use case modeling and traceability between phases.
The document discusses various software architectural styles. It provides descriptions and examples of different styles including:
1) Data-centered architectures which focus on integrating data access and use a centralized data store. Examples given are repository and blackboard styles.
2) Pipe-and-filter architectures which view systems as data transformations through a series of components. Both batch sequential and incremental pipe-and-filter styles are covered.
3) Client-server architectures which separate systems into independent clients that request services from servers. Peer-to-peer is also discussed as a related style.
Software Engineering with Objects (M363) Final Revision By Kuwait10Kuwait10
This document provides an overview of software engineering concepts covered in various course units. It begins with introductions to approaches to software development, requirements concepts, and modeling. Key topics covered include the software development life cycle, requirements elicitation and analysis techniques, types of requirements (functional and non-functional), modeling languages like UML, and risks and traceability in software projects. The document also lists contents for each of the 14 course units.
Software cost estimation is a key open issue for the software industry, which
suffers from cost overruns frequently. As the most popular technique for object-oriented
software cost estimation is Use Case Points (UCP) method, however, it has two major
drawbacks: the uncertainty of the cost factors and the abrupt classification. To address
these two issues, refined the use case complexity classification using fuzzy logic theory which
mitigate the uncertainty of cost factors and improve the accuracy of classification.
Software estimation is a crucial task in software engineering. Software estimation
encompasses cost, effort, schedule, and size. The importance of software estimation becomes
critical in the early stages of the software life cycle when the details of software have not
been revealed yet. Several commercial and non-commercial tools exist to estimate software
in the early stages. Most software effort estimation methods require software size as one of
the important metric inputs and consequently, software size estimation in the early stages
becomes essential.
The proposed method presents a techniques using fuzzy logic theory to improve the
accuracy of the use case points method by refining the use case classification.
SE18_Lec 07_System Modelling and Context ModelAmr E. Mohamed
System modeling is the process of developing abstract models of a system using graphical notation like UML. It helps analysts understand system functionality and communicate with customers. Models present different views like external context, structural organization, dynamic behavior, and interactions. Key UML diagrams include use case, class, sequence, state, and activity diagrams. System context diagrams specifically focus on external factors and the system boundaries.
MODEL CHECKERS –TOOLS AND LANGUAGES FOR SYSTEM DESIGN- A SURVEYcsandit
For over four decades now, variants of Model Checkers are being used as an approach for formal verification of systems consisting of software, hardware or combination of both. Though various model checking tools are available like NuSMV, UPPAAL, PRISM, PAT,FDR, it is difficult to comprehend their usage for systems in different domains like telecommunication, automobile, health and entertainment. However, industry experts and researchers have showcased the use of formal verifications techniques in various domains including Networking, Security and Semiconductor design. With current generation systems becoming more complex, there is an urgent need to better understand and use appropriate methodology, language and tool for definite domain. In this paper, we have made an effort to present Model checking in detail with relevance to available tools and languages to specific domain. For novices in the field, this paper would provide knowledge of model checkers languages and tools that would be suitable for various purposes in diverse systems
This document discusses model-based software testing. It defines a model as a depiction of software behavior. Model-based testing uses models to guide testing tasks like test selection and evaluation. Common models include finite state machines, statecharts, UML diagrams, and Markov chains. The document provides an overview of these models and discusses how they are applied to software testing. It also gives examples to illustrate finite state machines and model-based testing terminology.
System Models in Software Engineering SE7koolkampus
The document discusses various types of system models used in requirements engineering including context models, behavioral models, data models, object models, and how CASE workbenches support system modeling. It describes behavioral models like data flow diagrams and state machine models, data models like entity-relationship diagrams, and object models using the Unified Modeling Language. CASE tools can support modeling through features like diagram editors, repositories, and code generation.
The document discusses the Unified Approach (UA) methodology for software development proposed by Ali Bahrami. The UA aims to combine the best practices of other methodologies like Booch, Rumbaugh, and Jacobson while using the Unified Modeling Language (UML). The core of the UA is use case-driven development. It establishes a unified framework around these methodologies using UML for modeling and documenting the software development process. The UA allows for iterative development by allowing moving between analysis, design, and modeling phases.
Integrating profiling into mde compilersijseajournal
Scientific computation requires more and more performance in its algorithms. New massively parallel
architectures suit well to these algorithms. They are known for offering high performance and power
efficiency. Unfortunately, as parallel programming for these architectures requires a complex distribution
of tasks and data, developers find difficult to implement their applications effectively. Although approaches
based on source-to-source intends to provide a low learning curve for parallel programming and take
advantage of architecture features to create optimized applications, programming remains difficult for
neophytes. This work aims at improving performance by returning to the high-level models, specific
execution data from a profiling tool enhanced by smart advices computed by an analysis engine. In order to
keep the link between execution and model, the process is based on a traceability mechanism. Once the
model is automatically annotated, it can be re-factored aiming better performances on the re-generated
code. Hence, this work allows keeping coherence between model and code without forgetting to harness the
power of parallel architectures. To illustrate and clarify key points of this approach, we provide an
experimental example in GPUs context. The example uses a transformation chain from UML-MARTE
models to OpenCL code.
Operations research originated during World War II when scientists applied scientific methods to military operations. It has since been applied to many domains including business, transportation, and public health. Some key OR techniques include linear programming, transportation models, assignment problems, queuing theory, simulation, and inventory control models. The OR process involves formulating the problem, developing a mathematical model, selecting data inputs, solving the model, validating the model, and implementing the solution. Models can be classified as deterministic or stochastic, descriptive, predictive, or prescriptive, static or dynamic, and analytical or simulation-based. OR aims to help management make better decisions through quantitative analysis and optimization of systems and processes.
The document discusses key concepts in software design including:
- The goals of software design are to transform customer requirements into a suitable implementation while meeting constraints like budget and quality.
- Design involves iterations through high-level, detailed, and architectural design phases to identify modules, interfaces, data structures, and algorithms.
- Good design principles include correctness, simplicity, adaptability, and maintainability. This involves modular and hierarchical decomposition.
- Techniques like top-down and bottom-up design, as well as object-oriented design, are used to arrive at a solution through abstraction layers.
International Journal of Engineering and Science Invention (IJESI) is an international journal intended for professionals and researchers in all fields of computer science and electronics. IJESI publishes research articles and reviews within the whole field Engineering Science and Technology, new teaching methods, assessment, validation and the impact of new technologies and it will continue to provide information on the latest trends and developments in this ever-expanding subject. The publications of papers are selected through double peer reviewed to ensure originality, relevance, and readability. The articles published in our journal can be accessed online.
STRUCTURAL VALIDATION OF SOFTWARE PRODUCT LINE VARIANTS: A GRAPH TRANSFORMATI...IJSEA
This document discusses an approach to structurally validating software product line variants using graph transformations. The authors propose using model transformations to automatically validate products according to dependencies defined in the feature diagram. They introduce necessary meta-models and present graph grammars to perform validation using the AToM3 tool. The approach is illustrated through examples.
This document provides an overview of object-oriented analysis and design. It discusses traditional software development approaches versus object-oriented approaches. The key aspects of object-oriented development covered include objects, classes, inheritance, encapsulation, and polymorphism. Software development life cycle stages like planning, analysis, design, implementation and testing are also summarized. The document compares structured and object-oriented approaches and provides examples of object-oriented programming and design methodologies.
The document discusses modeling performance for distributed real-time process control systems early in development. It proposes representing individual system elements like sensors and actuators as periodic processes and using Model Driven Architecture to develop functional models prior to UML models. This allows performance to be animated or calculated early based on individual element models, helping establish performance requirements before implementation.
Generation of Testcases from UML Sequence Diagram and Detecting Deadlocks usi...KIIT
Abstract:In an environment where processes those execute concurrently, speeding up their computation is important. Deadlock
is a major issue that occurs during concurrent execution. In this paper, we present an approach to generate testcases from UML
sequence diagram for detecting deadlocks during the design phase. This will reduce the effort and cost involved to fix deadlocks
at a later stage. Our work begins with design of sequence diagram for the system, then converting it to intermediate graph where
deadlock points are marked and then traverse to get testcases. The testcases thus generated are suitable for detecting deadlocks.
A framework to performance analysis of software architectural stylesijfcstjournal
Growing and executable system architecture has a significant role in successful production of large and
distributed systems. Assessing the effect of different decisions in architecture design can decrease the time and cost of software production, especially when these decisions are related to non-functional properties of system. Performance is a non-functional property which relates to timing behaviour of system. In this paper
we propose an approach for modelling and analysis of performance in architecture level. To do this,we follow a general process which needs two formal notations for specifying architecture and performance models of system. In this paper we show how Stochastic Process Algebra (SPA) in the form of PEPA language can be used for performance modelling and analysis of software archi
tectures modelled using Graph Transformation System (GTS). To enable architecture model for performance analysis, equivalent PEPA model should be constructed with transformation. Transformed performance model of the
architecture has been analysed through PEPA toolkit for some properties like throughput, sensitivity analysis, response time and utilisation rate. The analysis results have been explained with regard to a realistic case study.
Unit 4- Software Engineering System Model Notes arvind pandey
This document discusses system modeling techniques used in software engineering. It covers context models, behavioral models, data models, object models, and CASE workbenches. Different types of models present the system from external, behavioral, and structural perspectives. Common model types include data processing, composition, architectural, and classification models. The document provides examples of context models, state machine models, data flow diagrams, and object models. It also discusses semantic data models, object behavior modeling with sequence diagrams, and components of analysis and design workbenches.
The document discusses object-oriented analysis and design concepts like refinement, extensibility, and design for reusability. It provides details on different types of extensibility like white-box, black-box, and gray-box extensibility. It also discusses object-oriented database management systems and compares relational databases with object-oriented databases.
This summary provides an overview of the key concepts discussed in the document:
1. The document discusses various object-oriented analysis and design concepts including use case modeling, the Unified Modeling Language (UML), activity diagrams, associations, aggregation, and composition.
2. It provides descriptions and examples of these concepts, such as defining use cases, actors, and use case diagrams. Activity diagrams are described as showing workflows and processes.
3. The document also discusses UML notation for modeling associations, including binary and ternary associations, and modeling cardinality ratios between associated classes.
Testing and verification of software model through formal semantics a systema...eSAT Publishing House
This document summarizes research on automated testing and verification of software models through formal semantics. It discusses various approaches for transforming UML diagrams into other representations to enable verification. The most widely used technique is model-based testing using use case, class, and state diagrams. Formalizing UML diagrams with other formal languages allows verification of properties. Automating test case generation from UML models can improve efficiency and effectiveness of software testing.
CS8592 Object Oriented Analysis & Design - UNIT V pkaviya
This document discusses object-oriented methodologies for software development. It describes the Rumbaugh, Booch, and Jacobson methodologies which were influential in the development of the Unified Modeling Language. The Rumbaugh Object Modeling Technique focuses on object models, dynamic models, and functional models. The Booch methodology emphasizes class diagrams, state diagrams, and other modeling tools. Jacobson's methodologies like Objectory emphasize use case modeling and traceability between phases.
The document discusses various software architectural styles. It provides descriptions and examples of different styles including:
1) Data-centered architectures which focus on integrating data access and use a centralized data store. Examples given are repository and blackboard styles.
2) Pipe-and-filter architectures which view systems as data transformations through a series of components. Both batch sequential and incremental pipe-and-filter styles are covered.
3) Client-server architectures which separate systems into independent clients that request services from servers. Peer-to-peer is also discussed as a related style.
Software Engineering with Objects (M363) Final Revision By Kuwait10Kuwait10
This document provides an overview of software engineering concepts covered in various course units. It begins with introductions to approaches to software development, requirements concepts, and modeling. Key topics covered include the software development life cycle, requirements elicitation and analysis techniques, types of requirements (functional and non-functional), modeling languages like UML, and risks and traceability in software projects. The document also lists contents for each of the 14 course units.
Software cost estimation is a key open issue for the software industry, which
suffers from cost overruns frequently. As the most popular technique for object-oriented
software cost estimation is Use Case Points (UCP) method, however, it has two major
drawbacks: the uncertainty of the cost factors and the abrupt classification. To address
these two issues, refined the use case complexity classification using fuzzy logic theory which
mitigate the uncertainty of cost factors and improve the accuracy of classification.
Software estimation is a crucial task in software engineering. Software estimation
encompasses cost, effort, schedule, and size. The importance of software estimation becomes
critical in the early stages of the software life cycle when the details of software have not
been revealed yet. Several commercial and non-commercial tools exist to estimate software
in the early stages. Most software effort estimation methods require software size as one of
the important metric inputs and consequently, software size estimation in the early stages
becomes essential.
The proposed method presents a techniques using fuzzy logic theory to improve the
accuracy of the use case points method by refining the use case classification.
SE18_Lec 07_System Modelling and Context ModelAmr E. Mohamed
System modeling is the process of developing abstract models of a system using graphical notation like UML. It helps analysts understand system functionality and communicate with customers. Models present different views like external context, structural organization, dynamic behavior, and interactions. Key UML diagrams include use case, class, sequence, state, and activity diagrams. System context diagrams specifically focus on external factors and the system boundaries.
MODEL CHECKERS –TOOLS AND LANGUAGES FOR SYSTEM DESIGN- A SURVEYcsandit
For over four decades now, variants of Model Checkers are being used as an approach for formal verification of systems consisting of software, hardware or combination of both. Though various model checking tools are available like NuSMV, UPPAAL, PRISM, PAT,FDR, it is difficult to comprehend their usage for systems in different domains like telecommunication, automobile, health and entertainment. However, industry experts and researchers have showcased the use of formal verifications techniques in various domains including Networking, Security and Semiconductor design. With current generation systems becoming more complex, there is an urgent need to better understand and use appropriate methodology, language and tool for definite domain. In this paper, we have made an effort to present Model checking in detail with relevance to available tools and languages to specific domain. For novices in the field, this paper would provide knowledge of model checkers languages and tools that would be suitable for various purposes in diverse systems
This document discusses model-based software testing. It defines a model as a depiction of software behavior. Model-based testing uses models to guide testing tasks like test selection and evaluation. Common models include finite state machines, statecharts, UML diagrams, and Markov chains. The document provides an overview of these models and discusses how they are applied to software testing. It also gives examples to illustrate finite state machines and model-based testing terminology.
System Models in Software Engineering SE7koolkampus
The document discusses various types of system models used in requirements engineering including context models, behavioral models, data models, object models, and how CASE workbenches support system modeling. It describes behavioral models like data flow diagrams and state machine models, data models like entity-relationship diagrams, and object models using the Unified Modeling Language. CASE tools can support modeling through features like diagram editors, repositories, and code generation.
The document discusses the Unified Approach (UA) methodology for software development proposed by Ali Bahrami. The UA aims to combine the best practices of other methodologies like Booch, Rumbaugh, and Jacobson while using the Unified Modeling Language (UML). The core of the UA is use case-driven development. It establishes a unified framework around these methodologies using UML for modeling and documenting the software development process. The UA allows for iterative development by allowing moving between analysis, design, and modeling phases.
Integrating profiling into mde compilersijseajournal
Scientific computation requires more and more performance in its algorithms. New massively parallel
architectures suit well to these algorithms. They are known for offering high performance and power
efficiency. Unfortunately, as parallel programming for these architectures requires a complex distribution
of tasks and data, developers find difficult to implement their applications effectively. Although approaches
based on source-to-source intends to provide a low learning curve for parallel programming and take
advantage of architecture features to create optimized applications, programming remains difficult for
neophytes. This work aims at improving performance by returning to the high-level models, specific
execution data from a profiling tool enhanced by smart advices computed by an analysis engine. In order to
keep the link between execution and model, the process is based on a traceability mechanism. Once the
model is automatically annotated, it can be re-factored aiming better performances on the re-generated
code. Hence, this work allows keeping coherence between model and code without forgetting to harness the
power of parallel architectures. To illustrate and clarify key points of this approach, we provide an
experimental example in GPUs context. The example uses a transformation chain from UML-MARTE
models to OpenCL code.
Operations research originated during World War II when scientists applied scientific methods to military operations. It has since been applied to many domains including business, transportation, and public health. Some key OR techniques include linear programming, transportation models, assignment problems, queuing theory, simulation, and inventory control models. The OR process involves formulating the problem, developing a mathematical model, selecting data inputs, solving the model, validating the model, and implementing the solution. Models can be classified as deterministic or stochastic, descriptive, predictive, or prescriptive, static or dynamic, and analytical or simulation-based. OR aims to help management make better decisions through quantitative analysis and optimization of systems and processes.
The document discusses key concepts in software design including:
- The goals of software design are to transform customer requirements into a suitable implementation while meeting constraints like budget and quality.
- Design involves iterations through high-level, detailed, and architectural design phases to identify modules, interfaces, data structures, and algorithms.
- Good design principles include correctness, simplicity, adaptability, and maintainability. This involves modular and hierarchical decomposition.
- Techniques like top-down and bottom-up design, as well as object-oriented design, are used to arrive at a solution through abstraction layers.
International Journal of Engineering and Science Invention (IJESI) is an international journal intended for professionals and researchers in all fields of computer science and electronics. IJESI publishes research articles and reviews within the whole field Engineering Science and Technology, new teaching methods, assessment, validation and the impact of new technologies and it will continue to provide information on the latest trends and developments in this ever-expanding subject. The publications of papers are selected through double peer reviewed to ensure originality, relevance, and readability. The articles published in our journal can be accessed online.
STRUCTURAL VALIDATION OF SOFTWARE PRODUCT LINE VARIANTS: A GRAPH TRANSFORMATI...IJSEA
This document discusses an approach to structurally validating software product line variants using graph transformations. The authors propose using model transformations to automatically validate products according to dependencies defined in the feature diagram. They introduce necessary meta-models and present graph grammars to perform validation using the AToM3 tool. The approach is illustrated through examples.
This document provides an overview of object-oriented analysis and design. It discusses traditional software development approaches versus object-oriented approaches. The key aspects of object-oriented development covered include objects, classes, inheritance, encapsulation, and polymorphism. Software development life cycle stages like planning, analysis, design, implementation and testing are also summarized. The document compares structured and object-oriented approaches and provides examples of object-oriented programming and design methodologies.
The document discusses modeling performance for distributed real-time process control systems early in development. It proposes representing individual system elements like sensors and actuators as periodic processes and using Model Driven Architecture to develop functional models prior to UML models. This allows performance to be animated or calculated early based on individual element models, helping establish performance requirements before implementation.
Generation of Testcases from UML Sequence Diagram and Detecting Deadlocks usi...KIIT
Abstract:In an environment where processes those execute concurrently, speeding up their computation is important. Deadlock
is a major issue that occurs during concurrent execution. In this paper, we present an approach to generate testcases from UML
sequence diagram for detecting deadlocks during the design phase. This will reduce the effort and cost involved to fix deadlocks
at a later stage. Our work begins with design of sequence diagram for the system, then converting it to intermediate graph where
deadlock points are marked and then traverse to get testcases. The testcases thus generated are suitable for detecting deadlocks.
This document provides an introduction to object-oriented analysis and design (OOAD) and the Unified Modeling Language (UML). It discusses the basic concepts of OOAD and how UML uses diagrams to model software systems. UML diagrams can be used in all phases of the software development life cycle, including requirements analysis, design, implementation, and testing. The document also gives an overview of the different parts of UML, such as views, diagrams, relationships, and model elements.
This document provides an overview of modeling and simulation. It defines modeling as representing a system to enable predicting the effects of changes. Simulation involves running experiments on a model. The key steps in modeling and simulation projects are: 1) identifying the problem, 2) formulating and developing the model, 3) validating the model, 4) designing simulation experiments, 5) performing simulations, and 6) analyzing and presenting results. Modeling and simulation can be used for a variety of purposes including education, design evaluation, forecasting, and risk assessment.
A practical approach for model based slicingIOSR Journals
This document presents a methodology for model-based slicing of UML sequence diagrams to extract submodels. The methodology involves:
1. Generating a sequence diagram from requirements and converting it to XML.
2. Parsing the XML with a DOM parser to extract message information.
3. Slicing the message information based on a slicing criteria, such as a variable, to extract relevant messages.
4. Converting the sliced messages back into a simplified sequence diagram fragment focused on the slicing criteria.
The methodology aims to address the difficulty of visualizing and testing large, complex software models by extracting a relevant submodel based on a slicing criteria, making the model easier to understand and test.
The document discusses object-oriented analysis and design (OOAD) and the Unified Modeling Language (UML). It describes OOAD as modeling a system as interacting objects characterized by their class, state, and behavior. Various UML diagrams can show the static structure, dynamic behavior, and runtime deployment of these collaborating objects. It then discusses object-oriented analysis, design, and the Unified Process framework for software development before briefly introducing UML diagrams.
Modeling and Evaluation of Performance and Reliability of Component-based So...Editor IJCATR
Validation of software systems is very useful at the primary stages of their development cycle. Evaluation of functional
requirements is supported by clear and appropriate approaches, but there is no similar strategy for evaluation of non-functional requirements
(such as performance and reliability). Whereas establishing the non-functional requirements have significant effect on success of software
systems, therefore considerable necessities are needed for evaluation of non-functional requirements. Also, if the software performance has
been specified based on performance models, may be evaluated at the primary stages of software development cycle. Therefore, modeling
and evaluation of non-functional requirements in software architecture level, that are designed at the primary stages of software systems
development cycle and prior to implementation, will be very effective.
We propose an approach for evaluate the performance and reliability of software systems, based on formal models (hierarchical timed
colored petri nets) in software architecture level. In this approach, the software architecture is described by UML use case, activity and
component diagrams, then UML model is transformed to an executable model based on hierarchical timed colored petri nets (HTCPN) by a
proposed algorithm. Consequently, upon execution of an executive model and analysis of its results, non-functional requirements including
performance (such as response time) and reliability may be evaluated in software architecture level.
Model Based Testing Tools discusses model-based testing where a model of the system is used to automatically generate test cases. It outlines how MBT works by deriving an abstract test suite from the model, then mapping those tests to concrete executable tests. The benefits of MBT include increased testing effectiveness and potential cost savings. Several MBT tools used in industry are also described, including Conformiq, Reactis Tester, and Spec Explorer.
Object-oriented analysis and design (OOAD) uses visual modeling techniques like the Unified Modeling Language (UML) to analyze and design systems based on interacting objects. UML captures system elements and facilitates specification and visualization. It includes static diagrams for non-changing characteristics and dynamic diagrams for changing behaviors. The goal of OOAD and UML is to integrate analysis and development teams through defined processes and modeling.
Object-oriented analysis and design (OOAD) uses visual modeling techniques like the Unified Modeling Language (UML) to analyze and design systems based on interacting objects. UML captures system elements and facilitates specification and visualization. It includes static diagrams for non-changing characteristics and dynamic diagrams for changing behaviors. The goal of OOAD and UML is to integrate analysis and development teams through defined processes and modeling.
A Novel Approach to Derive the Average-Case Behavior of Distributed Embedded ...ijccmsjournal
Monte-Carlo simulation is widely used in distributed embedded system in our present era. In this
research work, we have put an emphasis on reliability assessment of any distributed embedded system
through Monte-Carlo simulation. We have done this assessment on random data which represents input
voltages ranging from 0 volt to 12 volt; several numbers of trials have been executed on those data to
check the average case behavior of a distributed real time embedded system. From the experimental result, a saturation point has been achieved against the time behavior which shows the average case behavior of the concerned distributed embedded system.
TRANSFORMING SOFTWARE REQUIREMENTS INTO TEST CASES VIA MODEL TRANSFORMATIONijseajournal
Executable test cases originate at the onset of testing as abstract requirements that represent system
behavior. Their manual development is time-consuming, susceptible to errors, and expensive. Translating
system requirements into behavioral models and then transforming them into a scripting language has the
potential to automate their conversion into executable tests. Ideally, an effective testing process should
start as early as possible, refine the use cases with ample details, and facilitate the creation of test cases.
We propose a methodology that enables automation in converting functional requirements into executable
test cases via model transformation. The proposed testing process starts with capturing system behavior in
the form of visual use cases, using a domain-specific language, defining transformation rules, and
ultimately transforming the use cases into executable tests.
an analysis and new methodology for reverse engineering of uml behavioralINFOGAIN PUBLICATION
The emergence of Unified Modeling Language (UML) as a standard for modeling systems has encouraged the use of automated software tools that facilitate the development process from analysis through coding. Reverse Engineering has become a viable method to measure an existing system and reconstruct the necessary model from its original. The Reverse Engineering of behavioral models consists in extracting high-level models that help understand the behavior of existing software systems. In this paper we present an ongoing work on extracting UML diagrams from object-oriented programming languages. we propose an approach for the reverse engineering of UML behavior from the analysis of execution traces produced dynamically by an object-oriented application using formal and semi-formal techniques for modeling the dynamic behavior of a system. Our methods show that this approach can produce UML behavioral diagrams in reasonable time and suggest that these diagrams are helpful in understanding the behavior of the underlying application.
This document describes a collaboration between Aalborg University and NOVO Nordisk to develop an automatic model-based testing tool for GUI testing on embedded medical devices. The tool takes UML state machine models of the GUI as input, generates test cases to satisfy coverage criteria like edge coverage, and converts the tests to a scripting language to run on the target system. The tool significantly reduced test construction time from 30 days to 3 days, decreased the number of tests while improving coverage, and uncovered bugs. Both organizations found the collaboration and use of the testing tool to be very successful and beneficial.
MANAGING AND ANALYSING SOFTWARE PRODUCT LINE REQUIREMENTSijseajournal
Modelling software product line (SPL) features plays a crucial role to a successful development of SPL.
Feature diagram is one of the widely used notations to model SPL variants. However, there is a lack of
precisely defined formal notations for representing and verifying such models. This paper presents an
approach that we adopt to model SPL variants by using UML and subsequently verify them by using firstorder
logic. UML provides an overall modelling view of the system. First-order logic provides a precise
and rigorous interpretation of the feature diagrams. We model variants and their dependencies by using
propositional connectives and build logical expressions. These expressions are then validated by the Alloy
verification tool. The analysis and verification process is illustrated by using Computer Aided Dispatch
(CAD) system.
General Methodology for developing UML models from UIijwscjournal
In recent past every discipline and every industry have their own methods of developing products. It may
be software development, mechanics, construction, psychology and so on. These demarcations work fine
as long as the requirements are within one discipline. However, if the project extends over several
disciplines, interfaces have to be created and coordinated between the methods of these disciplines.
Performance is an important quality aspect of Web Services because of their distributed nature.
Predicting the performance of web services during early stages of software development is significant. In
Industry, Prototype of these applications is developed during analysis phase of Software Development Life
Cycle (SDLC). However, Performance models are generated from UML models. Methodologies for
predicting the performance from UML models is available. Hence, In this paper, a methodology for
developing Use Case model and Activity model from User Interface is presented. The methodology is
illustrated with a case study on Amazon.com
General Methodology for developing UML models from UIijwscjournal
In recent past every discipline and every industry have their own methods of developing products. It may
be software development, mechanics, construction, psychology and so on. These demarcations work fine
as long as the requirements are within one discipline. However, if the project extends over several
disciplines, interfaces have to be created and coordinated between the methods of these disciplines.
Performance is an important quality aspect of Web Services because of their distributed nature.
Predicting the performance of web services during early stages of software development is significant. In
Industry, Prototype of these applications is developed during analysis phase of Software Development Life
Cycle (SDLC). However, Performance models are generated from UML models. Methodologies for
predicting the performance from UML models is available. Hence, In this paper, a methodology for
developing Use Case model and Activity model from User Interface is presented. The methodology is
illustrated with a case study on Amazon.com.
General Methodology for developing UML models from UI ijwscjournal
In recent past every discipline and every industry have their own methods of developing products. It may be software development, mechanics, construction, psychology and so on. These demarcations work fine as long as the requirements are within one discipline. However, if the project extends over several disciplines, interfaces have to be created and coordinated between the methods of these disciplines.
Performance is an important quality aspect of Web Services because of their distributed nature. Predicting the performance of web services during early stages of software development is significant. In Industry, Prototype of these applications is developed during analysis phase of Software Development Life
Cycle (SDLC). However, Performance models are generated from UML models. Methodologies for predicting the performance from UML models is available. Hence, In this paper, a methodology for developing Use Case model and Activity model from User Interface is presented. The methodology is illustrated with a case study on Amazon.com.
General Methodology for developing UML models from UIijwscjournal
In recent past every discipline and every industry have their own methods of developing products. It may be software development, mechanics, construction, psychology and so on. These demarcations work fine as long as the requirements are within one discipline. However, if the project extends over several disciplines, interfaces have to be created and coordinated between the methods of these disciplines. Performance is an important quality aspect of Web Services because of their distributed nature. Predicting the performance of web services during early stages of software development is significant. In Industry, Prototype of these applications is developed during analysis phase of Software Development Life Cycle (SDLC). However, Performance models are generated from UML models. Methodologies for predicting the performance from UML models is available. Hence, In this paper, a methodology for developing Use Case model and Activity model from User Interface is presented. The methodology is illustrated with a case study on Amazon.com.
General Methodology for developing UML models from UIijwscjournal
The document presents a methodology for developing UML models from a user interface prototype. The methodology involves identifying user interface elements from the prototype, developing a flow diagram of the elements, creating an activity model, and developing a use case model. The methodology is demonstrated through a case study of developing UML models for the login page of the Amazon.com website. Key steps include identifying UI elements like workspaces and functions, creating a flow diagram to show the main and exception flows, developing an activity model of the login process, and specifying a use case for login and authentication.
Similar to Generation and Optimization of Test cases for Object-Oriented Software Using State Chart Diagram (20)
ANALYSIS OF LAND SURFACE DEFORMATION GRADIENT BY DINSAR cscpconf
The progressive development of Synthetic Aperture Radar (SAR) systems diversify the exploitation of the generated images by these systems in different applications of geoscience. Detection and monitoring surface deformations, procreated by various phenomena had benefited from this evolution and had been realized by interferometry (InSAR) and differential interferometry (DInSAR) techniques. Nevertheless, spatial and temporal decorrelations of the interferometric couples used, limit strongly the precision of analysis results by these techniques. In this context, we propose, in this work, a methodological approach of surface deformation detection and analysis by differential interferograms to show the limits of this technique according to noise quality and level. The detectability model is generated from the deformation signatures, by simulating a linear fault merged to the images couples of ERS1 / ERS2 sensors acquired in a region of the Algerian south.
4D AUTOMATIC LIP-READING FOR SPEAKER'S FACE IDENTIFCATIONcscpconf
A novel based a trajectory-guided, concatenating approach for synthesizing high-quality image real sample renders video is proposed . The lips reading automated is seeking for modeled the closest real image sample sequence preserve in the library under the data video to the HMM predicted trajectory. The object trajectory is modeled obtained by projecting the face patterns into an KDA feature space is estimated. The approach for speaker's face identification by using synthesise the identity surface of a subject face from a small sample of patterns which sparsely each the view sphere. An KDA algorithm use to the Lip-reading image is discrimination, after that work consisted of in the low dimensional for the fundamental lip features vector is reduced by using the 2D-DCT.The mouth of the set area dimensionality is ordered by a normally reduction base on the PCA to obtain the Eigen lips approach, their proposed approach by[33]. The subjective performance results of the cost function under the automatic lips reading modeled , which wasn’t illustrate the superior performance of the
method.
MOVING FROM WATERFALL TO AGILE PROCESS IN SOFTWARE ENGINEERING CAPSTONE PROJE...cscpconf
Universities offer software engineering capstone course to simulate a real world-working environment in which students can work in a team for a fixed period to deliver a quality product. The objective of the paper is to report on our experience in moving from Waterfall process to Agile process in conducting the software engineering capstone project. We present the capstone course designs for both Waterfall driven and Agile driven methodologies that highlight the structure, deliverables and assessment plans.To evaluate the improvement, we conducted a survey for two different sections taught by two different instructors to evaluate students’ experience in moving from traditional Waterfall model to Agile like process. Twentyeight students filled the survey. The survey consisted of eight multiple-choice questions and an open-ended question to collect feedback from students. The survey results show that students were able to attain hands one experience, which simulate a real world-working environment. The results also show that the Agile approach helped students to have overall better design and avoid mistakes they have made in the initial design completed in of the first phase of the capstone project. In addition, they were able to decide on their team capabilities, training needs and thus learn the required technologies earlier which is reflected on the final product quality
PROMOTING STUDENT ENGAGEMENT USING SOCIAL MEDIA TECHNOLOGIEScscpconf
This document discusses using social media technologies to promote student engagement in a software project management course. It describes the course and objectives of enhancing communication. It discusses using Facebook for 4 years, then switching to WhatsApp based on student feedback, and finally introducing Slack to enable personalized team communication. Surveys found students engaged and satisfied with all three tools, though less familiar with Slack. The conclusion is that social media promotes engagement but familiarity with the tool also impacts satisfaction.
A SURVEY ON QUESTION ANSWERING SYSTEMS: THE ADVANCES OF FUZZY LOGICcscpconf
In real world computing environment with using a computer to answer questions has been a human dream since the beginning of the digital era, Question-answering systems are referred to as intelligent systems, that can be used to provide responses for the questions being asked by the user based on certain facts or rules stored in the knowledge base it can generate answers of questions asked in natural , and the first main idea of fuzzy logic was to working on the problem of computer understanding of natural language, so this survey paper provides an overview on what Question-Answering is and its system architecture and the possible relationship and
different with fuzzy logic, as well as the previous related research with respect to approaches that were followed. At the end, the survey provides an analytical discussion of the proposed QA models, along or combined with fuzzy logic and their main contributions and limitations.
DYNAMIC PHONE WARPING – A METHOD TO MEASURE THE DISTANCE BETWEEN PRONUNCIATIONS cscpconf
Human beings generate different speech waveforms while speaking the same word at different times. Also, different human beings have different accents and generate significantly varying speech waveforms for the same word. There is a need to measure the distances between various words which facilitate preparation of pronunciation dictionaries. A new algorithm called Dynamic Phone Warping (DPW) is presented in this paper. It uses dynamic programming technique for global alignment and shortest distance measurements. The DPW algorithm can be used to enhance the pronunciation dictionaries of the well-known languages like English or to build pronunciation dictionaries to the less known sparse languages. The precision measurement experiments show 88.9% accuracy.
INTELLIGENT ELECTRONIC ASSESSMENT FOR SUBJECTIVE EXAMS cscpconf
In education, the use of electronic (E) examination systems is not a novel idea, as Eexamination systems have been used to conduct objective assessments for the last few years. This research deals with randomly designed E-examinations and proposes an E-assessment system that can be used for subjective questions. This system assesses answers to subjective questions by finding a matching ratio for the keywords in instructor and student answers. The matching ratio is achieved based on semantic and document similarity. The assessment system is composed of four modules: preprocessing, keyword expansion, matching, and grading. A survey and case study were used in the research design to validate the proposed system. The examination assessment system will help instructors to save time, costs, and resources, while increasing efficiency and improving the productivity of exam setting and assessments.
TWO DISCRETE BINARY VERSIONS OF AFRICAN BUFFALO OPTIMIZATION METAHEURISTICcscpconf
African Buffalo Optimization (ABO) is one of the most recent swarms intelligence based metaheuristics. ABO algorithm is inspired by the buffalo’s behavior and lifestyle. Unfortunately, the standard ABO algorithm is proposed only for continuous optimization problems. In this paper, the authors propose two discrete binary ABO algorithms to deal with binary optimization problems. In the first version (called SBABO) they use the sigmoid function and probability model to generate binary solutions. In the second version (called LBABO) they use some logical operator to operate the binary solutions. Computational results on two knapsack problems (KP and MKP) instances show the effectiveness of the proposed algorithm and their ability to achieve good and promising solutions.
DETECTION OF ALGORITHMICALLY GENERATED MALICIOUS DOMAINcscpconf
In recent years, many malware writers have relied on Dynamic Domain Name Services (DDNS) to maintain their Command and Control (C&C) network infrastructure to ensure a persistence presence on a compromised host. Amongst the various DDNS techniques, Domain Generation Algorithm (DGA) is often perceived as the most difficult to detect using traditional methods. This paper presents an approach for detecting DGA using frequency analysis of the character distribution and the weighted scores of the domain names. The approach’s feasibility is demonstrated using a range of legitimate domains and a number of malicious algorithmicallygenerated domain names. Findings from this study show that domain names made up of English characters “a-z” achieving a weighted score of < 45 are often associated with DGA. When a weighted score of < 45 is applied to the Alexa one million list of domain names, only 15% of the domain names were treated as non-human generated.
GLOBAL MUSIC ASSET ASSURANCE DIGITAL CURRENCY: A DRM SOLUTION FOR STREAMING C...cscpconf
The document proposes a blockchain-based digital currency and streaming platform called GoMAA to address issues of piracy in the online music streaming industry. Key points:
- GoMAA would use a digital token on the iMediaStreams blockchain to enable secure dissemination and tracking of streamed content. Content owners could control access and track consumption of released content.
- Original media files would be converted to a Secure Portable Streaming (SPS) format, embedding watermarks and smart contract data to indicate ownership and enable validation on the blockchain.
- A browser plugin would provide wallets for fans to collect GoMAA tokens as rewards for consuming content, incentivizing participation and addressing royalty discrepancies by recording
IMPORTANCE OF VERB SUFFIX MAPPING IN DISCOURSE TRANSLATION SYSTEMcscpconf
This document discusses the importance of verb suffix mapping in discourse translation from English to Telugu. It explains that after anaphora resolution, the verbs must be changed to agree with the gender, number, and person features of the subject or anaphoric pronoun. Verbs in Telugu inflect based on these features, while verbs in English only inflect based on number and person. Several examples are provided that demonstrate how the Telugu verb changes based on whether the subject or pronoun is masculine, feminine, neuter, singular or plural. Proper verb suffix mapping is essential for generating natural and coherent translations while preserving the context and meaning of the original discourse.
EXACT SOLUTIONS OF A FAMILY OF HIGHER-DIMENSIONAL SPACE-TIME FRACTIONAL KDV-T...cscpconf
In this paper, based on the definition of conformable fractional derivative, the functional
variable method (FVM) is proposed to seek the exact traveling wave solutions of two higherdimensional
space-time fractional KdV-type equations in mathematical physics, namely the
(3+1)-dimensional space–time fractional Zakharov-Kuznetsov (ZK) equation and the (2+1)-
dimensional space–time fractional Generalized Zakharov-Kuznetsov-Benjamin-Bona-Mahony
(GZK-BBM) equation. Some new solutions are procured and depicted. These solutions, which
contain kink-shaped, singular kink, bell-shaped soliton, singular soliton and periodic wave
solutions, have many potential applications in mathematical physics and engineering. The
simplicity and reliability of the proposed method is verified.
AUTOMATED PENETRATION TESTING: AN OVERVIEWcscpconf
The document discusses automated penetration testing and provides an overview. It compares manual and automated penetration testing, noting that automated testing allows for faster, more standardized and repeatable tests but has limitations in developing new exploits. It also reviews some current automated penetration testing methodologies and tools, including those using HTTP/TCP/IP attacks, linking common scanning tools, a Python-based tool targeting databases, and one using POMDPs for multi-step penetration test planning under uncertainty. The document concludes that automated testing is more efficient than manual for known vulnerabilities but cannot replace manual testing for discovering new exploits.
CLASSIFICATION OF ALZHEIMER USING fMRI DATA AND BRAIN NETWORKcscpconf
Since the mid of 1990s, functional connectivity study using fMRI (fcMRI) has drawn increasing
attention of neuroscientists and computer scientists, since it opens a new window to explore
functional network of human brain with relatively high resolution. BOLD technique provides
almost accurate state of brain. Past researches prove that neuro diseases damage the brain
network interaction, protein- protein interaction and gene-gene interaction. A number of
neurological research paper also analyse the relationship among damaged part. By
computational method especially machine learning technique we can show such classifications.
In this paper we used OASIS fMRI dataset affected with Alzheimer’s disease and normal
patient’s dataset. After proper processing the fMRI data we use the processed data to form
classifier models using SVM (Support Vector Machine), KNN (K- nearest neighbour) & Naïve
Bayes. We also compare the accuracy of our proposed method with existing methods. In future,
we will other combinations of methods for better accuracy.
VALIDATION METHOD OF FUZZY ASSOCIATION RULES BASED ON FUZZY FORMAL CONCEPT AN...cscpconf
The document proposes a new validation method for fuzzy association rules based on three steps: (1) applying the EFAR-PN algorithm to extract a generic base of non-redundant fuzzy association rules using fuzzy formal concept analysis, (2) categorizing the extracted rules into groups, and (3) evaluating the relevance of the rules using structural equation modeling, specifically partial least squares. The method aims to address issues with existing fuzzy association rule extraction algorithms such as large numbers of extracted rules, redundancy, and difficulties with manual validation.
PROBABILITY BASED CLUSTER EXPANSION OVERSAMPLING TECHNIQUE FOR IMBALANCED DATAcscpconf
In many applications of data mining, class imbalance is noticed when examples in one class are
overrepresented. Traditional classifiers result in poor accuracy of the minority class due to the
class imbalance. Further, the presence of within class imbalance where classes are composed of
multiple sub-concepts with different number of examples also affect the performance of
classifier. In this paper, we propose an oversampling technique that handles between class and
within class imbalance simultaneously and also takes into consideration the generalization
ability in data space. The proposed method is based on two steps- performing Model Based
Clustering with respect to classes to identify the sub-concepts; and then computing the
separating hyperplane based on equal posterior probability between the classes. The proposed
method is tested on 10 publicly available data sets and the result shows that the proposed
method is statistically superior to other existing oversampling methods.
CHARACTER AND IMAGE RECOGNITION FOR DATA CATALOGING IN ECOLOGICAL RESEARCHcscpconf
Data collection is an essential, but manpower intensive procedure in ecological research. An
algorithm was developed by the author which incorporated two important computer vision
techniques to automate data cataloging for butterfly measurements. Optical Character
Recognition is used for character recognition and Contour Detection is used for imageprocessing.
Proper pre-processing is first done on the images to improve accuracy. Although
there are limitations to Tesseract’s detection of certain fonts, overall, it can successfully identify
words of basic fonts. Contour detection is an advanced technique that can be utilized to
measure an image. Shapes and mathematical calculations are crucial in determining the precise
location of the points on which to draw the body and forewing lines of the butterfly. Overall,
92% accuracy were achieved by the program for the set of butterflies measured.
SOCIAL MEDIA ANALYTICS FOR SENTIMENT ANALYSIS AND EVENT DETECTION IN SMART CI...cscpconf
Smart cities utilize Internet of Things (IoT) devices and sensors to enhance the quality of the city
services including energy, transportation, health, and much more. They generate massive
volumes of structured and unstructured data on a daily basis. Also, social networks, such as
Twitter, Facebook, and Google+, are becoming a new source of real-time information in smart
cities. Social network users are acting as social sensors. These datasets so large and complex
are difficult to manage with conventional data management tools and methods. To become
valuable, this massive amount of data, known as 'big data,' needs to be processed and
comprehended to hold the promise of supporting a broad range of urban and smart cities
functions, including among others transportation, water, and energy consumption, pollution
surveillance, and smart city governance. In this work, we investigate how social media analytics
help to analyze smart city data collected from various social media sources, such as Twitter and
Facebook, to detect various events taking place in a smart city and identify the importance of
events and concerns of citizens regarding some events. A case scenario analyses the opinions of
users concerning the traffic in three largest cities in the UAE
SOCIAL NETWORK HATE SPEECH DETECTION FOR AMHARIC LANGUAGEcscpconf
The anonymity of social networks makes it attractive for hate speech to mask their criminal
activities online posing a challenge to the world and in particular Ethiopia. With this everincreasing
volume of social media data, hate speech identification becomes a challenge in
aggravating conflict between citizens of nations. The high rate of production, has become
difficult to collect, store and analyze such big data using traditional detection methods. This
paper proposed the application of apache spark in hate speech detection to reduce the
challenges. Authors developed an apache spark based model to classify Amharic Facebook
posts and comments into hate and not hate. Authors employed Random forest and Naïve Bayes
for learning and Word2Vec and TF-IDF for feature selection. Tested by 10-fold crossvalidation,
the model based on word2vec embedding performed best with 79.83%accuracy. The
proposed method achieve a promising result with unique feature of spark for big data.
GENERAL REGRESSION NEURAL NETWORK BASED POS TAGGING FOR NEPALI TEXTcscpconf
This article presents Part of Speech tagging for Nepali text using General Regression Neural
Network (GRNN). The corpus is divided into two parts viz. training and testing. The network is
trained and validated on both training and testing data. It is observed that 96.13% words are
correctly being tagged on training set whereas 74.38% words are tagged correctly on testing
data set using GRNN. The result is compared with the traditional Viterbi algorithm based on
Hidden Markov Model. Viterbi algorithm yields 97.2% and 40% classification accuracies on
training and testing data sets respectively. GRNN based POS Tagger is more consistent than the
traditional Viterbi decoding technique.
Strategies for Effective Upskilling is a presentation by Chinwendu Peace in a Your Skill Boost Masterclass organisation by the Excellence Foundation for South Sudan on 08th and 09th June 2024 from 1 PM to 3 PM on each day.
it describes the bony anatomy including the femoral head , acetabulum, labrum . also discusses the capsule , ligaments . muscle that act on the hip joint and the range of motion are outlined. factors affecting hip joint stability and weight transmission through the joint are summarized.
Gender and Mental Health - Counselling and Family Therapy Applications and In...PsychoTech Services
A proprietary approach developed by bringing together the best of learning theories from Psychology, design principles from the world of visualization, and pedagogical methods from over a decade of training experience, that enables you to: Learn better, faster!
Philippine Edukasyong Pantahanan at Pangkabuhayan (EPP) CurriculumMJDuyan
(𝐓𝐋𝐄 𝟏𝟎𝟎) (𝐋𝐞𝐬𝐬𝐨𝐧 𝟏)-𝐏𝐫𝐞𝐥𝐢𝐦𝐬
𝐃𝐢𝐬𝐜𝐮𝐬𝐬 𝐭𝐡𝐞 𝐄𝐏𝐏 𝐂𝐮𝐫𝐫𝐢𝐜𝐮𝐥𝐮𝐦 𝐢𝐧 𝐭𝐡𝐞 𝐏𝐡𝐢𝐥𝐢𝐩𝐩𝐢𝐧𝐞𝐬:
- Understand the goals and objectives of the Edukasyong Pantahanan at Pangkabuhayan (EPP) curriculum, recognizing its importance in fostering practical life skills and values among students. Students will also be able to identify the key components and subjects covered, such as agriculture, home economics, industrial arts, and information and communication technology.
𝐄𝐱𝐩𝐥𝐚𝐢𝐧 𝐭𝐡𝐞 𝐍𝐚𝐭𝐮𝐫𝐞 𝐚𝐧𝐝 𝐒𝐜𝐨𝐩𝐞 𝐨𝐟 𝐚𝐧 𝐄𝐧𝐭𝐫𝐞𝐩𝐫𝐞𝐧𝐞𝐮𝐫:
-Define entrepreneurship, distinguishing it from general business activities by emphasizing its focus on innovation, risk-taking, and value creation. Students will describe the characteristics and traits of successful entrepreneurs, including their roles and responsibilities, and discuss the broader economic and social impacts of entrepreneurial activities on both local and global scales.
हिंदी वर्णमाला पीपीटी, hindi alphabet PPT presentation, hindi varnamala PPT, Hindi Varnamala pdf, हिंदी स्वर, हिंदी व्यंजन, sikhiye hindi varnmala, dr. mulla adam ali, hindi language and literature, hindi alphabet with drawing, hindi alphabet pdf, hindi varnamala for childrens, hindi language, hindi varnamala practice for kids, https://www.drmullaadamali.com
ISO/IEC 27001, ISO/IEC 42001, and GDPR: Best Practices for Implementation and...PECB
Denis is a dynamic and results-driven Chief Information Officer (CIO) with a distinguished career spanning information systems analysis and technical project management. With a proven track record of spearheading the design and delivery of cutting-edge Information Management solutions, he has consistently elevated business operations, streamlined reporting functions, and maximized process efficiency.
Certified as an ISO/IEC 27001: Information Security Management Systems (ISMS) Lead Implementer, Data Protection Officer, and Cyber Risks Analyst, Denis brings a heightened focus on data security, privacy, and cyber resilience to every endeavor.
His expertise extends across a diverse spectrum of reporting, database, and web development applications, underpinned by an exceptional grasp of data storage and virtualization technologies. His proficiency in application testing, database administration, and data cleansing ensures seamless execution of complex projects.
What sets Denis apart is his comprehensive understanding of Business and Systems Analysis technologies, honed through involvement in all phases of the Software Development Lifecycle (SDLC). From meticulous requirements gathering to precise analysis, innovative design, rigorous development, thorough testing, and successful implementation, he has consistently delivered exceptional results.
Throughout his career, he has taken on multifaceted roles, from leading technical project management teams to owning solutions that drive operational excellence. His conscientious and proactive approach is unwavering, whether he is working independently or collaboratively within a team. His ability to connect with colleagues on a personal level underscores his commitment to fostering a harmonious and productive workplace environment.
Date: May 29, 2024
Tags: Information Security, ISO/IEC 27001, ISO/IEC 42001, Artificial Intelligence, GDPR
-------------------------------------------------------------------------------
Find out more about ISO training and certification services
Training: ISO/IEC 27001 Information Security Management System - EN | PECB
ISO/IEC 42001 Artificial Intelligence Management System - EN | PECB
General Data Protection Regulation (GDPR) - Training Courses - EN | PECB
Webinars: https://pecb.com/webinars
Article: https://pecb.com/article
-------------------------------------------------------------------------------
For more information about PECB:
Website: https://pecb.com/
LinkedIn: https://www.linkedin.com/company/pecb/
Facebook: https://www.facebook.com/PECBInternational/
Slideshare: http://www.slideshare.net/PECBCERTIFICATION
Chapter wise All Notes of First year Basic Civil Engineering.pptxDenish Jangid
Chapter wise All Notes of First year Basic Civil Engineering
Syllabus
Chapter-1
Introduction to objective, scope and outcome the subject
Chapter 2
Introduction: Scope and Specialization of Civil Engineering, Role of civil Engineer in Society, Impact of infrastructural development on economy of country.
Chapter 3
Surveying: Object Principles & Types of Surveying; Site Plans, Plans & Maps; Scales & Unit of different Measurements.
Linear Measurements: Instruments used. Linear Measurement by Tape, Ranging out Survey Lines and overcoming Obstructions; Measurements on sloping ground; Tape corrections, conventional symbols. Angular Measurements: Instruments used; Introduction to Compass Surveying, Bearings and Longitude & Latitude of a Line, Introduction to total station.
Levelling: Instrument used Object of levelling, Methods of levelling in brief, and Contour maps.
Chapter 4
Buildings: Selection of site for Buildings, Layout of Building Plan, Types of buildings, Plinth area, carpet area, floor space index, Introduction to building byelaws, concept of sun light & ventilation. Components of Buildings & their functions, Basic concept of R.C.C., Introduction to types of foundation
Chapter 5
Transportation: Introduction to Transportation Engineering; Traffic and Road Safety: Types and Characteristics of Various Modes of Transportation; Various Road Traffic Signs, Causes of Accidents and Road Safety Measures.
Chapter 6
Environmental Engineering: Environmental Pollution, Environmental Acts and Regulations, Functional Concepts of Ecology, Basics of Species, Biodiversity, Ecosystem, Hydrological Cycle; Chemical Cycles: Carbon, Nitrogen & Phosphorus; Energy Flow in Ecosystems.
Water Pollution: Water Quality standards, Introduction to Treatment & Disposal of Waste Water. Reuse and Saving of Water, Rain Water Harvesting. Solid Waste Management: Classification of Solid Waste, Collection, Transportation and Disposal of Solid. Recycling of Solid Waste: Energy Recovery, Sanitary Landfill, On-Site Sanitation. Air & Noise Pollution: Primary and Secondary air pollutants, Harmful effects of Air Pollution, Control of Air Pollution. . Noise Pollution Harmful Effects of noise pollution, control of noise pollution, Global warming & Climate Change, Ozone depletion, Greenhouse effect
Text Books:
1. Palancharmy, Basic Civil Engineering, McGraw Hill publishers.
2. Satheesh Gopi, Basic Civil Engineering, Pearson Publishers.
3. Ketki Rangwala Dalal, Essentials of Civil Engineering, Charotar Publishing House.
4. BCP, Surveying volume 1
2. 408 Computer Science & Information Technology (CS & IT)
properly generated test suite may not only locate the errors in a software system, but also help in
reducing the high cost associated with software testing [16]. Many present day software solutions
are state based. In such systems, the system behavior is determined by its state. In other words, a
system can respond differently to the same event in different states. Therefore, unless a system is
made to assume all its possible states and tested, it would not be possible to uncover state-based
bugs. Adequate system testing of such software requires satisfactory coverage of system states
and transitions. Generation of test specifications to meet these coverage criteria can be
accomplished by using the state model of a system. However, it is a non-trivial task to manually
construct the state model of a system. The state model of an actual system is usually extremely
complex and comprises of a large number of states and transitions. Possibly for this reason, state
models of complete systems are rarely constructed by system developers [26].
Testing activities consist of designing test cases that are sequences of inputs, executing the
program with test cases and examining the results produced by this execution. Testing can be
carried out earlier in the development process so that the developer will be able to find the
inconsistencies and ambiguities in the specification and hence will be able to improve the
specification before the program is written [11]. Unified modeling language (UML) has emerged
as the de facto standard for modeling software systems and has received significant attention from
researchers as well as practitioners. UML models are popular not only for designing and
documenting systems, the importance of UML models in designing test cases has also been well
recognized. Even though UML models are intended to help reduce the complexity of a problem,
with the increase in product sizes and complexities, the UML models themselves become large
and complex involving thousands of interactions across hundreds of objects [15]. The important
part of quality control in the software life-cycle is testing. As the complexity and size of software
increase, the time and effort required to do sufficient testing grow. Manual testing is time-
consuming and error prone. So, there is a pressing to automate the testing process. The testing
process can be divided into three parts: test case generation, test execution, and test evaluation.
The latter two parts are relatively easy to automate provided that the criteria for passing the tests
are available. However, to determine which tests are required to achieve a certain level of
confidence is not trivial [17].
Model-based testing [5] has grown in importance. Models are specified to represent the relevant,
desirable features of the system under consideration (SUC). These models are used as a basis for
(automatically) generating test cases to be applied to the SUC. Typical models that are used for
representing system behavior are unified modeling language, finite state machines, state charts
etc. [3].
With this motivation, we aim our work at deriving the test sequence from state transition diagram
and maximizing state or node coverage. Also our method minimizes the size of test, time and
cost, while preserving test coverage. The rest of the paper is structured as follows: A brief
discussion on UML diagrams, which are relevant to our paper is described in the Section 2. Then,
we discuss some testing coverage criteria in Section 3. Section 4 represents some concepts,
notations and definitions of state chart diagram. In Section 5, we explain the overview of our
proposed method for construction of state transition graph, generation of test sequence using state
charts and how node coverage is calculated for each test case. Section 6 provides the working of
our methodology with the ATM (Automatic Ticket Machine) case study. Section 7 discusses
some related work. Finally, Section 7 presents the conclusion and future work of this paper.
2. UML DIAGRAMS
In this section, we discuss some basic concepts which will be used subsequently in our paper.
UML, Unified Modeling Language is a visual language that has been developed to support the
design of complex object-oriented systems. Since its introduction in the late 90s, it has undergone
3. Computer Science & Information Technology (CS & IT) 409
several revisions. The latest release being UML version 2.0, which adds several new capabilities
to UML 1.x. In this section, we restrict our review to only those developments that are directly
relevant to our work. A typical software procedure incorporates all the three aspects: It uses data
structure (class model), it sequences operations in time (state model), and it passes data and
control among objects (interaction model). The three kinds of models separate a system into
different views. The different models are not completely independent but a system is more than a
collection of these independent parts. UML specification defines two major kinds of UML
diagram: structural diagrams and behavioral diagrams.
The elements in a structural diagram represent the meaningful concepts of a system, and may
include abstract, real world and implementation concepts. Behavioral diagrams show the dynamic
behavior of the objects in a system, which can be described as a series of changes to the system
over time.
2.1. UML state chart diagram
In this section, we explain the few fundamentals on state chart diagram. The name of the diagram
itself clarifies the purpose of the diagram and other details. It describes different states of a
component in a system. The states are specific to a component or object of a system. A state chart
diagram describes a state machine. Now to clarify it state machine can be defined as a machine
which defines different states of an object and these states are controlled by external or internal
events. State chart diagram is one of the five UML diagrams used to model dynamic nature of a
system. They define different states of an object during its lifetime. And these states are changed
by events. So state chart diagrams are useful to model reactive systems. Reactive systems can be
defined as a system that responds to external or internal events. State chart diagram describes the
flow of control from one state to another state. States are defined as a condition in which an
object exists and it changes when some event is triggered. So the most important purpose of State
chart diagram is to model life time of an object from creation to termination. State chart diagrams
are also used for forward and reverse engineering of a system. But the main purpose is to model
reactive system.
State diagrams are used to give an abstract description of the behavior of a system. This behavior
is analyzed and represented in series of events that could occur in one or more possible states.
Hereby “each diagram usually represents objects of a single class and tracks the different states of
its objects through the system”. State diagrams can be used to graphically represent finite state
machines. Followings are the main purposes of using state chart diagrams:
• To model dynamic aspect of a system.
• To model life time of a reactive system.
• To describe different states of an object during its lifetime.
• To define a state machine to model states of an object.
Figure. 1. Basic concepts of a simple state chart for a coin machine and reservation class
4. 410 Computer Science & Information Technology (CS & IT)
The basic components of a state chart diagram are - events, states and transitions. But it has some
distinguishing characteristics for modeling dynamic nature. State chart diagram defines the states
of a component and these state changes are dynamic in nature. So, its specific purpose is to
represent the state changes triggered by events. Events are internal or external factors influencing
the system. If we look into the practical implementation of state chart diagram then it is mainly
used to analyze the object states influenced by events. This analysis is helpful to understand the
system behavior during its execution. The following are the basic notational elements that can be
used to make up a diagram:
2.1.1. State: The state of an object is represented by rectangle with rounded corners. Top of the
rectangle contains a name of the state. It can contain a horizontal line in the middle, below which
the activities that are done in that state are indicated. A state in a state chart diagram can either be
simple or composite type. A simple state does not have any sub-states. A composite state, on the
other hand, consists of one or more regions. A region is a container for sub-states.
2.1.2. Initial state: A transition leading from an initial event shows the state that an object goes
into when it is created or initialized. This is shown as a small black disk or filled circle. A state-
chart can have only one initial state.
2.1.3. Final state: Like initial state the state diagram shows final state. It represents the state
reached when an object is destroyed, switched off or stops responding to events. This is shown as
a hollow circle containing a smaller filled circle or small black disk within a large circle. A state-
chart may have more than one final state. A transition to a history state causes the sub state that
was most recently active in the composite state to become active again [22].
2.1.4. Transition: Arrows, denote transitions. The name of the event (if any) causing this
transition is written as the labels with the transition names or event names. A guard expression
may be added before a “/” and enclosed in square-brackets (event Name [guard Expression]),
denoting that this expression must be true for the transition to take place. The general format of
the label of a transition is as follows:
Event [guard-constraint] ‘/’ activity-expression/action
2.1.5. An event: An event is an occurrence at a point of time. Events often correspond to verbs in
the past tense e.g. (power turned on, alarm set) [4]. Events include error conditions as well as
normal occurrences, e.g. motor jammed, transaction aborted etc.
3. TEST ADEQUECY CRITERIA
Testing coverage / adequacy criterion specifies the requirement of a particular testing, and can be
used as an objective measurement of the test case. In traditional software code testing, the
definition of testing adequacy is defined as a measurement function. The case of UML state chart
diagrams is different because it is in the form of model instead of code. Especially the coverage
of state chart diagram is little bit complex. In this paper, we propose different types of coverage
metrics as follows:
• State Coverage requires that all the state nodes in a state chart diagram be covered. The
value of state coverage is the ratio between the covered states and all the states in the
state chart diagram.
• Action Coverage: In order to generate test cases with respect to action coverage we
construct as many marked specifications as there are actions within the specification.
5. Computer Science & Information Technology (CS & IT) 411
• Transition Coverage requires that all the completion transitions in a state chart diagram
be covered. The value of transition coverage is the ratio between the checked transitions
and all the transitions in the state chart diagram.
• Path Coverage requires that all the paths in a state chart diagram be covered. The value
of path coverage is the ratio between the traversed paths and all the paths in the diagram.
• Condition coverage. A decision consists of conditions separated by logical operators
(e.g. and, or). A single condition is covered, if it evaluates to both true and false at some
point during test execution. Decision coverage has also been called branch coverage or
predicate coverage. This means that 100% condition / decision coverage is achieved if all
conditions evaluate to true and to false and if every decision also evaluates to true and to
false during the test execution.
4. SOME BASIC DEFINITIONS
There are many forms of state diagrams, which differ slightly and have different semantics. For a
deterministic finite state machine (DFA), nondeterministic finite state machine (NFA),
generalized nondeterministic finite state machine (GNFA), Mealy machine or Moore machine,
the input is denoted on each edge. For a Mealy machine, input and output are signified on each
edge, separated with a slash “/”: “1/0” denotes the state change upon encountering the symbol “1”
causing the symbol “0” to be output. For a Moore machine the state’s output is usually written
inside the state’s circle, also separated from the state’s designator with a slash “/”. There are also
variants that combine these two notations.
It is assumed that a state chart STc is correct in the sense that for each state s ∈ Ssimple there exists
a sequence of transitions t1, t2..., tk so that source(t1) ∈ Si and target(tk) = s and for each state s
∈ Ssimple there exists a sequence of transitions t1, t2..., tk so that source(t1) = s and target(tk) ∈
Sf .
The following terms will be used to describe our technique.
Definition 1. A state chart can be a quadruple Sc = (E, St, H, T), where E is a finite set of events
and St = (S, Si, Sf ) is a triple of set of states with S as a finite set of states, Si ⊆ S denoting the
entries (initial states) and Sf ⊆ S the exits (final states),
H ⊆ S × S is a hierarchy relation, a binary relation on the set S forming a tree. For an element (s,
s′ ) ∈ H holds, that a state s is an immediate sub state of state S′.
T ⊆ S × E × S is a finite set T of transitions. The set of states S is composed of disjoint sets of
simple states Ssimple and composite states Scomp.
Definition 2. A transition pair TP = (t, t′ ) with t, t′ belongs to Tlegal is a sequence of a legal
incoming transition to a legal outgoing transition of a (simple) state so that ∃ s ∈ Ssimple :
t ∈ in(s) U t′ ∈ out(s).
Definition 3. A false transition pair FP = (t, t′ ) with t ∈ Tlegal and t ′ ∈ Tfaulty is a sequence of a
legal incoming transition to a faulty outgoing transition of a (simple) state so that ∃ s ∈ Ssimple : t
∈ in(s) U t′ ∈ out(s).
Definition 4. A sequence of n legal transitions (t1, t2..., tn) with ti ∈ Tlegal where (ti, ti+1) denotes
a valid transition pair for all i ∈ 1, ..., n - 1 is called a transition sequence (Tseq) of length n. A
transition sequence (t1, t2..., tn) is complete if it starts at the initial state of the state chart that is
6. 412 Computer Science & Information Technology (CS & IT)
entered firstly and ends at a final state. In this case it is called a complete transition sequence
(Tsqcom).
Definition 5. A fault transition sequence Tsqfault = (t1, t2..., tn) of length n consists of n - 1
subsequent transitions, forming a (legal) transition sequence of the length n - 1 plus a concluding,
faulty transition tn ∈ Tfaulty. A faulty transition sequence is called complete if it starts at the initial
state of the state chart, abbreviated as CFTS. The sequence (t1, t2...,tn-1) is called a start
sequence.
Definition 6. A test case is the triplet [I, S, O], where I is the initial state of the system at which
the test data is input, S is the test data input to the system and O is the expected output of the
system [18], [19]. The output produced by the execution of the software with a particular test case
provides a specification of the actual software behavior. A test case is also characterized by an
ordered pair of an input and an expected output of the SUC.
Definition 7: A test suite is a set of test cases. A single test case in most cases may satisfy more
than one test obligation. For instance, a test case used to cover a certain state of interest may also
cover other states during its execution. This then provides for a way to reduce the size of the final
test suite by choosing a subset of test cases that preserves the coverage obtained by the full test
suite [9]. Based on Definitions 4 and 5 the following two coverage criteria are introduced:
Definition 8: k-transition coverage (k-TC) generates complete transition sequences that
sequentially conduct all legal transition sequences of length k ∈ N.
Definition 9: Faulty transition pair coverage (FTC), generates complete faulty transition sequence
for each faulty transition and faulty transition pair[13].
Definition 8 guarantees that all possible (legal) transition sequences of length k will be tested. A
test suite consisting of all transition sequences of a fixed length k does not necessarily cover a set
of all sequences of length i ∈ 1, ...k-1 as there may exist sequences of length i that cannot be
expanded to length k. Definition 9 guarantees that all potential malfunctions will be tested.
Typically, state based test generation methods focus on some form of coverage, for instance on
covering transitions [19], [20] or on transition coverage and state identification [6], [14]. Our
approach creates all transition sequences of length k including all shorter sequences of length 1,
..., k -1 that cannot be found in longer sequences.
5. GeMiTefSc–OUR PROPOSED APPROACH TO GENERATE AND
MINIMIZE TEST SEQUENCE FROM STATE CHART DIAGRAM
In this section, we discuss a overview of our proposed approach to generate test sequence from
UML state chart diagram and then, we optimize the test node coverage while minimizing time
and cost. We have named our approach, Generation and Minimization of test cases from State
Charts (GeMiTefSc).
Our approach consists of 5 steps. The schematic representation of our approach is shown in fig.2.
• Step 1: Building model of the system.
• Step 2: Constructing the transition graph from state chart diagram.
• Step 3: Extracting the required information from the transition.
7. Computer Science & Information Technology (CS & IT) 413
• Step 4: Generating test cases.
• Step 5: Minimize a set of test cases by calculating node coverage for each test sequence.
In the next section, we discuss each step in detail, by using different algorithms for each step in
different sections. Before that we present some related definitions.
Fig. 2. Schematic representation of our approach
5.1. Building model of the system.
State diagram is graph where nodes represent states end the directed arcs that interconnect states
represent transitions. It also models dynamic behavior, and captures the different states that an
object can be in, and its response to various events that may arise in each of its states. State chart
diagram is one of the 13 UML diagrams used to model dynamic nature of a system. They define
different states of an object during its lifetime. The notation and semantics of UML state
diagrams are substantially based on State charts modified to include object-oriented features [12].
The states and the transition of a system are important to set up a state diagrams from system. Fig.
3 shows a UML state diagram for a ticket machine system.
Figure. 3. State chart diagram for Automated Ticket Machine
8. 414 Computer Science & Information Technology (CS & IT)
5.2. Constructing the transition graph from state chart diagram
Here, we convert the state diagram into state transition graph. A state transition graph
TG = (Vt, Ed).
Definition 10: A transition graph TG = (Vt, Ed) represents a directed graph consisting of a set of
vertices (Vt), a set of directed edges (Ed). In TG, nodes represent states and edges represent
transitions between states. Without any loss of generality, we assume that there is a unique node
that corresponds to the initial state and that one or more nodes represent the final states. The
initial state is represented as the root of the tree. States at each level of nesting are considered as a
sub graph. We represent this step through an algorithm.
Algorithm-1: For constructing transition graph from state chart diagram
Input: SSSSc = (E, SSSSt, H, T)
Output: A transition graph TG = (VVVVt, EEEEd)
1. V := {ti, tj}, A := NULL
2. Foreach t ∈ Tlegal do
3. V := V U {t}
4. Foreach s ∈ Ssimple do
5. Foreach t ∈ in(s) do
6. Foreach t′ ∈ out(s) Tfaulty do
7. A := A U {t,t′ }
8. Endfor
9. Endfor
10. Endfor
11. Foreach t ∈ out(initial(root())) Tfaulty do
12. A := A U {ti,t}
13. Endfor
14. Foreach s ∈ Sf do
15. Foreach t ∈ in(s) do
16. A := A U {t, tj}
17. Endfor
18. Endfor
Finally, the transition graph is used as a source for the graphical traveling salesman problem and
it is augmented by an additional edge (ti, tj). This edge and the preconditions for a state chart
claimed in the last section ensure that the resulting graph is strongly connected.
5.3. Extracting all required information from the graph
Here, in this subsection, we present how to extract all the information which are required to
generate the test sequences.
Input: Transition graph TG = (Vt, Ed)
Output: A set of stages or node ST, set of input data ID, set of output data OD and set of
transition TR.
9. Computer Science & Information Technology (CS & IT) 415
ST = {St1, St2, St3 ....Stn}, each Sti is a stage or node
ID = {ID1, ID2, ID3 ....IDn}, each IDi is an input data
OD = {OD1, OD2, OD3 ....ODn}, each ODi is an output value TR = {TR1, TR2, TR3 ....TRn},
each TRi is a transition between source and destination stage, where each TRi = {Stp, Stq}, Stp is
a source stage and Stq is a destination stage . Algorithm - 1 describes how a transition graph is
constructed for a state chart Sc = (E, St, H, T) : Set V = { t| t ∈ Tlegal} consists of vertices
representing the legal transitions of state chart Sc. For each (legal) transition pair (t, t′ ) of the
state chart, a directed edge is created. Vertex ti has to be connected with all transitions that may
be triggered from the state belonging to the initial configuration. Transitions leading into a final
state have to be connected with vertex tj .
Figure 4. Corresponding transition graph of the state chart diagram of ATM
A simple transition coverage may be reached by visiting all vertices of the graph, based on a
transition graph at least once by starting in vertex ti and ending in vertex tj. The problem of
10. 416 Computer Science & Information Technology (CS & IT)
computing a route for visiting all vertices of a graph by minimizing the length of the route is well
known as the traveling salesman problem (TSP). If visiting vertices and traversing edges more
than once is allowed, it is called the graphical traveling salesman problem (GTSP) [23].A test
case set fulfilling k-transition coverage for k > 1 is computed by transforming the transition graph
stepwise and then applying the graphical traveling salesman problem. Also by computing all
complete transition sequences whose length is smaller than k and that cannot be expanded to
longer sequences, a minimal test case set fulfilling k-transition coverage for all k ∈ 1, ..., n is
achieved. This proceeding is described in Algorithm-2, in the next section.
5.4. Generating test cases
After, a transition graph is constructed based on a state chart Sc. If n = l, the graphical traveling
salesman problem can be applied directly. If n is greater than 1 the transition graph has to be
transformed k - 1 times. The resulting graph represents all possible sequences of transitions of
length k. Additionally, all sequences of length k-1 are computed that cannot be expanded to
longer sequences. These sequences are characterized by the fact that the corresponding vertex
representing that sequence is solely connected with vertices ti and tj. The functions indeg(v) :=
v′,(v′, v) ∈ A and outdeg(v) := v′(v, v′) ∈ A are used to compute these vertices. As these sequences
are already complete, they can be added to the set TS.
Algorithm-2: Generation of a test case set for k-transition coverage for k ∈ 1, ..., n
Input: A state transition graph from SSSSc = = (E,SSSSt,H, T), n ∈∈∈∈ N
Output: A test case set TS fulfilling k-transition coverage
1. For k ∈ 1, ..., n
2. Begin
3. i := 0; j := 1; ts := null; s := null; visited NSt := 0
4. Do while NSt [i] = NULL
5. push ( NSt [i], s);
6. visited NSt [ NSt [i] ] := visited NSt [ NSt [i] ] + 1;
7. Do while s not = NULL
8. t := pop(s); NSt[i] := pop(s);
9. If enabled ( NSt[i]) not = NULL
10. visitnexttransition( NSt [i] );
11. Endif
12. Enddo
13. Create a transition graph TG = (Vt, Ed) from Sc by applying Algorithm-1
14. TS := ϕ
15. For k := 2 to n do
16. Foreach v ∈ V do
17. If (ti, v) ∈ Ed ∧ (v, tj ) ∈ Ed ∧ indeg(v) = outdeg(v) = 1 then
18. TS := TS U v
19. Ed := Ed U (ti, tj )
20. Apply the graphical traveling salesman problem.
21. Add them to set TS
22. Endif
23. Endfor
24. Enddo
25. Enddo
26. End
27. Endfor
11. Computer Science & Information Technology (CS & IT) 417
5.5. Minimizing the test cases
Here, in this section , we discuss how the generated test cases are reduced while maximizing test
coverage. Though Wang’s algorithm [17] is widely used, but it does not cover other critical
attributes, like defect id, dependency and automated test case indicator. In order to generate an
effective size of generated test cases. This step contains two subactivities, which are
• calculate node coverage for each test case. Let NC(tc) = t1, t2,...tn for NC(tc) to be a set of
test cases that tc is covered by t1, t2,...tn. Hence, if a number of set tc is zero, then tc is
included in the effective set of test cases.
• select effective test cases. Now, we present this step through an algorithm.
Algorithm-3
Input: Sc = (E, St, H, T), Transition graph and A set of test cases TS[n];
Output: Reduced test suite RTs;
1.ANC, PNC: Node coverage, Previous coverage, tc: test case
2.RTs = ϕ;
3.NC(tc) = t1, t2,...tn
4.ANC = 0;
5.repeat
6.select a test case F from TS[n];
7. Foreach s ∈ Ssimple do
8. Foreach t ∈ in(s) do
9. Foreach t′ ∈ out(s) ∩Tfaulty do
10. ANC := ANC U (t, t′)
11. Foreach (t, t′) ∈ ANC do
12. (t1, ..., ti) := STARTSEQUENCE(t)
13. RTs := RTs U (t1, ...ti, t, t′ )
14. If in(inital(root())) = ϕ then
15. RTs := RTs U (t)
16. select effective test cases;
17. If a number of set tc is zero;
18. then tc is included in the effective set of test cases;
19. Endif
20. Endif
21. Endfor
22. Endfor
23. Endfor
24. Endfor
The resulting graph TGout = (V tout, Edout ) contains a vertex v = (t1, ..., tk) for each transition
sequence of length k. Two vertices v = (t1, ..., tk) and v′ = (t′1, ..., t′k) are connected by a directed
edge if it holds that (t2, ..., tk) equals (t′1, ..., t′k-1) for each component. These two vertices thus
represent the sequence (t1, ..., tk, t′k).
12. 418 Computer Science & Information Technology (CS & IT)
6. WORKING OF OUR ALGORITHM
In this section, we explain the working of our algorithm using an automatic ticket machine
example as described below.
The ATM(Automatic Ticket machine)issues tickets to passengers on receiving money from them.
The state chart diagram of an automatic ticket machine, ATM object for various events of interest
are shown in Fig 3. The object enters into idle state, when the power switch is on. Once the user
selects an ticket type button in the menu, the object enters the display destination state, where the
ticket fare to different destinations are displayed. The user can select the destination, ticket type
and the number of persons(n) to travel. The condition n≤6 is inserted for the event
tickettypeselected, as the ticket machine is not expected to issue a ticket for more than 6 persons
in one transaction. Once the ticket type and number of persons required are selected, the object
enters the display money state. In this state, the object displays the amount of money (totalfair)
the user has to enter into the ticket machine. Note that totalfair = ticket fare × number of persons.
As the user enters money (amt) into the machine, the machine object changes its state to busy. In
the busy state, it calculates how much balance or change (chng) has to be returned to the user if
any, where chng = (amt - totalfair). If the change balance is less than zero, the machine object
changes its state from busy to return money as the money inserted is insufficient. If the change
balance is more than or equal to zero, the machine object goes to issueticket state and issues the
ticket for requested number of persons. If the balance is zero, then once the ticket is issued the
machine object changes its state from issueticket to idle. If the balance (chng) is more than zero,
the machine object enters into the return money state, where the change balance money is
returned. Once the money is returned, the machine object again enters into idle state. Here the
state chart diagram of the machine is given in the figure 3.
After constructing state chart diagram, we construct transition graph using algorithm-1. The
transition graph is shown in figure 4. In next step, we extract all required information from the
state transition graph as described below.
ST = {St1, St2, St3, St4, St5, St6, St7}, each Sti is a stage or node
ID = {ID1,ID2,ID3,ID4,ID5,ID6,ID7,OD8,OD9}, each IDi is an input data
OD = {OD1, OD2, OD3, OD4, OD5, OD6, OD7, OD8, OD9}, each ODi is an output value
TR = {TR1,TR2,TR3,TR4,TR5,TR6,TR7}, each TRi is a transition between source and
destination stage, where each TRi = {Stp, Stq}, Stp is a source stage and Stq is a destination
stage. Hence, each transition can be extracted as follows:
TR1 = {St1, St2}
TR2 = {St2, St3}
TR3 = {St3, St4}
TR4 = {St4, St5}
TR5 = {St5, St6}
TR6 = {St5, St7}
TR7 = {St7, St6}
14. 420 Computer Science & Information Technology (CS & IT)
tc25 = {St5, St7, St6, ID6, ID7, OD6, OD7, TR6, TR7}
tc26 = {St7, St6, ID7, OD7,TR7}
The last step is to minimize the set of test cases by calculating node coverage for each test case
and determine which test cases are covered by other test cases.
NC(tc1) = {tc2, tc3, tc4, tc5, tc6, tc7}
NC(tc2) = {tc3, tc4, tc5, tc6, tc7}
NC(tc3) = {tc4, tc5, tc6, tc7}
NC(tc4) = {tc5, tc6, tc7}
NC(tc5) = { }
NC(tc6) = {tc7}
NC(tc7) = { }
NC(tc8) = {tc9, tc10, tc11, tc12, tc13}
NC(tc9) = {tc10, tc11, tc12, tc13}
NC(tc10) = {tc11, tc12, tc13}
NC(tc11) = {tc13}
NC(tc12) = {tc13}
NC(tc13) = { }
NC(tc14) = {tc15, tc16, tc17, tc18}
NC(tc15) = {tc16, tc17, tc18}
NC(tc16) = {tc18}
NC(tc17) = {tc18}
NC(tc18) = { }
NC(tc19) = {tc20, tc21, tc22}
NC(tc20) = {tc22}
NC(tc21) = {tc22}
NC(tc22) = { }
NC(tc23) = {tc25}
NC(tc24) = {tc25}
15. Computer Science & Information Technology (CS & IT) 421
NC(tc25) = { }
NC(tc26) = {tc25, tc22, tc18, tc13, tc7}
Therefore, the following test cases like tc1, tc2, tc3, tc4, tc6, tc8, tc9, tc10, tc11, tc12, tc14, tc15,
tc16, tc17, tc19, tc20, tc21, tc23, tc24, tc26 should be ignored. Hence, the remaining effective set
of test cases is TS = {tc5, tc7, tc13, tc18, tc22, tc25}.
6.1. Reduction
In practical situations, there is often insufficient time for thorough testing activities within
industrial projects. Hence, it is reasonable to try to reduce the size of generated test suites.
However, the effect of the reduction on the fault-detection ability of the test suites should be
small. The techniques proposed in this paper can be used to apply reduction during test case
generation. A single test case may cover more than the coverage item it has been generated for.
When using a probe based technique as described in this paper it is easy to identify all items
covered by a particular test case.
7. RELATED WORK
A lot of studies have investigated the effect of test-set reduction on the size and fault finding
capability of a test set.
In an early study, Wong et al. [27 ]address the question of the effect on fault detection of reducing
the size of a test set while holding coverage constant [27], [28]. They randomly generated a large
collection of test sets that achieved block and all-uses data flow coverage for each subject
program. For each test set they created a minimal subset that preserved the coverage of the
original set. They then compared the fault finding capability of the reduced test-set to that of the
original set. Their data shows that test minimization keeping coverage constant results in little or
no reduction in its fault detection effectiveness. This observation leads to the conclusion that test
cases that do not contribute to additional coverage are likely to be ineffective in detecting
additional faults.
To confirm or refute the results in the Wong study, Rothermel et al. [24] performed a similar
experiment using seven sets of C programs with manually seeded faults [24]. For their experiment
they used edge-coverage [7] adequate test suites containing redundant tests and compared the
fault finding of the reduced sets to the full test sets. In this experiment, they found that [2] the
fault-finding capability was significantly compromised when the test-sets were reduced and [25]
there was little correlation between test-set size and fault finding capability. The results of the
Rothermel [24] study were also observed by Jones and Harrold in a similar experiment [10].
Offutt and Abdurazik [19], [20] developed a technique for generating test cases from UML state
diagrams. They have highlighted several useful test coverage criteria for UML state charts such
as: (1) full predicate coverage, (2) transition coverage etc.
Kansomkeat and Rivepiboon [11] have introduced a method for generating test sequences using
UML state chart diagrams. They transformed the state chart diagram into a flattened structure of
states called testing flow graph (TFG). From the TFG, they listed possible event sequences which
they considered as test sequences. The testing criterion they used to guide the generation of test
sequences is the coverage of the states and transitions of TFG.
Kim et al. [12] proposed a method for generating test cases for class testing using UML state
chart diagrams. They transformed state charts to extended FSMs (EFSMs) to derive test cases. In
16. 422 Computer Science & Information Technology (CS & IT)
the resulting EFSMs, the hierarchical and concurrent structure of states are flattened and
broadcast communications are eliminated. Then data flow is identified by transforming the
EFSMs into flow graphs, to which conventional data flow analysis techniques are applied. These
different results are difficult to reconcile and the relationship between coverage criteria, test-suite
size, and fault finding capability clearly needs more study. In the experiment discussed in this
paper we attempt to highlight some additional issue. Our work is different in some respects. First,
we are not studying testing of traditional programs, we are interested in test-case generation, test
case minimization by calculating node coverage for each test case and testing of specifications. A
single test-case in most cases may satisfy more than one test obligation. For instance, a test case
used to cover a certain state of interest may also cover other states during its execution. It
provides a way to reduce the size of the final test-suite by choosing a subset of test-cases that
preserves the coverage obtained by the full test-suite.
8. CONCLUSION AND FUTURE WORK
In this paper, first, we build a state chart model of our system under test. Next, we derived state
transition graph from state chart diagram. Then, all required information are extracted from the
graph. Then, the test cases are generated by applying Wang’s algorithm. Lastly, a set of test cases
are minimized by calculating node coverage for each test case and it is determined that which test
case are covered by other test cases. In this way, this paper introduces efficient test generation
technique to optimize test coverage by minimizing time and cost.
This paper presents a coverage and specification-oriented test approach based on state chart
diagram. In our opinion, there is an unacceptable loss in terms of test-suite quality. Thus, we
advocate research into test-case prioritization techniques and experimental studies to determine if
such techniques can more reliably lessen the burden of the testing effort by running a subset of an
ordered test suite as opposed to a reduced test suite, without loss in fault finding capability.
Further research is planned to extend the model for considering time constraints to handle more
intricate applications.
REFERENCES
[1] OMG. Unified Modeling Language specification, version 2.0, August 2005, object management
group, www.omg.org.
[2] M. Archer, C. Heitmeyer, and S. Sims, 1998. TAME: A PVS interface to simplify proofs for automata
models, In User Interfaces for Theorem Provers.
[3] Fevzi Belli and Axel Hollmann, March 2008. Test generation and minimization with basic
statecharts. ACM, SAC-08, pages 718 – 723.
[4] Michel R. Blaha and James R. Rumbaugh. Object-Oriented Modeling and Design with UML. Pearson,
second edition.
[5] M. Broy, June 2005. Model-based testing of reactive systems. Advanced Lectures , Springer..
[6] T. S. Chow, 1978. Testing software design modeled by finite-state machines. IEEE TSE, 4(3): , pages
178 – 187.
[7] P. Frankl and S. N. Weiss, 1991. An experimental comparison of the effectiveness of the all-uses and
all-edges adequacy criteria. In Proceedings of the symposium on Testing, analysis, and verification.
[8] D. Harel, 1987.. Statecharts: A visual formulation for complex systems. Sci. Comp. Prog., 8: , pages
231 – 274
[9] Mats P. E. Heimdahl and Devaraj George. Test-suite reduction for model based tests: Effects on test
quality and implications for testing.
17. Computer Science & Information Technology (CS & IT) 423
[10] J. A. Jones and M. J. Harrold, March 2003. Test-suite reduction and prioritization for modified
condition/decision coverage. IEEE Transactions on Software Emgineering, 29(3): , pages 195 – 209.
[11] S. Kansomkeat and W. Rivepiboon, 2003. Automated-generating test case using UML statechart
diagrams. In Proc. SAICSIT 2003, ACM, pages 296 – 300.
[12] Y. G. Kim, H. S. Hong, D. H. Bae, and S. D. Cha et a, 1999l. Test cases generation from UML state
diagram, Software Testing Verification and Reliability, , pages 187 – 192.
[13] Nicha Kosindrecha and Jirapun Daengdej, 2005 – 2010. A test generation method based on state
diagram. journal of Theoritical and Applied Information Technology, pages 28 – 44.
[14] R. Lai, 2002. A survey of communication protocol testing. Journal of Systems and Software, 62(1): ,
pages 21 – 46.
[15] J. T. Lallchandani and R. Mall, 2010. Integrated state-based dynamic slicing technique for UML
models. In IET Software, Vol. 4, Iss. 1, pages 55 –78.
[16] H. Li and L. C. Peng, January 2005. Software test data generation using ant colony optimization. In
Proceedings of World Academy of Science, Engineeing and Technology.
[17] Wang Linzhang, Yuan Jiesong, Yu Xiaofeng, Hu Ju, Li Xuandong, and Zheng Guoliang, 2004.
Generating test cases from UML activity diagram based on gray-box method. Proceedings of the 11th
Asia-Pacific Software Engineering Conference (APSEC04).
[18] R. Mall, 2009. Fundamentals of Software Engineering. Prentice Hall, 3rd
edition.
[19] J. Offutt and A. Abdurazik, 1999. Generating tests from uml specifications. In Proceedings of 2nd
International Conference. UML, Lecture Notes in Computer Science, pages 416 – 429.
[20] J. Offutt, S. Liu, A. Abdurazik, and P. Ammann et al. , 2003 Generating test data from state-based
specifications. Software Testing Verification Reliability., 13: , pages 25 – 53.
[21] D. Pilone and N. Pitman, 2005. UML 2.0 in a Nutshell. NY. O’Reilly, USA.
[22] M. Priestley. Practical Object-Oriented Design with UML. Tata McGraw-Hill, second edition.
[23] G. Reinelt, 1994. In the traveling salesman: Computational solutions for tsp applications. Springer
Berlin / Heidelberg, 840.
[24] G. Rothermel, M. Harrold, J. Ostrin, and C. Hong, November 1998. An empirical study of the effects
of minimization on the fault detection capabilities of test suites. In Proceedings of the International
Conference on Software Maintenance, pages 34 – 43.
[25] C. Parent-Vigouroux S. Bensalem, P. Caspi and C. Dumas, 1999. A methodology for proving control
systems with lustre and pvs. In In Proceedings of the Seventh Working Conference on Dependable
Computing for Critical Applications (DCCA 7).
[26] M. Sharma and R. Mall, 2009. Automatic generation of test specifications for coverage of system
state transitions. Information and Software Technology, (51): , pages 418 – 432.
[27] W. Wong, J. Horgan, S. London, and A. Mathur, April 1998. Effect of test set minimization on fault
detection effectiveness. Software Practice and Experience, 28(4): , pages 347 – 369.
[28] W. Wong, J. Horgan, A. Mathur, and A. Pasquini, August 1997. Test set size minimization and fault
detection effectiveness: A case study in a space application. In Proceedings of the 21st Annual
International Computer Software and Applications Conference, pages 522 – 528.
18. 424 Computer Science & Information Technology (CS & IT)
Authors
.
Prafulla Ku. Behera has received his Ph.D
degree from Utkal University, Vani vihar,
Bhubaneswar, India. He is currently working as a
reader at Dept. of Computer Science &
Application, in Utkal University, Vani vihar,
Bhubaneswar, India. His special fields of interest
include Mobile Computing, Software
Engineering, He is a member of CSI.
Durga Prasad Mohapatra received his Ph. D.
from Indian Institute of Technology Kharagpur
and M. E. from Regional Engineering College
(now NIT), Rourkela. He joined the faculty of
the Department of Computer Science and
Engineering at the National Institute of
Technology, Rourkela in 1996, where he is now
Associate Professor. His research interests
include software engineering, real-time systems,
discrete mathematics and distributed computing
and published more than forty papers in these
fields. He has received many awards including
Young Scientist Award for the year 2006 by
Orissa Bigyan Academy, Prof. K. Arumugam
award for innovative research for the year 2009
and Maharasthra State National Award for
outstanding research for the year 2010 by ISTE,
NewDelhi. He has also received three research
projects from DST and UGC. Currently, he is a
member of IEEE. Dr. Mohapatra has co-authored
the book Elements of Discrete Mathematics: A
computer Oriented Approach published by Tata
Mc-Graw Hill.
Ranjita Ku. Swain completed her MCA from
College of Engg.And Technology, OUAT,
Bhubaneswar, India. She is pursuing her Ph.D
degree from Utkal University, Vani vihar,
Bhubaneswar, India. She is currently working as
Senior Lecturer in Computer Science Dept.,
Rourkela Institute of Management Studies,
Rourkela, India. She has 11years of teaching
experience and her fields of interest are Software
Engg., Discrete, Mathematical Structure and
Numerical Methods..