Home
Search results “Functional specification of product”
Documenting Functional Requirements
 
06:26
An important step to picking the right software is to document Functional Requirements. This video describes the process of documenting Functional Requirements. Stakeholders will be the people who provide your project's software requirements. For more information, please visit website WWW.SOFTREQ.COM where you will find more useful information such as Business Requirements document templates, completed Business Requirements document, training videos, FAQ's, etc.
Views: 116949 Terry Reiber
Functional specification
 
06:05
A functional specification (also, functional spec, specs, functional specifications document (FSD), functional requirements specification, or Program specification) in systems engineering and software development is the documentation that describes the requested behavior of an engineering system. The documentation typically describes what is needed by the system user as well as requested properties of inputs and outputs (e.g. of the software system). A functional specification is the more technical response onto a matching requirements document, e.g. the Product Requirement Document "PRD". Thus it picks up the results of the requirements analysis stage. On more complex systems multiple levels of functional specifications will typically nest to each other, e.g. on the system level, on the module level and on the level of technical details. This video is targeted to blind users. Attribution: Article text available under CC-BY-SA Creative Commons image source in video
Views: 9542 Audiopedia
How To Write A Project Specification
 
06:22
In this video, Dave describes a basic brainstorming approach that anyone can use to write requirement and specification documents. http://www.SourceSeek.com - Connect WIth Top Offshore Software Teams SourceSeek (www.sourceseek.com) matches your software projects for free with trusted dev teams in the U.S. and around the world. Whether you're a startup founder, small-business owner, or Fortune 100 manager, you need to get it right the first time. But too often, software projects fail, resulting in wasted time and money. SourceSeek is here to help you keep your project on-time and on-budget, and your development partners highly motivated. Our founder, Dave Hecker, is one of the foremost experts on outsourcing software, web, and mobile development projects. We're passionate about teaching both clients and vendors what they can do to ensure the success of their projects. Here's what we do, in as little as two weeks: - Quickly and efficiently assess a client's needs - Intelligently match you to a dev team for your product or project needs - Co-pilot to help you optimize distributed teams and see instant results SourceSeek is free for clients; we find you the best teams and the perfect match. It's that simple. Watch all our videos, send us feedback, and tell us about your project at http://www.sourceseek.com/get-started-now/. SUBSCRIBE NOW FOR MORE OUTSOURCING VIDEO TIPS AND NEWS! https://www.youtube.com/subscription_center?add_user=sourceseek LET'S CONNECT! Google+ ► http://google.com/+Sourceseek Facebook ► http://facebook.com/SourceSeek Twitter ► http://twitter.com/SourceSeek Linkedin ► https://www.linkedin.com/company/sourceseek Pinterest ► http://www.pinterest.com/SourceSeek SourceSeek ► http://www.sourceseek.com
Views: 120459 SourceSeek
Writing an App Specification
 
04:37
In this video I talk about what makes a good specification for building an app. In these times of agile development practices, it's tempting to just go ahead and write the code from simple requirements, and then refine during short iterations with the users and stakeholders. This may actually work for the development, but already when starting to test it becomes difficult without complete requirements. There are many practices for documenting the architecture and requirements of a solution and the most common methodologies (e.g. RUP, TOGAF, etc) divide them into a number of different documents, which is the main reason that many promote a simpler approach. In an attempt to find a middle path, I will show you a template that I've created by merging the best from the common methodologies, but still keeping everything in one single document. The specification template consists of mainly three parts, and they are the conceptual, the logical, and the physical views of the solution. The conceptual solution answers the question "what?" as in "what the mobile solution will do?", and include the functional and non-functional requirements. It starts with an overview figure and description, followed by the user stories (or simplified use cases). The user stories are complemented by screen mockups of all the screens in the app. If a screen is very complex, which should be avoided if possible (apps should be simple), several mockups may be needed for that screen. Following the user stories is a brief description of the service calls and data that the app will use, and finally comes the non-functional requirements (e.g. security, availability, etc). The conceptual solution is very useful during the implementation, and in the creation of test cases to verify the quality of the solution. The logical solution answers the question "how?" as in "how will the solution be implemented?", and describe the main parts of the solution, but without being specific on what technologies and products to use. It starts with a figure followed by a description of the different parts of the solution. The logical solution is essential when it comes to compare and select the final physical solution. For example, it can be shared with different suppliers, which can come back with a suggested physical solution based on their products. The physical solution answer the question "with what?" as in "with what will the solution be realized?", and describe the actual products and technologies used as well as solution details (service interfaces, database structures, etc). It also starts with a figure that is similar to the one in the logical solution, but here each part of the solution is also specified with the actual technology or product that will be used to realize that part. In the description of the figure, all details about each technology and product are provided (like edition, version, etc). Then service interfaces are documented with request format, parameters and their data types, returned entities and their data types, response and error codes, etc. The database tables are specified with attributes and their data types, primary keys, etc. An important point about a document like this is to ensure that it's a living thing throughout the project, and therefore I recommend storing the document using a cloud service (e.g. Google Drive). When requirements or technical solutions change, make sure that the document is updated so that it's aligned with the implemented solution. This way, the document will automatically become the system documentation. So there you have an example of what a good specification for building an app can look like. You can find the actual template on http://cforsberg.com/?p=145. Follow me on Twitter https://twitter.com/chrisforsberg Visit my site http://cforsberg.com
Views: 8774 Chris Forsberg
Functional Requirements
 
