• CLEARLY PRINT YOUR NAME HERE:
• You have 3 hours to complete the exam (1:00-4:00)
• There are 9 questions on the exam, worth 12 marks each.
• Your best 8 answers will be used, for a total of 96 marks.
• Answer directly on the exam paper, using the backs of pages if extra space is required.
• The exam is open book and open notes, but no calculators, phones, or other electronic aids of any form may be used during the exam.
• Many of the questions are quite open-ended, the expectation is that students spend roughly 20 minutes per question.
• Be sure to check your exam to make sure all 9 questions are present.

Question	Mark
1. Software life cycles [12 marks]
2. Feasibility analysis [12 marks]
3. System rollout/changeover [12 marks]
4. Risk management [12 marks]
5. Project requirements [12 marks]
6. Process modeling [12 marks]
7. Data modeling [12 marks]
8. Quality (testing, standards, inspections) [12 marks]
9. Project tasks and scheduling [12 marks]
Exam Total [96 marks]

Question 1: Software life cycles [12]

Discuss the life cycle model you wish had been used for your team project this semester, and why that model would have been the best choice.

Question 1 cont.

Question 2: Feasibility analysis [12]

Suppose the scale of your team project were to be drastically increased:

• for EBK and WoC the product was to be deployed for all departments on campus,
• for IDG a fully randomized, many level, many puzzle-type product was to be playable on machines across campus.

Discuss the feasibility challenges that would be associated with this change - economic, technnical, and organizational.

Question 2 cont.

Question 3: System rollout/changeover [12]

Using your scaled-up product from question 2, discuss the major challenges in rolling out your product, and outline a plan you think would address these challenges.

Question 3 cont.

Question 4: Risk management [12]

The ISO recommendations for risk management are that it should:

• create value - resources expended to mitigate risk should be less than the consequences of inaction
• be an integral part of organizational processes
• be part of decision making process
• explicitly address uncertainty and assumptions
• be a systematic and structured process
• be based on the best available information
• be tailorable
• take human factors into account
• be transparent and inclusive
• be dynamic, interative and responsive to change
• be capable of continual improvement and enhancement
• be continually or periodically re-assessed

Discuss which two of these recommendations you feel your team's risk management addressed the best, and why, and which two were addressed the worst, and why.

Question 4 cont.

Question 5: Project requirements [12]

Suppose you decided a custom bug-tracking tool would be helpful in the ongoing development of your project.

Provide a brief description of your proposed tool, and outline an initial set of requirements for the tool.

Question 5 cont.

Question 6: Process modeling [12]

Sketch a preliminary process model for the bug tracking tool you outlined in question 5.

Question 6 cont.

Question 7: Data modeling [12]

Sketch a preliminary ERD for the bug tracking tool you covered in questions 5 and 6.

Question 7 cont.

Question 8: Quality (testing, standards, inspections) [12]

From your personal perpective with respect to your team's project, discuss the greatest challenge you faced in producing a high quality final product, and how you might have addressed that challenge if you had the project to do over.

Question 8 cont.

Question 9: Project tasks and scheduling [12]

Suppose the full version of your team's project (i.e. with all the originally planned and desired features) was to be completed over the summer.

Outline how many people you feel would be required to carry this out, the skills they would need to possess, and provide a preliminary schedule of the tasks that would need to be completed. Identify any dependencies between tasks and provide a rough estimate of the time you expect each task to take.