...FY08 TAD Consulting Skills Case Library This document is for the INTERVIEWER only. Table of Contents: Case Interview Process and Guidelines 3 Case 1: Requirements Gathering Process 4 Case 2: Improving the Customer Experience 6 Case 3: Vendor Selection Process 8 Case Interview Process 1) Introduce yourself and explain your background and career at Deloitte Consulting. 3 min 2) State the objective of the case interview and present the case to the candidate: 2 min • Explain that you want to understand how the candidate handles a situation relevant to those found on the job. • Mention that throughout the case, you will evaluate several capabilities: problem solving, communication, composure, and structured thinking. • You are evaluating how the candidate approaches the case and the logic and creativity behind his / her recommendations. There is no “right” answer. • Verbally present the case to the candidate. 3) Candidate review of case: 2 min • The candidate may or may not ask for a few minutes to get his / her thoughts together regarding the case. The candidate may take notes. Encourage the candidate to do both if needed. • Make yourself available to answer any questions during this time. 4) Candidate presents solution / approach to the case: 15 min • Make yourself available to answer any questions about the case during this time. • Present “Curve...
Words: 1934 - Pages: 8
...Software Requirements Document Tanya Berezin Table of Contents SHOULD YOU READ THIS PAPER? WHAT IS A REQUIREMENTS DOCUMENT? WHY BOTHER WITH A REQUIREMENTS DOCUMENT? DO I HAVE TO WRITE A REQUIREMENTS DOCUMENT? WHO USES THE REQUIREMENTS DOCUMENT AND WHY? GENERAL PRINCIPLES IN WRITING A REQUIREMENTS DOCUMENT SECTIONS OF A REQUIREMENTS DOCUMENT PART I – APPLICATION OVERVIEW PART II – FUNCTIONAL REQUIREMENTS PART III – APPENDICES 3 3 4 5 5 6 9 10 12 15 WHO NEEDS WHAT? SUMMARY OF PURPOSE AND USAGE OF THE SECTIONS OF THE REQUIREMENTS DOCUMENT 17 HOW TO GET OTHERS TO READ THE REQUIREMENTS DOCUMENT? REFLECTING CHANGES IN REQUIREMENTS DOCUMENTING REQUESTS FOR ENHANCEMENTS TRACING REQUIREMENTS CONCLUSION AND FURTHER READING AUTHOR BIOGRAPHY 18 19 20 21 21 22 Should You Read This Paper? Should You Read This Paper? This paper discusses the purpose and contents of a requirements document for a business application. It is an introduction to the subject and will be most helpful to you if any of the following applies to you: • you are responsible for collecting requirements for a business application • you are leading a business application development project • you are not sure what a requirements document ought to look like or even if you need one • you are not sure what to do with a requirements document even if one miraculously appeared on your desk tomorrow This paper will help you write a professional requirements document. Once you feel you understand what a requirements document...
Words: 7624 - Pages: 31
...Writing a Software Requirements Document Tanya Berezin Table of Contents SHOULD YOU READ THIS PAPER? 3 WHAT IS A REQUIREMENTS DOCUMENT? 3 WHY BOTHER WITH A REQUIREMENTS DOCUMENT? 4 DO I HAVE TO WRITE A REQUIREMENTS DOCUMENT? 5 WHO USES THE REQUIREMENTS DOCUMENT AND WHY? 5 GENERAL PRINCIPLES IN WRITING A REQUIREMENTS DOCUMENT 6 SECTIONS OF A REQUIREMENTS DOCUMENT 9 PART I – APPLICATION OVERVIEW 10 PART II – FUNCTIONAL REQUIREMENTS 12 PART III – APPENDICES 15 WHO NEEDS WHAT? SUMMARY OF PURPOSE AND USAGE OF THE SECTIONS OF THE REQUIREMENTS DOCUMENT 17 HOW TO GET OTHERS TO READ THE REQUIREMENTS DOCUMENT? 18 REFLECTING CHANGES IN REQUIREMENTS 19 DOCUMENTING REQUESTS FOR ENHANCEMENTS 20 TRACING REQUIREMENTS 21 CONCLUSION AND FURTHER READING 21 AUTHOR BIOGRAPHY 22 Should You Read This Paper? Should You Read This Paper? This paper discusses the purpose and contents of a requirements document for a business application. It is an introduction to the subject and will be most helpful to you if any of the following applies to you: • you are responsible for collecting requirements for a business application • you are leading a business application development project • you are not sure what a requirements document ought to look like or even if you need one • you are not sure what to do with a requirements document even if one miraculously appeared on your desk tomorrow This...
Words: 7624 - Pages: 31
...REQUIREMENTS COLLECTION Template A GUIDE FOR REQUIREMENTS GATHERING AND TRACE-ABILITY MATRIX DEVELOPMENT Revision: 1.0 About this document 3 Guidelines for using the Requirements Collection Template 4 Requirement ID: 4 Requirement Type 4 Parent Requirement#: 5 Source and source Document: 5 Dependencies: 5 Definitions of Priorities: 5 Tracking Requirements and status 6 Status Options: 6 Change History: 6 Clarification/specification of Requirement 6 Rationale: 6 Acceptance/Fit Criteria: 6 Dependencies: 6 The requirements collection template form 7 Requirements Traceability Matrix 8 About this document Requirements are the foundation of the project and the development of the product that the project has been organized to develop. The purpose of this document is to present a standardized requirements collection template. The template proposed in this document serves a variety of purposes. It is intended for all types of project requirements: • Business • User • System • Functional • Non-Functional The template is useful for the development of a traceability matrix because it tracks a requirement to its parent requirement, and requests the source and or document from which the requirement came. The template also supports specific, measureable, attainable, realistic and testable requirements by asking for supporting clarifications...
Words: 1161 - Pages: 5
...Ministry/Agency Name [Complete file/properties to populate fields on this page and in the document headers] Project Name Project #: Business Requirements Document (BRD) Template Prepared by: Author's Name Prepared for: Date Submitted: [Date] Project Sponsor: Project Sponsor's Name Client Acceptor: Project Manager: Document Number: 6450-20/Project Number /BRD Security Classification: Low Version: 0.1 Last Updated: April 26, 2013 Creation Date: June 06, 2006 Table of Contents Table of Contents 2 1. Introduction 4 1.1. Document Purpose 4 1.2. Intended Audience 4 1.3. Project Background 5 1.4. Purpose of the Business Requirements 5 1.5. Business Goals/Objectives to be achieved 6 1.6. Benefits/Rationale 6 1.7. Stakeholders 6 1.8. Dependencies on existing systems 6 1.9. References 6 1.10. Assumptions 6 2. Requirements Scope 7 2.1. In Scope 8 2.2. Out of Scope 8 3. Functional Requirements 8 3.1. Actor Profiles Specification 8 3.2. Essential Use Case Diagram 9 3.3. Essential Use Case Specifications 9 3.4. Function Hierarchy Diagram 11 3.5. Function Definition Report 11 3.6. Business Rules 12 4. Data Requirements 13 4.1. Data Architecture 13 4.1.1. Domain Class Diagram 13 4.1.2. Entity Relationship...
Words: 5662 - Pages: 23
...1.5 Explain how the requirements of security, data protection, copyright and intellectual property legislation may affect the production of business documents • The requirements of security, data protection, copyright and intellectual property legislation may affect the production of business documents. • Data protection-It is important that information is accurately and fairly processed. Certain documents should be authorised by a manager and produced or communicated on a secure system or database • Security- It is important that information does not breach security protocols. If security is breached, production may need to be minimised or stopped, wasting both time and money. Also, storing of business documents may need to be relocated. • Copyright-...
Words: 828 - Pages: 4
...writing by your assessor. Submit this document with any required evidence attached. See specifications below for details. Performance objective For this assessment learners are required to review existing policy documents and compare them to regulatory documents and current organisational usage. A report is required that outlines revised policy documents and describes the implementation process. Assessment description You are required to examine and review the MacVille policy and procedure documents(in the additional resources of your Student Workbook) to determine the shortfalls between required sustainable practices and documented approaches to the same. In doing this you will need to review current usage of resources to gain an understanding of potential for recommending change to organisational practices. After evaluation of this information, you will need to outline revised policy documents for MacVille together with a description of the approaches that can be taken to implementation of the revised policy documents. Procedure 1. Review the case study information provided (attached), policy and procedure documents (in the Appendices of your Student Workbook) and legislative and regulatory documents that describe compliance requirements for the business sector. The reviewing process of the current policies and procedures and case study of MacVille revealed that there are no sustainability policies and procedures within the business that directly link to a sustainable...
Words: 1106 - Pages: 5
...Chapter 5 Review Questions 1. Describe systems analysis and the major activities that occur during this phase of the systems development life cycle. During systems analysis, you determine how the current information system functions and assess what users would like to see in a new system. Requirements determination, requirements structuring, and alternative generation and selection are the three primary systems analysis activities. 2. What are some useful character traits for an analyst involved in requirements determination? Requirements determination is a crucial part of the systems development life cycle; therefore impertinence, impartiality, relaxing constraints, attention to details, and reframing are important characteristics. 3. Describe three traditional techniques for collecting information during analysis. When might one be better than another? Traditional techniques for collecting requirements include interviewing and listening, observing users, and analyzing procedures and other documents. Interviewing and listening involve talking with users individually or as a group to discover their views about the current and target systems; it also involves carefully preparing an interview outline and guide before conducting the interview. Interviews are best done when only a few people are involved, when you need open-ended questions or the questions vary from individual to individual, or when a more personal method is needed. 4. What are the general...
Words: 947 - Pages: 4
...PADMA ARYAL padmaaryal@gmail.com 646-701-4780 PROFILE | | Dynamic Business Analyst with over 6 years of professional experience in Software Development Lifecycle (SDLC) and business reengineering process, offering extensive experience in healthcare domain. Areas of expertise include HIPAA compliance ANSI X12 4010 to 5010 and ICD 9 to ICD 10, EDI transactions and Claims Adjudication process. Experience with FACETS and NASCO configuration, coordination of benefits (COB), Medicare and Medicaid programs; strong interpersonal communication, writing, presentation and collaboration skills. QUALIFICATIONS SUMMARY | | * Proven track record of delivering cost-effective, high performance technology solutions to meet the constantly changing business needs. * Demonstrated experience in gathering requirements and developing detailed functional specifications through JAD sessions, interviews, observation, and on site meetings with SME, business users & development teams. * Adept at writing business requirement documents (BRD), functional requirement documents (FRD), system requirement specifications (SRS), system design specifications (SDS) and other project related documents. * Expertise in conducting gap analysis, SWOT analysis, risk analysis, root-cause analysis and change management assessment. * Proficient in business process reengineering and Software Development Life Cycle (SDLC), including analysis, design, development, testing,...
Words: 2820 - Pages: 12
...TUTORIAL 3 There are several methods that systems analysts use to determine requirements for a proposed system. The requirements gathering techniques can be categorized into traditional, modern, or radical. The traditional requirements gathering techniques are interviews, questionnaires, , and documents analysis. The modern requirements determination techniques include Joint Application Design (JAD), group support systems, prototyping, and CASE tools. Business Process Reengineering (BPR) is a radical method for determining system requirements. Each of these approaches has advantages and disadvantages to system implementation and operation. 1. Briefly describe systems analysis and the major activities that occur during this phase of the systems development life cycle. (4 Marks) Answer: Systems analysis involves determining how the current information system functions and assess what users would like to see in a new system. Requirements determination, requirements structuring, and alternative generation and selection are the three primary systems analysis activities. 2. Describe THREE (3) traditional techniques for collecting information during analysis. When might one be better than another? (6 Marks) Answer: Traditional techniques for collecting requirements include interviewing individuals, interviewing groups, observing users, and document and procedure analysis. (a) Interview: Interviewing involves speaking...
Words: 689 - Pages: 3
...DOCUMENT TYPE DOC NO. REVISION Quality Management Policy TITLE ISSUED BY QMP-001 EFFECTIVE DATE 1.0 PAGE Q Pharma Quality System Manual rJ Boatman 16 Feb 2007 1 of 32 SUPERCEDES CSSC QSM-001 iPT QSM-001 QUALITY MANAGEMENT POLICY QUALITY SYSTEM MANUAL QMP-001 Rev. 1.0 Prepared by Date (Signed) Jeff Boatman, Director of Quality Reviewed by 01 Feb 2007 Date (Signed) Alexis Stroud, Compliance Manager Reviewed by 07 Feb 2007 Date (Signed) Raymond Roggero, iPT Business Unit Manager Reviewed by 2/7/07 Date (Signed) Robert Lorence, CSSC Business Unit Manager Approved by 9 Feb 2007 Date (Signed) Patrick Den Boer, President and CEO 16 Feb 2007 ©2007 Q Pharma Incorporated. Unauthorized reproduction or distribution prohibited. CONTROLLED DOCUMENT • VERIFY LATEST REVISION • PRINTED COPY IS UNCONTROLLED IF NOT STAMPED IN RED DOCUMENT TYPE DOC. NO. REVISION Quality Management Policy TITLE QMP-001 1.0 PAGE Quality System Manual TABLE OF CONTENTS 0. Page 2 of 32 1. 2. 3. 4. 5. 6. INTRODUCTION .........................................................................................................................4 0.1 General...............................................................................................................................4 0.2 Process Approach ................................................................................................................
Words: 10681 - Pages: 43
...continuing filing and disclosure obligations • you act as an adviser to an overseas company and are looking for guidance on registration and disclosure requirements in the UK GPO1 March 2015 – Version 3.1 Companies Act 2006 Page 2 of 22 Contents Introduction Chapter 1. Who needs to register? Chapter 2. Registration Chapter 3. Delivery requirements Chapter 4. Changing the accounting reference date or accounting requirements Chapter 5. Disclosure requirements Chapter 6. Insolvency, winding up and closure Chapter 7. Quality of documents Chapter 8. Further information This guide answers many frequently asked questions and provides information on completing the most commonly used filings relating to this area. The guide is not drafted with unusual or complex transactions in mind. Specialist professional advice may be needed in those circumstances. GPO1 March 2015 – Version 3.1 Companies Act 2006 Page 3 of 22 Companies Act 2006 Introduction This guide explains how to register an overseas company that opens an establishment in the UK. It also provides guidance on the disclosure obligations subsequent to such a registration. It outlines the documents you must send to Companies House and some of the important rules on accounting requirements, company names and trading disclosures. You will find the majority of the relevant UK law in the following places, • Part 34 Companies Act 2006(sections...
Words: 6462 - Pages: 26
...Stakeholders / Team Document History Approval Form A. Introduction Purpose Referenced Documents Requirements Issues B. Group Purpose and Objective Business Process / Need or Background Information Specification 1.1. Treatment Plan Goal Rating Module C. Ad Hoc Reporting Reporting Examples Data Dictionary D. Customer Communication E. Traceability Requirements to Specification Stakeholders / Team The following people are stakeholders or part of the team. Stakeholder Function Christy Winters Director of CQI for Families First Steve Walton Information Systems Coordinator Brent Blane Project Manager, QSI Doug King Business Analyst, QSI Document History Version Release Date Author, Reviewers Release Notes V1 Author: Doug King Reviewers: BA Team Approval Form Treatment Plan Rating Feature Specification Families First Project Information Client Families First Project Families First Version V1 Families First Qualifacts Systems Inc. 200 2nd Avenue South Nashville, TN 37201 By: By: Printed: Printed: Title: Title: Date: Date: Introduction Purpose This document details the business requirements and functional specifications for the following Feature. Group Description ECR Adding the treatment plan goal rating to a service document in the ECR Referenced Documents The following documents were referenced during...
Words: 865 - Pages: 4
...response. There may be additional Guidance in the Appendix of some documents, which should also be deleted once it has been used. Some templates have four levels of headings. They are not indented, but can be differentiated by font type and size: • Heading 1 – Arial Bold 16 font • Heading 2 – Arial Bold Italic 14 font • Heading 3 – Arial Bold 13 font • Heading 3 – Arial Bold Italic 12 font You may elect to indent sections for readability. |Author | | |Author Position | | |Date | | Version: 1.0 ( 2002 Microsoft Corporation. All rights reserved. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. Microsoft and Visual Basic are either registered trademarks or...
Words: 2271 - Pages: 10
...of the MIS team. The MIS is also a complement of those phases. As software is always of a large system (or business), work begins by establishing the requirements for all system elements and then allocating some subset of these requirements to software. This system view is essential when the software must interface with other elements such as hardware, people and other resources. System is the basic and very critical requirement for the existence of software in any entity. So if the system is not in place, the system should be engineered and put in place. In some cases, to extract the maximum output, the system should be re-engineered and spruced up. Major function: This step involves identification of potential projects in which the firm may engage. Some of the sources for project ideas include user departments, steering committees, top-level managers and brainstorming sessions. The guiding factors while identifying potential projects are the needs of the organization and the weaknesses of the current systems. After the identification of potential projects, the management conducts value-chain analysis on each project in order to rank the projects based on their viability. Factors to consider when selecting the ranked projects include, but are not limited to, the organization's environment and its needs. Projects selected should be capable of achieving the firm's business objectives. From a pool of identified...
Words: 1490 - Pages: 6