04:44
Business Unit asking for a product.
Views: 71683 Curtis Owings
Writing Specifications
 
24:06
An online training module for agency procurement officers working with the West Virginia Purchasing Division.
Views: 4447 WVPurchasingDivision
software requirement specification | software engineering |
 
08:13
software engineering software requirement specification
Views: 28597 Education 4u
Writing Requirements: Write Functional Requirements - Traditional, Agile, Outsourcing
 
11:41
Writing Requirements: Write Functional Requirements is an excerpt from Requirements: The Masterclass LiveLessons--Traditional, Agile, Outsourcing (Video Training). Purchase full course at informit.com/YouTube and save 50% with code YOUTUBE. Also available in Safari subscription service. 13+ Hours of Video Training - Requirements: The Masterclass LiveLessons--Agile, Traditional, Outsourcing is a video course covering requirements, whether they are the requirements for software, a service, or a product. This video teaches the requirements process from initiation and scoping, through investigating the work being done and then determining the optimal solution to improve that work. After this course, business analysts, agile team members, and others concerned with requirements will be able to discover the correct requirements and communicate them precisely and unambiguously to the product developers. Description This video course teaches you how to become a requirements wizard--it covers the gamut of the requirements activities. It begins with how to scope the problem using a context model and then how to use business events and business use cases to subdivide the problem space into manageable and convenient chunks. It looks at how to uncover the real problem--something not done on many projects--and then how to find its optimal solution. Then the video show how to write unambiguous and correct stories or requirements to ensure correct development. The course includes some downloadable material that enhances the video lessons and provides exercises to sharpen your requirements skills. Skill Level Intermediate to advanced What You Will Learn How to discover and elicit requirements How to write unambiguous and testable requirements How to write the correct agile stories How to run your requirements project, whether it’s an agile, traditional, outsourced, or OTS project How to understand the role of good requirements in agile development How to scope the business problem How to ensure the scope and the stakeholders match the goals How to study the business How to find the right solution to the real business problem How to review the requirements How to trace requirements How to get requirements right Who Should Take This Course Business analysts who want to be more effective in their requirements work Product owners and product/program managers Agile team members who want to improve the accuracy of their deliverables Users and software customers who want to ensure the requirements process is delivering what they need Course Requirements Basic understanding of the need for requirements in the development process http://www.informit.com/store/requirements-the-masterclass-livelessons-traditional-9780134189758?WT.mc_id=Social_YT
Views: 12243 LiveLessons
Conformance and Performance Specification
 
08:34
Here we are trying to discuss Conformance Specification and Performance Specification https://youtu.be/ow4oOhsxuPk Hope the Video is useful. Subscribe to the channel for more procurement and other management functions related videos. Purchasing and Procurement: https://youtu.be/ntHnQrQBG2Y 5 Rights Of Procurement: https://youtu.be/wpKQWvVYnME Total Cost Of Ownership: https://youtu.be/YKdcEOTA7Pk Content : The purpose of procurement specification, and the 2 types of specification, various forms, major differences, etc
Views: 4310 P&S Buddy
Product Requirements Document (PRD) of an Online Product
 
