Cross Checking Rules to Improve Consistency between UML Static Diagram and Dynamic Diagram

Ha, Il-Kyu; Kang, Byunguk

doi:10.1007/978-3-540-88906-9_55

Cited by 6 publications

(6 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Ha and Kang proposed several verification rules to check for consistency between UML static and dynamic diagrams, such as class diagram, component diagram, state-chart diagram, sequence diagram, activity diagram, use case diagram, deployment diagram, collaboration diagram and object diagram [54]. A relation graph is used to show the relationship between diagrams.…”

Section: Heuristic Analysis: -mentioning

confidence: 99%

A Review on Software Requirements Validation and Consistency Management

Kamalrudin¹,

Sidek²

2015

IJSEIA

View full text Add to dashboard Cite

Requirements need to be validated at the early phase of the software development to avoid errors such as inconsistency, incompleteness and incorrectness. Drawn from this argument, a requirements validation process needs to consider Consistency, Completeness and Correctness ("3 Cs") for the production of a quality software specifications. This paper provides a review of requirements validation and consistency management based on the existing literature in order to identify the gaps in the existing knowledge on the process of software requirements specifications. This paper begins with a review of the definitions of the 3Cs,upon which the understanding of the 3Cs is derived. Next comprehensive review of related works on the identified consistency management techniques: traceability and analysis approaches are then presented. This is supported with a heat map representations of the related research on the types of contributions, techniques, specifications and semantics used in consistency management. Since semiformal specifications were found as the most common representation of the requirements, the types of models used as semi-formal specifications to represent the requirements were also discussed. Overall, this paper identifies the various gaps existing within the process of validating and managing the consistency of requirements to avoid re-inventing the wheels in the diverse and comprehensive knowledge of requirements engineering.

show abstract

Section: Heuristic Analysis: -mentioning

confidence: 99%

A Review on Software Requirements Validation and Consistency Management

Kamalrudin¹,

Sidek²

2015

IJSEIA

View full text Add to dashboard Cite

show abstract

“…As shown in [9], there are several methods to verify consistency in UML diagrams: meta-model-based method [10], graph-based method [11], scenario-based method, constraint-based methods and knowledge-based methods [12]. We are focusing here on constraint-based methods and on graph-based methods.…”

Section: Related Workmentioning

confidence: 99%

The Sufficient Criteria For Consistent Modelling Of The Use Case Realization Diagrams With A New Functional-Structure- Behaviour UML Diagram

Niepostyn¹

2015

ELECTROTECHNICAL REVIEW

View full text Add to dashboard Cite

UML activity diagrams are primarily used to visualise scenarios. The verification of activity diagrams consistency is subsequently needed to identify errors in requirements at the early stage of the development process. The consistency verification is difficult due to a semi-formal nature of activity diagrams. We propose to extend the activity diagram to the new Functional-Structure-Behaviour (FSB) UML diagram to enable automatic verification of consistency of scenarios of the visualized use cases. Moreover the FSB UML diagram enables simultaneous modelling of the functionality, of the structure and of the behaviour of the target system model. Thus the proposed Functional-Structure-Behaviour UML activity diagram enables consistent and complete models to be developed from scenarios. Furthermore the FSB UML activity diagram can be used for automatic generation of complete workflow applications without any manual programming. Streszczenie. Diagramy aktywności UML używane są przede wszystkim do wizualizacji scenariuszy. W celu wyeliminowania błędów w przyszłym systemie niezbędny okazuje się proces weryfikacji tych diagramów UML. Weryfikacja spójności jest jednakże dość złożonym zagadnieniem, gdyż diagramy aktywności nie są formalnym sposobem zapisu wymagań. Proponujemy rozszerzenie diagramów aktywności UML do diagramów nazwanych przez nas diagramami Funkcjonalność-Struktura-Behawioryzm (FSB) UML które umożliwiają automatyzację weryfikacji spójności scenariuszy wizualizowanych przypadków użycia. Co więcej diagram FSB UML umożliwia równoczesne modelowanie funkcjonalności, struktury i zachowania docelowego modelu systemu. Dlatego też zaproponowany diagram aktywności FSB UML umożliwia również opracowywanie kolejnych spójnych i kompletnych modeli na jego podstawie. Ponadto diagram aktywności FSB UML może być wykorzystany do automatyzacji generowania aplikacji typu workflow bez potrzeby ręcznego programowania. Warunki wystarczające do spójnego modelowania diagramów realizacji przypadku użycia z wykorzystaniem ulepszonego diagramu aktywności FSB UML.

show abstract

“…Ha and Kang (Ha and Kang, 2008) have discussed the idea to create cross checking to improve consistency between UML static diagram and dynamic diagram. They had proposed base on meta-models for both diagrams.…”

Section: Related Workmentioning

confidence: 99%

“…Secondly they describes how to derived consistency checking from meta-models and finally, the derive rules will be evaluated through a case study. Ha and Kang (Ha and Kang, 2008) discussed the rules that are specified formally with Object Constraint Language (OCL).…”

Section: Related Workmentioning

confidence: 99%

“…In the previous works, we found that many researchers work on data integrity or quality in UML diagram especially in designing system (Hadj Ali, Boufares, and Abdellatif, 2006;Alsaadi, 2006;Ha and Kang, 2008;Zhu, Shanker, and Cai, 2007;Boufares and Bennaceur, 2003). A few of them discussed the idea of extracting manually schema table from class diagram using OCL (Hadj Ali, Boufares, and Abdellatif, 2006;He, Ying, and Zhang, 2002).…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

A Proposal for Constructing Relational Database from Class Diagram

Saringat¹,

Herawan²,

Ibrahim³

2010

CIS

View full text Add to dashboard Cite

Database system is important to ensure the data can be stored, updated and retrieved for future use. Data modelling using the Entity Relationship Model has been introduced more than thirty years. However, designing a good database system is still an attractive issue particularly in system analysis and design because of very hard to do consistency checking between system design and database design. In this paper, a proposal for designing a relational database system based on Object Oriented Analysis and Design is presented. The database system is created by the schema table that extract from class diagram. The rules applying in this paper is following the object oriented concept. It is based on the relationships among the classes, multiplicity, attributes name, class name, data type and the behaviours of the classes. Beside that the user is required to insert record to accomplish a good designing the schema tables to avoid redundancy data. Finally, an automatic editor called CDGeST is proposed in order to automate the process.

show abstract

Cross Checking Rules to Improve Consistency between UML Static Diagram and Dynamic Diagram

Cited by 6 publications

References 1 publication

A Review on Software Requirements Validation and Consistency Management

A Review on Software Requirements Validation and Consistency Management

The Sufficient Criteria For Consistent Modelling Of The Use Case Realization Diagrams With A New Functional-Structure- Behaviour UML Diagram

A Proposal for Constructing Relational Database from Class Diagram

Contact Info

Product

Resources

About