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

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

Robertson, Suzanne, and James Robertson, 1999. Mastering the Requirements Process. Reading, MA: Addison-Wesley.

Rogers, Everett M. 1995. Diffusion of Innovations, 4th ed. New York, NY The Free Press.

Rombach, H. Dieter. 1990. «Design Measurements: Some Lessons Learned* IEEE Software, March, 17-25.

Rubin, Frank. 1987. «GOTO Considered Harmful Considered Harmful.* Letter to the editor. Communications of the ACM 30, no. 3 (March): 195-96. Follow-up letters in 30, no. 5 (May 1987): 351-55; 30, no. 6 Qune 1987): 475-78; 30, no. 7 QuXy 1987): 632-34; 30, no. 8 (August 1987): 659-62; 30, no. 12 (December 1987): 997, 1085.

Sackman, H., W.J. Erikson, and E. E. Grant. 1968. «Exploratory Experimental Studies Comparing Online and Offline Programming Performance.* Communications of the ACM 11, no. 1 (January): 3-11.

Schneider, G Michael, Johnny Martin, and W. T. Tsai. 1992. «An Experimental Study of Fault Detection in User Requirements Documents,* ACM Transactions on Software Engineering and Methodology, vol 1, no. 2, 188-204.

Schulmeyer, G. Gordon. 1990. Zero Defect Software. New York, NY McGraw-Hill.

Sedgewick, Robert. 1997. Algorithms in C, Parts 1-4, 3d ed. Boston, MA: Addison-Wesley.

Sedgewick, Robert. 2001. Algorithms in C, Part 5, 3d ed. Boston, MA: Addison-Wesley.

Sedgewick, Robert. \99S. Algorithms in С++, Parts 1-4, 3d ed. Boston, MA: Addison-Wesley.

Sedgewick, Robert. 2002. Algorithms in С++, Part 5, 3d ed. Boston, MA: Addison-Wesley.

Sedgewick, Robert. 2002. Algorithms in Java, Parts 1-4, 3d ed. Boston, MA: Addison-Wesley.

Sedgewick, Robert. 2003. Algorithms in Java, Part 5, 3d ed. Boston, MA: Addison-Wesley.

SEI 1995. The Capability Maturity Model: Guidelines for Improving the Software Process, Software Engineering Institute, Reading, MA: Addison-Wesley, 1995.

SEI, 2003. «Process Maturity Profile: Software CMM®, CBA IPI and SPA Appraisal Results: 2002 Year End Update,* Software Engineering Institute, April 2003.

Selby, Richard W., and Victor R. Basili. 1991. «Analyzing Error-Prone System Structure.* IEEE Transactions on Software Engineering SE-17, no. 2 (February): 141-52.

SEN 1990. «Subsection on Telephone Systems,* Software Engineering Notes, April 1990, 11-14.

Shalloway, Alan, and James R. Trott. 2002. Design Patterns Explained. Boston, MA: Addison-Wesley.

Sheil, B. A. 1981. «The Psychological Study of Programming.* Computing Surveys 13, no. 1 (March): 101-20.

Shen, Vincent Y, et al. 1985. «Identifying Error-Prone Software-An Empirical Study.* IEEE Transactions on Software Engineering SE-11, no. 4 (April): 317-24.

Sheppard, S. В., et al. 1978. «Predicting Programmers Ability to Modify Software.* TR 78-388100-3, General Electric Company, May.

Sheppard, S. В., et al. 1979. «Modern Coding Practices and Programmer Performance.* IEEE Computer 12, no. 12 (December): 41-49.

Shepperd, M., and D. Ince. 1989. «Metrics, Outlier Analysis and the Software Design Process.* Information and Software Technology 31, no. 2 (March): 91-98.

Shirazi, Jack. 2000. Java Рефгтапсе Tuning. Sebastopol, CA: OReilly & Associates.

Shlaer, Sally, and Stephen J. Mellor. 1988. Object Oriented Systems Analysis-Modeling the World in Data. Englewood Cliffs, NJ: Prentice Hall.

