DOCSLIB.ORG

3D Virtual Prototyping Traces New Avenues for Fashion Design And

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Scienc ile e & Papahristou and Bilalis, J Textile Sci Eng 2017, 7:2 xt e E T n : g DOI 10.4172/2165-8064.1000297 f i o n l e a e n r r i n u g o J Journal of Textile Science & Engineering ISSN: 2165-8064 Research Article Article Open Access 3D Virtual Prototyping Traces New Avenues for Fashion Design and Product Development: A Qualitative Study Papahristou E* and Bilalis N Technical University of Crete, School of Production Engineering and Management, Kounoupidiana, 73100, Crete Greece, Greece Abstract Design, Development and Production have largely relied on the same, often manual, methods despite all the technological advances happening in the world outside of fashion and apparel. Ten years ago, academic research (by contrast to the existing 3D virtual software solutions) posited about clothing companies complaints’ on the lack of effective garment-oriented CAD packages to design directly in 3D and provide the model list with tools for shape modelling and cloth behaviour simulation. Although, common place in other sectors, 3D virtual prototyping in the apparel industry has been slow and complex. A qualitative research investigating the level of the technology implementation in the early adopters, the vision of the big corporations, entrepreneurs and professional users for the global clothing and fashion industry as well as the challenges, opportunities and barriers that need to be overcome in order for digital prototype to accelerate business processes on an integrated basis. Keywords: Virtual simulation; Fashion industry; Prototype; visualization or PLM and according to their roles and relationships Automotive; Visualization with the industry we divided them in 4 groups: Introduction 1. Technology providers-vendors The fashion industry faces the increasing complexity of its activities 2. Managers-executives-professional users such as the globalization of the market, the proliferation of information, 3. Entrepreneurs-independent user the reduced time to market, the increasing distance between industrial partners and pressures related to costs. Digital prototype in the textile 4. Academics and clothing industry enables technologies in the process of product The research has been contacted using a combination of primary development where various operators are involved in the different and secondary sources. First hand interviews with the previously stages, with various skills and competencies, and different necessity mentioned categories were used; interviewees were called to share their of formalizing and defining in a deterministic way the result of their experiences, answer questions, examine and criticize the existing tools activities. Taking into account the recent trends in the industry, the and help the investigation study to dig deeper into the characteristics of product development cycle and the use of new digital technologies cannot be restricted in the “typical cycle” but additional tools and skills these technologies, the way they affect the apparel product development are required to be integrated taking into account these developments [1]. process and see if the hypothesis stated by the vendor side (3D design and visualization features is now an important part of the revolution in Design, Development and Production have largely relied on the digital design and production technology for apparel manufacturers) same, often manual, methods despite all the technological advances is established by the experienced users of 3D, the independent happening in the world outside of fashion and apparel. Ten years ago, consultants of the industry and the academic researchers. The software academic research (by contrast to the existing 3D virtual software NVivo was chosen as a state-of-the-art analysis tool for qualitative and solutions) posited about clothing companies complaints’ on the lack mixed methods research. of effective garment-oriented CAD packages to design directly in 3D and provide the model list with tools for shape modelling and cloth Virtualization as an Integral Part of Fashion Product behaviour simulation [2]. Nowadays, with the growth of demand from Development better educated consumers, mass customization, e-commerce, advances in virtual reality applications, the virtual garment development is The 3D concept is an important development in the design process. strongly desired in order to optimize apparel industry’s design and It allows designers to unleash their creativity in a real-life visualization development processes. Although this is now commonplace in the of designs that could previously only be imagined through 2D sketches. aeronautical, automotive, furniture and shoe sectors, development in It is clearly visible that the world is going digital. 3D virtualization plays the apparel industry has been slow and complex; mainly due to the dropping and stretching properties inherent in fabric, which are not only radically different between different fabric types and constructions, *Corresponding author: Papahristou E, Technical University of Crete, School of but also in the direction off weave or knit within the piece [3]. Production Engineering and Management, Kounoupidiana, 73100, Crete Greece, Greece, Tel: +30 2821 037001; E-mail: [email protected] This research investigated the level of the technology implementation Received April 24, 2017; Accepted April 27, 2017; Published April 30, 2017 in the early adopters, the vision of the big corporations, entrepreneurs and professional users for the global clothing and fashion industry as well Citation: Papahristou E, Bilalis N (2017) 3D Virtual Prototyping Traces New Avenues for Fashion Design and Product Development: A Qualitative Study. J as the challenges, opportunities and barriers that need to be overcome Textile Sci Eng 6: 297. doi: 10.4172/2165-8064.1000297 in order for digital prototype to accelerate business processes on an integrated basis. During the process of identifying everyone affected Copyright: © 2017 Papahristou E. This is an open-access article distributed under the terms of the Creative Commons Attribution License, which permits unrestricted by a change initiative, we grouped the areas that will be impacted by use, distribution, and reproduction in any medium, provided the original author and the new involved technology implementation like 3D prototyping and source are credited. J Textile Sci Eng, an open access journal Volume 7 • Issue 2 • 1000297 ISSN: 2165-8064 Citation: Papahristou E, Bilalis N (2017) 3D Virtual Prototyping Traces New Avenues for Fashion Design and Product Development: A Qualitative Study. J Textile Sci Eng 6: 297. doi: 10.4172/2165-8064.1000297 Page 2 of 6 a leading part in this. According to Dassault System though, many the traditional apparel design process and the repetitive manual processes still do not live up to their full potential. Creative 3D materials changes. The fact is that 3D visualization is now much more embraced have always been painful whereas vendor software companies claim and embedded in the fashion industry than in the past. Interviewees that with 3D virtualization is a fantastic way of starting the process of were called to share their experiences, answer questions, examine and apparel product development. If it is so, then why is the industry using criticize the existing tools and help the investigation study to dig deeper 2D tools to design products that are fundamentally 3D objects? If 3D into the characteristics of these technologies, the way they affect the virtualization has so many benefits and potential for the business why apparel product development process and see if the hypothesis stated hasn’t it been adopted in a large scale yet? by the vendor side is established by the experienced users of 3D, the independent consultants of the industry and the academic researchers. The clothing industry has been transformed from a traditional labour-intensive industry into a highly automated and computer- Materials and Methods aided one. However, the primary drawback for the most of the existing commercial CAD systems in the last decade, was, that they relied on The research project gathered the opinions and experiences mere geometrical modelling and did not provide virtual simulation of experts with direct contact and use of technology solutions for tools (with few exceptions) [2]. 3D technology started to get in that the product development process like 3D and virtual prototype or market but needed technology advancements to get there [4]. The PLM (Product Lifecycle Management); the selection of the sample first developed sewing and draping tools gave the designers the ability was purposive rather than random. 100 Experts from four different to evaluate their design on the screen but the proposed approaches backgrounds of the fashion industry were selected to participate in [5], were generally computationally intensive. Later, Wang et al. [6], this survey contacting personal interviews. As Figure 1a shows, 43 developed a 3D sketch input method for the design of the garment “relatively unstructured” personal interviews were carried out; some of pattern to fit the 3D human model but still, they were not effective in them in typing due to lack of time on their behalf or the time difference supporting design modifications. Updated algorithms, Luo et al. [7] between countries 34 didn't respond at all, although they have been provided 3D garment fitting simulation the ability to react to the 2D contacted with a coming-up e-mail twice. In Figures 1b-1e, participants pattern modification efficiently
Recommended publications
  • Budgen, Software Design Methods

    Budgen, Software Design Methods

    David Budgen The Loyal Opposition Software Design Methods: Life Belt or Leg Iron? o software design methods have a correctly means “study of method.”) To address, but future? In introducing the January- not necessarily answer, this question, I’ll first consider D February 1998 issue of IEEE Software,Al what designing involves in a wider context, then com- Davis spoke of the hazards implicit in pare this with what we do, and finally consider what “method abuse,”manifested by a desire this might imply for the future. to “play safe.”(If things go well, you can take the credit, but if they go wrong, the organization’s choice of method can take the blame.) As Davis argues, such a THE DESIGN PROCESS policy will almost certainly lead to our becoming builders of what he terms “cookie-cutter, low-risk, low- Developing solutions to problems is a distinguish- payoff, mediocre systems.” ing human activity that occurs in many spheres of life. The issue I’ll explore in this column is slightly dif- So, although the properties of software-based systems ferent, although it’s also concerned with the problems offer some specific problems to the designer (such as that the use of design methods can present. It can be software’s invisibility and its mix of static and dynamic expressed as a question: Will the adoption of a design properties), as individual design characteristics, these method help the software development process (the properties are by no means unique. Indeed, while “life belt” role), or is there significant risk that its use largely ignored by software engineers, the study of the will lead to suboptimum solutions (the “leg iron”role)? nature of design activities has long been established Robert L.
  • Design Piracy: the Extensive Impact of a Fashion Knockoff

    Design Piracy: the Extensive Impact of a Fashion Knockoff

    On the Monetary Impact of Fashion Design Piracy Gil Appel Marshall School of Business, University of Southern California [email protected] Barak Libai Arison School of Business, Interdisciplinary Center (IDC), Herzliya [email protected] Eitan Muller Stern School of Business, New York University Arison School of Business, Interdisciplinary Center (IDC), Herzliya [email protected] July 2017 The authors would like to thank Roland Rust, Senior Editor and reviewers, On Amir, Michael Haenlein, Liraz Lasry, Irit Nitzan, Raphael Thomadsen, the participants of the Marketing Science and EMAC conferences and the participants of the seminars of the business schools at University of California at Davis, the University of California at San Diego, and Stanford University for a number of helpful comments and suggestions. On the Monetary Impact of Fashion Design Piracy Abstract Whether to legally protect original fashion designs against design piracy (“knockoffs”) is an ongoing debate among legislators, industry groups, and legal academic circles, yet to-date this discussion has not utilized marketing knowledge and formal approaches. We combine data collected on the growth of fashion items, price markups, and industry statistics, to create a formal analysis of the essential questions in the base of the debate. We distinguish between three effects: Acceleration, whereby the presence of a pirated design increases the awareness of the design, and thus might have a positive effect on the growth of the original; Substitution, which represents the loss of sales due to consumers who would have purchased the original design, yet instead buy the knockoff; and the loss due to Overexposure of the design that follows the loss of uniqueness due to the design becoming too popular, causing some consumer not to adopt the design or stop using it.
  • Software Design Document 1

    Software Design Document 1

    SOFTWARE DESIGN DOCUMENT 1. Introduction The following subsections of the Software Design Document (SDD) should provide an overview of the entire SDD. 1.1 Purpose This subsection should explain the purpose of the SDD and specify the intended audience for it. The SDD described the software structure, software components, interfaces and data necessary for the implementation phase. Each requirement in the SRS should be traceable to one or more design entities in the SDD. 1.2 Scope This subsection should relate the design document to the SRS and to the software to be developed. 1.3 Definitions, Acronyms and Abbreviations This subsection should provide the definitions of all terms, acronyms and abbreviations that are used in the SDD. 2. References This subsection should provide a complete list of all documents referenced in the SDD. It should identify these references by title, report number, date and publishing organization. It should also specify the sources from which these references are available. 3. Attributes of Design Entities There are some attributes common to all entities, regardless of the approach utilized, whether procedural or object-oriented. These are used in subsections 4 and later. 3.1 Identification The name of the entity should be specified. Two entities should not have the same name. 3.2 Type The type attribute should describe the nature of the entity. It may simply name the kind of entity, such as subprogram, module, procedure, process, data item, object etc. Alternatively, design entities can be grouped, in order to assist in locating an entity dealing with a particular type of information.
  • Change Orders Ordeal: the Output of Project Disintegration

    Change Orders Ordeal: the Output of Project Disintegration

    International Journal of Business, Humanities and Technology Vol. 2 No. 1; January 2012 Change Orders Ordeal: The Output of Project Disintegration Roberto Soares, Ph.D., D.Sc., AIC, PE Assistant Professor College of Computing, Engineering and Construction University of North Florida Jacksonville, Florida United States of America Abstract Change orders are one of the most controversial issues in construction contracts and require successful negotiations to avoid claims and possible litigation. Contractors, owners and architects behave differently when dealing with change orders. The aim of this paper is to demonstrate that change orders are the natural result of the disintegration of design and construction, which started in the US in 1893 with a Congressional Act formally separating the design and construction phases of a capital project .Delivery methods such as Design-Build (DB) and Construction Management at Risk (CMR), which are designed to mend the missing integration of design and construction and, consequently, eliminate the existence of change order conflict are proposed to recover the level of integration that existed at the time of the master builder. Key words: change orders, project integration, design-build, delivery methods 1. Introduction Change orders in construction are one of the most controversial issues to manage and a challenge to project management to satisfactorily resolve any change in order to avoid claims. Any construction contract is signed under the principle of “good faith,” which means that the parties will trust each other to perform according to the contract and that the contract is fair with no intention of taking advantage of the parties during the life of the contract.
  • Software Design Document (SDD) Template

    Software Design Document (SDD) Template

    Software Design Document (SDD) Template Software design is a process by which the software requirements are translated into a representation of software components, interfaces, and data necessary for the implementation phase. The SDD shows how the software system will be structured to satisfy the requirements. It is the primary reference for code development and, therefore, it must contain all the information required by a programmer to write code. The SDD is performed in two stages. The first is a preliminary design in which the overall system architecture and data architecture is defined. In the second stage, i.e. the detailed design stage, more detailed data structures are defined and algorithms are developed for the defined architecture. This template is an annotated outline for a software design document adapted from the IEEE Recommended Practice for Software Design Descriptions. The IEEE Recommended Practice for Software Design Descriptions have been reduced in order to simplify this assignment while still retaining the main components and providing a general idea of a project definition report. For your own information, please refer to IEEE Std 1016­1998 1 for the full IEEE Recommended Practice for Software Design Descriptions. 1 http://www.cs.concordia.ca/~ormandj/comp354/2003/Project/ieee­SDD.pdf Downloaded from http://www.tidyforms.com (Team Name) (Project Title) Software Design Document Name (s): Lab Section: Workstation: Date: (mm/dd/yyyy) Downloaded from http://www.tidyforms.com Software Design Document TABLE OF CONTENTS 1. INTRODUCTION 2 1.1 Purpose 2 1.2 Scope 2 1.3 Overview 2 1.4 Reference Material 2 1.5 Definitions and Acronyms 2 2.
  • SELECTED TOPICS in NOVEL OPTICAL DESIGN by Yufeng

    SELECTED TOPICS in NOVEL OPTICAL DESIGN by Yufeng

    Selected Topics in Novel Optical Design Item Type text; Electronic Dissertation Authors Yan, Yufeng Publisher The University of Arizona. Rights Copyright © is held by the author. Digital access to this material is made possible by the University Libraries, University of Arizona. Further transmission, reproduction, presentation (such as public display or performance) of protected items is prohibited except with permission of the author. Download date 03/10/2021 19:21:21 Link to Item http://hdl.handle.net/10150/636613 SELECTED TOPICS IN NOVEL OPTICAL DESIGN by Yufeng Yan ____________________________ Copyright © Yufeng Yan 2019 A Dissertation Submitted to the Faculty of the JAMES C. WYANT COLLEGE OF OPTICAL SCIENCES In Partial Fulfillment of the Requirements For the Degree of DOCTOR OF PHILOSOPHY In the Graduate College THE UNIVERSITY OF ARIZONA 2019 2 3 ACKNOWLEDGEMENTS I would like to first thank my parents in China for their support that encouraged me to pursue both bachelor’s, master’s and doctorate degree abroad. I would also like to thank my girlfriend Jie Feng for her strong support and being the first reader of each chapter of this dissertation. I am very grateful to my adviser, Dr. Jose Sasian. This project would not have been possible without his constant support and mentoring. I would also like to acknowledge the members of my committee, Dr. Rongguang Liang and Dr. Jim Schwiegerling, who took their time to review this dissertation and gave me valuable suggestions. In addition, I would like to thank Zemax for giving me permission to use their software for designing and evaluating the optical systems in this project.
  • Software Reliability and Dependability: a Roadmap Bev Littlewood & Lorenzo Strigini

    Software Reliability and Dependability: a Roadmap Bev Littlewood & Lorenzo Strigini

    Software Reliability and Dependability: a Roadmap Bev Littlewood & Lorenzo Strigini Key Research Pointers Shifting the focus from software reliability to user-centred measures of dependability in complete software-based systems. Influencing design practice to facilitate dependability assessment. Propagating awareness of dependability issues and the use of existing, useful methods. Injecting some rigour in the use of process-related evidence for dependability assessment. Better understanding issues of diversity and variation as drivers of dependability. The Authors Bev Littlewood is founder-Director of the Centre for Software Reliability, and Professor of Software Engineering at City University, London. Prof Littlewood has worked for many years on problems associated with the modelling and evaluation of the dependability of software-based systems; he has published many papers in international journals and conference proceedings and has edited several books. Much of this work has been carried out in collaborative projects, including the successful EC-funded projects SHIP, PDCS, PDCS2, DeVa. He has been employed as a consultant to industrial companies in France, Germany, Italy, the USA and the UK. He is a member of the UK Nuclear Safety Advisory Committee, of IFIPWorking Group 10.4 on Dependable Computing and Fault Tolerance, and of the BCS Safety-Critical Systems Task Force. He is on the editorial boards of several international scientific journals. 175 Lorenzo Strigini is Professor of Systems Engineering in the Centre for Software Reliability at City University, London, which he joined in 1995. In 1985-1995 he was a researcher with the Institute for Information Processing of the National Research Council of Italy (IEI-CNR), Pisa, Italy, and spent several periods as a research visitor with the Computer Science Department at the University of California, Los Angeles, and the Bell Communication Research laboratories in Morristown, New Jersey.
  • Design by Contract: the Lessons of Ariane

    Design by Contract: the Lessons of Ariane

    . Editor: Bertrand Meyer, EiffelSoft, 270 Storke Rd., Ste. 7, Goleta, CA 93117; voice (805) 685-6869; [email protected] several hours (at least in earlier versions of Ariane), it was better to let the computa- tion proceed than to stop it and then have Design by to restart it if liftoff was delayed. So the SRI computation continues for 50 seconds after the start of flight mode—well into the flight period. After takeoff, of course, this com- Contract: putation is useless. In the Ariane 5 flight, Object Technology however, it caused an exception, which was not caught and—boom. The exception was due to a floating- point error during a conversion from a 64- The Lessons bit floating-point value, representing the flight’s “horizontal bias,” to a 16-bit signed integer: In other words, the value that was converted was greater than what of Ariane can be represented as a 16-bit signed inte- ger. There was no explicit exception han- dler to catch the exception, so it followed the usual fate of uncaught exceptions and crashed the entire software, hence the onboard computers, hence the mission. This is the kind of trivial error that we Jean-Marc Jézéquel, IRISA/CNRS are all familiar with (raise your hand if you Bertrand Meyer, EiffelSoft have never done anything of this sort), although fortunately the consequences are usually less expensive. How in the world everal contributions to this made up of respected experts from major department have emphasized the European countries, which produced a How in the world could importance of design by contract report in hardly more than a month.
  • Improving Software Reliability Using Software Engineering Approach- a Review

    Improving Software Reliability Using Software Engineering Approach- a Review

    International Journal of Computer Applications (0975 – 8887) Volume 10– No.5, November 2010 Improving Software Reliability using Software Engineering Approach- A Review Aasia Quyoum Mehraj – Ud - Din Dar S. M. K. Quadri Research Scholar Director, IT & SS Director Computer Sciences University of Kashmir (India) University of Kashmir (India) University of Kashmir (India) ABSTRACT Randomness means that the failure can‟t be predicted accurately. Software Reliability is an important facet of software quality. The randomness of the failure occurrence is necessary for Software reliability is the probability of the failure free operation reliability modeling. In [MIO87], it is suggested that reliability of a computer program for a specified period of time in a specified modeling should be applied to systems larger than 5000 LOC. environment. Software Reliability is dynamic and stochastic. It differs from the hardware reliability in that it reflects design 3. RELIABILITY PROCESS perfection, rather than manufacturing perfection. This article The reliability process in generic terms is a model of the provides an overview of Software Reliability which can be reliability-oriented aspects of software development, operations categorized into: modeling, measurement and improvement, and and maintenance. The set of life cycle activities and artifacts, then examines different modeling technique and metrics for together with their attributes and interrelationships that are software reliability, however, there is no single model that is related to reliability comprise the reliability process. The artifacts universal to all the situations. The article will also provide an of the software life cycle include documents, reports, manuals, overview of improving software reliability and then provides plans, code configuration data and test data.
  • Theoretically Comparing Design Thinking to Design Methods for Large- Scale Infrastructure Systems

    Theoretically Comparing Design Thinking to Design Methods for Large- Scale Infrastructure Systems

    The Fifth International Conference on Design Creativity (ICDC2018) Bath, UK, January 31st – February 2nd 2018 THEORETICALLY COMPARING DESIGN THINKING TO DESIGN METHODS FOR LARGE- SCALE INFRASTRUCTURE SYSTEMS M.A. Guerra1 and T. Shealy1 1Civil Engineering, Virginia Tech, Blacksburg, USA Abstract: Design of new and re-design of existing infrastructure systems will require creative ways of thinking in order to meet increasingly high demand for services. Both the theory and practice of design thinking helps to exploit opposing ideas for creativity, and also provides an approach to balance stakeholder needs, technical feasibility, and resource constraints. This study compares the intent and function of five current design strategies for infrastructure with the theory and practice of design thinking. The evidence suggests the function and purpose of the later phases of design thinking, prototyping and testing, are missing from current design strategies for infrastructure. This is a critical oversight in design because designers gain much needed information about the performance of the system amid user behaviour. Those who design infrastructure need to explore new ways to incorporate feedback mechanisms gained from prototyping and testing. The use of physical prototypes for infrastructure may not be feasible due to scale and complexity. Future research should explore the use of prototyping and testing, in particular, how virtual prototypes could substitute the experience of real world installments and how this influences design cognition among designers and stakeholders. Keywords: Design thinking, design of infrastructure systems 1. Introduction Infrastructure systems account for the vast majority of energy use and associated carbon emissions in the United States (US EPA, 2014).
  • Design-Build Manual

    Design-Build Manual

    DISTRICT OF COLUMBIA DEPARTMENT OF TRANSPORTATION DESIGN BUILD MANUAL May 2014 DISTRICT OF COLUMBIA DEPARTMENT OF TRANSPORTATION MATTHEW BROWN - ACTING DIRECTOR MUHAMMED KHALID, P.E. – INTERIM CHIEF ENGINEER ACKNOWLEDGEMENTS M. ADIL RIZVI, P.E. RONALDO NICHOLSON, P.E. MUHAMMED KHALID, P.E. RAVINDRA GANVIR, P.E. SANJAY KUMAR, P.E. RICHARD KENNEY, P.E. KEITH FOXX, P.E. E.J. SIMIE, P.E. WASI KHAN, P.E. FEDERAL HIGHWAY ADMINISTRATION Design-Build Manual Table of Contents 1.0 Overview ...................................................................................................................... 1 1.1. Introduction .................................................................................................................................. 1 1.2. Authority and Applicability ........................................................................................................... 1 1.3. Future Changes and Revisions ...................................................................................................... 1 2.0 Project Delivery Methods .............................................................................................. 2 2.1. Design Bid Build ............................................................................................................................ 2 2.2. Design‐Build .................................................................................................................................. 3 2.3. Design‐Build Operate Maintain....................................................................................................
  • Combining Design by Contract and Inference Rules of Programming Logic Towards Software Reliability

    Combining Design by Contract and Inference Rules of Programming Logic Towards Software Reliability

    Combining Design by Contract and Inference Rules of Programming Logic towards Software Reliability Nuha Aldausari*, Cui Zhang and Jun Dai Department of Computer Science, California State University, Sacramento, CA 95819, U.S.A. Keywords: Software Security, Software Reliability, Program Specifications, Error Detection, Design by Contract, Programming Logic. Abstract: Detecting errors in software products is very important to software reliability because many security vulnerabilities are caused by the defects in software. Design by contract (DBC) is an effective methodology that dynamically checks whether a program meets its specifications, which are also called design contracts, and whether there are errors in the program. The contracts for object-oriented programs are defined in terms of preconditions and postconditions for methods as well as invariants for classes. However, if there is an error in a large piece of code that has a design contract, it is still difficult to identify the exact location of that error. To address this issue, a tool named Subcontractor has been developed. Subcontractor is implemented in Eclipse environment using libraries such as Java Development Tools (JDT), Plugin Development Environment (PDE), and JFace. The tool Subcontractor is built upon an open source DBC tool, OpenJML Runtime Assertion Checking (RAC), which is a tool that verifies specifications at runtime. Subcontractor combines this DBC tool with inference rules of program logic for if-statements and loop- statements to automatically generate subcontracts for programs. When the programs, with subcontracts automatically generated and inserted by Subcontractor, are verified using OpenJML Runtime Assertion Checking (RAC), identification of errors in the code can be facilitated. 1 INTRODUCTION (University of Oldenburg, 2001), and Contracts for Java (C4J) (Bergström, 2012).