京都大学 / 0048 / 新制・課程博士 / 博士(経済学) / 甲第19459号 / 経博第528号 / 新制||経||276(附属図書館) / 32495 / 京都大学大学院経済学研究科経済学専攻 / (主査)教授 西山 慶彦, 准教授 奥井 亮, 准教授 高野 久紀 / 学位規則第4条第1項該当 / Doctor of Economics / Kyoto University / DGAM

京都大学 / 0048 / 新制・論文博士 / 博士(医学) / 乙第13213号 / 論医博第2163号 / 京都大学大学院医学研究科脳統御医科学系専攻 / (主査)教授 山下 潤, 教授 髙橋 良輔, 教授 木村 剛 / 学位規則第4条第2項該当 / Doctor of Medical Science / Kyoto University / DFAM

Each day, the need for as well as the amount of network-based applications grows and with it the implementation of RESTful APIs. For all these APIs there is a need for documentation of the API's behavior, its benefits, how it interacts with other APIs, and its expected result. To solve this; An API specification is constructed. This is a document containing the design philosophy of the APIs and can act as a guideline for how they should be constructed. When designing API specifications it is often difficult to understand what objective quality the API document upholds. To understand the objective quality of an API specification it must first be understood what a good objective quality is in this regard. We used static code tests (linter rules) that are mapped to three quality attributes that fit the industry's consensus of the most important quality attributes that need to be complacent for a good quality API. We then implemented an automatic process of splitting API specifications into positive and negative training data using the linter results of the rules. The resulting data is used to train our BERT model.The model will then be able to give an objective score to unseen API specifications. We then used a saliency map (textual heatmap) in order to understand BERT's decisions, which added the potential to generate new linter rules from the given results. After testing unseen API specifications on our BERT model, we saw that it was able to generate a reasonable quality score. Although, when inserting smaller features to generate a textual heatmap, the predictions of our model were not correct, hence not making it possible to understand BERT's decisions through our implementation. This also meant that new rules could not be acquired from reviewing the BERT's result.

Software intensive systems are developed to provide solutions in some problem domain and software engineering principles are employed to develop and implement that system. Software engineering principles should enhance the development and production of software artifacts and yet the artifacts often lack in quality. Crucial in the development process are requirements engineering activities and methods for software documentation. This research focused on requirements engineering activities, software requirements documentation and employed a new approach in these activities that incorporated ontology engineering principles. Ontology engineering refers to the set of activities concerned with the ontology development process, the ontology life cycle, the methods for building ontologies, and the tool suites and languages that support them. Ontologies facilitate domain knowledge reuse and sharing and provides a common vocabulary to system developers. The motivation of this research came from Ambr´osio and Kaiya, advocating the definition of the Software Requirements Knowledge Area of the Software Engineering Body of Knowledge (SWEBOK ) within an ontology system. The resulting system utilized the benefits of intelligent reasoning to elicit, automatically verify, extract and document software requirements. The requirements engineering process was modeled in an ontology. An ontology is a machine-readable data structure that distinctly defines concepts and describes relationships among those concepts. The requirements engineering process and ontology were the focal points in this research. A baseline ontology for software requirements engineering was created. The following are contributions of this research. A methodology was designed to enhance the software documentation production process. An initial ontology model of SWEBOK recommended data items was created. A method was provided to verify software requirements as they were elicited, entered and maintained in an ontology. A method was created that electronically provided provenance of software requirements. Software was created to automatically extract the software requirements from within an ontology.

No description available.

This thesis presents a new design process in which design specifications and task distribution are determined from a parallel multi user prospective. Using this method, projects are more easily decomposed into tasks that can be performed concurrently, thus decreasing the design time. Also, a framework is provided to determine the correct distribution of available talent and stakeholders that can be utilized on a given project. The research suggests that by involving the necessary stakeholders in a multi user setting, changes can be made quickly and without additional approval wait time. By including individuals from the various areas of required talent, persons of expertise will be able to work together in a mode of shared design rather than an iterative design process. Decreasing iterations as well as reducing wait time for approval will reduce the overall design time significantly. This method has been tested and validated utilizing controlled tests simulating real life situations of much larger scale. The validation results show that the new method does in fact improve design time and overall achievement of initial design goals

