Главная - Литература

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 [283] 284 285 286 287 288 289 290 291 292 293 294

Metzger, Philip W., and John Boddie. 1996. Managing a Programming Project: Processes and People, 3d ed. Englewood Cliffs, NJ: Prentice Hall, 1996.

Meyer, Bertrand. 1997. Object-Oriented Software Construction, 2d ed. New York, NY Prentice Hall.

Meyers, Scott. 1996. More Effective С++: 35 New Ways to Improve Your Programs and Designs. Reading, MA: Addison-Wesley.

Meyers, Scott. 1998. Effective С++: 50 Specific Ways to Improve Your Programs and Designs, 2d ed. Reading, MA: Addison-Wesley.

Miaria, Richard J., et al. 1983. «Program Indentation and Comprehensibility» Communications of the ACM 26, no. 11 (November): 861-67.

Michalewicz, Zbigniew, and David B. Fogel. 2000. How to Solve It: Modem Heuristics. Beriin: Springer-Verlag.

Miller, G. A. 1956. «The Magical Number Seven, Plus or Minus Two: Some Limits on Our Capacity for Processing Information.* The Psychological Review 63, no. 2 (March): 81-97.

Mills, Hadan D. 1983. Software Productivity. Boston, MA: Little, Brown.

Mills, Harlan D. 1986. «Structured Programming: Retrospect and Prospect.* IEEE Software, November, 58-66.

Mills, Hadan D, and Richard C. Linger. 1986. «Data Structured Programming: Program Design Without Arrays and Pointers.* IEEE Transactions on Software Engineering SE-12, no. 2 (February): 192-97.

Mills, Harlan D., Michael Dyer, and Richard С Linger. 1987. «Cleanroom Software Engineering* IEEE Software, September, 19-25.

Misfeldt, Trevor, Greg Bumgardner, and Andrew Gray. 2004. The Elements ofC- Style. Cambridge University Press.

Mitchell, Jeffrey, Joseph Urban, and Robert McDonald. 1987. «The Effect of Abstract Data Types on Program Development.* IEEE Computer 20, no. 9 (September): 85-88.

Mody, R. P 1991. «C in Education and Software Engineering.* SIGCSE Bulletin 23, no. 3 (September): 45-56.

Moore, Dave. 1992. Private communication.

Moore, James W. 1997. Software Engineering Standards: A Users Road Map. Los Alamitos, CA: IEEE Computer Society Press.

Morales, Alexandra Weber. 2003. «The Consummate Coach: Watts Humphrey, Father of Cmm and Author of Winning with Software, Explains How to Get Better at What You Do,* SD Show Daily, September 16, 2003.

Myers, Glenford J. 1976. Software Reliability. New York, NY John Wiley & Sons.

Myers, Glenford J. 1978a. Composite/Structural Design. New York, NY Van Nostrand Reinhold.

Myers, Glenford J. 1978b. «A Controlled Experiment in Program Testing and Code Walkthroughs/ Inspections.* Communications of the ACM 21, no. 9 (September): 760-68.

Myers, Glenford J. 1979. The Art of Software Testing. New York, NY John Wiley & Sons.

Myers, Ware. 1992. «Good Software Practices Pay Off-Or Do They?* IEEE Software, March, 96-97.

Naisbitt, John. 1982. Megatrends. New York, NY Warner Books.

NASA Software Engineering Laboratory, 1994. Software Measurement Guidebook, June 1995, NASA-GB-001-94. Available from http: sel.gsfc.nasa.gov/website/documents/online-doc/94-102.pdf

NCES 2002. National Center for Education Statistics, 2001 Digest of Educational Statistics, Document Number NCES 2002130, April 2002.

Nevison, John M. 1978. The Little Book of BASIC Style. Reading, MA: Addison-Wesley.



Newcomer, Joseph М. 2000. «Optimi2ation: Your Worst Enemy,» May 2000, unvwflounder. com/ optimizationbtm.

Norcio, A. F. 1982. «Indentation, Documentation and Programmer Comprehension.* Proceedings: Human Factors in Computer Systems, March 15-17, 1982, Gaithersburg MD: 118-20.

Norman, Donald A. 1988. The Psychology of Everyday Things. New York, NY Basic Books. (Also published in paperback as The Design of Everyday Things. New York, NY Doubleday, 1990.)

Oman, Paul and Shari Lawrence Pfleeger, eds. \99в. Applying Software Metrics. Los Alamitos, CA: IEEE Computer Society Press.

Oman, Paul W, and Curtis R. Cook. 1990a. «The Book Paradigm for Improved Maintenance.* IEEE Software, January, 39-45.

Oman, Paul W, and Curtis R. Cook. 1990b. «Typographic Style Is More Than Cosmetic* Communications of the ACM ЪЪ, no. 5 (May): 506-20.

Ostrand, Thomas J., and Elaine J. Weyuker. 1984. «Collecting and Categorizing Software Error Data in an Industrial Environment.* Journal of Systems and Software 4, no. 4 (November): 289-300.

Page-Jones, Meilir. 2000. Fundamentals of Object-Oriented Design in UML. Boston, MA Addison-Wesley

Page-Jones, Meilir. 1988. The Practical Guide to Structured Systems Design. Englewood Cliffs, NJ: Yourdon Press.

Parikh, G., and N. Zvegintzov, eds. 1983. Tutorial on Software Maintenance. Los Alamitos, CA: IEEE Computer Society Press.

Parikh, Girish. 1986. Handbook of Software Maintenance. New York, NY John Wiley & Sons.

Parnas, David L 1972. «On the Criteria to Be Used in Decomposing Systems into Modules.* Communications of the ACM 5, no. 12 (December): 1053-58.

