Requirements

• 1.a customer has engaged your software development company to develop a new order­processing system. However, the time frames are very tight and inflexible for delivery of at least the basic part of the new system. Further, user requirements are sketchy and unclear. What are two system development strategies that might be advantageous to use in this engagement?

what is the potential downside to using the strategies described in the preceding question?

For the two strategies you select from question 1, you shall find (on the Internet) a success story for each strategy.

In the form of a well­written business letter to the customer, Mr. Jimmy Page, CIO of Zeppelin Industries Inc., you shall:

• Provide a problem statement for the order­processing system (OPS)

• Explain how the first strategy could help solve the problem and back up your statements using

• Explain how the second strategy could help solve the problem and back up your statements

• Provide an explanation for question 2

• Provide a conclusion that explains why the risks of using one of the strategies outweighs the

• Provide a one­paragraph scope statement for the OPS

• Provide ten well­written, high­level requirements for the OPS

• The length of your letter shall not exceed 500 words.

• Be careful writing the ten requirements; they must conform to the principles and syntax (writing

rules) of the Ivy Hooks document. Common mistakes:

• The statement is not a requirement (what the customer wants) it is an implementation detail (a

• Requirement is poorly written

• Requirement expresses more than one thought the example you found on the Internet.

using the example you found on the Internet. potential downside you covered in requirement 3d "how" something will be delivered - you must know "what" before you can define "how")