<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Erandi Galappaththi on Medium]]></title>
        <description><![CDATA[Stories by Erandi Galappaththi on Medium]]></description>
        <link>https://medium.com/@erandig7?source=rss-bd733e8ec725------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*34dUTF8AON3Euy1n.</url>
            <title>Stories by Erandi Galappaththi on Medium</title>
            <link>https://medium.com/@erandig7?source=rss-bd733e8ec725------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 01:46:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@erandig7/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Designing Use Case at once!]]></title>
            <link>https://medium.com/@erandig7/designing-use-case-at-once-722ebb7abccc?source=rss-bd733e8ec725------2</link>
            <guid isPermaLink="false">https://medium.com/p/722ebb7abccc</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[use-cases]]></category>
            <category><![CDATA[uml]]></category>
            <dc:creator><![CDATA[Erandi Galappaththi]]></dc:creator>
            <pubDate>Fri, 06 Jul 2018 08:29:44 GMT</pubDate>
            <atom:updated>2018-07-06T08:32:15.859Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6H92AKovP7Edt64jpURnCA.jpeg" /></figure><p>Why do we need use cases? Just think for a moment, there can be scenario that you have a clear picture of particular application or system. You are the person who is having overall knowledge of that and ideal expert for that. But when it comes to explain it to others might be difficult due to the functionalities and other complex relationships in it. It’s simply as you can’t express all the things in your mind about the system. At that moment, you can get an aid from use case diagram. By seeing the diagram, audience grabs overall idea and also it’s easy to manage the flow of the system when it describes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/852/1*aRvxo0TaPynuX-9n9Opkkw.jpeg" /></figure><p>This is really important in explaining an innovative idea to others and very helpful to convey an idea to other party.</p><p>Though use case is a high level diagram it describes complex ideas in very basic way.</p><p>Simply this is user perspective diagram of the system. Mainly consists 4 major components as follows:</p><ol><li>Systems (Boundary)</li><li>Actors</li><li>Use Cases</li><li>Relationships</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/511/1*hOE-DF2PVM_3UW96tXXRZQ.png" /></figure><p>Let’s get into the components of use cases. <strong>System </strong>is basically the application you want to build. It can be either web site, software, business process, application etc. System represents with red color rectangular in the above diagram. Every action happens with in the system should appear with in the rectangular.</p><p><strong>Actors</strong> are something or someone which use in the system to achieve its goal. It could be a person, organization, another system or external device. When dealing with actors it’s important to keep in mind that actors are always external to the system and needs to be located outside. Actors should be categorized always. For an example there can be several customers for the system, but all customers should represent as one actor in order to reduce complexity of diagram.</p><p>There are two types of actors in use cases.</p><ol><li>Primary actors</li><li>Secondary actors</li></ol><p>Primary actors are always initiating the use of system and secondary actors and just reactionary to the system. In visualization process, primary actors should always located in left side of the diagram and secondary actors in right side.</p><p><strong>Use cases</strong> are really represents an actions that subjects to the task which happens within the system. Use cases always should be located within the rectangular because those are internal parties of the system. When we come up with several use cases, it’s better to sort them in logical manner.</p><p><strong>Relationships</strong> are actually connectors between actors and use cases. Actors should link with use cases in order to initiate the actions within the system.</p><p>There are some types of relationships in use cases:</p><ol><li>Association</li><li>Include</li><li>Extend</li><li>Generalization</li></ol><p>We use solid line between actors and use cases to show association. <strong>Association</strong> signifies basic relationship or communication between actor and use case.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/341/1*8dYja0_sdPTqQsaiu-xkQQ.png" /></figure><p>Suppose that to execute one use case in the diagram needs another use case executed. First use case depends on second use case in order to complete its action. In this particular scenario, the relationship between two use cases becomes<strong> include</strong>. We use dashline arrow to show include and as well as labelled it as &lt;&lt;include&gt;&gt;.</p><p>Meanwhile, there is an important fact to keep in mind that you have to make arrow head always into included use case. For an example only after the login to the system, the password is being verified. So here login is base use case and verify password is included use case. You have to make and arrow head to verify password use case to make relationship between them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/461/1*04GNmDoVcyODm-L69TCDyA.png" /></figure><p>In <strong>extend</strong> relationship, base use case is executing, but extend use case can be execute or not. Actually to execute extend use case there are some other criteria to met rather than executing base use case. For an example when login to the system, if login fails system shows error message. Here login is base use case again and show error message is extend use case. Every time when login to the system, it doesn’t show error message. Its true that you need to login to the system to show the error message, but it doesn’t always happen. In these kind of scenarios extend relationship occurs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*OvUdgxMTHtG3koagxHo2Ag.png" /></figure><p><strong>Generalization</strong> here is same as inheritance. When two use cases have generalization, child use case inherits all the attributes of parent use case. For an example if you consider that one use case as “payment”, payment can either happens by cash or cheque. So there are separate two use cases as “pay by cash” and “pay by cheque”. Both these use cases become child to “payment” parent use case. In this scenario, generalization happens.</p><p>Now this is enough for you to draw a usecase! Cheers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=722ebb7abccc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>