Jump to content
  • forum (2).png

  • THE OPEN QUESTION on the forum right now is on Data Visualization Tools. This is part of our TWO QUESTIONS PER WEEK initiative. One question is launched on Tuesday and the other on Friday, both at 5 PM IST. Best answers are recognized well on this most active Lean Six Sigma forum. (Benchmark Six Sigma Forum ranks first on Google Search based on popularity) 

     

    Last question responded with the best response can be seen here - Refactoring. All questions can be seen here. The entire Dictionary of Business Excellence terms is here.

  •  

     

    1. High value Workshops - Our Corporate Workshops offered across the World can be seen here and the Open Enrollment Workshops (can be signed up from anywhere in the world) can be seen here
    2. If you are going through our online practice project, you can view details and updates here
    3. Questions? - For Industry specific questions or for general questions w.r.t Lean Six Sigma (or the broader domain of Business Excellence), please use the forums below. 

     

     

Forums

  1. Learning Business Excellence and Lean Six Sigma

    1. 525
      posts
    2. 1.5k
      posts
    3. 1.9k
      posts
    4. Bench and Mark Cartoons

      Bench is on the bench. Mark is on the mark. With a series of cartoons, see how Bench and Mark behave differently in approach towards solving management problems. Learn why Mark is successful when Bench is not. New toon appears every Wednesday. Discussions are open against each cartoon. 

       

       

      Bench and Mark Dual.PNG

       

       

      65
      posts
    5. Debate : For or Against

      Debate area for Excellence Ambassadors 

      199
      posts
  2. Six Sigma Practice Project for Benchmark Participants

    1. Six Sigma Practice Project - all updates

      The story of Six Sigma Practice Projects as it is progressing. Check back here for the latus status. Click on the title to see latest status. 

      8
      posts
    2. Enrolling for Practice Project

      Describes process for enrolling in practice project

      3
      posts
    3. Did not get email from Academy?

      What to do if you do not get an email from Academy after filling registration form within Progressive Group? 

      1
      post
    4. Working with Phases of Practice Project

      Guidance on how to address issues found while working with phases of practice project. 

      1
      post
    5. Registering and participating in webinars

      Guidelines for participating in webinars and accessing the recording later

      1
      post
  3. Know about Benchmark Six Sigma

    1. 2.2k
      posts
  4. Recreation and Discussion Center

    1. Debate Halls

      Debates on process improvement thoughts, articles, links, news, in addition to views on what scholars & authors say.

       

      debate catapult medieval2 launching.png

      259
      posts
    2. Fun and Trivia

      Jokes, Fun ideas, Idle thoughts - All come here

       

      Fun.png

      126
      posts
    3. Benchmark Six Sigma Cartoon Strip

      Cartoon strip co-created by the community. Submit your ideas based on characters. If approved, the strip shall be published with your name.

      20
      posts
    4. We ask and you answer! The best answer wins.

      Questions need to be answered in a limited time and use a specific format. The answers are showcased with the definition of the term in the World's Best Business Excellence Dictionary. 

      4.1k
      posts
  5. Discussions related to Training

    1. 151
      posts
    2. 181
      posts
    3. Master Black Belt and its competencies

      The Business Excellence MBB is globally recognized and carries several competencies within it. You may go for 1 or 2 competencies at a time instead of trying MBB at one go.  

      20
      posts
    4. Refresh your basics on data analysis

      This free basic maths refresher subgroup has been created for Six Sigma enthusiasts. Please feel free to reply with topic specific application examples or queries.

      55
      posts
  6. Benchmark Six Sigma Participants Support Forum

    1. Post Workshops Guidelines

      Includes discussions, success stories, advice, support, tips, and ideas.

      • No posts here yet
    2. Career & Project Discussions

      Jobs available, jobs wanted, online project support

      4
      posts
    3. 4
      posts
  7. Coronavirus Discussions

    1. Coronavirus forecasts

      Forecasts to see if the trend is likely to change and to review how we are performing against Coronavirus

      40
      posts
  • Most Solved

  • Recent Achievements

  • Who's Online (See full list)

    • There are no registered users currently online
  • Member Statistics

    • Total Members
      53,905
    • Most Online
      888

    Newest Member
    Daniel
    Joined
  • Forum Statistics

    • Total Topics
      3k
    • Total Posts
      15k
  • Gallery Statistics

    • Images
      2.3k
    • Comments
      43
    • Albums
      73

  • ALL TIME GB TOP SCORERS

     

    Name

    Score (%)

    City/Year

     
     

    Purvi Gupta

    100

    Del 2019

     

    Bhawana Sethi

    100

    Del 2015

     

    Adyan Prabhakaran

    100

    Hyd 2014

     

    Thirumoorthi.M

    99

    Chn 2019

     

    Sneha Vivek More

    99

    Mum 2019

     

    Sumita Maiti

    99

    Kol 2017

     

    Vidula Valavalkar

    99

    Hyd 2014

     

    Vishal Tillu

    99

    Mum 2014

     

    Yashwanth J G

    99

    Bng 2013

     

    Jyothi Kanuri

    99

    Hyd 2013

     

    Vrajesh Parekh

    99

    Mum 2013

     

    Gnanasekaran D

    99

    Chn 2012

     

    Benoy Ramachandran

    99

    Chn 2012

     

     

    Muthu Naveen S

    99

    Mum 2012

     

    Ketan Trivedi

    99

    Mum 2012

     

    Piyush Mangal

    99

    Del 2011

     

    Sourav Thakur

    99

    Del 2011

     

    Tushar Chaudhari

    99

    Mum 2011

     

    Komal Bansal

    99

    Mum 2011

     

    Parag Suresh Kamble

    99

    Mum 2011

     

    Ritik Gupta

    99

    Pun 2011

     

    Amit Kumar Makkar

    99

    Del 2010

     

    Shaifali Singh

    99

    Del 2010

     

    Clarence Wong

    99

    Hyd 2010

     

    Devendra Singh Baghel

    99

    Hyd 2010

     

    Varun Hemrajani

    99

    Pun 2010

     
         

    Here is the complete list of all time Lean Six Sigma Green Belt Top Scorers

  • ALL TIME BB TOP SCORERS

     

    Name

    Score (%)

    City/Year

     
     

    Kunal Obhrai

    98

    Del 2019

     

    Mahesh P K

    98

    Bng 2017

     

    Balaji M

    97

    Bng 2017

     

    Rohit Arora

    97

    Bng 2017

     

    Amit Kumar Makkar

    97

    Del 2015

     

    Kanishk Jain

    97

    Bng 2014

     

    Akshay Khatri

    97

    Del 2013

     

    Rahul Kumar

    97

    Mum 2013

     

    Sairam Balakrishnan

    97

    Hyd 2011

     

    Ashish Sharma

    96

    Pun 2019

     

    Sunil M. Bhat

    96

    Bng 2017

     

    Rohan Chavali

    96

    Del 2017

     

    Apoorve Arya

    96

    Mum 2014

     

    Sandeep P.R. 

    96

    Chn 2013

     

    Awojide Martins Olabisi

    95

    Mum 2020

     

    Zeshan Abubacker

    95

    Bng 2019

     

    Kumar Kaushal

    95

    Del 2019

     

    Vishal Kanojia

    95

    Hyd 2019

     

    Swati Malhotra

    95

    Mum 2019

     

    Nithin Sandhyala

    95

    Bng 2017

     

    Abhishek Arora

    95

    Del 2017

     

    Satishkumar Jain

    95

    Mum 2017

     

    Atirakshit Bhatt

    95

    Mum 2017

     

    Narendra Anil Murdeshwar

    95

    Pun 2017

     

    Rupinder Kaur Narang

    95

    Del 2016

     

    S Sujay Kumar

    95

    Mum 2016

     

    Kuljinder Kaur

    95

    Del 2015

     

    Vetrivendhan K P

    95

    Bng 2014

     

    Sunil Bissa

    95

    Chn 2013

     

    Mayank Gupta

    95

    Pun 2011

     

    Here is the complete list of all time Lean Six Sigma Black Belt Top Scorers

  • Posts

    • The best answer to this question has been provided by James Bob Lawless for highlighting the various methods by which refactoring can be avoided and Mohamed Asif for highlighting multiple guidelines for doing refactoring.    And then, there are a couple of answers that are a must read - Chaitanya Shankar Nemani for giving the perspective of technical debt, Johanan Collins for highlighting a risk in refactoring.
    • Code refactoring is a process that involves modifying and cleaning up previously written code without changing the function of the code. In other words, it is improving the internal structure of an existing source code, while preserving its external behavior. Code refactoring can be a great asset for project especially for projects driven in agile methodology. In an agile project, depending on the business requirements of the customer, the product/service keeps changing. Hence, the design structure should be robust to accommodate the changes.   Refactoring of the design/code can help to achieve the objectives. ·       Refactoring makes the code easier to modify ·       Refactoring makes the code easier to understand ·       Refactoring helps in sharing knowledge   Code refactoring can be considered for two reasons: 1.       Before adding any updates or new features to existing code – Helps in improving the overall quality of the product 2.       Post product delivery – To make sure the code is standardized and as a part of housekeeping.   Code refactoring should be primarily be used for clean-up effort. However, if code refactoring is not sufficient to support the business needs or when an application needs to be completely revamped, then rework effort should be taken up.
    • Refactoring implies improving the internal structure of an existing program source code, while safeguarding its external behaviour. It simply refers to particular behavior preserving transformation.   It is not limited only to writing the code again fix the bugs Improve aspects of software like its interface etc. Refactoring actions are inclined towards the below to maintain the desired preserving conditions Duplicates- removing duplicates enables to change the code in the future Clarity - Renaming and redistributing responsibilities captures much more concepts thus improving reading and comprehension time Below are the benefits of refactoring: it improves objective attributes of code corelating with ease of maintenance It helps code understanding It encourages developers to think and understand design decisions, It favors emergence of reusable design patterns and code modules      
    • Q 424. How does the data visualization tool Power BI compare with Tableau? Provide use cases that highlight advantages of one over the other.   Note for website visitors - Two questions are asked every week on this platform. One on Tuesday and the other on Friday. All questions so far can be seen here - https://www.benchmarksixsigma.com/forum/lean-six-sigma-business-excellence-questions/ Please visit the forum home page at https://www.benchmarksixsigma.com/forum/ to respond to the latest question open till the next Tuesday/ Friday evening 5 PM as per Indian Standard Time. Questions launched on Tuesdays are open till Friday and questions launched on Friday are open till Tuesday.  When you respond to this question, your answer will not be visible till it is reviewed. Only non-plagiarised (plagiarism below 5-10%) responses will be approved. If you have doubts about plagiarism, please check your answer with a plagiarism checker tool like https://smallseotools.com/plagiarism-checker/ before submitting.  The best answer is always shown at the top among responses and the author finds honorable mention in our Business Excellence dictionary at https://www.benchmarksixsigma.com/forum/business-excellence-dictionary-glossary/ along with the related term
    • Refactoring or more specifically Code Refractoring is a process by which a computer code is restructured without changing its behaviour.  Restructuring makes the software more maintainable and extensible by improving the design, structure and implementation of the software without changing its functionality.  Refractoring might also help developers to detect and fix dormant bugs and potential vulnarabilities.  Applied to mechanical product design, refactoring would be a process of refining a design with a rapid prototyping and testing cycle used along with tools such as Deisgn FMEA that results in a more refined design before finalization. Refactoring is usually performed before adding major updates or features. Interestingly, another perfect time to consider refactoring is when you've actually delivered the product. This could be the best time to do some housekeeping on your code to clean it up and make it more understandable.  Code refactoring could be avoided if you're going to revamp the complete software since it would be better to start from scratch.  In agile development refactoring is seamlessly integrated in the process itself so much so that build test and refactor cycle is a continuous process.      
    • Code Refracting is all about the improving or simplifying the designs of existing codes or code components without changing/impacting any external  functional behavior.   Usually, team does the refactoring in the below instances :- 1)      Slicing a large technique to simpler & smaller focused techniques 2)      Rewriting the names of variables & parameters to make it clearer & more meaningful 3)      Moving the responsibilities towards more appropriate of class or division from the existing one 4)      Introducing new interfaces or changing exiting interfaces   Refactoring is also an important principal technique for controlling technical debt. These are 3 types   Type of Technical Debt Causes Methods to avoid Refactoring in Technical debts Naive Technical Debt Unclear Methods of execution, Accidental, Ignorance, non-Vigilant Providing best design pattern, documentation and guidelines Unavoidable Technical Debt Upgrades, Newer versions availability in the market, Change requests or features addition in Scope during the mid of development Future Proofing the Original Designs, Codes should be repeatable & often useful to avoid the huge cost incurrence due to scope change Strategic Technical Debt Missing proper quality code practices, Either refactoring too often than usual, Or refactoring entirely is missing Including PR & Design Reviews, Monitoring Standards, Sign Off's at each developmental stage   Additionally,  there are 3 more methods to avoid technical debit which also avoids code refactoring -Managing the accrual of technical debt by using good technical practices   -Making the technical debt visible by using a defect-tracking system -Servicing (repaying) technical debt by remodeling the infrastructure and code development practices often as per the latest standards   Code Refactoring cannot be 100 % avoided. It will be part of Software development. However, those who follows the industry expertise, proves on its minimizing and always stands first at producing the acceptable software product.
    • When the code used for development is restructured without impacting any of the external behaviour or any functionality is known as Code Refractoring.   The code refactoring can be achieved in multiple ways. The most common is to add or remove, introduce or replace parameter with explicit method and method call and so on. There are several techniques available which can be used for achieving code refractoring. Some of the most common are Red Green Factoring, Refracting by Abstract, Simplifying methods and so on.   When we want to implement any new feature in the application, code refractoring should be considered. Below are some of the common areas where we need to follow this approach. ·       Standardize the coding so that the defects can be fixed without impacting the other functionality ·       Uniformity in usage of the code so that any developer can understand in future ·       Patch any new features without impacting the entire functionality ·       Reuse of the code for any similar development   In the real life scenario it is important to have code refractoring as every software will keep on evolving. However, we can avoid this in those areas where below conditions prevails. ·       No new feature & functionality to be added ·       When the development has to be done in very faster pace as Code Refractoring is time consuming   In my opinion Code Refractoring is a very strong method a developer can use. There are many developer using this concept in a complete different level.
    • Code Refactoring is a technique/skill used by the agile software developers to improve the structure of the code without compromising the functionality and external behavior of the  code.   It is achieved by applying micro refactorings which are standardized actions. The introduction of code refactorings brings about very small changes in the code without adding any new bugs.   The agile team normally consider refactoring during: * Code reviewing: Its done just before code goes live * Scheduled Intervals: Club its introduction along with with routine scheduled actions   Benefits * Easier to read both for the originator and other developers who  may work on it. * High maintainability of source code  * Expressive Internal Architecture   Avoiding Refactoring Avoiding the code refactoring completely is an ideal situation. The only way to do that is by "code is written perfect the first time" which is akin to "first time right" or "Zero Defects" in the world of Quality  
    • Code Refactoring involves changing the structure of the code, which may also be labeled as changing the factoring of the code. While code factoring changes the structure of the code, it does not change its functionality. The benefits of Code Refactoring are that it helps to improve the structure, design, and implementation of the code, making it more readable, less complex, easier to understand and maintain without changing its behavior. While code refactoring does not change the functionality, it can improve performance wherein the code uses less memory and works faster. Code refactoring is done in a series of smaller steps called micro-refactoring. Such small steps done continuously, help in removing hidden bugs and software vulnerabilities. However, if code refactoring is not done well, it can introduce bugs into the system. Benefits Maintainability and supportability. Refactored code is easy to read and understand. Its logic is not only clear to the person who has written the code, but also to the one who is maintaining the code. Scalability and Extensibility. It is easier to scale and extend the capabilities of Refactored code. Saved resources such as time and money in the future. Problems Code refactoring is not easy. It requires understanding the metadata, data models, dependencies, and the very structure of the software system. With the high turnover of team members in the software development industry, the new team will have to recreate this understanding of the software system. Code Refactoring should be avoided when the modifications are made, the structural architecture of the system could deteriorate. This can affect the maintainability and comprehensibility leading to a total change to the software system. Reference https://en.wikipedia.org/wiki/Code_refactoring https://lvivity.com/what-is-code-refactoring  
    • Code refactoring is the process of restructuring the existing code – structure, content, design etc without having any changes to its functionality/behaviour. Code refactoring is done to make the code simpler – reduce complexity in terms of the logic used, cleaner, better readable, maintainable and efficient which would also help in improving the performance. In agile where the focus is on smaller continuous iterations it is paramount to have code refactoring which will ensure the code quality is improved continuously through modifications Certain things have to be kept in mind while refactoring code. ·       Refactored code needs to be testable and should be tested appropriately before changing ·       Refactoring should be done in an incremental manner ·       It needs to be done by breaking down the code in smaller chunks, refactoring should be small   Refactoring is essential and it has to happen. However if you want to avoid refactoring altogether, following steps could help but is very difficult. ·       Coding the perfect way: though this might be absurd but the perfect code might be the first thing that can help you from not having to refactor later ·       Sufficient testing : Sufficiently testing the code when you write it initially can avoid refactoring to an extend ·       Simple logic : Code logic can be written in simple or complex logic. It is always better to stick to simple terms while coding which will help in understanding it better for anyone referring and would help in avoiding any refactoring need arising due to code complexity    
×
×
  • Create New...