Software engineering (3rd ed.): a practitioner's approach
Software engineering (3rd ed.): a practitioner's approach
Simulating requirements gathering
SIGCSE '97 Proceedings of the twenty-eighth SIGCSE technical symposium on Computer science education
TAMODIA '04 Proceedings of the 3rd annual conference on Task models and diagrams
Agile development of secure web applications
ICWE '06 Proceedings of the 6th international conference on Web engineering
Knowledge modeling -- State of the art
Integrated Computer-Aided Engineering
Towards a framework for requirement change management in healthcare software applications
Companion to the 22nd ACM SIGPLAN conference on Object-oriented programming systems and applications companion
| Hi-index | 0.02 |
Requirement management is the most important as well as most neglected area of Software Engineering and Project management. 80% projects get fail due to poor requirement gathering and tracking follow ups. In Process models which are being followed in Software Development requirement gathering process is considered a task. Web development having fast iterations and quick releases mostly follows agile model. The pace and principles of agile development do not allow developers to maintain a proper set of requirement documentation. As per agile manifesto client and developers being in face to face communication minimizes the need of client requirement documentation. The focus is totally on the development and delivery to client in minimum time period. So documentation importance has not been realized in this scenario. But case is different in distributed agile based development, where development resources and client are globally at different locations without any direct and face to face communication. Thus there arises the need of maintaining minimum documentation related to client requirement and tracking to meet and fulfill the client requirements. Proper documentation helps developers to keep track of the client requirements so that they could not miss even a minor task. Therefore, light weight process needs to be introduced so that developers could follow the process of requirement gathering and tracking without putting extra time and effort during their fast paced development. A light weight process for requirement gathering and tracking in distributed agile development is proposed in this research. The process proposed requires minimum resources and very small documentation besides the actual development process. This process improves the client's satisfaction and performance of the developers. It also bridges the communication gap between client and developers.