System Design Templates (1) 1 .Doc: Fill & Download for Free

The below List contains essential things according to me every one student should know.1)Email and other Sharing Hubs:Access e-mail system using username and passwordChange username-password,Receive / read an e-mail message, Reply to an e-mail messageCompose and send an original e-mail messageAttach a file to an e-mail messageMeaning of CC, BCC etc.Some example for sharing your data- Dropbox, Build software better, together etc.2) Everyday Use keyboard shortcutsExample- Ctrl + C, Ctrl + V, Ctrl + Z, Ctrl + Y, Ctrl + X, Ctrl + A, Ctrl + S Ctrl + T, Ctrl + W, Alt + Tab etc. to name a few.Other than CAPS LOCK, which key can you use to insert uppercase/capital letters in a document?3) Basics Of Office toolsKnowledge of Ms-word, Power point and Excel.How to create graphs and pie charts in excelHow to make animations/design templates in power pointHow to drafts letters in MS- word4) Concepts of Internet and Networkinghow to check whether an e-mail address is valid or not?concept of IP address.concept of LAN.name some good search engines.meaning of www, netmask etc.exporting bookmarks to your google drivehow to use google as a calculator?google drive, google doc, google forms etc.5) Concept of command window and folderscreate a directory, edit files, search filesUse of ls, pwd, rm, mv, cp command. (for Linux users and equivalent in windows)How to open two programs simultaneously from your terminal?Concept of chmod, permissions, installing softwares, installing linux on your computer.how to change passwords of your computers?concept of root user on linux?sudo commandconcept of ssh and scp.6) Concept of Memory and Memory devicesbasic knowledge of bits, byte, RAM, ROM, hard disk.What is inside the CPU?What is i5, i7 etc. processor and how are they different?7) Some extra software related to your daily workExample- graph plotters, Latex etc.8) Using net facilitiesnet bankingonline bookingonline shopping9) know about DC++10) Finally, if you are a geek/ computer science student, you should have command over atleast one programming language like C, C++, python, Java or any one you like.As per your interests, you can also participate in competitions on coding at online sites like Sphere Online Judge (SPOJ), Programming Competition,Programming Contest,Online Computer Programming, topcoder etc.These are only some of the things I can suggest anyone at present. As I learn more, I will add the suggestions to the list.Hope you like the answer.

