COSC 565/475: Software Engineering I
Fall Semester 2009 Course Information Instructor:
Dr. Sharad
Sharma E-MAIL: ssharma@bowiestate.edu CLASS
HOURS:Wednesday:
4:55 PM to 7:25PM, CSB 312 |
 |
Required Text
Braude, Eric J. (2001). Software Engineering An Object-Oriented Perspective, John Wiley & Sons, Inc., ISBN 0-471-32208-3.
Reference Book(s):
COURSE DESCRIPTION
This course introduces
the student to major topics in software engineering such as: requirements
specification, analysis and design, testing, project management, and implementation.
Additional topics such as software life cycle models, the Unified Modeling
Language (UML), agile software development techniques, configuration management,
change control, and project documentation will be discussed.
Prerequisite: COSC 214 or COSC 504
Course Related Links
* Syllabus
* Coding Style
* Assignments
Source Code for Encounter Video game
ENCOUNTER TEST EVALUATION REPORT
Weekly Time Schedule
| Date | Topics | Chapters | Assignments |
| 02-Sep |
Introduction |
Chapter 1 | |
| 09-Sep |
Process |
Chapter 1 | |
| 16-Sep |
Project Management. |
Chapter 2 | |
| 23-Sep |
Requirements Analysis I. |
Chapter 3 | |
| 30-Sep |
Requirements Analysis II |
Chapter 4 | Project Proposal |
| 7-Oct |
Software Architecture |
Chapter 5 | Quiz 1 |
| 14-Oct |
Detailed Design |
Chapter 6 | |
| 21-Oct |
Mid
Term Exam
|
|
|
| 28-Oct |
Unit Implementation. |
Chapter 7 | |
| 4-Nov |
Unit Implementation. |
Chapter 7 | |
| 11-Nov |
Unit Testing |
Chapter 8 | |
| 18-Nov |
Unit Testing |
Chapter 8 | Quiz 2 |
| 25-Nov |
System Integration, Verification, and Validation |
Chapter 8 | |
| 02-Dec |
System Integration, Verification, and Validation |
Chapter 9 | |
| 09-Dec |
Object Oriented Design |
Chapter 9 | |
| 16-Dec |
Final
Exam
|
|
STUDENT EXPECTED OUTCOMES: Upon completion of this course, the student will be able to:
- Analyze and developthe role and responsibilities of a software engineer Assess project management and its role in systems planning, systems analysis, systems design, systems implementation, and systems supportAnalyzeand develop a feasibility plan, requirements and design documentationSynthesis and perform data modeling and process modeling, and explain why they are important,Design, develop, test, and demonstrate a major piece of software.Develop and produce software process artifacts, most importantly the code and user documentation.
- Whether adapt a process to your needs and select an appropriate set of best practices that will guide you in completing a software development project.
EVALUATION: Following is the Evaluation system for the Final Grade. Each assignment will be graded. Students are responsible for completing them as scheduled.
- Two Assignments 20%
- Quizzes (2) 10%
- Mid-Term Exam 20%
- Final Exam 20%
- Final Project 30%
Final Project, Mid-term and Final exams are mandatory.
Assignments: One assignment given prior to the mid-term exam will involve topics: Software Process Project Management, Requirements Analysis, and Software Architecture. One assignment given after the mid-term exam will involve topics: Unit Implementation, Unit testing, System Integration, Verification, and Validation.
Final Project: The purpose of the course project is to provide the students with the knowledge of software engineering methodology and the skills to apply it. The project consists of two iterations, both focused around the same software product. The first iteration is exploratory and represents the first attempt at developing the proposed software product. The second iteration is development and also includes revision of the project goals. The deliverables for the first and second iteration are reports and demos.
GRADING: Academic dishonesty will result in grade F. The following grade scale will be used:
90 % - 100% = A
80 % - 89% = B
70 % - 79% = C
60 % - 69% = D
0 - 59% = F
Final grades will be computed based upon credits earned for all the five components mentioned above.
USEFUL LINKS