Course Name      : Software Requirement Engineering  Course Code       : TDB4313/ TEB3413   Overview  Software development processes consist of several phases; requirement specification, analysis and design, implementation (code), testing, and Deployment

Course Name      : Software Requirement Engineering 

Course Code       : TDB4313/ TEB3413  

Overview 

Software development processes consist of several phases; requirement specification, analysis and design, implementation (code), testing, and Deployment. The requirement specification activity is the one also known as requirement engineering. requirement engineering is defined by Wiegers as “The domain that encompasses all project life cycle activities associated with understanding a product’s necessary capabilities and attributes. Includes requirements development and requirements management. A sub discipline of system engineering and software engineering”. Generally, requirements engineering plays a major role in the development of software and it has direct impact on the overall success of software projects and systems. However, the research studies stated that inappropriate requirements engineering is one of the most importance reasons for project failures.

Objectives

The objective of this assignment is to expose students (1) to explore the current practices of requirements engineering amongst  IT Small and Medium enterprises (SMEs) or Large enterprise , (2) to investigate the requirements engineering processes and how they implement them during software development, (3) to list and categorize all requirements engineering problems faced by IT company  either Small and Medium enterprises (SMEs) or  Large enterprise, (4) to explore the requirement engineering techniques used by them.

Your  Task

Assignment 1 (40 marks)

You are required to identified 10 quality research papers ( from 2012-2020) from journal or  conferences paper,  summaries all the findings from all the papers and  document all the findings. 

Assignment 2 ( 60 marks)

You are required to do a systematic literature review for 10 quality research papers for to identify, evaluate and interpret all available research relevant to fulfill the aforementioned objectives. 

A systematic literature review involves into three main phases and each phase has several discrete activities.

1. Planning the review 
   1. Identification of the need for a review: 
   2. Identification of the need for a review 
   3. Specifying the research question(s) 
   4. Developing a review protocol 
   5. Evaluating the review protocol
2. Conducting the review  A. Identification of research 
   2. Selection of primary studies 
   3. Study quality assessment
   4. Data extraction and monitoring 
   5. Data synthesis 
3. Reporting the review 
   1. Specifying dissemination mechanisms
   2. Formatting the main report
   3. Evaluating the report

Important notes:

1. 1. Each group students are required to submit their report based on IEEE format paper. 
   2. Similarity check report are also required to submit through TURNITIN. if the final percentage similarity is equal or greater than 30%, then the group student will be considered to have failed and will be given "0" grade for their assignment. TURNITIN account will be provided for each group soon
   3. Both documents ( paper and Turn it in report) must submit online and hard copy.  

Important References:

Keele, S. (2007). Guidelines for performing systematic literature reviews in software engineering. In Technical report, Ver. 2.3 EBSE Technical Report. EBSE. sn.