Shneiderman, Ben, and Richard Mayer. 1979. «Syntactic/Semantic Interactions in Programmer Behavior: A Model and Experimental Results.* International Journal of Computer and Information Sciences 8, no. 3: 219-38.



Shneiderman, Ben. 1976. «Exploratory Experiments in Programmer Beh2vior.» International Journal of Computing and Information Science 5: 123-43-

Shneiderman, Ben. 1980. Software Psychology: Human Factors in Computer and Information Systems. Cambridge, MA: Winthrop.

Shneiderman, Ben. 1987. Designing the User Interface: Strategies for Effective Human-Computer Interaction. Reading, MA: Addison-Wesley.

Shull, et al. 2002. «What We Have Learned About Fighting Defects,* Proceedings, Metrics 2002. IEEE; 249-258.

Simon, Herbert. 1996. The Sciences of the Artificial, 3d ed. Cambridge, MA: MIT Press.

Simon, Herbert. The Shape of Automation for Men and Management. Harper and Row, 1965.

Simonyi, Charies, and Martin Heller. 1991. <The Hungarian Revolution.* BYTE, August, 131-38.

Smith, Connie U., and Lloyd G. Williams. 2002. Performance Solutions: A Practical Guide to Creating Responsive, Scalable Software. Boston, MA: Addison-Wesley.

Software Productivity Consortium. 1989. Ada Quality and Style: Guidelines for Professional Programmers. New York, NY Van Nostrand Reinhold.

Soloway, Elliot, and Kate Ehrlich. 1984. «Empirical Studies of Programming Knowledge. > IEEE Transactions on Software Engineering SE-10, no. 5 (September): 595-609.

Soloway, Elliot, and Sitharama Iyengar, eds. 1986. Empirical Studies of Programmers. Norwood, NJ: Ablex.

Soloway, Elliot, Jeffrey Bonar, and Kate Ehriich. 1983. «Cognitive Strategies and Looping Constructs: An Empirical Study.* Communications of the ACM 26, no. 11 (November): 853-60.

Solution Systems. 1987. Worid-Class Programmers Editing Techniques: Interviews with Seven Programmers. South Weymouth, MA: Solution Systems.

Sommerville, Ian. 1989. Software Engineering, 3d ed. Reading, MA: Addison-Wesley.

Spier, Michael J. 1976. «Software Malpractice-A Distasteful Experience.* Software-Practice and Experience 6: 293-99.

Spinellis, Diomidis. 2003. Code Reading: The Open Source Perspective. Boston, MA: Addison-Wesley

SPMN. 1998. Little Book of Coitfiguration Management. Ariington, VA; Software Program Managers Network.

Starr, Daniel. 2003. «What Supports the Roof?* Software Development. July 2003, 38-41.

Stephens, Matt. 2003. «Emergent Design vs. Early Prototyping,* May 26, 2003, wwwsoftwarereality.com/ design/early prototypingjsp.

Stevens, Scott M. 1989. «Intelligent Interactive Video Simulation of a Code Inspection.* Communications of the ACM 32, no. 7 QuXy): 832-43-

Stevens, W., G. Myers, and L. Constantine. 1974- «Structured Design.* IBM Systems Journal 13, no. 2 (May): 115-39.

Stevens, Wayne. 1981. Using Structured Design. New York, NY John Wiley & Sons.

Stroustrup, Bjarne. 1997. The С++ Programming Language, 3d ed. Reading, MA: Addison-Wesley.

Strunk, William, and E. B. White. 2000. Elements of Style, 4th ed. Pearson.

Sun Microsystems, Inc. 2000. «How to Write Doc Comments for the Javadoc Tool,* 2000. Available from http: javasun.com/j2se/javadoc/writingdoccomments/.

Sutter, Herb. 2000. Exceptional С++: 47 Engineering Puzzles, Programming Problems, and Solutions. Boston, MA: Addison-Wesley.