This is a very good question to ask since many people go into hiring freelancers without understanding the intricate details that can make or break your project and/or budget. The advice provided here applies to people who do not have a technical background and also people with a technical background who are new to hiring freelancers and outsourcing development.The first thing you want to do before you hire a freelancer is to see if there are ready made templates or full solutions that can satisfy a majority of your requirements. This will not only save you money but will also get you thinking as to what you really need in your app from a functional user perspective. Templates for iOS can be found on sites like CodeCanyon, an Envato marketplace (I am not affiliated with them). You can also find hybrid templates that work on iOS, Android and other platforms which will require a different set of skills but will allow you to deploy to many more app stores. Templates can be full apps that need customization on the user interface, content and backend development or they can just be themes/mockups/designs for the front-end like CSS/HTML/Javascript or Photoshop/Illustrator design files styling. The great thing about doing this first is you will be better informed and equipped to negotiate a contract and design requirements. Spend at least 16 hours doing this and you will save hundreds of hours in development and design time.Whether you find a full/partial or no design template at all you will still need someone to customize it and integrate it to a backend if you intend to do any kind of networking and server based database work. The assumption you made is that you only need one software engineer. This will be the first thing you want to avoid. Do not hire just one software engineer that says they can do everything. You will eventually need to hire someone else when they are asked to do something they can't handle within your budget and timeline. It is also better to use the terms front-end, user interface, back-end, integration, developer, programmer, designer, architect than software engineer since software engineer is a vague term and for some people it is a technically incorrect use of the term engineer. So what do you need to do? Since this may be your first iOS app I suggest you work with an agency that has a team of developers and can give you a fixed price on the full project from design, development, testing, deployment and maintenance. This will reduce your costs (not guaranteed) since you can negotiate a better fixed price and also increase (not guaranteed) your chances of the project coming in on time and within budget.Before you create a job post you will want to create a detailed requirements document that can be a simple spreadsheet or text document listing everything you need the app to do from a user perspective. Also create a flowchart to help visualize how your users will flow through the app. The more detail the better. This will serve as your user interface, use case and functional requirements document all in one. There are many online resources that teach you how to do these requirements docs so I won't detail them here. Most well managed projects will have separate documents for each but you will be able to accomplish the same with one or two very well thought out requirements doc. You will not be able to create the technical design unless you have done many of these in the past. This is where the design/template research will come in handy as you will be able to include readymade screenshots of your concept. Without existing readymade designs you will need to at least create wireframe designs which show each and every screen/view your app will have. Everything from login/signup forms, to settings, lists, data entry forms, popups etc... Do not leave any screen/view out. You can draw them by hand or use any drawing/design tool you want. The key is to include everything the user will have to interact with since this will determine how you build the client front-end (what the user sees on their mobile device) and back-end (server and database code that does work). If the team you hire is good they will let you know up-front in their proposal if there are any issues. Spend at least 80 hours on developing your requirements and you will save countless hours in change requests, meetings and overall distress. Get feedback from potential users and modify accordingly until you feel your users are getting what they need. This is very important since they will tell you what they need not what you think they need. The design requirements should be at least half of the effort and be completed before you create a job post.Once you have the design doc(s) with screenshots, user functionality and screen flow requirements you can create the job post. Fill out the form and include a summary description of your app. You don't have to give any details of what the app will be used for just what it will do. Upload your requirements doc(s) and reference them in your summary description. Select that you are only looking for agencies at this time unless you want to hire 3-5 different freelancers and manage them (don't do this). At the end you will be able to ask questions you want answered in your proposal. Some of the questions I like to ask are:Show 1-2 mobile applications (in your case iOS) that are currently in the app store. -Eliminate any proposal that did not provide this.Who will be part of the project team? -Eliminate any proposal that does not include a PM, Business Analyst, Tech Lead-Developer, Mobile iOS Developer, Designer (Optional if you have designs ready made), Back-End Developer, Testers. Some roles can be done by the same person such as PM/BA. Front/Back End developer can sometimes be the same person if the project is not too complicated (judgement call). Developers should not be the testers. You will negotiate with the account manager who will be there if you have any complaints/issues with the quality of work or performance.What is the expected duration (how long from start to finish) of the project?What is the expected effort in hours of the project?What is the guarantee period after delivery of the app?Do you provide app store submission services? -Optional unless you need someone to do the app store deployments with your app store account.Describe your development process and what will be expected of the client.What are some potential issues with the job requirements/description?What technologies will you use for the front and back end? For front end iOS they will say Swift, Ojective-C or Cordova/PhoneGap/Ionic. For full native use swift as that is the language Apple will be solely supporting in the future. Use Cordova for hybrid apps. Objective-C as a last resort. Back-end database and server language can be anything although you will probably want to go with what makes sense for your business/app. You can use something like Parse which provides a full back-end as a platform or build your own on something like Node/MongoDB and host on AWS/Azure/Bluemix or any cloud provider.What online project tracking tool do you use?What online code repository do you use for version management and delivery?Ask anything else you want related to your specific app.Stating your fixed price budget is a bit more involved. If you price it too low you may not get as many quality proposals. Too high and proposals will always be close to your budget without taking into account the true cost. This takes time and experience to get right but here are some numbers based on the costs I have seen to get you started:$1k and below will get you the simplest of apps with little to no back-end integration. Not recommended for full customer facing app. Will be good for proof of concept apps that are not for production use. I will often do these small projects to test out an idea with potential customers. It will have enough functionality to give users something tangible to provide feedback on. This is also a good way to vet a team without risking too much budget.$1k-5k will get you most simple (1-2 database sets without advanced user management) data driven apps (not high end games or large database/back-end integrations) for one native platform or hybrid app.$5k-10k will allow you much greater flexibility in terms of what you can build and allow you to target iOS and Android native apps.$10k-20k will get you most anything data driven.$20k+ I would not put a budget of this size. Best approach is to break down your project into separate jobs with short 3 or less months duration.Leave your job open for at least one week but no more than two weeks. Once you start getting proposals eliminate all proposals that do not meet your criteria for budget, timeline, process, team etc... You will get a sense of the of the right price after getting about 12 proposals. Get rid of the top and lowest bids right off. Ask additional questions based on the answers provided from your initial questions. Narrow down your list to a 3-4 finalists. Schedule a Skype or phone interview for an hour and get to know how they speak, communicate and overall how you get along. If they say yes to everything you ask eliminate them. For people without a technical background I recommend you hire another freelancer with a lot of experience on an hourly basis ($50-80 per hour, 5 star reviews, similar projects to your own) to evaluate the agency during your interview. This freelancer can be your on-demand consultant when you need objective technical advice. After many projects you may have more than one go-to people who you trust.Once you select a proposal it's time to negotiate terms. Send them your NDA doc to sign as part of the agreement. Clearly state how long the vendor will provide fixes for any issues found after delivery of your app. Clearly state that your milestones will be considered delivered once the code has been checked into via your Github or similar code repository. You can have someone review the code if needed at this point before payment. Collect any tax documents/info like an I-9 if needed. I don't think this will ever be used to sue someone but it let's them know you don't want anything shared outside their company for any reason. Price can still be negotiated but typically I don't do that if the price is not an issue and will only save you a couple hundred dollars as it just wastes time and provides a tiny bit of incentive to the vendor to under deliver/perform. You can set bonus (5-10%) contingencies for early or on time delivery of your app. This provides a good positive motivation and return on your investment if your timeline is strict. Break your milestones into 2 week deliverables. Only fund the first two milestones. Do not pay anything upfront although some will ask for an initial fee to get started. Do not release payment until the milestone has been met. Use your requirements doc to break up the work and make each requirement part of one of the milestones. If the requirements is not met then do not move forward. Have them agree to the milestones or have them provide their suggested milestones and hold them to it. Stop working with the agency if they do not deliver the first 2 milestones as required and on time.While working with team make sure they are always available on Skype or on the phone for whatever reason. Use an online project management tool to keep track of requirements and dates. I use Asana to keep things simple and allow the vendor to create and manage tasks as well. There are other tools with more technical functions but those should be used and managed by the vendor and not the client. Your concern is with the requirements and timeline not bug tracking. Meet at least 2 times a week with the PM/BA to go over any issues and review changes to the timeline. Nothing should be a surprise. Keep archives of all chats and emails not done through the Upwork system. End the project if they consistently take more than a day to get back to you. Use the first two weeks as a probationary period if you have never worked with them before. At the end of two weeks decide if you want to keep working with them or let them go. If you have any doubts let them know your concerns within a few hours of experiencing your issue with written proof. Give them time correct the issue or let them go if they do not improve. Make sure you have a good reason though. If you start having issues with more than a couple of teams it may be that you are the problem and not the team.At the end of your project when everything has been delivered as required determine if there are any changes that came up during the project that you need implemented. You can address these changes during the project timeline but keep into account that your initial timeline will be affected. If you start doing more than a few change requests during your project it is best to stop the project and start it over again once you figure out your requirements again. During the guarantee period (should be at least 30-90 days) make sure you report issues immediately and keep track of them using your project management tool. At this point you have already provided all payments so fixes will be dependent on the vendor to abiding by their guarantee.Treat your vendor team members well but if you are having to many unresolved issues early on it is best to cut them loose within a couple of weeks and find another team. There should not be any need to threaten or micro-manage any of your teams if they are professional and listen to your concerns. Let them know when they are doing something well. If you have to cancel a project due to an issue that is not due to the vendor you should provide an appropriate review and let them know as soon as you can when you will end the project. Provide a bonus at the end of the project if they exceed your expectations. You get reviewed as well.There is a lot more not covered but this should provide a good starting point for your endeavors. Feel free to ask any other questions.

