29th Annual IEEE/NASA Software Engineering Workshop - Tutorial Notes (SEW'05)最新文献

{"title":"Decision Support for Software Release Planning - Methods, Tools, and Practical Experience","authors":"G. Ruhe, Moshood Omolade Saliu, Pankaj Bhawnani, J. Momoh, An Ngo-The","doi":"10.1109/SEW.2005.4","DOIUrl":"https://doi.org/10.1109/SEW.2005.4","url":null,"abstract":"","PeriodicalId":192443,"journal":{"name":"29th Annual IEEE/NASA Software Engineering Workshop - Tutorial Notes (SEW'05)","volume":"29 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-04-03","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132691390","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"Architecture On Demand for Any Domain Using Stable Software Patterns","authors":"M. Fayad","doi":"10.1109/SEW.2005.1","DOIUrl":"https://doi.org/10.1109/SEW.2005.1","url":null,"abstract":"The lightening growth of technology coupled with the need for a quick turnaround time and demand for low production cost, are exerting a tremendous pressure and an immense desire for software developers, to create new and improved designs to respond to a rapidly changing business environment. Enterprises and developers must try to invest in building stable architectures that can be immediately adapted in many different ways to meet the new and emerging challenges. These kinds of architecture types are called architectures on demand, as they can be adapted depending on the situation to meet the future requirements and changes in creating the system. The primary focus of this seminar is to show how software stability concepts are used to develop on-demand architectures. The seminar attempts to focus on three key aspects: (1) Enduring Business Themes (EBTs), or business goals and transformations, which we call stable analysis patterns; (2) Business Objects (BOs), or business process designs, which we call stable design patterns; and (3) Industrial Objects (IOs), or application objects. Both EBTs and BOs form a stable core, and, therefore provide architectures on demand for any domain. We shall call these architectures as “stable architectural patterns.” Our approach is based on an iteratively refined and practically defined framework arrangement that we call the “software stability model,” which consist of three major phases: 1. Enduring Business Themes (EBTs) represent the goals of the business and govern business transformation. We shall also call them “Stable Analysis Patterns”. Their main impact on business design is many and includes a technique for dividing an enterprise into self-contained business components, in order to identify new opportunities for innovation and improvement, and prioritize business transformation activities. These critical components may span a single department of an enterprise or multiple departments inside an enterprise or an ecosystem of a hub of partner enterprises. These goals will be ultimately achieved through the external adaptation of stable analysis patterns. Architectures on Demand for Any Domain Using Stable Software Patterns Seminar Proposal © M.E. Fayad, PhD, 2000-2006 2 2. Business Objects (BOs) are the capabilities, or the “workhorses,” of the enterprise. BOs are called “Stable Design Patterns.” These usually contain the workflow of the business, business process designs and infrastructure, like hooks, a gang of four pattern, and other similar concepts. BOs mainly focus on the operational aspects of business transformation. They always seek to design and implement flexible processes that integrate cross-divisional and cross-enterprise processes, as well as core process activities. BOs are the keys to business and support processes, such as finance and human resources. Flexibility is realized by separating business logic, application logic and data management in order to reduce and improve the time taken ","PeriodicalId":192443,"journal":{"name":"29th Annual IEEE/NASA Software Engineering Workshop - Tutorial Notes (SEW'05)","volume":"69 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-04-03","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129116828","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"Software Development for Real-Time Safety-Critical Applications","authors":"A. Kornecki, J. Zalewski","doi":"10.1109/SEW.2005.6","DOIUrl":"https://doi.org/10.1109/SEW.2005.6","url":null,"abstract":"We develop a software for real-time safety-critical applications. We study the fundamental concepts of real-time systems, design principles for real-time architectures, real-time programming. Rate monotonic analysis (RMA) refers to the real-time performance analysis of a system that uses static priority driven scheduling. Three application case studies: benchmark problem, air traffic control system, satellite ground control station is discussed.","PeriodicalId":192443,"journal":{"name":"29th Annual IEEE/NASA Software Engineering Workshop - Tutorial Notes (SEW'05)","volume":"50 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-12-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115675640","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"Designing Software Product Lines with UML","authors":"H. Gomaa","doi":"10.1109/SEW.2005.5","DOIUrl":"https://doi.org/10.1109/SEW.2005.5","url":null,"abstract":"Software Product Line Development advocates software reuse by modeling common and variable artefacts separately across members of a family of products. Aspect-Oriented Software Development aims at separation of concerns with “aspects†​ to increase modularity, reusability, maintainability and ease of evolution. In this paper, we apply an as-pect-oriented use case modeling approach to product line system modeling. A use case specification captures stake-holders concerns as interactions between a system and its actors. We adapt our previous work with the introduction of a “variability†​ r 40 Open Source, Free and Top Unified Modeling Language (UML) Tools : Review of Top Open Source and Free Unified Modeling Language (UML) Tools including ArgoUML, StarUML, UMLet, Dia, BOUML, Violet, EclipseUML, gModeler, RISE, NClass, NetBeans IDE, GenMyModel, Plantuml, UML Modeller, Open ModelSphere, Oracle Jdeveloper, Papyrus, Oracle SQL Developer are the Top Open Source and Free Unified Modeling Language (UML) Tools.Top Unified Modeling Language (UML) Tools : Review of Top Unified Modeling Language (UML) Tools including IBM Rational Rose, Visio, StarUML, Visual Paradigm, Sparx Enterprise Arch Explore a Service-Oriented Software product lines (SoSPL) methodology that applies SPL variability analysis techniques to Web services to design customized service-based applications. Find out how software product lines (SPL) promote agile and flexible application development for evolving system families. And discover how the adoption of SPL principles can provide a systematic way to analyze and design service-oriented applications. You can model business processes using Unified Modeling Language (UML) activity diagrams. Activity diagrams are particularly useful in detailing the workflow of business processes during domain business modeling. Figure 1 shows a hotel reservation process.","PeriodicalId":192443,"journal":{"name":"29th Annual IEEE/NASA Software Engineering Workshop - Tutorial Notes (SEW'05)","volume":"42 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127944514","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}