Effective Business Requirements (Virtual Classroom Edition)
|
|
- Lester Nichols
- 8 years ago
- Views:
Transcription
1 Developing & Confirming Effective Business Requirements (Virtual Classroom Edition) Eliminate Costly Changes and Save Time by Nailing Down the Project Requirements the First Time! Pre-Workshop Preparation
2 Developing and Confirming Effective Business Requirements (Virtual Classroom Edition) Version 1.0, April The Center for Requirements Excellence 558 Castle Pines Parkway Suite B4-111 Castle Rock, CO USA ALL RIGHTS RESERVED. All trademarks are owned by their respective companies and referred to herein for identification purposes only. RWBR VCL v1.0 Pre-Work
3 Pre-Workshop Preparation/1 Greetings! Thank you for choosing to attend Developing and Confirming Effective Business Requirements in our virtual classroom. The session runs on three consecutive days and will feature the same caliber of facilitation, peer interaction, labs, and courseware that you find in our traditional physical classroom training. Learning follows the principle that what you get out of a course the value you derive is directly proportional to the effort you put in. This is especially true for courses delivered virtually. To help you maximize your learning, we re asking that you complete a short pre-workshop preparation assignment. It s in the form of a short quiz about requirements development terminology and basic concepts. Our Developing and Confirming Effective Business Requirements course is specifically designed for Business Analysts and other IT professionals who already have a bit of knowledge of systems development and requirements. Thus, the pre-workshop preparation is intended as a review of information, concepts, and terms that you should already know. Please take the time to complete this exercise. You ll then have a chance to check your responses and to view additional reference information about any of the quiz questions you wish. In our virtual session, you ll have a brief opportunity to obtain answers to any questions you might have. Thank you for your time and effort. We look forward to seeing you in the virtual classroom soon! How to Use This Document 1. Complete the Pre-Test that begins on the next page. For each question, click the blank underlined field next to the question number and type in the letter corresponding to your chosen answer. 2. Check your answers. Click the link at the bottom of any page in the Pre-Test to quickly go to the Answer Key. 3. If your selected answer was not correct, read the explanation. 4. If you want more information than the explanation, click the italicized links in the Answer Key to learn more. You ll be directed to some helpful reference information. RWBR VCL v1.0 Pre-work
4 2/Pre-Workshop Preparation EXERCISE: TEST YOUR KNOWLEDGE OF REQUIREMENTS DEVELOPMENT PURPOSE To review terms and concepts of requirements development OBJECTIVES Gain a common definition of important terms Review key concepts in requirements definition Be able to correctly differentiate and categorize types of requirements INSTRUCTIONS 1. For each Pre-Test question, click or tab to the underlined field next to the question number. 2. Type the letter corresponding to your chosen answer 3. View the Answer Key by holding down the CRTL key and clicking on the links at the bottom of each page 4. To return to the Pre-Test, click the Back arrow in the toolbar at the top of the screen To enable this feature in Word, click View > Toolbars > Web 5. If you would like further explanation of an incorrect answer or if you want to see more information about a topic being tested, click the italicized links in the Answer Key 6. Note any further questions or remarks you have so that we can discuss them in our workshop session RWBR VCL v1.0 Pre-Work
5 Pre-Workshop Preparation/1 PRE-TEST 1. A requirement is any of the following EXCEPT: a. A capability needed by a stakeholder to solve a problem or achieve a goal b. A set of interrelated processes performed to accomplish a business goal c. A statement of a customer need d. A condition that a system must meet to satisfy a specification 2. What is the first question an analyst should ask about a proposed new requirement? a. How long will it take to incorporate this requirement? b. Is this requirement a must have or a nice to have? c. What impact will this requirement have on the project budget? d. Is this requirement in scope? 3. The most critical contributor to software quality is: a. Effective modeling b. Coding c. Customer involvement d. Testing 4. Effective requirements meet several quality characteristics. These include which of the following? a. Design-independent, unambiguous, and consistent b. Correct, complete, and implementation-specific c. Verifiable, optional, and prioritized d. Traceable, feasible, and solution-specific 5. Which characteristic of effective requirements is lacking in this statement? The ticket reservation system must accommodate multiple simultaneous users without crashing. a. Design independent b. Unambiguous c. Consistent d. Complete Check your answers RWBR VCL v1.0 Pre-work
6 2/Pre-Workshop Preparation 6. All of the following statements are true EXCEPT: a. Every system must have at least one input and at least one output b. Internal actors receive inputs and produce outputs c. Each external actor must supply at least one input and receive at least one output d. A system must include a process for receiving every input and a process for producing every output 7. What is the difference between an actor and a stakeholder? a. Stakeholders give us requirements, and actors validate them b. Actors interact with the system, while stakeholders have some interest in the system c. An actor is a technical user and a stakeholder is a business user d. There is no difference between an actor and a stakeholder 8. A project/product manager: a. Monitors changing requirements and coordinates negotiation b. Coordinates requirements management activities c. Selects elicitation techniques to be used in gathering requirements d. Monitors the progress of requirements development and management 9. Which of the following describes one of an analyst s responsibilities? a. Performs strategic planning b. Translates user needs into requirements c. Resolves conflicts in the project priorities d. Oversees scope negotiations 10. Subject matter experts are responsible for all of the following EXCEPT: a. Ensuring requirements align with the product vision b. Reviewing all requirements documentation c. Prioritizing requirements d. Providing details about business processes, rules, and data Check your answers RWBR VCL v1.0 Pre-Work
7 Pre-Workshop Preparation/3 11. A project sponsor: a. Ensures that analysts and subject matter experts have everything they need to manage the requirements process b. Acts as a liaison between the project team and the business management organization c. Makes decisions about the overall scope of the project d. Verifies that requirements are necessary, correct, complete, and consistent 12. An analyst is responsible for all of the following EXCEPT: a. Creating and maintaining user requirements b. Approving the requirements specification c. Producing the requirements specifications d. Managing requirements 13. Business requirements should be approved by: a. Subject-Matter Expert b. Project Manager c. Business Analyst d. Project Sponsor 14. User requirements are approved by: a. Project Sponsor, Business Analyst b. Project Sponsor, Project Manager c. Subject-Matter Expert d. Developer 15. The requirement Rush orders will incur a surcharge meets all of the following quality criteria EXCEPT: a. Unambiguous b. Verifiable c. Design-independent d. Consistent Check your answers RWBR VCL v1.0 Pre-work
8
9 Pre-Workshop Preparation/1 ANSWER KEY 1. b A set of interrelated processes performed to accomplish a business goal Choices a, c, and d are true of requirements. All requirements are statements of customer need. Some requirements specify capabilities needed by the stakeholder, while others define conditions that the system must meet. However, choice b is the definition of a system. 2. d Is this requirement in scope? Questions a and c are good ways of determining project constraints. The project budget and schedule impacts do need to be discovered. Similarly, it s important to discover the priority of each requirement, which question b helps uncover. But priority and constraints are only relevant for requirements determined to be in scope. To avoid wasting time and effort, we should first establish whether a proposed requirement is consistent with the goals of the project. Once a requirement seems to be in scope, we can then proceed with understanding its impact on the project. 3. c Customer involvement It s almost impossible to produce a system that meets its user needs if time and care aren t taken to understand them. Choices a, b, and d are important; we need to model, code, and test in the development process in order to reduce the chances of defects. But the best modeling, coding, and testing techniques won t lead to a successful outcome unless we know what our user wants. So involving the customer in the requirements phase is critical. 4. a Design-independent, unambiguous, and consistent To be effective, a requirement or set of requirements conforms to specific characteristics. Among these are that the requirements must be designindependent (specifying what is to be done or produced but not how it s to be implemented), unambiguous (clear, specific, and subject to consistent interpretation), and consistent (don t conflict with each other). Valid characteristics in the answer choices include correct (accurately state stakeholders needs and are within scope), complete (fully describes the behavior or characteristic of the system), verifiable (capable of being tested and validated), prioritized (have varying levels of importance, which allows for real-world tradeoffs and changes in the project), traceable connected to the stakeholders and the system components), and feasible (they have a high likelihood of being implemented within the known project parameters). RWBR VCL v1.0 Pre-work
10 2/Pre-Workshop Preparation Answer Key (continued) 5. b Unambiguous This question is about characteristics of effective requirements. Nothing in the statement is obviously inconsistent, erroneous, or specific to a particular solution design, so a, c, and d seem correct. However, it s not clear what multiple simultaneous users means. The statement does not specify how many users at one time nor what the simultaneous users might be doings (updating data, merely viewing, etc.). The statement is ambiguous, and thus b is correct. 6. c Each external actor must supply at least one input and receive at least one output Every system or process must have at least one input and output ( a ) and must include some process for receiving the inputs and producing the outputs ( d ). Actors provide inputs, process them, and receive outputs. An actor that provides an input or receives an output, or both, is known as an external actor, while an actor that receives an input or produces an output is known as an internal actor (b ). It is possible for an external actor to supply an input but not receive an output or vice versa; there is no requirement that an external actor do both. 7. b Actors interact with the system, while stakeholders have some interest in the system On any system development effort, a variety of parties can affect the project, be affected by the project, or have some other interest in the project. These people and organizations are the stakeholders. Some of the stakeholders will interact with the system; they are known as users or actors. So choice b is correct. An actor does use a system, but a stakeholder may or may not ( c ). All stakeholders may give us requirements; it is usually the stakeholders that validate the requirements, not just the actors or users ( a ). 8. d Monitors the progress of requirements development and management Choices a, b, and c are usually performed by the business analyst assigned to the project. Note that a Business Analyst might have a title such as Requirements Analyst, Business Systems Analyst, or Requirements Manager. On the other hand, we depend upon someone else to manage the overall project, including the progress of but not the performance of the requirements development aspects. That person typically has the role of project manager or product manager. Choice d is the correct answer. RWBR VCL v1.0 Pre-Work
11 Pre-Workshop Preparation/3 Answer Key (continued) 9. b Translates user requirements into specifications Choice a is incorrect because strategic planning is a management responsibility, one which ought to be performed before projects are prioritized, selected and initiated. The project manager should resolve conflicts in project priorities ( c ), working with various project stakeholders and involving management as needed. Similarly, the Project Manager should work with stakeholders as they negotiate about the specific scope of the project ( d ). That leaves b, which is correct. Essential responsibilities of a business analyst are understanding the needs of the users and other stakeholders and translating them into clear, effective statements of requirements. 10. b Reviewing all requirements documentation Subject-matter experts play a vital role in project success. Among their most important contributions are ensuring that the requirements fit within the vision for the product or solution ( a ), prioritizing the requirements to ensure that the mostneeded functions are produced as soon as possible ( c ), and providing details about business rules and processes ( d ). While a subject-matter expert might review some of the requirements for a system, there will likely be aspects of the system that are unrelated to her or his expertise. Therefore, the best answer choice is b. 11. c Makes decisions about the overall scope of the project A classic responsibility of a project sponsor is to make decisions about what is included in the scope of the project ( c ). Choices a and b are incorrect because they are responsibilities of the project manager. Verifying that requirements meet the characteristics for effectiveness is the responsibility of the business analyst, so choice d is also incorrect. 12. b Approving the requirements specification Business analysts have a great deal of involvement with requirements specifications. Using a variety of elicitation techniques, they collect, create, document, and maintain user and solution requirements. This responsibility includes managing the requirements throughout the life cycle ( a, c, and d ). One thing analysts should not do is approve the requirements; that is the responsibility of designated stakeholders. So b is the correct response. RWBR VCL v1.0 Pre-work
12 4/Pre-Workshop Preparation Answer Key (continued) 13. d Project Sponsor A business requirement is a basic statement of the rationale for a project. It describes the needs that the project is undertaken to satisfy and are usually written by business managers. The project sponsor ( d ) has the ultimate authority for approving the business requirements. While subject-matter experts ( a ) might have input into the business requirements, they lack the authority to approve them. And business analysts and project managers ( b and c ) not only don t approve the business requirements, they should not contribute to them either, for that is the role of the stakeholders from the business. 14. c Subject-Matter Expert A user requirement is a statement of tasks that a user of a system needs to accomplish. The best-qualified team member to approve user requirements would therefore be a subject-matter expert ( c ) that either has experience using the system or has knowledge of how it will be used. The other team members listed (project sponsor, business analyst, project manager, and developer) might review the user requirements, but they should neither contribute nor be responsible for approving them. 15. a Unambiguous The statement Rush orders will incur a surcharge is verifiable ( b ) because we can test that a surcharge is added whenever an order has a status of rush. Because the statement doesn t specify exactly how the surcharge is to be added, it is design-independent ( c ), and as far as we can tell, it s consistent ( d ). But it s not unambiguous ( a ) because it doesn t include specifics about how much the surcharge must be. RWBR VCL v1.0 Pre-Work
13 Pre-Workshop Preparation/5 Reference: Requirements Terms and Concepts Process A set of tasks to transform at least one input into at least one output May be manual, automated, or both May be composed of hardware, software, and people Must have at least one Input Output Actor System A process or set of processes done to accomplish some business goal or objective A collection of interrelated elements that work together to achieve an objective May be manual, automated, or both May consist of hardware, software, and people Analyzed to discover what to Keep Remove Add Change Scope The extent or limit of a project A statement of what the project will produce or deliver for its customers Represents the project boundaries and limitations Must have at least one Requirement A condition or capability needed by a user to solve a problem or achieve an objective A condition or capability that must be met or possessed by a system component to satisfy a contract, standard, specification or regulation A documented representation of that condition or capability See IEEE standard RWBR VCL v1.0 Pre-work
14 6/Pre-Workshop Preparation Reference: Requirements Terms and Concepts (continued) Business Requirement A statement of the business rationale justifying a project A high-level statement of the need that the project will satisfy for the business Often described in a project charter, business case, or project scope document Written for the business team and project sponsor User Requirement A statement of a task that a user will need to accomplish with a system A statement of a characteristics that a user will need a system to meet Often described in a user requirements or features document or in use cases Written for users, subject-matter experts, and technical staff (such as developers and testers) Solution Requirement A detailed statement of a functional or nonfunctional requirement that the system (also call solution or sometimes, software) will fulfill Documents an agreement between stakeholders in the business and the technical staff about what the solution must do and be Often described in a requirements specification, requirements definition document, or functional specification Written for the technical staff but must be understood and approved by the subject-matter experts from the business RWBR VCL v1.0 Pre-Work
15 Pre-Workshop Preparation/7 Reference: Key Roles in Requirements Development Stakeholder Anyone with a vested interest in the project or system Anyone who can affect the outcome of the project (consider especially those that could cause the project to fail) Anyone who can be affected by the outcome of the project Should be defined for the system Has roles, interests, capabilities, and concerns that should be documented Actor Anyone or anything that interacts with a system Has a specific role in interactions with the system May be A person by position title A functional area or department if the position title is not known An entity outside the organization Another system (manual, automated or both) External actors provide inputs, receive outputs or both Internal actors convert inputs into outputs using the processes of the system Project Sponsor Allocates resources for the project Ensures appropriate participation by customers and users Defines and approves the overall project scope Resolves conflicts in the requirements priorities RWBR VCL v1.0 Pre-work
16 8/Pre-Workshop Preparation Reference: Key Roles in Requirements Development (continued) Business Analyst Chooses elicitation techniques and methods Coordinates and facilitates elicitation activities Develops requirements through collaboration with subject-matter experts and users Drafts models and documents requirements Translates user requirements into specifications Monitors changing requirements Verifies requirements quality Note: Business Analyst may also be known as analyst, systems analyst, systems engineer, requirements analyst, etc. The position title of the analyst is not important the role is. Project Manager Acts as a liaison between the project team and the business Oversees requirements prioritization Coordinates user involvement Ensures that analysts and subject-matter experts have resources needed to develop and manage requirements Manages the requirements change control process Monitors progress of requirements development and management May be known as a Product Manager RWBR VCL v1.0 Pre-Work
17 Pre-Workshop Preparation/9 Reference: Key Roles in Requirements Development (continued) Subject-Matter Expert Represents the users Provides details about the business processes, policies, and data Communicates user needs Participates in creating or reviewing requirements models and documents Prioritizes requirements Reviews requirements documents for quality and alignment with user needs Developer Provides details about design constraints Advises the team about feasibility of requirements May assist in writing software requirements specification Should review all requirements documentation Tester Contributes ideas for success criteria for the requirements and system May assist in writing software requirements specification Reviews all requirements documentation Reviews software specifications to ensure that they can be tested RWBR VCL v1.0 Pre-work
18 10/Pre-Workshop Preparation Reference: Characteristics of Effective Requirements Complete Fully describes functionality to be delivered Example: Incomplete: The system shall provide details (TBD) of a tour when a tour code is entered. Complete: The system shall provide the tour name, description and cost of a tour when the tour code is entered. Correct Accurately describes functionality to be built Example: Incorrect: A security deposit equal to the value of a rental villa shall be collected at the time the villa is occupied. (Yikes! The villa is worth $1,150,000!) Correct: A security deposit equal to the amount of the insurance company deductible for the villa shall be collected at the time the villa is occupied. (Whew! Much better.) Feasible Possible to implement within known capabilities/ limitations of system and operating environment (and known technology) Example: Not feasible: The rental property map should be a rotating, three-dimensional map like the one on Star Trek. Feasible: The location of any rental villa shall be displayed in such a way that it is visible from any point in the rental office. Necessary Represents capability user really needs or that s required for external requirement or standard Originated from and validated by recognized authority Prioritized Assigned an implementation priority As simple as must have and nice to have Used by project manager to respond to changes (budget cuts, schedule overruns, personnel losses, or new requirements) Documented It s not a requirement if it s not documented! RWBR VCL v1.0 Pre-Work
19 Pre-Workshop Preparation/11 Reference: Characteristics of Effective Requirements (continued) Unambiguous All readers arrive at a single, consistent interpretation Define all terms, abbreviations, acronyms, etc. Avoid using terms such as user friendly, intuitive, etc. Avoid using connectors: and, or, etc. Example: Ambiguous: A customer must be acceptable to us in order to rent a villa. Unambiguous: A customer must have a status of preferred, excellent or good in order to rent a villa. Verifiable Possible to devise tests, inspect and/or demonstrate functionality Example: Not testable: The customer will receive a reservation confirmation within a reasonable time when they book a tour. Testable: The system shall generate a reservation confirmation to the customer within 2 minutes. Traceable Connected back to source and forward to use cases, design elements, code modules, test scripts, etc. Example: BR-22: The customer must have a status of preferred, excellent, or good in order to rent a villa Traced to: UC-2, step 5: The system validates the status of the customer. Or the step of the use case can be traced back to the business rule to be validated in that step. Design-Independent States what needs to be done, not how it should or could be done Most requirements can be fulfilled in a number of ways Example: Not design-independent: Tour Reps shall enter all reservations from their laptops. Design-independent: Tour Reps must be able to enter reservations from any remote location outside of a company office. Consistent As a set, requirements should not conflict with each other RWBR VCL v1.0 Pre-work
Utilizing Defect Management for Process Improvement. Kenneth Brown, CSQA, CSTE kdbqa@yahoo.com
Utilizing Defect Management for Process Improvement Kenneth Brown, CSQA, CSTE kdbqa@yahoo.com What This Presentation Will Cover How to Appropriately Classify and Measure Defects What to Measure in Defect
More informationRequirements Engineering Process
Software Engineering Requirements Engineering Process Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To describe the principal requirements engineering activities and d their
More informationRequirements Definition and Management Processes
Software Engineering G22.2440-001 Session 1 Sub-Topic 1 Requirements Definition & Management Processes and Tools Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute
More informationProject Quality Planning
The PROJECT PERFECT White Paper Collection Project Quality Planning Neville Turbit Overview Every project should have a quality plan. In reality, very few do. It is something that has puzzled me for some
More informationSoftware Engineering. Session 3 Main Theme Requirements Definition & Management Processes and Tools Dr. Jean-Claude Franchitti
Software Engineering Session 3 Main Theme Requirements Definition & Management Processes and Tools Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical
More information3SL. Requirements Definition and Management Using Cradle
3SL Requirements Definition and Management Using Cradle November 2014 1 1 Introduction This white paper describes Requirements Definition and Management activities for system/product development and modification
More informationThis alignment chart was designed specifically for the use of Red River College. These alignments have not been verified or endorsed by the IIBA.
Red River College Course Learning Outcome Alignment with BABOK Version 2 This alignment chart was designed specifically for the use of Red River College. These alignments have not been verified or endorsed
More informationThe What, Why, Who, When and How of Software Requirements
SUMMARY The What, Why, Who, When and How of Software Requirements Linda Westfall President The Westfall Team 3000 Custer Road, Suite 270, PMB 101 Plano, TX 75075 lwestfall@westfallteam.com www.westfallteam.com
More informationModule 2. Software Life Cycle Model. Version 2 CSE IIT, Kharagpur
Module 2 Software Life Cycle Model Lesson 3 Basics of Software Life Cycle and Waterfall Model Specific Instructional Objectives At the end of this lesson the student will be able to: Explain what is a
More informationZarządzanie projektem agile 2015-05-21. The Mystery of Effective IT by Bogdan Bereza blogomotion.com/mystery 1 (30) Effective IT?
The Mystery of Effective IT by Bogdan Bereza blogomotion.com/mystery 1 (30) Effective IT? The Mystery of Effective IT by Bogdan Bereza blogomotion.com/mystery 2 (30) Bogdan Bereza, Victo.eu 1 The Mystery
More informationApplied Software Project Management
Applied Software Project Management Software Project Planning http://www.stellman-greene.com 1 Who needs software? Most software is built in organizations for people with specific needs. A stakeholder
More informationDefining Quality Workbook. <Program/Project/Work Name> Quality Definition
Defining Quality Workbook Quality Definition Introduction: Defining Quality When starting on a piece of work it is important to understand what you are working towards. Much
More informationWriting a Requirements Document For Multimedia and Software Projects
Writing a Requirements Document For Multimedia and Software Projects Rachel S. Smith, Senior Interface Designer, CSU Center for Distributed Learning Introduction This guide explains what a requirements
More informationExpert Reference Series of White Papers. Intersecting Project Management and Business Analysis
Expert Reference Series of White Papers Intersecting Project Management and Business Analysis 1-800-COURSES www.globalknowledge.com Intersecting Project Management and Business Analysis Daniel Stober,
More informationExplanation of a Project and the Value of a Project Manager
Comprehensive Consulting Solutions, Inc. Bu siness Savvy. IT Smart. What is a Project and when is a Project Manager needed? White Paper Published: March 2001 (with revisions) Explanation of a Project and
More informationLecture 17: Requirements Specifications
Lecture 17: Requirements Specifications Why we need to write specifications Purpose and audience Choosing an appropriate size and formality Desiderata for Specifications Properties of good specifications
More informationDo You Have the Right Stuff to be a Good Tester?
An e-newsletter published by April 2008 Software Quality Consulting, Inc. Vol. 5 No. 4 Welcome to Food for Thought TM, an e-newsletter from Software Quality Consulting. I've created free subscriptions
More informationTesting, What is it Good For? Absolutely Everything!
Testing, What is it Good For? Absolutely Everything! An overview of software testing and why it s an essential step in building a good product Beth Schechner Elementool The content of this ebook is provided
More informationSPECIFICATION BY EXAMPLE. Gojko Adzic. How successful teams deliver the right software. MANNING Shelter Island
SPECIFICATION BY EXAMPLE How successful teams deliver the right software Gojko Adzic MANNING Shelter Island Brief Contents 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 Preface xiii Acknowledgments xxii
More informationGetting Started with Kanban Paul Klipp
Getting Started with Kanban Paul Klipp kanbanery 2 Contents 3/ Getting Started with Kanban 4/ What is Kanban? 7/ Using Kanban Does kanban apply to me? How can it help me? What will I have to change? 10/
More informationStory Card Based Agile Software Development
Story Card Based Agile Software Development Chetankumar Patel, and Muthu Ramachandran Leeds Metropolitan University, UK c.patel@leedsmet.ac.uk Abstract The use of story cards for user stories in many Extreme
More informationRequirements Engineering Processes. Feasibility studies. Elicitation and analysis. Problems of requirements analysis
Requirements engineering processes Requirements Engineering Processes The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the.
More informationHow To Develop Software
Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II) We studied the problem definition phase, with which
More informationBusiness Requirements Guidelines
August 25, 2001 Version 1.0 1 Important Information This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes
More informationEssentials of the Quality Assurance Practice Principles of Testing Test Documentation Techniques. Target Audience: Prerequisites:
Curriculum Certified Software Tester (CST) Common Body of Knowledge Control Procedures Problem Resolution Reports Requirements Test Builds Test Cases Test Execution Test Plans Test Planning Testing Concepts
More informationRequirements Management In Action. A beginners guide to Requirements Management
Requirements Management In Action A beginners guide to Requirements Management Table of Contents Introduction How to Capture Requirements What is Traceability? Tips to Capture Better Requirements Conclusion
More informationPartnering for Project Success: Project Manager and Business Analyst Collaboration
Partnering for Project Success: Project Manager and Business Analyst Collaboration By Barbara Carkenord, CBAP, Chris Cartwright, PMP, Robin Grace, CBAP, Larry Goldsmith, PMP, Elizabeth Larson, PMP, CBAP,
More informationBusiness Analyst Boot Camp Course BA101; 5 Days, Instructor-led
Business Analyst Boot Camp Course BA101; 5 Days, Instructor-led Course Description Full-Spectrum Business Analyst Training and Skills Development. Course Objectives Bridge the expectations gap between
More informationSoftware Quality Assurance Plan
For Database Applications Document ID: Version: 2.1a Planning Installation & Acceptance Integration & Test Requirements Definition Design Development 1 / 54 Copyright 2000-2006 Digital Publications LLC.
More informationYour Software Quality is Our Business. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc.
INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc. February 2013 1 Executive Summary Adnet is pleased to provide this white paper, describing our approach to performing
More informationB.2.2. Project Management Principles
B.2.2. Project Management Principles Project management is the application of knowledge, skills, tools, and techniques to project activities in order to meet or exceed stakeholder needs and expectations
More informationSofware Requirements Engineeing
Sofware Requirements Engineeing Three main tasks in RE: 1 Elicit find out what the customers really want. Identify stakeholders, their goals and viewpoints. 2 Document write it down (). Understandable
More informationSoftware Requirements Engineering: What, Why, Who, When, and How By Linda Westfall
Software Engineering: What, Why, Who, When, and How By Linda Westfall Key words: requirements engineering, requirements elicitation, requirements analysis, requirements specification, requirements management,
More informationAs the use of agile approaches
What Does a Business Analyst Do on an Agile Project? By Kent J. McDonald Senior Instructor, B2T Training As the use of agile approaches increases, business analysts struggle to determine how their role
More informationRequirements engineering
Learning Unit 2 Requirements engineering Contents Introduction............................................... 21 2.1 Important concepts........................................ 21 2.1.1 Stakeholders and
More informationTECH. Requirements. Why are requirements important? The Requirements Process REQUIREMENTS ELICITATION AND ANALYSIS. Requirements vs.
CH04 Capturing the Requirements Understanding what the customers and users expect the system to do * The Requirements Process * Types of Requirements * Characteristics of Requirements * How to Express
More informationSOFTWARE DEVELOPMENT STANDARD FOR SPACECRAFT
SOFTWARE DEVELOPMENT STANDARD FOR SPACECRAFT Mar 31, 2014 Japan Aerospace Exploration Agency This is an English translation of JERG-2-610. Whenever there is anything ambiguous in this document, the original
More informationCDC UNIFIED PROCESS PRACTICES GUIDE
Document Purpose The purpose of this document is to provide guidance on the practice of Requirements Definition and to describe the practice overview, requirements, best practices, activities, and key
More informationDraft Requirements Management Plan
BAO111: Core Competencies for the Business Analyst Draft Requirements Management Plan 1.0 INTRODUCTION 1.1 Purpose This document outlines requirements roles and responsibilities, presents a stakeholder
More informationDo you know? "7 Practices" for a Reliable Requirements Management. by Software Process Engineering Inc. translated by Sparx Systems Japan Co., Ltd.
Do you know? "7 Practices" for a Reliable Requirements Management by Software Process Engineering Inc. translated by Sparx Systems Japan Co., Ltd. In this white paper, we focus on the "Requirements Management,"
More informationSystems Development Life Cycle (SDLC)
DEPARTMENT OF BUDGET & MANAGEMENT (SDLC) Volume 1 Introduction to the SDLC August 2006 Table of Contents Introduction... 3 Overview... 4 Page 2 of 17 INTRODUCTION 1.0 STRUCTURE The SDLC Manual consists
More informationOn Efficient Collaboration between Lawyers and Software Engineers when Transforming Legal Regulations to Law-related Requirements
Proceedings of the 2n d International Conference on Information Technology, ICIT 2010 28-30 June 2010, Gdansk, Poland. On Efficient Collaboration between Lawyers and Software Engineers when Transforming
More informationBasic Testing Concepts and Terminology
T-76.5613 Software Testing and Quality Assurance Lecture 2, 13.9.2006 Basic Testing Concepts and Terminology Juha Itkonen SoberIT Contents Realities and principles of Testing terminology and basic concepts
More informationSOFTWARE REQUIREMENTS
SOFTWARE REQUIREMENTS http://www.tutorialspoint.com/software_engineering/software_requirements.htm Copyright tutorialspoint.com The software requirements are description of features and functionalities
More informationSyllabus. REQB Certified Professional for Requirements Engineering. Foundation Level
Syllabus REQB Certified Professional for Requirements Engineering Version 2.1 2014 The copyright to this edition of the syllabus in all languages is held by the Global Association for Software Quality,
More informationA Business Analysis Perspective on Business Process Management
A Business Analysis Perspective on Business Process Management October 2013 Discussion Points! Why have Roles?! What is Business Analysis?! Who is the Business Analyst?! Business Analysis & Business Process
More informationHow To Measure Quality
Introduction Metrics for Software Testing: Managing with Facts Part 4: Product Metrics In the previous article in this series, we moved from a discussion of process metrics to a discussion of how metrics
More informationJOURNAL OF OBJECT TECHNOLOGY
JOURNAL OF OBJECT TECHNOLOGY Online at www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2006 Vol. 5. No. 8, November-December 2006 Requirements Engineering Tasks Donald Firesmith,
More informationSoftware development life cycle. Software Engineering - II ITNP92 - Object Oriented Software Design. Requirements. Requirements. Dr Andrea Bracciali
Software development life cycle Software life cycle: Software Engineering - II ITNP92 - Object Oriented Software Design Dr Andrea Bracciali Module Co-ordinator 4B86 abb@cs.stir.ac.uk Spring 2014 (elicitation)
More informationRequirements Management
REQUIREMENTS By Harold Halbleib Requirements Management Identify, Specify, Track and Control Requirements Using a Standard Process About the author... Harold Halbleib has a degree in Electrical Engineering
More informationSound Transit Internal Audit Report - No. 2014-3
Sound Transit Internal Audit Report - No. 2014-3 IT Project Management Report Date: Dec. 26, 2014 Table of Contents Page Background 2 Audit Approach and Methodology 2 Summary of Results 4 Findings & Management
More informationHOW TO USE THE DGI DATA GOVERNANCE FRAMEWORK TO CONFIGURE YOUR PROGRAM
HOW TO USE THE DGI DATA GOVERNANCE FRAMEWORK TO CONFIGURE YOUR PROGRAM Prepared by Gwen Thomas of the Data Governance Institute Contents Why Data Governance?... 3 Why the DGI Data Governance Framework
More informationSoftware Requirements, Third Edition
j Microsoft Software Requirements, Third Edition Karl Wiegers and Joy Beatty Contents Introduction Acknowledgments xxv xxxi PART I SOFTWARE REQUIREMENTS: WHAT, WHY, AND WHO Chapter 1 The essential software
More informationRequirements Engineering Processes. Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 7 Slide 1
Requirements Engineering Processes Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 7 Slide 1 Objectives To describe the principal requirements engineering activities and their relationships
More informationSample Document. Onboarding: The Essential Rules For A Successful Onboarding Program. Student Manual. www.catraining.co.uk
The Essential Rules For A Successful Onboarding Program Tel: 020 7920 9500 Onboarding: The Essential Rules For A Successful Onboarding Program www.catraining.co.uk Student Manual Copyright 2014 Charis
More informationVancouver Chapter Study Group. BABOK Chapter 1 Introduction. Jorge Vega
Vancouver Chapter Study Group BABOK Chapter 1 Introduction Jorge Vega 1 Study Group Sessions About me Format BABOK 2.0 Frequency Type of sessions Prep work required Professional Development Units Expanding
More informationTen steps to better requirements management.
White paper June 2009 Ten steps to better requirements management. Dominic Tavassoli, IBM Actionable enterprise architecture management Page 2 Contents 2 Introduction 2 Defining a good requirement 3 Ten
More informationSystems Analysis and Design Life Cycle
Systems Analysis and Design Life Cycle 2.1 The major goal of requirement determination phase of information system development is a. determine whether information is needed by an organization b. determine
More informationBusiness Analysis Standardization & Maturity
Business Analysis Standardization & Maturity Contact Us: 210.399.4240 info@enfocussolutions.com Copyright 2014 Enfocus Solutions Inc. Enfocus Requirements Suite is a trademark of Enfocus Solutions Inc.
More informationITIL Introducing service strategy
ITIL Introducing service strategy The objectives of service strategy Service strategy shows organisations how to transform service management from an organisational capability into a strategic asset, and
More informationProject Knowledge Areas
From Houston S: The Project Manager s Guide to Health Information Technology Implementation. Chicago: HIMSS; 2011; pp 27 39. This book is available on the HIMSS online bookstore at www. himss.org/store.
More informationThe profile of your work on an Agile project will be very different. Agile projects have several things in common:
The Agile Business Analyst IT s all about being Agile? You re working as a Business Analyst in a traditional project environment, specifying the requirements for IT Developers to build. Suddenly everyone
More informationIntroduction... 4. Purpose... 4 Scope... 4 Manitoba ehealth Change Management... 4 Icons... 4. RFC Procedures... 5
Remedy Change Management Version 3.0 Modified: 10/27/2015 Table of Contents Introduction... 4 Purpose... 4 Scope... 4 Manitoba ehealth Change Management... 4 Icons... 4 RFC Procedures... 5 Process Flow
More informationDepartment of Energy Quality Managers Software Quality Assurance Subcommittee Reference Document SQAS19.01.00-2000
Department of Energy Quality Managers Software Quality Assurance Subcommittee Reference Document SQAS19.01.00-2000 Guidelines for Requirements Management April 2000 United States Department of Energy Albuquerque
More informationSample Exam. 2011 Syllabus
ISTQ Foundation Level 2011 Syllabus Version 2.3 Qualifications oard Release ate: 13 June 2015 ertified Tester Foundation Level Qualifications oard opyright 2015 Qualifications oard (hereinafter called
More informationLowering business costs: Mitigating risk in the software delivery lifecycle
August 2009 Lowering business costs: Mitigating risk in the software delivery Roberto Argento IBM Rational Business Development Executive Valerie Hamilton IBM Rational Solution Marketing Manager and Certified
More informationhttp://www.io4pm.org IO4PM - International Organization for Project Management
THE ONLY BOOK CAN SIMPLY LEARN PROJECT MANAGEMENT! Page 1 Contents ABOUT THE AUTHOR... 3 WHAT IS PROJECT MANAGEMENT?... 5 ORGANIZATIONAL INFLUENCES AND PROJECT LIFECYCLE... 11 PROJECT MANAGEMENT PROCESSES...
More informationITS Projects Systems Engineering Process Compliance Checklist
ITS Projects Systems Engineering Process Compliance Checklist FHWA Final Rule (23 CFR 940) This checklist is to be completed by the MDOT or LPA Project Management Staff. Please refer to the accompanying
More informationApplied Software Project Management
Applied Software Project Management Introduction http://www.stellman-greene.com 1 Why do software projects fail? People begin programming before they understand the problem Everyone likes to feel that
More informationBuild the Right Software First Time
Build the Right Software First Time are the most misunderstood part of systems development, and yet the most crucial. must be correct if the rest of the development effort is to succeed. This workshop
More informationSummary of GAO Cost Estimate Development Best Practices and GAO Cost Estimate Audit Criteria
Characteristic Best Practice Estimate Package Component / GAO Audit Criteria Comprehensive Step 2: Develop the estimating plan Documented in BOE or Separate Appendix to BOE. An analytic approach to cost
More informationProcurement Programmes & Projects P3M3 v2.1 Self-Assessment Instructions and Questionnaire. P3M3 Project Management Self-Assessment
Procurement Programmes & Projects P3M3 v2.1 Self-Assessment Instructions and Questionnaire P3M3 Project Management Self-Assessment Contents Introduction 3 User Guidance 4 P3M3 Self-Assessment Questionnaire
More informationA Framework for Software Product Line Engineering
Günter Böckle Klaus Pohl Frank van der Linden 2 A Framework for Software Product Line Engineering In this chapter you will learn: o The principles of software product line subsumed by our software product
More informationTranslating IT Metrics into Business Benefits
Translating IT Metrics into Business Benefits By Rae Ann Bruno President, Business Solutions Training, Inc. IT managers regularly gather and distribute metrics reflecting group performance. But are these
More informationDSDM DSDM. CONSORTiUM. CONSORTiUM. AgileBA. The Handbook for Business Analysts. Extract The Requirements Lifecycle In An Agile Project. www.dsdm.
DSDM CONSORTiUM DSDM CONSORTiUM AgileBA The Handbook for Business Analysts Extract The Lifecycle In An Agile Project www.dsdm.org This Extract from AgileBA, The Lifecycle in an Agile Project, is based
More informationSoftware Development Life Cycle
4 Software Development Life Cycle M MAJOR A J O R T TOPICSO P I C S Objectives... 52 Pre-Test Questions... 52 Introduction... 53 Software Development Life Cycle Model... 53 Waterfall Life Cycle Model...
More informationDevelop Project Charter. Develop Project Management Plan
Develop Charter Develop Charter is the process of developing documentation that formally authorizes a project or a phase. The documentation includes initial requirements that satisfy stakeholder needs
More informationAchieving Business Analysis Excellence
RG Perspective Achieving Business Analysis Excellence Turning Business Analysts into Key Contributors by Building a Center of Excellence Susan Martin March 5, 2013 11 Canal Center Plaza Alexandria, VA
More informationSoftware Risk Factors in Developing E-Governance Projects
International Journal of Allied Practice, Research and Review Website: www.ijaprr.com (ISSN 2350-1294) Software Risk Factors in Developing E-Governance Projects Ms. Harmeet Malhotra Associate Professor,
More informationFundamentals of Measurements
Objective Software Project Measurements Slide 1 Fundamentals of Measurements Educational Objective: To review the fundamentals of software measurement, to illustrate that measurement plays a central role
More informationSEVEN KEY TACTICS FOR ENSURING QUALITY
SEVEN KEY TACTICS FOR ENSURING QUALITY 1 INTRODUCTION Besides avoiding disasters and fatal flaws, quality assurance (QA) delivers significant benefits for banks. Strong QA planning provides the groundwork
More informationpm4dev, 2007 management for development series Introduction to Project Management PROJECT MANAGEMENT FOR DEVELOPMENT ORGANIZATIONS
pm4dev, 2007 management for development series Introduction to Project Management PROJECT MANAGEMENT FOR DEVELOPMENT ORGANIZATIONS PROJECT MANAGEMENT FOR DEVELOPMENT ORGANIZATIONS A methodology to manage
More informationRequirements Traceability
UNIVERSITY OF WATERLOO Faculty of Mathematics School of Computer Science CS 645 - Software Requirements Specification and Analysis Requirements Traceability prepared by Michael Morckos ID : 20363329 Electrical
More informationRequirements Traceability. Mirka Palo
Requirements Traceability Mirka Palo Seminar Report Department of Computer Science University of Helsinki 30 th October 2003 Table of Contents 1 INTRODUCTION... 1 2 DEFINITION... 1 3 REASONS FOR REQUIREMENTS
More informationTop 10 Do s and Don ts in Selecting Campus Recreation Software
Top 10 Do s and Don ts in Selecting Campus Recreation Software Discussion Paper Investing in technology can make your Campus Recreation department more efficient, increase revenues, reduce costs, and improve
More informationOffice of Community Planning and Development
WHEN A PUBLIC AGENCY ACQUIRES YOUR PROPERTY www.hud.gov/relocation U.S. Department of Housing and Urban Development Office of Community Planning and Development Introduction This booklet describes important
More informationTHE INFORMATION AUDIT AS A FIRST STEP TOWARDS EFFECTIVE KNOWLEDGE MANAGEMENT: AN OPPORTUNITY FOR THE SPECIAL LIBRARIAN * By Susan Henczel
INSPEL 34(2000)3/4, pp. 210-226 THE INFORMATION AUDIT AS A FIRST STEP TOWARDS EFFECTIVE KNOWLEDGE MANAGEMENT: AN OPPORTUNITY FOR THE SPECIAL LIBRARIAN * By Susan Henczel Introduction Knowledge is universally
More informationFormal Software Testing. Terri Grenda, CSTE IV&V Testing Solutions, LLC www.ivvts.com
Formal Software Testing Terri Grenda, CSTE IV&V Testing Solutions, LLC www.ivvts.com Scope of Testing Find defects early Remove defects prior to production Identify Risks Unbiased opinion When Should Testing
More informationThe role of integrated requirements management in software delivery.
Software development White paper October 2007 The role of integrated requirements Jim Heumann, requirements evangelist, IBM Rational 2 Contents 2 Introduction 2 What is integrated requirements management?
More informationLife Cycle Quality Gates
1 Operations Release Life Cycle Quality Gates 8 Post Implement Validation 6 Implement Build Product Test Quality Assurance 2 Versions 3 4 5 Patches 7 Design 1 10 9 Requirements Requirements Sources: Executive
More informationThe Business Analyst Role in Agile Projects and How To Do It
ASPE RESOURCE SERIES The Business Analyst Role in Agile Projects and How To Do It Prepared for ASPE-SDLC by Rob Snowden The skills we teach drive real project success. The Business Analyst Role in Agile
More informationHow To Choose the Right Vendor Information you need to select the IT Security Testing vendor that is right for you.
Information you need to select the IT Security Testing vendor that is right for you. Netragard, Inc Main: 617-934- 0269 Email: sales@netragard.com Website: http://www.netragard.com Blog: http://pentest.netragard.com
More informationProject Management Process
Project Management Process Description... 1 STAGE/STEP/TASK SUMMARY LIST... 2 Project Initiation 2 Project Control 4 Project Closure 5 Project Initiation... 7 Step 01: Project Kick Off 10 Step 02: Project
More informationThe Basics of Scrum An introduction to the framework
The Basics of Scrum An introduction to the framework Introduction Scrum, the most widely practiced Agile process, has been successfully used in software development for the last 20 years. While Scrum has
More informationpm4dev, 2015 management for development series Project Schedule Management PROJECT MANAGEMENT FOR DEVELOPMENT ORGANIZATIONS
pm4dev, 2015 management for development series Project Schedule Management PROJECT MANAGEMENT FOR DEVELOPMENT ORGANIZATIONS PROJECT MANAGEMENT FOR DEVELOPMENT ORGANIZATIONS A methodology to manage development
More informationProfessional Engineers Using Software-Based Engineering Tools
GUIDELINE Professional Engineers Using Software-Based Engineering Tools CONTRIBUTORS Eric Brown, P. Eng. Colin Cantlie, P. Eng. Norm Fisher, P. Eng. Jeremy Jackson, P. Eng. Tibor Palinko, P. Eng. Daniel
More informationBusiness Analyst Position Description
Analyst Position Description September 4, 2015 Analysis Position Description September 4, 2015 Page i Table of Contents General Characteristics... 1 Career Path... 2 Explanation of Proficiency Level Definitions...
More informationProven Best Practices for a Successful Credit Portfolio Conversion
Proven Best Practices for a Successful Credit Portfolio Conversion 2011 First Data Corporation. All trademarks, service marks and trade names referenced in this material are the property of their respective
More informationDevelopment of User Requirements and Use Cases for a Contamination Warning System Dashboard
May 2013 Philadelphia Water Department Contamination Warning System Demonstration Pilot Project: Development of User Requirements and Use Cases for a Contamination Warning System Dashboard Online Water
More informationChapter 3 The Integrated Requirements Management Framework (IREQM)
Chapter 3 The Integrated Management Framework (IREQM) During the software requirements development process, customer and development team meet together for many times to obtain customer and product requirements
More information