Text Box: Clark Atlanta University

 

Course Syllabus

 

CIS 691 Software Engineering

 

Instructor_______Dr. Zhicheng Wang______________________________________________

 

 

Office Hours

Tuesday/Thursday: 11:00 am-12:00 pm, 2:00-4:00 pm

Monday/Wednesday/Friday:  Appointment available

 

Office Location

SRC 1017

 

Office Telephone

(404) 880-6934

 

Email

zwang@cau.edu

 

Course

Number/Sect

Course Title

Credit

Hours

Semester

Time

Level

(U/G)

CIS 691

01

SOFTWARE ENGINEERING

3

Spring 07

T/TH 9:25-10:40 am

G

Brief Description

This course provides an introduction to Software Engineering, focusing on the process for developing large-scale software products. Concepts, procedures, management and major design issues will be covered

Prerequisites

if applicable

CIS 673 Operating System Design

HTTP Links

http://www.cis.cau.edu/course/cis691

http://www.cis.cau.edu

http://acm.org

Course Length

3 hours credit for 16 weeks.  Twice a week for 1 hour and 30 minutes each session.  The total of 48 hours

 

Course Description:

This course provides an introduction to Software Engineering, focusing on the process for developing large-scale software products. Concepts, procedures, management and major design issues will be covered. Analysis of industrial cases will be presented in the course. Unified Modeling Language (UML) will be utilized as examples of applicable technology in the semester project. This course will culminate with a group project presentation and paper encompassing the major elements of the course contents.         

 

Course Objectives:

1.       The student will have a working knowledge of software development procedures

2.       The student will obtain hand on experience by practicing teamwork project.

 

 

 

Learning Outcomes:

1.  The student will have an introduction to the concepts of Software Engineering.

2.  The student will have a working knowledge of software development life cycle management.

3.      The student will have a skill to use Unified Modeling Language.

4.      The student will practice the stage in project management.

5.      The student will learn software verification and validation.

6.      The student will learn about managing people, quality management, process improvement

7.      The student will learn software cost estimation, configuration management.

8.      The student will have an understanding of security involve software development

9.      The student will learn about the certification for CISM) and accreditation.

10.  The student will have made presentations to the class.

11.  The student will practice teamwork.

 

Course outline and Major Topics

  1. Introduction to software engineering
  2. Professional and ethical responsibility

a.       Freedom of information ACT

b.      Federal Management ACT

  1. Soci-technical systems
  2. Risk assessment (management, identification, acceptance, analysis, planning, monitoring and acceptance)
  3. Software protections

a.       Threats

b.      Vulnerabilities

c.          Application software protection (Web-based applications)

  1. Software reusability

a.       Type of reuse

b.      Reuse technology and component retrieval

c.       Experiences with reuse 

  1. Security Architecture

a.       Wesserman’s Steps to Maturity

b.      Software security process

c.       Reuse

d.      Measurement

  1. Risk evaluation involving all team member
  2. System life cycle management (analysis, development, design, evaluation and implementation)
  3. Critical systems, availability and reliability of systems

a.       Describe malicious code policy, techniques and protections

  1. Project management, software requirements and interface specification
  2. User interface design, user analysis
  3. Planning verification and validation
  4. Manage people. The People Capability Maturity Model
  5. Quality management
  6. Configuration management planning.
  7. Security specifications and performance evaluation for software development.
  8. Discuss the security systems certification and accredited process to fulfill the systems requirements.

- discuss the role of managers in the accreditation process

  1. Acquisition
  2. Explain the purpose of Approval to operate (ATO) regard to users
  3. Explain the purpose of Interim Approval to Operate (IATO) to user
  4. Describe contracts, agreements and other obligations

 

Teaching/Learning Methods: (lectures, videos, outside speakers, etc.)

  1. Lectures , T/TH, 3 hours.
  2. Project for problem solving practice
  3. Practice teamwork
  4. PowerPoint presentation to the class

 

 

Required Readings:

    • Stephen R. Schach; Object-Oriented and Classical Software Engineering, 6th Edition
    • Software engineering, 7th edition by Ian Sommerville, Addition Wesley, ISBN#0321-21026-3

 

 

 

Supplemental Readings/Additional Bibliography:

  • Shari Lawence Pfleeger; Software Engineering
  • Fowler, Martin, with Scott, Kendall; UML Distilled, 2nd Edition: A Brief    Guide to the Standard Object Modeling Language   

 

 

Grading and other policies and expectations:

The Final Grade will be based on an accumulation of all grades received during the Semester, which will consist of In-Classes exam (4), home work (5), Midterm Exam, Final Exam and Classroom Participation.          

There will be NO makeup. Any exception based on extraordinary circumstances may suffer a degradation of points awarded.

Legibility is important on all tests. English (Spelling, sentence construction, etc.) will be grade, where appropriate.

 

Evaluation Methods

Grading and other policies and expectations:

 

Assignment Type Weight (%)

  • Homework- 25%
  • Article Critiques- 20%
  • Class Project- 30%
  • Class Participation/Attendance/Quizzes- 25%

All assignments and projects are required for passing the course.

 

 