1. Using BoilerplateBoilerplate is a front-end kickstart template that contains a series of best practices and common inclusions. It offers a generic files/folders structure, HTML5-ready template and basic server-side global configurations. It’s like blueprint for your house, but without the building blocks. You have the idea what you’re going to build and you have made all preparation steps, but you don’t have the materials needed to actually build the house. You are free to include “the missing” HTML/CSS/JavaScript components from anywhere else, including from Bootstrap.At first glance Boilerplate may seem a quite simple template, but in fact it gives you many benefits that can’t be seen immediately. Let’s check out some of them:HTML5-ready template plus basic structure for your files and foldersReady-to-use, performance optimized print stylesCross-browser compatibilityMobile browser optimizationsProgressive enhancement and graceful degradationBest-practice server configurationsOptimal caching and compression rulesOptimized Google Analytics snippet codeand more…You get all these goodies by default, without need of writing a single line of code. And here is the content of the default download:css – a directory containing normalize.css, and main.css with Boilerplate’s defaults, common helpers, media queries, and print styles.doc – a directory containing all Boilerplate’s documentation. You can use it as the location for your own project’s documentation.img – an empty folder for your imagesjs – a directory containing main.js for your custom code and plugins.js containing the code for all your plugins. Also there are Modernizr and jQuery libraries placed in vendor subfolder..htaccess – default web server configurations for Apache. For other servers there is Server Configsrepository.404.html – a very basic error pageapple touch iconscrossdomain.xml – a template for working with cross-domain requests.favicon.icohumans.txt – a file to include credits for you and your project.index.html – default HTML5-ready template, the base of all pages on your web site.robots.txt – a file to include any pages you want to be hidden from search engines.From this point on, you can start building your web site just by adding your own code and the components you have chosen to use in your project.2. Using BootstrapBootstrap is a front-end framework and web design kit for building modern web sites. With Bootstrap you can build an entire web site from scratch. So it gives you not only a starting point, but also all the building blocks you may need to create your site. The Bootstrap’s download contains only files for CSS and JS components, plus an icon font. Eventually you can download also a basic template to get started with. There is no files/folders structure or any server-side configurations.Benefits/Highlights:Mobile-first approachBrowser compatibilityAccessibilityCSS grid systemReady-to-use components and utilitiesand more…Components and utilities are listed below:Grid – a utility for laying out your designIcons – resolution independent icon setCSS base styling classesCSS components – styled HTML componentsJS widgets – a nice set of interactive componentsStarting templates and examplesAs you can see Bootstrap provides all the components you can start using right now to build your web site.