Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

CPRE-FL Module 1: RE Intro and Competencies

214 views

Published on

This Slideshare presentation is a partial preview of the full business document. To view and download the full document, please go here:
http://flevy.com/browse/business-document/cpre-fl-module-1-re-intro-and-competencies-2556

BENEFITS OF DOCUMENT
1. Learn about CPRE-FL practices

DOCUMENT DESCRIPTION

This module deals with RE Intro and Competencies to CPRE-FL Program.

Published in: Business
  • Login to see the comments

  • Be the first to like this

CPRE-FL Module 1: RE Intro and Competencies

  1. 1. Introduction and Foundation1
  2. 2. Requirements IEEE defines requirements as: A condition or capability to be met or possessed by a solution or solution component to satisfy a contract, standard, specification, or other formally imposed documents. A condition or capability needed by a stakeholder to solve a problem or achieve an objective. A documented representation of a condition or capability. A requirement may be unstated, implied by or derived from other requirements, or directly stated, and managed. This document is a partial preview. Full document download can be found on Flevy: http://flevy.com/browse/document/cpre-fl-module-1-re-intro-and-competencies-2556
  3. 3. Symptoms of and reasons for inadequate RE A study by Tech Republic shows 68% of projects fail due to poor requirements engineering Majority of customer expectation mismatches can be attributed to poor requirements. Costs of fixing errors increase exponentially with each project phase Importance needs to be given to requirements engineering! Unclear, incomplete, or wrong requirements lead to development of wrong solutions This document is a partial preview. Full document download can be found on Flevy: http://flevy.com/browse/document/cpre-fl-module-1-re-intro-and-competencies-2556
  4. 4. Different levels of Requirements Stakeholder System Software This document is a partial preview. Full document download can be found on Flevy: http://flevy.com/browse/document/cpre-fl-module-1-re-intro-and-competencies-2556
  5. 5. Mnemonic for Skills of Requirements Engineers M – Moderation skills E – Empathy C – Communication C – Conflict resolution A – Analytical thinking S – Self-confidence A – Ability to convince MECCA is in Saudi Arabia. This document is a partial preview. Full document download can be found on Flevy: http://flevy.com/browse/document/cpre-fl-module-1-re-intro-and-competencies-2556
  6. 6. Quality requirements Quality requirements influence the system architecture more than functional requirement It must be documented explicitly Non-functional (Quality, Supplementary) requirements Aspects of quality considered are: - Performance - Security - Reliability - Usability - Maintainability - Portability, also known as - Transferability This document is a partial preview. Full document download can be found on Flevy: http://flevy.com/browse/document/cpre-fl-module-1-re-intro-and-competencies-2556
  7. 7. Let’s discuss few sample questions This document is a partial preview. Full document download can be found on Flevy: http://flevy.com/browse/document/cpre-fl-module-1-re-intro-and-competencies-2556
  8. 8. Question 2 2. Which of the following statements are true for “constraints”? True / False Statements System shall be able to capture necessary information about project risks. 1st release of the application must be completed within 3 months. Application should process any report within 15 minutes. Application development shall follow agile development approach. This document is a partial preview. Full document download can be found on Flevy: http://flevy.com/browse/document/cpre-fl-module-1-re-intro-and-competencies-2556
  9. 9. Correct Option for Question 3 True / False Statements Explanation TRUE Empathy As per guidebook, this is an essential quality. TRUE Analytic thinking As per guidebook, this is an essential quality. FALSE Public speaking As per guidebook, this is not an essential quality. TRUE Conflict resolution As per guidebook, this is an essential quality.This document is a partial preview. Full document download can be found on Flevy: http://flevy.com/browse/document/cpre-fl-module-1-re-intro-and-competencies-2556
  10. 10. Question 5 5. Among following which is objective of Elicitation? a. Gather requirements b. Document requirements c. Validate requirements d. None of the above This document is a partial preview. Full document download can be found on Flevy: http://flevy.com/browse/document/cpre-fl-module-1-re-intro-and-competencies-2556
  11. 11. Correct Option for Question 6 C and D. Promoting agile method is not an objective of requirements validation This document is a partial preview. Full document download can be found on Flevy: http://flevy.com/browse/document/cpre-fl-module-1-re-intro-and-competencies-2556
  12. 12. Question 8 8. Peter is the requirements engineer for a project and needs to identify the stakeholder that will be responsible for authorizing the actions needed in order to meet the identified business need. Which stakeholder does Peter need to identify? a. Sponsor b. Customer c. User d. Project Manager This document is a partial preview. Full document download can be found on Flevy: http://flevy.com/browse/document/cpre-fl-module-1-re-intro-and-competencies-2556
  13. 13. Correct Option for Question 9 A. Option A discusses about data requirements of the system This document is a partial preview. Full document download can be found on Flevy: http://flevy.com/browse/document/cpre-fl-module-1-re-intro-and-competencies-2556
  14. 14. Thank you and best of Luck! This document is a partial preview. Full document download can be found on Flevy: http://flevy.com/browse/document/cpre-fl-module-1-re-intro-and-competencies-2556
  15. 15. 1 Flevy (www.flevy.com) is the marketplace for premium documents. These documents can range from Business Frameworks to Financial Models to PowerPoint Templates. Flevy was founded under the principle that companies waste a lot of time and money recreating the same foundational business documents. Our vision is for Flevy to become a comprehensive knowledge base of business documents. All organizations, from startups to large enterprises, can use Flevy— whether it's to jumpstart projects, to find reference or comparison materials, or just to learn. Contact Us Please contact us with any questions you may have about our company. • General Inquiries support@flevy.com • Media/PR press@flevy.com • Billing billing@flevy.com

×