CSCE 4963 CAPSTONE II - Syllabus



CSCE 4963: Capstone IISyllabus Fall 2019Meeting times: MWF 3:05-3:55Location: JBHT 0239Instructor: Dr. James Patrick ParkersonOffice: JBHT 520Email: jparkers@uark.eduWeb site: hours: TBDCourse Description: Computer Science and Computer Engineering students complete a comprehensive project during their final year of undergraduate studies. The project is completed over two semesters in phases: concept, design, formal proposal, implementation, presentation, and report. The project includes and may require the integration of software, hardware, and human factors elements and is developed using appropriate software engineering and system design methodologies. The emphasis in Capstone I (one hour) is on brainstorming, project evaluation, team formation, careers, business, intellectual property, professional organizations, and professional ethics. The emphasis of Capstone II (three hours) is on detailed design, rapid prototyping, implementation, testing, and packaging.Prerequisite: CSCE 4561 Capstone ITextbook/required material: No textbook is required and necessary course information will be posted on the course web page.ScheduleThe scheduling of presentations and meetings will be done via email. The instructor will email the entire class or individual teams as necessary.“Team meetings” – should occur weekly, on your own, but it is strongly suggested that you meet during class time (and more frequently when necessary).“Team updates” – will typically occur in the conference room across the hall from Dr. Parkerson’s office (JBHT 532) but may occur elsewhere and announced in emails. All team members must be present for each team update, and the team’s task list and schedule must be updated on the group web site beforehand. Each team will have approximately 10 minutes per meeting, and teams assigned to meet on a given day will meet in numerical order by team number.Deliverables and Evaluation20% - Project Planning and Reporting 5% - Attendance at team meetings, design reviews, and in-class project presentations - participation as appropriate 5% - Project Web Site* - including Project title, Team members’ names with links to their individual web pages, Project Summary (same as abstract from proposal), link to Project Proposal, Final Report, and presentations (in pdf format), and all deliverable software, documentation, and electronic content.10% - Tasks and Schedule – before every “Team update” meeting, the team’s task list and schedule must be updated on the group’s web site. This should include a thorough breakdown of tasks (completed, current, and future) with the name(s) of the student(s) assigned to each task and estimated beginning and completion dates.60% - Project Results 50% - team grade - Final Project Presentation includes presentation, final demo in class (10-12 minutes), and report. Presentations should contain full project introduction, overview, design, and live demo if possible.? Final project deliverable on group web site should be well packaged and contain source code and README.html instructions for how to install, and a demo script and/or clear instructions for use.10% - team grade – Poster presentation (see example poster template on the course site – keep poster size same but format can and should vary – be creative and make it look good and show off your project!)20% - Team ParticipationPeer evaluation. At the end of the semester, every student will fill out a survey ranking the performance and participation of each of his or her team members. Any student who does not complete and submit this form will receive a 0. Every other student will receive a grade related to the average scores assigned by his or her project team members. (The instructor retains the right to discard an evaluation which is a dramatic outlier.)* Capstone web sites should be self-contained at . All report and presentation documents should be in pdf format and uploaded to the capstone web server (i.e. not links to documents hosted elsewhere).Note on presentations:Presentations are expected to be of professional quality. Each should be well practiced and take an amount of time very close to the allotted amount for that presentation (i.e. if you are asked to give a 5 minute presentation, your presentation should at least be between 4:30-5:30). Presentations which are too short or too long will receive sizeable deductions which are proportional to their deviation from the expected time. Please see the “Tips for presentations.pdf” on the course web site to help prepare presentations.Grading PoliciesA scale similar to the following will be used to determine final course grades. However, it is approximate and subject to change.A: over 90%B: 80-89%C: 70-79%D: 60-69%F: below 60%Late work: Late work will be penalized an additional 10% (absolute, not relative) for each day late (including holidays, weekends, etc.) up to a maximum late penalty of 30% (3 days), after which a 0 will be assigned. An assignment is considered one day late if it is submitted after the deadline, but less than 24 hours after the deadline. ?Per university policy, no work will be accepted after the last day of class, even if it is submitted before the final exam.Grading Criteria:Presentation checklist:Content: Problem statement, Understandable objective, Potential impact/champion, Topic difficulty, Believable scope, Related work reviewed, Approach will lead to result, Tasks make sense, Use cases make sense, High level design, Factual accuracy, How well audience can understand the material.Presentation: Well-organized, All team members present a section, Aesthetics, Presentation skills, Well-timed, Ability to stimulate interestProposal/Report checklist:Content: Problem statement, Coverage of all required sections, Organization, Interesting, Relevant, Understandable objective, Potential impact/champion, Topic difficulty, Believable scope, Related work reviewed, Approach will lead to result, Tasks make sense, Use cases make sense, High level design, Factual accuracy, How well a reader can understand the material.Format: Typing, format, spelling, Figures appropriate and correct, AestheticsEquipment:Projects may require resources including software and/or equipment.??Since there is no textbook, expect to spend up to $100 on miscellaneous equipment per person.??More expensive projects can be partially covered from student lab fees as well, with the department covering up to $100 per project.??The student needs to provide the instructor with a request and details on how to make the purchase.??The request is sent to the instructor and then to the CSCE Department Head for approval.??The student then works with CSCE office staff so that the department pays for the item.??This can proceed via email with attachments.??If the CSCE Department buys an item, it owns the item.Course Objectives for Capstone I & IIProblem SolvingStudents identify problems and design and implement solutions. Students are strongly encouraged to make industry or university contacts and to identify real problems.Students work in small teams and learn collaborative skills.Students use knowledge from earlier courses. In particular, students exercise core topics in our curriculum: data structures, algorithms, programming languages, computer organization, operating systems, and software engineering.Students opportunistically learn to discover missing knowledge needed to solve problems using the literature and the web.Students use system and software engineering methods.Students present results and package results for reuse.Job Skills - Organization, Presentation, and Writing SkillsProject lifecycle and project management skills - staying on track, managing riskTime management skillsCollaboration skillsWriting skillsPresentation skillsOrganization skillsSoftware EngineeringIterative development, continuous integrationProblem, proposal, requirements, use cases, design, implementation, unit/regression testingUse of computation tools: e.g., web page development, source control, etc.Career PlanningStudents gain a clearer understanding of their career options and develop a plan for how to achieve them (i.e. what they want to accomplish, life and career planning)Typically, students prepare for careers in industry or for graduate schoolLeave no student behind, meaning that every student has a plan for work, grad school, or another productive direction - no one goes home to live with their parents following senior yearCareer adviceResume & interview, career center, career fair infoAttend career fairs and meet potential employersCS/CE marketplaceEmployee, consultant, or small business ownerGraduate schools - MS or PhD programs - GRE - grad school applications - applying for graduate assistantshipsBusiness of ComputingTypes of companies, marketplacesSurvival skills - time management - return on investment (ROI) - planningLarge business option - employee agreements - annual evaluation, hiring/firing, raises, etc.Small business option - cash flow - how to start a small business - business planProposals - tell a compelling story - problem, objective, technical approach (background and related work, approach, impact, tech transfer plan), statement of work (tasks, deliverables, schedule), facilities, budgetRead and negotiate a software license - open source - source forgeInventions - how to complete a patent disclosure - file a patentCollaboration - privacy-enhanced web page or - non-disclosure agreementsEthics and ProfessionalismStudents write a paper and give a presentation over topics in computing related to: Ethics, Life Long Learning, Professionalism, and/or Knowledge of Contemporary IssuesRelationship of Capstone II to Computer Engineering Program Student Outcomes: (c) An ability to design a system, component, or process to meet desired needs within realistic constraints such as economic, environmental, social, political, ethical, health and safety, manufacturability, and sustainability.(d) An ability to function on multidisciplinary teams.(e) An ability to identify, formulate, and solve engineering problems.(g) An ability to communicate effectively.Relationship of Capstone II to Computer Science Program Student Outcomes: (c) An ability to design, implement and evaluate a computer-based system, process, component, or program to meet desired needs.(d) An ability to function effectively on teams to accomplish a common goal.(f) An ability to communicate effectively with a range of audiences.(j) An ability to apply mathematical foundations, algorithmic principles, and computer science theory in the modeling and design of computer-based systems in a way that demonstrates comprehension of the tradeoffs involved in design choices.(k) An ability to apply design and development principles in the construction of software systems of varying complexity.Academic Honesty Statement:As a core part of its mission, the University of Arkansas provides students with the opportunity to further their educational goals through programs of study and research in an environment that promotes freedom of inquiry and academic responsibility. Accomplishing this mission is only possible when intellectual honesty and individual integrity prevail. Each University of Arkansas student is required to be familiar with and abide by the University’s ‘Academic Integrity Policy' at . Students with questions about how these policies apply to a particular course or assignment should immediately contact their instructor.The following policies will apply to this class.The work you submit for this class is expected to be the result of your own work, or that of your partner(s) for any group work – but the groups must be those assigned by the instructor in advance. You are free to discuss course material and general approaches to problems with others but you should never misrepresent someone else's work as your own and all material from other sources must be properly cited during presentations and in reports. It is also your responsibility to protect your work from unauthorized access.?Violations of the policies above will be reported to the Provost's office via an Academic Integrity Allegation Evidence Form (see ) and may result in a ZERO on the assignment, an F in the class, or suspension from the university, depending on the severity of the violation.ADA Statement:If any member of the class has a documented disability and needs special accommodations, the instructor will work with the student to provide reasonable accommodation to ensure the student a fair opportunity to perform in this class. Please advise the instructor of the disability and the desired accommodations within the first week of the semester.Inclement Weather:If the university is officially closed, class will not be held. When the university is open, you are expected to make a reasonable effort to attend class, but not if you do not feel that you can get to campus safely. Assignment due dates will be postponed in case of inclement weather.Emergency ProceduresMany types of emergencies can occur on campus; instructions for specific emergencies such as severe weather, active shooter, or fire can be found at Weather (Tornado Warning):Follow the directions of the instructor or emergency personnel.Seek shelter in the basement or interior room or hallway on the lowest floor, putting as many walls as possible between you and the outside.If you are in a multi-story building, and you cannot get to the lowest floor, pick a hallway in the center of the building.Stay in the center of the room, away from exterior walls, windows, and doors.Violence / Active Shooter:CALL - 9-1-1AVOID - If possible, self-evacuate to a safe area outside the building. Follow directions of police officers.DENY - Barricade the door with desk, chairs, bookcases or any items. Move to a place inside the room where you are not visible. Turn off the lights and remain quiet. Remain there until told by police it is safe.DEFEND - Use chairs, desks, cell phones or whatever is immediately available to distract and/or defend yourself and others from attack. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download