You are on page 1of 8

Advance Software Engineering Paper Review Assignment 1 MSCS-17

Group: 1 Paper title:Requirements Engineering: A Roadmap

Bashar Nuseibeh, Steve Easterbrook.

Submission date:October 11, 2010.

It further suggests to follow an integrated RE approach to manage multidisciplinary RE activities. the paper focuses on how to carry out software requirements engineering effectively. The paper presents current research activities in different areas of RE and it also carries out a survey of the RE research in 90s. At the end a roadmap for integrated RE process has been suggested and certain research issues have also been highlighted in RE for the upcoming decade.PART . through which real world goals of the system are determined and precise specifications are documented.I Executive Summary The paper at hand presents an overview of the field of Software System Requirements Engineering (RE) which is regarded as a multidisciplinary. modeling and analysis. Problem Statement The paper identifies a problem about the ineffective requirements engineering approach towards delivered software systems which results in unfulfilled customers’ requirements. to ensure the success of software projects? Solution Approach The paper tries to develop a good understanding of RE field and its key areas in order to make the RE process easier to be followed. which ultimately affect the success of software projects. and evolving requirements-. the paper suggests improvements in the field of RE and provides with an ample roadmap to the future research for an integrated RE process. It discusses the core requirement engineering activities--namely: elicitation. human-centered process. . In detail. communicating the requirements. Moreover. and the most critical activity of software system. agreeing upon requirements.

The paper presents a road map based on very comprehensive study and analysis of the related literature published in from 1990 till 2000. Moreover. have presented their candid analysis of the referenced literature while citing in the paper. The results obtained are based on thorough analysis by authors and on voluminous relevant literature. being based on literature published in 90s the research and approach may have been further refined. The authors. The subject has been aptly explained from basics till most advanced topics of the field. It would have been even better to discuss the RE core activities with the help of specific examples to enhance the understandability. These . in sections 4-8 of the paper were little hard to understand. The language used is mostly simple and each new concept has been appropriately explained. However. Results: RE is an important software process activity and the proper use of the techniques and models will ensure the success of the software projects. Evaluation Approach: The paper presents an extensive review of the relevant research. they have supported their point of view by citing work from different authors which indicate carefulness and genuineness of the research. The suggested approach is likely to address the daunting challenges impeding this field of crucial importance. The open research challenges in the field have been identified which can form basis for future research. sites etc). The paper contains 84 reference papers/sites for further study. Quality of Related Work: The paper presents a very comprehensive review of the related research. In addition. The sections are adequate linked to previous section thus maintaining continuity. However. most of the times. Every new concept has been cited from references which total to 84 (articles.

Some probable typos were also encountered in the paper. .sections may require deeper background knowledge.

b. cites texts from numerous references. advanced topics and open research challenges for the field. Readers can consult those for clarity of concepts. Requirements elicitation techniques discussed with their practical applications. Simple presentation. Readers can be successfully convinced about the importance of this Requirements Engineering. e. Seen with respect to the course work. Weaknesses . The research is done thoroughly considering each aspect of requirements engineering. It can act as jump starter for a new comer and direct him to the most advanced level. It covers the basics. General categories of RE modeling approaches are discussed along with examples. f. Covers the basics and the most advanced topics both including open research challenges.Significance: The paper provides an extensive introduction and review research of a very crucial field of software engineering. it is cent percent relevant. Well research. g. c. Comprehensiveness. d. PART – II Strengths a.

The understanding of section 4-8 may require background knowledge. techniques presented might have already refined. d. The integration approach of different activities is not discussed in detail.a. Based on relatively early research spanning from 1990 till 2000. b. c. Few probable typos were encountered. More detailed description would have facilitated the understanding. .

Contextual techniques. RAD/JAD workshops (Section 4. d. In Section 6. which can improve quality of the requirements documentations. .Summery As Per Our Understanding: RE is an extremely crucial field of software engineering which determines the real-world goals of a software system on which the success of the whole system is gauged. Agreeing requirements. Laddering. e.2) require more elaboration. it is written: “Kovitz suggests some heuristics for focusing on small details of writing requirements documentation. Modeling and analyzing requirements. b. Section 5 not fully understood. It has presented a thorough review of the current research in the filed of RE along with basics.2) require more detail. The field deserves more emphases. namely. Eliciting requirements. f.4). RE is multidisciplinary process that requires different skills for a practitioner. Goal-based methods and Scenario based methods (Section 4. Final words about the paper: The paper is comprehensive and can serve as quick starter for a new comer to the filed of RE. To fulfill the needs of the stakeholders in order to build a successful software product. Terms / Areas not understood: a. Communicating requirements. card sorting. but still need further advancement. Tractable reasoning over a closed world model of the system (Section 5. and Evolving requirements. The RE process comprises of main activities. The RE field evolved in early 90s as an active research area. the traditional techniques used for RE have undergone significant evolution. c. property grid (Section 4. The RE filed has still has a long way to go.” We can’t get an idea/detail of heuristics from this because authors have neither written any detail nor given any reference.2). regardless of the format in which requirements are expressed.