Abstract
Requirement engineering in any software development is the most important phase to ensure the success or failure of software. Knowledge modeling and management are helping tools to learn the software organizations. The traditional Requirements engineering practices are based upon the interaction of stakeholders which causes iteratively changes in requirements and difficulties in communication and understanding problem domain etc. So, to resolve such issues we use knowledge based techniques to support the RE practices as well as software development process. Our technique is based on two prospective, theoretical and practical implementations. In this paper, we described the need of knowledge management in software engineering and then proposed a model based on knowledge management to support the software development process. To verify our results, we used controlled experiment approach. We have implemented our model, and verify results by using and without using proposed knowledge based RE process. Our resultant proposed model can save the overall cost and time of requirement engineering process as well as software development.
Highlights
IntroductionRequirement Engineering Software requirement engineering involves requirements elicitation, requirements specification, requirements validation and requirements management [1] [2]
In our implementation phase we suggest one student group member to make knowledge model of the police station system, he/she will store the knowledge in their particular database in form of textual or descriptive data as well as in form of UML diagrams
This paper is about presenting a knowledge based model to support the software requirement engineering phase which will definitely be a supportive material or supportive product for a complete software development methodology
Summary
Requirement Engineering Software requirement engineering involves requirements elicitation, requirements specification, requirements validation and requirements management [1] [2]. Requirements elicitation involves the ways of gathering the. How to cite this paper: Humayoun, M. and Qazi, A.M. (2015) Towards Knowledge Management in RE Practices to Support Software Development. M. Qazi requirements which include many traditional, cognitive, model based etc. Specifications can be formal as well as non-formal [3]. There are many and many techniques in both types of specification. Like in formal techniques of specifications, we have different formal specification languages like Z, VDM etc. In In-formal or non-formal techniques, we have UML diagrams which include use-cases, sequence diagrams, collaboration and interaction diagrams etc Like in formal techniques of specifications, we have different formal specification languages like Z, VDM etc. and in In-formal or non-formal techniques, we have UML diagrams which include use-cases, sequence diagrams, collaboration and interaction diagrams etc
Sign-in/Register to view highlights & summary 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 callDisclaimer: 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.