The mammalian central nervous system (CNS) has a high degree of complexity and cell type diversity that enables sophisticated processing of sensory information, circuit formation, and behaviour. While much is known about the patterning and specification of the major neuronal classes in the CNS, through processes such as morphogen gradient signaling and transcription factor combinatorial coding, much less is known about how subtypes within each cell class are specified. Bipolar cells are one of the main classes of interneurons in the vertebrate retina and consist of fifteen different subtypes based on their physiological function, morphology, and unique gene expression. The cellular mechanisms behind the specification of these subtypes are not fully known. In this thesis, I examine these mechanisms by investigating the role of extrinsic and intrinsic factors on the specification and differentiation of bipolar cell subtypes. We hypothesize that the specification of bipolar cell subtypes occurs in a multi-step manner and is dependent on non-cell autonomous (extrinsic) signals. To test this hypothesis, I conducted a series of experiments on the early postnatal mouse retina, which is the period when bipolar cells are generated. First, I examined whether bipolar cell marker onset was temporally ordered as would be predicted in a multi-step model. Postnatal day 3 (P3) mice were injected with EdU (5-ethynyl-2’-deoxyuridine), a thymidine analog that labels proliferating cells and then dissociated and fixed the retinal cells 24-120 hours after injection. My results show that Vsx2-5.3-PRE-Cre, a marker of pan-bipolar cells specification, is first detected 36 hrs after cell cycle exit, whereas specialized bipolar subtype-specific markers are expressed 48-60 hrs post-EdU injection. This observation is consistent with the idea that bipolar cells develop in a stepwise manner, first as an unspecified, pan-bipolar cell intermediate and then into one of the 15 subtypes. To further investigate this possibility, I developed a novel dissociated retinal culture assay that enabled me to accurately track retinal progenitor cells and postmitotic precursor cells and determine the requirement of cell autonomous and non-cell autonomous mechanisms during bipolar cell subtype specification. This assay involves culturing dissociated retinal cells from P3 EdU-injected mice at high density (abundant cell contact) or low density (scarce cell contact) at various timepoints, thereby allowing me to probe the role of these mechanisms in RPCs, early postmitotic cells, and late postmitotic cells. My findings revealed the first 24-48 hrs post cell cycle exit to be a critical, cell contact-dependent period for the specification of bipolar cell subtypes. This assay also allowed us to test the effect of blocking or activating the Notch and the Sonic Hedgehog (Shh) signal transduction pathways by using pharmacological compounds and recombinant ligands. Co-activation of Notch and Shh pathways increased the specification of Vsx1+ subtypes suggesting they play a role in their specification. Altogether, our results suggest that bipolar cell subtype specification follows a multi-step model, through an undifferentiated bipolar cell intermediate, and that cell contact plays a role in the specification mechanisms of bipolar cell subtype development. This is a novel finding that provides insight into the mechanisms underlying retinal neuronal subtype development and possibly in other neuronal cell types throughout the CNS. / Graduate / 10000-01-01

The Java platform is becoming a vital tool for developing real-time and safety-critical systems. Design patterns and the availability of Java libraries, both provide solutions to many known problems. Furthermore, the object-oriented nature of Java simplifies modular development of real-time systems. However, limitations of Java as a programming language for real-time systems are a notable obstacle to producing safe real-time systems. These limitations are found in the unpredictable execution model of the language, due to Java’s garbage collector, and the lack of support for non-functional specification and verification tools. In this dissertation I introduce SafeJML, a specification language for support of functional and non-functional specifications, based on an implementation of a safety-critical Java platform and the Java Modeling Language (JML). This dissertation concentrates on techniques that enable specification and dynamic checking of timing constraints for some important Java features, including methods and subtyping. SafeJML and these dynamic checking techniques allow modular specification and checking of safety-critical systems, including those that use object-orientation and design patterns. Such coding techniques could have maintenance benefits for real-time and safety-critical software

The research presented provides an overview of a 1U+ form factor propulsion system design developed for the Cal Poly CubeSat Laboratory (CPCL). This design utilizes a Radiofrequency Electrothermal Thruster (RFET) called Pocket Rocket that can generate 9.30 m/s of delta-V with argon, and 20.2 ± 3 m/s of delta-V with xenon. Due to the demand for advanced mission capabilities in the CubeSat form factor, a need for micro-propulsion systems that can generate between 1 – 1500 m/s of delta-V are necessary. By 2019, Pocket Rocket had been developed to a Technology Readiness Level (TRL) of 5 and ground tested in a 1U CubeSat form factor that incorporated propellant storage, pressure regulation, RF power and thruster control, as well as two Pocket Rocket thrusters under vacuum, and showcased a thrust of 2.4 mN at a required 10 Wdc of power with Argon propellant. The design focused on ground testing of the thruster and did not incorporate all necessary components for operation of the thruster. Therefore in 2020, a 1U+ Propulsion Module that incorporates Pocket Rocket, the RF amplification PCB, a propellant tank, propellant regulation and delivery, as well as a DC-RF conversion with a PIB, that are all attached to a 2U customer CubeSat for a 3U+ overall form factor. This design was created to increase the TRL level of Pocket Rocket from 5 to 8 by demonstrating drag compensation in a 400 km orbit with a delta-V of 20 ± 3 m/s in the flight configuration. The 1U+ Propulsion Module design included interface and requirements definition, assembly instructions, Concept of Operations (ConOps), as well as structural and thermal analysis of the system. The 1U+ design enhances the capabilities of Pocket Rocket in a 1U+ form factor propulsion system and increases future mission capabilities as well as propulsion system heritage for the CPCL.

Smart contracts are software systems that monitor and control the execution of legal contracts to ensure compliance with the contracts' terms and conditions. They often exploit Internet-of-Things technologies to support their monitoring functions, and blockchain technology to ensure the integrity of their data. Ethereum and business blockchain platforms, such as Hyperledger Fabric, are among the most popular choices for smart contract development. However, there is a substantial gap in the knowledge of smart contracts between developers and legal experts. Symboleo is a formal specification language for legal contracts that was introduced to address this issue. Symboleo specifications directly encode legal concepts such as parties, obligations, and powers. This thesis proposes a tool-supported method for translating Symboleo specifications into smart contracts. Its contributions include extensions to the existing Symboleo IDE, the implementation of the ontology and semantics of Symboleo into a reusable library, and the Symboleo2SC tool that generates Hyperledger Fabric code exploiting this library. Symboleo2SC was evaluated with three sample contracts. Experimentation with Symboleo2SC shows that legal contract specifications in Symboleo can be fully converted to smart contracts for monitoring purposes. Moreover, Symboleo2SC helps simplify the smart contract development process, saves development effort, and helps reduce risks of coding errors.