Not Signed-In
Which clippings match 'Requirements Gathering' keyword pg.1 of 3
19 JULY 2014

Using OneNote for gathering design project requirements

"Having a laptop open in a research interview puts a barrier between you and the person you're interviewing, and the typing can be quite distracting and intimidating for the interviewee. But typed notes are searchable, making for very useful reference when you're synthesizing your notes. OneNote is a nice compromise. With a Tablet in slate mode, we remove the physical barrier of the laptop, and as long as you have the pen in a 'Create Handwriting' mode, you can later go back and search your notes as if they were typed. (The handwriting recognition is pretty amazing.)

We sometimes have interviews by phone, and in these cases we often type notes. OneNote can go back and forth pretty seamlessly between handwriting and text, so it keeps all notes in one place. Also I find the quick–keys for adding tags to notes to be very useful when typing. You can tag questions you have, comments for follow–up, and ideas you generate, all with the quick stroke of a key.

For really important meetings, we can also use the audio recording features, which gives the ability to later go back and click on a piece of handwriting to hear what was being said at the time. Unfortunately you have to be using an external microphone for this, or all you hear is the tap–tap–tapping of the stylus hitting the slate surface instead of insightful interview conversation.

And I should note that research is not where OneNote shines the most. There are a few competing tools, like the LiveScribe Echo SmartPen and even pen and paper and that are giving it a run for its money. But as long as we're outfitting our designers with the Tablet, OneNote is a fine tool to use during research."

(Chris Noessel, 7 March 2013, Cooper Journal)

1

TAGS

audio recording • client interview • client liaisoncontent integration • content integration tool • design businessdesign objectivesdesign plandesign projectgeneral grounding document • handwriting • handwriting recognition • interaction design • Livescribe Echo Smartpen • managing design • Microsoft OneNote • multimedia toolnotebooknotesnotetakingpen and paperpersonas (UCD) • project reference • project requirements • requirements capture • requirements elicitationrequirements gatheringresearch interviewscope of practicesearchable content • slate mode • synthesising information • Tablet PCtext recognition • typed notes • user storiesvideo documentationworkflow toolworking practices

CONTRIBUTOR

Simon Perkins
26 JANUARY 2014

MoSCoW Analysis: a project requirements prioritisation technique

"MoSCoW analysis divides requirements into four categories: Must, Should, Could, and Won't. It is most applicable for software development or timeboxed delivery efforts, as it focuses on determining which requirements can be implemented given specified time or resource constraints. Category descriptions are as follows:

Must: Describes a requirement that must be satisfied in the final solution for the solution to be considered a success.

Should: Represents a high–priority item that should be included in the solution if it is possible. This is often a critical requirement but one which can be satisfied in other ways if strictly necessary.

Could: Describes a requirement which is considered desirable but not necessary. This will be included if time and resources permit.

Won't: Represents a requirement that stakeholders have agreed will not be implemented in a given release, but may be considered for the future."

(Kevin Brennan, 2009, p.165)

Kevin Brennan (2009). "A Guide to the Business Analysis Body of Knowledge". International Institute of Business Analysis. ISBN 978–0–9811292–1–1.

TAGS

building in measuresbusiness analysis • business requirements • clear project objectives • could • design requirements • importance • International Institute of Business Analysis • management methodmanagement methodologymanagement technique • MoSCoW analysis • MoSCoW method • MoSCoW prioritisation • must • organisational process • organisational technique • prioritisationprioritisation analysisprioritisation techniqueproject definitionproject deliverables • project delivery • project goalsproject managementproject management methodproject objectivesproject requirementsquantifiable definitionsrequirements gatheringrequirements prioritisation • should • software development methodtime management • wont

CONTRIBUTOR

Simon Perkins
29 OCTOBER 2013

Creating a Technical Specification

"A technical specification is a document that defines a set of requirements that a product or assembly must meet or exceed. A product or assembly that does not meet all of the specifically expressed requirements does not meet the specification, and often is referred to as being out of specification or 'out of spec.' Specifications are used when a contract for technical products or services is issued. The technical specification defines the requirements to fulfill the contract."

(WikiHow)

1
2

TAGS

abbreviations • appropriately complex representation • business document • clarity of thought • closed specification • contractual requirements • description of realitydesign projects • detailed specification • direct sentences • explicit definitionsexplicit meaningexplicit objectives • general requirements • industry terms • jargon • open specification • operational criteriaoperational definitions • out of spec • out of specification • performance requirements • precision • product or assembly • product requirements • professional communication practices • project specification • quantification of variablesquantified measurement • required performances • requirements gatheringrequirements process • set of requirements • software engineeringspecification • technical product • technical requirements • technical specification • TLA

CONTRIBUTOR

Simon Perkins
22 OCTOBER 2013

Project Management and Business Analysis Guides

"The Project Service Centre (PSC) role within CSU is to establish sound Project Management (PM) principles throughout the organisation. This will provide a means of clearly identifying the true needs of the University and help facilitate those desired outcomes.

To achieve these objectives, the PSC must provide and enhance the methodology for project management and business analysis, including guides and templates. This particular section concentrates on a set of guides which recommends how different processes can be undertaken."

(Charles Sturt University)

TAGS

enefits analysis • brainstormingbusiness analysisbusiness analystbusiness communicationbusiness logicbusiness management • business process modelling • Charles Sturt University • conducting meetings • cost estimatedecision makingdocument analysis • echnical specification • elicitation practices • elicitation process • engineering process • financial analysis • focus group • functional decomposition • gathering requirements • interface analysis • interviewingmodelling and prototyping • needs analysis • PowerPoint lectureproblem-solvingproject managementprototypingquestionnaire • requirements analysis • requirements elicitationrequirements engineeringrequirements gatheringrequirements process • requirements workshop • reverse engineeringrole playingshared practicessoftware engineering • stakeholder interviews • surveysystem requirementsuse casesuser activity data • user observation • workshops

CONTRIBUTOR

Simon Perkins
21 OCTOBER 2013

Design briefing for SMEs

"Design briefs are an essential part of the design process. In fact, they mark the beginning of the design process, helping designers understand the business problem they are required to solve and businesses clarify what they need from a design project."

1

TAGS

businessbusiness analystbusiness consultant • business focused briefs • business problem • clear project objectivesdesign brief • design briefing • Design Council (UK)design processdesign projectdesign teamdomain expertexplicit objectivesexplicitly definedlingoPeter Phillipsproblem-oriented thinkingproblem-solvingproject definitionproject designproject goalsproject objectivesrequirements gathering • small and medium enterprise • small and medium-sized business • small company • SMB • SMETLAwriting a design brief

CONTRIBUTOR

Simon Perkins
Sign-In

Sign-In to Folksonomy

Can't access your account?

New to Folksonomy?

Sign-Up or learn more.