18 years of proven training for business systems analysts in requirements and testing
IIBA Endorsed Education Provider

The purpose of an iterative development approach is to separate a development project into logical and manageable units for incremental delivery.  The completion of each iteration adds to the knowledge about the system being developed and reduces the risk when progressing to the next iteration.  It also provides a repeatable method for business system development.  It provides business user sign off and approval before continuing to commit resources to the project.

 

Reusability is also described throughout the system development process.  Reusing previously developed parts in a product is a significant way of decreasing the product’s life cycle cost.  Reuse in software engineering means deliverables that can be reused later.  This includes all the information and knowledge that has been developed, such as; system architectures, development methods, program code and completed algorithms.

Requirements Gathering & Writing Class

The Requirements Gathering and Writing class focuses on how to gather and write the different levels of requirements.  After attending Pierson’s training, customers have achieved a 30 – 40% time and cost saving in the requirements phase.  The class teaches how to implement UML and use case best practices for requirements gathering and writing for enhancements and new software development projects.  The workshop is one third lecture and two thirds hands on exercises for writing project scope definitions, business requirements and functional specifications requirements.

 

The seminar focus is on:

 

·         Understanding the different levels of requirements

 

·         The requirements management process

 

·         Characteristics and guidelines for writing effective requirements and use cases

 

·         Communication techniques for gathering requirements

 

·         Writing skills and instructions for writing successful scoping, requirements documents and detailed requirements

 

·         Practical exercises in scoping, business objectives, functional requirements, non-functional requirements, use cases and screen and reporting specifications

 

·         Writing and critiquing use cases and requirements using guidelines and checklists



Schedule

Date: June 2 – 4, 2010
Time: 1:00 pm to 5:00 pm EST
Duration: 3 half day sessions
Cost: $750.00
PDUs: 12
CDU’s towards CBAP recertification: 12

Register

Contact us to Register for the Requirements Gathering & Writing Virtual Class

Cost: $750.00

·         Live Instructor-Led Interactive sessions (4 hours per day over a 3 day period)

·         Training material presented via the web and live interactive instruction by phone or the web

·         Interactive exercises both in groups and individually

·         All participants receive printable .pdfs of materials

·         PDUs, CDUs and Certificates of successful completion are provided

Questions? Call or Email at 203- 322-1606 jmatthews@piersonrequirementsgroup.com

Click here to view the agenda

 

Instructor: Joy Matthews, Pierson Requirements Group, Inc.

Joy is the co-founder of Pierson Requirements Group which specializes in business systems requirements analysis and design best practices. Joy provides corporate training and consulting services to companies around the world and has assisted to implement requirements management best practices at hundreds of organizations in requirements gathering, requirements and system design methodologies.  Joy has over 20 years experience in Applications Development, Business Analysis, Requirements Management and Software Testing.

List of interview questions to define the user requirements for the new EDW

 

What data will go in the warehouse?

How will they use that data?

 

What Type of Data is needed?:

What information is important to access?

 

Sources of Data: What data is needed from excel format, etc.

 

What type of reporting is needed? 

 

What is the method of accessibility?

 

Technical Questions:

What questions/problems you would like to be answered by mining in EDW?

 

How many years of information would you like to store?

 

How often the data should be refreshed in the EDW?  How often to load data, weekly, monthly?

 

What kind of reports you would like to see?  What kind of information is needed? i.e.  HR data- turnover from start date to end date.

 

What format you would like to see your reports? Pie chart, bar chart, etc.