BTC-202
Business Analysis for the IT Professional Training Class:
- Ways to Train:
- Live Classroom Class is delivered at a Centriq location with a live instructor actually in the classroom.
- Live Virtual Class Class is delivered live online via Centriq's Virtual Remote technology. Student may attend class from home or office or other location with internet access.
- HD Class Class is delivered via award winning HD-ILT at Centriq's facility. Students view the live instructor utilizing a 60'' HD monitor.
- Ways to Buy:
- Retail Class can be purchased directly via check, credit card, or PO.
- CV Centriq Vouchers Class is available for students using Centriq Vouchers.
- CP Centriq Choice Pass Eligible Class is available to students utilizing Centriq Choice Pass program.
| Start Date | End Date | Duration | Days | Start Time | End Time | Time Zone | Location | Ways to Train | Ways to Buy | Price | |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Request a Date |
The role of the business analyst is to gather and communicate high-level requirements to stakeholders and technical staff. Update your skills with this five-day class at Centriq.
Audience
- New business analysts
- Experienced business analysts seeking to update their skills.
- Project managers who incorporate business analysis roles in their projects.
- Managers that have business analysts on their staff.
- Programmers being tasked with requirements gathering and writing.
- Software testers who would like to apply structured requirements to test case design and development.
Prerequisites
No technical skills are required.
Course Completion
At the completion of this course, the student will be able to:
- Describe the relationship between project management and business analysis.
- Gather and document user requirements.
- Model the business using business analysis techniques.
- Understand how to define all types of functional and non-functional requirements.
- Understand how to write a use case model.
View the Business Analysis for the IT Professional Training Course Outline
Requirements Gathering
- Core concepts
- The business analyst role
- What are requirements?
- Requirement priority
- Requirement types
- Functional requirement levels
- Overcoming objections
Enterprise analysis
- Requirements planning and management
- Problem solving
- Identify stakeholders and users
- Gain agreement on the problem definition
- Understand the root causes
- Requirements strategy
- Traceability
- Prioritization
Elicitation
- User involvement
- Barriers
Elicitation techniques
- Brainstorming
- Document analysis
- Focus groups
- Interface analysis
- Individual / Group interview
- Observation
- Prototyping
- Requirements workshops
- Survey/questionnaire
Elicitation techniques - special
- Pilot experiments
- XP Story telling
- Similar companies
- Asking suppliers
- Reviews
Requirements documentation
- The requirements management plan
- Report structure
- Interim report types
- Business process analysis
- Object oriented analysis
- Determine system constraints
- Validation
- Verification
- Data and behavior models
Requirements communication
- Grouping logically
- Sequence
- Emphasis
- Design principles
- Requirements tools
- Software
- Selection
Requirements writing
- Why written requirements?
- Extension of knowledge
- Consistency
- Quick overview
- Protection of intellectual property
- Communication
- Understanding
Technical writing
- Writing is a craft
- Write for humans
- Create lists
- Form follows content
- Organize details
- Reinforcement
- Use relevant text
- Completeness counts
- Use business terminology
- Use consistent terminology
- Assume a friendly reader
How to state requirements
- Present tense
- Imperative
- Modal verbs - must, shall
- Definitions - list or glossary item
- Categorize by entity in requirement
Ordering
- Requirements pattern
- Writing taboos
- Too little information
- Too much information - conjunctions
- Useless information - negative requirements
- Requirement quality criteria
- Testable or verifiable
- Consistent
- Correct
- Complete
- Unambiguous
- Ranked
- Modifiable
- Traceable
- Feasible
- Independent
- Necessary
- Non-redundant
- Terse
- Understandable
- Measurable or specific
Business rules
- Qualities
- Using a table of business rules
Rewriting user needs into requirements
- Glossary
Use case basics
- History
- Definition
- Domains
- Use case styles
- The formal use case process
- Use case names
- Use case levels
- Actors
- Use case validation
- Use case diagrams
- Prioritization
Use case detail
- Write the basic flow of events
- References
- Write the top alternative flows
- Capture pre-conditions and post-conditions
- Document any special requirements
Use case structuring
- The grouping use case
- The partial scenario use case
UML - Use case diagram symbol reference
- Icons
- Relationships