CIS 204 COMPUTER SCIENCE II, Fall 2000



KUTZTOWN UNIVERSITY (KU)

CSC35410 – SOFTWARE ENGINEERING I, WRITING-INTENSIVE (WI) COURSE, FALL 2019

Collaboration with Ming Chuan University (MCU)

Instructor: Dr. Joo Tan

E-Mail: tan@kutztown.edu (Best way to contact me)

Web Site:

Office: Old Main 247 x3-4413

Office Hours: TH 8:00AM -9:15AM and W 8:30AM – 9:45AM

COURSE DESCRIPTION

This is the first 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

Completion of 24 CSC credits, numbered CSC125 or higher AND a GPA of 2.25 in the CSC courses

See the course instructor immediately if you do not meet these pre-requisites.

TEXT BOOKS:

1. (Required) Essentials of Software Engineering, Frank Tsui, Orlando Karam, Barbara Bernal, Jones & Bartlett Learning, 2016, 4thEdition, ISBN: 978-1449691998

2. (Recommended) 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 the issues involved with risk management

• Outline 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

Your final grade will be calculated using the following percentages:

• Technical Documents 45%

• Attendance 10%

• Collaboration 10%

• Mid Term Examination 20%

• Final Examination 15%

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%

TEAM PRESENTATION

There will be a formal team presentation at the end of the semester, which replaces the final examination. Details will be given during the semester.

ATTENDANCE

You are allowed three absences during the semester. You will lose the 10% attendance grade if you miss more than three unexcused absences. For each day over the three unexcused absences, you will lose 2 points from your collaboration grade. Arriving 20 or more minutes late for class is considered ½ day missed. You are responsible for all material covered in class, including team meetings, technical information, coding standards and conventions, verbal specification of assignments, and your questions about topics that are not clear to you. There should be no loud interpersonal conversations, cell phone usage, text messaging, eating, sleeping, obscenities, listening to music or other disruptions of the class during class meetings.

TEAM ROLES

Each student will assume one or more of the following project roles within your team:

• Project Leader (PL)

• Project Manager (PM)

• Systems Analyst (SA)

• UI Designer (UI)

• System Tester (QA)

• System Developer (DV)

• Database Administrator (DBA)

TEAM RULES

• You will be working in teams of three to five KU students on a project for the entire semester.

• Additionally, students from Ming Chuan University (MCU) of Taiwan will be assigned to each project team. You must collaborate (have a meeting) with them each week on your project.

• Note that there is a twelve (12) hour difference between EST and Taiwan during non-daylight savings time. There is a thirteen (13) hour difference during daylight savings period.

• To simulate real world projects, you will be considered part of a company and are assigned to a project team at the beginning of the semester.

• You are to keep a weekly collaboration journal/log about your communication with MCU’s students. This will be considered your collaboration grade for the course.

• You are required to meet as a team at least once a week to discuss your team project.

• 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 attend future team meetings or participate in team activities until a team accepts him/her into the team. As a result, this person may no longer earn team points.

• The project leader role may be rotated during the semester.

DELIVERABLE ARTIFACTS

Each team will write/update some of the following technical documents (artifacts) during the semester:

1. Software Project Plan (SPP)

2. Software Requirements Specification (SRS)

3. High Level Design (HLD): Use Case Diagrams (USD) & System Sequence Diagrams (SSD)

4. User Interface Design (UID)

5. Risk Management Plan (RMP)

NOTE:

• Since this is a writing-intensive course, each student is expected to write a portion of each document.

• You must specify clearly in the Revision History section which portion of the document you are responsible for writing. Grades will be given based on your personal contribution/participation.

EXAMINATIONS

There will be a mid-term examination during the semester. You may bring one 8.5” x 11” piece of paper (cheat sheet) for reference. The cheat sheet must be hand-written and may cover both sides; however, it cannot be copied or xeroxed.

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.

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.

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:

................
................

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

Google Online Preview   Download