Downloads & Free Reading Options - Results

Course Technology https://archive.org/details/B-001-003-630

Course Technology https://archive.org/details/B-001-003-630

≪UML≫ 2000 — The Unified Modeling Language: Advancing the Standard Third International Conference York, UK, October 2–6, 2000 Proceedings Author: Andy Evans, Stuart Kent, Bran Selic Published by Springer Berlin Heidelberg ISBN: 978-3-540-41133-8 DOI: 10.1007/3-540-40011-7 Table of Contents: From Use Cases to System Operation Specifications On the Extension of UML with Use Case Maps Concepts HyperMSCs and Sequence Diagrams for Use Case Modelling and Testing Business-Oriented Constraint Language Processes, Roles, and Events: UML Concepts for Enterprise Architecture Statistical Constraints for EAI Heaven or Hell? A “Real-Time” UML? Towards a UML Profile for Interaction Design: The Wisdom Approach UMLi: The Unified Modeling Language for Interactive Applications A Diagrammatic Tool for Representing User Interaction in UML UML Extension for ASAM-GDI Device Capability Description Swinging UML How to Make Class Diagrams and State Machines Amenable to Constraint Solving and Proving UML Based Performance Modeling of Distributed Systems A Radical Revision of UML’s Role Concept The Role of “Roles” in Use Case Diagrams Ensuring Quality of Geographic Data with UML and OCL Contextual Diagrams as Structuring Mechanisms for Designing Configuration Knowledge Bases in UML The UML Family: Profiles, Prefaces and Packages Validating UML Models and OCL Constraints Modular Architecture for a Toolset Supporting OCL

≪UML≫ 2000 — The Unified Modeling Language: Advancing the Standard Third International Conference York, UK, October 2–6, 2000 Proceedings Author: Andy Evans, Stuart Kent, Bran Selic Published by Springer Berlin Heidelberg ISBN: 978-3-540-41133-8 DOI: 10.1007/3-540-40011-7 Table of Contents: From Use Cases to System Operation Specifications On the Extension of UML with Use Case Maps Concepts HyperMSCs and Sequence Diagrams for Use Case Modelling and Testing Business-Oriented Constraint Language Processes, Roles, and Events: UML Concepts for Enterprise Architecture Statistical Constraints for EAI Heaven or Hell? A “Real-Time” UML? Towards a UML Profile for Interaction Design: The Wisdom Approach UMLi: The Unified Modeling Language for Interactive Applications A Diagrammatic Tool for Representing User Interaction in UML UML Extension for ASAM-GDI Device Capability Description Swinging UML How to Make Class Diagrams and State Machines Amenable to Constraint Solving and Proving UML Based Performance Modeling of Distributed Systems A Radical Revision of UML’s Role Concept The Role of “Roles” in Use Case Diagrams Ensuring Quality of Geographic Data with UML and OCL Contextual Diagrams as Structuring Mechanisms for Designing Configuration Knowledge Bases in UML The UML Family: Profiles, Prefaces and Packages Validating UML Models and OCL Constraints Modular Architecture for a Toolset Supporting OCL

≪UML≫ 2000 — The Unified Modeling Language: Advancing the Standard Third International Conference York, UK, October 2–6, 2000 Proceedings Author: Andy Evans, Stuart Kent, Bran Selic Published by Springer Berlin Heidelberg ISBN: 978-3-540-41133-8 DOI: 10.1007/3-540-40011-7 Table of Contents: From Use Cases to System Operation Specifications On the Extension of UML with Use Case Maps Concepts HyperMSCs and Sequence Diagrams for Use Case Modelling and Testing Business-Oriented Constraint Language Processes, Roles, and Events: UML Concepts for Enterprise Architecture Statistical Constraints for EAI Heaven or Hell? A “Real-Time” UML? Towards a UML Profile for Interaction Design: The Wisdom Approach UMLi: The Unified Modeling Language for Interactive Applications A Diagrammatic Tool for Representing User Interaction in UML UML Extension for ASAM-GDI Device Capability Description Swinging UML How to Make Class Diagrams and State Machines Amenable to Constraint Solving and Proving UML Based Performance Modeling of Distributed Systems A Radical Revision of UML’s Role Concept The Role of “Roles” in Use Case Diagrams Ensuring Quality of Geographic Data with UML and OCL Contextual Diagrams as Structuring Mechanisms for Designing Configuration Knowledge Bases in UML The UML Family: Profiles, Prefaces and Packages Validating UML Models and OCL Constraints Modular Architecture for a Toolset Supporting OCL

