Case Study 1: Semester 2: Maintenance Costs of Simple Code
In semester two, the provost changed the values for the scores. In Fine Arts, the analysts changed the chart and the developer changed the code in two days. The normal testing and implementation took parts of four days. The clerks in the admissions office of Fine Arts wisely realized that they needed to process all of the older applications before the program changed and the new criteria took effect. In the School of Engineering, together the lead programmer and a clerk from admissions added new rows to the table and tested. In Engineering, the admissions clerks could process either semester with the same program. Fine Arts took six days this semester for a total of 18 calendar days and 22 man days. Engineering spent four hours for a total of 6 calendar days and 7 man days. See Semester1
Semester 3 and Groaning: Yes, We do Maintenance
Semester 3 and Groaning: Yes, We do Maintenance
For semester three, which was Fall13, the provost added two more levels and a new action called more. Fine Arts conducted a thorough examination for an entire day. The analyst changed her chart and the developers followed the new flowchart in just two days. Both schools added the more_routine; each took a day. A review and days of testing the many paths and corrections took four days Fine Arts. (There were 30 or so paths and the same unnoticed error) Installation took two days for FA and one for Engineering. Fine Arts took 12 days for a cumulative total of 30. Engineering had one spot to insert the routine; testing took one day. Overall Engineering took 5 days for a total of 11.
The analyst from Fine Arts was suspicious, so she watched as engineering conducted another test. The senior programmer had calculated that each of the five vertical routes required 12 cases and then one final exception case. So he had 61 cases; the analyst argue that her people had spent hours testing of case that they could think of. She also wanted to know why it was necessary that have a case that the chart did not cover.
Fine Arts 30 calendar days and 37 man days; Engineering 11 calendar and 11 man days.
Semester 4 went by in Similar Fashion.
The VP decided to give Fine Arts another developer, and he threatened to convert the programmers in Engineering to analysts and developers. Meanwhile, several applicants to Fine Arts complained that they had paid admission fees, but the University never responded. An inquiry by the assistant to the provost revealed the error; the same error that the junior programmer had flagged two years earlier.
The analyst from Fine Arts was suspicious, so she watched as engineering conducted another test. The senior programmer had calculated that each of the five vertical routes required 12 cases and then one final exception case. So he had 61 cases; the analyst argue that her people had spent hours testing of case that they could think of. She also wanted to know why it was necessary that have a case that the chart did not cover.
Fine Arts 30 calendar days and 37 man days; Engineering 11 calendar and 11 man days.
Semester 4 went by in Similar Fashion.
The VP decided to give Fine Arts another developer, and he threatened to convert the programmers in Engineering to analysts and developers. Meanwhile, several applicants to Fine Arts complained that they had paid admission fees, but the University never responded. An inquiry by the assistant to the provost revealed the error; the same error that the junior programmer had flagged two years earlier.