This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
team_report [2015/09/27 14:29] – scmfcl | team_report [2022/10/06 12:02] (current) – removed scmfcl | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Team Report ====== | ||
- | |||
- | You must submit a team report on the requirements specification, | ||
- | |||
- | The team report is marked by your supervisor and moderator independently. Before you submit the final version you should discuss the report with your supervisor to make sure both of you agree on what your project entails. The team report should be submitted via learning central as a single PDF document by a nominated member of your team. You will get oral feedback during the supervisor team meeting in the following week, and further formal written feedback by about three weeks after submission. | ||
- | |||
- | Finally, note that this is about the requirements and architecture decided by that stage of the project. You can, and most likely should, adjust these as you progress. Note, however, that with the report you are prescribing what you intend to deliver at the various stages and how it will integrate with the other team member' | ||
- | |||
- | ===== Structure and Contents ===== | ||
- | |||
- | Your team report should be at most 5,000 words per team member, excluding any figures, tables and appendices. | ||
- | |||
- | The report must address a full set of requirements with associated testable acceptance criteria, benefit and risk assessment with relevant quality factors, and a discussion of legal, social ethical and professional issues. It must further contain a description of the software development process the team wishes to adopt. In particular it should state clearly the deliverables each member of the team is working on. | ||
- | |||
- | There should be a list of more detailed aims and objectives for the project, in sufficient detail to show what each member will be working on and also how all the individual contributions will work together in the end. These are statements of what you set out to achieve with your project. Try to be as specific as possible at this stage, but avoid getting into too many details that may change later. It's only the main results and components of your project you should list. | ||
- | |||
- | You are free to decide on the format and structure of the work plan, as suitable for your project. The report should, however, contain the following information: | ||
- | |||
- | ==== Project Title ==== | ||
- | |||
- | The title of the team report document should be "Team Report" | ||
- | |||
- | ==== Project Description and Initiation ==== | ||
- | |||
- | Provide a brief description of your project outlining the problem you are trying to solve, its context, and overall aims. You can adapt the proposal used to select your project, but should extend it according to your findings. Following the general overview, discuss the scope of the project and specify the vision and key objectives for the project. You also have to select and justify the project management approach. Moreover, provide a risk assessment for the most significant risks and explain how these will be mitigated. This should also include managing the risks of associated legal, social ethical and professional issues. Discuss how communications will be managed within the team and with other stakeholders. | ||
- | |||
- | ==== Requirements Specification ==== | ||
- | |||
- | Select and justify the approach to analysing the problem situation, include associated deliverables in the appendices (e.g. transcripts of any interviews, survey results and questionnaires, | ||
- | |||
- | ==== High level software architecture ==== | ||
- | |||
- | Design a model of the high level software architecture to show the main components, services and dependencies. It is important this this is sufficiently detailed to enable every team member to work on their part of the system. It should, however, avoid prescribing too many details that may unnecessarily limit the individual project work. | ||
- | |||
- | ==== Work Plan ==== | ||
- | |||
- | The last section of the team report should consist of a high-level work plan for the remainder of the project with separate detailed plans for each team member stating what each member is working on when. This plan should be presented in a format that is suitable for the selected project management / software development approach. It should state clearly the deliverables each member of the team is working on. | ||
- | In particular ensure it include clear milestones of what you expect to achieve by which date and also show how you intent to achieve these milestones and show the dependencies between the various tasks. Link the deliverables to your time plan, such that you actually plan to deliver them when they are due. | ||
- | |||
- | Your time plan should further have at least two scheduled review meetings with your supervisor. You should typically see your supervisor once a week for a shorter time or once every two weeks for a longer time. The details of these arrangements are for you to agree with your supervisor. However, in your time plan you should mark special meetings with your supervisor where you are reviewing your progress since the last such meeting (or from the beginning) and adjust your plan for the project based on the outcome of this meeting. These review meetings are mandatory and are considered as part of the mark of the reports (see marking criteria there). | ||
- | |||
- | You are free to choose the work plan format that you think is best suited for your project and working style. This //may// be a [[wp> | ||
- | |||
- | ===== Marking Criteria ===== | ||
- | |||
- | Your supervisor and moderator will mark your plan according to the following criteria: | ||
- | * Project description with aims and objectives are clear, sufficiently detailed and provide a suitable challenge for each member of the team. | ||
- | * A suitable, well-justified project management and software development process has been selected with a discussion of associates risks and how these will be mitigated. | ||
- | * Legal, social, ethical and professional issues: Clear understanding and broader appreciation of how legal, ethical and social issues are addressed. | ||
- | * Team working: Quality and extent of contributions to group tasks to ensure fair distribution of workload and opportunity for originality for each team member. The ability to interact effectively with others through the use of excellent communication, | ||
- | * System requirements: | ||
- | * Acceptance criteria: Testable acceptance criteria are associated with both the functional and non-functional requirements. Benefit and risk assessment and relevant quality factors. | ||
- | * Good, high-level, expandable and flexible software architecture in sufficient detail to progress with the individual projects without over-constraining them by unnecessary detail. | ||
- | * Integration: | ||
- | * Work plan is feasible, sufficiently specific to the project, and has a clear timeline and milestones; deliverables are suitable and clearly specified for each member of the team; approximate dates for at least two review meetings per student are given; the amount of work is suitable for the credits and level of the module. | ||
- | * The report is well written and clearly structured. It shows clarity of expression without going into unnecessary detail. | ||
- | |||
- | All criteria carry equal weight for the mark of the team report and will be evaluated on the following indicative scale: | ||
- | * 70 - 100% - Excellent | ||
- | * 55 - 69% - Good | ||
- | * 40 - 54% - Satisfactory | ||
- | * 0 - 39% - Unsatisfactory | ||
- | * 0% indicates that the team has not adequately covered the topic or addressed the issue. | ||
- | |||
- | Supervisor and moderator will provide formal feedback about your report explaining any concerns they may have and their expectations regarding the aims and objectives and deliverables. You will further get informal feedback from your supervisor in the weekly meetings. Make sure you consider both when executing the remainder of the project. | ||
- | |||
- | Supervisor and moderator will mark the report independently and your overall mark for the report is the average of the two marks. | ||