User Tools


cm3301

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
cm3301 [2015/09/27 13:30]
scmfcl
cm3301 [2018/05/15 14:02] (current)
scmfcl Guide link
Line 3: Line 3:
 This is the main page for information about the 40 credit two-semester software engineering project module [[http://​handbooks.data.cardiff.ac.uk/​module/​CM3301.html|CM3301]]. This is the main page for information about the 40 credit two-semester software engineering project module [[http://​handbooks.data.cardiff.ac.uk/​module/​CM3301.html|CM3301]].
  
-Below are some guides to help you preparing these deliverables and submitting the reports ​on PATS. These are still under development,​ so please discuss the specifics with your supervisor and the project coordinator Frank Langbein.+ * [[CM3301 Guide]]: The complete guide for CM3301 ​on a single page for printing/​saving as PDF.
  
 ===== Project Selection ===== ===== Project Selection =====
  
-At the beginning ​of the third year you will be given a list of group projects proposed by some members of staff. You will be asked to indicate your preferences for the projects based on the descriptions. You may also want to ask some members of staff proposing projects for more details or clarify anything ​that you are uncertain about. By the middle of week 1 you will have to submit your preferences and we will then assign you to a team, based on your preferences and past performance to achieve a good balance of skills for each team. Each team will have an assigned project with one supervisor who initially will be interacting with the team as a whole and later on have individual meetings with each member to discuss their part of the project. Each team will also have a moderator assigned to them.+At the start of the module ​you will be given a list of group projects proposed by some members of staff. You will be asked to indicate your preferences for the projects based on the descriptions. You may also want to ask the members of staff proposing projects for more details or clarify anything ​in the description. By the middle of week 1 you will have to submit your preferences and we will then assign you to a team, based on your preferences and past performance to achieve a good balance of skills for each team. Each team will have an assigned project with one supervisor who initially will be interacting with the team as a whole and later on have individual meetings with each member to discuss their part of the project. Each team will also have a moderator assigned to them.
  
-You will be notified via learning central announcements and e-mails on the precise ​arrangements and deadlines. The overall module arrangements and projects will be discussed with you in lectures ​as well.+You will be notified via learning central announcements and e-mails on the detailed ​arrangements and deadlines. The overall module arrangements and projects will also be discussed with you in the lectures.
  
 ===== Deliverables ===== ===== Deliverables =====
  
-This is an overview of the expected deliverables and related tasks you have to execute for your project. Details on these deliverables and tasks are available on the linked pages. You also find the required deliverables with their submission deadlines ​under your PATS project details.+This is an overview of the expected deliverables and related tasks you have to execute for your project. Details on these deliverables and tasks are available on the linked pages. You also find the required deliverables with their submission deadlines ​on learning central.
  
-  * [[Team Report]]: You must submit a team report ​on the requirements specificationlimitationshigh-level ​architecture and project plan in the first semester (by end of week 9 of the first semester, at most 5,000 words per team member, worth 15%). +  * [[Team Report]]: You must submit a team report ​covering ​the project initiation documentationthe requirementssoftware ​architecture and project plan in the first semester (by end of week 9 of the first semester, at most 5,000 words per team member, worth 15%). 
-  * [[Team Presentation]]:​ A team presentation on the completed project, including a demonstration of the system ​must be submitted ​in the second semester (in week 11 of the second semester, up to 1h including audience questions and discussions,​ worth 10%).+  * [[Team Presentation]]:​ A team presentation on the completed project, including a demonstration of the system ​is due in the second semester (in week 11 of the second semester, up to 1h including audience questions and discussions,​ worth 10%).
   * [[Individual Report]]: ​ An individual report on your work on the project must be submitted by the end of the second semester (by the end of week 12 of the second semester, at most 20,000 words, worth 75%).   * [[Individual Report]]: ​ An individual report on your work on the project must be submitted by the end of the second semester (by the end of week 12 of the second semester, at most 20,000 words, worth 75%).
   * [[Project Viva]]: A project viva will take place after the exams for every final year project to discuss your individual work.   * [[Project Viva]]: A project viva will take place after the exams for every final year project to discuss your individual work.
  
-Reports and presentation material will have to be submitted on learning central. For details see the instructions for the deliverables ​there. +Reports and presentation material will have to be submitted on learning central. For details see the instructions for the assignments ​there.
 ===== Guides ===== ===== Guides =====
  
-These guides are meant to help you produce good final year project reports. A good report is one that presents your project work concisely and effectively. It should contain various materials relevant to the work you have undertaken ​in respect of your project; it should be organised into a logical framework; and it should be supported by written material that follows well-established academic conventions in a consistent fashion.+These guides are meant to help you produce good final year project reports. They are generic and have to be adapted to your specific module and project requirements. A good report is one that presents your project work concisely and effectively. It should contain various materials relevant to the work you have undertaken ​for your project; it should be organised into a logical framework; and it should be supported by written material that follows well-established academic conventions in a consistent fashion.
  
-An important point to remember is that the report should describe your work. Large chunks of bookwork describing standard material are unnecessary. You should simply refer to such material where necessary - assume that your reader is a competent computer or information systems theorist or practitioner. The guidelines here are arranged roughly in the order that you will need them.+An important point to remember is that the report should describe your work. Large chunks of bookwork describing standard material are unnecessary. You should simply refer to such material where necessary - assume that your reader is a competent computer or information systems theorist or practitioner ​as suitable in the wider context of your project. The guidelines here are arranged roughly in the order that you will need them.
  
 Your project supervisor will guide you on what it is reasonable to expect a project in your chosen topic to deliver. However, all projects are required to justify all decisions made at every stage of research and the development of appropriate deliverables,​ including the choice of approach. Your project supervisor will guide you on what it is reasonable to expect a project in your chosen topic to deliver. However, all projects are required to justify all decisions made at every stage of research and the development of appropriate deliverables,​ including the choice of approach.
  
 +  * {{ :​ethicsintro.pdf |Introduction to Ethical Rules and Procedures}}
   * General guides for writing reports:   * General guides for writing reports:
     * [[Gathering Material]]     * [[Gathering Material]]
cm3301.1443357004.txt.gz · Last modified: 2015/09/27 13:30 by scmfcl