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

Having a person on staff with the training to be able to identify any issue and point out all opportunities for growth in your company is an invauable asset. However, most companies, especially smaller companies looking to grow, do not have the resources to make such a position available full time. Instead they find it prudent and economical to hire a business analysis company to do these things for them.

Pierson Requirements Group offers a multitude of ways to do just that. This company will assess every single area of your business and find out if there are any gaping holes or even small leaks so that any problem is found and corrected as soon as possible. This may mean hiring more staff, letting some go, re organizing who does what and almost always involves more focused training.

Trusting a company like Pierson to have your best intrests in mind is the key to a good working relationship, Pierson will answer any questions you or your staff may have before, during, and after your analysis begins. Find out if the methodology used by Pierson is something your company can benefit from by contacting them today

Some of the companies that have taken advantage of Pierson’s experience are:

Nationwide - “Pierson provided the 4-day Requirements Gathering & Writing Training Seminar using JAD, Use Cases and UML. The Business Analysts, Project Managers and Quality Assurance Testers were trained. Also conducted was the User Acceptance Testing Training Seminar for the Testing staff.”

Prudential - “Pierson trained over 40 Project Managers, Technical Leads and DBAs in JAD Facilitation & Requirements Gathering using Data Techniques.”

, ,
Pierson’s training provides a framework for project teams that promotes development iterations throughout the life cycle of a project using a RAD/Agile software development approach. NEW Virtual Instructor-Led Training is a time efficient and cost effective way of delivering training to individuals and groups of attendees without travel. When we use Web Conferencing instead of traveling, we use less gasoline and we reduce our impact on our environment. Web Conferencing is a green technology. Instructor Led Classroom Training is also available for classes that require a face-to-face format to improve facilitating, requirements gathering and conducting effective meetings skills. All of Pierson’s training can be conducted on-site.
One such seminar offered is the Writing Effective Requirements Training Seminar. It’s a three day seminar who’s complete breakdown can be found on the Pierson website. Some of the Description is as follows:

The class focuses on industry standards and best practices for writing requirements needed for project scope definition, requirements and documenting the system specifications necessary for IT projects. The seminar focus is on:

  • Understanding the different levels of requirements
  • The requirements management process
  • Characteristics and guidelines for writing effective requirements
  • Communication techniques for gathering requirements
  • Writing skills and instructions for writing successful scoping and requirements documents
  • Practical exercises in writing problem statements, b
  • usiness objectives, high-level requirements, non-functional requirements, screen and reporting specifications
  • Writing and critiquing use cases and requirements using guidelines and checklists

The objectives of the seminar are to:

  • Define best practices and standards for writing requirements and solutions documents
  • Provide practical exercises for using requirements gathering techniques using UML diagrams and use cases
  • Writing and critiquing requirements and system specifications using industry standards and best practice guidelines and checklists
,

Business Analyst Training is a way of targeting learning for exactly what your employees need. Pierson Requirements Group is a company who will provide business analysis training courses either on or off site to aid you in making your company as effective as possible. In order to take your business’ services to the next level you have to pinpoint your weaknesses and then create training classes and software to strengthen those areas.

Their Joint Application Development (JAD) which is used as a way to bring together the teams your company uses to design technical and creative aspects and the realities of the business world to create a round-table type discussion forum workshop to find out exactly what is needed in your field and make sure that your software is going to cater to those needs. This process saves time and money that is valuable during the upstart of any business.

They aim to cover every area of:

  • project management
  • business analysis
  • system specification
  • and more

Trusting a company like Pierson to have your best intrests in mind is the key to a good working relationship, Pierson will answer any questions you or your staff may have before, during, and after your analysis begins. Find out if the methodology used by Pierson is something your company can benefit from by contacting them today.

, ,

The Pierson Requirements Group has been a consulting and training company since 1990 and they’ve helped many businesses realize their potential by using practices to uniquely steer your company down the road to success. Their business analysts can help you take your idea from inception to full fruition in a clear and concisely planned way which will aide the smooth running of your ship.

By taking the business analysis training courses offered at the Pierson Requirements Group website you are equipping yourself and your staff to be the absolute best in the specialized world of your field. Sparing no expense you will also utilize every penny of your investment for the most excellent training available.
Some of the companies that have benefited from the business analysis training courses are:
  1. Hallmark
  2. Experian
  3. Dell Professional Services
  4. The US Department of Energy
  5. the list goes on!
By utilizing their business analysis training courses you can learn the best business practices for whatever your plan needs to get started. They offer seminars on Agile Projects, Acceptance Testing, JAD Techniques and many many more. Their Consulting services includes mentoring, methodology,process analysis and improvement and even outsourcing facilitating.
, ,

Iterative Development is a process that speeds the delivery of functionality to end-users by segmenting a system into pieces for delivery, rather than delivering all of the system functionality in one large implementation. The iterative process utilizes a spiral methodology and is also customer driven following an evolutionary process using continuous application engineering in a timeboxed fashion with a dedicated professional team. The goal of the iterative approach is to reduce the time between requests and delivery of Business Application Systems. Some of the primary characteristics of iterative development projects are:

 

·         There is a strict deadline for basic functionality

·         Can be released in increments

·         Uses techniques such as time-boxing, dedicated teams and focus sessions

·         Business users are involved throughout the project and JAD is used