The IA UML project sought to design and create a simple but powerful methodology and notation for analyzing assurance within the context of a system analysis and design. With such tools, software developers and information assurance analysts express their common problems and solutions in a fashion accessible to both groups. The project extended the common Unified Modeling Language(TradeMark) notation to express IA concepts. The report documents the history, developments, and conclusions of the project. It recommends practices for software development and suggests possible future work in this area.

The Unified Modeling Language (UML) is the standard method for specifying, visualizing, and documenting the artifacts of an object-oriented system under development. UML is the unification of the object-oriented methods developed by Grady Booch and James Rumbaugh, and of the Use Case Model developed by Ivar Jacobson. This paper discusses the application of UML by the Communications and Data Systems (CDS) team to model the ground control and command of the Space Station Biological Research Project (SSBRP) User Operations Facility (UOF). UML is used to define the context of the system, the logical static structure, the life history of objects, and the interactions among objects.

The Unified Modeling Language (UML) is the standard method for specifying, visualizing, and documenting the artifacts of an object-oriented system under development. UML is the unification of the object-oriented methods developed by Grady Booch and James Rumbaugh, and of the Use Case Model developed by Ivar Jacobson. This paper discusses the application of UML by the Communications and Data Systems (CDS) team to model the ground control and command of the Space Station Biological Research Project (SSBRP) User Operations Facility (UOF). UML is used to define the context of the system, the logical static structure, the life history of objects, and the interactions among objects.

The Unified Modeling Language (UML) is the standard method for specifying, visualizing, and documenting the artifacts of an object-oriented system under development. UML is the unification of the object-oriented methods developed by Grady Booch and James Rumbaugh, and of the Use Case Model developed by Ivar Jacobson. This paper discusses the application of UML by the Communications and Data Systems (CDS) team to model the ground control and command of the Space Station Biological Research Project (SSBRP) User Operations Facility (UOF). UML is used to define the context of the system, the logical static structure, the life history of objects, and the interactions among objects.

In response to concern about the effectiveness of programs for English-as-a-Second-Language students in California's schools, the Santa Ana Unified School District, in which over 80 percent of students are limited-English-proficient (LEP) conducted a study of both the operations and effectiveness of the district's language development program, using data accumulated over several years. The findings, documented in this report, cover five broad areas: information system reliability; language development services for LEP students; development of English fluency; impacts on reading and mathematics achievement; and an analysis of school attendance data. The report concludes with 14 recommendations for action in three areas: improving language development program effectiveness; improving data systems operations; and further study. Appended materials detail the technical aspects of the study. Contains 35 references. (MSE)

One of the key assumptions behind most Model-Based Development (MBD) efforts is the selection of Unified Modeling Language (UML) for the design language. While popular, more than 90 percent of all MBD efforts choose UML. This choice is often taken for granted. Typically, no trade studies are provided to support the choice of UML, especially the evaluation of UML traits that would make it adequate for use in MBD for safety-critical applications. Given that UML is selected for MBD, this report seeks to look at some of UML's traits in light of safety related expectations. Moreover, this report recommends practices for using UML on safety-critical applications and makes an appeal to the MBD community for additional suggested safe practices.

