CSCI 3350 Software Engineering II

Transcription

1 CSCI 3350 Software Engineering II Spring 2017 Course Syllabus Brian T. Bennett, Ph.D. Assistant Professor Department of Computing Office: 479 Nicks Hall Campus Office Hours: MW, 3:00pm 4:30pm, Office Phone: TR, 1:00pm 2:30pm Other Times By Appointment Course Site: Best ways to contact: , Slack, In Person Course Overview Section Information Sections: CSCI Meeting Time: MW, 9:05am 11:05am Meeting Location: Nicks Hall Room 321 Catalog Description Prerequisites: CSCI 3250, completed with a grade of C minus or better. Students not meeting this requirement will be administratively dropped. Software development as an engineering discipline with emphasis on detailed design, implementation, testing, maintenance, project management, verification and validation, configuration management, and software quality assurance. Communications (written and oral), legal, professional, ethical issues, participation on team projects, and use of automated tools are integral. This course is Oral Intensive. Learning Outcomes At the completion of this course, the student is expected to: 1. apply an appropriate software lifecycle model to a given scenario (Student Outcome 5a*), 2. demonstrate an understanding of processes involved in the creation, evaluation, and use of project deliverables in each phase of the software development lifecycle with a focus on detailed design, implementation, testing, and maintenance (Student Outcomes 4b, 5a, CS-2, and IS-2), 3. demonstrate the ability to participate on project teams in various roles (Student Outcomes 1c*, IS- 2*), 4. demonstrate an understanding of the measurement of software products and processes (Student Outcomes 4b*, IS-2*), 5. demonstrate an understanding of project scheduling and estimation (Student Outcomes 4b*, 5c*, IS-2*), Spring 2017 Course Syllabus Page 1

2 6. demonstrate an understanding of the controlling disciplines used to assess and improve software quality, including configuration management, quality assurance, verification, and validation (Student Outcomes 4b, IS-2) 7. write and orally communicate about software engineering (Student Outcomes 1a*, 1b*). Major Topics Oral Communication in Software Engineering, Project Planning and Estimation, Evaluating Products and Processes, Quality Assurance: QA and Metrics, Configuration Management, Dev/Ops, Emerging Architectures (Microservices, Serverless, Internet of Things), Testing Review, Testing Tools, Acceptance Testing, Design Patterns, Security, Maintenance and Refactoring. Course Materials Textbook Recommended Braude, E.J., & Bernstein, M.E. (2011). Software Engineering: Modern Approaches. (2 nd Ed.). Hoboken, NJ: John Wiley & Sons, Inc. ISBN : Resource Readings Recommended Cohn, M. (2006). Agile Estimating and Planning. Upper Saddle River, NJ: Prentice Hall. ISBN: Sims, C., & Johnson, H. L. (2012). Scrum: A Breathtakingly Brief and Agile Introduction. ISBN: Library Resources You will be required to use research materials such as the ACM and IEEE digital libraries to complete one or more oral intensive assignments. Students can find computer science research materials at Sherrod Library's Research Guide for Computer & Information Sciences: Software Collaboration Tools You will use collaboration tools to complete the course project. Most of these tools will be cloud-based, so an Internet connection is required. Additional mobile or local software may be used, but is not completely necessary. o For Team Communication: Slack ( Software Development Cycle Tools The course project will be managed using Scrum. Therefore, you must use software that will manage the project backlog, and story boards. Configuration Management Tools The course project will require you to use git for source code control. We will discuss other tools during the semester as well. Software Development Language The particular implementation language for the course project is up to your development team unless other requirements impose a language restriction. The language must be appropriate for the project, and the software produced must be easy to demonstrate in the classroom using the resources available. Several programming environments are available in our computer labs. Java tools are available on the web. Visual Studio Community Edition is available as a free download. More advanced Visual Studio IDEs are available via the MSDNAA agreement. To get your copy of Visual Studio, compete the form available at The completed form must be submitted to the department s System Administrator, Robert Nielsen, 475 Nicks Hall. Spring 2017 Course Syllabus Page 2

