( ), also called as ( ), is a branch of software engineering that emphasizes the separation of concerns with respect to the wide-ranging functionality available throughout a given software system. Component-based software engineering CBSE component-based development CBD In this day’s Component-Based Architecture is highly popular, each modern UI framework provides component structure approach. Check out this for pros and cons. What I like the most in CBA is the separation of concerns😎 article Whether starting a small project or having a huge one the separation of concerns is going to be a key point for easy maintenance, testability, reusability. If you are UI engineer you should have probably heard about package manager. This is a good way to move your reusable components, services there. npm ☝️1. easy to share between teams2. integration in one line - 3. maintenance 4. testing5. 6. private or public (community may help to improve) Why should I do that? import package from ‘package’ semantic versioning If you want to have a it is also possible. private packages As an example you may check this project. _create react redux app structure with build configurations_www.npmjs.com create-react-redux-app-structure In Dependencies list it has 4 public packages which were checked by open source community and improved 👌 ( , , , ). no-internet publish-subscribe-js set-interval famulus How to create npm package? Check out official . (module bundler for JavaScript) may help you to create a new standardized format for code modules included in the ES6 revision of JavaScript. doc Rollup In addition, to the separation of concerns, I would like to mention “Pattern library” as a way to collect user interface design elements. Check out this for more understanding 💪 article Some thoughts are and there: here 👏 👍 Thank you for reading. Suggestions, comments, thoughts are welcome 😎 If you like this, clap, follow me on medium , twitter , github share with your friends
