|
|
COURSE ID: |
CSC-454 |
|
COURSE NAME: |
Software Engineering |
|
CREDITS: |
3 |
TEXT BOOK (tentative)
Software Engineering, the 8-th edition by
Ian Sommerville; published by Addison Wesley.
INSTRUCTOR INFORMATION
Michele Petrovsky
Office: Room 207, Science
Building
Campus email: mpetrovsky@lincoln.edu
Home email: petrovsky.m@comcast.net
COURSE DESCRIPTION
This course will introduce the student to the principles and techniques involved in the generation of production quality software items. The emphasis will be on the specification, organization, implementation, testing and documentation of software products.
PREREQUISITE CSC-254 (Data Structures)
COURSE GOALS- STUDENT LEARNER OUTCOMES
The student will be able to
- Demonstrate basic skills of software development and knowledge of software life cycle, in both waterfall and non-waterfall approaches
- Create/ analyze end-user software/ system requirements
- Create/ analyze developer software specifications
- Demonstrate and apply knowledge of various software design skills
- Demonstrate understanding of various graphing techniques
- Design software GUI (Graphical User Interface) and software menu-submenu toolbars
- Implement software by coding via programming languages such as Visual Basic, Java, or PHP (client/server, web) and/ or using CASE tools to generate code
- Show basic skills in testing, debugging software and software fault handling and tolerance
- Validate and verify software
- Demonstrate fundamental (software) project management skills
TENTATIVE SCHEDULE OF WEEKLY TEXTBOOK READING ASSIGNMENTS
(WEEK 1-2)
Chapter 1-3: Overview of Software Engineering
. Introduction
. Computer-based system engineering
. Software Processes
(WEEK 3-4)
Chapter 15: Preview of GUI/ Event-driven programming
Object
Oriented and Visual Programming
. Code for menu and toolbar creation/ (CASE) Code
generators
. Introduction to software requirements and
specifications
. Fault tolerance and handling (Chapter 18)
(WEEK 5-7)
Chapter 5-9: Software requirements and Specifications (advanced)
. Software requirements
. Requirements engineering processes
. System models
. Software prototyping
. Formal specification
(WEEK 7-8)
Chapter 4: Project management - Hypothetical proposal writing, project
planning, and scheduling will be applied in final project
Mid term exam (100 points)
Team Software Engineering project due Midterm
(WEEK 9-11)
Chapter 10,11,12,13,15: Design
. Architectural design
. Distributed systems architectures
. Object oriented design
. Real time software design
. User interface design
(WEEK 12-13)
Chapters 16-18 inclusive: More on implementation plus critical systems
. Coding
. Dependability
. Critical systems specification
. Critical systems development
(WEEK 14-15)
Chapter 19-21: Verification and validation
. Verification and validation
. Software testing
. Critical systems validation
FINAL
EXAM (100 points, taken during the official
final exam period)
Completed Team Software Engineering project
due week 15
COURSE ASSESSMENT- LEARNING OPPORTUNITIES*
- Software Engineering Project
The Team Project will “translate” material covered in class into specific design and implementation activities as described immediately below.
The Team Software Engineering Project will consist of the design and implementation, through Linux shell scripts and PHP code, of a set of network security tools and a Graphical User Interface (GUI) for that set of tools.
- Late Work And Make-Ups
All projects and exams must be completed by the scheduled date. Late assignments or make-up tests or quizzes will only be allowed with official documentation and grades may be lowered. To qualify for a make-up, a student must have notified the professor and rescheduled in a timely manner.
GRADING STANDARDS- ASSESSMENT TOOLS
The grades will be evaluated based on the practical and written tests/
quizzes as follows.
|
Average of Two Projects |
45% |
|
Attendance and Class Participation |
10% |
|
Exams |
45% |
The grading scale guideline: **
|
A |
92-100% |
|
A- |
88-91% |
|
B+ |
85-87% |
|
B |
82-84% |
|
B- |
78-81% |
|
C+ |
75-77% |
|
C |
72-74% |
|
C- |
68-71% |
|
D+ |
65-67% |
|
D |
58-64% |
|
F |
0-57% |
UNIVERSITY POLICY
Please note that Ms. Petrovsky will scrupulously enforce the University policies below. No exceptions will be permitted. Pay particular attention to the statements below regarding attendance, plagiarism, cheating, and disruptive conduct.
1) Attendance:
Lincoln University uses the class method of teaching, which assumes that each student has something to contribute and something to gain by attending class. It further assumes that there is much more instruction absorbed in the classroom than can be tested on examinations. Therefore, students are expected to attend all regularly scheduled class meetings and should exhibit good faith in this regard. For the control of absences, the faculty adopted the following regulations:
- Four absences may result in an automatic failure in the course.
- Three tardy arrivals may be counted as one absence.
- Absences will be counted starting with whatever day is specified by the instructor but not later than the deadline for adding or dropping courses.
- In case of illness, death in the family, or other extenuating circumstances, the student must present documented evidence of inability to attend classes to the Vice President for Student Affairs and Enrollment Management. However, in such cases the student is responsible for all work missed during those absences.
- Students representing the University in athletic events or other University sanctioned activities will be excused from class (es) with the responsibility of making up all work and examinations. The Registrar will issue the excused format to the faculty member in charge of the off- or on-campus activity for delivery by the student(s) to their instructors.
2) Statement on Academic Integrity:
Students are responsible for proper conduct and integrity in all of their scholastic work. They must follow a professor's instructions when completing tests, homework, and laboratory reports, and must ask for clarification if the instructions are not clear. In general, students should not give or receive aid when taking exams, or exceed the time limitations specified by the professor. In seeking the truth, in learning to think critically, and in preparing for a life of constructive service, honesty is imperative. Honesty in the classroom and in the preparation of papers is therefore expected of all students. Each student has the responsibility to submit work that is uniquely his or her own. All of this work must be done in accordance with established principles of academic integrity.
An act of academic dishonesty or plagiarism may result in
failure for a project or in a course. Plagiarism involves representing
another person's ideas or scholarship, including material from the Internet, as
your own. Cheating or acts of academic dishonesty include (but are not
limited to) fabricating data, tampering with grades, copying, and offering or
receiving unauthorized assistance or information.
3) The Student Conduct Code:
Students will be held to the rules and regulations of the Student Conduct Code as described in the Lincoln University Student Handbook. In particular, excessive talking, leaving and reentering class, phones or pagers, or other means of disrupting the class will not be tolerated and students may be asked to leave. Students who constantly disrupt class may be asked to leave permanently and will receive an F.
4) The Core Curriculum Learner Competencies:
All courses offered through the Department of Mathematics and Computer Science require students to meet at least the following out of the 8 Core Curriculum Learner Competencies:
(1) Listen
and effectively communicate ideas through written, spoken, and visual means;
(2) Think critically via classifying, analyzing, comparing, contrasting,
hypothesizing, synthesizing, extrapolating, and evaluating ideas;
(6) Apply and evaluate quantitative reasoning through the disciplines of
mathematics, computational science, laboratory science, selected social
sciences and other like-minded approaches that require precision of thought;
(8) Demonstrate positive interpersonal skills by adhering to the principles
of freedom, justice, equality, fairness, tolerance, open dialogue and concern
for the common good.
Note:
* The instructor of a given section of the course may make some
modifications to the evaluation as well as to the rest of the syllabi
including but not limited to; the grade weights, number of tests, and test
total points. In case of a textbook change, the chapter assignments will be
adjusted.
**The gradig scale guideline includes a 2-point flexibility.
|
Lincoln University of the Commonwealth
of Pennsylvania |
|
|