KUTZTOWN UNIVERSIT of PENNSYLVANIA

CSC 355–SOFTWARE ENGINEERING II, SPRING 2016

WRITING-INTENSIVE (WI) COURSE

Instructor:Dr. Joo Tan

E-Mail:

Web Site:

Office:Old Main247

Phone:610-683-4413

Office Hours: MW10am-12pm,F10-11am or by Appointment only

COURSE DESCRIPTION

This is the second course in a two semester capstone sequence. This course introduces the fundamental principles of software engineering. Coverage will include the System Development Lifecycle (SDLC) methodologies, capturing requirements, design modeling, project management, risk management, and quality assurance. Students will learn techniques for requirements elicitation, prioritization, validation, and specification.They will be introduced to various design models that are used to capture requirements.

PREREQUISITES

A grade of "C" or better in CSC354 and a GPA of 2.25 in all CSC courses is required.

TEXT BOOKS: (both books are required)

  1. Essentials of Software Engineering,Frank Tsui, Orlando Karam, Barbara Bernal,Addison-Wesley, 2014, 3rd Edition, ISBN:978-1449691998
  1. UML Distilled,Martin Fowler,Jones & Bartlett Learning, 2013, 3rd Edition, ISBN: 978-0321193681

COURSE OBJECTIVES

After completion of this course, students will be able to:

  • Describe the software requirements specification process
  • Identify the various software process models that are commonly followed today
  • Outline and discuss issues involved in software project management
  • Identify and explain the issues involved with risk management
  • Outline and explain the process of requirements elicitation
  • Explain the object-oriented (OO) models used in requirements specification
  • Explain the object-oriented (OO) models used in architectural design
  • Explain and discuss the complexities of working in a team environment
  • Participate in formal technical presentations

GRADING

  • Technical Documents50%
  • Presentation10%
  • Attendance10%
  • Mid TermDelivery10%
  • Final Delivery20%

Your final letter grade in the course will be given according to the following scale:

A:93-100%,A-: 90-92%,B+: 87-89%,B: 83-86%,B-: 80-82%

C+: 77-79%,C: 70-76%,D: 60-69,F: < 60%

ATTENDANCE

Attendance in the course is mandatory. You will lose the attendance grade if you miss threeor more unexcused absences. You will receive a grade of “F” if you miss 6 or more unexcused class meetings. Arriving late (10 or more minutes) late for three class meetings is considered one day missed. You are responsible for allmaterial covered in class, including team meetings, technical information, coding standards andconventions, verbal specification of assignments, and your questions about topics that are not clear toyou. There should be no classroom conversations, cell phone usage, text messaging, eating, sleeping,obscenities, listening to music or other disruptions of the class.

TEAM ROLES

Each studentwillassume one or more of the following project roles within your team:

  • Project Leader (PL)
  • Project Manager (PM)
  • Systems Analyst (SA)
  • System Designer (SD)
  • System Tester (ST)
  • System Developer (DV)

Restriction: A developer cannot be a tester and vice versa.

TEAMRULES

The following will apply for your team project during the semester:

  • As in CSC354 you will be working in teams of three or four students on a project for the entire semester.

To simulate real world projects, you are assigned to a project team at the beginning of the semester.

  • You are encouraged to meet as a team at least once a week to discuss your team project.
  • Meet with your client contact person frequently; at least twice a month is recommended.
  • It is your responsibility to understand the project, process, and system as it relates to your role at each phase of the software development lifecycle (SDLC). This means that you must attend all team meetings, including any meetings scheduled with the client.
  • Talk to the course instructor if you do not understand the responsibilities of your assigned role(s).
  • The instructor has the authority to fire a particular student from a team at any time. When a person is fired, s/he will not be allowed to attendfutureteam meetingsor participate in team activities until a team accepts him/her into the team. As a result, this person may not earn team points.
  • The project team may also recommend the firing of a team member at any time during the semester. Contact the course instructor to initiate this recommendation.

DELIVERABLE ARTIFACTS

Each team will write and revise the following technical documents (artifacts) during the semester:

  1. Sequence Diagrams/Design Class Diagrams
  2. Database Design/Package Diagrams
  3. Development Plan (DP)
  4. Test Plan/Specification (TPS)
  5. System/User Manual

NOTE: Since each person in a team will receive the same grade for each artifact, you should read each document and provide input/feedback before it is submitted for grading.

PACISE CONFERENCE

The CS&IT department at Kutztown University will be hosting the Pennsylvania Association of Computer and Information Science Educators (PACISE) conference in April 2016. There is a call for paper submissions that is due on February 5, 2016. Each project team is encouraged to submit a paper regarding their project to the conference. Paper submission will count as your Development Plan document and it will be graded as such. If your paper is accepted for presentation at the conference, you will earn extra credit points in the course. The conference website is located at:

ACADEMIC INTEGRITY

Plagiarism and cheating are serious offences and may be punished by failure on exam, or project; failure in the course; and/or expulsion from the University. Read the Computer Science department’s academic integrity policy at:

Plagiarism is a form of stealing; as with other offences against the law; ignorance is no excuse. The way to avoid plagiarism is to give credit where credit is due. If you are using someone else’s idea, acknowledge it, even if you have changed the wording or just summarized the main points.To avoid plagiarism, you must give credit whenever you use

  • another person's idea, opinion, or theory;
  • any facts, statistics, graphs, drawings--any pieces of information--that are not common knowledge;
  • quotations of another person's actual spoken or written words; or
  • paraphrase of another person's spoken or written words.

TEAM PRESENTATION

There will be aformal team presentation at end ofthe semester. More details about the presentation will be given in class. Also, you have to create a poster of your project for demonstration during the presentation.

E-MAIL CORRESPONDENCE

The best way to contact me is by e-mail. You must use your KU e-mail account for all electronic mail correspondence. Include the course #, [CSC354], in the e-mail subject.There is no guarantee that I will receive nor reply to your private web-based e-mail such as Yahoo! or Gmail.

SYSTEM DELIVERY

There will betwo important system/application deliveries this semester:

An intermediate delivery during the middle of the semester

  • A final delivery near the end of the semester

Your project will be graded based on successful completion of agreed upon functionality.

ACCREDITATION

Note that for accreditation purposes, some assignments, projects, and/or examinations may be photo-copied and retained.

STUDENTS WITH SPECIAL NEEDS

If you have already disclosed a disability to the Disability Services Office (215 Stratton Administration Building) and are seeking accommodations, please feel free to speak with me privately so that I may assist you. If you have an injury sustained during military service including PTSD or TBI, you are also eligible for accommodations under the ADA and should contact the Disability Services Office.

Web reference: