Nature of Course
The primary objective of the USC software engineering education program is to perpare students for leadership careers in the field. Good software engineering leadership requires an understanding of three major areas: software technology, economic factors, and human relations. This course assumes that you have a good background in software technology, and concentrates on the economic and human factors and shows how they interplay with software factors.
The course focuses on a set of pervasive management and economic paradigms which are highly valuable software engineering tools: teambuilding, empowerment, continuous process improvement, business case analysis, win-win situations, production functions, economies of scale, present value, constrained optimization, risk and decision analysis, etc. It does this in the context of new software challenges (rapid development, rapid change, COTS integration, talent shortages) and new approaches to the software process, including process maturity models, Theory W, the Spiral Model, Model-based (System) Architectecting and Software Engineering (MBASE), and software risk management. These are all integrated into a framework of Value-Based Software Engineering (VBSE).
VBSE and its MBASE/WinWin Spiral process integrate economics and human factors into software development through the fundamental concept of reconciling stakeholder value propositions into a win-win shared vision of the products to be developed and the process for developing them. A software project's success-critical stakeholders generally include users, acquirers, developers, and maintainers; and may also include marketers, venture capitalists, operators, and representatives of the general public.
Theory W project management is based on the fundamental principle that the project manager's principal objective is to Make Everyone a Winner (customers, subordinates, bosses, users, maintainers). The course elaborates this principle into a stakeholder value-based approach which focuses on techniques for creating win-win conditions, negotiation, expectations management, and conflict resolution.
Software risk management is one of the primary Theory W elements: identifying and managing win-lose or lose-lose project risks. It is also the driver of the Spiral Model. The course will cover the discipline of software risk management under six primary sub-topics: risk identification, risk analysis, risk prioritization, risk management planning, risk resolution, and risk monitoring. This course offers opportunities to practice skills through several case studies. As students' careers will span many generations of software technology and practices, some case studies will provide practice in learning how to learn about new technologies and practices.
500 points: Homework exercises. Due dates are indicated in the Course Schedule. Assignments are due at 12 noon on the day indicated, in hardcopy in the box outside SAL339. Please do not submit softcopy for on campus students. A 15% per day penalty will apply for all late submissions.
Distance Education Network (DEN)students: please submit your homework through DEN and we will pick up your homework from DEN. Please contact DEN about the homework submission procedures or visit http://den.usc.edu/help/documentcenter.htm
200 points: Midterm Exams: 9/23(Friday) and 10/26(Wednesday). 100 points each; based on lecture, homework, and reading material covered through the previous class session. Open book; bring a hand calculator with an x^y key, but no laptops or palmtops.
300 points: Final Exam: 12/7(Wednesday). Covering the full range of course material, but focused on topics covered in lectures and homeworks. Open book; bring at least textbooks and a hand calculator with an x^y key, but no laptops or palmtops.
Asking Questions
To get your questions answered quickly, please follow the steps below (in order):
1. Check the hot course FAQ list - we will maintain a question/answer list and update it on a daily basis. All good or popular questions will be posted there with answers.
2. Send one of the TAs an email and CC the other TA at the same time. Please include 510 keyword in your email title - If you cannot find the answer to your question in the FAQ, please feel free to send emails to TAs.
3. If TAs cannot answer your question, please try to speak with the related course instructor after class or during his office hour, or contact him through email.
Regrading
All homework submissions are final. No modifications are allowed after submission. You will have exactly 2 weeks right after the date when each homework is returned to the class, to come to the TA's office hour to discuss your regrading requests. Any request after that will not be accepted. This policy also applies to midterm and final exams.
Abut Plagiarism (using other people's work without crediting them). Minor first offenses: You lose ONE grade level (e.g., B+ instead of A-). Second offenses and major first offenses: You get an F for the course.