Entity-relationship and object-oriented data modeling — An experimental comparison of design quality

Shoval, Peretz; Shiran, Sagit

doi:10.1016/s0169-023x(97)88935-5

“…It was felt that many mana gers did not want to leave what was described as a comfort zone, particularly in view of the empirical studies indicate that Entity Relationship (ER) schemas are often more correct and easier to develop than corresponding OO schemas. (Shoval & Shiran, 1997;Haplin & Bloesch, 1999). It was also suggested that a spill over from this comfort zone was that many of the technical leaders in the organizations have not kept up-to-date in the new methodologies and were therefore not co mfortable with introducing them or using them in their organizations.…”

Section: Resultsmentioning

confidence: 99%

“…"Some empirical studies indicate that Entity Relationship (ER) schemas are often more correct and easier to develop than corresponding OO schemas." (Shoval & Shiran, 1997;Haplin & Bloesch, 1999) and "UML's object-oriented approach facilitates the transition to object-oriented code. As shown later however, UML can make it awkward to capture and validate data concepts and business rules with domain experts, and cater for structural changes in the application.…”

Section: Introductionmentioning

confidence: 99%

The Acceptance of Object-Oriented Development Methodologies in Australian Organizations and the Place of UML in Information Systems Programs

Hodgett

¹

2003

InSITE Conference

0

View full text Add to dashboard Cite

It is claimed that the Unified Modeling Language (UML) is emerging as the accepted standard graphical language for specifying, constructing, visualizing and documenting the object oriented information systems development process. As such it has gained a place in many information systems programs. An investigation of Australian organizations indicates that the use of object oriented development methodologies and UML is gradually increasing in Australia but is still to see general acceptance. This raises the question of the priority that should be accorded to the inclusion of UML in competition with other topics and issues in information systems education programs.

show abstract

“…Our work yields important insights into the difficulties that engineers face when trying to understand the implications that previous security incident reports have for their own organisations. There have been numerous empirical studies to evaluate the usability of graphical notations, including Entity-Relationship diagrams [44], UML [45,46] etc. However, as far as we are aware, there have been no previous studies to assess the strengths and weaknesses of graphical notations to help transfer the lessons learned from previous security incidents.…”

Section: Discussionmentioning

confidence: 99%

Improving the exchange of lessons learned in security incident reports: case studies in the privacy of electronic patient records

He

¹

,

Johnson

²

,

Yu

³

2015

J Trust Manag

2

0

View full text Add to dashboard Cite

The increasing use of Electronic Health Records has been mirrored by a similar rise in the number of security incidents where confidential information has inadvertently been disclosed to third parties. These problems have been compounded by an apparent inability to learn from previous violations; similar security incidents have been observed across Europe, North America and Asia. This has resulted in the loss of confidence and trust of the public towards the organisations' ability to protect the patients' private information. The Generic Security Template (G.S.T.) has been proposed to communicate security lessons learned from previous security incidents. This paper conducts a series of empirical studies to evaluate the usability of the G.S.T. The first study compares the G.S.T. with the conventional text-based security incident reports. The two methods were compared in term of the users' ability to identify a number of lessons learned from investigations into previous incidents involving the disclosure of healthcare records. The study showed that the graphical approach resulted in higher accuracy in terms of number of correct answers generated by participants. However, subjective feedback raised further questions about the usability of the G.S.T. as the readers of security incident reports try to interpret the lessons that can increase the security of patient data. The second study further evaluates the usability of the G.S.T. using the Cognitive Dimensions and identifies some aspects that need to be improved.

show abstract

“…There have been numerous empirical studies to evaluate the usability of graphical notations, including Entity-Relationship diagrams [44], UML [45,46] etc. However, as far as we are aware, there have been no previous studies to assess the strengths and weaknesses of graphical notations to help transfer the lessons learned from previous security incidents.…”

Section: Discussionmentioning

confidence: 99%

Improving the Exchange of Lessons Learned in Security Incident Reports: Case Studies in the Privacy of Electronic Patient Records

He

¹

,

Johnson

²

,

Lyu

³

et al. 2014

IFIP Advances in Information and Communication Technology

View full text Add to dashboard Cite

The increasing use of Electronic Health Records has been mirrored by a similar rise in the number of security incidents where confidential information has inadvertently been disclosed to third parties. These problems have been compounded by an apparent inability to learn from previous violations; similar security incidents have been observed across Europe, North America and Asia. This has resulted in the loss of confidence and trust of the public towards the organisations' ability to protect the patients' private information. The Generic Security Template (G.S.T.) has been proposed to communicate security lessons learned from previous security incidents. This paper conducts a series of empirical studies to evaluate the usability of the G.S.T. The first study compares the G.S.T. with the conventional text-based security incident reports. The two methods were compared in term of the users' ability to identify a number of lessons learned from investigations into previous incidents involving the disclosure of healthcare records. The study showed that the graphical approach resulted in higher accuracy in terms of number of correct answers generated by participants. However, subjective feedback raised further questions about the usability of the G.S.T. as the readers of security incident reports try to interpret the lessons that can increase the security of patient data. The second study further evaluates the usability of the G.S.T. using the Cognitive Dimensions and identifies some aspects that need to be improved.

show abstract

Entity-relationship and object-oriented data modeling — An experimental comparison of design quality

Cited by 82 publications

References 10 publications

The Acceptance of Object-Oriented Development Methodologies in Australian Organizations and the Place of UML in Information Systems Programs

The Acceptance of Object-Oriented Development Methodologies in Australian Organizations and the Place of UML in Information Systems Programs

Improving the exchange of lessons learned in security incident reports: case studies in the privacy of electronic patient records

Improving the Exchange of Lessons Learned in Security Incident Reports: Case Studies in the Privacy of Electronic Patient Records

Contact Info

Product

Resources

About