Abstract
New trends in software development, such as agile software development, have a difficulty in conventional document-based management. Executable software has a higher priority than development documents such as detail design documents and formal bug reports. If managers depend on development reports in order to determine the project progress and the product quality, they will miss the opportunity of determining the progress and quality in agile software development. Therefore, we proposed a project reliability growth model for determining the project state without development documents. This model is based on conventional software reliability growth models. The parameters related to bugs are replaced with communication topic parameters. The concept and procedure of the model are the same as those of the software reliability growth model. By applying this model to open source projects, it is possible to detect a significant change in the project state without development documents.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: International Journal of Software Engineering and Knowledge Engineering
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
