The Psychiatric Hospital as a Small Society by William Caudill

Standish, Christopher T.

doi:10.1080/00207284.1961.11508148

Cited by 1 publication

(2 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The results show that the most common 'high' value practice (61%) is 'obtain an understanding of requirements'. Research shows that if a system's requirements are not fully understood, it can have a huge impact on the effectiveness of the software development process for that system [13][14][15]. When requirements are poorly defined, the end result is usually a poorer product or a cancelled project [14].…”

Section: Resultsmentioning

confidence: 99%

“…Research shows that if a system's requirements are not fully understood, it can have a huge impact on the effectiveness of the software development process for that system [13][14][15]. When requirements are poorly defined, the end result is usually a poorer product or a cancelled project [14]. An industry survey in the UK reported that only 16% of software projects could be considered truly successful: "Projects are often poorly defined, codes of practice are frequently ignored and there is a woeful inability to learn from past experience" [16].…”

Section: Resultsmentioning

confidence: 99%

See 1 more Smart Citation

An Empirical Study Identifying High Perceived Value Practices of CMMI Level 2

Niazi

Babar

Ibrahim³

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

Abstract.We have conducted face-to-face questionnaire based interview sessions with twenty-three Malaysian software practitioners in order to determine the perceived value associated with the specific practices of "requirements management", "process and product quality assurance" and "configuration management" process areas of CMMI level 2 in the stage representation. The objective of this study is to identify the extent to which a CMMI practice is used in order to develop a finer-grained framework, which encompasses the notion of perceived value within specific practices. This will provide software process improvement (SPI) practitioners with some insight into designing appropriate SPI implementation strategies.We asked practitioners to choose and rank "requirements management", "process and product quality assurance" and "configuration management" practices against the five types of assessments (high, medium, low, zero or do not know). From this, we propose the notion of 'perceived value' associated with each practice. We have identified 'high' and 'medium' perceived values CMMI level 2 practices. We have also identified the viewpoints of developers and managers about these practices.

show abstract