Docstoc

ASE – the programming stage(1)

Document Sample
ASE – the programming stage(1) Powered By Docstoc
					Advanced Software Engineering – semester 1, 2007 Presentation 4 (10 marks): Implementation phase. Part A: Presentation guidelines:
A1.Goals: 1.To simulate real-life conditions of formal presentation (in English) of a software project to your clients, superiors, and colleagues. 2. To exercise an objective self-assessment of one’s own performance during a presentation. 3.To outline an initial plan for the implementation phase of the software system, the development of which you are researching and reviewing. 4.To prepare documentation (e.g. schedules and checklists of tasks) that need to be completed for a successful implementation stage of your software system under research. 5.To gain awareness of selected real-life problems that may eventuate during implementation phase of your software system under research. 6.To facilitate a better understanding of the idea of system-engineering based approach to SE (for details see Lecture Notes ASE-L5).

A2.Objective: By the end of this session students are to exercise their practical skills and experience in formal presentation of the documentation (e.g. schedules, checklists, tasks, problems, and solutions) to be completed during the implementation stage of their software systems under research, as well as to review potential sources of problems that may eventuate during this implementation and to propose possible solutions to these problems. A3.Scenario: Let us assume, that you are a project manager for the software system subjected to the presentation. Your team developed successfully the software that you are researching, and now you face a task of implementing this software. You need to come up with three groups of implementation documents, namely (a) with the implementation schedule (e.g. “timeline chart” that synchronises subsequent tasks listed in the order of their implementation; note that this chart is to contain all items that need be in the implementation schedule because of the nature of your project), (b) with the changeover plan which explains how the present (old) system is to be changed into a new (your just developed) system, and (c) with checklist of actions to be undertaken to ensure further clients for your team and for the newly developed system. Assumptions: for the completion of your implementation plan you are to take the following assumptions: - Assume that all people that you have in your disposal for the implementation phase, are present members of your team (i.e. if you are a single-person team, all people that you have is just yourself). -Assume that all time you have to implement your new system is the time defined by your study calendar (i.e. whenever you are to finish your studies you are also to finish all work on this project). Notice: should your documents be interesting and the reasonably readable, you can submit voluntarily these documents to be added to the samples of student presentations displayed on the web pages for this subject.
This Controlled Document was issued for ASE 1/2007, by Prof. Dr Jan Pajak Document Revision #: 1 On 28 November 2009 at 03:56 Presentation 4 guidelines and marking; page 1 of 4

A3.Your task: Develop a brief presentation (ideally aimed at 15 minutes of speaking), which shows and explains as follows: (A) Your “timeline chart” for the implementation of the new software system in facilities of already existing clients. This “timeline chart” must include at least all activities that lead to accomplishing the following goals: -Software installed on the premises of already existing clients, -Software test-run on the premises of already existing clients, -User documentation being delivered to already existing clients, -Staff members of the already existing clients are being trained in the use of the new system, -The new system is formally handed in and becomes owned by the already existing clients. -The rewards (payment, diploma, thesis, publication) for making the new system are delivered to your team. (B) Your list of at least 5 most important problems which you foresee that they probably appear in the implementation phase, together with origins (sources) of these problems and with ways you believe they ca be solved. (C) Your changeover plan. This plan should briefly explain: (a) the old, already existing system, (b) outline how this old system is to be replaced with the new one, or how the new system is to fit into the already existing system, (c) should provide a list of at least 3 potential problems with the changeover, and (d) should explain how you believe these problems can be solved. (D) A checklist of activities that your team must undertake in order to find and to secure further (new) clients for your team and for your system, and to make the system available to such new clients as well. (After your presentation is finished, you are welcome to voluntarily post the electronic version of all your documents at the address pajakjan@gmail.com – if you wish they be published on the ASE web page.)

A4.Self-assessment: You are to self-assess objectively your own presentation. Therefore, outlined below is a list of requirements which your presentation supposed to meet. Marks are allocated to all these requirements. To earn these marks you need to meet a given requirement in full. Means, you either get a full mark for a given requirement - when you address all aspects of it during your presentation, or you get zero marks from this requirement. (Zero mark is even in the case when you satisfied a given requirement partially – e.g. for item “Y5” you still get zero marks even if you clean the blackboard after yourself – only that you missed in cleaning a section of it, or if you get to your sit and only then start to remember that you supposed to clean the blackboard after yourself, so you rush to the blackboard and try to repair this error.) Part X. Content. The requirements imposed on the presentation of the content are as follows: #X1.Introduction: you are required to remind to the audience your project name and the team composition. Remember that whatever you talk about, there should be a visual illustration for it either on the screen or on the blackboard. E.g. when you remind names of yourself and your team, all these names should be displayed as well (i.e. not just repeated verbally). #X2.The implementation schedule and accompanying matters. #X3.The changeover plan and accompanying matters. #X4.The further clients and orders checklist.
This Controlled Document was issued for ASE 1/2007, by Prof. Dr Jan Pajak Document Revision #: 1 On 28 November 2009 at 03:56 Presentation 4 guidelines and marking; page 2 of 4

