Philadelphia University Faculty of Information Technology Department of Software Engineering Second Semester, 2015/2016

Transcription

1 Philadelphia University Faculty f Infrmatin Technlgy Department f Sftware Engineering Secnd Semester, 2015/2016 Curse Syllabus Curse Title: Research Prject (1) Curse Level: 4 Lecture Time: 12:10-13:00 16:10-17:00 Curse cde: Curse prerequisite: Exceeding 90 credit hurs + Department Agreement Credit hurs: 1 hur Academic Staff Specifics Name Rank Office N. Office Hrs. Address Dr. Mhammad Taye Assistant Prfessr -S-T-T :00-12:00 12:00-13:00 mtaye@philadelphia.edu.j Curse Descriptin The prject curse cnsists f a tw curses n which the student wrks ver tw semesters that can be extended. There are three deliverables: demnstratin, discussin, and a written reprt. A student wrks under the supervisin f a member f staff, the curse lecturer. Mst f the prjects grups invlve three students wrking tgether n the same prject; apart frm these, all students d different prjects. The aims fr the prject wrk dne in the furth year are :t manage and execute a substantial prject in a limited time, t identify and learn whatever new skills are needed t cmplete the prject, t apply design and engineering skills in the accmplishment f a single task. In this cntext the skills mentined may be in the general area f design and engineering in its bradest sense, r may be very specifically related t particular tls. A student wrks under the supervisin f a member f staff, the Supervisr. Curse Objectives The aims fr the prject curse are: 1- T learn real prject definitin, analysis, design, implementatin, testing, writing, and presenting 2- T manage and execute a substantial prject in a limited time. 3- T identify and learn whatever new skills are needed t cmplete the prject. 4- T apply design and engineering skills in the accmplishment f a single task. Curse Cmpnents The lectures are n tpics f particular interest t students ding a prject in their final year: Overview f prjects and prject assessment, real prject definitin, analysis, design, implementatin, testing, writing, and presenting (with demnstratin), Career advice. Text bks - C. W. Dawsn, The Essence f Cmputing Prjects, A Student's Guide. ISBN X. Prentice Hall Department Research Prject Guide Teaching Methds Duratin: 16 weeks Lectures: 7 lectures (7 hurs), spread thrugh the 16 weeks.

2 Learning Outcmes On successful cmpletin f these mdules students will be able t: Knwledge and understanding Real prject leading prcess Address a mderate sized prblem and in s ding select and justify an apprpriate apprach, and fllw the apprach systematically. Recgnize alternatives, selecting and justifying the apprach taken at each pint in the prject and identify thse parts f the prject that are feasible within the time (etc.) cnstraints f the prject. Cgnitive skills (thinking and analysis). Plan, execute and cmplete a significant design and, as apprpriate, implementatin within the time budget available Demnstrate that students have acquired a degree f specializatin in a particular part f the subject area, including enhanced r new technical skills that build n thery. Demnstrate in the technical executin f the prject the required level f analysis, design, and technical skill. Recgnise ethical issues that may arise when cnducting research Cmmunicatin skills (persnal and academic). Give a demnstratin shwing practical cmpetence and demnstrating the results f the prject Dcument the prject in a final reprt. Cmmunicate t bth a technical audience in the written reprt and prject dem and t a mre general audience in the pster. Practical and subject specific skills (Transferable Skills). Use the prject Lecturers apprpriately as prject cnsultant r custmer. Prject Classificatins Students may develp prjects related t different Cmputing disciplines. They may add functinality t existing systems, r remve restrictins r generalize the way a system wrks, r autmate manual prcesses, r cmbine functinality frm different systems. Hw t Chse a Prject? The list f prjects fr each semester will be available at the beginning f the semester. This list will cntain the prjects title and names f Lecturers. The main selectin and allcatin f students t prjects was made at the beginning f the semester. It is pssible fr students t prpse their wn prjects, in which case, they shuld prepare a prpsal and give it t the Graduatin Prject Cmmittee (GPC). Usually each prject is suitable fr mre than ne student (nrmally 3 students). Therefre, grups f three students shuld be arranged by students themselves. Each grup f three students shuld make three chices f prjects n the selectin frm btained frm the GPC. Students are strngly encuraged t see the assciated members f staff fr prjects they are interested in, t find ut mre abut the prjects. OWN Prjects If a student has successfully negtiated a prject - utside the list f prjects given by the department - with the prject cmmittee, and pssibly a prspective lecturer, he/she still gives anther 2 chices, and cde chice number 1 as "OWN"; this is likely t be the student's first chice, but it des nt have t be. Prject Timetable Yu are expected t be in regular attendance wrking n yur prject. Yu must c-perate in maintaining regular cntact with yur lecturer. It is an attendance requirement that yu see yur lecturer every week during term time, and accrding t the Curse Time table. The frmal prject deliverables are a demnstratin with discussin, and a written reprt. The prject lifecycle shuld fllw a sensible methdlgy and include the varius stages identified in any Sftware Engineering curse, and presented in the prject curse lectures. Wrk n the prject itself, in particular use f equipment and cmputing facilities. The Lecturer will annunce a timetable fr all prject discussins, in parallel with the final written exam. The GPC frms a number f discussin cmmittees, where each cnsists f at least ne staff member (reviewer) and discusses ne prject dcument.

