Wow, I still found this helpful. After 6 years, it was uploaded on KZread. Thank you, sir, for sharing your knowledge

@ltlacademy6129

2 жыл бұрын

You are most welcome

Thank you for this video. Needed to brush up on my understanding of use cases and this video is exactly what I needed!

@ltlacademy6129

Жыл бұрын

Thank you. Glad that the video still proved useful. 🙏

Can you please tell me ow to link generalization in use case description?

This has been a great refresher thank you!

@ltlacademy6129

2 жыл бұрын

Thank you very much for the comments. I might now actively devoted more time on this channel now that I have retired. 😀

Hi sir if I an administrator can delete,import or create data here is 3 points have to be described in description so here what can be the alternative flow

Thank you so much for this breakdown

@ltlacademy6129

Жыл бұрын

Glad it was helpful!

Thank you! This is such an amazing explanation. Very good job! You deserve my tuition money😅

@ltlacademy6129

Жыл бұрын

😀 Thank you very much for your awesome feedback! Do like and subscribe to the channel for future upcoming presentations. 🙏

@tanmelianiputri

Жыл бұрын

@@ltlacademy6129 yes sir, i've already subscribed😀👍

Thanks, nicely done

@tctan23

5 жыл бұрын

Ross Gerard Thank you. Appreciate it

Such an informative video. Thank you!

@ltlacademy6129

2 жыл бұрын

Thank you for your feedback

I don't think that we need to add "extends" and "includes" relationships into the specification in textual format. These relations are already documented in use case diagrams why would you clutter the specification with additional text? When you write a document you should consider who is the reader and how he will read it. Obviously the reader starts to read the UML diagrams first. And he will see that there is a "extends" or "includes" relationship. And then he will find your specification and read it already knowing it "extends" something or it "includes" something.

Thank you sir for the video!

@ltlacademy6129

Жыл бұрын

Thank you for watching. Hope you found it useful.

This made my life easy. Thank you.

@tctan23

Жыл бұрын

Hi, I am glad you had found this useful.

Another question can I include the "included" and "extended" use case in the Alternate Sequence of the Base Case?

@ltlacademy6129

2 жыл бұрын

There are no reasons why they cannot be used as you asked.

@johngeronimo8821

2 жыл бұрын

@@ltlacademy6129 thank you because sometimes you can choose to the excluded cases

I think it was confusing when you switched the base use case to the extended use case and vice versa. Anyway, I learned a lot. Thanks

@ltlacademy6129

2 жыл бұрын

Thank you for your feedback. I will review the slides.

Thanks for everything

@ltlacademy6129

2 жыл бұрын

Thank you very much for your feedback.

It will be helpful if you upload the lecture as pdf and put a link in the description.

@ltlacademy6129

2 жыл бұрын

I will take note of this. Thanks for the feedback.

one project can have many use cases or only 1 use case?

@tctan23

5 жыл бұрын

A project can have many use cases. A use case is a function of a system you are designing and implementing

Hello you can teach well, you should do more videos...

@ltlacademy6129

2 жыл бұрын

Thank you so much for you encouragement. And seriously considering doing so as I had retired from full time teaching.

fking great

this is ery good thank u

@ltlacademy6129

Жыл бұрын

Thank you very much. I will be uploading more videos 😀

I have a question is Included Use Case is same as Dependency?

@ltlacademy6129

2 жыл бұрын

Well you can think of it like that. Include use case are a set of common business functionalities which can be used (hence included) in many other business processes

very clear

@ltlacademy6129

2 жыл бұрын

Thank you for your feedback

You should make more videos man

@ltlacademy6129

Жыл бұрын

Thank you very much for your encouragement! Yes I am in the process of making more videos on different topics.

hi,nice one.Cld you pls help me with user stories

@tctan23

5 жыл бұрын

Pradeep M Hi, user stories are used in the context of Agile. It does not have main Nor alternate flows and you basically write a short description of the feature or function or build. There are not standard format for writing user stories but there are guidelines.

Can you do a use case that includes a case study on a software redesign

@ltlacademy6129

Жыл бұрын

Hi, my apologies, I didn't quite understand your question.

pak apip ribet bat segala nyuruh bikin use case deskripsi, pusing boss

View dashboard ka description batha do Business rule

@ltlacademy6129

Жыл бұрын

My apologies, I can't read the comment

It would be appreciated if you pl speak slow.

@logs

6 жыл бұрын

He talks normal lmao, you need to buy new ears.