≪UML≫ 2001 — The Unified Modeling Language. Modeling Languages, Concepts, and Tools: 4th International Conference Toronto, Canada, October 1–5, 2001 Proceedings Author: Martin Gogolla, Cris Kobryn Published by Springer Berlin Heidelberg ISBN: 978-3-540-42667-7 DOI: 10.1007/3-540-45441-1 Table of Contents: The Preacher at Arrakeen An Action Semantics for MML The Essence of Multilevel Metamodeling Mapping between Levels in the Metamodel Architecture An Execution Algorithm for UML Activity Graphs Timing Analysis of UML Activity Diagrams UML Activity Diagrams as a Workflow Specification Language On Querying UML Data Models with OCL OCL as a Specification Language for Business Rules in Database Applications A Formal Semantics for OCL 1.4 Refactoring UML Models UML Support for Designing Software Systems as a Composition of Design Patterns Integrating the ConcernBASE Approach with SADL The Message Paradigm in Object-Oriented Analysis A UML-Based Approach to System Testing UML Modelling and Performance Analysis of Mobile Software Architectures Extending UML for Object-Relational Database Design Understanding UML — Pains and Rewards A Formal Semantics of UML State Machines Based on Structured Graph Transformation A Visualization of OCL Using Collaborations

Includes index

The Department of Defense uses modeling and simulation systems in many various roles, from research and training to modeling likely outcomes of command decisions. Simulation systems have been increasing in complexity with the increased capability of low-cost computer systems to support these DOD requirements. The demand for scenarios is also increasing, but the complexity of the simulation systems has caused a bottleneck in scenario development due to the limited number of individuals with knowledge of the arcane simulator languages in which these scenarios are written. This research combines the results of previous AFIT efforts in visual modeling languages to create a language that unifies description of entities within a scenario with its behavior using a visual tool that was developed in the course of this research. The resulting language has a grammar and syntax that can be parsed from the visual representation of the scenario. The language is designed so that scenarios can be described in a generic manner, not tied to a specific simulation system, allowing the future development of modules to translate the generic scenario into simulation system specific scenarios.

Includes bibliographical references (p. 537) and index

The objective for the UBOT project was to reduce the barriers for adoption of Semantic Web technology. The target adopters were DoD and Intelligence community software practitioners. The UBOT project focused on three major barriers: Ontology engineering is hard, Semantic markup creation is time consuming and expensive, and Semantic Web application engineering trade-offs are not well understood. The approach to reducing these barriers was to apply software engineering principles: automated tools, formal methods and software architecture. There were four research focus areas in this project: Ontology engineering; Automated markup generation; Reasoning architectures and benchmarks; and Semantic Web architectures and design patterns.

The objective for the UBOT project was to reduce the barriers for adoption of Semantic Web technology. The target adopters were DoD and Intelligence community software practitioners. The UBOT project focused on three major barriers: Ontology engineering is hard, Semantic markup creation is time consuming and expensive, and Semantic Web application engineering trade-offs are not well understood. The approach to reducing these barriers was to apply software engineering principles: automated tools, formal methods and software architecture. There were four research focus areas in this project: Ontology engineering; Automated markup generation; Reasoning architectures and benchmarks; and Semantic Web architectures and design patterns.

The Department of Defense (DoD) is developing a Joint Battlespace Infosphere, linking a large number of data sources and user applications. Debugging and analysis tools are required to aid in this process. Debugging of large object-oriented systems is a difficult cognitive process that requires understanding of both the overall and detailed behavior of the application. In addition, many such applications linked through a distributed system add to this complexity. Standard debuggers do not utilize visualization techniques, focusing mainly on information extracted directly from the source code. To overcome this deficiency, this research designs and implements a methodology that enables developers to analyze, troubleshoot and evaluate object-oriented systems using visualization techniques. It uses the standard UML class diagram coupled with visualization features such as focus+context, animation, graph layout, color encoding and filtering techniques to organize and present information in a manner that facilitates greater program and system comprehension. Multiple levels of abstraction, from low-level details such as source code and variable information to high-level structural detail in the form of a UML class diagram are accessible along with views of the program s control flow. The methods applied provide a considerable improvement (up to 1110%) in the number of classes that can be displayed in a set display area while still preserving user context and the semantics of UML, thus maintaining system understanding. Usability tests validated the application in terms of three criteria software visualization, debugging, and general system usability.

