In Requirement Engineering Introspection is an software Requirement Elicitation Technique. This tutorial Will provide you information on following topics. 1.Requirement Engineering 2. Requirement Elicitation 3. Requirement Elicitation Techniques 4. Introspection 5. When it is Appropriate 6. Effective 7. Pros and Cons 8. Conclusion

2. INTROSPECTION
REQUIREMENT ELICITATION TECHNIQUE
FAHAD FAROOQ

3. CONTENTS
• Requirement Engineering
• Requirement Elicitation
• Requirement Elicitation Techniques
• Introspection
• When it is Appropriate
• Effective
• Pros and Cons
• Conclusion

4. REQUIREMENT ENGINEERING
• Requirement Engineering is the process of determining user
expectation for new or modified product.
• These features called requirements, must be quantifiable,
relevant and detailed.
• Requirement Engineering activities may include Requirement inception,
Requirements Analysis, System modeling, Requirements Specification,
Requirements Validation and Requirements Management.

5. REQUIREMENT ELICITATION
• Requirement Elicitation is the practice of collecting the requirements of a system
from users, customers and other stakeholders.
• Before requirements can be analyzed, modeled, or specified they must be
gathered through an elicitation process.
• Requirements elicitation is non-trivial because you can never be sure you get all
requirements from the user and customer by just asking them what the system
should do or not do.

6. REQUIREMENT ELICITATION TECHNIQUES
• Interviews
• Questionnaires
• User observation
• Workshops
• Brainstorming
• Use cases
• Prototyping
• Introspection
• Background Reading
• Social Analysis
• Survey
• Joint Application Development
• Scenarios
• View points

7. INTROSPECTION
• In Introspection technique Requirements analyst “imagines” what
kind of system is required for doing the required job, or by using
available equipment etc.
• Introspection is the first and the most obvious method
for trying to understand what properties a system
should have in order to succeed.

8. • Introspection is observing one’s own thoughts and inner self.
Analysts work for what they imagine and observe by themselves
how a system design should be.
• . Despite being employed by most analysts to some extent, this technique
is mainly used only as a starting point for other requirements
elicitation efforts.

9. WHEN IS IT APPROPRIATE
• when users are not available, don’t want to answer your questions or shows lack
of feedback or input then Requirement Engineer’s can use this technique to
imagine the things which he assumes that the user would require.

10. • In cases where the analyst is forced to use this technique more, for example when
the users have little or no previous experience with software systems in their work
environment, a type of facilitation introspection should take place.
• This method can be very useful, but the problem is that users and experts being
from different fields and the introspection of one doesn’t reflect the
understanding of the other.

11. EFFECTIVE
• Introspection is only really effective when the analyst is not
only very familiar with the domain and goals of the system,
but also expert in the business processes performed by the users.
• This technique is effective with users who have a lot of experience
of their own fields but have less knowledge about the other
fields as well as the new system.

12. PROS AND CONS
Pros:
• Introspection is an easier technique to apply.
• There are almost no costs for implementing this technique.
• It can act as a good initial step to start requirements elicitation.

13. Cons:
• It is hard for analysts to imagine the environment in which
the new system works.
• It doesn’t allow discussion with stakeholders and other experts.
Therefore, it is not encouraged if not used in combination with other techniques.
• Analysts and stakeholders need to be well known about the domain.

14. • Introspection can be very inaccurate at times because
Requirement Analyst imagines what is required rather
than asking from the user what he requires.
• This technique is unlikely to reflect the stakeholder’s goals and
actual user experiences.

15. CONCLUSIONS
Introspection is a requirement elicitation technique from which
analysts can gather requirements.
Analysts can imagine the need and wish of customer to complete the
production of system if customer is not able to tell requirements.

16. Thank
you