jonathan Babcock's Library tagged requirements →  View Popular

To identify and document the interfaces to other systems and external entities within the project scope. These types of interfaces are classed as subsystem interfaces.

it.toolbox.com/...al-interface-requirements-6352 - Preview

data modeling requirements

Most interesting aspect of this is the comments. Lots of dialog questioning how well agile can work in less than ideal circumstances......

The Agile approach to managing software projects has been getting a lot of play recently. Why are people talking about it so much? Is this just the latest "new thing"? Or is there some real value to it?

"Agile," as a set of software development methods, was defined seven years ago, so the "flash in the pan" would have burned itself out long ago. The fact is that more and more organizations (from small shops to large corporations) are finding real value in Agility.

www.batimes.com/...108 - Preview

methodology agile requirements

Examples of inconsistencies, redundancies, and misuses of plain English language. Could serve as a good example for why plain language is imprecise.

www.cut-the-knot.org/...plain.shtml - Preview

language requirements communication

Poor communication about user requirements can doom a software development project. But there are tools to make the discussion more organized and successful.

www.computerworld.com/...article.do - Preview

requirements management tools

Two major reasons why "requirements suck."

www.scottberkun.com/...why-requirements-stink - Preview

requirements businessanalyst communication

The close of one year tends to make one reflect on the past and ponder the future. Here we ponder some trends in the Project Management and Business Analysis fields for 2009. We invite you to read the trends we offer and ponder for yourself our advice about what project professionals can do about them.

www.projectmanagerspotlight.com/...nagement-and-business-analysis - Preview

projectmanagement businessanalyst requirements

The approach is, of course, Agile, but adding the concept of an Increment or Micro-Increment on top of an Iteration. Increments should be measured in days, yet still deliver some demo-able or executable software to stakeholders. Micro-Increments are important as they drive projects to meet short term goals that are focused on software delivery, even if it's a simple as a dumb HTML UI mock-up, this adds infinitely more value that lines of requirements text or use cases.

380z.blogspot.com/...quirements-collaborate-on.html - Preview

requirements agile prototyping

The Goddard Space Flight Center's (GSFC) Software Assurance Technology Center (SATC) has developed an early life cycle tool for assessing requirements that are specified in natural language. This paper describes the development and experimental use of the Automated Requirements Measurement (ARM) tool. The ARM tool searches the requirements document for terms the SATC has identified as quality indicators. Reports produced by the tool are used to identify specification statements and structural areas of the requirements document that need to be improved.

satc.gsfc.nasa.gov/...pnq.html - Preview

requirements specification measurement quality tools

The Automated Requirement Measurement (ARM) Tool was developed by the Software Assurance Technology Center (SATC) at the NASA Goddard Space Flight Center as an early life cycle tool for assessing requirements that are specified in natural language. The objective of the ARM tool is to provide measures that can be used by project managers to assess the quality of a requirements specification document. The tool is not intended to evaluate the correctness of the specified requirements. It is an aid to "writing the requirements right", not "writing the right requirements".

satc.gsfc.nasa.gov/arm - Preview

requirements quality tools

So if we're gathering requirements, we assume that they must be out there, ready to be assembled like a roll of coins. Our problem is finding and selecting the right ones. So if the users don't tell us what they really want, we should grab them by the ankles, hold them upside down, and shake them until those pesky requirements fall out on the floor. The only logical conclusion is that if we don't get good requirements, we haven't shaken enough.

www.builderau.com.au/...0,339028292,339293632,00.htm - Preview

requirements elicitation

How do you get requirements right? Do you have to be clairvoyant to do requirements engineering?\n\nAt JAOO Aarhus 2008 Chris Rupp talked about exactly that and why it is so hard to get requirements right. She talked about different approaches to reading the customers mind, how you can match the techniques to your project based on the biggest threat in the project and how to ask the right questions to identify defects in a delivered requirements document.

blog.jaoo.dk/...nding-requirements-engineering - Preview

requirements elicitation analysis

According to new research, success in 68% of technology projects is "improbable." Poor requirements analysis causes many of these failures, meaning projects are doomed right from the start.

blogs.zdnet.com/projectfailures - Preview

businessanalyst requirements

"If we don't know our requirements, we can't have quality."\n\n"Recent surveys have found that the most frequent causes of software project failure have to do with requirements problems - requirements that define the wrong system, that are too ambiguous to support detailed implementation, or that change frequently and wreak havoc on the system design."

geekswithblogs.net/...for-requirements-analysts.aspx - Preview

requirements businessanalyst

University of Toronto lecure on requirements prioritization.

www.cs.toronto.edu/...20-prioritizing2-up.pdf - Preview

requirements prioritization

Looking back on one of the first game projects I worked on, I realize now, more than ever, how important good requirements are, how important good communication and best practices are in designing and developing a software system.

This article summarizes the impact of not having good requirements in a game development environment.

bradleyrblankenship.blogspot.com/...nts-maintanence-and-games.html - Preview

requirements

Nice, comprehensive list of business analysis and software requirements articles.

rationalizedthoughts.blogspot.com/...dex-for-business-analysis.html - Preview

businessanalyst requirements

Pierson Requirements Group’s customers have found that they are able to capture 93 – 95% of the business requirements functionality by using a collaborative requirements method and by creating and validating paper prototypes with the business community.

blog.piersonrequirementsgroup.com/...orative-requirements-gathering - Preview

prototyping requirements elicitation analysis

Given that something has already happened (e.g., user logged in) [context]
When the user does something (e.g., clicks on a button) [event]
Then this is what should happen [outcome]

Very straightforward. Very understandable. And once written, the client must review and sign-off on the scenarios before we begin to code.

The benefit of this process is that we’re not asking the client to do the impossible (write the nitty gritty details); we’ll take the first pass at bringing the 60,000 foot idea down to the nitty gritty. But, we are asking that the client read the scenarios and approve them as the definition for the feature ... or get back to us with improvements/additions and then approve the scenarios. Once approved, though, the scope of the feature is now defined and understood by both the business stakeholder and the development team.

www.pathf.com/...definition-of-a-feature - Preview

requirements functional features

Wireframes are a sketch of the business and user requirements. Since they are a drawing, they allow us to demonstrate how these requirements, nicely bulleted in a list format, are translated to a visual medium. In addition to showing that the requirements are met, wireframes can generate discussions uncovering what may have been overlooked. As the project progresses, we use them to begin explorations on how the user will interact with the screens and which data is affected.

www.pathf.com/...wireframes_much - Preview

requirements visualization prototyping

annotated pictures are far more specific & engaging than trying to describe with only text things that can be easily shown. If that adds pages to the document, it is a small price if it gets read and understood.\n\nAnnotated pictures are far more specific & engaging than trying to describe with only text things that can be easily shown. If that adds pages to the document, it is a small price if it gets read and understood.

www.pathf.com/...requirements_vi - Preview

visualization prototyping requirements