Software Engineering Principles

Bachelors Degree in Computer Systems & Information Technology

CS 350

Breyer State University

Instructor: Bryan I. Jensen, MSCIS, BSCIS.

SYLLABUS

COURSE OVERVIEW: Welcome to Software Engineering Principles, a Bachelor Level course in the curriculum for the Degree, Bachelor in Computer Systems and Information Technology. I am pleased to instruct you in this course, which will be a foundational course for the remainder of your studies in the bachelor program.

This course is organized so as to, first, provide a general introduction to software development and identify the important phases of any software project. Then, each of the phases is examined in detail, in order to give the reader a picture of the current state of our understanding of software development.

I know you will enjoy this course. Please learn as much as you can as you progress through it, as it does lay down a solid foundation for the rest of the curriculum. It is my pleasure to have you in the course.

TIME FRAME: This is a five-semester hour course. This course is allotted 10 weeks of time. You must complete all of the requirements for the course successfully by the end of the 10-week period. The first day of week one will begin the day that you register for the course, or the day which you notify me that your textbooks have arrived and you are ready to begin your studies. Please be cognizant of the time frame. It is rare that extensions of time are permitted, unless you have good justification. Upon successful completion of this course, you will be awarded five semester hours of credit.

TEXTBOOKS: There one required book for this course.

Book 1: Software Engineering: Theory and Practice, Second Edition. Shari Lawrence Pfleeger. 2001: ISBN # 131469134.

You can order your book from:

	» Click Here to Enter
» Additional Student Resources at StudyTactics

EXAMINATIONS: There are two examinations for this course, a mid-term exam and a final exam. The mid-term exam covers the material in the book to Chapter 6. The final exam covers the material in the book from Chapter 7 - 14.

The mid-term examination must be taken by the end of the 5th week in the course.

The final examination must be taken by the end of the 10th week in the course.

Both exams are programmed and are located in the classroom for this course. The examinations are "open book" objective type. You will have one (1) day to complete your exam, once you access it from the classroom. To access the exam, you must send me an email and request to have access to the exam. Upon registration, you will receive your email address. I will then program your access in. You will receive an email back from me telling you that you are now authorized to go ahead and to access your exam. To access, you will come into the classroom, click on testing, and click on the exam you are taking. You will need your User ID and PASS WORD to access the exam. The exam will appear on your screen. Once you access the exam, you have 24 hours to submit your answers. The program provides me the exact date and time that you accessed the exam. The program also notifies me of the exact date and time that you submitted your answers. Thus, the program is timing you. When you are ready, go back into the classroom and click in your responses and then click submit. Shortly, you will receive the exam in your email box with your computed score. You will also know what questions, if any, that you missed, and what the correct answer is. I also receive a copy of your exam and your score.

GRADING: The grading scale for this course is as follows:

8 Homework assignments @ 5 points each: 40 points

Mid Term Exam: 30 points

Final Exam: 30 points

90-100 % = A

80-89 % = B

70-79 % = C

Below 70% = Fail

COMMUNICATION: You are encouraged to communicate with me. I am available as a teacher, coach, and mentor to assist you in meeting your goals for this course. Primarily, communication is through email. However, I am also available for conversation by telephone if you would like. Our classroom for this course has a "chat" room. I am also very willing to meet with you one-on-one in the chat room at your request. From time to time, depending on how many students are enrolled in this course at a particular time, we will have some scheduled group chats. You will receive more detailed information at the time such chat sessions are scheduled. Please keep my email address handy so that you can contact me whenever necessary. If at any time during this course you change your email address, please be sure to notify me right away.

WRITTEN ASSIGNMENTS: There are written assignments for this course that need to be done and submitted to me via e-mail. There is a considerable amount of reading involved in this course, and I would prefer you spend your time with the books learning the material and using the software that came with your textbook. I do not accept late assignments without prior coordination. Late assignments are counted as a zero grade.

ABOUT YOUR INSTRUCTOR: I, Bryan Jensen, MSCIS, BSCIS., currently teach undergraduate and courses online at Breyer State University . I hold a degree in Masters in Computer Information Systems and a Bachelor of Science in Computer Information Systems. I have 11 years experience in the military as a communications officer and have worked for various large defense contractors such as Northrop Grumman and SAIC.

COURSE OBJECTIVES: The objectives for this course are:

1). What is encompassed by the field of study within computer science known as "software engineering." Your understanding of this field should include its past contributions, a sense of what is understood today about software development, and an overview of important and promising areas of future research.
2). What it means to be a software engineer:
   a). What kinds of activities are necessary for the production of a software system;
   b). What the relationship with the customer should be like, and when to involve the customer in the software development process to ensure that the system meets his or her needs;
   c). What the relationship with other members of the development team should be like, in order to achieve the complex, collaborative tasks that are necessary for developing large systems.
3). What it means to be a software engineering researcher:
   a). What kind of working relationship is needed with practitioners;    b). What types of research problems are of interest to researchers, and stand to give practical benefit to practitioners;
   c). A general idea of how software engineering research is done.
4). What is meant by a "software life-cycle":
   a). What the important phases of software development are, and why each is necessary;
   b). What types of intermediate products are produced in each phase;
   c). How the phases relate to each other and to the finished product;    d). What type of activities a software engineer must complete in each phase.
5). Particular techniques and tools that have been applied to software development, and the circumstances under which they may be more or less appropriate.
6). How software projects are planned and managed:
   a). What types of resources are involved in software development projects;
   b). How risks are identified and assessed;
   c). How predictions and assessments are made.
7). How software process improvement can be achieved. You should also have an understanding of the role of empirical studies in process improvement, including the general types of empirical studies and the kinds of answers each is able to give to software problems.

Apply	Pay Online	Refund Policy
Payment Plan	Email for Info	Register for a Course