International Institute of Business Analysis | Home
Click the above heading to visit: http://www.theiiba.org
IIBA® is the independent non-profit professional association serving the growing field of Business Analysis. Whatever your role—requirements management, systems analysis, business analysis, requirements analysis, project management, or consulting—IIBA® can help you do your job better
Wednesday, September 22, 2010
Requirements elicitation - Wikipedia, the free encyclopedia
Requirements elicitation - Wikipedia, the free encyclopedia
In requirements engineering, requirements elicitation is the practice of obtaining the requirements of a system from users, customers and other stakeholders. [1] The practice is also sometimes referred to as requirements gathering.
The term elicitation is used in books and research to raise the fact that good requirements can not just be collected from the customer, as would be indicated by the name requirements gathering. 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. Requirements elicitation practices include interviews, questionnaires, user observation, workshops, brain storming, use cases, role playing and prototyping.
Requirements elicitation is a part of the requirements engineering process, usually followed by analysis and specification of the requirements.
Before requirements can be analyzed, modeled, or specified they must be gathered through an elicitation process. The most commonly used elicitation process is to carry out meetings or interview. The first one with the software engineer and customer where they can discuss over the topics of the requirements.
In requirements engineering, requirements elicitation is the practice of obtaining the requirements of a system from users, customers and other stakeholders. [1] The practice is also sometimes referred to as requirements gathering.
The term elicitation is used in books and research to raise the fact that good requirements can not just be collected from the customer, as would be indicated by the name requirements gathering. 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. Requirements elicitation practices include interviews, questionnaires, user observation, workshops, brain storming, use cases, role playing and prototyping.
Requirements elicitation is a part of the requirements engineering process, usually followed by analysis and specification of the requirements.
Before requirements can be analyzed, modeled, or specified they must be gathered through an elicitation process. The most commonly used elicitation process is to carry out meetings or interview. The first one with the software engineer and customer where they can discuss over the topics of the requirements.
Monday, September 20, 2010
Business analyst - Wikipedia, the free encyclopedia
Business analyst - Wikipedia, the free encyclopedia
A Business Analyst (BA) analyzes the organization and design of businesses, government departments, and non-profit organizations; BAs also assess business models and their integration with technology.
There are at least four tiers of business analysis:
1.Planning Strategically - The analysis of the organization's strategic business needs
2.Operating/Business Model Analysis - The definition and analysis of the organization's policies and market business approaches
3.Process Definition and Design - The business process modeling (often developed through process modeling and design)
4.IT/Technical Business Analysis - The interpretation of business rules and requirements for technical systems (generally IT)
A Business Analyst (BA) analyzes the organization and design of businesses, government departments, and non-profit organizations; BAs also assess business models and their integration with technology.
There are at least four tiers of business analysis:
1.Planning Strategically - The analysis of the organization's strategic business needs
2.Operating/Business Model Analysis - The definition and analysis of the organization's policies and market business approaches
3.Process Definition and Design - The business process modeling (often developed through process modeling and design)
4.IT/Technical Business Analysis - The interpretation of business rules and requirements for technical systems (generally IT)
Business analysis - Wikipedia, the free encyclopedia
Business analysis - Wikipedia, the free encyclopedia
Business analysis is the discipline[1] of identifying business needs and determining solutions to business problems. Solutions often include a systems development component, but may also consist of process improvement or organizational change or strategic planning and policy development. The person who carries out this task is called a business analyst or BA
Business analysis is the discipline[1] of identifying business needs and determining solutions to business problems. Solutions often include a systems development component, but may also consist of process improvement or organizational change or strategic planning and policy development. The person who carries out this task is called a business analyst or BA
Subscribe to:
Posts (Atom)