


Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
An examination paper for a software engineering module (comp9029) as part of a master of science in software development program at cork institute of technology. Instructions, duration, and requirements for the exam, as well as four questions covering various topics in software engineering, such as software process phases, functional requirements, software architectural styles, and software testing. Students are required to answer any four questions within 2 hours.
Typology: Exams
1 / 4
This page cannot be seen from the preview
Don't miss anything!



Autumn Examinations 2011/
Module Code: COMP
School: Science
Programme Title: Master of Science in Software Development – Award
Programme Code: KSDEV_9_Y
External Examiner(s): Dr Thomas Dowling Internal Examiner(s): Mr John O’Brien
Instructions: Answer any FOUR questions.
Duration: 2 Hours
Sitting: Autumn 2012
Requirements for this examination:
Note to Candidates: Please check the Programme Title and the Module Title to ensure that you have received the correct examination paper. If in doubt please contact an Invigilator.
Q1. (a) The adequate engineering of a software entity requires that a software development process be defined. Elaborate on the focus of each of the following generic phases of the software process: (i) Definition phase; (ii) Development phase; (iii)Support/maintenance phase. [6 Marks]
(b) Consider the following extract from the “ Manifesto for agile software development ”: “ We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools; Working software over comprehensive documentation; Customer collaboration over contract negotiation ; Responding to change over following a plan.” In your opinion, are there situations in which one/more of the above-listed four “values” could get a software team into trouble? Justify your answer. [6 Marks]
(c) Agile software development processes were developed in an effort to overcome perceived and actual weaknesses in conventional software development. Discuss. Support your presentation with suitable illustrative examples. [13 Marks]
Q2. (a) In principle, a functional requirements specification should be both complete and consistent. In practice, these objectives are not always achieved. Why is this so? [2 marks] (b) Consider the following statement: “The software requirements document, the official statement of what a system’s developers should implement, is very often a compromise document.” Discuss, briefly. [5 Marks]
(c) The goal of the requirements engineering process is to create and maintain a system requirements document. The process includes a number of high-level requirements engineering sub-processes, including: (i) Feasibility study; (ii) Requirements elicitation; (iii) Requirements validation. Elaborate on the importance of each, of the above-identified requirements engineering sub-processes, to the successful outcome of a software development project. [18 Marks]
Q5. (a) (i) What does the term “ jelled team” refer to? [2 Marks] (ii) In a team-based work environment, “ team toxicity” should be avoided. “ Continuous and repeated exposure to failure” is one factor offered by Jackman, 1998 , likely to foster a potentially toxic team environment. List four other factors which, according to Jackman , 1998 , are likely to lead to a toxic team environment, and therefore should be avoided. [4 Marks]
(b) Elaborate, briefly, on the following elements of John Reel’s, 1999, commonsense approach to software projects: (i) Start on the right foot; (ii) Maintain momentum; (iii)Track progress; (iv) Make smart decisions; (v) Conduct post-mortem analysis. [5 Marks]
(c) Elaborate on each of the following software configuration management, SCM, tasks: (i) Identification; (ii) Version control; (iii)Change control; (iv) Configuration auditing; (v) Reporting. [14 Marks]