Spelling suggestions: "subject:"collaboration diagrams"" "subject:"acollaboration diagrams""
1 |
Using Collaboration Diagrams In Component Oriented ModelingTuncel, Mehmet Burhan 01 January 2006 (has links) (PDF)
Component Oriented Software Engineering (COSE) seems to be the future of software engineering. Currently, COSEML is the only modeling language that completely supports the COSE approach. Abstract decomposition of the system and their representing components are shown in a hierarchy diagram to support the COSE process model. In COSEML, only static modeling is supported through this single diagram. However, software is about behavior and static modeling is not sufficient to describe the system. The aim of this thesis is providing the benefits of dynamic modeling to COSEML by adopting collaboration diagrams. For this purpose, first, specification of modified collaboration diagrams is made for COSEML. Then software is developed for supporting collaboration diagrams in COSECASE. Also, an e-store application is modeled with COSEML using the collaboration diagrams. With this work, modeling the dynamic behavior of the system in both abstract and component levels is made possible. Furthermore, use case realization is enabled in the COSE modeling. More important, modeling the sequential interactions among components is made possible. Consequently, a suitable environment is provided for automated testing and application generation from the model.
|
2 |
An investigation into the use of ORM as a conceptual modelling technique with the UML domain model class diagram as benchmarkJohn, Manju Mereen 02 1900 (has links)
This study investigated the use of ORM as a conceptual modelling technique by using the UML domain model class diagram as benchmark. The rationale was that if the ORM-class diagram compared favourably with the benchmark, then ORM could be proposed as an alternate conceptual modelling technique. Proponents of ORM suggest that it has significant advantages over other techniques for conceptual modelling.
The benchmark UML class diagram was developed according to the Unified Process through use-cases and collaboration diagrams. The ORM-class diagram was derived using the Conceptual Schema Design Process and ORM-UML Mapping Process. The evaluation of the two class diagrams was conducted by means of a questionnaire, based on a set of principles for conceptual models. The study concluded that ORM could not be proposed as a conceptual modelling technique
up to the UML domain class diagram level without considering additional
techniques for capturing the dynamics of the system. / Computer Science / M.Sc. (Computer Science)
|
3 |
An investigation into the use of ORM as a conceptual modelling technique with the UML domain model class diagram as benchmarkJohn, Manju Mereen 02 1900 (has links)
This study investigated the use of ORM as a conceptual modelling technique by using the UML domain model class diagram as benchmark. The rationale was that if the ORM-class diagram compared favourably with the benchmark, then ORM could be proposed as an alternate conceptual modelling technique. Proponents of ORM suggest that it has significant advantages over other techniques for conceptual modelling.
The benchmark UML class diagram was developed according to the Unified Process through use-cases and collaboration diagrams. The ORM-class diagram was derived using the Conceptual Schema Design Process and ORM-UML Mapping Process. The evaluation of the two class diagrams was conducted by means of a questionnaire, based on a set of principles for conceptual models. The study concluded that ORM could not be proposed as a conceptual modelling technique
up to the UML domain class diagram level without considering additional
techniques for capturing the dynamics of the system. / Computer Science / M.Sc. (Computer Science)
|
Page generated in 0.0858 seconds