Thanks for watching! Download the FREE USE CASE TEMPLATE here: www.bridging-the-gap.com/uctemplate/?KZbin&Functional%20Requirements%20and%20Specifications:%20A%20Quick%20Tutorial&Comments
@joelamouzou9762 жыл бұрын
Finally a tuto with an example, thank you !
@BridgingtheGapBA2 жыл бұрын
So glad you found this helpful!
@ungket58462 жыл бұрын
Thank you for this knowlage. It was very helpful for me when I try to make docment of my new sofware project. 🙏🙏🙏
@BridgingtheGapBA2 жыл бұрын
We are so glad you found this helpful! Good luck on your new project.
@rastcheck60376 сағат бұрын
Thank you. Very clear explanation. One question: is a Project Mamagememt waterfall process, in which phase should the requirements produce? Before the approval of the project, for example in the Business Case document? Or after the approval? Or both but a different level of details?
@BridgingtheGapBAСағат бұрын
Business analysis should be part of the project from beginning through implementation - at different levels and with different types of collaboration. Check out this video with a complete business analysis process as a framework: kzbin.info/www/bejne/mXmtnIOad9p5aqc&t
@cherinetkassu54423 жыл бұрын
Hey Laura 👋, It was a very greater and useful presentation. I will be looking for your videos furthermore. THANK YOU!!
@BridgingtheGapBA3 жыл бұрын
So glad you found it helpful! Be sure to browse this channel as there are many more valuable videos on business analysis techniques.
@NomsaPSmith2 жыл бұрын
Love your videos, very informative. Thank you
@BridgingtheGapBA2 жыл бұрын
We're so glad you found this and our other videos helpful in your career as a business analyst!
@CarelleKiam-he8yg9 ай бұрын
This video is great. I like it, thank U
@BridgingtheGapBA9 ай бұрын
So glad you found it helpful!
@robalan9975 Жыл бұрын
Very helpful and informative! Thank you for this resource!
@BridgingtheGapBA Жыл бұрын
You are so welcome Robert!
@abhishekjain86753 жыл бұрын
Thanks Laura 🙏🏻
@BridgingtheGapBA3 жыл бұрын
You are so welcomed!
@nanaabaasarewanaomi76463 жыл бұрын
Thank you so much, madam.
@sarahs14.00 Жыл бұрын
Thank you so much!!
@BridgingtheGapBA Жыл бұрын
You are so welcome!
@deenesbitt96743 жыл бұрын
Hi, your content is very insightful and helpful and I appreciate you sharing with the world ! I was wondering if you could explain briefly , how you use use case thinking and user story methodology to keep big picture in mind . I agree that user stories can cause you to lose sight of big picture . Thanks !
@BridgingtheGapBA3 жыл бұрын
Thank you so much for your positive feedback. We're so glad you are benefiting from our video content. Here is a video where Laura goes deeper on the relationship between use cases and user stories. kzbin.info/www/bejne/jJ_JZKudaNSMaqM&t
@1ancore2 жыл бұрын
Thank you for the free template and for the video, I learned some good points
@BridgingtheGapBA2 жыл бұрын
You are so welcome!
@phaedra426 Жыл бұрын
Really great, thanks for the examples.
@BridgingtheGapBA Жыл бұрын
You are so welcome Melanie!
@mrymzrzr4741 Жыл бұрын
Thank you so much was very helpful
@BridgingtheGapBA Жыл бұрын
We're so glad to hear that!
@drumsanddance Жыл бұрын
Hi Laura! I love your content and often view the videos. You have discussed the alignment between the business and technology. I'd love to hear from you where does UX design sit in this whole process?
@BridgingtheGapBA Жыл бұрын
We're so glad you find Laura's videos helpful! As a business analyst, we tend to think of UX designers as part of both the business stakeholder group and technical design/implementation group. Getting them involved early and throughout is key, when your organization is lucky enough to have them.
@sachinjagtap45283 жыл бұрын
Hi Could you explain what is intended use testing and functional testing
@rekkya10002 жыл бұрын
Amazing insights we'll done Laura. I bought your book and still refer to it after 8 years of being a BA thanks
@BridgingtheGapBA2 жыл бұрын
You are so welcome. And that's so great to hear about Laura's book - we're glad it's been so useful.
@paulallies2 жыл бұрын
Very helpful
@BridgingtheGapBA2 жыл бұрын
We're so glad to hear it's been helpful for you!
@purnimadevulaplli53283 жыл бұрын
Great explanation 👍🏻
@BridgingtheGapBA3 жыл бұрын
So glad you found it helpful!
@Ndjjrfjndkfncmfkffirjjfj3 жыл бұрын
Very useful for BAs. Thx 🙏
@BridgingtheGapBA3 жыл бұрын
So glad to hear it!
@m77ast3 жыл бұрын
I need a quick overview of all the docs needed in the full implementation cycle. I never write the docs but someone was asking. Are you able to provide different documents required at the different stages of a project.
@BridgingtheGapBA3 жыл бұрын
That's going to be highly dependent on the methodology in place at your company. But you can start with the BA process framework here: kzbin.info/www/bejne/mXmtnIOad9p5aqc
@bisiyahaya6142 Жыл бұрын
So the use case specifications are contained in the functional requirements or it's a stand alone document?
@BridgingtheGapBA Жыл бұрын
It depends on the BA and the project, but the most common practice is to have separate use case documents for each use case, and not a single big functional requirements document.
@bisiyahaya6142 Жыл бұрын
@@BridgingtheGapBA Thank you for your explanation and insights from your other videos. Here's my understanding, although I acknowledge that it could vary based on the organization and the project's specifics.⬇️ 1. Gather all necessary project requirements 2. Create a BRD covering the project's purpose (the "why") and how success will be measured. 3. Obtain sign-off from relevant stakeholders. 4. Develop a visual representation of the system's interactions using a use case diagram. 5. Create detailed specifications for each identified use case. 6. Include a use case narrative outlining the flow and interactions. 7. Develop test cases corresponding to each use case to ensure functionality and reliability. 8. Write user stories that condense user requirements and functionalities. 9. Support user stories with visual aids like wireframes, providing a tangible representation of the system's interface and functionalities.
@chaitaliscreation2 жыл бұрын
Hi can you please explain about technical business analyst documents, how to prepare DACT, TMRT, BMT, S2T from confluence given
@BridgingtheGapBA2 жыл бұрын
Chaitalis, Thanks for checking out this video. Those aren't acronyms in our vocabulary here at BTG. 🙂
@theresecagle67772 жыл бұрын
Laura I love your UDL design on this page. May I use a screen shot of your information for my Instructional Design masters portfolio course review on the best way to display UDL in eLearning? Our University is having functional transitioning issues in providing eLearning content displays that encourage engagement. Thank you for getting back to me.
@BridgingtheGapBA2 жыл бұрын
Hi Therese, Can you please clarify what UDL is and what page you are referencing?
@lilyazamanova36923 жыл бұрын
thanks a million!!
@mj-sj8of2 жыл бұрын
If you don’t have a technical background how do you know what the system will do and it’s limitations
@BridgingtheGapBA2 жыл бұрын
This is where collaboration with your technical team is key! But always start with end user goals.
@NCN358 Жыл бұрын
Is functional testing the same as task specification? I have a job application test but am confused .The test says task specification but can't find info on such
@BridgingtheGapBA Жыл бұрын
I haven't heard those terms used interchangeably before. Task specification sounds more like a project management activity. Good luck with your job application!
@mosesose64263 жыл бұрын
Thank you!
@akshaypatil8155 Жыл бұрын
Hello lady, is their a link or website where you have shared samples of BRD, FSD, usecase doc, user story doc etc.....
@BridgingtheGapBA Жыл бұрын
You can start here for our free Use Case Template: www.bridging-the-gap.com/uctemplate We do not offer a BRD or FSD as part of our free or paid offerings, as most BAs no longer use these longer documentation methods.
@lunarmodule64193 жыл бұрын
Interesting thank you.
@EmperorMingg Жыл бұрын
I’d disagree… the technical requirements are to define what’s needed; the functional specification defines how it will work
@BridgingtheGapBA11 ай бұрын
Yes - the functional specifications defines how it will work from an end-user/black box type of perspective.
@jagroop2003 жыл бұрын
Mam so we can say that use case is an alternative to BRD, FRD and SRS. Right ?
@BridgingtheGapBA3 жыл бұрын
Not exactly...A collection of use cases, and perhaps also business processes along with a scope document and data model would be.
@jagroop2003 жыл бұрын
Mam. Please tell difference between FRD and SRS
@BridgingtheGapBA3 жыл бұрын
It depends on your organization. Often an SRS is more technical and an FRD is what is described here.