Quotes About Requirements

I am not looking for a life partner right now. But if I've to list out the requirements, I have a huge list. But the first requirement is he should be tall and should be taller than me; even I wear heels.

You don't drive the architecture, the requirements do. You do your best to serve their needs.

As you work in requirements meetings to design software, pretend that your customer is not your customer. It turns out that this is a very easy thing to do, because it is true. Your customer is not your customer. Your customer's customer is your customer. If your customer's customer wins, your customer wins. Which means you win.

Animals need food, water and shelter. We humans need all those things, but we need fire too.

The requirements of romantic love are difficult to satisfy in the back seat of a Dodge Dart.

Shippers and logistics service providers impose multiple requirements on their transportation carriers regardless of the product shipped. These include low and predictable price; short and consistent travel times; high departure and arrival frequency; high equipment availability; accurate and damage-free delivery; and ease of doing business with the carriers. No

monkeys must have psychological needs and desires that go beyond their material requirements, and if these are not fulfilled, they will suffer greatly.

While there is no doubt that certain specific skills and experiencesmay be very helpful in preparing a person for a particular job, we should be careful not to require these skills. We will not find the people most capable of making important decisions by instituting arbitrary or inflexible prerequisites. On the contrary, these requirements end up excluding some of the best possible people.

We continuously enhance our knowledge base be it latest in technology, market scenario or customer requirements.

I'm obviously not a guy who focuses on weight too much. But for certain jobs, you have to gain or lose weight.

When I purchased my home, it was very strict underwriting standards. I had to provide two pay stubs, two years' tax returns, three months of bank statements, all sorts of credit card information.

soon enough, the day would come when new recruits claimed the Army no longer examined eyes, just counted them. A conscript had to stand at least five feet tall and weigh 105 pounds; possess twelve or more of his natural thirty-two teeth; and be free of flat feet, venereal disease, and hernias. More than forty of every hundred men were rejected, a grim testament to the toll taken on the nation's health by the Great Depression.

If a change to the requirements breaks your architecture, then your architecture sucks.

Which kinds of decisions are premature? Decisions that have nothing to do with the business requirements—the use cases—of the system.

Why does good code rot so quickly into bad code? We have lots of explanations for it. We complain that the requirements changed in ways that thwart the original design. We bemoan the schedules that were too tight to do things right. We blather about stupid managers and intolerant customers and useless marketing types and telephone sanitizers. But the fault, dear Dilbert, is not in our stars, but in ourselves. We are unprofessional.

This is the world of the software development team. It's a world in which dates are frozen and requirements are continuously changing. And somehow in that context, the development team must drive the project to a good outcome.

Indeed, most of us realize that the requirements are the most volatile elements in the project.

Nothing has a more profound and long-term degrading effect upon a development project than bad code. Bad schedules can be redone, bad requirements can be redefined. Bad team dynamics can be repaired. But bad code rots and ferments, becoming an inexorable weight that drags the team down.

if simple extensions to the requirements force massive changes to the software, then the architects of that software system have engaged in a spectacular failure.

The first value of software is its behavior. Programmers are hired to make machines behave in a way that makes or saves money for the stakeholders. We do this by helping the stakeholders develop a functional specification, or requirements document. Then we write the code that causes the stakeholder's machines to satisfy those requirements.

When the stakeholders change their minds about a feature, that change should be simple and easy to make. The difficulty in making such a change should be proportional only to the scope of the change, and not to the shape of the change.

Remember that code is really the language in which we ultimately express the requirements. We may create languages that are closer to the requirements. We may create tools that help us parse and assemble those requirements into formal structures. But we will never eliminate necessary precision—so there will always be code.

one of the government's requirements is that anyone it lends money to must have a successful track record at managing multifamily apartment houses.

You do, Bob. You have the requirements for it. A certain simplicity is necessary for love. You have it. Keep it. It is a gift of God. Never to be gotten again once it is lost." "Don't take it to heart too much, though, Baby," said Lenz with a grin. "It's no shame to be born stupid. Only to die stupid.