CTC 310 Software Project Management

Transcription

1 Instructor Jack Han WEEK LECTURE Assignment/Project WEEK 1 I t d ti C i t d ti P j t R dr f K CTC 310 Software Project Management CATALOG DESCRIPTION: This 3-credit course will focus on the critical aspects of project management, including software project management concepts and case studies, and discuss software project management roadmap, and especially address linear, incremental, iterative, adaptive, and extreme effective software project management from the perspectives of project scoping, planning, launching, monitoring, controlling and closing phases. PRE-REQUISITE: CSC301 TEXTBOOKS: Effective Software Project Management, by Robert K. Wysocki, John Wiley and Sons, 2006, ISBN: REFERENCES: Requirements and Analysis for Secure Software See Architecture and Design Requirements for Secure Software See Software Security Testing See Key Practices for Mitigating the Most Egregious Exploitable Software Weaknesses See Software Assurance in Acquisition and Contract Language See

2 COURSE GOALS: Understand how and why software development must be planned on a certainty-to-uncertainty continuum Categorize your projects on a four-quadrant model Learn when to use each of the five SDPM strategies--linear, Incremental, Iterative, Adaptive, and Extreme Explore the benefits of each strategic model and what types of projects it supports best Recognize the activities that go into the Scoping, Planning, Launching, Monitoring, Controlling, and Closing phases of each strategy (and the role of Internal or External Auditors in these processes.) Apply this knowledge to the specific projects you manage Get a clear picture of where you are and how to get where you want to go (Awareness of external Information and resources on Best Practices and Lessons learned in this field) STUDENT LEARNING OUTCOMES: Upon completing this course students will be able To demonstrate the knowledge regarding the software project management; To include the ability of software project management in the process of software development; To expose the skills of presentation and effective communication with project team members (and internal or external reviewers (IT Auditors, IT Security, DOD Contract Managers, GAO, Management, etc.) To exhibit a heighten level of competencies in the use of software project management and leadership. To identify available resources and guidance on this subject ATTENDANCE POLICY California State University, Dominguez Hills requires regular class attendance. Excessive absences will result in lowered grades. Excessive absenteeism, whether excused or unexcused, may result in a student s course grade being reduced or in assignment of a grade of F. Absences are accumulated beginning with the first day of class. Very Important Note: Attendance is expected and required. The student is responsible for materials missed during an absence, whether excused or not. Excessive absences or tardiness will result in lowered grades. A sign-in sheet will be put in the class room entrance. YOU MUST CHECK-IN EACH CLASS. STUDENT ACADEMIC APPEALS PROCESS Authority and responsibility for assigning grades to students rests with the faculty. However, in those instances where students believe that miscommunication, error, or unfairness of any kind may have adversely affected the instructor s assessment of their academic performance, the student has a right to appeal by the procedure listed in the Undergraduate Catalog and by doing so within thirty days of receiving the grade or experiencing any other problematic academic event that prompted the complaint.

3 ADA STATEMENT Students with disabilities, who believe they may need an academic adjustment in this class, are encouraged to contact Disabled Student Services as soon as possible to better ensure receipt of timely adjustments. ACADEMIC INTEGRITY Academic integrity is of central importance in this and every other course at CSUDH. You are obliged to consult the appropriate sections of the University Catalog and obey all rules and regulations imposed by the University relevant to its lawful missions, processes, and functions. All work turned in by a student for a grade must be student ' own work. Plagiarism and cheating (e.g. stealing or copying the work of others and turning it in as your own) will not be tolerated, and will be dealt with according to University policy. The consequences for being caught plagiarizing or cheating range from a minimum of a zero grade for the work you plagiarized or cheated on, to being dropped from the course. COURSE POLICIES: This course uses the lecture format. Reading, projects and homework will be assigned, and all problems will be graded. It is expected that you will need to spend at least one hour studying outside the class for each hour spent in the class. That means you should plan to devote a minimum of six (6) hours per week for this class (3-hours in class, 3-hours outside class). Note taking is very important in this course and students are asked to keep an organized notebook. A notebook will help you to organize your work for easy access when preparing for tests. HOMEWORK ASSIGNMENTS Please be aware that all homework assignments must be handed to the instructor in person and in class. The computer-print out homework is preferable, but handwriting is also acceptable. However, it is the student s responsibility to make your writing clear enough for the instructor to grade. Do not slide any homework under the office door. PROJECT ASSIGNMENTS The standards for submission of projects will be made available per project assignment. Each project should be presentable and submitted with a cover sheet. Reports should include name of the student, section number, instructor, and class meeting time. Homework and projects will be handed out ONE week before the due day. LATE HOMEWORK/PROJECTS:

4 All assignments are due near the end of class on the scheduled dates. NO LATE ASSIGNMENT WILL BE ACCEPTED. MID-TERM TEST/MISSED TEST: Two midterm tests will be given. The test material that does not appear in the textbooks will be presented in lectures. Students are responsible for the additional materials that will be presented in the class. Missed midterm tests may not be made up unless the students are supported by documentations acknowledged by the university for an excuse.. GRADING SCALE: = A = A = B = B 80-82=B77-79=C =C 70-72=C67-69=D =D below 60 = F EVALUATION TECHNIQUES: Attendance % Homework % Project % Mid-term % Presentation % TOTAL 100% TOPIC OUTLINE (Will be conducted according to the following. However, the schedule of the topics or timetable may be varying slightly) Instructor Jack Han WEEK LECTURE Assignment/Project WEEK 1 Introduction Course introduction Project management introduction (Lessons from Industry read references (1) Key Practices for Mitigating the Most Egregious Exploitable Software Weaknesses and (2) Software Assurance in Acquisition and Contract Language) Read Reference Key Practices for Mitigating the Most Egregious Exploitable Software Weaknesses and Software Assurance in Acquisition and Contract Language WEEK 2 Software Development Process and Roadmap (Please read reference Requirements and Analysis for Secure Software) HW #1 and (Please read reference Requirements and Analysis for Secure Software) WEEK 3 Project management functions: controlling, 1. HW#2 and (

5 Instructor Jack Han WEEK LECTURE Assignment/Project WEEK 1 Introduction Course introduction Project management introduction (Lessons from Industry read references (1) Key Practices for Mitigating the Most Egregious Exploitable Software Weaknesses and (2) Software Assurance in Acquisition and Contract Language) Read Reference Key Practices for Mitigating the Most Egregious Exploitable Software Weaknesses and Software Assurance in Acquisition and WEEK 2 WEEK 3 Software Development Process and Roadmap (Please read reference Requirements and Analysis for Secure Software) Project management functions: controlling, directing, authority, leadership, life-cycle, review meeting ( Please read reference Architecture and Design Considerations for Secure Software) WEEK 4 Linear Effective Software Project Management: Strategy, Scoping, Planning, and Launching WEEK 5 Linear Effective Software Project Management: Monitoring, Controlling and Closing WEEK 6 Incremental Effective Software Project Management: Strategy, Scoping, Planning, and Launching WEEK 7 MIDTERM #1 WEEK 8 Incremental Effective Software Project Management: Monitoring, Controlling and Closing Contract Language HW #1 and (Please read reference Requirements and Analysis for Secure Software) 1. H W #2 and ( Please read reference Architecture and Design Consideratio ns for Secure Software) HW #3 PROJECT #1 PROJECT #2 HW #4 WEEK 9 Iterative Effective Software Project Management: Strategy, Scoping, Planning, and Launching WEEK 10 Iterative Effective Software Project Management: Monitoring, Controlling and Closing WEEK 11 Adaptive Effective Software Project Management: Strategy, Scoping, Planning, and Launching WEEK 12 Adaptive Effective Software Project Management: Monitoring, Controlling and Closing (Interfacing with Internal or External Reviewers (Auditors, Management, Government Regulators, Consultants, etc. Their Role in the Process) WEEK 13 Case studies WEEK 14 MIDTERM #2 WEEK 15 Summary: Where are we? Where do you want to go? How can you get there HW #5 PROJECT #3 PROJECT #4

6 Instructor Jack Han WEEK LECTURE A i t/p j t