{"title":"工作流:定义、设计和构建一个编程过程和版本控制系统。第一部分:历史和背景","authors":"G. Silva","doi":"10.1179/175709208X334605","DOIUrl":null,"url":null,"abstract":"Abstract There are a number of papers discussing the need for version control in the development of programs in the pharmaceutical industry. From simple CVS or RCS command line interfaces to the more complex and graphical tools like Rational Rose, programmers are told: there is a system out there to version your software, so do it! This is an important step in software development, but it is not the ‘be all end all’ for programmers. Since the industry insists on a review (Quality Control or ‘QC’) step to ensure that the specifications of the statisticians are met by the code of the programmers, it makes sense to have that same system allow for the ‘flow’ of validated code from the programmer to the statistician to the production version of the code. This paper discusses the process that was originally used until the company purchased a version control system in 2001– a paper-based system – and the evolution of our workflow from this paper-based system, through a commercial application and into an internal...","PeriodicalId":253012,"journal":{"name":"Pharmaceutical Programming","volume":"23 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2008-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Workflow: defining, designing and building a programming process and version control system. Part I – history and background\",\"authors\":\"G. Silva\",\"doi\":\"10.1179/175709208X334605\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Abstract There are a number of papers discussing the need for version control in the development of programs in the pharmaceutical industry. From simple CVS or RCS command line interfaces to the more complex and graphical tools like Rational Rose, programmers are told: there is a system out there to version your software, so do it! This is an important step in software development, but it is not the ‘be all end all’ for programmers. Since the industry insists on a review (Quality Control or ‘QC’) step to ensure that the specifications of the statisticians are met by the code of the programmers, it makes sense to have that same system allow for the ‘flow’ of validated code from the programmer to the statistician to the production version of the code. This paper discusses the process that was originally used until the company purchased a version control system in 2001– a paper-based system – and the evolution of our workflow from this paper-based system, through a commercial application and into an internal...\",\"PeriodicalId\":253012,\"journal\":{\"name\":\"Pharmaceutical Programming\",\"volume\":\"23 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2008-08-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Pharmaceutical Programming\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1179/175709208X334605\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Pharmaceutical Programming","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1179/175709208X334605","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Workflow: defining, designing and building a programming process and version control system. Part I – history and background
Abstract There are a number of papers discussing the need for version control in the development of programs in the pharmaceutical industry. From simple CVS or RCS command line interfaces to the more complex and graphical tools like Rational Rose, programmers are told: there is a system out there to version your software, so do it! This is an important step in software development, but it is not the ‘be all end all’ for programmers. Since the industry insists on a review (Quality Control or ‘QC’) step to ensure that the specifications of the statisticians are met by the code of the programmers, it makes sense to have that same system allow for the ‘flow’ of validated code from the programmer to the statistician to the production version of the code. This paper discusses the process that was originally used until the company purchased a version control system in 2001– a paper-based system – and the evolution of our workflow from this paper-based system, through a commercial application and into an internal...