Part Y. Technique. Demonstrate following techniques and behaviours during your presentation: Y1.Speak always turned towards the audience (no speaking turned back to the audience – as it is considered very impolite). Y2.Speak loudly and clearly – the most distant person should hear you clearly. If you refer to a slide or a handout, then indicate clearly which exactly item you are explaining. Y3.Project the professional confidence and the knowledge of your subject area by your behaviour, body language, and by words. Y4.Always link the visual material supporting your presentation with whatever you are just explaining. Means, each time you are shifting to a next matter, indicate on your visual material the exact place where this matter is illustrated. Point using a mouse, a pen, or any other kind of pointer – never point just with bare fingers or hands. (Pointing with fingers or hands in many cultures is considered to be a primitive and an offensive behaviour.) However, distinguish pointing with fingers from body language and polite gestures - which NOT only are allowed, but also are encouraged as the vitalize the audience and convey vital messages of the presentation. Y5.Everything that you talk about should also be presented visually. Means whenever you try to explain something, the key points or keywords should be listed on the blackboard, or on the screen. If you intend to write something, do it precisely as you planned it in advance. Do not keep too long period of silence while writing, but rather explain your points in portions (means write something, turn to the audience and explain, then write a next part, etc.). Y6.After you finish your presentation, you need to ask for questions. Before leaving the podium you need to clear the board and/or the projector and computer, making it ready for use by a next presenter. Notice that characteristics of your English are NOT assessed nor commented. So you can speak in any manner you wish – as long as it is in English. In our presentations it is a responsibility of listeners to make an effort to understand you – e.g. by asking additional questions (but NOT so in the real life).

Part Z. Assessment: Now print the marking schedule attached, and take it to your presentation to make your assessment on it. Notice that there are punishment marks to be subtracted when your presentation does NOT meet certain criteria. One mark is to be subtracted for each of the following taking place: - your presentation lasted less than 10 minutes or longer than 18 minutes (ideal timing of the presentation is 15 minutes), - you were NOT ready for the presentation when asked to present, and there was NO advanced indication of the emerging problem. (Note that any team can be asked to present at random at any day and time of the presentation week, unless a problem is reported in advance). - your time management was very bad, e.g. you wasted a lot of time on non-important issues, while you run out of time to present important matters. - you strongly projected the lack of professional confidence and the low knowledge of the subject area in your behaviour, body language, or words. - you did NOT fill up and hand in the assessment schedule at the day of presentation. In order to make you marking easier, there are “mission statements” assigned to each item of the marking schedule. If a given mission statement is TRUE for your presentation, then you deserve to gain a given mark. If this mission statement turns out to be FALSE for your presentation, then you should NOT give yourself this mark. (Note: do NOT use fractions of marks. You either deserve a full mark allocation, or zero mark from a given criterion.)
This Controlled Document was issued for ASE 1/2007, by Prof. Dr Jan Pajak Document Revision #: 1 On 28 November 2009 at 03:56 Presentation 4 guidelines and marking; page 3 of 4

Marking schedule (ASE - presentation 4):
#A. Header: (For information only - no mark allocated). List of team members (write names clearly):………………………...……………………………….. Name of the team’s project: ……………………………………...…………………………………….. #X. Marks for the content of presentation (allocated 7 marks in total). Give these marks to your presentation only if you fully and completely covered what is stated below: X1. Introduction: earned ……………. (marks out of 0.5 mark): Team members are re-introduced properly, and the topic that they investigate is reminded. X2. Implementation schedule (allocated 3 marks): X2.1. The “timeline chart” of tasks: earned ……………. (marks out of 1 mark) The presentation illustrated and explained the timeline chart for all tasks of the entire implementation phase in facilities of the existing client(s). X2.2. A list of problems expected during the implementation phase:……(marks out of 1) The list of at least 5 problems expected during the implementation phase is displayed, and the source of each problem is explained. X2.3. Staff allocation to the subsequent tasks ……………. (marks out of 1 mark) Assuming that your present team is all the staff that you have, the presentation explained how you are going to complete all tasks of the implementation phase, and which duties you delegate to whom. In case you are a single-member team, explain how you intend to complete all tasks. X3. Changeover plan (allocated 2 marks): X3.1. The present system and a changeover plan: earned ………. (marks out of 1 mark) The presentation had a separate section for the changeover plan. It outlined the present system and explained how the present system is to be changed into a new system just developed. X3.2. List of potential problems and proposed solutions for them:…(marks out of 1 mark) A list of at least 3 potential problems of changeover was provided. The origin of each problem from this list is fully explained. For each problem a way of solving it is suggested. X4. Further clients and orders (earned …… out of 1.5 mark). The presentation included and briefly explained the checklist of actions to ensure further clients to the system being developed. #Y. Technique and style of presentation (allocated 3 marks). Y1. All speaking was done when turned towards the audience: earned ….…… (out of 0.5 mark) Y2. Speech was loud enough to hear it clearly in the last row: earned ……..… (out of 0.5 mark) Y3.Professional confidence was projected by body language and by words….. (out of 0.5 mark) Y4. The matter under presentation was always indicated on the screen: ………(out of 0.5 mark) Y5. Everything explained had also a visual representation: earned ….……..… (out of 0.5 mark) Y6. All traces of your presentation were removed at the end: earned ….…...… (out of 0.5 mark) Z. Punishment marks (if needed to be subtracted - notify how many) …..…………… (marks) Total marks (add #Xs to #Y and subtract punishment marks): …………..……..….….... (marks). Signatures of all team members: ………………………………......................................................; Date: …………………………
This Controlled Document was issued for ASE 1/2007, by Prof. Dr Jan Pajak Document Revision #: 1 On 28 November 2009 at 03:56 Presentation 4 guidelines and marking; page 4 of 4


				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:8
posted:11/28/2009
language:English
pages:4
Jun Wang Jun Wang Dr
About Some of Those documents come from internet for research purpose,if you have the copyrights of one of them,tell me by mail vixychina@gmail.com.Thank you!