3 Course Policies Format The emphasis of this course will be finishing and presenting a software project from inception to completion, or continuing an incomplete project. Therefore, the course will consist of a hybrid delivery style that incorporates traditional lecture with in-class activities, while requiring heavy group activities. All course materials and assignments will be available through the course website: You should check this site daily for updates and announcements. A tentative course schedule is provided separately. This course is 3 credit hours, but meets 4 hours per week. This schedule is designed to give groups project meeting time during class. You should expect to meet with your team about one hour in class each week, except when other circumstances prevent this meeting. Grading The following grade scale will be used this semester. There is no rounding of calculated grades. While I generally do not change this scale, I reserve the right to adjust it slightly up or down at the end of the term. A A B+ B B C+ C C D+ D F < 60 Evaluation The final grade in the course is based on the students performance on both group project deliverables, individual oral assignments, participation in in-class exercises and quizzes, and examinations. The percentage breakdown, and an explanation of each assignment category follows. Major Assignments (Overview) Exams 45% Exam 1 10% Exam 2 10% Final Exam 25% Course Project (equally weighted) 25% Presentation Assignments 25% Participation and Exercises 5% The artifacts for a class case study are an integral part of this course. This will include technical oral presentations both as a team and individually. Individual presentations may relate to material covered in class, or some aspect of your group project. Because Oral Communication involves both speaking to be understood, and listening to understand, individual presentation topics are testable (i.e., aspects of the presentations will appear on the exams). Exams I will give three exams during the semester. The first two exams will test your knowledge of the materials just covered, and will count 10% each. The final exam will be comprehensive, covering all material from the course to ensure you meet the learning outcomes, and will count 25% of the final grade. Course Project(s) The course project(s) gives you hands-on experience in the design and implementation of a software system using a specific software development methodology within a team environment. The course project may be a project for a real customer, which provides a service-learning experience. To set your pace for the project, you will have multiple sprint deliverables due throughout the semester. Deliverables must be completed and submitted electronically to D2L by 11:59pm on the due date. Late submissions are NOT accepted under any circumstances (unless in the case of a documentable D2L outage). All sprint grades in Software Engineering II receive equal weight. Sprint deliverables may include more than simple Scrum-related tasks, such as waterfall-style tasks, that will help your team become familiar with classical methodologies. Spring 2017 Course Syllabus Page 3

4 Presentation Assignments Because this course is oral-intensive, 25% of the final grade is based on oral presentations. You will have both individual (or pair) presentations and team presentations during the semester. Individual (or pair) presentations are testable and questions from these presentations may appear on exams. Team and pair presentations must allow each person to have a significant role in the presentation. Presentation grades are assigned to each person who participates in the team or pair presentation. An individual s presentation grade may be prorated based on their contribution to the presentation. For example, a person who contributes only 2 minutes to a 30-minute presentation (6.7%) will receive a lower grade than someone who contributes 15 minutes (50%) in the same presentation. Exercises and Participation Frequent exercises will be assigned throughout the semester. Exercises will consist of in-class (and potentially out-of-class) activities that help you better understand the course content. In-class exercises are usually participatory in nature and will contribute to an overall participation grade, while out-of-class activities must be completed and submitted for a grade. Out-of-class exercises may include more detailed activities or quizzes over lecture material. In-class exercises may also be quizzes over the previous class s material. The motivation for these assignments is to keep you engaged both inside and away from the classroom. You cannot make up missed in-class or out-of-class exercises. Components of the participation grade may include: grades on graded exercises, the percentage of classes you attended, and the contribution factor of project peer reviews. Attendance Participation and Attendance While I expect you to manage your time appropriately, spending time in class is important. Because attendance and grades are highly correlated, attendance in this course is required. Attendance and participation will be tracked and enforced in the following ways: 1. Attendance will be tracked via an attendance sheet. You must sign this sheet each regular class session to be considered present. Attendance is always taken, so not signing the sheet counts as an absence. 2. You must complete every assignment. Software engineering requires professionalism, so meeting deadlines and behaving in a professional manner with classmates, customers, and the instructor is essential. Participation in project activities is required, and will be enforced via project grading and peer reviews. a. Missing any assignment, no matter how small, will result in a grade of F. An exception to this policy is made for missed in-class exercises or quizzes. I reserve the right to waive this clause if you show proof of an extenuating circumstance. b. Late assignments are not accepted, except as stated in the Makeup Work policy in this syllabus. You must complete every assignment on time. I reserve the right to waive this clause if you show proof that you completed a significant portion of the assignment before the due date. c. Receiving an average peer review rating below 50% for two sprints (whether consecutive or not) during the semester will result in an F for the course. The essence of this course is the course project. Not participating in the project at an adequate level will not be tolerated. Note that I will investigate these low ratings by reviewing all project contributions. If I feel the low rating is unwarranted based on the evidence available, I will waive this clause. 3. Absences a. Missing 3-4 classes will result in the loss of one step of your final letter grade. For example, A becomes A-, A- becomes B+, B+ becomes B, etc. b. Missing 5 or more classes will result in the loss an additional step of your final grade FOR EACH ABSENCE. c. I will consider extenuating circumstances when enforcing the absentee policy. However, you must notify me of extenuating circumstances as soon as possible before an absence. Spring 2017 Course Syllabus Page 4

