Call for Paper

CAE solicits original research papers for the July 2021 Edition. Last date of manuscript submission is June 30, 2021.

Read More

Requirements Engineering: A Survey

Vivek Shukla, Dhirendra Pandey, Raj Shree. Published in System Architecture.

Communications on Applied Electronics
Year of Publication: 2015
Publisher: Foundation of Computer Science (FCS), NY, USA
Authors: Vivek Shukla, Dhirendra Pandey, Raj Shree
10.5120/cae2015651947

Vivek Shukla, Dhirendra Pandey and Raj Shree. Article: Requirements Engineering: A Survey. Communications on Applied Electronics 3(5):28-31, November 2015. Published by Foundation of Computer Science (FCS), NY, USA. BibTeX

@article{key:article,
	author = {Vivek Shukla and Dhirendra Pandey and Raj Shree},
	title = {Article: Requirements Engineering: A Survey},
	journal = {Communications on Applied Electronics},
	year = {2015},
	volume = {3},
	number = {5},
	pages = {28-31},
	month = {November},
	note = {Published by Foundation of Computer Science (FCS), NY, USA}
}

Abstract

Software development process is the collection of a variety of phases. Requirement engineering is one of phases that involve in software development processes. From all the phases, Requirement Engineering phase play an important role for every software product. During requirement engineering phase, development team interacts with representative of stakeholders and uses these requirements to build up software product that satisfy the stakeholder’s needs. After collecting all the requirements, these requirements can be divided into two categories. First category will take requirements those are important and necessary for software development at present time while the other category take requirements those are not important for the software product at present but can be important in future. The motive of requirement engineering is to find out exact requirement of the stakeholders with the help of step by step predefined procedure. Collected requirements can be first verified by stakeholders. At last, stakeholder and developer team sign contract. It cannot be concluded that requirement engineering phase completed at the beginning of the product development but incorporates parts of next phase of software engineering. In this paper, researcher tries to give basic information about software requirement engineering phase and present why requirement engineering is important for software development?

References

  1. Zave, P. (1997). Classification of Research Efforts in Requirements Engineering. ACM Computing Surveys, 29(4): 315-321.
  2. Phillip A. Laplante . 2014. Requirements Engineering for Software and Systems, Second Edition. CRC press, Taylor & Francis Group. An Auerbach Book. ISBN978-1-4665-6082-6
  3. Philip A. Laplante. 2007. What Every Engineer Should Know about Software Engineering. Press, Taylor & Francis Group. An Auerbach Book. ISBN978-0-8493-7228-5.
  4. Billy Hendrawan. 1601215765. 34PFT. Chapter 5. http://billyhendrawan.blog.binusian.org/files/2014/03/Chapter-5.docx.
  5. Roger S. Pressman. 2005. Software Engineering: A Practitioner's Approach. Sixth edition, tata Mc Graw Hill Higher Education, 2005, ISBN 0-07-285318-2.
  6. Davey, B. & Cope, C., 2008. Requirements Elicitation – What’s missing? Issues in Informing Science and Information Technology, 5(1), p.53-57.
  7. B. W. Boehm, R. Valerdi 2005. Achievements and Challenges in Software Resource Estimation. USC CSSE Technical Report. No.USC-CSE-2005-513. http://sunset.usc.edu/csse/TECHRPTS/2005/usccse2005-513/usccse2005-513.pdf.
  8. Del Gobbo, D., Napolitano, M., Callahan, J. & Cukic, B. 1998. Experience in Developing System Requirements Specification for a Sensor Failure Detection and Identification Scheme. 3rd High- Assurance Systems Engineering Symposium, Washington, DC, USA, 13-14 November 1998.
  9. Standish, G.. 1995. CHAOS.
  10. A Framework for Software Product Line Practice, Version 5.0. http://www.sei.cmu.edu/productlines/frame_report/req_een.htm.
  11. Kathy Schwalbe. 2014. Information Technology Project Management. ISBN978-1-285-84709-2.
  12. Brusa, G., Caliusco, M.L., Chiotti, O.. 2008. towards ontological engineering: a process for building a domain ontology from scratch in public administration. Expert Systems: The Journal of Knowledge Engineering. 25(5). 484-503.
  13. Michael Middleton, Len Asprey. 2011. Integrative Document and Content Management: Strategies for Exploiting Enterprise Knowledge: Systems for Exploiting Enterprise Knowledge. Idea Group Publishing, USA. ISBN1-59140-068-6.
  14. Business Requirements. Wikipedia, the free encyclopedia. https://en.wikipedia.org/wiki/Business_requirements.
  15. John Parker. 2012. Business, User and System Requirementshttp://requirements101.com/Powering_Requirements_Success/bid/123830/Business-User-and-System-Requirements.
  16. John Parker. 2012. Business Requirements vs. Functional Requirements. http://enfocussolutions.com/business-requirements-vs-functional-requirements/.
  17. Kris Slaboszewski. 2013. Requirement Type Defined. http://community.rightpoint.com/blogs/viewpoint/archive/2013/08/08/requirement-types-defined.aspx.
  18. P. Loucopoulos and V. Karakostas. Chapter 2. System Requirements Engineering. McGraw-Hill. http://www.utdallas.edu/~chung/SYSM6309/RE_chapters/Chapter%202.pdf.
  19. Software Verification and Validation. Wikipedia, the free encyclopedia. https://en.wikipedia.org/wiki/Software_verification_and_validation.
  20. Requirements Management. Wikipedia, the free encyclopedia. https://en.wikipedia.org/wiki/Requirements_management

Keywords

Requirement engineering, types of requirements, requirement engineering framework.