IMAT5205: Systems Analysis And Design

8 Pages1703 Words134 Views

Systems Analysis and Design (IMAT5205)

Added on 2020-04-21

IMAT5205: Systems Analysis And Design

Systems Analysis and Design (IMAT5205)

Added on 2020-04-21

BookmarkRelated Documents

Running head: SYSTEM ANALYSIS AND DESIGNSystem Analysis and DesignName of the StudentName of the UniversityAuthor Note

1 SYSTEM ANALYSIS AND DESIGNTable of Contents1. Introduction......................................................................................................................22. What is a use case?..........................................................................................................23. Use cases are not inherently object oriented....................................................................24. Why is use case modeling important in object oriented approach..................................35. Importance.......................................................................................................................46. Advantages and Disadvantages.......................................................................................57. Conclusion.......................................................................................................................58. References........................................................................................................................7

2 SYSTEM ANALYSIS AND DESIGN1. IntroductionUse case generally explains the process of interaction of an actor or an external entity to aparticular system related to a particular business. It generally deals with the function of aparticular system provide an actor. Use case is generally employed to model the differentbusiness processes functional requirements of the system or the internal operations of the system.It describes the different functions required in a system or an application. However, uses casesare not object oriented. They have originated as a part of the object oriented development methodand therefore, use case modeling is very important in OO approach. There is nothing inherentlyobject oriented in relation to the use cases. It is generally employed for modeling of thefunctional requirements of a system or an application (Dennis, Wixom and Tegarden 2015). Theuse case is widely used for understanding the requirements of the object oriented softwaredevelopment and are commonly supported in the modeling languages. The report discusses theuse of use case modeling in Object Oriented (OO) approach along with its advantages anddisadvantages. 2. What is a use case? Use cases are generally a detailed description of the process by which a person uses orinteracts with a system to accomplish a certain goal. It is generally associated with the softwaresystems but can be used as a reference or clear understanding of any process. There are mainlythree elements of a use case, which are actor, system and goal. Actor denotes a user or a group ofusers that interacts with the system. System here refers to the process that awaits the outcomeand goal denotes the successful user outcome. A complex use case may also include otherelements such as stakeholders, preconditions and triggers as well (Kulak and Guiney 2012).

End of preview

Want to access all the pages? Upload your documents or become a member.

System Analysis and Design Solution Template

|1430

|55

Role of System Analyst in System Design

|1532

|143

System Analysis and Design Solution Template

|1847

|149

IMAT5205: Systems Analysis And Design Assignment

|12

|2002

|148

System Analysis and Design Solution Template

|1502

|307

System Analysis and Design Solution Template Assignment

|1780

|78

IMAT5205: Systems Analysis And Design