3 Prject Assessment The prject evaluatin is allcated as the fllwing: Prject Supervisr: 65% Prject Reviewer : 35% Demnstratin The demnstratin is an infrmal presentatin f the results f the prject t the prject lecturer. The students will say briefly, what the aims f the prject are, and will then demnstrate the results fr example by running the prgram r using the equipment cnstructed. The duratin is abut 20 minutes. Reprt The reprt is a frmal written reprt n the prject. This must be wrd prcessed. The reprt must fllw a set f standards, given belw, t facilitate its inclusin in the library and its usefulness fr subsequent readers. Besides these, student will find it useful t fllw the talk given n writing, which is given in the lecture. Cpies f previus graduatin prject reprts are available fr reference in the Department. Prject dcumentatin may be prepared n the PCs and printed n a laser printer. Students shuld hand in three sft cver cpies f the reprt. After the dcument evaluatin by the GPC, students shuld make all the crrectin that are suggested by the cmmittee within the specified perid f time under the supervisin f their lecturer, then they shuld handed in three blue clr hard cver cpies f the prject. The title f the prject, the University, Faculty, Department names, and students' names are all written in glden clr. Guidance n Demnstratins A demnstratin lasts abut 20 minutes. The grup f students shuld aim t spend n mre than 10 minutes summarizing what their prject is designed t achieve and shwing what it currently des achieve. The rest f the time is spent in answering questins. Nte: Students shuld nt attempt t demnstrate n the cmputer every last thing their prgram can d. A demnstratin f its basic peratin plus ne r tw highlights shuld suffice. The mark given fr the demnstratin is based n the quantity f the wrk attempted and the final state f achievement. Students shuld have their wrking dcuments t hand and apprpriate reference material, design wrkings, reasnably up-t-date listings, examples, tests, etc. They are nt giving a 20-minute seminar; at least half the time must be available fr questins. Obviusly, the kinds f things that are sensibly shwn in a demnstratin vary frm prject t prject. If students are in dubt as t what t shw, they shuld ask their lecturer. In general, students shuld be available and ready t start their demnstratins at least within ne week f their submissin f the prject. Reprt Standards 1. The reprt is a frmal written accunt f the prject, satisfying certain standards fr inclusin in a library. Students must hand in all relevant wrk n the prject by the end f the 14th week f the semester. In additin t the reprt, this includes a CD cntaining the surce and cde files f the prject. It is imprtant t meet this deadline. When students hand this t their lecturers it must be accmpanied by a signed versin f a frm supplied by the GPC. Lecturer guidance shuld anyway be sught! Intrductin: Reprting the system cncept f the prject, the verall aim f the prject, and the prblem statement. Dmain Analysis: Reprting the details and the results f the dmain analysis activity. Applicatin Analysis: Reprting the details and the results f the requirement analysis activity System Design: Reprting the details and the results f the sftware architecture cnstructin activity. Detailed Design: Reprting the details and the results f the lw level design activity. Implementatin: Reprting the details and the results f the prject cding activity. Testing: Reprting the details and the results f the prject testing activity. Cnclusins (last chapter). What cnclusins can students draw frm the whle prject? This shuld include a clear statement f what has been achieved verall, and will nrmally cntinue by suggesting areas f further related wrk, which culd be dne. 2. The reprt itself (apart frm technical cnsideratins) is wrth 15% f the prject mark. Hwever, it frms the basis f an independent assessment f the prject and therefre has greater effect than 15% in practice. 3. The reprt must be n paper f A4 size (210 x 297 mm). Only ne side f paper shuld be used except in the Auxiliary Appendix.

