88 Articles match "Requirements"

237 Articles match "Requirements"

• The Best from DevelopMentor

  MORE

• Systems Thinking: Requirements?
  
  So how do you define requirement? The problem is that the notion of requirement comes in many forms. The definition seems to depend on what role you play in relationship to requirements definition – Customer, Business Analyst, Systems Analyst, Designer, Architect, [.]. Tags: Systems Development Requirements Systems was working with a large hospitality corporation when I was asked this question.
  Jim Schardt's Blog - Tuesday, January 6, 2009
  READ MORE
• Requirements and Black Boxes
  
  After dealing with requirements in all sorts of shapes and sizes over the years I find the “black box&# approach works well. For requirements, I think of any system as if it were a black box. Tags: Systems Development Black Box Requirements Systems Thinking can “see” or experience the outside of the box. can experience the contours of the box. can [.].
  Jim Schardt's Blog - Monday, January 12, 2009
  READ MORE
• More Black Box Requirements
  
  In my last post I talked about how requirements are really the stuff that goes in and out of your system, the black box. But what else constitutes requirements (stuff)? Tags: Software Development Systems Development Black Box Business Rules QOS Requirements The “stuff” are things like data, documents, objects, requests, events, and when “this stuff happens. Well systems often adhere to rules. W-2s for the previous [.].
  Jim Schardt's Blog - Tuesday, March 24, 2009
  READ MORE
• Avoiding Requirements Confusion with Black Boxes
  
  By clearly understanding the boundary of your system you can easily distinguish between requirement and design statements. Tags: Software Development Black Box Requirements Systems Thinking
  Jim Schardt's Blog - Monday, January 19, 2009
  READ MORE
• Requirements, requirements everywhere; no clue on what to do
  
  Twice this year I have visited companies which want to try a more Agile way of working but who have requirements coming of their ears. m talking hundreds of pages of requirements. Sometimes as big meat documents written by expensive consultants and bearing names like “Requirements Specification” or “Business Design.” Its hard to argue with such requirements documents, in part because its hard to read them and understand what they are about. One variation is a project I saw last year were the documents were not requirements documents but strategy documents.
  Allan Kelly's Blog - Friday, December 4, 2009
  READ MORE
• Managing requirements in Agile development
  
  That is one of two reasons why Agile methods tend to underplay requirements and “Product Ownership” - because you get a lot of benefits by ignoring them to start with. The other is that Agile methods largely originated with developers who generally tend to underplay the role of requirements. But architects are also tasked with looking at technology therefore any requirements they come up with are likely to be technology not market based. I make no apologies for blogging again about Product Management because it is important and because, on the whole.
  Allan Kelly's Blog - Sunday, November 2, 2008
  READ MORE
• Requirements: The next challenge for Agile
  
  Lets get one thing straight: I’m not saying requirements don’t matter. In which case, you can, and should, take liberties with the requirements process. Then, when delivery shapes up you should come back and fix the requirements issues. Because requirements is where the long term gain is. Anyone who thinks I don’t value requirements should look at all the postings on this blog about the importance of Product Managers. The requirements is also where the long term future of Agile is. Well oiled IT: this is where Agile takes you. But it leaves you there.
  Allan Kelly's Blog - Monday, February 23, 2009
  READ MORE