| Overview | Grading Criteria | Schedule | Study Questions | References |
[CP] Clements, Paul, Parnas, David. A Rational Design Process: How and Why to Fake It.
[Easterbrook+96] Easterbrook, Steve, et al. Experiences Using Formal Methods for Requirements Modeling, NASA IV&V Facility, http://research.ivv.nasa.gov/~steve/papers/index.html.
[Ivers+] Ivers, James, Melton, Ralph, Bigelow, Elizabeth, Allen, Robert, Garlan, David. Z and NP HLA Model, Released as CMU Technical Report
[Jackson94] Jackson, Daniel. Structuring Z Specifications with Views. ACM Transactions on Software Engineering and Methodology, Vol. 4, No. 4, October 1994. http://www.cs.cmu.edu/afs/cs.cmu.edu/user/dnj/pub/www/home.html
[Jackson+96] Jackson, Daniel, Jackson, Michael. Problem Decomposition for Reuse. Software Engineering Journal, Vol. 11, No. l, January 1996. http://www.cs.cmu.edu/afs/cs.cmu.edu/user/dnj/pub/www/home.html
[Jackson95a] Jackson, Daniel, Damon, Craig. Semi-executable Specification. CMU School of Computer Science Tech Report 95-216, Pittsburgh, PA, November 1995. http://www.cs.cmu.edu/afs/cs/project/nitpick/www/pubs.html
[Jackson95b] Jackson, Michael. Software Requirements & Specifications. Addison-Wesley: Harlow, England, 1995.
[Jacobson+99] Jacobson, Ivar, Booch, Grady, Rumbaugh, James. The Unified Software Development Process. Addison-Wesley: Reading, Massachusettes, 1999.
[Janicki+94] Janicki, Ryszard; Parnas, David; Zucker, Jeffrey. Tabular Representations in Relational Documents. Relational Methods in Computer Science, Wadem, Germany. Schloss Dagstuhl, 184-196:1994
[Liskov87] Liskov, Barbara. Data abstraction and hierarchy. Proc. Object-oriented Programming Systems, Languages and Applications, Orlando, FL, Oct.1987, pp. 17-34
[Liskov+75] Liskov, Barbara H., Zilles, Stephen N. Specification techniques for data abstraction. IEEE Transactions on Software Engineering. Vol. SEI, No. 1, March 1975.
[Loy89] Loy, Patrick. A Comparison of Object-Oriented and Structured Development Methods. Software Engineering Notes, 15:1, January 1990.
[Mills+87] Mills, Harlan, Dyer, Michael, Linger, Richard. Cleanroom Software Engineering. IEEE Software, September 1987.
[Place+90] Place, Patrick, Wood, William, and Tudball, Mike. Survey of Formal Specification Techniques for Reactive Systems. CMU/SEI-90-TR-5.
[Parnas72] Parnas, D. L. On the criteria to be used in decomposing Systems into modules. Communications of the ACM, vol.12, no. 15, pp.1053-1058, 1972.
[Parnas78] Parnas, D. L. Software Requirements of the A-7E Aircraft. Naval Research Laboratory.
[Robillard99] Robillard, Pierre N. The Role of Knowledge in Software Development. Communications of the ACM, Vol. 42, No. 1, pp. 87-92, 1999.
[Rumbaugh+91] Rumbaugh, James, et al. Chapter 4 of Object-Oriented Modeling and Design. Prentice Hall: Englewood Cliffs, NJ 1991.
[Rumbaugh94] Rumbaugh, James. Getting Started: Using Use Cases to Capture Requirements, Journal of Object-Oriented Programming, September 1994, pp. 8-12, 23
[STARS] IBM Federal Sector Division. Software Technology for Adaptable, Reliable Systems (STARS) Program, 1991
[Trammell+92] Trammell, Carmen, Binder, Leon, Snyder, Catherine. The Automated Production Control Documentation System: A Case Study in Cleanroom Software Engineering. ACM Transactions on Software Engineering and Methodology. Vol. 1 No. 1, pp. 81-94. January 1992.
Web Publications:
[Rising] Rising, Linda. Patterns: A Way to Reuse Expertise. http://www.agcs.com/patterns/expertise.htm
[Duell] Duell, Michael. Non-Software Examples of Software Design Patterns. http://www.agcs.com/patterns/papers/patexamples.htm
Rational Rose Web site: http://www.rational.com/products/rose/index.jtmpl
Software Technology for Adaptable, Reliable Systems (STARS) Program Web site: http://source.asset.com/stars/
ASSET Cleanroom Software Engineering Web site: http://www.asset.com/WSRD/indices/domains/CLEANROOM_SOFTWARE_ENGINEERING.html