<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.4 20241031//EN"
        "https://jats.nlm.nih.gov/publishing/1.4/JATS-journalpublishing1-4.dtd">
<article  article-type="research-article"        dtd-version="1.4">
            <front>

                <journal-meta>
                                    <journal-id></journal-id>
            <journal-title-group>
                                                                                    <journal-title>Yönetim Bilişim Sistemleri Dergisi</journal-title>
            </journal-title-group>
                            <issn pub-type="ppub">2630-550X</issn>
                                        <issn pub-type="epub">2630-550X</issn>
                                                                                            <publisher>
                    <publisher-name>Dokuz Eylul University</publisher-name>
                </publisher>
                    </journal-meta>
                <article-meta>
                                        <article-id/>
                                                                                                                                                                                            <title-group>
                                                                                                                        <article-title>YAZILIM TEST SÜRECİNDE DURUM RAPORLAMASINA GENEL BAKIŞ VE YAKLAŞIMLAR</article-title>
                                                                                                                                                                                                <trans-title-group xml:lang="en">
                                    <trans-title>AN OVERVIEW AND APPROACHES TO STATUS REPORTING IN THE SOFTWARE TEST PROCESS</trans-title>
                                </trans-title-group>
                                                                                                    </title-group>
            
                                                    <contrib-group content-type="authors">
                                                                        <contrib contrib-type="author">
                                                                <name>
                                    <surname>Uzun</surname>
                                    <given-names>Beytullah</given-names>
                                </name>
                                                                    <aff>Ericsson Araştırma Geliştirme Ve Bilişim Hizmetleri A.Ş.</aff>
                                                            </contrib>
                                                    <contrib contrib-type="author">
                                                                    <contrib-id contrib-id-type="orcid">
                                        https://orcid.org/0000-0002-3115-5676</contrib-id>
                                                                <name>
                                    <surname>Koruyan</surname>
                                    <given-names>Kutan</given-names>
                                </name>
                                                                    <aff>DOKUZ EYLÜL ÜNİVERSİTESİ</aff>
                                                            </contrib>
                                                                                </contrib-group>
                        
                                        <pub-date pub-type="pub" iso-8601-date="20191206">
                    <day>12</day>
                    <month>06</month>
                    <year>2019</year>
                </pub-date>
                                        <volume>5</volume>
                                        <issue>1</issue>
                                        <fpage>52</fpage>
                                        <lpage>63</lpage>
                        
                        <history>
                                    <date date-type="received" iso-8601-date="20191002">
                        <day>10</day>
                        <month>02</month>
                        <year>2019</year>
                    </date>
                                                    <date date-type="accepted" iso-8601-date="20191128">
                        <day>11</day>
                        <month>28</month>
                        <year>2019</year>
                    </date>
                            </history>
                                        <permissions>
                    <copyright-statement>Copyright © 2015, </copyright-statement>
                    <copyright-year>2015</copyright-year>
                    <copyright-holder></copyright-holder>
                </permissions>
            
                                                                                                <abstract><p>Günümüz dünyasında hızla büyümekte olanteknoloji sistemleri hayatımıza hızlıca yerleşmiş ve yaşamımızın her alanındayerini almıştır. Teknoloji firmaları ürünlerinin pazarlanması ve piyasaiçerisinde kalabilmeleri için büyük bir rekabetin içerisinde bulunmaktadırlar.Özellikle yazılım şirketlerinin piyasa içerisinde var olabilmek ve sunduğuhizmetlerle müşterilerinin memnuniyetini kazanabilmek için ürün ve hizmetlerininiyi bir test sürecinden geçirmeleri önem taşımaktadır. Bir yazılım projesininkalitesi müşteriye sunulmadan önce en erken test aşamasında görülebilmektedir.Test sürecinde projenin ne kalitede olduğu, projenin istenilen gereksinimlerikarşılayıp karşılamadığı ve bulunan hataların durumlarıyla ilgili bilgiler testdurum raporlamalarıyla görüntülenebilmektedir. Bu çalışmada yazılım test süreciboyunca yapılacak sürekli raporlamalar ve raporlamaların önemine değinilmekte,raporlamalara dair önerilerde bulunulmaktadır.</p></abstract>
                                                                                                                                    <trans-abstract xml:lang="en">
                            <p>Rapidly growing technology systems in today&#039;sworld have quickly settled in our lives and have taken its place in everyaspect of our lives. Technology companies are in a big competition to markettheir products and stay strong in the market. It is especially important forsoftware companies to have a good testing process in order to secure theirplace in the market and gain the satisfaction of their customers with theservices they provide. The quality of a software project is provided first inthe testing stage. The quality of the project, whether meet the requirements ornot, the information about bugs found during testing process could be viewed inthe test reports. In this study continuous reporting during testing process arediscussed and also recommendations about reporting are made.</p></trans-abstract>
                                                            
            
                                                            <kwd-group>
                                                    <kwd>Yazılım Testi</kwd>
                                                    <kwd>  Yazılım Test Durum Raporlaması</kwd>
                                                    <kwd>  Yazılım Test Hata Raporlaması</kwd>
                                            </kwd-group>
                                                        
                                                                            <kwd-group xml:lang="en">
                                                    <kwd>Software Testing</kwd>
                                                    <kwd>  Software Test Reporting</kwd>
                                                    <kwd>  Software Defect Reporting</kwd>
                                            </kwd-group>
                                                                                                            </article-meta>
    </front>
    <back>
                            <ref-list>
                                    <ref id="ref1">
                        <label>1</label>
                        <mixed-citation publication-type="journal">Ammann, P., ve Offutt, J. (2016). Introduction to software testing. Cambridge University Press.</mixed-citation>
                    </ref>
                                    <ref id="ref2">
                        <label>2</label>
                        <mixed-citation publication-type="journal">Black, R. (2002). Managing the Testing Process: Practical Tools and Techniques for Managing Hardware and Software Testing. USA: Wiley Publishing, Inc.</mixed-citation>
                    </ref>
                                    <ref id="ref3">
                        <label>3</label>
                        <mixed-citation publication-type="journal">Bourque, P. ve Fairley, R.E. (2014). Guide to the Software Engineering Body of Knowledge (SWEBOK (R)): Version 3.0. IEEE Computer Society Press.</mixed-citation>
                    </ref>
                                    <ref id="ref4">
                        <label>4</label>
                        <mixed-citation publication-type="journal">Calleam Consulting Ltd. (2008). “Case Study – Denver International Airport Baggage Handling System – An illustration of ineffectual decision making”. https://www5.in.tum.de/persons/huckle/DIABaggage.pdf, (30.04.2018).</mixed-citation>
                    </ref>
                                    <ref id="ref5">
                        <label>5</label>
                        <mixed-citation publication-type="journal">Graham, D., Van Veenendaal, E. ve Evans, I. (2008). Foundations of software testing: ISTQB certification. Cengage Learning EMEA.</mixed-citation>
                    </ref>
                                    <ref id="ref6">
                        <label>6</label>
                        <mixed-citation publication-type="journal">Johnson, P. (2012). Mariner 1&#039;s $135 Million Software Bug. https://www.itwo-rld.com/article/2717299/mariner-1-s--135-million-software-bug.html, (06.05.2018)</mixed-citation>
                    </ref>
                                    <ref id="ref7">
                        <label>7</label>
                        <mixed-citation publication-type="journal">Jones, C. (2008). Applied Software Measurement: Global Analysis of Productivity and Quality. McGraw-Hill Education Group.</mixed-citation>
                    </ref>
                                    <ref id="ref8">
                        <label>8</label>
                        <mixed-citation publication-type="journal">Lazic, L. ve Mastorakis, N. (2008). Cost effective software test metrics. WSEAS Transactions on Computers, 7(6): 599-619.</mixed-citation>
                    </ref>
                                    <ref id="ref9">
                        <label>9</label>
                        <mixed-citation publication-type="journal">Lewis, W. E. (2017). Software testing and continuous quality improvement. Auerbach publications.</mixed-citation>
                    </ref>
                                    <ref id="ref10">
                        <label>10</label>
                        <mixed-citation publication-type="journal">Naik, K. ve Tripathy, P. (2008). Software Testing and Quality Assurance: Theory and Practice. USA: John Wiley &amp; Sons, Inc.</mixed-citation>
                    </ref>
                                    <ref id="ref11">
                        <label>11</label>
                        <mixed-citation publication-type="journal">Patton, R. (2006). Software Testing. India: Pearson Education.</mixed-citation>
                    </ref>
                                    <ref id="ref12">
                        <label>12</label>
                        <mixed-citation publication-type="journal">Rational Software Corporation (2001). Test Evaluation Summary for the Architectural Prototype. https://sceweb.uhcl.edu/helm/RUP_course_example/courseregistrationproject/artifacts/test/results/test_report_arch.htm, (29.04.2019).</mixed-citation>
                    </ref>
                                    <ref id="ref13">
                        <label>13</label>
                        <mixed-citation publication-type="journal">Software Testing Fundementals (bt.). Defect Severity. http://softwaretestingfundamentals.com/defect-severity/, (18.05.2018).</mixed-citation>
                    </ref>
                            </ref-list>
                    </back>
    </article>