Parnas, David L. 1976. «On the Design and Development of Program Families.* IEEE Transactions on Software Engineering SE-2, 1 (March): 1 -9.

Parnas, David L 1979. «Designing Software for Ease of Extension and Contraction.* IEEE Transactions on Software Engineering SE-5, no. 2 (March): 128-38.

Parnas, David L. 1999. ACM Fellow Profile: David Lorge Parnas,* ACM Software Engineering Notes, May 1999, 10-14.

Parnas, David L, and Paul C. Clements. 1986. «A Rational Design Process: How and Why to Fake It.* IEEE Transactions on Software Engineering SE-12, no. 2 (February): 251-57.

Parnas, David L, Paul C. Clements, and D. M. Weiss. 1985. «The Modular Structure of Complex Systems.* IEEE Transactions on Software Engineering SE-11, no. 3 (March): 259-66.

Perrott, Pamela. 2004. Private communication.

Peters, L J., and L L Tripp. 1976. «Is Software Design Wicked* Datamation, Vol. 22, No. 5 (May 1976), 127-136.

Peters, Lawrence J. 1981. Handbook of Software Design: Methods and Techniques New York, NY Yourdon Press.

Peters, Lawrence J., and Leonard L. Tripp. 1977. «Comparing Software Design Methodologies.* Datamation, November, 89- 94.

Peters, Tom. 1987. Thriving on Chaos: Handbook for a Management Revolution. New York, NY Knopf

Petroski, Henry. 1994. Design Paradigms: Case Histories of Error and Judgment in Engineering. Cambridge, U.K.: Cambridge University Press.

Pietrasanta, Alfred M. 1990. «Alfred M. Pietrasanta on Improving the Software Process.* Software Engineering: Tools, Techniques, Practices 1, no. 1 (May/June): 29-34.



Pietrasanta, Alfred М. 1991a. «А Strategy for Software Process Improvement.* Ninth Anntml Pacific Northwest Sofiware Quality Conference, October 7-8,1991. Oregon Convention Center, Portland, OR

Pietrasanta, Alfred M. 1991b. «Implementing Software Engineering in IBM.» Keynote address. Ninth Annual Pacific Northwest Sofiware Quality Conference, October 7- 8, 1991. Oregon Convention Center, Portland, OR.

Pigoski, Thomas M. 1997. Practical Sofiware Maintenance. New York, NY John Wiley & Sons.

Pirsig, Robert M. 1974. Zen and the Art of Motorcycle Maintenance: An Inquiry into Values. William Morrow.

Plauger, P J. 1988. «A Designers Bibliography* Computer Language, July, 17-22.

Plauger, P J. 1993. Programming on Purpose: Essays on Sofiware Design. New York, NY Prentice Hall.

Plum, Thomas. 1984. С Programming Guidelines. Cardiff, NJ: Plum Hall.

Polya, G. 1957. How to Solve It: A New Aspect of Mathematical Method, 2d ed. Princeton, NJ: Princeton University Press.

Post, Ed. 1983. «Real Programmers Dont Use Pascal,* Datamation, July 1983, 263- 265.

Prechelt, Lutz. 2000. «An Empirical Comparison of Seven Programming Languages,* IEEE Computer, October 2000, 23-29.

Pressman, Roger S. 1987. Sofiware Engineering: A Practitioners Approach. New York, NY: McGraw-Hill.

Pressman, Roger S. 1988. Making Software Engineering Happen: A Guide for Instituting the Technology. Englewood Cliffs, NJ: Prentice Hall.

Putnam, Lawrence H. 2000. «Familiar Metric Management - Effort, Development Time, and Defects Interact.* Downloadable from www.qsm.com.

Putnam, Lawrence H., and Ware Myers. 1992. Measures for Excellence: Reliable Sofiware On Time, Within Budget. Englewood Cliffs, NJ: Yourdon Press, 1992.

Putnam, Lawrence H., and Ware Myers. 1997. Industrial Strength Sofiware: Effective Management Using Measurement. Washington, DC: IEEE Computer Society Press.

Putnam, Lawrence H., and Ware Myers. 2000. «What We Have Learned.* Downloadable from www.qsm.com, June 2000.

Raghavan, Sridhar A., and Donald R. Chand. 1989. «Diffusing Software-Engineering Methods.* IEEE Sofiware, July, 81-90.

Ramsey, H. Rudy, Michael E. Atwood, and James R. Van Doren. 1983. «Flowcharts Versus Program Design Languages: An Experimental Comparison.* Communications of the ACM 26, no. 6 Qune): 445-49.

Ratliff, Wayne. 1987. Interview in Solution System.

Raymond, E. S. 2000. «The Cathedral and the Bzr, www.catb.org/~esr/writings/cathedral-bazaar

Raymond, Eric S. 2004. The Art of Unix Programming. Boston, MA: Addison-Wesley

Rees, Michael J. 1982. «Automatic Assessment Aids for Pascal ?rogr2ims.» ACM Sigplan Notices 17, no. 10 (October): 33-42.

Reifer, Donald. 2002. «How to Get the Most Out of Extreme Programming/Agile Methods,* Proceedings, XP/Agile Universe 2002. New York, NY Springer; 185-196.

Reingold, Edward M., and Wilfred J. Hansen. 1983. Data Structures. Boston, MA: Little, Brown.

Rettig, Marc. 1991. «Testing Made Palatable.* Communications of the ACM 34, no. 5 (May): 25-29.

Riel, Arthur J. 1996. Object-Oriented Design Heuristics. Reading, MA: Addison-Wesley.

Rittel, Horst, and Melvin Webber. 1973. «Dilemmas in a General Theory of Planning* Policy Sciences 4: 155-69.



0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 [283] 284 285 286 287 288 289 290 291 292 293 294



0.0025