CLASS PARTICIPATION AND ATTENDANCE
Discovery does not arise from instruction but from personal engagement with the controversies and potentials of a computerized society.  You have to be in class to contribute to and benefit from that personal engagement. As you saw above, a quarter of your grade depends on class participation and attendance. In this class, engagement will take several forms:

  • You will be expected to read, summarize, and interpret the articles for yourself and others.
  • You will be expected to study problems, techniques, and approaches individually and in groups, and then present your findings both orally and in writing.
  • You will be expected to critique the perspectives/opinions of both authors and classmates in discussions and position papers.

At any class period, you may be asked to summarize and critique readings from the book or elsewhere in an “elevator speech” for the class. On such occasions, you are invited to refer to notes you've made in response to the readings. You may also be quizzed on the high points of the material.

If you are unable to attend class, notify the TA by email before the period begins for consideration of an excused absence.

CAU/CIS Policies and Expectations:

 

 COURSE POLICIES:

1.  Student Conduct In Class Policy

Any acts of classroom disruption that go beyond the normal rights of students to question and discuss with instructors the educational process relative to subject content will not be tolerated, in accordance with the Academic Code of Conduct described in the Student Handbook.

 

2.  Electronic Devices

Cellular phones, pagers, CD players, radios, and similar devices are prohibited in the classroom and laboratory facilities. Calculators and computers are prohibited during examinations and quizzes, unless specified.

 

3.  Disabilities Policy

In compliance with the Americans with Disabilities Act (ADA), all qualified students enrolled in this course are entitled to “reasonable accommodations.” Please present proper documentation and notify the instructor within the first two weeks of class of any accommodations needed for the course.

 

4.  Academic honesty

Academic honesty is based on the principle that one’s work is one’s own.  Clark Atlanta University encourages all members of the University to accept responsibility for taking academic honesty seriously by being informed, by contributing to a climate in which honesty is valued, and by considering responsible ways to discourage dishonesty in the work of others.  Students, faculty, administrators and staff should not condone or tolerate cheating, plagiarism, or falsification, since such activity negatively affects members of the academic community.  Plagiarism is the presentation of all or a portion of someone else’s work, as one’s own, without properly citing/documenting the work.  Plagiarism is unacceptable and will result in a failing grade in the course. 

 

5.  Clark Atlanta University Campus Cultural Creed 

Clark Atlanta University is committed to academic excellence, building character, and service to others.  The University will achieve its mission by cultivating an environment of honesty, kindness, mutual respect, self-discipline, school loyalty, trust, academic integrity and communal pride.  As a member of this scholarly community, I make the following pledge:

·              I will work to promote academic honesty and integrity;

·              I will work to cultivate a learning environment which opposes violence, vulgarity, lewdness and selfishness;

·            I will embrace the concept of mutual respect by treating others the way I want them to treat me;

·          I will support a campus culture of diversity by respecting the rights of those whose views and experiences differ from my own;

·            I will honor and care for the sanctity of my body as the temple of God;

·            I will commit myself to service so that I can make a difference in the world and a difference for more than just myself;

·         I will celebrate and contribute to the “spirit of greatness” left by those who preceded me, and I will work to leave this a better place for those who follow me;

As a member of this community, I am committed to conducting myself in ways that contribute to a civil campus environment, which encourages positive behavior in others.  I accept the responsibility to uphold these noble ideals as a proud member of the Clark Atlanta University Family.

 

6.     Attendance

To confirm enrollment, a student must attend each scheduled class within the first two weeks following the official start of the semester.  After this period, a student will not be permitted to enter any class, and the professor will report the student’s nonattendance to the Registrar.  The student will be withdrawn from the class with a grade of “WU” assigned.

  

Students are expected to attend all classes and are responsible for all notes, class assignments and activities whether in class or not.  If a student has an excused absence, he or she must provide documentation and must makeup missed work within one week of absence.  Unexcused absences will result in a grade of zero for missed assignments. 

 

7. Incomplete Policy

An incomplete grade (“I”) is given when a student has been enrolled in a course for an entire semester but has not completed all the requirements.  The “I” is given only when the student has an acceptable excuse for not taking the final examination or for failing to complete other requirements, but does the instructor determine otherwise doing passing work as.  An “I” should be removed by the end of the semester following the one in which the “I” grade was earned, but no later than one year from the end of the semester in which the “I” grade was earned.  Removal of an “I” does not assure a passing grade in the course.  (Undergraduate Academic Regulations and Procedures Handbook for Students)

 

 

Course Outline and Schedule:

 

Week

 

Comment

Class

Reading

T, Th

 

Present

Books/materials

1

Syllabus

 

 

2

Introduction, Overview

 

Chapter1

3

Life Cycle Models

 

Chapter2

4

Software Process

 

Chapter3

5

Project Management and Plan

 

Chapter 4-9/Ref.

6

Requirements

 

Chapter 10

7

Specification

 

Chapter 11

8

Current Technology

 

 

9

Analysis and Design

 

Chapter 12-13

10

UML

 

Ref.

11

Implementation, Project Presentation

 

Chapter 14

12

Integration, Lab

 

Chapter 15

13

Maintenance, Lab

 

Chapter 16

14

Project Due

 

 

15

Presentation, Documentation