Tackett, Buford D, III, and Buddy Van Doren. 1999. «Process Control for Error Free Software: A Software Success Story,* IEEE Software, May 1999.



Tenner, Edward 1997. Why Things Bite Back: Technology and the Revenge of Unintended Consequences. Vintage Books.

Tenny, Ted. 1988. «Program Readability: Procedures versus Comments.* IEEE Transactions on Software Engineering SE-14, no. 9 (September): 1271-79-

Thayer, Richard H., ed. 1990. Tutorial: Software Engineering Project Management. Los Alamitos, CA: IEEE Computer Society Press.

Thimbleby Harold. 1988. «Delaying Commitment.* IEEE Software, May 78-86.

Thomas, Dave, and Andy Hunt. 2002. «Моек Objects,* IEEE Software, May/June 2002.

Thomas, Edward J., and Paul W. Oman. 1990. «A Bibliography of Programming Siy\. ACM Sigplan Notices 25, no. 2 (February): 7-16.

Thomas, Richard A. 1984- «Using Comments to Aid Program Maintenance.* BYTE, May, 415-22.

Tripp, Leonard L, William F Struck, and Bryan K. Pflug. 1991- «The Application of Multiple Team Inspections on a Safety-Critical Software Standard,* Proceedings of the 4th Software Engineering Standards Application Workshop, Los Alamitos, CA: IEEE Computer Society Press.

U.S. Department of Labor. 1990. «The 1990- 91 Job Outlook in Brief* Occupational Outlook Quarterly, Spring. U.S. Government Printing Office. Document 1990-282-086/20007.

Valett, J., and F E. McGarry. 1989- «A Summary of Software Measurement Experiences in the Software Engineering Laboratory.* Journal of Systems and Software 9, no. 2 (February): 137-48.

Van Genuchten, Michiel. 1991- «Why Is Software Late? An Empirical Study of Reasons for Delay in Software Development.* IEEE Transactions on Software Engineering SE-17, no. 6 Qune): 582-90.

Van Tassel, Dennie. 1978. Program Style, Design, Efficiency, Debugging, and Testing, 2d ed. Englewood Cliffs, NJ: Prentice Hall.

Vaughn-Nichols, Steven. 2003- «Building Better Software with Better Tools,* IEEE Computer, September 2003, 12-14-

Vermeulen, Allan, et al. 2000. The Elements of Java Style. Cambridge University Press.

Vessey Iris, Sirkka L. Jarvenpaa, and Noam Tractinsky. 1992. «Evaluation of Vendor Products: CASE Tools as Methodological Companions.* Communications of the ACM 35, no. 4 (April): 91-105-

Vessey Iris. 1986. «Expertise in Debugging Computer Programs: An Analysis of the Content of Verbal Protocols.* IEEE Transactions on Systems, Man, and Cybernetics SMC-16, no. 5 (September/ October): 621-37.

Votta, Lawrence G, et al. 1991- Investigating the Application of Capture-Recapture Techniques to Requirements and Design Reviews.* Proceedings of the Sixteenth Annual Software Engineering Workshop, December 4-5, 199T Greenbelt, MD: Goddard Space Flight Center. Document SEL-91-006.

Walston, C. E., and C. P Felix. 1977. «A Method of Programming Measurement and Estimation.* IBM Systems Journal 16, no. 1: 54-73-

Ward, Robert. 1989- A Programmers Introduction to Debugging C. Lawrence, KS: R & D Publications.

Ward, William T. 1989- «Software Defect Prevention Using McCabes Complexity Metric* Hewlett-Packard Journal, April, 64-68.

Webster, Dallas E. 1988. «Mapping the Design Information Representation тт.» IEEE Computer, December, 8-23-

Weeks, Kevin. 1992. «Is Your Code Done Yet?* Computer Language, April, 63-72.

Weiland, Richard J. 1983- The Programmers Craft: Program Construction, Computer Architecture, and Data Management. Reston, VA: Reston Publishing.

Weinberg, Gerald M. 1983- «Kill That Code!* Infosystems, August, 48-49-



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.0023