Three Innovative Software Engineering Methodologies

E. Foster
{"title":"Three Innovative Software Engineering Methodologies","authors":"E. Foster","doi":"10.1109/GOCICT.2015.25","DOIUrl":null,"url":null,"abstract":"Software engineering has come to the stage where speed of development, level of correctness, interoperability, user friendliness, usefulness, and reusability in different projects are very important factors in determining the success of a software engineering venture. Equally important is the use of methodologies for software design. In just over six decades, we have seen the progress of software design from an amorphous set of informal methodologies to structured techniques, formal methodologies, and object-oriented methodologies. In the area of object-oriented methodologies (OOM), the unified modeling language (UML) has made a significant contribution in defining a set of methodologies that can be applied to any software engineering effort. This paper draws on the UML methodologies and proposes three methodologies that could add richness and additional flexibility to the software engineering experience. They are system topology charts, object/entity specification grid, and the extended operation specification. The system topology charts include an information topology chart (ITC) that presents the object types and/or information entities in the way they will be managed in the software system, and a user interface topology chart (UITC) that presents operations the way they will appear in the system. The object/entity specification grid (O/ESG) adopts the conventions of the UML class diagram, but expands it to include additional critical information that lead to better software construction. The extended operation specification (EOS) embraces the UML guidelines for the activity diagram, but is flexible enough to include other techniques such as pseudo-code, Warnier-Orr diagram, and collaboration diagram. It also allows for the specification of other critical information not covered in these standard techniques.","PeriodicalId":221523,"journal":{"name":"2015 Annual Global Online Conference on Information and Computer Technology (GOCICT)","volume":"82 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2015-11-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"1","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2015 Annual Global Online Conference on Information and Computer Technology (GOCICT)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/GOCICT.2015.25","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 1

Abstract

Software engineering has come to the stage where speed of development, level of correctness, interoperability, user friendliness, usefulness, and reusability in different projects are very important factors in determining the success of a software engineering venture. Equally important is the use of methodologies for software design. In just over six decades, we have seen the progress of software design from an amorphous set of informal methodologies to structured techniques, formal methodologies, and object-oriented methodologies. In the area of object-oriented methodologies (OOM), the unified modeling language (UML) has made a significant contribution in defining a set of methodologies that can be applied to any software engineering effort. This paper draws on the UML methodologies and proposes three methodologies that could add richness and additional flexibility to the software engineering experience. They are system topology charts, object/entity specification grid, and the extended operation specification. The system topology charts include an information topology chart (ITC) that presents the object types and/or information entities in the way they will be managed in the software system, and a user interface topology chart (UITC) that presents operations the way they will appear in the system. The object/entity specification grid (O/ESG) adopts the conventions of the UML class diagram, but expands it to include additional critical information that lead to better software construction. The extended operation specification (EOS) embraces the UML guidelines for the activity diagram, but is flexible enough to include other techniques such as pseudo-code, Warnier-Orr diagram, and collaboration diagram. It also allows for the specification of other critical information not covered in these standard techniques.
三种创新的软件工程方法论
软件工程已经发展到这样一个阶段:不同项目中的开发速度、正确性水平、互操作性、用户友好性、有用性和可重用性是决定软件工程项目成功的非常重要的因素。同样重要的是软件设计方法的使用。在刚刚过去的60年里,我们已经看到了软件设计的进步,从一组无定形的非正式方法到结构化技术、形式化方法和面向对象的方法。在面向对象方法学(OOM)领域,统一建模语言(UML)在定义一组可应用于任何软件工程工作的方法学方面做出了重大贡献。本文借鉴了UML方法,并提出了三种可以为软件工程经验增加丰富性和额外灵活性的方法。它们是系统拓扑图、对象/实体规范网格和扩展操作规范。系统拓扑图包括一个信息拓扑图(ITC),它以将在软件系统中管理的方式表示对象类型和/或信息实体,以及一个用户界面拓扑图(UITC),它以将在系统中出现的方式表示操作。对象/实体规范网格(O/ESG)采用UML类图的约定,但对其进行了扩展,以包含导致更好的软件构造的附加关键信息。扩展操作规范(EOS)包含活动图的UML指导方针,但是足够灵活,可以包含其他技术,如伪代码、Warnier-Orr图和协作图。它还允许规范这些标准技术中未涵盖的其他关键信息。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术官方微信