03:02
Click Here To See More From This Expert: http://www.docstoc.com/profile/Jason Product Requirements Document (PRD) of an Online Product Jason Nazar, co-founder and CEO of Docstoc (docstoc.com), explains the best way to put together the PRD. The main function of your site is conveyed by the PRD which Jason elaborates on. Docstoc has over 20 million business and legal documents to help you grow and manage your small business and professional life. Thousands of how-to articles and videos with fresh content uploaded every day. Attorney reviewed documents to save you time and money. Connect with us on Facebook - http://www.facebook.com/DocstocFB Connect with us on Twitter - https://twitter.com/#!/docstoc Connect with us on Google+ - https://plus.google.com/103801755756812961700 Keywords: "Small business" Entrepreneurs Entrepreneurship "How to start a business" "Starting a business" Startups "Startup business" Financial Success DIY "Docstoc Videos" Docstoc
Views: 5950 docstocTV
Video 13 - Use Cases and Functional Requirements
 
04:53
Use Cases and Functional Requirements by Karl Wiegers for Enfocus Solutions www.EnfocusSolutions.com
Views: 42074 Enfocus Solutions
Q: what is functional and technical spec?
 
17:21
A: A functional and technical specs include what a component is supposed to do. For example if you are trying to build an application where you need to upload pictures and then present them in certain format those function specifications would be to allow the application to upload multiple pictures at the same time or allow the application to upload one picture at a time and then select the kind of slide show that you want. You should be able to sort of set the duration of this slide show you should be able to set the priority of a images and all those things. Functional specification defines what exactly and how exactly do you want a product to function or let us say a component to function.
Views: 14825 TechGig
Product Specification
 
01:04
Views: 1138 sahilmudassar
What is FUNCTIONAL DESIGN? What does FUNCTIONAL DESIGN mean? FUNCTIONAL DESIGN meaning
 
03:27
What is FUNCTIONAL DESIGN? What does FUNCTIONAL DESIGN mean? FUNCTIONAL DESIGN meaning - FUNCTIONAL DESIGN definition - FUNCTIONAL DESIGN explanation. Source: Wikipedia.org article, adapted under https://creativecommons.org/licenses/by-sa/3.0/ license. Functional Design is a paradigm used to simplify the design of hardware and software devices such as computer software and increasingly, 3D models. A functional design assures that each modular part of a device has only one responsibility and performs that responsibility with the minimum of side effects on other parts. Functionally designed modules tend to have low coupling. The advantage for implementation is that if a software module has a single purpose, it will be simpler, and therefore easier and less expensive, to design and implement. Systems with functionally designed parts are easier to modify because each part does only what it claims to do. Since maintenance is more than 3/4 of a successful system's life, this feature is a crucial advantage. It also makes the system easier to understand and document, which simplifies training. The result is that the practical lifetime of a functional system is longer. In a system of programs, a functional module will be easier to reuse because it is less likely to have side effects that appear in other parts of the system. The standard way to assure functional design is to review the description of a module. If the description includes conjunctions such as "and" or "or", then the design has more than one responsibility, and is therefore likely to have side effects. The responsibilities need to be divided into several modules in order to achieve a functional design. Every computer system has parts that cannot be functionally pure because they exist to distribute CPU cycles or other resources to different modules. For example, most systems have an "initialization" section that starts up the modules. Other well-known examples are the interrupt vector table and the main loop. Some functions inherently have mixed semantics. For example, a function "move the car from the garage" inherently has a side effect of changing the "car position". In some cases, the mixed semantics can extend over a large topological tree or graph of related concepts. In these unusual cases, functional design is not recommended by some authorities. Instead polymorphism, inheritance, or procedural methods may be preferred. Recently several software companies have introduced functional design as a concept to describe a Parametric feature based modeler for 3D modeling and simulation. In this context, they mean a parametric model of an object where the parameters are tied to real-world design criteria, such as an axle that will adjust its diameter based on the strength of the material and the amount of force being applied to it in the simulation. It is hoped that this will create efficiencies in the design process for mechanical and perhaps even architectural/structural assemblies by integrating the results of finite element analysis directly to the behavior of individual objects.
Views: 1263 The Audiopedia
#3 - Business Requirements vs. Functional Specifications. How to decide which is which (BRD vs SRS)
 
14:09
Article from this video: https://LEARN.BA/requirements-done-yet/ Sign up for our email list to get the latest materials we release | http://LEARN.BA/connect/ http://LEARN.BA for BA Education http://BARIALI.COM for BA Consulting
Views: 560 LEARN.BA
Software Specification Document: Why does your project need one? — All about Apps by Cleveroad Inc.
 