·         Total project time is usually 3 - 6 months

Roles

 

The execution of an Application Project can involve a number of different actors, each with a specific role and set of responsibilities. The following table defines all the different roles and responsibilities that can be found on an Application Development Project. These roles always exist although the size and characteristics of the project may cause the same person to carry out more than one role.

 

Add and remove roles as appropriate.  Make sure the responsibilities of each role are clearly understood.  It is as important to list client responsibilities to ensure client resources have the appropriate authority.

Role

Responsibilities

Roles

 

 

 

  Project Manager

Produce Project Definition Document.

Manage project schedule.

Manage project budget.

Manage change, issues risk and status.

  Technical Manager

Schedule and manage day-to-day development activities.

Resolve technical issues.

  Test/QA Manager

Define system test plan & test cases.

Execute system test plan.

Schedule testing resources.

Ensure application adheres to standards.

  Business Analyst

Analyze and document client requirements.

  Developer

Produce Prototype (optional).

Produce Design Document.

Code the application.

Unit test code.

Fix bugs in a timely manner.

  Tester

Test the application to ensure it complies with the Requirements & Design Documents.

 

 

<Client> Roles

 

  Sponsor/Champion

Sign-off on major deliverables and budget.

Participate in phase-end reviews.

Assign client resources to the project.

Eliminate roadblocks and motivate staff.

  Client Project Manager

Primary point of contact for Hallmark.

Sign-off on major deliverables.

Approve change requests & change budget.

Participate in phase-end reviews.

Coordinate client meetings, participation in workshops, training and status meetings.

  Other Client Representatives

Participate in analysis & design workshops.

Ensure the requirements specification meets the needs of the organization.

Participate in User Acceptance Testing.

 

 

TBD Roles

 

  Rollout manager

Plan and manage installation activities.

Plan/coordinate conversion activities.

  Support manager

Provide ongoing product support.

  Training manager

Develop training plan (with client lead).

Develop training material.

Train employees on the system.

  Documentation manager

Develop user documentation & help.

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.

 

Use Case Template

Use Case #

#1

Author:

Author’s name

Iteration:

Filled (outlining the high level business requirements and identifying the alternate and exception scenarios)

Finished- completed in the Functional Specification to identify the detailed system requirements for the use case and how the  user interaction with the system should work

Name:

Use case name Verb noun

Category:

Category name – optional; use this field only if you’ve divided your use cases into functional groups (or categories).

Actor(s):

 End users performing this activity and/or systems that interface with this activity.

Description:

This use case describes…provide a brief summary of the use case.

Pre-Conditions

List any pre-conditions here in a bullet list.  What are the state of things prior to executing this use case?  What conditions must be true before this use case begins?  A pre-condition is a constraint that must be true before this use case can operate.  Often, other use cases are stated as pre-conditions.

E.g. database initialized, record already found, security established

Assumptions

Items that are outside the control of development (including the out of scope) AND must be in place before the use case can run.

Business Trigger

What is the business event that causes this use case to occur?

Flow of Events (Basic Path)

Step

Action 

This is the primary flow.  Supply the detailed flow descriptions here in a numbered style text.  You should have 3 -9 steps.  Document how the use case starts and ends.  Indicate what the customer wants the system to do.  Use the active voice.  The actor and the system perform the actions.  Use present tense.  Name the actor based upon the role that the actor represents in the problem domain.  The flow should contain the step #, Actor Action, System Action, Screen (if available) and Event.  The events are documented to better understand the major functions/processes the Actors are performing on the system. This information will later be used to create the event list template.

1

The use case begins when…

2

 

3

 

4

The use case ends when…

Post Conditions

List any post conditions here in a bullet list.  What are the state of things after you execute this use case?  What is the next step?  Indicate the successful post-conditions and the failed post-conditions.  E.g. Client added to the database, Resource ‘X’ assigned to project ‘Y’.

Alternate Scenarios

Step

Branching Action

1

Alternate flows are generally considered to be choices that are intentionally made by an actor.  Each alternate flow is labeled with an identifier in the form  A#1.  Each alternative flow is also named with a one-sentence description.  Each alternative flow has a set of steps numbered in sequential order.  It then statements are alternate scenarios.

Note:  the step number here refers to step in the basic path where the alternate scenario branches off of the basic path.

2

 

3

 

Exception

Scenarios

Exception flows are generally considered to be choices that are not intentionally made by the actor and normally result from significant error conditions.  What are the what ifs?  The errors that can happen.  Each exceptional flow is labeled with an identifier in the form E#1.  Each exceptional flow is also named with a one-sentence description.

Business Rules Validated

List any business rules associated with this use case, e.g. guests cannot order a quantity greater than 3 of any one item; to calculate tax in the state of Massachusetts, multiply the total by .05.

Special Requirements

In many situations you will uncover requirements that do not fall within the scope of the use case description, list those here, e.g. volumes, usability issues, time constraints, security issues.

Issues

List any questions and issues to be addressed by the end of the discovery stage.

Design Comments

This section is optional.  State any design comments and/or suggestions and clearly identify them as either comments/suggestions or as customer-stated, design constraints.  This can include suggestions or constraints on the GUI as well as other parts of the system.  These will be used as considerations by the design team when designing the classes that will implement the use case.  Also can use this section to document system rules.