Deposits of clastic carbonate-dominated (calciclastic) sedimentary slope systems in the rock record have been identified mostly as linearly-consistent carbonate apron deposits, even though most ancient clastic carbonate slope deposits fit the submarine fan systems better. Calciclastic submarine fans are consequently rarely described and are poorly understood. Subsequently, very little is known especially in mud-dominated calciclastic submarine fan systems. Presented in this study are a sedimentological core and petrographic characterisation of samples from eleven boreholes from the Lower Carboniferous of Bowland Basin (Northwest England) that reveals a >250 m thick calciturbidite complex deposited in a calciclastic submarine fan setting. Seven facies are recognised from core and thin section characterisation and are grouped into three carbonate turbidite sequences. They include: 1) Calciturbidites, comprising mostly of highto low-density, wavy-laminated bioclast-rich facies; 2) low-density densite mudstones which are characterised by planar laminated and unlaminated muddominated facies; and 3) Calcidebrites which are muddy or hyper-concentrated debrisflow deposits occurring as poorly-sorted, chaotic, mud-supported floatstones. These

Phd by thesis

https://onlinelibrary.wiley.com/doi/pdf/10.1002/stvr.247

Problem frames: analyzing and structuring software development problems. By Michael Jackson. Published by Addison‐Wesley, Boston, Massachusetts, U.S.A., ACM Press Series, 2001. ISBN: 0‐201‐59627‐X, 390 pages. Price: U.K. ?32.95, U.S.A. $49.99, soft cover.

Scenario languages are widely used in software development. Typical usage scenarios, forbidden behaviors, test cases, and many more aspects can be depicted with graphical scenarios. Scenario languages were introduced into the Unified Modeling Language (UML) under the name of Sequence Diagrams. The 2.0 version of UML changed Sequence Diagrams significantly and the expressiveness of the language was highly increased. However, the complexity of the language (and the diversity of the goals Sequence Diagrams are used for) yields several possible choices in its semantics. This paper collects and categorizes the semantic choices in the language, surveys the formal semantics proposed for Sequence Diagrams, and presents how these approaches handle the various semantic choices.

/pdf/the-many-meanings-of-uml-2-sequence-diagrams-a-survey-rjef4vsn8h.pdf

The many meanings of UML 2 Sequence Diagrams: a survey

Children's Online Privacy Protection Act

In light of the looming threats of global climate change and environmental degradation, the software research community has begun to recognize the need to transition toward environmental sustainability. However, the process of detecting, specifying and evaluating requirements related to environmental sustainability within industry is often neglected or at best performed after the system is built. Most software engineering teams do not include any environmental sustainability expertise to account for the broad range of sustainability concerns related to software systems. To overcome the barriers of incorporating environmental sustainability into the requirements engineering process, this paper suggests the use of sustainability requirement patterns (SRPs), which will provide software engineers with guidance on how to write specific types of sustainability requirements. SRPs contain information on the situations in which the pattern should be used, a starting point for developing sustainability requirements, and any other information needed to develop requirements of a specific type. This research is part of an overarching research project on Software Engineering for Sustainability.

Sustainability requirement patterns

UML 2 sequence diagram introduced many new structured control constructs, such as Combined Fragments, to express concurrent message exchanges. These new features makes it more expressive than it in UML 1, however, the lack of formal semantics descriptions makes it difficult for software practitioners and tool builders to construct and analyze sequence diagrams. In this paper, we adapt our previously developed template semantics to formalize the structured control constructs of sequence diagrams.

/pdf/formalize-uml-2-sequence-diagrams-4v0zynrnkp.pdf

Formalize UML 2 Sequence Diagrams

Very often in the software development life cycle, security is applied too late or important security aspects are overlooked. Although the use of security patterns is gaining popularity, the current state of security requirements patterns is such that there is not much in terms of a defining structure. To address this issue, we are working towards defining the important characteristics as well as the boundaries for security requirements patterns in order to make them more effective. By examining an existing general pattern format that describes how security patterns should be structured and comparing it to existing security requirements patterns, we are deriving characterizations and boundaries for security requirements patterns. From these attributes, we propose a defining format. We hope that these can reduce user effort in elicitation and specification of security requirements patterns.

Characterizations and boundaries of security requirements patterns

Graphical representations of scenarios, such as UML Sequence Diagrams, serve as a well-accepted means for modeling the interactions among software systems and their environment through the exchange of messages. The Combined Fragments of Sequence Diagram permit different types of control flows, including interleaving, alternative, and loop, for representing complex and concurrent behaviors. These fragments increase a Sequence Diagram's expressiveness, yet introduce a challenge to comprehend what behavior is possible in the traces that express system executions. Furthermore, software practitioners tend to use a collection of Sequence Diagrams to express multiple usages of a software system. It can be extremely difficult to determine manually that multiple Sequence Diagrams constitute a consistent, correct specification. 
This dissertation introduces an approach to codify the semantics of Sequence Diagrams with Combined Fragments in terms of Linear Temporal Logic (LTL) templates. In each template, different semantic aspects are expressed as separate, yet simple LTL formulas that can be composed to define the semantics of all the Combined Fragments. In addition, we develop an approach to transform Sequence Diagrams with Combined Fragments into the input language of model checker NuSMV. The analytical powers of model checking can be leveraged to automatically determine if a collection of Sequence Diagrams is consistent. Another benefit of this approach is the ability to specify certain safety properties of a system as intuitive Sequence Diagrams. 
We have developed tools to translate Sequence Diagrams to both LTL and NuSMV's input language to demonstrate that they can be automatically verified. We validate our techniques by analyzing two design examples taken from an insurance industry software application. We also model Health Insurance Portability and Accountability Act of 1996 (HIPAA) Privacy Rule using Sequence Diagrams to show that high-level policies can be described using Sequence Diagrams.

A formal framework for analyzing sequence diagram

The Combined Fragments of UML Sequence Diagram permit various types of control flow among messages (e.g., interleaving and branching) to express an aggregation of multiple traces encompassing complex and concurrent behaviors. However, Combined Fragments increase the difficulty of Sequence Diagram comprehension and analysis. To alleviate this problem, we introduce an approach to formally describe Sequence Diagrams with Combined Fragments in terms of the input language of the model checker NuSMV. This approach permits the verification of desired properties against Sequence Diagrams.

Formal Analysis of Sequence Diagram with Combined Fragments

A fundamental problem in the specification of regulatory privacy policies such as the Health Insurance Portability and Accountability Act (HIPAA) in a computer system is to state the policies precisely, consistent with their high-level intuition. In this paper, we propose UML sequence diagrams as a practical means to graphically express privacy policies. A graphical representation allows decision-makers such as application domain experts and security architects to easily verify and confirm the expected behavior. Once intuitively confirmed, our work in this article introduces an algorithmic approach to formalizing the semantics of sequence diagrams in terms of linear temporal logic (LTL) templates. In all the templates, different semantic aspects are expressed as separate, yet simple LTL formulas that can be composed to define the complex semantics of sequence diagrams. The formalization enables us to leverage the analytical powers of automated decision procedures for LTL formulas to determine if a collection of sequence diagrams is consistent, independent, etc. and also to verify if a system design conforms to the privacy policies. We evaluate our approach by modeling and analyzing a substantial subset of HIPAA rules using sequence diagrams.

Hui Shen

Papers

Formalize UML 2 Sequence Diagrams

Characterizations and boundaries of security requirements patterns

A formal framework for analyzing sequence diagram

Formal Analysis of Sequence Diagram with Combined Fragments

Sequence Diagram Aided Privacy Policy Specification