04:57
Full article — https://www.cleveroad.com/blog/why-you-need-a-great-specification-for-your-project Hardly any software development project was implemented successfully without specifications. That is true for a number of reasons. First of all, software development, be it an app or website, is a complicated and, let’s face it, risky process at times. Well-grounded and well-thought documentation can help reduce or even eliminate the majority of those risks. So, this edition of All About Apps video series is devoted to the secrets of creating proper software development documents. You deserve to know more! Enjoy your watching and don’t forget to leave us your feedback.
Importance of Design Specifications
 
12:25
Professor Turner talks about the product design specification.
Views: 8448 Wisconsin Mrsec
QC Specification -Good Documentation
 
14:58
This video go over basic Quality department structure , function and cross functional department practices. How a QC department work in life science company and what to expected from a QC role. QC function include use Specification and test data sheet while performing the tests. Getting to know about specification structure help you present better in job interview.
Views: 385 gourav pandey
Software Requirement Specification SRS Document in hindi/urdu | SoftwareEngineering
 
16:59
Brief: This video is about how to make Software Requirement Specification document in Software Engineering. It is the complete lecture, at the end A real SRS is also shown by the teacher to make the concept more clear. ===================================================== Link to Functional and Non-Functional requirement Lecture: https://youtu.be/02AouF6wXz4 Link to Gantt Chart Lecture: https://youtu.be/k8y6Uotw8go ===================================================== What is SRS? A documents use to describe the behavior of the software System, Functional, Non-Functional requirements of the software system. Users of the SRS? Development Team Maintenance Team Clients Technical writers Contents of the SRS are also well define in the Video. Real SRS Document is also shown by the teacher. Download Link to Slides (pdf) Link : https://www.dropbox.com/s/fhd19vfii1bbknv/SRS-Slides%20PPT.pdf?dl=0 ===================================================== Download link to SRS Template of (virtual Class Room System) Link : https://www.dropbox.com/s/wzs5e7wpwdm1rcp/SRS.pdf?dl=0 ===================================================== Subscribe our YouTube channel: https://www.youtube.com/SoftwareEngineering Like us on Facebook: https://www.facebook.com/SoftwareEngineeringYT Follow us on twitter: https://www.twitter.com/imsoftwareeng
Views: 18525 Software Engineering
Functional and Nonfunctional Requirements - Georgia Tech - Software Development Process
 
01:37
Watch on Udacity: https://www.udacity.com/course/viewer#!/c-ud805/l-1729809167/m-672908660 Check out the full Advanced Operating Systems course for free at: https://www.udacity.com/course/ud805 Georgia Tech online Master's program: https://www.udacity.com/georgia-tech
Views: 63176 Udacity
Functional misspecification 1
 
05:33
This video provides some explanation of what is meant by 'functional misspecification' of an econometric model, and some of the effects this has on estimators. Check out https://ben-lambert.com/econometrics-course-problem-sets-and-data/ for course materials, and information regarding updates on each of the courses. Quite excitingly (for me at least), I am about to publish a whole series of new videos on Bayesian statistics on youtube. See here for information: https://ben-lambert.com/bayesian/ Accompanying this series, there will be a book: https://www.amazon.co.uk/gp/product/1473916364/ref=pe_3140701_247401851_em_1p_0_ti
Views: 24771 Ben Lambert
Lecture -5 Requirements Engineering / Specification
 
56:39
Lecture Series on Software Engineering by Prof.N.L. Sarda, Prof. Umesh Bellur,Prof.R.K.Joshi and Prof.Shashi Kelkar, Department of Computer Science & Engineering ,IIT Bombay . For more details on NPTEL visit http://nptel.iitm.ac.in
Views: 93299 nptelhrd
Template - Software Requirements Specification - Adaptive US
 
13:06
Adaptive US provides CBAP, CCBA, ECBA, CPRE, Agile BA and other business analysis training and consulting needs for Individual or Corporate either online or offline. Learn more on this training here: https://www.adaptiveus.com This is a comprehensive software Requirements Specification Template from Adaptive US Inc. The template describes product catalog, non-functional requirements and matrix model in detail. This template has been effectively used in multiple projects successfully. If you like the same, you may purchase the same by paying a very minimal amount on https://adaptiveus.com/product/template-systems-requirements/ For more updates on courses & tips follow us on: Facebook: https://www.facebook.com/Adaptiveus Twitter: https://twitter.com/Adaptiveus LinkedIn: https://www.linkedin.com/company/adaptive-processes/ Google+: https://plus.google.com/+Adaptiveprocesses Copyright Statement: All rights reserved ‘Adaptive US Inc. This content is available for mass viewing only through this platform or through any other platform as presented by Adaptive US from time to time. Any unauthorized download of this content for any personal or commercial use is restricted. Unauthorized use of the content or any part of the same for mass viewing or broadcast or use in other productions without written permission of the producer is illegal and may violate copyright laws.
Introduction to Program Specification
 