4 4. The reprt must be prduced using wrd prcessing facilities. The bdy f the reprt shuld be suitably divided int chapters and sectins. Chapters, sectins, pages, figures and appendices shuld all be numbered. Chapters, sectins and appendices shuld have a heading. Each chapter shuld start n a new page. The bdy f the reprt shuld be preceded by a temprary title page, an abstract and a list f cntents, and it shuld be fllwed by the references and then any appendices. References t ther published wrk shuld fllw the cnventins used in giving references in published wrk. e.g.: [1] P.J. Denning. Human errr and the search fr blame. Cmmunicatins f the ACM 33(1): pp 6-7, January The abstract page must give the title, authr, and supervisr, as well as an abstract f the prject. 5. Straightfrward and peripheral aspects f the wrk dne shuld be mentined nly briefly, and descriptin and explanatin cncentrated n imprtant and interesting aspects. N extra credit is gained by writing a lng reprt and excessive length is detrimental. Mre detailed descriptin shuld be placed in appendices t the reprt. The appendices and/r the Auxiliary Appendix shuld cntain any further dcumentatin. Only the reprt itself will be held in the Department. Therefre, where imprtant material is nt included in it, e.g. because it is nt cnvenient t prduce it in A4 frmat, r it wuld be t bulky, it may smetimes be apprpriate t include extracts in the reprt. Cpyright In general, it is an infringement f cpyright t reprduce any material, except shrt acknwledged qutatins, frm a published bk r jurnal withut the written permissin f the publisher. Except fr the cpying f material that is clearly frm internal dcuments f the Department, any cpying f bks, jurnals, r dcuments required fr the reprt shuld be checked with the supervisr befre it is carried ut. Any material that is cpied must be acknwledged as such. Attempting t present material written by thers as yur wn is plagiarism and a serius disciplinary ffence, as described in the University guidelines in the Undergraduate Handbk. Aviding Plagiarism 1. Unacknwledged direct cpying frm the wrk f anther persn, r the clse paraphrasing f smebdy else's wrk, is called plagiarism and is a serius ffence, equated with cheating in examinatins. This applies t cpying bth frm ther students' wrk and frm published surces such as bks, reprts r jurnal articles. 2. Paraphrasing, when the riginal statement is still identifiable and has n acknwledgement, is plagiarism. A clse paraphrase f anther persn's wrk must have an acknwledgement t the surce. It is nt acceptable fr yu t put tgether unacknwledged passages frm the same r frm different surces linking these tgether with a few wrds r sentences f yur wn and changing a few wrds frm the riginal text: this is regarded as ver-dependence n ther surces, which is a frm f plagiarism. 3. Direct qutatins frm an earlier piece f yur wn wrk, if nt attributed, suggest that yur wrk is riginal, when in fact it is nt. The direct cpying f ne's wn writings qualifies as plagiarism if the fact that the wrk has been r is t be presented elsewhere is nt acknwledged. 4. Plagiarism is a serius ffence and will always result in impsitin f a penalty. In deciding upn the penalty the Department will take int accunt factrs such as the year f study, the extent and prprtin f the wrk that has been plagiarized, and the apparent intent f the student. The penalties that can be impsed range frm a minimum f a zer mark fr the wrk (withut allwing resubmissin) thrugh cautin t disciplinary measures (such as suspensin r expulsin). Expected wrklad On average students need t spend 6 hurs f study and preparatin fr each 50-minute lecture/tutrial. Attendance plicy Nt cntacting yur Lecturer regularly is equivalent t absence frm lectures which shall nt exceed 15%. Students wh exceed the 15% limit withut a medical r emergency excuse acceptable t and apprved by the Dean f faculty shall nt be allwed t take the final exam f the prject and shall receive a mark f zer fr the curse. If the excuse is apprved by the Dean, the student shall be cnsidered t have withdrawn frm the curse.

5 Curse academic calendar week Basic and supprt material t be cvered Deliverables Psting the list f prject tpics (1) (2) Selectin f prject Frming prject teams Selectin f prject (3) Final apprval f prject teams and prject allcatin t teams Orientatin meeting with prject supervisrs (4) Intrductin t general rules, prject planning, grading, team wrk - Intrductin t prject develpment prcess, - Intrductin t Prject dcument Structure, - System cncept and prblem statement Prblem diagnsis Prpsed treatment, Wrk Plan (5) (6) Submissin f Wrk Plan t supervisrs. (7) Apprval f Wrk Plan. Exam Prpsal (8) Requirement elicitatin. (9) Requirement mdelling analysis. SRS dcument (10) (11) SRS dcument SRS Revisin Requirement Analysis Describe the prblem dmain; describe clearly what kinds f issues exist in the current practice that yu wuld like t address. (12) Prttype (13) Exam 2 Sftware architecture (style, subsystems, cmpnents...) (14) (15) Architectural design: Mapping analysis t architectural design Revisin: Architectural design: Mapping analysis t architectural design Architectural design (16) Examinatin Mdule references Bks Title: The Unified Sftware Develpment Prcess Authr(s)/Editr(s): Jacbsn, Bch and Rumbaugh Publisher: Addisn Wesley, 2003 Title: Object-Oriented Sftware Engineering: Using UML, Patterns, and Java Authr(s)/Editr(s): Bernd Bruegge, Allen Dutit Publisher: Prentice Hall, 2003 Title: Object-Oriented Mdeling and Design with UML

6 Authr(s)/Editr(s): Michael R. Blaha, James R Rumbaugh Publisher: Prentice Hall, 2005