The Department of Defense (DoD) is developing a Joint Battlespace Infosphere, linking a large number of data sources and user applications. Debugging and analysis tools are required to aid in this process. Debugging of large object-oriented systems is a difficult cognitive process that requires understanding of both the overall and detailed behavior of the application. In addition, many such applications linked through a distributed system add to this complexity. Standard debuggers do not utilize visualization techniques, focusing mainly on information extracted directly from the source code. To overcome this deficiency, this research designs and implements a methodology that enables developers to analyze, troubleshoot and evaluate object-oriented systems using visualization techniques. It uses the standard UML class diagram coupled with visualization features such as focus+context, animation, graph layout, color encoding and filtering techniques to organize and present information in a manner that facilitates greater program and system comprehension. Multiple levels of abstraction, from low-level details such as source code and variable information to high-level structural detail in the form of a UML class diagram are accessible along with views of the program s control flow. The methods applied provide a considerable improvement (up to 1110%) in the number of classes that can be displayed in a set display area while still preserving user context and the semantics of UML, thus maintaining system understanding. Usability tests validated the application in terms of three criteria software visualization, debugging, and general system usability.

The Department of Defense (DoD) is developing a Joint Battlespace Infosphere, linking a large number of data sources and user applications. Debugging and analysis tools are required to aid in this process. Debugging of large object-oriented systems is a difficult cognitive process that requires understanding of both the overall and detailed behavior of the application. In addition, many such applications linked through a distributed system add to this complexity. Standard debuggers do not utilize visualization techniques, focusing mainly on information extracted directly from the source code. To overcome this deficiency, this research designs and implements a methodology that enables developers to analyze, troubleshoot and evaluate object-oriented systems using visualization techniques. It uses the standard UML class diagram coupled with visualization features such as focus+context, animation, graph layout, color encoding and filtering techniques to organize and present information in a manner that facilitates greater program and system comprehension. Multiple levels of abstraction, from low-level details such as source code and variable information to high-level structural detail in the form of a UML class diagram are accessible along with views of the program s control flow. The methods applied provide a considerable improvement (up to 1110%) in the number of classes that can be displayed in a set display area while still preserving user context and the semantics of UML, thus maintaining system understanding. Usability tests validated the application in terms of three criteria software visualization, debugging, and general system usability.

The Department of Defense (DoD) is developing a Joint Battlespace Infosphere, linking a large number of data sources and user applications. Debugging and analysis tools are required to aid in this process. Debugging of large object-oriented systems is a difficult cognitive process that requires understanding of both the overall and detailed behavior of the application. In addition, many such applications linked through a distributed system add to this complexity. Standard debuggers do not utilize visualization techniques, focusing mainly on information extracted directly from the source code. To overcome this deficiency, this research designs and implements a methodology that enables developers to analyze, troubleshoot and evaluate object-oriented systems using visualization techniques. It uses the standard UML class diagram coupled with visualization features such as focus+context, animation, graph layout, color encoding and filtering techniques to organize and present information in a manner that facilitates greater program and system comprehension. Multiple levels of abstraction, from low-level details such as source code and variable information to high-level structural detail in the form of a UML class diagram are accessible along with views of the program s control flow. The methods applied provide a considerable improvement (up to 1110%) in the number of classes that can be displayed in a set display area while still preserving user context and the semantics of UML, thus maintaining system understanding. Usability tests validated the application in terms of three criteria software visualization, debugging, and general system usability.