Welcome to our new home tynerblain.com/blog! If you use feedburner, nothing should have changed (except all the permalinks are now in this domain) – you will still subscribe to the RSS for our blog via feeds.feedburner.com/TynerBlain. It should be completely seemless for you. I, however, have been unpacking boxes all […]
IEEE Austin Event: Seilevel presents on requirements
Jerry Aubin and Joe Shideler of Seilevel will be giving their presentation, Beyond the System Shall – A Journey from Good to Great Requirements. Although this meeting is sponsored by the Austin chapter of IEEE, it is open to the public. [Update: The meeting is from 6:30-9:00pm on Wednesday 15 […]
Foundation Series: Software Process (Waterfall Process versus Incremental Process)
A software process is the set of activities required to create software. This process can be defined with very precise steps, roles and responsibilities. The process can also be defined with a more fluid set activities in pursuit of concrete, high level objectives. Or software can be created without explicitly […]
Foundation Series: Introduction
I want to thank one of my readers who offered a fantastic suggestion. He didn’t have the needed background knowledge to read some posts. He’s exactly right. The Foundation series of posts will provide introductory posts on topics. What topics would you like to see on Tyner Blain? – – […]
Happy New Year!
Thank you to everyone who has been reading the blog here at Tyner Blain! And I’d like to send a double thanks to everyone who’s commented on a post, linked to the blog, or told a friend about it. It makes a difference and I appreciate it.
Readability and Requirements
Thanks to the download squad for pointing me at the Juicy Studio: Readability Test! You can go to Juicy Studio’s site, and calculate the reading level of any URL. You can also try the Readability Grader at Jellymetrics, for a modern take on it. Of the multiple analyses provided, the […]
CRUDdy use cases and Shakespeare
CRUD (Create, Retrieve, Update, Delete) is an acronym used to refer to a set of mundane, important, and indirect (if not implicit) requirements or use cases. To create a report on orders, you have to first create the orders and retrieve them. Further, the ability to update (edit) and delete […]
Why We Should Invest in Requirements Management
Need to convince someone in your management chain why they should invest in managing requirements? There are some great arguments…
Managing requirements conversations
In Documents vs. Conversations, on the Pyre blog, Greg Wilson does that thing that we so rarely do – he takes a step back, and thinks from an entirely different perspective about managing requirements. He proposes the idea of managing requirements as conversations, instead of as documents. Greg makes the […]