<?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 Ertuğrul Yalçın on Medium]]></title>
        <description><![CDATA[Stories by Ertuğrul Yalçın on Medium]]></description>
        <link>https://medium.com/@yalcine_99772?source=rss-668bdeb5c3c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*DIW6b-uA62yjqrT1</url>
            <title>Stories by Ertuğrul Yalçın on Medium</title>
            <link>https://medium.com/@yalcine_99772?source=rss-668bdeb5c3c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 06:56:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yalcine_99772/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[Asking right questions]]></title>
            <link>https://medium.com/adessoturkey/asking-right-questions-5627f5748622?source=rss-668bdeb5c3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/5627f5748622</guid>
            <category><![CDATA[requirements-elicitation]]></category>
            <category><![CDATA[requirements-engineering]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[asking-right-questions]]></category>
            <dc:creator><![CDATA[Ertuğrul Yalçın]]></dc:creator>
            <pubDate>Mon, 27 Dec 2021 14:41:25 GMT</pubDate>
            <atom:updated>2021-12-30T13:23:24.204Z</atom:updated>
            <content:encoded><![CDATA[<p>Regardless of your experience, the question of what to document arises frequently and, at times, is heatedly debated. Different methodologies encourage or challenge the idea of capturing what is happening, especially given how quickly things change in a business environment. Will what you’ve written be out of date by the time someone reads it?<br>One point on which all parties agree is that requirements are frequently elicited from stakeholders and shared with project teams in order to deliver the solution. The BA is typically found in the role of eliciting requirements because not only is the facilitation skill set of a BA important, but the unbiased solution view of a BA becomes extremely valuable toward ensuring that the team is heading in the right direction in order to accomplish their goals.</p><h3>Why are we doing these?</h3><p>Ok, we need to capture the requirements and document them to some extent in various ways, with this, being convinced of the reasons will provide a driving force during the whole journey. Here are some <strong>essential reasons why requirements should be captured and documented</strong>:</p><p><strong>We all forget things:</strong> business stakeholders occasionally forget what they communicate to solution teams, and solution teams occasionally forget the requirements. This results in <strong>considerable time</strong> <strong>being wasted</strong> as team members attempt to recall what was discussed. The difficulty is in capturing the outcome of any discussions, not necessarily all the meeting minutes that led up to decisions.</p><p><strong>Verbal communication is open to misunderstandings: </strong>As a child, do you recall playing the telephone game? When multiple people are involved in the transmission of a message, the message changes significantly. Requirements are highly specific, detailed items that can easily be modified by changing the wording or phrase used. You want to <strong>ensure that everyone is literally on the same page </strong>with regards to the representation they are envisioning. Verbal communication can be ambiguous.</p><p><strong>We occasionally respond differently to the same question when asked twice:</strong> Business stakeholders frequently provide contradictory responses to the same question at different points in time. This could be because a stakeholder <strong>has had time to reflect further on the issue following the initial discussion</strong>, or it could be that a stakeholder has simply changed his or her mind. Before documenting a requirement, BAs are experts at asking the same question multiple times to ensure that the stakeholder has truly answered definitively.</p><p><strong>Writing itself forces us to consider it more carefully than we do when we just say it:</strong> For instance, a stakeholder may state that he desires a report that displays totals by month, but upon viewing a report layout with 12 columns crammed together, he realizes that he actually desires only the last three months.</p><p><strong>It ensures precision and help us identifying undocumented requirements and assumptions:</strong> When a user makes a request, have someone other than the user write it down, such as the BA. After that, have the user verify its accuracy. This will draw attention to ambiguity and inadequately defined requirements.</p><p><strong>New people joining a project need to quickly get familiar with the goal, the approach, and the requirements that the team is working on:</strong> Having the requirements easily accessible to any team member at any time keeps both new and assigned team members on the same page.</p><h3><strong>Core Requirements Components</strong></h3><p>When describing a business, there are four basic requirements components: <strong>people, information, processes, and rules.</strong></p><p><strong>The people</strong> component may include individuals or departments inside or outside of the organization (called external agents or actors). The people component also represents systems or other business areas.</p><p><strong>Information</strong> is data and all aspects and attributes of them.</p><p><strong>Processes</strong> are manual or automated activities or procedures that the<br>business performs.</p><p><strong>Rules</strong> include business rules, guidelines, constraints, regulations, or policies under which the business operates. Think of rules as encircling the other three components because rules guide the use of the other components. This is a simple way to start thinking about analyzing any business area.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fT4WaNKvjl1e7SLtGQ90KA.png" /><figcaption>Core Requirements Components</figcaption></figure><p>By breaking requirements into their core components, BAs begin to see the business more analytically. They can identify specific parts of the business that may need improvement and develop more specific questions to get more detailed requirements.</p><h3>A skill which needs to be sharp at all times: Asking the Right Questions</h3><p>A critical analytical skill is the ability to formulate sound questions. To elicit information, questions are used. The emphasis of this skill set is on <strong>developing good questions, not on correct answers. </strong>If you already knew the answer, why would you ask the question? A business analyst should constantly be on the lookout for additional questions that require resolution. Use broad questions and elicit responses that describe an overall view during initial meetings and interviews with stakeholders. Following elicitation sessions, more detailed, clarifying questions will be required. After you’ve asked a question, repeat the response in your own words to ensure you’ve understood it correctly. This is an excellent way to ensure that you have accurately captured the response.</p><p>Additional clarifying questions can then assist you in validating the data. When stakeholders describe how they carry out a task, such as accepting a customer order, follow-up questions may include the following: • What happens if the customer’s payment is declined?</p><p>• What payment methods do you accept?<br>• How much money do these payments typically cost?</p><p>A skilled BA will elicit detailed information about each process, piece of data, and business rule. While some of the questions may be slightly out of scope, it is critical to ensure that nothing is overlooked. By posing these additional questions, context is established. <strong>BAs must understand context in order to ensure the success of their solution, not just the end result of the change.</strong></p><p><strong>Open-ended </strong>questions elicit <strong>in-depth responses </strong>from the subject matter expert. In many cases, a stakeholder will provide information that goes above and beyond the call of duty. There may be value in this additional information.</p><p>Consider the <strong>who, what, where, when, why, </strong>and<strong> how </strong>using the journalistic model. Each of these question starters will generate a vast number of specific questions relevant to a specific project or business area. Any BA, working alone or in a group, can create a list of questions at any point during a project.</p><h3>Create a list</h3><p>Creating and reviewing this list exposes the analysis work that needs to be done. Sample questions for different categories of information are listed below for a good start.</p><p><strong>Basic Flow steps </strong><br>How is the process performed? Describe a typical, successful interaction.<br>What is the user doing at each step?<br>What should the system do in response?</p><p><strong>Alternate Flow triggers</strong><br>Is there any other way it could play out?<br>Is there anything that could go wrong?<br>Are there any editing or verifications that might fail?<br>Could a user or system timeout occur a this point?<br>Are these events correctable or do they lead to<br>cancellation?</p><p>When should the user be allowed to cancel the<br>transaction?<br>Is there anything else that could happen that could<br>result in the task being cancelled?</p><p><strong>Triggers</strong><br>When is the process performed? On a regular basis? After a triggering event? What event triggers the interaction?</p><p><strong>Priority</strong><br>How important is it that this user task (system use<br>case) be supported by the solution?<br>Would the solution be acceptable if it did not include it?<br>Would you accept a workaround, if you knew it would<br>be added in a later release?</p><p><strong>Pre-conditions / constraints / policies</strong><br>Are there any activities or events that should already<br>have taken place before the interaction begins?<br>What constraints, policies, or procedures guide the process?</p><p><strong>Post-conditions on success</strong><br>What is the net effect of the interaction once it has<br>completed successfully?</p><p><strong>Guaranteed post-conditions</strong><br>What should the net effect of the interaction be when<br>it is not completed successfully (for example, because<br>the user cancelled, invalid input, or a requested IT service<br>was not available)?</p><p>Should any audit trails or logs of the failed attempt be<br>produced?</p><p>Once you have a list of questions, look at each question and think about:<br>• How could you best elicit this information?<br>• How will you best record it when you receive it?<br>• How critical will the answer be?<br>• What type of requirement component will be found in the answer?<br>• Who would have the answer?<br>• Who is going to use this information?</p><p>As you are formulating questions, you should think about <strong>who would be able to best answer them.</strong> Typically, the <strong>why questions</strong> are best asked to <strong>high-level stakeholders</strong>. Executives and managers often. See the bigger picture and know the reasons for the organization’s decisions. <strong>Middle-level managers</strong> and supervisors can answer questions about <strong>who does what, where</strong> activities are performed, and what the goals of each activity are. <strong>Business worker</strong>s will be able to answer specific, detailed questions about <strong>how work is accomplished</strong> and what specific activities are related to others.</p><p><strong>WRAP UP</strong></p><p>Planning your questions is an integral part of your overall business analysis planning. <strong>Always begin with the end in mind </strong>— what are you hoping to achieve or learn by asking the question? What purpose will the data be used for? Be specific about your objective(s), as this will not only help you stay focused, but it will also help your stakeholders understand <strong>why you require their assistance and, more importantly, their valuable time.</strong></p><p>Then, take a moment to consider all the questions that might assist you in obtaining this information. With these questions in mind or on paper in front of you, you can determine which stakeholders are best equipped to provide the requested information. Following these steps results in the creation of a straightforward communication plan. Carry out this exercise even if you are unaware of all the information. This will reveal any gaps in your knowledge that you should fill before proceeding, regardless of the technique you are using. Good luck you all.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5627f5748622" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adessoturkey/asking-right-questions-5627f5748622">Asking right questions</a> was originally published in <a href="https://medium.com/adessoturkey">adessoTurkey</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Listening for Requirements]]></title>
            <link>https://medium.com/adessoturkey/listening-for-requirements-e20bd011c33e?source=rss-668bdeb5c3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/e20bd011c33e</guid>
            <category><![CDATA[listening-skills]]></category>
            <category><![CDATA[requirements-elicitation]]></category>
            <dc:creator><![CDATA[Ertuğrul Yalçın]]></dc:creator>
            <pubDate>Thu, 16 Dec 2021 06:57:29 GMT</pubDate>
            <atom:updated>2021-12-17T13:50:59.483Z</atom:updated>
            <content:encoded><![CDATA[<p>Effective listening is a necessary skill for everyone, but especially for those who perform business analysis. Frequently, eliciting requirements entails asking excellent questions and carefully listening for responses. Listening is challenging and distinct from simply hearing someone. The majority of people have never been taught how to listen formally.</p><blockquote>Listening is a deliberate, active <strong>decision</strong> made during a conversation.</blockquote><p>The BA must choose to listen and actively participate in the process.<br>Becoming an excellent listener has numerous benefits for the BA. People enjoy conversing with attentive listeners and are extremely appreciative of the time spent. By identifying common ground and clearly articulating opposing viewpoints, effective listeners can assist in resolving disagreements and conflicts. Listening enables you to make sound judgments based on solid facts.</p><p>When you actively listen, you are <strong>engaged</strong>. According to studies, up to 55% of a message is received non-verbally. Keep an eye out for unconscious body language and facial expressions. When a business stakeholder informs you about a task, look for indicators of their feelings about the task. Is it pleasurable? Is it tiresome? Do they see the value in it, or is it merely a means to an end? Are they interested in assisting in the process’s improvement? By listening with your eyes and ears, you can glean valuable information about a business area.</p><h3>anything else?</h3><p>Through your <strong>tone of voice and body language</strong>, convey your own interest and curiosity. Be cognizant of the non-verbal messages you send. When you are physically engaged with a stakeholder, by actively leaning toward them, concentrating on their responses, taking notes, and <strong>showing genuine interest</strong> in what they are saying, you <strong>encourage</strong> the individual to provide much more detail and clarification on unclear points. If you are uninterested, sarcastic, condescending, demeaning, or otherwise negative toward the stakeholder, the stakeholder may withdraw and refuse to provide critical requirements.</p><p>Bear in mind that regardless of how you ask the questions, <strong>informing</strong> your stakeholders about how you use the data you collect will <strong>help you build and maintain trust</strong>. When stakeholders see that the information they share is used objectively and to improve the organization, they will develop a greater level of trust in you and will be much more willing to continue sharing and supporting your change efforts. After the session, <strong>a simple e-mail with a summary of your notes </strong>can earn you a great deal of trust and support moving forward.</p><h3>what are the barriers to listen effectively?</h3><p>There are numerous impediments to listening. These impediments keep the listener from correctly interpreting the intended message. <strong>Filters</strong> are one type of barrier. Each new piece of information is processed by an individual’s brain using filters that have been developed since childhood. You may be unaware of the filters that affect your ability to hear a desired message. P<strong>rejudices, beliefs, values, attitudes, past experiences, interests, and fears</strong> are all used as filters. Learn to recognize your filters. Try to figure out how they came to be and how they affect your thinking. Improve your communication skills by becoming aware of your filters and how they affect your ability to listen. A BA should always <strong>be as objective as possible</strong>, focusing on the best solution for all stakeholders. Furthermore, keep in mind that other people have filters as well. Keep an ear out for these and be mindful of their impact on your intended messages.</p><p><strong>Lack of interest</strong> is another impediment to listening. When a BA is not curious or interested in learning about a SME’s business area, their body language and behavior reveal that lack of interest, which the speaker may interpret as a lack of interest in him or her <strong>as a person</strong>. Determine the reason for your lack of interest. Do you have a tired feeling? Are you being sidetracked by unrelated issues? Do you believe<strong> you already understand</strong> what the speaker is saying? You can fix the problem once you figure out why you’re not interested. <strong>Listening is a commitment</strong>; decide ahead of time that you want to get something out of the conversation.</p><p>Listening can also be hampered by <strong>preconceived notions</strong>. When dealing with a familiar topic or person, preconceived ideas and thoughts are almost always present. It’s natural to listen selectively for what you expect or want to hear. You can filter out information that does not meet your standards. If you have prior experience in the business area being studied, you run the risk of overlooking important information due to preconceived notions. Although prior knowledge of the industry is beneficial, it can also be a hindrance. You may not need to reconfirm specific information because you believe you already know it. You may also<strong> fail to look for discrepancies between what you already know and what the SME says</strong>. It is critical to elicit clear and complete requirements by keeping an open mind rather than relying on preconceived notions.</p><p>When a subject matter expert (SME) is still talking, <strong>avoid formulating responses or asking follow-up questions.</strong> When you let your thoughts wander to the next thing you want to say or ask, you <strong>run the risk of leaving out important details.</strong> Try to keep your ears open and your mind focused until you get the full message. Return the message to the SME to confirm that you received it in its entirety. Observe and record what is being said. Wait until the SME has finished to prepare your response and any follow-up questions you may have. SME will appreciate that you paid attention to what they were saying, rather than interrupting them.</p><p>Another problem with listening is <strong>having to finish other people’s sentences</strong>. This is very important not only for BA activities but for all conversions we make. This will make it <strong>less likely for a SME to want to keep talking to you</strong>. If you notice that you have this habit, try to break it by listening for periods and question marks from the SME. The SME will stop when they finish a thought, and this is the time for you to answer. If you find it hard to stay quiet, drink water while the SME is talking. Make sure the SME is done and that you can think about what you want to say before you answer. Body language like nodding and eye contact can help the SME finish his or her thought, so use them to help.</p><p><strong>Hearing the Requirements</strong><br>There are common phrases an analyst can listen for to find requirements.</p><p>Below is a list of words and phrases to listen for and the possible requirements components that could be discovered from that information.</p><p>🚩 Has, performs, does ➡️ Functional requirement<br>🚩 If . . . ➡️ Business rule<br>🚩 Sometimes . . . ➡️ Conditional business rule<br>🚩 Of course . . . ➡️ Assumption<br>🚩 It would be nice . . . ➡️ Unnecessary or low priority requirement<br>🚩 Hopefully, envision, imagine, would like ➡️ TO-BE solution possibilities/ideas<br>🚩 Existing, current ➡️ AS-IS procedures and processes<br>🚩 Only when . . . ➡️ Business rule, possibly a security issue<br>🚩 Quickly ➡️ Performance requirements<br>🚩 Not ➡️ Business rule<br>🚩 Always, never ➡️ Mandatory business rules<br>🚩 When . . . ➡️ Business rule<br>🚩 Save, store, capture, write down ➡️ Data<br>🚩 Access . . . ➡️ Nonfunctional requirements</p><p>“Asking the right questions” is another subject which is very important and deserves to be addressed in a larger article. Catch you later.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e20bd011c33e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adessoturkey/listening-for-requirements-e20bd011c33e">Listening for Requirements</a> was originally published in <a href="https://medium.com/adessoturkey">adessoTurkey</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vague Requirements vs. Perfect Requirements]]></title>
            <link>https://medium.com/adessoturkey/vague-requirements-vs-perfect-requirements-ebc1c5adcfb7?source=rss-668bdeb5c3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebc1c5adcfb7</guid>
            <category><![CDATA[requirements-engineering]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[writing-user-stories]]></category>
            <dc:creator><![CDATA[Ertuğrul Yalçın]]></dc:creator>
            <pubDate>Mon, 04 Oct 2021 18:30:23 GMT</pubDate>
            <atom:updated>2021-10-13T10:41:03.748Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s begin with an admittance : it’s difficult to specify requirements precisely! You’re working on a new invention, and no one exactly knows what it should look like or do yet. People may feel more at ease with ambiguous requirements. Here’s how: It’s possible <strong>customers</strong> like them / or leave them vague because <strong>they can change the requirements at any time to mean whatever they want (This is one of the most common situations in today’s world, but this is another story)</strong>.<strong> </strong>Vague requirements are often preferred by <strong>developers</strong> because they give them the freedom to create whatever they want. Vague requirements may be appealing to <strong>testers</strong> because they can run all possible scenarios in their heads. Even though it’s a lot of fun, none of it actually leads to better software.</p><p>In the end, you are creating only one product, and at many points someone needs to decide just what that product will be. It will be the developers who will be forced to make decisions in the absence of clear inputs from customers and analysts. This is an indication that key stakeholders are abandoning their responsibilities to make requirements-level decisions and handing those responsibilities over to others who are far less familiar with the issue. As business analysts, we should never allow this to happen in our projects. How? I believe we need to elaborate and clarify our points a little more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_U4i5qca7ef5pp-RdhNXMA.jpeg" /></figure><h3>You’re never going to have perfect requirements.</h3><p>First and foremost, <strong>requirements are never finished or complete. </strong>One can never be certain that they haven’t missed a requirement, and there will always be some requirements that the analyst will not feel it is necessary to record because of time constraints. Rather than declaring the requirements “completed” at a specific point in time, establish a baseline. Once you’ve established a baseline, you can modify the requirements using your change control process, while keeping in mind the consequences of making changes. <strong>It is naive to believe that after some initial elicitation activities, you can freeze the requirements and prevent any further changes.</strong></p><p>Furthermore, the <strong>pursuit of perfection</strong> can result in analysis paralysis. <strong>Analysis paralysis</strong>, on the other hand, can have a negative repercussion. A project that became bogged down in requirements issues has a negative impact on the confidence of stakeholders, who might consequently be reluctant to invest in requirements development on their subsequent projects.</p><p>From a pragmatic standpoint, requirements development aims to produce requirements that are good enough to allow the team to proceed with design, construction, and testing while maintaining a manageable level of risk. The risk is the possibility of being forced to perform costly and unnecessary rework. In order to minimize risks : <strong>always review the requirements with team members who will be relying on them to create their own work to determine whether they provide a sufficiently solid foundation for that subsequent work to be completed. </strong>While pursuing your quest for quality requirements, keep in mind the <strong>practical goal of “good enough.”</strong></p><p>Requirements analysts (also known as requirements engineers): “That’s all right. However, we are unsure as to how specific our requirements must be.”</p><p>All literature : <strong>“There is no single correct answer to this question.” </strong>(Even if we could all agree on the exact definition of “detail” in terms of requirement specifications.)</p><p>Despite this, there are several approaches to determining how much detail is appropriate in a given situation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/976/1*vOe1cESn4b7qB-vyzphG1Q.jpeg" /></figure><h3>Who Makes the Call?</h3><p>When deciding how detailed to make the requirements specifications, the following is the most important question to consider:</p><blockquote>Who do you want to have making decisions about requirements details and when?</blockquote><p>You don’t need to include as much information in the requirements documentation if you’re willing to delegate many of the final decisions about product capabilities and characteristics to the developers. More detailed specifications, on the other hand, are required if you want to describe exactly what you expect to be delivered. <strong>You must strike a balance between cost and risk.</strong> It is more expensive to develop requirements in greater depth than it is to leave them more general. The appropriate level of detail to include is determined by the risk associated with leaving decisions about specifics to developers.</p><p>For example, it is unrealistic to expect every reader to automatically understand which system functions require the user to be logged in and which do not. It’s unrealistic to expect every reader to distinguish between the parts of the system that require particularly quick response times — and to know exactly what those response times should be — and those that don’t. Speaking of response times, many architectural choices are also influenced by quality requirements. If those high-impact requirements aren’t documented because those with that knowledge assume that others will share their insight, the product may fall short of expectations for performance, reliability, integrity, and so on. An expensive rework project may then begin, with the goal of creating a new architecture to meet the demands of the operating environment.</p><h3>When Less Detail Is Appropriate</h3><p>Under certain circumstances, it is acceptable to leave the requirements descriptions at a higher level of abstraction. Keep in mind that these are general guidelines. Conduct a<strong> risk-benefit analysis </strong>to weigh the potential consequences of omitting critical information against the effort involved in including it. Here you can find some of the most common examples (including necessary drawbacks or warnings) listed below.</p><p><strong>Product owners are extensively involved. </strong>If the appropriate business/user/customer representatives are involved extensively, continuously, and intimately, you can talk more on requirements and write less documentation. This is the fundamental benefit of agile software development methodologies’ use of on-site customers. In such cases, developers require only a minimal amount of written information about requirements in order to assess their size and gain a general understanding of the customer’s intent, user experience desired.</p><p>Conversations with business representatives and subject matter experts provide the details. <em>(See References “The 3 C’s (Card, Conversation, Confirmation) of User Stories” for more details) </em>This strategy is only effective when developers have ready access to customers who have the time, knowledge, and authority to make decisions on behalf of the communities they represent. Even if customers can provide just-in-time information,<strong> it’s unlikely that anyone will record it. This makes it more difficult to reach a consensus among the various stakeholders.</strong></p><p>Another drawback is that there will be <strong>little documentation to review for your project.</strong> You will be unable to ensure that the product has been adequately tested and that no requirements were inadvertently overlooked during implementation<strong> because you will lack a written reference.</strong> Of course, if someone accepts responsibility for this role, it is possible to capture detailed information as developers obtain it, thereby growing the requirements specification (or, in some agile approaches, the test documentation) incrementally.</p><p><strong>Team has extensive domain knowledge.</strong> Developers with extensive application domain knowledge can sometimes provide a large portion of the required requirements details. Keep an eye out for developers who are overconfident, certain that they understand what users require without having to ask. In an ideal world, knowledgeable stakeholders from various user classes / business units will collaborate with the requirements analyst to develop requirements. <strong>When using surrogates who will not actually use the product being developed,</strong> <strong>there is always the risk of a disconnect.</strong></p><p><strong>There are precedents that can be used.</strong> When you have precedents to use as a model, you don’t have to include all of the details of the requirements in the specification. When there are details in the existing product or documentation that are not provided in the current specification, the developers can use them as a reference. It is possible that this will be the case, for example, when reengineering a legacy application. Keep an eye out, though. Unless you are looking at the user interface or a high-level product description, <strong>most software contains extensive functionality that is not immediately visible to someone who is simply looking at the software.</strong> Example of this are exception handlers, business rule enforcement, and relationships between data in fields on a form or dialog box, just to name a few. Each developer should not reverse-engineer the existing product in order to figure out exactly what it does, as this may result in different conclusions being reached by different developers.</p><p><strong>A package solution will be implemented.</strong> Highly detailed requirements are not required for projects that will acquire a commercial package solution for all or part of their needs. It is pointless to write extensive functional requirements because the package vendor has already done so (or so you hope). However, it is uncommon for a package to fully meet your requirements, so you must still specify the requirements for change requests, feature extensions, integrations, and customizations. For package-solution projects, use cases work well (see my previous article for more details). The package must enable your users to complete specific tasks (use cases), though the specifics of how this is accomplished will vary from package to package (functional requirements and design). User acceptance tests based on use cases can also help with package evaluation. It is critical to understand the relevant business rules. The package you choose must enforce the necessary business rules while also allowing you to change or customize them as needed. Defining quality attribute requirements will also assist stakeholders in selecting the best package.</p><h3>Conclusion</h3><p>No set of requirements can ever fully describe a product. No written documentation can ever replace human dialogue. Still, we must do our best to avoid “implied” or “assumed” requirements as much as possible. Plus, it’s risky to assume that all <strong>readers </strong>of the requirements specification will understand exactly what the analyst <strong>intends, </strong>so we must<strong> tell and show </strong>in addition to writing narratives. Here, balance is the key. If you try to write a comprehensive specification, you’ll never have time to build and test software. But we can agree that, it’s best to write down anything you’re not sure the reader knows. Don’t rely on telepathy or business unit representatives’ verbal / non-verbal communication skills as you build the foundations of your product.</p><p><em>References</em></p><ul><li>Wiegers, Karl E. “More About Software Requirements: Thorny Issues and Practical Advice”</li><li>Birch, Travis’s article <a href="https://berteig.com/how-to-apply-agile/summary-of-user-stories-the-three-cs-and-invest/">on three “C”s</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebc1c5adcfb7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adessoturkey/vague-requirements-vs-perfect-requirements-ebc1c5adcfb7">Vague Requirements vs. Perfect Requirements</a> was originally published in <a href="https://medium.com/adessoturkey">adessoTurkey</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Visiting an old friend: Use Cases]]></title>
            <link>https://medium.com/adessoturkey/visiting-an-old-friend-use-cases-20c8eff979fb?source=rss-668bdeb5c3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/20c8eff979fb</guid>
            <category><![CDATA[requirements-engineering]]></category>
            <category><![CDATA[use-case-diagram]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Ertuğrul Yalçın]]></dc:creator>
            <pubDate>Thu, 23 Sep 2021 06:23:31 GMT</pubDate>
            <atom:updated>2021-10-04T13:27:05.023Z</atom:updated>
            <content:encoded><![CDATA[<p>Why bother with documentation? Of the four reasons(1) that IREB responds to this question, I personally put this one first on the list: <strong>getting us to think better.</strong> And use case modeling is definitely a good tool in terms of forcing our minds to work hard and focus, in order to shape the scope, understand the relationships between users, processes, and subsystems in the scope of the solution we are working on. We can agree that use cases “sound” old fashioned. Has agile killed use cases? Well, I don’t think so. Here is, why not?</p><p><strong>Why use use cases?</strong></p><p>Rather than giving basic information about use cases, we’d better talk about the benefits of and tips for creating them. First of all, use cases not only define how different types of users interact with the system to solve a problem, but they also aid in the identification of all the alternative scenarios that often cause us to make mistakes when it comes to system-level efficiency. This is particularly true when the team is working on complex systems, with system-spanning epics, features, and stories surfacing in and out like a fish. According to Cockburn, “Five good reasons to use use cases in agile development,” — pursuing accuracy and <strong>completeness</strong> — are as follows:</p><p>1. The list of use case “names” (purposes of the use cases) gives executives a quick overview of how the system can benefit the company and its users. It also includes a skeleton /structure for project planning, which can be used to develop initial goals, forecasts, team assignments, and timelines. It’s the first part of the issue about <strong>completeness</strong>.</p><p>2. The use case’s key success scenario ensures that everyone understands what the system will…and will not do. It provides background for each requirement, which is difficult to obtain in some other way. It also serves a basis for shaping regression test scenarios.</p><p>3. The use case’s alternate flows offer a basis for investigating all of the small, niggling issues that consume a large amount of development effort. It has a look-ahead feature that allows the customer/product owner/business analyst to identify problems that will take a long time to resolve. For example if different actors have different use cases for the same function, alternate flows will perfectly serve as a solid source of information for determining personas and their goals. The second aspect of the <strong>completeness</strong> issue is the use case extension conditions.</p><p>4. Use case’s extension conditions / alternate flows address programmers’ many thorough, tricky business questions, such as “What are we supposed to do in this case?” It’s a thought/documentation paradigm that corresponds to the if…then…else argument and aids programmers in thinking about such problems while developing the main scenario.</p><p>5. The complete use case collection (use case model) demonstrates that the developers/analysts have considered every user’s/ persona’s (stakeholders’) needs, every objective they have for the system, and every business variant involved. This is the last part of the question about <strong>completeness</strong>.</p><p>On the other hand, use cases provide a mechanism to help developers think about all the possible paths through the system and subsystems that the users may encounter. In turn, this helps the team understand where user stories are likely to be needed to implement the required functionality. Every time a new use case touches a subsystem, there are probably new stories that must be developed for that subsystem, as is shown in Figure 1.</p><p><strong>Figure 1.</strong> Use cases traversing a system identify where stories are needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EY2QQ-DKYWhED22-osNjSQ.png" /></figure><p>Since use cases can be so useful with above mentioned benefits, regardless of project management approach, we’ll try to provide a basic guideline for successful usage. Those who say I already know this, can proceed to the conclusion part; others may proceed with the steps.</p><p><strong>A Step-by-Step Guide to Building the Use Case Model</strong></p><p>An individual use case explains how a specific actor communicates or interacts with the system in order to obtain a useful outcome or solve a problem for that actor. The sum total of all use cases represents the system’s overall behavior. The use case model for the system is made up of the entire set of use cases, actors, and their interactions, including necessary use case diagrams and flows with textual explanations (Use Case Narratives) for each use case.</p><p>Building the system’s use case model is a vital research phase that will serve as the foundation for understanding, interacting, and optimizing the system’s actions during the project. A simple five-step approach to building the use case model has proven to be successful. These phases, however, do not all occur at the same time in the project life cycle, and some will almost certainly be repeated.</p><p><strong>Step 1: Identify and Describe the Actors</strong></p><p>To begin, list all of the actors who interact with the system. It’s a matter of organizing the environment into two categories: the system we’re creating and the objects (actors) that communicate with it.</p><p>The following questions will be helpful for finding the actors.</p><p>• Who uses the system?</p><p>• Who gets information from this system?</p><p>• Who provides information to the system?</p><p>• Where is the system used?</p><p>• Who supports and maintains the system?</p><p>• What other systems or devices use this system?</p><p><strong>Step 2: Identify the Use Cases</strong></p><p>Once the actors are identified, the next step is to identify the various use cases that the actors need to accomplish. We can do this by determining the specific goals for each actor in turn.</p><p>• What will the actor use the system for?</p><p>• Will the actor create, store, change, remove, or read data in the system?</p><p>• Will the actor need to inform the system about external events or changes?</p><p>• Will the actor need to be informed about certain occurrences in the system?</p><p>Each use case has a <strong><em>name</em></strong> that represents the goal of the use case. The name is a few words or short phrase that starts with an <strong>action verb</strong> and communicates what the actor <strong>achieves</strong>. Names help communicate what the system does and create context.</p><p>Along with the name, there is a brief description that further describes the intent of the use case.</p><p><strong>Figure 2</strong> Sample use case diagram : four use cases for the utility network operations center</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Efd4VSTalUoSp8JTpnrfw.png" /></figure><p><strong>Step 3: Find Actors and Use Case Relationships — carefully!</strong></p><p>While a single actor may initiate a use case, some use cases require multiple actors to participate. The system becomes a system when the actors and use cases communicate in harmony. Each use case is examined to determine the actors engage with it, and each actor’s expected actions are examined to ensure that the actor participates in all of the required use cases. For the success of the projects maybe this step is the most crucial part. An important yet neglected / underestimated actor’s late involvement into the scope might be fatal.</p><p><strong>Step 4: Outline the Flow of the Use Cases</strong></p><p>Next is to sketch out the flow of each use case in order to begin to understand the required actions and responses at a more detailed level. The flow of events, including the basic and alternative flows can be depicted as follows:</p><p><strong>Figure 3</strong> A use case has one main flow and some number of alternate flows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YlsWK4-jau7bpsuxVH58pg.png" /></figure><p>Then, sketch out the basic flow. This is the flow that depicts the most popular route (the “happy path”) through the use case from beginning to end.</p><p>The use case would also have a variety of alternative flows based on both normal and exceptional events. The following questions will assist you in identifying these branches.</p><p>Basic flow</p><p>• How does the use case start and end?</p><p>• How, under what conditions does the use case repeat its behavior?</p><p>Alternate flows</p><p>• What else can the actor do?</p><p>• How will the actor react to optional situations?</p><p>• What options does the actor have and what might happen in response?</p><p>• What exceptions to the usual behavior may occur?</p><p>Having these questions answered, now we can proceed to writing in detail : <strong>use case narratives.</strong> Use case narratives describe the process steps inside each use case. The narratives are needed because while it is great to see the features at a glance, no one really understands what these process names mean until we describe the detailed steps. A good example is provided(2).</p><p><strong>Step 5: Refine the Use Cases</strong></p><p>This is where the team will decide whether to refine the use case to another level of detail, or to move directly to the stories that implement the use case. There are a number of additional factors to be considered for refining.</p><p>First, think of all possible scenarios, including rare exceptions: Since the primary alternate flows of a use case are governed by explicit actor choices, identifying them is typically easy. The “what ifs,” on the other hand, are a major source of concern, and they must be thoroughly discussed in alternative flows. The application may not act as intended unless all of these exceptions are recognized, coded, and checked.</p><p>Second, preconditions: Preconditions are the conditions that must be met before a use case can begin. A precondition for programming vacation settings, for example, may be that the user has set the time zone. The use case cannot be successfully executed until this is achieved.</p><p><em>And finally exit conditions </em>which describe the persistent states when use case ends. They can include the success states after successful execution and failure states after unsuccessful execution.</p><p><strong>Conclusion</strong></p><p>User stories, features, and epics are used to organize requirements and define the behavior of the systems. As convenient as they are, however, they can be insufficient for teams to define and understand the behavior of more complex systems. At this point, use cases can help. It is proven that use cases (both diagrams and textual specifications) provide a structured way of defining system scope and capturing and documenting requirements in detail. As an added bonus, the testing team will be able to produce test scripts from the use cases as the development team begins its work, which will ensure that the team will build the right thing and validate the right way.</p><p><strong><em>Footnotes</em></strong></p><p>(1) Four reasons for documentation according to IREB : 1- legal purposes, 2-preservation purposes, 3- communication purposes 4- thinking purposes</p><p>(2) Sample Use Case Narrative (<a href="https://drive.google.com/file/d/1Yg_Z3lhThtC9gMsz9PG7W_36ggJLAwYd/view?usp=sharing">here</a>)</p><p><strong><em>References</em></strong></p><p>· Cockburn, Alistair. Writing Effective Use Cases. Boston, MA: Addison-Wesley, 2001.</p><p>· Leffingwell, Dean. Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise, Addison-Wesley Professional, 2010.</p><p>· norwalkaberdeen.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20c8eff979fb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adessoturkey/visiting-an-old-friend-use-cases-20c8eff979fb">Visiting an old friend: Use Cases</a> was originally published in <a href="https://medium.com/adessoturkey">adessoTurkey</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>