HW23: Chapter 22


22.6. Fixed-price contracts, where the contractor bids a fixed price to complete a system development, may be used to move project risk from client to contractor. If anything goes wrong, the contractor has to pay. Suggest how the use of such contracts may increase the likelihood that product risks will arise.

Fixed-price contracts may increase the likelihood of product risk because the contractor will be responsible for any additional cost beyond the amount that they won the bid for and they might forgo some aspects of software engineering in order to deliver a product in budget on time. For example, the contractor might not put as many resources into testing their system if they believe that they will go over budget because, as we’ve read, software projects can easily go over budget, and testing makes up a large part of the budget. This would result in a product that is complete but not tested and therefore prone to more bugs than normal.  

Comments

Post a Comment

Popular posts from this blog

HW6: Chapter 4

1.       4.5.  Using the technique suggested here, where natural language descriptions are presented in a standard format, write plausible user requirements for the following functions: o     An unattended petrol (gas) pump system that includes a credit card reader. The customer swipes the card through the reader, then specifies the amount of fuel required. The fuel is delivered and the customer’s account debited. Function: Accept customer input for the amount of gas they want and charge them for it Description: The system will accept a customer’s credit card, allow the customer to specify the amount of gas they want, dispense the gas, and charge the customer for the gas Inputs: Customer credit card information, amount of gas that the customer specified Source: The card reader Outputs: The amount of gas that the customer specified Destination: The customer’s car’s gas tank. Action: The customer will swipe their card through ...
Read more

HW24: Chapter 23

Image
23.6.  Figure  23.14  shows the task durations for software project activities. Assume that a serious, unanticipated setback occurs, and instead of taking 10 days, task T5 takes 40 days. Draw up new bar charts showing how the project might be reorganized.
Read more

HW11: Chapter 6

Image
6.4.  Draw diagrams showing a conceptual view and a process view of the architectures of the following systems: ·          A ticket machine used by passengers at a railway station. Conceptual view: Process view: ·          A computer-controlled video conferencing system that allows video, audio, and computer data to be visible to several participants at the same time. Conceptual view: Process view: ·          A robot floor-cleaner that is intended to clean relatively clear spaces such as corridors. The cleaner must be able to sense walls and other obstructions. Conceptual view: Process view:
Read more