用于模型驱动域分析和软件开发的拓扑建模:功能和体系结构

J. Osis, Erika Asnina
{"title":"用于模型驱动域分析和软件开发的拓扑建模:功能和体系结构","authors":"J. Osis, Erika Asnina","doi":"10.4018/978-1-61692-874-2.ch002","DOIUrl":null,"url":null,"abstract":"There are many ways how to describe semantics. In software development during the so called problem domain analysis mostly informal approaches and languages are used. There are several causes, and one of more important is that the problem domain itself is not well determined. Thus, developers explore the problem domain by parts, at the beginning trying to understand each fragment of the problem domain and only after that trying to join those fragments together in the holistic and more formal representation. Indeed, the question about possibility of formal description of semantics still exists. The important property of diagrams used in software development is that they must provide very precise or even formal sense. In (Diskin, Kadish, Piessens, & ABstrAct","PeriodicalId":158461,"journal":{"name":"Model-Driven Domain Analysis and Software Development","volume":"189 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"49","resultStr":"{\"title\":\"Topological Modeling for Model-Driven Domain Analysis and Software Development: Functions and Architectures\",\"authors\":\"J. Osis, Erika Asnina\",\"doi\":\"10.4018/978-1-61692-874-2.ch002\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"There are many ways how to describe semantics. In software development during the so called problem domain analysis mostly informal approaches and languages are used. There are several causes, and one of more important is that the problem domain itself is not well determined. Thus, developers explore the problem domain by parts, at the beginning trying to understand each fragment of the problem domain and only after that trying to join those fragments together in the holistic and more formal representation. Indeed, the question about possibility of formal description of semantics still exists. The important property of diagrams used in software development is that they must provide very precise or even formal sense. In (Diskin, Kadish, Piessens, & ABstrAct\",\"PeriodicalId\":158461,\"journal\":{\"name\":\"Model-Driven Domain Analysis and Software Development\",\"volume\":\"189 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1900-01-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"49\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Model-Driven Domain Analysis and Software Development\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.4018/978-1-61692-874-2.ch002\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Model-Driven Domain Analysis and Software Development","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.4018/978-1-61692-874-2.ch002","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 49

摘要

描述语义的方法有很多种。在软件开发过程中,所谓的问题域分析大多使用非正式的方法和语言。有几个原因,其中一个更重要的原因是问题域本身没有很好地确定。因此,开发人员按部分探索问题域,在开始时试图理解问题域的每个片段,然后才尝试将这些片段以整体的和更正式的表示形式连接在一起。事实上,语义学形式描述的可能性问题仍然存在。在软件开发中使用的图的重要属性是它们必须提供非常精确甚至是形式化的意义。在Diskin, Kadish, Piessens, & ABstrAct中
本文章由计算机程序翻译,如有差异,请以英文原文为准。
查看原文
分享 分享
微信好友 朋友圈 QQ好友 复制链接
本刊更多论文
Topological Modeling for Model-Driven Domain Analysis and Software Development: Functions and Architectures
There are many ways how to describe semantics. In software development during the so called problem domain analysis mostly informal approaches and languages are used. There are several causes, and one of more important is that the problem domain itself is not well determined. Thus, developers explore the problem domain by parts, at the beginning trying to understand each fragment of the problem domain and only after that trying to join those fragments together in the holistic and more formal representation. Indeed, the question about possibility of formal description of semantics still exists. The important property of diagrams used in software development is that they must provide very precise or even formal sense. In (Diskin, Kadish, Piessens, & ABstrAct
求助全文
通过发布文献求助,成功后即可免费获取论文全文。 去求助
来源期刊
自引率
0.00%
发文量
0
期刊最新文献
Model-Driven Performance Evaluation of Web Application Portals Derivation of Use Cases from the Topological Computation Independent Business Model Model-Driven Configuration of Distributed Real-time and Embedded Systems Model-Driven Impact Analysis of Software Product Lines Reducing Enterprise Product Line Architecture Deployment and Testing Costs via Model Driven Deployment, Configuration, and Testing
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
现在去查看 取消
×
提示
确定
0
微信
客服QQ
Book学术公众号 扫码关注我们
反馈
×
意见反馈
请填写您的意见或建议
请填写您的手机或邮箱
已复制链接
已复制链接
快去分享给好友吧!
我知道了
×
扫码分享
扫码分享
Book学术官方微信
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术
文献互助 智能选刊 最新文献 互助须知 联系我们:info@booksci.cn
Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。
Copyright © 2023 Book学术 All rights reserved.
ghs 京公网安备 11010802042870号 京ICP备2023020795号-1