Functional requirements often form the core of a requirements document. The traditional approach for specifying functionality is to specify each function that the system should provide. Use cases specify the functionality of a system by specifying the behavior of the system, captured as interactions of the users with the system. Use cases can be used to describe the business processes of the larger business or organization that deploys the software, or it could just describe the behavior of the software system. We will focus on describing the behavior of software systems that are to be built.
Though use cases are primarily for specifying behavior, they can also be used effectively for analysis. Later when we discuss how to develop use cases, we will discuss how they can help in eliciting requirements also.
Use cases drew attention after they were used as part of the object-oriented modeling approach proposed by Jacobson [56]. Due to this connection with an object-oriented approach, use cases are sometimes viewed as part of an object-oriented approach to software development. However, they are a general method for describing the interaction of a system (even non-IT systems). The discussion of use cases here is based on the concepts and processes discussed in [24].
Posts
Very Impressive Business Analyst Tutorial. The content seems to be pretty exhaustive and excellent and will definitely help in learning Business Analyst. I'm also a learner taken up Business Analyst and I think your content has cleared some concepts of mine. While browsing for Business Analyst on YouTube i found this fantastic video on Business Analyst. Do check it out if you are interested to know more.:-hhttps://www.youtube.com/watch?v=ndDJgKFKOu4
ReplyDeleteThank u so much for the information
ReplyDelete