80 likes | 104 Views
Project – Details of submission. Deadline: November 18 th , Format: PDF
E N D
Project – Details of submission • Deadline: November 18th , Format: PDF • Together with the project report you must submit a declaration of not cheating. The form can be found here: http://www.uio.no/english/studies/admin/examinations/cheating/declaration.pdf or here: http://www.uio.no/studier/admin/eksamen/fusk/egenerklering-bm.pdf • Submit • both report and form in Fronter, or • report via email to anastp@ifi.uio.no with cc to bentea@ifi.uio.no, and hand in declaration form on paper to Bente Anda either • in the lecture on November 11th , or • in post box at 4th floor at IFI by November 18th
Project – Report structure • A (realistic) software process improvement plan for a software development organization • Cover page (Title, Author(s), Date, Email, Course ID, ...) • Table of content • Content (details on the nextslides) • References
Project – Report content 1/3 • Improvementcontext • Briefdescriptionoforganization (real or imagined) • Software product(s) • Problem and possiblyhow it wasidentified • Baseline process (basedonHomework 1) • Currentprocess (textualdescription) • Current roles, activities, artefacts and tools • Graphicalprocessmodel • ImprovementGoal(s) • What? • Howmuch? • When?
Project – Report content 2/3 • Suggestedchanges, • The scope of the change, that is, the process or activity that will be changed • Typeofchange, i.e. • Introductionof new process, methods or techniques? • Change in process? • Organizational change (team organization, human factors..)? • Updated graphical process model • Plan • What? When? Responsible?
Project – Report content 3/3 • Measurements (based on Homework 2) • Who will collect/report data? • When (how often) will data be corrected? • How is data collected, for example using which tools ? • How is data quality and validity ensured, who is for example responsible? Also discuss possible challenges related to data collection and data validity. • Discussion • Rationale for changes • Risks
Project – Evaluation • Maximum number of marks: 16 • Content = 12 marks • Clarity/Conciseness = 3 marks • Formality (cover page, captions, referencing, etc.) = 1 mark • Section 2 should be based on much reuse from Homework 1, and Section 6 correspondingly on reuse from Homework 2, but you must • make sure that all comments that you previously got on your Homeworks are addressed in the report, and • make the necessary adjustments to fit the rest of the report. • Note that the marks on the report will be completely independent of previous marks on Homework 1 and 2. • Evaluation results will be ready one week before exam
Evaluation of individual vs. group submissions • In a group all members get the same number of marks • The same quality is expected regardless of whether you do the project individually or in a group, but length should be related to number of people • 15-20 pages from 1 person • 18-23 pages from 2 people • 20-25 pages from 3 people • The additional length is in particular expected in Sections 4 and 6, with more suggestions for changes/improvements and more discussion
Evaluation of real vs. imagined case • Basically the same expectations and evaluation, but • with a real case the description of the organization current problem(s) (Section 1) and a realistic plan (Section 5) should be emphasized, and • with an imagined case suggestions for changes (Section 4) and discussion (Section 7) should be based on curriculum and emphasized.