CS 491 - Software Engineering                Fall 2013                                 Syllabus

 

Instructor:   Clark B. Archer, PhD.                                      Office:   KHIC 041

                     Professor Emeritus of CSIS                           Office hours:  TR 11:00-12:00, 2:00-3:15.

                                                                                                                          W 9:30-11:30.

 

Texts:  Class notes that are made available on the M: drive.

                                    >>>>>>> References on library reserve:-

Sommerville, Ian.  Software Engineering, 7th Ed.  Addison-Wesley Publishers, 2004.

Archer, Clark. Measuring Object-Oriented Software Products. Software Engineering Institute, 1995.

 

         

Catalog description: A study of software development characterized by a practical, orderly, and   measured development process. The dominant features of this process are requirements specification, software design method selection, software testing, and quality assurance. 

 

Objectives:

·       Acquaint students with the knowledge of how large-scale software products are developed in the industry.  This incorporates the front-end of that sequence of processes.

·       Acquaint students with the industry standards and the software development life cycle.

·       Acquaint students with software quality issues.

·       Acquaint students with requirements gathering and requirements specification.

·       Discuss the specifics of software analysis and design approaches.

 

 

Outline of the course by topic:‑

1.      Overview of Software Engineering  (1.5 wks)   

      a.      A history of software development from 1951 to the present.

b.      NATO and DoD initiatives in the early 1970s 

c.      Failure of past methods of software development to produce reliable and safe software that is produced on time and within budgetary constraints  (by examples)

d.      ACM Code of Ethics . 

 

2.      Software Requirements specification  (includes a brief overview of systems analysis)  (1.5 wks)

         a.   Project planning

      b.      Requirements solicitation – an overview  

c.      Documentation standards – detailed  

d.      Data flow diagrams as a specification method for – detailed

 

3.      Software quality  (1.5 wk).

a.      Viewpoint analysis

b.      Quality standards:  SEI’s Capability Maturity Model  &  ISO 9000 

c.      Quality assurance issues – an overview

d.      Software process as the key to quality.

 

4.      The software development environment -  (1 wk)

     a.  Software configuration management.

b.  Models for software development (Waterfall and Spiral models)

 

 

Test #1  -   September 26 [End  of week #5]  (100 pts)  over topics 1-4.

 

 5.      Software economics   (1.5 wk)   

a.      Software project planning – an overview from a cost perspective

b.      Statistics for software engineers – overview of sampling and simple point estimates

c.      Software cost estimation - The COCOMO model –  detailed. 

 

6.      Software measure  (3 wks).

 a.  Basic statistics for software engineers - linear regression and t tests.

      b.  Software product measures  read  CM-28,  section #9

 c.  Software effort measures

 

7.      Design concepts ( 1.5 wks)   read CM-28 pp 29 - 40.

a.      Procedure-oriented design   read CM-28 section #7

b.      Object-Oriented design  

c.      State-transition diagrams

 

Test #2  November 14 [End of week #12]  (100 pts) over topics 5-7.  {This might be in two parts; one in class and one be completed outside of class individually}

 

8. Issues related to software engineering  (2 wks ) 

      a.   Reliability

b.   Reuse 

c.  Safety  

d.  Ethical and legal environment

e.   Verification and validation 

 

9.  Software research article presentations  (1 wk). Exam is as stated on the campus exam calendar.

    

 

        Course Evaluation:                                            Grading Scale: 

        Mock interview                    20                    

        Attendance                         30*                        A          94-100%          C         73-76

        Presentation                       30                         A-         90-93               C-        70-72

        Projects (3 of these)         120                         B+       87-89               D+       67-69

        Tests(2)                            200                         B          83-86               D         63-66

        Exam                                100                         B-        80-82               D-        60-62

                    Total               500 pts                        C+       77-79               F          0  -59

                                    

Attendance:  Attendance is strongly encouraged ( you are expected to attend at least 85% of all classes).   Tests missed due to an excused absence (usually meaning prior approval of instructor) can be made up.  This equates to  “miss five classes (an excused absence is still an absence - excused allows you to make up the missed activity) and you automatically fail the course.”   *Otherwise, attendance is graded  as 30 – 2X, where X is the number of absences.

 

        Academic honesty:   All assignments must represent the student’s own efforts.  Copying written      assignments or portions of another’s work in any manner from any source, without the explicit      direction/permission of the instructor is a form of plagiarism and will cause the student to receive a          zero for the assignment and possible failure of the course; and the student may be subject to other          punitive actions by the college.

 

Disability: If you are a student with a documented disability who will require accommodations in this course, please meet with Karen Saracusa, Director of Student Accessibility Services, in Room 88 Hoover-Price Campus Center, for assistance in developing a plan to address your academic needs.  Please call (330) 823-7372 to schedule an appointment or e-mail

studentaccessibility@mountunion.edu.  All information shared will remain confidential.

 

        Software Documents:  Deliverables for this course will include:

Each of these documents must be peer-reviewed and reviewed by the course instructor.  Thus, the document must be produced early enough in the software development process to enable meaningful review and modification. 

 

        NOTE: CS 491 is an intensive writing course.

        Criteria for an intensive writing course will be met by the following:

        Criterion 1:  Each student will be required to submit five written documents each of which should         contain at least two pages.  The detailed specification document and the included data dictionary should         contain at least six or more pages. 

        Criterion 2:  Each written document must be peer-reviewed before submission.  Each document will       be reviewed by the instructor who will recommend revisions when necessary. The revised document      will be peer reviewed a second time and resubmitted for evaluation.

        Criterion 3:  Software design documents have standard formats and incorporate some diagrammatic         conventions.  These formats and conventions will be discussed in class.   The Association for     Computing Machinery has a standard bibliographic format to be used for referencing other documents      and reference material.  This format will be discussed in class.

Criterion 4:  Software engineers must be able to read, assimilate, and present research material published by professionals in the discipline.  Students are required to select an article in a professional journal, read it, outline it, and make a presentation to a peer group.