25:18
This lecture provides a basic introduction to the idea of program specification. That is, specifying using either informal or formal language to state exactly what the program should do.
Views: 929 Whiley
Product Requirements Blueprint Video for Confluence Team Collaboration Software
 
01:36
Collaboratively create, discuss, and organize product requirements documents in one place with Confluence, team collaboration software, from Atlassian. Learn more at: http://www.atlassian.com/software/confluence/whats-new/confluence-51
Views: 58865 Atlassian
Product Specifications
 
02:00
Views: 37 Bojun Lai
What Is A Use Case
 
03:48
This KnowledgeKnugget™ (KK) teaches you how to create a simple Use Case. Watch the full-length video for FREE at http://businessanalysisexperts.com/product/what-is-a-use-case/. For a more in-depth treatment, see our online or traditional classroom course “Writing and Managing LEAN Use Cases – Simply Put!”. View Description and Outline at https://businessanalysisexperts.com/product/how-to-write-document-manage-use-cases/ DESCRIPTION: Defining Interaction Between People and Technology as Functional Requirements for IT Applications. Use cases are a fundamental and phenomenal tool for defining the requirements of an IT solutions. They show how people will interact with a proposed IT solution – and how the application will interact with other applications. This KnowledgeKnugget™ answers questions like: 1. What is the purpose of a Use Case? 2. What does a Use Case Look Like? 3. How can I get started Creating a Use Case?
Views: 165347 BA-EXPERTS
Ramsey RESET test for functional misspecification
 
07:25
This video explains how the Ramsey RESET test for functional misspecification works, and how it is carried out in practice. Check out https://ben-lambert.com/econometrics-course-problem-sets-and-data/ for course materials, and information regarding updates on each of the courses. Quite excitingly (for me at least), I am about to publish a whole series of new videos on Bayesian statistics on youtube. See here for information: https://ben-lambert.com/bayesian/ Accompanying this series, there will be a book: https://www.amazon.co.uk/gp/product/1473916364/ref=pe_3140701_247401851_em_1p_0_ti
Views: 43285 Ben Lambert
Product Concept Design | Adding Requirement Specifications to a Concept
 
01:54
This video tutorial applies to Rel 9 through Rel 12. It shows the process of adding requirements specifications to a concept in Oracle Fusion PLM.
Design Specification.mp4
 
02:50
How to write justified specification points following research
Views: 3052 THSFoodTechnology
Product requirements document
 
02:01
A Product Requirements Document is a document containing all the requirements to a certain product. It is written to allow people to understand what a product should do. A PRD should, however, generally avoid anticipating or defining how the product will do it in order to later allow interface designers and engineers to use their expertise to provide the optimal solution to the requirements. PRDs are most frequently written for software products, but can be used for any type of product and also for services. Typically, a PRD is created from a user's point-of-view by a user/client or a company's marketing department). The requirements are then [Requirements analysis|analysed]] by a maker/supplier from a more technical point of view, broken down and detailed in a Functional Specification. This video is targeted to blind users. Attribution: Article text available under CC-BY-SA Creative Commons image source in video
Views: 1157 Audiopedia
Product Requirment Document
 
02:17
Product Requirement Document - CS 470
Views: 26 Matthew Perera
T1 Product Specifications
 
03:21
Specifications for the T1 handheld biometric enrollment device.
Views: 446 Talon ID
Product spec feedback
 
02:37
Need to gather some feedback on a document you've been working on? Here's how to do so with Polly in Slack.
Views: 73 Polly
Software Requirements Analysis and Specification
 
24:15
Requirements analysis, also called requirements engineering, is the process of determining user expectations for a new or modified product. These features, called requirements, must be quantifiable, relevant and detailed. In software engineering, such requirements are often called functional specifications. In this video tutorial, we give an overview of the process. This is a lecture by a Professor in IIT Delhi.
Views: 14242 Arpan Kar
iNetSec Smart Finder - Product Specifications
 
02:24
Technical overview
Views: 224 iNetSec
functional & non functional Requirements
 
