http://chineseinput.net/에서 pinyin(병음)방식으로 중국어를 변환할 수 있습니다.
변환된 중국어를 복사하여 사용하시면 됩니다.
Kanth, B.K.,Jnawali, H.N.,Niraula, N.P.,Sohng, J.K. G. Fischer 2011 Microbiological research Vol.166 No.5
Two superoxide dismutase (SOD) genes; sod1 and sod2, from Streptomyces peucetius ATCC 27952 show high similarity to other known SODs from Streptomyces coelicolor A3(2) and Streptomyces avermitilis MA-4680. These sod1 and sod2 were cloned into pIBR25 expression vector under a strong ermE* promoter to enhance secondary metabolites from Streptomyces strains. The recombinant expression plasmids; pIBR25SD1 and pIBR25SD2, were constructed to overexpress sod1 and sod2 respectively to enhance production of doxorubicin (DXR) in S. peucetius, clavulanic acid (CA) in Streptomyces clavuligerus NRRL 3585 and actinorhodin (ACT) and undecylprodigiosin (Red) in Streptomyces lividans TK24. Biomass variation, antibiotics production and transcriptional analysis of regulatory genes in recombinant strains have been studied to understand the effect of sod1 and sod2. The cell growth analysis shows that life span of all recombinant strains was found to be elevated as compared to wild type cells. In S. peucetius, overexpression of sod1 and sod2 was not effective in DXR production but in case of S. clavuligerus, CA production was increased by 2.5 and 1.5 times in sod1 and sod2 overexpression, respectively while in case of S. lividans, ACT production was increased by 1.4 and 1.6 times and Red production by 1.5 and 1.2 times upon sod1 and sod2 overexpressions, respectively as compared to the corresponding wild type strains.
Identification of Two Superoxide Dismutases (FeSOD and NiSOD) from Streptomyces peucetius ATCC 27952
Kanth, Bashistha Kumar,Oh, Tae-Jin,Sohng, Jae-Kyung 한국생물공학회 2010 Biotechnology and Bioprocess Engineering Vol.15 No.5
In this study, the whole genome of Streptomyces peucetius ATCC 27952 was analyzed and two superoxide dismutases (SODs), named sp-sod1 and sp-sod2, were identified. The sp-sod1 is a putative Fe-Zn sod that is 636 bp in length. The sp-sod2 is a putative NiSOD that is 396 bp in length. The deduced amino acid sequence of sp-sod1 shared approximately 85 ~ 90% identity with the iron sod of S. griseus, S. coelicolor A3(2), and S. avermitilis MA-4680 whereas sp-sod2 shared approximately 87 ~ 94% identity with S. avermitilis, S. coelicolor A3(2) and S. seoulensis. The sp-sod1 was characterized to be FeSOD in the sod mutant E. coli QC871. The N-terminal deleted sp-sod2 along with a putative signal peptidase sp-sodX, which was immediately downstream, was co-expressed in E. coli. This recombinant E. coli strain did not produce the processed mature Sp-SOD2 unlike S. coelicolor Muller. However, Sp-SOD2 was confirmed to be NiSOD in S. lividans TK24.
Suman Kumar Kanth,Sanjay Mohapatra,Debashisa Mohanty,P C Basak KINFORMS 2013 Management Review Vol.8 No.2
This paper is a practitioner’s view of impact of different parameters like Centralization, Offshoring, Productivity mprovement, Quality and other process improvement on Return on Investment calculation for a CTO (Centralized testing Organization). This analysis can help IT QA(Quality Assurance) management to quantify Return on Investment from different parameters of operation and decide on where to invest for optimum benefit. Return on Investment is one the critical factors that any large / small organization chooses before investing. At all the stages of the project life cycle, Return on Investment calculation is a must - that is at business requirements to design, development, testing and implementation phase. In today’s world, independent testing has become very important. The organization needs to do a proper due diligence on selecting testing model, process, time to market, cost etc. For these the organization needs to understand the criteria for selecting the right model for testing which gives the maximum return on investment. This study analyses different parameters and their impact on Return on Investment. This paper does not elaborate on how to establish a CTO. Rather this is an attempt to quantify results after due consideration of various focus areas like - lower cost of operation by offshoring and centralization and savings through Productivity Improvement thru Automated Test Case Execution, savings through Process and tools standardization etc. to implement different parameters within a CTO. The findings are based on authors’ experience of implementing CTOs for reputed clients and implementing that across big size portfolios. The constraints for pure development projects, product testing projects or open system projects may vary in nature. For example scope and benefit from automation may be very high for product testin projects or open system projects but not so for legacy mainframe based maintenance projects.