latest tools and techniques of requirment elicitation


Published on

its about the requirement elicitation techniques ..... in software engineering
its about the research paper

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • You cannot test in quality. However, testing is an important part of achieving quality. Testing can expose poor designs as well as finding bugs.
    V&V is more than just testing.
    It includes the process by which tests are designed
    It includes the signoff process by which test failures are certified to have been resolved.
    It includes the reporting structure of concerns and problems to upper management without endangering the career of the person reporting the problem. This latter requires some form of independent reporting channels.
    It includes concern the funding of the V&V activity. Project managers should not be able to cut V&V funding to get product out sooner.
    Possible homework problem: Suppose you are manager of a large software project. Your budget is $1 million over budget and that the V&V budget is $4 million. What do you do?
    Testers should be independent of builders -- builders have both a vested interest and may have a built in limited perspective.
    Test group must be closely related to project, though, to understand it.
    V&V group may follow project and evaluate processes as it goes.
  • latest tools and techniques of requirment elicitation

    1. 1. 1
    2. 2. OU GR 13 P# BY:ORK MW TEA P KIAN SD RO U SG 2
    3. 3. PICS TO introduction Explanation Merits & demerits conclusion 3
    4. 4. Discussion points 4
    5. 5. Discussion points 5
    6. 6. Discussion points Definition  factors making R.E difficult  6
    7. 7. Discussion points 7
    8. 8. Discussion points Elicitation requirements Traditional techniques Modeling and analysis requirement Technique s Agreeing &communicating requirement Requirement management Evolving requirements Contextual & personal techniques Innovative techniques Feedback techniqu es 8
    9. 9. Discussion points 9
    10. 10. Discussion points Research methods &metho d ol og i e s Evolutio n of empirica l researc h 10
    11. 11. Discussion points 11
    12. 12. Discussion points globalization Scale  dynamicity Requirement re use . .  12
    13. 13. Discussion points 13
    14. 14.  To discuss about latest development in RE . 14
    15. 15. Introduction SE , the subject of large volume. plays significant role in SDLC. Requirement means any thing you want to get Engeenring means to design and build something like machines etc. RE , a process, identifying a goal and evaluate the needs of stake holders 15
    16. 16. Introduction Requirement engineering activities differs from other software. engineering activities as they are concerned with identifying the problem how the environment will be affected by the proposed system other activities are concerned with the solution of the problem and the behavior of the system under these requirements. Furthermore, different factors 16
    17. 17. INTRODUCTION........... Factors create difficulties in RE nts me e e uir fin q Re t de y no learl c An a con lysis Req uir flict em ent s Maintaining integrity and consistency among already set and new requirements d os e p im n t s int nme tify a str viro iden t n Co y en and men b in n a iro v m do ar en cle Requirement statements not understood by stakeholders and experts 17
    18. 18. Introduction........ ❶ we evaluate the techniques of development of RE by a road map designed by Nuseibeh and Easterbrook. elicitation modeling and analysis agreeing and communicating requirements Evolving requirements Current trends resolu tion and activities in RE 18
    19. 19. Introduction  Latest development in RE techniques ❸ Research methods and empirical research in RE ❹ Observation during this research. 19
    20. 20. • The main work of RE is concerned with static elicitation, representation, and analysis of requirements. • One of the remarkable works on this field was carried out by Berry et al. [36]. They suggested four levels of RE activities needed to support adaptive systems. 20
    21. 21. 1. Level one, associated with human and related to activities associated with elicitation and analysis of requirements. 2. Level two, associated with the system when it is running and its ability to adapt according to various inputs and behaviors. 21
    22. 22. 3. Level three, associated with human and related to the previous level by determining the adaption elements of the adaptive system. 4. Level four, also done by human and associated with the general understanding systems and events. 22
    23. 23. Techniques and activities Notations Roles Context Results Tools 23
    24. 24. 1. Requirement engineering field is very huge, the need to have some sort of centralized repository or index to the work in this field can help researchers utilize research time in evaluating work and find solutions. 24
    25. 25. • • The gap between researchers and practitioners should be minimized. collaborative efforts between them will help researchers obtain a better understanding of problems and challenges. 25
    26. 26. • Lots of solutions and models have been developed addressing specific contexts and scenarios, sharing this knowledge through standardized channels… 26
    27. 27. • More attention should be given to evaluationbased and empirical research Gradual process Veriy .based on experience $ observation 27
    28. 28. • In conclusion, requirements engineering facing successive changes. • affecting it and making it susceptible to change all the time. Capbal $ admitting 28
    29. 29. THE END 29
    30. 30. Merits  Elicitation techniques are really helpful for collection rich information about the requirements.  The observational methods provide vital information for designing solution.  R.E used some techniques that are really helpful for collection rich information about the requirements.  R.E techniques bring certainty in the requirement 30
    31. 31. Demerits Time consuming. A small mistake or fact ignorance in analysis gives a great error.  User cant b explain there ideas due to lake of knowledge .  Difference of knowledge between user and analyst. 31