{"id":1053,"date":"2018-09-19T15:43:32","date_gmt":"2018-09-19T12:43:32","guid":{"rendered":"https:\/\/enisnecipoglu.com\/?p=1053"},"modified":"2018-09-20T10:04:27","modified_gmt":"2018-09-20T07:04:27","slug":"saas-proje-gelistirmek","status":"publish","type":"post","link":"https:\/\/enisnecipoglu.com\/en\/saas-proje-gelistirmek\/","title":{"rendered":"SaaS Project Development"},"content":{"rendered":"<h2> What is SaaS ?<\/h2>\n\n\n\n<p> You can find a lot of articles about SaaS. I&#8217;ll try explain it simply. For example; Instead of developing a calculator and deploy it to users, developing a service on server and users are using it via connecting to server. Users are chareged by using duration or usage volume. Finally you can sell that calculating system as a service. You&#8217;re using a lot of SaaS product in daily usage like Spotify, Netflix, Microsoft Office 365, Google Apps(GSuite, G.Drive, Gmail&#8230;)<\/p>\n\n\n\n<h2> Indispensable of SaaS Architecture<\/h2>\n\n\n\n<p>There is some important elements to run a SaaS project. For example, Users should feel safe while using the service and need to know their datas are safe in the service.\u00a0 By the way, users want support from paid service, and they want improvements and new features on service. They want to reach the service from different platforms. There is much more reasons to follow one or more element while developing a SaaS Project: <\/p>\n\n\n\n<h3>Essential\u00a0design elements<\/h3>\n\n\n\n<ul><li><strong>Multi-tenancy:<\/strong>\u00a0A\u00a0single instance of software should serve all tenants simultaneously.\u00a0 You can read about Multi-Tenancy from <a href=\"https:\/\/en.m.wikipedia.org\/wiki\/Multitenancy\">here<\/a><\/li><li><strong>Scalability:<\/strong>\u00a0Project, system, network or process should can handle growth or dwindle while it&#8217;s working. New features can be added project or some fetures can be removed from project. You can visit <a href=\"https:\/\/en.wikipedia.org\/wiki\/Scalability\">here <\/a>for more information<\/li><li><strong>Discov<\/strong><strong>erability:<\/strong>\u00a0 Users should use software without any need for additional setup from service provider. Proccess should be Qucik and Easy <\/li><li><strong>Reachability:<\/strong>\u00a0\u00a0Software should be available to all potential customers. <\/li><li><strong>Security:<\/strong>\u00a0\u00a0Software should provide an adequate\u00a0level of protection for customer data. Both database and communication channels should be encrypted and coupled with a secure authorization\u00a0process. <\/li><li><strong>Customization:<\/strong>\u00a0  Users should customize software by themselves. By the way it&#8217;s good way to stay users in sevice and increase brand advocacy.<\/li><li><strong>Support:<\/strong>\u00a0\u00a0Software should provide adequate level of customer support. Updates should be issued as fast and frequently as possible to help reduce the number of potential calls. <\/li><\/ul>\n\n\n\n<h2>Development Proccess<\/h2>\n\n\n\n<p>Development proccess is most important part of SaaS. Software must provide an architecture which supports essential design elements.\u00a0 There is some software development methodologies below:<\/p>\n\n\n\n<ul><li><strong>Waterfall Model:<\/strong>\u00a0That model follows phases and order is System, Analysis, Design, Coding, Testing, Operations. In that model development processess work step by step. You can read more from <a href=\"https:\/\/en.wikipedia.org\/wiki\/Waterfall_model\">here<\/a>. <br\/><\/li><li><strong>Spiral Model:<\/strong>\u00a0The\u00a0spiral model\u00a0is a risk-driven\u00a0software development process\u00a0model. Based on the unique risk patterns of a given project, the spiral model guides a team to adopt elements of one or more process models.<\/li><li><strong>Rapid application development:<\/strong>\u00a0In general, that method approaches to software development put less emphasis on planning and more emphasis on an adaptive process. Prototypes are often used in addition to or sometimes even in place of design specifications.<\/li><li><strong>Agile:<\/strong> In that method, requirements and solutions evolve through the collaborative effort of self-organizing and cross-functional teams and their customers or users. It advocates adaptive planning, evolutionary development, early delivery, and continual improvement, and it encourages rapid and flexible response to change.<br\/><\/li><\/ul>\n\n\n\n<p>There is much more development methods you can find. Agile is most popular method currently. Methodologies can be changed by you depending your requirements and project standards. Theese are only approaching style, they are not rule.<\/p>","protected":false},"excerpt":{"rendered":"What is SaaS ? You can find a lot of articles about SaaS. I&#8217;ll try explain it simply. For example; Instead of developing a calculator and deploy it to users, developing a service on server and users are using it via connecting to server. Users are chareged by using duration or usage volume. Finally you can sell that calculating system as a service. You&#8217;re using a lot of SaaS product in daily usage like Spotify, Netflix, Microsoft Office 365, Google Apps(GSuite, G.Drive, Gmail&#8230;) Indispensable of SaaS Architecture There is some important elements to run a SaaS project. For example, Users should feel safe while using the service and need to know their datas are safe in the service.\u00a0 By the way, users want support from paid service, and they want improvements and new features on service. They want to reach the service from different platforms. There is much more reasons to follow one or more element while developing a SaaS Project: Essential\u00a0design elements Multi-tenancy:\u00a0A\u00a0single instance of software should serve all tenants simultaneously.\u00a0 You can read about Multi-Tenancy from here Scalability:\u00a0Project, system, network or process should can handle growth or dwindle while it&#8217;s working. New features can be added project or some fetures can be removed from project. You can visit here for more information Discoverability:\u00a0 Users should use software without any need for additional setup from service provider. Proccess should be Qucik and Easy Reachability:\u00a0\u00a0Software should be available to all potential customers. Security:\u00a0\u00a0Software should provide an adequate\u00a0level of protection for customer data. Both database and communication channels should be encrypted and coupled with a secure authorization\u00a0process. Customization:\u00a0 Users should customize software by themselves. By the way it&#8217;s good way to stay users in sevice and increase brand advocacy. Support:\u00a0\u00a0Software should provide adequate level of customer support. Updates should be issued as fast and frequently as possible to help reduce the number of potential calls. Development Proccess Development proccess is most important part of SaaS. Software must provide an architecture which supports essential design elements.\u00a0 There is some software development methodologies below: Waterfall Model:\u00a0That model follows phases and order is System, Analysis, Design, Coding, Testing, Operations. In that model development processess work step by step. You can read more from here. Spiral Model:\u00a0The\u00a0spiral model\u00a0is a risk-driven\u00a0software development process\u00a0model. Based on the unique risk patterns of a given project, the spiral model guides a team to adopt elements of one or more ","protected":false},"author":1,"featured_media":1072,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[6],"tags":[63,65,66,64,62],"_links":{"self":[{"href":"https:\/\/enisnecipoglu.com\/en\/wp-json\/wp\/v2\/posts\/1053"}],"collection":[{"href":"https:\/\/enisnecipoglu.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/enisnecipoglu.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/enisnecipoglu.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/enisnecipoglu.com\/en\/wp-json\/wp\/v2\/comments?post=1053"}],"version-history":[{"count":20,"href":"https:\/\/enisnecipoglu.com\/en\/wp-json\/wp\/v2\/posts\/1053\/revisions"}],"predecessor-version":[{"id":1082,"href":"https:\/\/enisnecipoglu.com\/en\/wp-json\/wp\/v2\/posts\/1053\/revisions\/1082"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/enisnecipoglu.com\/en\/wp-json\/wp\/v2\/media\/1072"}],"wp:attachment":[{"href":"https:\/\/enisnecipoglu.com\/en\/wp-json\/wp\/v2\/media?parent=1053"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/enisnecipoglu.com\/en\/wp-json\/wp\/v2\/categories?post=1053"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/enisnecipoglu.com\/en\/wp-json\/wp\/v2\/tags?post=1053"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}