?? http:^^www.cs.uidaho.edu^~billjunk^courses^cs485^cs485.html
字號:
Date: Tue, 26 Nov 1996 19:04:55 GMTServer: NCSA/1.4.1Content-type: text/htmlLast-modified: Thu, 14 Nov 1996 21:22:35 GMTContent-length: 11648<HEAD><TITLE>CS 485/585 Software Process Management </TITLE><HEAD><BODY background="/~billjunk/images/back2.gif"><H1>CS 485/585 SOFTWARE PROCESS MANAGEMENT</H1><H2>Spring 96-97</H2><H2><B><I>Tentative Information</i></b></h2><H3>Lasted updated November 14, 1996</H3><!WA0><IMG Align=middle SRC="http://www.cs.uidaho.edu/~billjunk/images/rainbow.gif"><!WA1><A HREF="http://www.cs.uidaho.edu/index.html"><!WA2><IMG width=28 height=22ALIGN=middle SRC="http://www.cs.uidaho.edu/~billjunk/images/csclogo.gif"></A> Computer Science Home Page<!WA3><A HREF="http://www.uidaho.edu/"><!WA4><IMG width=22 height=22ALIGN=middle SRC="http://www.cs.uidaho.edu/~billjunk/images/uilogo3.gif"></A> Univ. of Idaho Home Page<!WA5><IMG Align=middle SRC="http://www.cs.uidaho.edu/~billjunk/images/rainbow.gif"><H2> Quick links to additional course material:</H2>Not yet implemented<UL><LI><!WA6><A HREF="http://www.cs.uidaho.edu/~billjunk/courses/cs485/schedule.html">Course Schedule</A><LI><!WA7><A HREF="http://www.cs.uidaho.edu/~billjunk/courses/cs485/termproj.html">Term Project Guidelines</A><LI><!WA8><A HREF="http://www.cs.uidaho.edu/~billjunk/courses/cs485/slides.html">Presentation Slides</A><LI><!WA9><A HREF="http://www.cs.uidaho.edu/~billjunk/courses/cs485/assignments.html">Assignments</A><LI><!WA10><A HREF="http://www.cs.uidaho.edu/~billjunk/courses/cs485/references.html">References</A><LI><!WA11><A HREF="http://www.cs.uidaho.edu/~billjunk/courses/cs485/weblinks.html">WWW Links</A></UL><!WA12><IMG Align=middle SRC="http://www.cs.uidaho.edu/~billjunk/images/rainbow.gif"><I><B>Instructor:</B> <!WA13><A HREF="http://www.cs.uidaho.edu/~billjunk/index.html">William S. Junk</A>, Computer Science Dept., University of Idaho, Moscow, ID 83844-1010<BR><B>Telephone:</B> 208-885-7530 / 800-824-2889<BR><B>Fax:</B> 208-885-6165 (alternate: 208-885-9052)<BR><B>E-Mail:</B> <!WA14><a href="mailto:billjunk@cs.uidaho.edu">billjunk@cs.uidaho.edu</a></I><!WA15><IMG Align=middle SRC="http://www.cs.uidaho.edu/~billjunk/images/rainbow.gif"><B>Video Tapes Are Available:</B> The Spring 94-95 offering of the course is available for purchase or rental. The contents of that course are very similar to that described here. Contact <!WA16><A HREF="http://www.uidaho.edu/evo/">EngineeringVideo Outreach</A> at 1-208-885-6373 for more information.<!WA17><IMG Align=middle SRC="http://www.cs.uidaho.edu/~billjunk/images/rainbow.gif"><h3>Course Description</h3> This course will view software engineering activities from a management perspective centering around a study of the software development process. We will view the process in terms of its constituent tasks, focusing on the flow of information and interconnection between tasks. We will highlight interdependencies created by work products. Our approach is in contrast to the traditional software engineering course (such as the prerequisite for this course) which focuses on the techniques employed to accomplish technical activities.<P>Topics to be covered include: software development paradigms (life cycles such as waterfall, evolutionary, incremental, and spiral), software process maturity (Capability Maturity Model and BOOTSTRAP Model), software process assessment and improvement, change management concepts, process and product metrics, organization and management strategies, and risk assessment. Although we will study several management topics, this is not a course in software project management. We will not cover how to manage people and resources. Project management will be discussed only as a constituent tasks in the overall context of producing a software product. Participation in class activities, some individual activities, a term project, and a final exam will be required. Some additional effort will be required for graduate credit.<P><H3>Prerequisites</h3>CS 381/581 Software Engineering or instructor's permission. For NTU students something equivalent to SE-710 or substantial work experience will be considered equivalent. Knowledge of modern software engineering techniques will be assumed.Computer Access: None required, but access to and use of Internet for course material and electronic mail is expected.<p><h3>Goals</h3>The goal of this course is to provide a systematic study of the softwaredevelopment process with an emphasis on how to define and manage it. This course will expose participants to several possible approaches to software development, identify the tasks that are essential for successful projects, discuss how tasks interact with each other, and discuss how an organization can develop and mature its software development process. The course will not advocate a particular development approach, but rather will take a critical look at the most popular and most talked about strategies.<P>After successfully completing this course participants will:<ul><li>be familiar with terminology used in this topical area <li>have read and analyzed important historical and current literature addressing software life cycle models and software process issues<li>understand the basic concepts embodied in the most prevalent software life cycle models, including knowledge of their advantages and disadvantages, and when it may be appropriate to use each life cycle approach<li>be able to construct and represent a software life cycle for an organization or project<LI>be able to construct a project software life cycle that is consistent with a specific software life cycle model<LI>understand the factors that are important in building the capability or maturity of a software development organization<LI>be able to assess the maturity level of a software development organization<LI>understand factors that contribute to successful process change implementation<LI>be able to plan and implement a software process improvement activity</UL><H3>Texts</h3>Mark Paulk, et al., <I><B>The Capability Maturity Model: Guidelines for Improving the Software Process</I></B>, Addison Wesley, 1995.Journal articles of historical or current importance and other material may be provided by the instructor.<P><h3>Alternate Resources</h3>If you are interested in additional information on this subject, the following list presents some resources that you may find useful. For this course you are not required to have access to these resources and a student without access to them will not be at a disadvantage in this course.<P><UL><LI><i><b>Managing the Software Process</i></b>, Watts S. Humphrey, Addison-Wesley, 1989.<LI><i><b>Capability Maturity Model for Software</i></b>, Version 1.1, Mark C. Paulk, et al.,CMU/SEI-93-TR-24, Software Engineering Institute, February 1993.<LI><I><B>Key Practices of the Capability Maturity Model</I></B>, Version 1.1, Mark C. Paulk, etal., CMU/SEI-93-TR-25, Software Engineering Institute, February 1993.<LI><I><B>Software Process Assessment and Improvement: The BOOTSTRAP Approach</I></B>, P. Kuvaja, et al., Blackwell (UK), 1994.<LI> <I><B>IEEE Std 1074 Standard for Developing Software Life Cycle Processes</I></B>, IEEE, 1991.</UL><P><H3>Grading</H3><pre> CS 485 CS 585Participation 10% 10%Outside reading (book) N/A 15%Process Assessment Assignment 15% 15%Process Definition Assignment 15% 15%Individual Project 35% 30%Final Exam 25% 15%</pre><p>Undergraduate and graduate sections of the course are graded separately. Due toslightly different schedules, off-campus and on-campus sections are graded separately.<h3>Participation</h3>All students are expected to make a regular contribution to the class.On-campus students should be prepared to offer their comments regarding material presented, ask interesting questions during class, and respond with good answers to questions asked in class. Calling to my attention a high quality article (not included in the course readings package) on a topic discussed in class is encouraged. Off campus students should communicate with me on a regular basis using telephone, fax, or e-mail to comment on material presented in class, to provide feedback on industry/practitioner perspectives regarding topics studied, relate personal experiences relevant to class discussions, and of course, to ask questions. On-campus students may also make contribution via e-mail. A significant contribution about every other week is considered the minimum satisfactoryparticipation level. A portion of some class session will be devoted to discussion and feedback based on questions and comments supplied from off-campus.<p><h3>Assignments</h3>You will be required to perform a software process assessment and to make a report of your findings. You may evaluate a software development organization with which you are familiar or you may evaluate a case study I will make available. As a practical application of some of the course material you will be expected to develop a process definition/representation of a portion of your work function. This process definition defines the tasks and interfaces with other people and/or organizations.<p> <h3>Outside Reading</h3>Students enrolled for graduate credit (CS 585) will be required to readone book that is related to development life cycles, organizational maturity, or process improvement. A list of acceptable books will be provided.<p><h3>Term Project</h3>The course also requires an approved term project which should be apractical application of some concept(s) studied in the course. The project is expected to be more extensive for graduate students than for undergraduates. For the project you might prepare a Software Management Plan following IEEE standards, develop a software process simulation model of your organization, or study software process metrics from your organization. You are expected to propose a topic and receive my approval before starting. Additional guidelines will be provided on each of these activities.<P>All assignment, projects, etc. should be sent directly to me, not to the Video Outreach Office. The address listed above will work for both US Mail, Federal Express, and UPS.. The final exam must be sent by your examination coordinator to the Video Outreach Office. You will probably want to keep a copy of all work that you submit just in case something gets lost in the mail. Unfortunately this does happen.<P><h3>Course Outline (approximate)</h3><UL><LI>I. Software Life Cycle Paradigms (13 sessions) <UL> <LI>Waterfall Model <LI>Incremental Development Model <LI>Evolutionary Development Model <LI>Object-oriented Model <LI>Maintenance Model <LI>Cleanroom Model <LI>Spiral Model </UL><LI>II. Software Processes, Maturity & Evolution (10 sessions) <UL> <LI>Software Processes <LI>SEI's Capability Maturity Model <LI>The BOOTSTRAP Model <LI>IEEE Standard 1074 <LI>Maturity Evaluation </UL><LI>III. Software Life Cycle Processes (15 sessions) <UL> <LI>Requirements Management <LI>Project Planning & Management <LI>Project Tracking & Oversight <LI>Software Subcontract Management <LI>Software Quality Assurance <LI>Software Configuration Management <LI>Process Definition <LI>Training <LI>Product Engineering <LI>Intergroup Coordination <LI>Peer Review <LI>Process Management <LI>Software Quality Management <LI>Defect Prevention <LI>Risk Analysis & Risk Management <LI>Installation and Support </UL><LI>IV. Change Management (5 sessions)</UL></BODY><!WA18><IMG Align=middle SRC="http://www.cs.uidaho.edu/~billjunk/images/rainbow.gif"><!WA19><A HREF="http://www.cs.uidaho.edu/index.html"><!WA20><IMG width=28 height=22ALIGN=middle SRC="http://www.cs.uidaho.edu/~billjunk/images/csclogo.gif"></A> Computer Science Home Page<!WA21><A HREF="http://www.uidaho.edu/"><!WA22><IMG width=22 height=22ALIGN=middle SRC="http://www.cs.uidaho.edu/~billjunk/images/uilogo3.gif"></A> Univ. of Idaho Home Page <HR><BODY><P><ADDRESS><I>billjunk@cs.uidaho.edu</I></ADDRESS>?? 快捷鍵說明
復制代碼
Ctrl + C
搜索代碼
Ctrl + F
全屏模式
F11
切換主題
Ctrl + Shift + D
顯示快捷鍵
?
增大字號
Ctrl + =
減小字號
Ctrl + -