A B C D E F G H I J K L M N O P Q R S T U V W X Y Z All
Srivastava, Smita
- Status of Family Lophoziaceae (Hepaticae) in India
Authors
1 Department of Botany, University of Lucknow, Lucknow, IN
2 CSIR National Botanical Research Institute, Rana Pratap Marg, Lucknow, IN
Source
Nelumbo - The Bulletin of the Botanical Survey of India, Vol 55 (2013), Pagination: 113-152Abstract
Status of family Lophoziaceae in India has been discussed in the light of recent investigations and our own observations on Indian taxa. A total of 19 taxa have been recognised under eight genera including Isopaches Buch., Lophozia (Dumort.) Dumort., Schistochilopsis (N. Kitag.) Konstant., Anastrepta (Lindb.) Schiffn., Anastrophyllum (Spruce) Schiffn., Tritomaria Schiffn. ex Loeske, Tetralophozia (R.M. Schust.) Schljakov and Plicanthus R.M. Schust. Four taxa viz., Anastrophyllum minutum var. himalayanum var. nov., Lophozia udarii sp. nov., Lophozia indica sp. nov. and Schistochilopsis incisa var. himalayana var. nov., have been described as new to science. Sphenolobus longkyrdumii A.P. Singh&V. Nath is proposed as synonym under Metahygrobiella albula (Mitt.) Grolle (family Cephaloziaceae Mig.), hence excluded.Keywords
Morpho-Taxonomy, Liverworts, Lophoziaceae.- TSP (Team Software Process)
Authors
Source
International Journal of Innovative Research and Development, Vol 2, No 5 (2013), Pagination:Abstract
As quoted by the CIO journal December 2003 issue, “By the numbers available, the software quality stinks.” The Standish Group reported in 1999 that 74% of all projects were not successful.
According to a survey by Standish Group in 2002, only 34 % of the software development is successful. Around 38 billion US dollars are lost every annum due to software failure and one of the major reasons for this high failure rate is poor software quality. Typical software projects are often late, over budget, of poor quality, and difficult to track. Engineers often have unrealistic schedules dictated to them and are kept in the dark as to the business objectives and customer needs. They are required to use imposed processes, tools, and standards, and often take shortcuts to meet schedule pressures. Very few teams can consistently be successful in this environment. As software systems get larger and more complex, these problems only get worse. The best projects are an artful balance of conflicting forces. To balance these conflicting forces, teams must understand the complete context for their projects.