Business Analysis and Iterative Methodologies

BA-EXPERTS2012-10-02

Business analysis#requirements#iterative system development#RUP#SDM#SDLC#system development life cycles#iterative#business analyst#Iterative And Incremental Development#Computer Science (Field Of Study)

12K views|11 years ago

💫 Short Summary

The video discusses iterative and spiral system development methodologies in business analysis, focusing on planning for change and continuous improvement. It highlights IBM's Rational Unified Process and ERUP as examples, emphasizing the use of the Unified Modeling Language (UML) in object-oriented system development. Use cases are identified as a common method for capturing solution requirements in information technology, with business analysts working with subject matter experts to develop prototypes and ensure stakeholder agreement on requirements. BAs also play a role in acceptance testing tasks during the transition phase.

✨ Highlights

📊 Transcript

✦

Overview of iterative and spiral system development methodologies in business analysis.

00:41

IBM's Rational Unified Process and ERUP are highlighted as examples of iterative methodologies that assume change and plan for it.

The iterative approach involves creating the ultimate solution in releases or iterations, with overlapping phases and continuous improvement.

Business analysis activities like modeling and requirements analysis cross phase boundaries, with a focus on separating activities from phases in the iterative approach.

The Unified Modeling Language (UML) is mentioned as a key technique for supporting object-oriented system development in iterative methodologies.

✦

Overview of use cases in information technology documentation.

03:22

Use cases focus on a single application usage by a single user, ideal for expressing functional requirements.

Business analysts utilize UML for design flexibility and to cover requirements components.

BAs collaborate with subject matter experts to develop prototypes and preliminary user manuals.

BAs ensure stakeholder agreement on requirements and provide clarifications to developers during construction.

00:00[Music]

00:14hello i'm tom hathaway

00:17i'm wearing my ba hat so let's talk

00:19business analysis

00:21in this nugget we're going to talk about

00:24iterative or

00:25spiral system development methodologies

00:27what they are

00:29and how they affect you when you are the

00:31one wearing the ba hat

00:34iterative methodologies assume the

00:36change will happen

00:38and plan for it a widespread iterative

00:41methodology

00:41is ibm's rational unified process or

00:45erupt a major feature of the iterative

00:48approach

00:49is the assumption that the ultimate

00:50solution will be created in a series of

00:52releases

00:53or iterations

00:56your role as the business analyst and we

00:58will refer to as

01:00the ba regardless of what your actual

01:02job title is

01:04in iterative methodologies in each phase

01:06is similar to your role

01:08in the waterfall approaches

01:11the initial phase of any project is the

01:13inception phase

01:15during this phase the ba will elicit and

01:17capture the vision statement

01:19and high level business goals and

01:20objectives you might create the business

01:23case for the project using problem

01:25analysis

01:26cost benefit analysis and business and

01:28stakeholder requirements definition

01:30techniques

01:32the project is then broken down into a

01:34series of iterations

01:35each of which has a single key objective

01:39each iteration goes through potentially

01:41multiple elaboration

01:43construction and transition phases to

01:46ultimately deliver a release that

01:47represents a preliminary

01:49version of the final product

01:53the phases often overlap during the

01:54iteration the next release would then

01:57build on the existing version

01:59and add further functionality or

02:00features in a cycle of continuous

02:03improvement

02:05typical business analysis activities

02:07such as business modeling

02:09requirements elicitation and analysis

02:12requirements decomposition etc

02:14cross-phase boundaries

02:18for example it is not uncommon for a

02:20business process model to be initiated

02:22during the inception phase at a high

02:23level

02:24and then be decomposed incrementally

02:26during the elaboration phases over a

02:28series of iterations

02:30separating activities from phases is one

02:32of the hallmarks of the iterative

02:34approach

02:36in the elaboration phase the ba defines

02:38solution requirements

02:40one of the major techniques that has

02:41evolved to support object oriented

02:43system development

02:44and by association iterative

02:46methodologies

02:48is the unified modeling language or uml

02:52the uml is a very complex set of

02:54diagramming symbols

02:55which makes it relatively difficult to

02:57learn and requires highly abstract

02:59thinking

03:00it is being applied successfully by

03:02developers in the software development

03:03process on a regular basis

03:05but due to its complexity is seldom used

03:08in the business analysis arena

03:11one exception to that rule is the use of

03:13a concept called use cases

03:16business use cases are a very common

03:18documentation method for capturing the

03:20solution requirements for an evolving

03:22information

03:22technology solution a major attribute of

03:26the use case

03:27is the focus on a single usage of the

03:29application by a single user this gives

03:32the ba

03:33a phenomenal tool for expressing

03:34functional requirements

03:37by design the uml allows for extensions

03:41giving it a great degree of flexibility

03:43and giving the ba

03:44opportunity to add dimensions to cover

03:47the requirements components

03:50furthermore in the elaboration phase the

03:53ba together with the subject matter

03:55experts or smes

03:57develops prototypes if needed and

03:59sometimes creates preliminary user

04:01manuals

04:02it is also the ba's responsibility in

04:04this phase

04:05to have agreement from all stakeholders

04:07regarding the requirements

04:10in the construction phase the ba has to

04:12be available to the developers

04:14for any requirements clarifications that

04:16are needed

04:18in the transition phase the ba might be

04:20tasked with acceptance testing tasks

04:22such as creating test plans test cases

04:25and

04:26test scripts whether or not the ba is

04:28involved in testing is an organizational

04:30decision

04:32a fundamental business analysis task in

04:34this phase

04:35is to define transition requirements and

04:38help the development team to transition

04:40the system

04:41from development to production after

04:43completion of the transition phase

04:45the next iteration for this project

04:47starts and all business analysis

04:49activities are repeated

04:56[Music]

05:01you

🎥 Related Videos

Make Money Online With The EASIEST ChatGPT Side Hustle ($680/Day) For Beginners!

Making a Macintosh Studio

How glowing up ruined my life

Easy Etsy Product Photography at Home with an iPhone!

Why Are You Making Programming HARDER?

How to Make Money on YouTube Without Making Videos (The REAL Way)

🔥 Recently Summarized Examples

4 Steps to Master Any Complex Skill (quickly)

40 Years of Fitness Experience in Less Than 11 Minutes.

Gun Controlling Media Makes FATAL Mistake... They Have Tied Their Fate To Biden's & Gun Rights Win

GET READY! Palantir Is Officially The Next Nvidia.

Abundant Thinking: The Hidden Key to Get Everything You Want (Audiobook)

The Coming Demonic Invasion (Revelation 9:12–21)

View original video