<?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 Oguz Senna on Medium]]></title>
        <description><![CDATA[Stories by Oguz Senna on Medium]]></description>
        <link>https://medium.com/@oguzsenna?source=rss-943bf5ca74ee------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3_KMSqyZF-9TCogYDIrTSQ.jpeg</url>
            <title>Stories by Oguz Senna on Medium</title>
            <link>https://medium.com/@oguzsenna?source=rss-943bf5ca74ee------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:37:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@oguzsenna/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[EARS: The Easy Approach to Requirements Syntax]]></title>
            <link>https://medium.com/paramtech/ears-the-easy-approach-to-requirements-syntax-b09597aae31d?source=rss-943bf5ca74ee------2</link>
            <guid isPermaLink="false">https://medium.com/p/b09597aae31d</guid>
            <category><![CDATA[requirements]]></category>
            <category><![CDATA[requirements-engineering]]></category>
            <dc:creator><![CDATA[Oguz Senna]]></dc:creator>
            <pubDate>Wed, 29 Mar 2023 14:02:08 GMT</pubDate>
            <atom:updated>2023-04-13T13:28:53.740Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/635/1*yd2JPHW_rEHKqibVEcvWMg.png" /></figure><p>Alistair Mavin and a team from Rolls-Royce PLC developed and introduced the EARS concept at the Requirements Engineering (RE 09) conference in 2009.</p><p>In the world of software development, requirements syntax can be a complex and daunting task. With so many different elements to consider, it can be easy to get lost in the details and lose sight of the bigger picture. That’s where <strong>EARS</strong> comes in — the Easy Approach to Requirements Syntax.</p><p><strong>EARS</strong> is a simple and effective way to organize and articulate software requirements, making the process more approachable and less overwhelming.</p><h3><strong>What is a requirement?</strong></h3><p>A requirement refers to a statement that can fall under one of the following categories:</p><ol><li><strong>What </strong>actions or functions a system is required to perform</li><li>Any known <strong>limitations</strong> or <strong>constraints</strong> on resources or design that may impact the system</li><li><strong>The level of performance or quality</strong> that is expected of the system.</li></ol><p>The first type of requirement is known as <strong>Functional</strong> Requirements while the second and third types fall under the category of <strong>Non-Functional</strong> Requirements (NFRs).</p><p>Let’s give a couple of examples about the Functional and Non-Functional Requirements:</p><h4><strong>Functional Requirements:</strong></h4><ul><li>A website must allow users to create an account and login securely.</li><li>A mobile app must provide users with the ability to purchase products and services using their credit card.</li></ul><h4><strong>Non-functional Requirements:</strong></h4><ul><li>The website must be able to handle a high volume of traffic without crashing or slowing down.</li><li>The mobile app must be compatible with both Android and iOS operating systems.</li></ul><p>Even if the requirements are so important in the design process, we can inevitably encounter some problems. I will provide a list of examples here also to expand our vision against requirements:</p><ul><li>Many requirement authors <strong>lack formal training</strong> on how to write requirements effectively.</li><li>Requirements are often written in natural language without any constraints, leading to <strong>ambiguity</strong>, <strong>vagueness</strong>, and <strong>subjectivity</strong>.</li><li>Requirements may not be clear, concise, or coherent, making it difficult to understand what is required.</li><li>Some requirements may be missing triggers or important context.</li><li>The logic in requirements may not be complete.</li><li>Poor quality requirements are often copied and pasted, leading to an increase in the number of requirements with defects.</li></ul><h3>EARS differantiate five patterns of requirements</h3><ul><li><strong>Ubiquitous</strong> (always occurring): Defines fundamental properties of the system.</li><li><strong>Event-driven : </strong>Initiates when and only when in case of a trigger.</li><li><strong>Unwanted behaviors : </strong>Managing undesired occurrences such as errors, failures, faults, disturbances, and other forms of unwanted behaviors.</li><li><strong>State-driven : </strong>Triggered while in a state.</li><li><strong>Optional features : </strong>These are called upon exclusively within systems that have the specific optional feature.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Opi8fPj6YQrKQ03ztG7cAw.png" /><figcaption>EARS Patterns for Requirements</figcaption></figure><h3>Examples:</h3><p><strong>Ubiquitous</strong>: The software shall be written in Python.</p><p><strong>Event-Driven</strong>: <strong>When</strong> the money is received, <strong>then</strong> the app should send and notification.</p><p><strong>Unwanted Behavior</strong>:<strong> If</strong> the password is entered incorrectly,<strong> then</strong> the app shall display error message.</p><p><strong>State-Driven: When</strong> in Do Not Disturb mode,<strong> then</strong> the software shall silence incoming calls.</p><p><strong>Optional</strong>: <strong>Where</strong> the DP port is present, <strong>then</strong> the software shall allow user to display maximum supported refresh rate.</p><p><strong>Complex</strong>: <strong>When</strong> the reverse gear button is pressed once, <strong>if</strong> the software detects that the reverse gear does not set in place , <strong>then</strong> the software shall pop up notification.</p><p>Moreover, I’d like the mention about what if we come across with a ambiguous written requirement and how to fix that by using EARS template. Let’s see with an example.</p><p><strong>Original requirement:</strong></p><ul><li>The system shall break network connection</li></ul><p><strong>Written by using EARS:</strong></p><ul><li>When the disconnect button is pressed, then the software shall break the network connection.</li></ul><h4><strong>Conclusion:</strong></h4><p>Intel EARS is a powerful tool for documenting software requirements. By using this standardized template, software development teams can ensure that all requirements are documented clearly and consistently, making it easier to track progress and ensure that all requirements have been met. Whether you are developing a small-scale application or a large enterprise system, Intel EARS can help you document your software requirements with ease and efficiency.</p><p>Thank you for reading.</p><p>O.S</p><p><strong>REFERENCE:</strong> <a href="https://www.iaria.org/conferences2013/filesICCGI13/ICCGI_2013_Tutorial_Terzakis.pdf">https://www.iaria.org/conferences2013/filesICCGI13/ICCGI_2013_Tutorial_Terzakis.pdf</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b09597aae31d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/paramtech/ears-the-easy-approach-to-requirements-syntax-b09597aae31d">EARS: The Easy Approach to Requirements Syntax</a> was originally published in <a href="https://medium.com/paramtech">ParamTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Development: Why it Rocks?]]></title>
            <link>https://medium.com/paramtech/agile-development-why-it-rocks-85146f688312?source=rss-943bf5ca74ee------2</link>
            <guid isPermaLink="false">https://medium.com/p/85146f688312</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <dc:creator><![CDATA[Oguz Senna]]></dc:creator>
            <pubDate>Fri, 24 Mar 2023 20:16:28 GMT</pubDate>
            <atom:updated>2023-03-24T20:16:28.299Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/516/1*u9m2SVi46kPlKUR_nEkdFw.png" /></figure><p>Agile Development is a flexible and efficient approach to software development that focuses on collaboration, adaptability, and iterative development. Agile methodology allows teams to respond to changing requirements and deliver value to customers quickly. It enables software teams to stay ahead of the curve in the world of software development. But, like any methodology, Agile development has its pros and cons. Let’s explore what makes Agile development so cool and some of its benefits and drawbacks.</p><p><strong>Why Agile Rocks?</strong></p><p>Agile Development has taken the software development world by storm for several reasons. Here are the top five reasons why Agile Rocks!</p><ol><li><strong>Faster Time to Market:</strong> Agile methodology allows teams to deliver working software frequently, which enables them to respond quickly to changing customer needs and market trends. This approach reduces the time it takes to get products to market, which is critical in today’s fast-paced business environment.</li><li><strong>Improved Quality:</strong> The Agile methodology emphasizes continuous testing and integration, which helps teams detect defects early and resolve them quickly. This approach ensures that the product meets the customer’s requirements and is of high quality. Agile development can also help eliminate the “silo effect” where teams work in isolation and creates an environment where team members share knowledge and support each other.</li><li><strong>Enhanced Collaboration:</strong> Agile methodology promotes collaboration between team members and stakeholders, which promotes communication and knowledge sharing. It builds a culture of continuous learning, improves team morale, and fosters an environment of creativity and innovation.</li><li><strong>Increased Customer Satisfaction:</strong> Agile development involves frequent customer feedback, which ensures that the product meets the customer’s needs and expectations. This approach builds trust between the development team and the customer, which leads to increased customer satisfaction.</li><li><strong>Flexibility:</strong> Agile development is flexible and can adapt to changing requirements and circumstances. This approach enables teams to respond quickly to new information and adjust their plans accordingly. Agile methodology values individuals and interactions over processes and tools, which creates an environment where the team can be creative and think outside the box.</li></ol><p><strong>Cons of Agile:</strong></p><ol><li><strong>Lack of predictability:</strong> Agile methodology is highly adaptable, which can make it difficult to predict the final outcome of a project accurately.</li><li><strong>Over-reliance on team members:</strong> Agile development places a lot of emphasis on team members’ skills and experience, making it challenging to find suitable replacements if team members leave.</li><li><strong>Requires high levels of communication:</strong> Agile methodology requires constant communication between team members and stakeholders, which can be difficult to maintain in large teams.</li><li><strong>Can be time-consuming:</strong> Agile development requires constant iteration and feedback, which can be time-consuming for teams with limited resources.</li><li><strong>Risk of scope creep:</strong> Agile development can lead to scope creep, where the project’s scope increases beyond the original plan, leading to delays and cost overruns.</li></ol><p>In summary, Agile development is a flexible and efficient approach to software development that emphasizes collaboration, adaptability, and iterative development. Agile Rocks because it allows software teams to respond to changing requirements faster and deliver value to customers. Besides, cons of the methodology should not overlooked by the software teams.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85146f688312" width="1" height="1" alt=""><hr><p><a href="https://medium.com/paramtech/agile-development-why-it-rocks-85146f688312">Agile Development: Why it Rocks?</a> was originally published in <a href="https://medium.com/paramtech">ParamTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>