Search Results

Search found 88156 results on 3527 pages for 'code contracts'.

facebook twitter digg google delicious technorati stumbleupon myspace wordpress linkedin gmail igoogle windows live tumblr viadeo yahoo buzz yahoo mail yahoo bookmarks favorites email print

Page 556/3527 | < Previous Page | 552 553 554 555 556 557 558 559 560 561 562 563  | Next Page >

  • GDL Presents: Creative Sandbox | Google+ API

    GDL Presents: Creative Sandbox | Google+ API Tune in to hear about two cool, new campaigns that use the Google+ API from the core creative teams at Goodby Silverstein & Partners, Hook and RESN in conversation with a Google+ Developer Relations expert. They'll talk about how they pushed the possibilities of the Google+ API - and will inspire you to do the same. From: GoogleDevelopers Views: 0 0 ratings Time: 01:00:00 More in Science & Technology

    Read the article

  • Google I/O 2012 - Meet the Go Team

    Google I/O 2012 - Meet the Go Team Andrew Gerrand , Rob Pike The Go programming language is an open source project to make programmers more productive. Go is expressive, concise, clean, and efficient. It's a fast, statically typed, compiled language that feels like a dynamically typed, interpreted language. In this fireside chat, Have your Go questions answered by the gophers themselves. For all I/O 2012 sessions, go to developers.google.com From: GoogleDevelopers Views: 168 11 ratings Time: 01:00:29 More in Science & Technology

    Read the article

  • Functional vs. Non-Functional Requirements vs Design ideas in an SRS

    - by Nicholas Chow
    For a school project, I had to create a SRS for a "fictional" application. However they did not show us what it exactly entails, and were very vague with explanations. The SRS asked of us has to have at least 5 functional requirements, 5 non functional requirements and 1 constraint. Now I have tried my best to make one however I there are still some uncertainties left, I hope you experts can tell me whether or not I am thinking in the right direction. I will keep on updating this posts as I have questions regarding requirements that are vague to me, thank you all in advance for making SRS more clear for me FR1 Registration of Organizer FR1 describes the registration of an Organizer on CrowdFundum FR1.1 The system shall display a registration form on the website. FR1.2 The system shall require a Name, Username, Document number passport/ID card, Address, Zip code, City, Email address, Telephone number, Bank account, Captcha code on the registration form when a user registers. FR1.3 The system shall check whether the Name, Username, Document number passport/ID card, Address, Zip code, City, Email address, Telephone number, Bank account, Captcha code are filled out correctly within 1 seconds after a user submits the registration form. FR1.4 The system shall display an error message containing: “Registration could not be completed” to the subscriber within 1 seconds after the system check of the registration form was unsuccessful. FR1.5 The system shall send a verification email containing a verification link to the subscriber within 30 seconds after the system check of the registration form was successful. FR1.6 The system shall add the newly registered Organizer to the user base within 5 seconds after the verification link was accessed. Questions: FR1.1 Is this a functional requirement, or have I incorporated design idea in it by using "shall display on website". If so what would be a better way to write it? FR1.2 Is this better written in one requirement, or should I write each condition as a seperate requirement? FR1.3-1.5 Are these functional requirements or did I mix some non functional elements in it? How is it better phrased? FR1.3-1.6 Are these all correct functional requirements? As in free of ambiguity, complete, implementation free etc.

    Read the article

  • GDD-BR 2010 [0B] Maps API V3: New Features and How to Use them

    GDD-BR 2010 [0B] Maps API V3: New Features and How to Use them Speaker: Ossama Alami Track: Google APIs Time slot: B [11:15 - 12:00] Room: 0 Level: 201 The Javascript Maps API v3 is the future of the Google Maps API. Come learn why we built it, how to use it and about some exciting new features not available in V2. From: GoogleDevelopers Views: 2 0 ratings Time: 43:37 More in Science & Technology

    Read the article

  • Google I/O Sandbox Case Study: Doubletwist

    Google I/O Sandbox Case Study: Doubletwist We interviewed DoubleTwist at the Google I/O Sandbox on May 11, 2011. They explained to us the benefits of building their DoubleTap application on the Android Platform. DoubleTwist AirSync let's you wirelessly sync your music collection across all your devices. Their new app, DoubleTap, let's you share music between phones by simply tapping the phones together. For more information about developing on Android, visit: developer.android.com For more information on DoubleTwist, visit: www.doubletwist.com From: GoogleDevelopers Views: 13 0 ratings Time: 01:42 More in Science & Technology

    Read the article

facebook twitter digg google delicious technorati stumbleupon myspace wordpress linkedin gmail igoogle windows live tumblr viadeo yahoo buzz yahoo mail yahoo bookmarks favorites email print

< Previous Page | 552 553 554 555 556 557 558 559 560 561 562 563  | Next Page >