02:31
Mohd Ismail-- Created using PowToon -- Free sign up at http://www.powtoon.com/youtube/ -- Create animated videos and animated presentations for free. PowToon is a free tool that allows you to develop cool animated clips and animated presentations for your website, office meeting, sales pitch, nonprofit fundraiser, product launch, video resume, or anything else you could use an animated explainer video. PowToon's animation templates help you create animated presentations and animated explainer videos from scratch. Anyone can produce awesome animations quickly with PowToon, without the cost or hassle other professional animation services require.
Views: 23462 mohd ismail
Approach to Software Design and Requirements Elaboration at EDISON
 
03:02
This video demonstrates our typical software design cycle. EDISON specialists have carved out a reputation as a successful team that you can rely on to: - Design software product architecture - Develop technical solutions - Elaborate requirements specification - Design organisational charts and conduct business-process modeling - Elaborate project documentation - Correctly schedule work and deadlines - Conduct risk management in software development - Handle the management of permanent projects - Carry out project recovery
SpecWizard - Automated Spec Writing
 
01:31
Instead of manually editing a 30 page manufacturer's spec, let http://www.arcat.com SpecWizard do it for you in 2 minutes. Select a few building product attirbutes and then generate a Word Doc you can use in your current project. You can also add it to your master for future use.
FUNCTIONAL AND NON FUNCTIONAL REQUIREMENTS by Syak
 
02:11
-- Created using PowToon -- Free sign up at http://www.powtoon.com/youtube/ -- Create animated videos and animated presentations for free. PowToon is a free tool that allows you to develop cool animated clips and animated presentations for your website, office meeting, sales pitch, nonprofit fundraiser, product launch, video resume, or anything else you could use an animated explainer video. PowToon's animation templates help you create animated presentations and animated explainer videos from scratch. Anyone can produce awesome animations quickly with PowToon, without the cost or hassle other professional animation services require.
Views: 1828 syakir shukri
Specification Demo
 
04:53
See specification creation in the new SAP WebUI
Views: 625 P K
How to draw [Random product] design in 4 steps | Industrial Design Sketching
 
15:17
++DOWNLOAD THE FREE SKETCHING GUIDES FOR BEGINNER: http://bit.ly/thedesignerstarterkityt ++Subscribe to the channel and get even more sketching tutorials at the blog http://www.thedesignsketchbook.com ++Facebook: https://www.facebook.com/TheDesignSKetchbook Awesome music from http://www.bensound.com Today we’ll look at a 4 steps tutorial that will help you better draw in 3D. It’s a perfect training for whom face the Malediction of the Blank page, where you may face these challenges: ◾Can’t visualize any shape in 3d on a 2D paper ◾Or just no inspiration ◾So you feel paralysed. Note: I recommend you to watch the video about the Contour lines first – if you don’t know how to draw them. http://thedesignsketchbook.com/tip-10... The idea here is to create [Random products] without caring much about the real functions of the prodcut. However you will combine hardware details to give it a look of a product. This exercise allow you to train without complexing about the feasibility, and focus on researching new shapes. Observe hardware that surround you, identify the details and “Drag & Drop” these elements to your sketches: ◾Industrial: Screw, joints, cables, grooves… ◾Functional: Power cords, button, tab, icons… ◾Commercial: Logo, barcode, product specification, illustration… Random product sketches - Step by StepThe 4 steps of the [Random product] Step 1 Draw random shapes. Fill your paper of few random shapes. Step 2 Draw the contour lines Even if these shapes are flat, play with the contour lines to give them a 3D volume appearance. Try to represent it with the minimum of lines. Step 3 Draw more contour lines To give more definition to your shapes, add more contour lines. Step 4 Add details You don’t care much about the “real” functions, you just try to assemble different details together to make your shape looks like a product. Details will bring life to your shape. Assignment of the day: Take few objects such as phone, mp3 players, mouse, camera, kitchenware… observe them and practice the “Random product” challenge. If you can do that, the day you need to create a product from a brief, your might visualise better some shapes without putting your pen on paper yet. There will be side benefits to this training: ◾You will improve your quality of lines ◾Improve your vision in 3D ◾Get more familiar to the Happy accident (create new shapes randomly) ◾Put in practice your memory of forms ◾And let your ideas flow faster. Have fun ! And let me know how it goes. :)

Cargo specialist metal gear solid 5 the phantom
Fluoxetine 20 mg dosierung algifor
Dapoxetine 30 mg in bangladesh nano
Tinidazole 500 mg indicaciones y
Inderal 40 mg prezzo handbags