8/12/2019 Concern-Oriented and Ontology-based Design Approach of Software Architectures
1/10
SYNASC 2008: 10th International Symposium on Symbolic and Numeric
Algorithms for Scienti fic Comput ing, Timisoara, Romania
Concern-Oriented and Ontology-based Design
Approach of Software Architectures
8/12/2019 Concern-Oriented and Ontology-based Design Approach of Software Architectures
2/10
Separation of Concerns
Concerns AnalysisOntologies
Our Software Design Approach of
Software Architecture
Application the Design Approach
CONTENTS
8/12/2019 Concern-Oriented and Ontology-based Design Approach of Software Architectures
3/10
Separation of ConcernsA c o n c e r n in information system engineering is a care related to a problem fromthe real world of one or more stakeholders involved in the construction or evolutionof an information system in its natural environment. The care of a stakeholder
depends on his/her interest or preoccupation on which he/she has related to aproblem from the real world. The interest of a stakeholder derives frequently from aneed, but can also originate in a desire, another interest or his/her responsibility inthe information system evolution process.
Separation of Concerns
Concerns Analysis
Ontologies
Our Software Design Approach of Software Architecture
Application of the Design Approach
C4
Name: Care to find how the clinical manifestation of the disease is related to the objectivesattainment and the selection criteria identification
Prob.
Hypothesis: The following information is available: trial objectives, trial design,
statistical considerations and previous CT projects and their scientific results.
Conclusion: How will the disease in the stage treated in the study is tested in order toget the diagnostic? What basic characteristics (gender, life expectancy, performancestatus) does the study population affected by the disease have? How the clinicalmanifestation of the disease might affect the safety of the subjects and the attainmentof the objectives? What particularities of the disease are important for the identificationof the selection criteria? How the pathogenesis of the disease might affect the generalclinical state of the subjects and the inferring of the selection criteria?
Stakeholder: Writing committee
8/12/2019 Concern-Oriented and Ontology-based Design Approach of Software Architectures
4/10
Separation of Concerns
Concerns Analysis
Ontologies
Our Software Design Approach of Software Architecture
Application of the Design Approach
Concerns AnalysisCode Mental representation description in natural language
K1 The persons who have the disease in the stage considered by the study areeligible.
B8 The clinical manifestation of the disease is related to the attainment of theobjectives and the selection criteria identification
B9 The disease in its stage has a diagnostic as it resulted from the tests
B10 The existence of the disease and its stage might affect the life expectancy of aperson
B11 The life expectancy is a characteristic of study population
B12 The study population has other basic characteristics: age, gender, race and
performance statusB13 The existence of the disease and its stage might affect the performance status
of a personB14 The clinical manifestation of the disease might have some particularities that
are important to identify the selection criteria.K15 Any disease has a pathogenesis.
B16 The pathogenesis of the disease might affect the general clinical state of thesubjects and the inference of the selection criteria.
8/12/2019 Concern-Oriented and Ontology-based Design Approach of Software Architectures
5/10
OntologiesTypes of ontologies:
top-level: DOLCE, SUMO,
BFO, CYC, GFO
domain: medicine, history,engineering
task
application
Languages: First Order
Logic, OWL
Tools: Protg,
SemanticWorks, RacerPro
Separation of Concerns
Concerns Analysis
Ontologies
Our Software Design Approach of Software Architecture
Application of the Design Approach
8/12/2019 Concern-Oriented and Ontology-based Design Approach of Software Architectures
6/10
Our Software Design Approach ofSoftware Architecture
1. Architectural module construction for each concern
2. For each concern introducing a controller object
3. Stating the model classes
4. Each object of a model class is a wrapper of an individual
of the mapped concept
Separation of Concerns
Concerns Analysis
Ontologies
Our Software Design Approach of Software Architecture
Application of the Design Approach
Design Rules
8/12/2019 Concern-Oriented and Ontology-based Design Approach of Software Architectures
7/10
Design Rules (Contd)
5. Composite objects identification
6. Manager objects identification
7. View objects identification
Separation of Concerns
Concerns Analysis
Ontologies
Our Software Design Approach of Software Architecture
Application of the Design Approach
8/12/2019 Concern-Oriented and Ontology-based Design Approach of Software Architectures
8/10
C4 Architectural Module
Separation of Concerns
Concerns Analysis
Ontologies
Our Software Design Approach of Software Architecture
Application of the Design Approach
8/12/2019 Concern-Oriented and Ontology-based Design Approach of Software Architectures
9/10
Sequence diagram
Separation of Concerns
Concerns Analysis
Ontologies
Our Software Design Approach of Software Architecture
Application of the Design Approach
8/12/2019 Concern-Oriented and Ontology-based Design Approach of Software Architectures
10/10
Implementation
Separation of Concerns
Concerns Analysis
Ontologies
Our Software Design Approach of Software Architecture
Application of the Design Approach