5 Makeup Work All work is due at the date and time specified on the assignment specification not the D2L Dropbox. If the due date or time changes for any reason, I will notify you either via , Slack, or D2L (or all three). Accepting makeup work is at my discretion. You will not be allowed to make up work except in the case of an emergency situation. Exams may be made up only if given advanced notice of an extenuating circumstance. If you must miss an exam, notify me as soon as possible BEFORE the exam time to discuss your reason for missing, and to arrange a makeup. Missed in-class exercises cannot be made up No Exceptions. Academic Misconduct Policy ETSU Honor Code East Tennessee State University is committed to developing the intellect and ethical behavior of its students. Students found to be in violation of policies on plagiarism, cheating, and/or fabrication will be held accountable for their actions. Any knowledge of academic misconduct should be reported. Students are expected to act with honesty, integrity, and civility in all matters. ETSU Honor Pledge By becoming a member of the campus community, students agree to live by the standards of the honor code and thereby pledge the following: I pledge to act with honesty, integrity, and civility in all matters. Course Honor Policy Academic Misconduct in any form will not be tolerated. East Tennessee State University defines Academic Misconduct as an offense for which both individuals and organizations may be subject to disciplinary action. See these policies in the catalog, located at The University defines academic misconduct as follows: Academic Misconduct. Plagiarism, cheating, fabrication. For purposes of this section the following definitions apply: 1. Plagiarism. The adoption or reproduction of ideas, words, statements, images, or works of another person as one s own without proper attribution, 2. Cheating. Using or attempting to use unauthorized materials, information, or aids in any academic exercise or test/examination. The term academic exercise includes all forms of work submitted for credit or hours, 3. Fabrication. Unauthorized falsification or invention of any information or citation in an academic exercise. If you observe or learn about a violation of academic integrity, it is your responsibility to report it. I will employ all means available to identify academic misconduct including electronic plagiarism detection. ETSU Student Disciplinary Policies, Part 3 Academic and Classroom Misconduct, Numbers 2 and 3, states: (2) Plagiarism, cheating, and other forms of academic dishonesty are prohibited. Students guilty of academic misconduct, either directly or indirectly, through participation or assistance, are immediately responsible to the instructor of the class. In addition to other possible disciplinary sanctions which may be imposed through the university s academic misconduct policy as a result of academic misconduct, the instructor has the authority to assign an F or a zero ( 0 ) for the exercise or examination, or to assign an F in the course. (3) Students may appeal a grade assignment associated with a finding of academic misconduct, as distinct from a student disciplinary sanction, through the university s Spring 2017 Course Syllabus Page 5

6 academic misconduct procedure. Courses may not be dropped pending the final resolution of an allegation of academic misconduct. (See Part 6 Disciplinary Procedures, Paragraph (6) Academic Misconduct Procedures). Given these definitions and restrictions, this course will enforce the following policies regarding academic integrity violations. The first offense of academic misconduct will result in a grade of zero ( 0 ) on the exercise or examination. A notice will be sent to the student, to the Office of the Dean of the College of Business and Technology, and to the Chair of the Department of Computing. The second offense of academic misconduct will result in a grade of F for the course. A notice will be sent to the student, to the Office of the Dean of the College of Business and Technology, and to the Chair of the Department of Computing. Be aware that ETSU Academic Misconduct Procedures state: For a second academic misconduct offense the penalty may be permanent expulsion from the University. A zero received as the result of academic misconduct cannot be dropped as a lowest grade. If you share your work with someone who copies your work, BOTH PARTIES are subject to the penalty for academic misconduct without regard to who copied whom. Know and understand your right to appeal. Other Issues Computer Lab Use The use of departmental computer labs is governed by the Department of Computing Lab Policies. You should familiarize yourself with these policies. The Grade of Incomplete In general, the grade of incomplete is only given in the cases of serious, uncontrollable situations that will prevent the student from completing the assigned coursework. A request for a grade of incomplete must be submitted in writing with the reason for the request and any appropriate documentation. I reserve the right to discuss your request with the department chair and/or other instructors. Remember that an incomplete could have financial aid implications; check into those issues before you make a request. Communication Policy Students must make every reasonable effort to make contact with the instructor as soon as possible to discuss any issues that arise. I generally have an open-door policy. If I am in my office, and the door is open even outside posted office hours, I d be happy to speak with you. For Software Engineering, Slack is one of the best ways to communicate with me, and is often more efficient than . However, you might not receive responses to electronic communications late at night, early in the morning, or on weekends. General Course Guidelines 1. Check the D2L site, Slack, and your ETSU account frequently. I may post announcements throughout the week. By default, all course communication will be through the D2L site and, in conjunction, your ETSU address. 2. The course schedule is provided as a suggested outline. It will remain fluid throughout the semester to give extra time on certain concepts, account for any University closings, or provide a better information flow. 3. I will provide grade sheets as appropriate to let you know where you stand throughout the semester. 4. Be courteous during class. a. Do not talk over other people and be respectful of your classmates opinions and questions. b. If you have a question, ask at the earliest opportunity! c. Come to class on time and leave on time. Spring 2017 Course Syllabus Page 6

7 5. Each student is expected to spend a minimum of 2-3 hours outside class for each hour spent inside class. Since we are in class 4 hours per week, this indicates 8-12 hours of outside involvement. This may include meeting with teammates, studying concepts, preparing for exams, or assignments. 6. Come to lectures prepared to learn and interact. I am much more effective as a professor if we have conversations in class. You will gain more from the material if you discuss it with others during the semester. Still, all individual work must be your original creation, and all team work should be the creation of the team, without input from anyone outside your team. 7. I will grade your assignments as promptly as possible usually within one week after the due date. Spring 2017 Course Syllabus Page 7