Part 6 of Dan Tasker’s Requirements in Context series discusses detailed business needs for a user interface (UI) or report, and capturing those needs as detailed requirements in a spreadsheet-based template for user interface.
Part 4 of Dan Tasker’s Requirements in Context series provides guidelines for what a business analyst should and shouldn’t include in a high-level requirement (HLR). It begins by comparing a formal HLR ‘shall’ statement to a user story. What is similar about them is that...
Requirements elicitation is one of three main disciplines of Requirements Engineering, complemented by requirements modeling and requirements management. A key success factor for professional Requirements Engineering - and especially for requirements elicitation - are good soft skills. During...
Part 3 of Dan Tasker’s Requirements in Context series continues to look at high-level requirements, narrowing the context to that of a project charted to deliver an IT-bases solution. It discusses how scope statements that identify functional capabilities are a good source of HLRs.
The International Council on Systems Engineering (INCOSE) outlines a number of guidelines for writing better requirements, 44 to be exact. From avoiding universal quantifiers, superfluous infinitives, and open-ended clauses, to maintaining consistency throughout the document - the INCOSE...
Amid the spread of the novel coronavirus (COVID-19) around the world, the ways we work and the ways businesses conduct their day to day activities are rapidly changing. From grocery stores to hospitals, from schools to houses of workship - "new normal" routines are emerging and,...
Having established “Business Information Systems” as the context for his series of articles on requirements, Dan Tasker introduces a three-level generic functional model applicable to any organization. The highest level, considered to be “… a view from 10,000...
What do you do when you're tasked with modifying a larger existing platform or when there is no time for a top-down or buttom-up design approach? The answer may just be Middle-Out Design also known as Inside-Out Design.
Why Design Thinking? Because it's time we stop assuming what the customer wants, how the user might use your product, or that we know the best way to solve a given problem. While the concept of design thinking has been around for a while, the advent of the digital...
You may be an aspiring product manager or may have been in that role for many years but do you know that it takes to be a great product manager? Product management sounds glamorous. You get to steer a product in any direction you want like the captain of a seaworthy vessel, weathering...
Requirements.com is trusted by leaders and experienced professionals across the world. Start your subscription today, for free.
it's all about requirements
for business analysts, data analysts and more...
one byte at a time!