Package.json: an interactive guide. HOWTO prototype and iterate for fun and profit. In this 30+ minute video, Firefox creative lead Aza Raskin explains why you'd want to do iterative prototyping and how you do it in order to get from idea to execution. I think that the Internet's ability to support and sustain low-cost iteration is its signal virtue, but this virtue is often missed by bigger, older institutions that are accustomed to high failure costs (e.g., you print a million of the wrong book or make a million of hte wrong shirt, it's a big deal; you serve a million of the wrong page and change the design, it's business as usual). For those who do not want to sit through the 30-minutes romp and my rapid prototyping, here are the principals of prototyping that I explain fully in talk: 1. Your first try will be wrong. Budget and design for it. 2. Aim to finish a usable artifact in a day. How To Prototype And Influence People (via O'Reilly Radar) Tigris.org: Open Source Software Engineering.
How I know when the requirements process is complete. By Alvin Alexander. Last updated: Mar 22, 2014 Summary: How to know when a software requirements specification is complete by using Function Point Analysis techniques. I've written dozens -- maybe hundreds -- of software requirement specifications over the years, and at one point in my career I learned an important little secret about knowing when the process of gathering requirements for a software requirements specification was really complete. Here's my secret. How I know when the software requirements specification is really complete As a business analyst, I'm lucky to have trained myself in the techniques of Function Point Analysis (FPA).
Right away, FPA helped clarify the definition of a UML Use Case for me, and then later on, when I became really comfortable with FPA, I realized that it also helps me understand when a given software requirements specification is "feature complete". I know the requirements process is complete when I can accurately count the Function Points. Summary. Function point. A function point is a unit of measurement to express the amount of business functionality an information system (as a product) provides to a user. The cost (in dollars or hours) of a single unit is calculated from past projects.[1] As of 2013[update], there are several recognized standards and/or public specifications for sizing software based on Function Point 1.
ISO Standards COSMIC: ISO/IEC 19761:2011 Software engineering. 2. OMG, an open membership and not-for-profit computer industry standards consortium, has adopted the Automated Function Point (AFP) specification led by the Consortium for IT Software Quality. Introduction[edit] Function points were defined in 1979 in Measuring Application Development Productivity by Allan Albrecht at IBM.[3] The functional user requirements of the software are identified and each one is categorized into one of five types: outputs, inquiries, inputs, internal files, and external interfaces.
Benefits[edit] Criticism[edit] See also[edit] References[edit]