Kayıtlar

2019 tarihine ait yayınlar gösteriliyor

SDLC - Software Development Life Cycle

Resim
SDLC -  Software Development Life Cycle  is a process used by the software industry to design, develop and test high quality softwares. 1- Requirement Analysis 2- Defining Requirements To clearly define and document the product requirements SRS (Software Requirement Specification)   document which consists of all the product requirements to be designed and developed during the project life cycle. 3-   Designing the Product Architecture One design approach for the product architecture is proposed and documented in a DDS - Design Document Specification . DDS is reviewed by all the important stakeholders and based on various parameters as risk assessment, product robustness, design modularity, budget and time constraints, the best design approach is selected for the product. DDS defines all the architectural modules of the product along with its communication and data flow representation with the external and third party modules. 4- Developing the ...

Best Practices

Best Practice 1- Keep Reading Existing Software Source Code Best Practice 2 - Complete your documents before next step Best Practice 3 - Follow the defined standards, don't create it Best Practice 4 - Code should be written to be reviewed criticism about one or more of the following points; Bad coding Not following standard Not keeping performance in mind History, Indentation, Comments are not appropriate. Readability is poor Open files are not closed Allocated memory has not been released Too many global variables. Too much hard coding. Poor error handling. No modularity. Repeated code. Best Practice 5 - Testing to be followed like a religion Best Practice 6 - Keep your Code and Documents Safe Best Practice 7 - Keep your Tools & Techniques Handy the essential tools, which should be readily available with a software developer: A good text editor to write and edit the program. A nice debugger to debug the program. A memory detector in case yo...

Compass - Important Notes

if we overuse it might make our code too complex and hard to read.  The most useful feature of Compass are; sprites ,  vertical rhytm,  horiznal lists, creating vendor prefixes.  However it is still better idea to use Autoprefixer over mixins for creating vendor prefixes.  Why?  Because Autoprefixes is a process that is gonna work even if you do not use compass/sass. You do not need to learn a new code. You also can keep having tips in your IDE when you want to change something. Autoprefixer is a PostCSS plugin which parse your CSS and add vendor prefixes. Href :  https://autoprefixer.github.io/ https://fatihhayrioglu.com/browserlist-ve-autoprefixere-guncelleme/

Compass - Horizontal List

HTML Code <!DOCTYPE html > < html lang= "en" > < head > < meta charset= "UTF-8" > < title > Compass </ title > < link href= "stylesheets/screen.css" media= "screen, projection" rel= "stylesheet" type= "text/css" /> < link href= "stylesheets/print.css" media= "print" rel= "stylesheet" type= "text/css" /> <!--[if IE]> <link href="stylesheets/ie.css" media="screen, projection" rel="stylesheet" type="text/css" /> <![endif]--> < link href= "stylesheets/index2.css" rel= "stylesheet" type= "text/css" /> </ head > < body > < ul id= "social-links" > < li class= "social_blogger" ></ li > < li class= "social_facebook" ></ li ...

Compass - Browser Support - Continue

D:\WebstormProjects\emptyProjectForCompass> compass interactive >> browsers() ("android", "android-chrome", "android-firefox", "blackberry", "chrome", "firefox", "ie", "ie-mobile", "ios-safari", "opera", "opera-mini", "opera-m obile", "safari") >> browser-versions(ie) ("5.5", "6", "7", "8", "9", "10", "11") >> browser-versions(firefox) ("2", "3", "3.5", "3.6", "4", "5", "6", "7", "8", "9", "10", "11", "12", "13", "14", "15", "16", "17", "18", "19", "20", "21", "22", "23", "24", "25 ", "26", ...

Compass - Browser Support

style.scss @import "compass" ; $debug-browser-support : true ; p { border : 2 px solid black ; @include border-radius ( 12 px ); } a { @include opacity ( 0.5 ); @include single-transition ( all , 5 s ); & : hover { font-size : 28 px ; color : red ; } } output: /* line 5, ../sass/style.scss */ p { border : 2 px solid black ; /* Capability border-radius is prefixed with -moz because 0.25036% of users need it which is more than the threshold of 0.1%. */ /* Creating new -moz context. */ -moz-border-radius : 12 px ; /* Capability border-radius is not prefixed with -ms because 0% of users are affected which is less than the threshold of 0.1. */ /* Capability border-radius is not prefixed with -o because 0% of users are affected which is less than the threshold of 0.1. */ /* Capability border-radius is prefixed with -webkit because 0.1583% of users need it which is more than the threshold of 0.1%. */ /* Creating new -webkit context. ...