Siddiqi J, Shekaran MC (1996) Requirements engineering: the emerging wisdom. IEEE Software 9:15--19 Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
A Low Cost Front End to a Legacy Data System Through the .. - Carr Software.. (1998) (Correct)
....support is required by each group 4. What technical considerations need to be borne in mind in the choice of the tool 5. What the future information needs of the organisation and user groups are The framework as proposed in figure 3 deals with the requirements phase as proposed by Krasner [Siddiqi, 1996], encompassing such issues as need identification, problem analysis, requirements determination and requirements specification. The problem analysis phase as proposed by Davis is also included and deals with issues surrounding the knowledge about the problem, discoveries about the end user and ....
....problem analysis, requirements determination and requirements specification. The problem analysis phase as proposed by Davis is also included and deals with issues surrounding the knowledge about the problem, discoveries about the end user and constraints of the solution [Davis, 1990] [Siddiqi, 1996]. Figure 3. Phases in functional specification and identification of requirements for front end GUI tool 3.2 Factors to be considered There are many factors influencing the use of such a tool in an enterprise. These need to be looked at from both a management perspective and a user view point. ....
, Siddiqi J., Shekaran M.C., Requirements Engineering: The emerging wisdom, IEEE Software, Volume 13, pg 15-19, March 1996
Controlling Requirements Evolution An Avionics Case Study - Anderson, Felici (2000) (1 citation) (Correct)
....specification, testing activities, source code, etc. Even small software projects require subsequent releases in order to fulfil changing user expectation and environmental constraints. Researchers and practitioners in Software Engineering have recognised the important role of requirements [2, 3, 16] leading to the development of the field of Requirements Engineering [18, 20] Recent research [14] in Requirements Engineering identifies the origins of requirements change in the development environment. Changing requirements are classified according to five types, which are related to the ....
J. Siddiqi and M.C. Shekaran. Requirements engineering: The emerging wisdom. IEEE Software, pages 15--19, March 1996.
Requirements Changes Risk/Cost Analyses: An Avionics Case Study - Anderson, Felici (2000) (1 citation) (Correct)
....software life cycle, impact of changes and structure of requirements. The results suggest further works dealing with requirements evolution. 1 INTRODUCTION Requirements specification is one of the most important phases of the software life cycle (Berry Lawrence 1998; Davis Hsia 1994; Siddiqi Shekaran 1996; Sommerville Sawyer 1997a) The recovery activity is more cost effective during the requirements specification phase than subsequent phases (i.e. design specification, coding, testing, etc. Boehm 1981; Boehm 1984) Recent research has pointed out interesting aspects of changing requirements ....
....business targets, etc. Requirements are interdependent on one another. Current methods in requirements engineering emphasise the need for the management and representation of multi perspectives and evolving requirements (Nuseibeh, Kramer, Finkelstein 1994; Sawyer, Sommerville, Viller 1997; Siddiqi Shekaran 1996; Sommerville Sawyer 1997b; Sommerville Sawyer 1997a) From the requirements process viewpoint there is actually the need for providing tools which help in the management of the process with predictive features. Recent research in requirements engineering (PROTEUS Project 1996) has identified ....
Siddiqi, J. & Shekaran, M. (1996, March). Requirements engineering: The emerging wisdom. IEEE Software, 15-- 19.
Criteria Used for the Evaluation of Software System.. - Haywood, Dart (1996) (Correct)
....Many applications expect a SRS to be produced that does not include any design or implementation directives, so a model which is independent of design would be necessary. However, this view is not universally held, Siddiqi and Shekaran remind us that requirements and design are interdependent [SS96] 8. How easy is it to apply the model easily used by non experts requires significant expertise a b c d e This is a more subjective criterion and should be treated with caution. We did not attempt to apply the model, but made a value judgement as to how easy it would ....
Jawed Siddiqi and M. Chandra Shekaran. Requirements Engineering: The Emerging Wisdom. IEEE Software, pages 15--19, March 1996.
Original Article - Berry Daudjee Dong (Correct)
No context found.
Siddiqi J, Shekaran MC (1996) Requirements engineering: the emerging wisdom. IEEE Software 9:15--19
Observational Models of Requirements Evolution - Felici (2004) (Correct)
No context found.
Siddiqi, J. and Shekaran, M. (1996). Requirements engineering: The emerging wisdom. IEEE Software, pages 15--19.
A Formal Framework for Requirements Evolution - Felici (2003) (Correct)
No context found.
J. Siddiqi and M.C. Shekaran. Requirements engineering: The emerging wisdom. IEEE Software, pages 15--19, March 1996.
Requirements Engineering and Technology Transfer: Obstacles.. - Kaindl, al. (2002) (Correct)
No context found.
Siddiqi J, Shekran M. Requirements engineering: the emerging wisdom. IEEE Software 1996;March/April:15--19
Linking the Selection of Requirements to Market Value: - Portfolio-Based Approach Siv (2001) (Correct)
No context found.
Siddiqi, J. & Shekaran, C. (1996). Requirements Engineering: The Emerging Wisdom. IEEE Software(March): 15-19.
Management View on Current Requirements Engineering.. - Nikula, Sajaniemi.. (2000) (Correct)
No context found.
Siddiqi, Jawed and Chandra M. Shekaran (1996), Requirements Engineering: The Emerging Wisdom, IEEE Software, Vol. 13, No. 2, pp. 15-19.
The Role of Emotion, Values, and Beliefs in - The Construction Of (Correct)
No context found.
Siddiqi, J., Shekaran, M.C.: Requirements Engineering: The Emerging Wisdom. IEEE Software 9:2 (March 1996) 15--19
An Evaluation of Methods for Prioritizing Software.. - Karlsson, Wohlin, Regnell (1998) (2 citations) (Correct)
No context found.
J. Siddiqi, M.C. Shekaran, Requirements engineering: the emerging wisdom, IEEE Software 13 (2) (1996) 15--19.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC