Pressman, Roger S. <br/><br/>
Software engineering :   a practitioner's approach /  
Roger S. Pressman. 
 - 6th ed. 
 - Boston, Mass. :  McGraw-Hill,  2005 
 - 912 p. 
<br/><br/> includes index 
<br/><br/>Table of contents>><br/>Part one-the product and the process 1<br/>Chapter 1	the product 3<br/>1.1	the evolving role of software 4<br/>1.2	software 6<br/>	1.2.1		software characteristics 6<br/>	1.2.2		software applications 9<br/>1.3	software: a crisis on the horizon? 11<br/>1.4	software myths 12<br/>1.5	summary 15<br/>References 15<br/>Problems and points to ponder 16<br/>Further readings and information sources 17<br/>Chapter 2	the process 19<br/>2.1	software engineering: a layered technology 20<br/>	2.1.1		process, methods, and tools 20<br/>	2.1.2 	a generic view of software engineering 21<br/>2.2	the software process 23<br/>2.3	software process models 26<br/>2.4	the linear sequential model 28<br/>2.5	the prototyping model 30<br/>2.6	the rad model 32<br/>2.7	evolutionary software process models 34<br/>	2.7.1		the incremental model 35<br/>	2.7.2		the spiral model 36<br/>	2.7.3		the winwin spiral model 38<br/>	2.7.4		the concurrent development model 40<br/>2.8	component-based development 42<br/>2.9	the formal methods model 43<br/>2.10	fourth generation techniques 44<br/>2.11	process technology 46<br/>2.12	product and process 46<br/>2.13 	summary 47<br/>References 47<br/>Problems and points to ponder 49<br/>Further readings and information sources 50<br/>Part two-managing software projects 53<br/>Chapter 3	project management concepts 55<br/>3.1	the management spectrum 56<br/>	3.1.1	 	the people 56<br/>	3.1.2		the product 57<br/>	3.1.2	 	the process 57<br/>	3.1.3	 	the project 57<br/>3.2	people 58<br/>	3.2.1		the players 58<br/>	3.2.2		team leaders 59<br/>	3.2.3		the software team 60<br/>	3.2.4		coordination and communication issues 65<br/>3.3	the product 67<br/>	3.3.1		software scope 67<br/>	3.3.2		problem decomposition 67<br/>3.4	the process 68<br/>	3.4.1		melding the product and the process 69<br/>	3.4.2		process decomposition 70<br/>3.5	the project 71<br/>3.6	the w5hh principle 73<br/>3.7	critical practices 74<br/>3.8	summary 74<br/>References 75<br/>Problems and points to ponder 76<br/>Further readings and information sources 77<br/>Chapter 4	software process and project metrics 79<br/>4.1	measures, metrics, and indicators 80<br/>4.2	metrics in the process and project domains 81<br/>	4.2.1		process metrics and software process <br/>Improvement 82<br/>	4.2.2		project metrics 86<br/>4.3	software measurement 87<br/>	4.3.1		size-oriented metrics 88<br/>	4.3.2		function-oriented metrics 89<br/>	4.3.3		extended function point metrics 91<br/>4.4	reconciling different metrics approaches 94<br/>4.5	metrics for software quality 95<br/>	4.5.1		an overview of factors that affect quality 95<br/>	4.5.2		measuring quality 96<br/>	4.5.3		defect removal efficiency 98<br/>4.6	integrating metrics within the software engineering process 98<br/>	4.6.1		arguments for software metrics 99<br/>	4.6.2		establishing a baseline 100<br/>	4.6.3		metrics collection, computation, and <br/>Evaluation 100<br/>4.7	managing variation: statistical quality control 100<br/>4.8	metrics for small organizations 104<br/>4.9	establishing a software metrics program 105<br/>4.10	summary 107<br/>References 107<br/>Problems and points to ponder 109<br/>Further readings and information sources 110<br/>Chapter 5	software project planning 113<br/>5.1	observations on estimating 114<br/>5.2	project planning objectives 115<br/>5.3	software scope 115<br/>	5.3.1		obtaining information necessary for scope 116<br/>	5.3.2		feasibility 117<br/>	5.3.3		a scoping example 118<br/>5.4	resources 120<br/>	5.4.1		human resources 121<br/>	5.4.2		reusable software resources 121<br/>	5.4.3		environmental resources 122<br/>5.5	software project estimation 123<br/>5.6	decomposition techniques 124<br/>	5.6.1		software sizing 124<br/>	5.6.2		problem-based estimation 126<br/>	5.6.3		an example of loc-based estimation 128<br/>	5.6.4		an example of fp-based estimation 129<br/>	5.6.4		process-based estimation 130<br/>	5.6.5		an example of process-based estimation 131<br/>5.7 	empirical estimation models 132<br/>	5.7.1		the structure of estimation models 132<br/>	5.7.2		the cocomo model 133<br/>	5.7.3		the software equation 135<br/>5.8	the make/buy decision 136<br/>	5.8.1		creating a decision tree 137<br/>	5.8.2		outsourcing 138<br/>5.9	automated estimation tools 139<br/>5.10 	summary 140<br/>References 140<br/>Problems and points to ponder 141<br/>Further readings and information sources 142<br/>Chapter 6	risk analysis and management 145<br/>6.1	reactive versus proactive risk strategies 146<br/>6.2	software risks 146<br/>6.3	risk identification 148<br/>	6.3.1		assessing overall project risk 149<br/>	6.3.2		risk components and drivers 149<br/>6.4	risk projection 151<br/>	6.4.1		developing a risk table 151<br/>	6.4.2		assessing risk impact 153<br/>	6.4.3		risk assessment 154<br/>6.5	risk refinement 156<br/>6.6	risk mitigation, monitoring, and management 156<br/>6.7	safety risks and hazards 158<br/>6.8	the rmmm plan 159<br/>6.9	summary 159<br/>References 160<br/>Problems and points to ponder 161<br/>Further readings and information sources 162<br/>Chapter 7	project scheduling and tracking 165<br/>7.1	basic concepts 166<br/>	7.1.1		comments on "lateness" 167<br/>	7.2.1		basic principles 168<br/>7.2	the relationship between people and effort 170<br/>	7.2.1 		an example 170<br/>	7.2.2		an empirical relationship 171<br/>	7.2.3		effort distribution 172<br/>7.3	defining a task set for the software project 172<br/>	7.3.1		degree of rigor 173<br/>	7.3.2		defining adaptation criteria 174<br/>	7.3.3		computing a task set selector value 175<br/>	7.3.4		interpreting the tss value and selecting the task <br/>Set 176<br/>7.4	selecting software engineering tasks 177<br/>7.5	refinement of major tasks 178<br/>7.6	defining a task network 180<br/>7.7	scheduling 181<br/>	7.7.1		timeline charts 182<br/>	7.7.2		tracking the schedule 185<br/>7.8	earned value analysis 186<br/>7.9	error tracking 187<br/>7.10	the project plan 189<br/>7.11	summary 189<br/>References 189<br/>Problems and points to ponder 190<br/>Further readings and information sources 192<br/>Chapter 8	software quality assurance 193<br/>8.1	quality concepts 194<br/>	8.1.1		quality 195<br/>	8.1.2		quality control 196<br/>	8.1.3		quality assurance 196<br/>	8.1.4		cost of quality 196<br/>8.2	the quality movement 198<br/>8.3	software quality assurance 199<br/>	8.3.1		background issues 200<br/>	8.3.2		sqa activities 201<br/>8.4	software reviews 202<br/>	8.4.1		cost impact of software defects 203<br/>	8.4.2		defect amplification and removal 204<br/>8.5	formal technical reviews 205<br/>	8.5.1		the review meeting 206<br/>	8.5.2		review reporting and record keeping 207<br/>	8.5.3		review guidelines 207<br/>8.6	formal approaches to sqa 209<br/>8.7 	statistical software quality assurance 209<br/>8.8 	software reliability 212<br/>	8.8.1		measures of reliability and availability 212<br/>	8.8.2		software safety 213<br/>8.9	mistake-proofing for software 214<br/>8.10 	the iso 9000 quality standards 216<br/>	8.10.1	the iso approach to quality assurance systems 217<br/>	8.10.2	the iso 9001 standard 217<br/>8.11	the sqa plan 218<br/>8.12	summary 219<br/>References 220<br/>Problems and points to ponder 221<br/>Further readings and information sources 222<br/>Chapter 9	software configuration management 225<br/>9.1	software configuration management 226<br/>	9.1.1		baselines 227<br/>	9.1.2		software configuration items 228<br/>9.2	the scm process 230<br/>9.3 	identification of objects in the software configuration 230<br/>9.4	version control 232<br/>9.5	change control 234<br/>9.6	configuration audit 237<br/>9.7	status reporting 237<br/>9.8	scm standards 238<br/>9.9	summary 238<br/>References 239<br/>Problems and points to ponder 239<br/>Further readings and information sources 240<br/>Part three-conventional methods for software engineering 243<br/>Chapter 10	system engineering 245<br/>10.1	computer-based systems 246<br/>10.2	the system engineering hierarchy 248<br/>	10.2.1	system modeling 249<br/>	10.2.2	system simulation 251<br/>10.3	business process engineering: an overview 251<br/>10.4	product engineering: an overview 254<br/>10.5	requirements engineering 256<br/>	10.5.1	requirements elicitation 256<br/>	10.5.2	requirements analysis and negotiation 258<br/>	10.5.3	requirements specification 259<br/>	10.5.4	system modeling 259<br/>	10.5.5	requirements validation 260<br/>	10.5.6	requirements management 261<br/>10.6	system modeling 262<br/>10.7	summary 265<br/>References 267<br/>Problems and points to ponder 267<br/>Further readings and information sources 269<br/>Chapter 11	analysis concepts and principles 271<br/>11.1	requirements analysis 272<br/>11.2	requirements elicitation for software 274<br/>	11.2.1	initiating the process 274<br/>	11.2.2	facilitated application specification techniques 275<br/>	11.2.3	quality function deployment 279<br/>	11.2.4	use-cases 280<br/>11.3	analysis principles 282<br/>	11.3.1	the information domain 283<br/>	11.3.2	modeling 285<br/>	11.3.3	partitioning 286<br/>	11.3.4	essential and implementation views 288<br/>11.4	software prototyping 289<br/>	11.4.1	selecting the prototyping approach 289<br/>	11.4.2	prototyping methods and tools 290<br/>11.5	specification 291<br/>	11.5.1	specification principles 291<br/>	11.5.2	representation 292<br/>	11.5.3	the software requirements specification 293<br/>11.6	specification review 294<br/>11.7	summary 294<br/>References 295<br/>Problems and points to ponder 296<br/>Further readings and information sources 297<br/>Chapter 12	analysis modeling 299<br/>12.1	a brief history 300<br/>12.2	the elements of the analysis model 301<br/>12.3	data modeling 302<br/>	12.3.1	data objects, attributes, and relationships 302<br/>	12.3.2	cardinality and modality 305<br/>	12.3.3	entity/relationship diagrams 307<br/>12.4	functional modeling and information flow 309<br/>	12.4.1	data flow diagrams 311<br/>	12.4.2	extensions for real-time systems 312<br/>	12.4.3	ward and mellor extensions 312<br/>	12.4.4	hatley and pirbhai extensions 315<br/>12.5	behavioral modeling 317<br/>12.6 	the mechanics of structured analysis 319<br/>	12.6.1	creating an entity/relationship diagram 319<br/>	12.6.2	creating a data flow model 321<br/>	12.6.3	creating a control flow model 324<br/>	12.6.4	the control specification 325<br/>	12.6.5	the process specification 327<br/>12.7	the data dictionary 328<br/>12.8	other classical analysis methods 330<br/>12.9	summary 331<br/>References 331<br/>Problems and points to ponder 332<br/>Further readings and information sources 334<br/>Chapter 13	design concepts and principles 335<br/>13.1	software design and software engineering 336<br/>13.2	the design process 338<br/>	13.2.1	design and software quality 338<br/>	13.2.2	the evolution of software design 339<br/>13.3	design principles 340<br/>13.4	design concepts 341<br/>	13.4.1	abstraction 342<br/>	13.4.2	refinement 343<br/>	13.4.3	modularity 343<br/>	13.4.4	software architecture 346<br/>	13.4.5	control hierarchy 347<br/>	13.4.6	structural partitioning 348<br/>	13.4.7	data structure 349<br/>	13.4.8	software procedure 351<br/>	13.4.9	information hiding 351<br/>13.5	effective modular design 352<br/>	13.5.1	functional independence 352<br/>	13.5.2	cohesion 353<br/>	13.5.3	coupling 354<br/>13.6	design heuristics for effective modularity 355<br/>13.7	the design model 357<br/>13.8	design documentation 358<br/>13.9	summary 359<br/>References 359<br/>Problems and points to ponder 361<br/>Further readings and information sources 362<br/>Chapter 14	architectural design 365<br/>14.1	software architecture 366<br/>	14.1.1	what is architecture? 366<br/>	14.1.2	why is architecture important? 367<br/>14.2	data design 368<br/>	14.2.1	data modeling, data structures, databases, and the data <br/>			warehouse 368<br/>	14.2.2	data design at the component level 369<br/>14.3			architectural styles 371<br/>	14.3.1	a brief taxonomy of styles and patterns 371<br/>	14.3.2	organization and refinement 374<br/>14.4	analyzing alternative architectural designs 375<br/>	14.4.1	an architecture trade-off analysis method 375<br/>	14.4.2	quantitative guidance for architectural design 376<br/>	14.4.3	architectural complexity 378<br/>14.5	mapping requirements into a software architecture 378<br/>	14.5.1	transform flow 379<br/>	14.5.2	transaction flow 380<br/>14.6	transform mapping 380<br/>	14.6.1	an example 380<br/>	14.6.2	design steps 381<br/>14.7 transaction mapping 389<br/>	14.7.1	an example 390<br/>	14.7.2	design steps 390<br/>14.8	refining the architectural design 394<br/>14.9	summary 395<br/>References 396<br/>Problems and points to ponder 397<br/>Further readings and information sources 399<br/>Chapter 15	user interface design 401<br/>15.1	the golden rules 402<br/>	15.1.1	place the user in control 402<br/>	15.1.2	reduce the user's memory load 404<br/>	15.1.3	make the interface consistent 404<br/>15.2	user interface design 405<br/>	15.2.1	interface design models 405<br/>	15.2.2	the user interface design process 407<br/>15.3	task analysis and modeling 408<br/>15.4	interface design activities 410<br/>	15.4.1	defining interface objects and actions 410<br/>	15.4.2	design issues 413<br/>15.5 	implementation tools 415<br/>15.6	design evaluation 416<br/>15.7	summary 418<br/>References 418<br/>Problems and points to ponder 419<br/>Further readings and information sources 420<br/>Chapter 16	component-level design 423<br/>16.1	structured programming 424<br/>	16.1.1	graphical design notation 425<br/>	16.1.2	tabular design notation 427<br/>	16.1.3	program design language 429<br/>	16.1.4	a pdl example 430<br/>16.2	comparison of design notation 432<br/>16.3	summary 433<br/>References 433<br/>Problems and points to ponder 434<br/>Further readings and information sources 435<br/>Chapter 17	software testing techniques 437<br/>17.1	software testing fundamentals 438<br/>	17.1.1	testing objectives 439<br/>	17.1.2	testing principles 439<br/>	17.1.3	testability 440<br/>17.2	test case design 443<br/>17.3	white-box testing 444<br/>17.4	basis path testing 445<br/>	17.4.1	flow graph notation 445<br/>	17.4.2	cyclomatic complexity 446<br/>	17.4.3	deriving test cases 449<br/>	17.4.4	graph matrices 452<br/>17.5	control structure testing 454<br/>	17.5.1	condition testing 454<br/>	17.5.2	data flow testing 456<br/>	17.5.3	loop testing 458<br/>17.6	black-box testing 459<br/>	17.6.1	graph-based testing methods 460<br/>	17.6.2	equivalence partitioning 463<br/>	17.6.3	boundary value analysis 465<br/>	17.6.4	comparison testing 465<br/>	17.6.5	orthogonal array testing 466<br/>17.7	testing for specialized environments, architectures, and <br/>Applications 468<br/>	17.7.1	testing guis 469<br/>	17.7.2	testing of client/server architectures 469<br/>	17.7.3	testing documentation and help facilities 469<br/>	17.7.4	testing for real-time systems 470<br/>17.8	summary 472<br/>References 473<br/>Problems and points to ponder 474<br/>Further readings and information sources 475<br/>Chapter 18	software testing strategies 477<br/>18.1	a strategic approach to software testing 478<br/>	18.1.1	verification and validation 479<br/>	18.1.2	organizing for software testing 479<br/>	18.1.3	a software testing strategy 480<br/>	18.1.4	criteria for completion of testing 482<br/>18.2	strategic issues 484<br/>18.3	unit testing 485<br/>	18.3.1	unit test considerations 485<br/>	18.3.2	unit test procedures 487<br/>18.4	integration testing 488<br/>	18.4.1	top-down integration 488<br/>	18.4.2	bottom-up integration 490<br/>	18.4.3	regression testing 491<br/>	18.4.4	smoke testing 492<br/>	18.4.5	comments on integration testing 493<br/>	18.4.6	integration test documentation 494<br/>18.5	validation testing 495<br/>	18.5.1	validation test criteria 495<br/>	18.5.2	configuration review 496<br/>	18.5.3	alpha and beta testing 496<br/>18.6	system testing 496<br/>	18.6.1	recovery testing 497<br/>	18.6.2	security testing 497<br/>	18.6.3	stress testing 498<br/>	18.6.4	performance testing 498<br/>18.7 the art of debugging 499<br/>	18.7.1	the debugging process 499<br/>	18.7.2	psychological considerations 500<br/>	18.7.3	debugging approaches 501<br/>18.8	summary 502<br/>References 503<br/>Problems and points to ponder 504<br/>Further readings and information sources 505<br/>Chapter 19	technical metrics for software 507<br/>19.1	software quality 508<br/>	19.1.1	mccall's quality factors 509<br/>	19.1.2	furps 511<br/>	19.1.3	iso 9126 quality factors 513<br/>	19.1.4	the transition to a quantitative view 513<br/>19.2 	a framework for technical software metrics 514<br/>	19.2.1	the challenge of technical metrics 514<br/>	19.2.2	measurement principles 515<br/>	19.2.3	the attributes of effective software metrics 516<br/>19.3 	metrics for the analysis model 517<br/>	19.3.1	function-based metrics 518<br/>	19.3.2	the bang metric 520<br/>	19.3.3	metrics for specification quality 522<br/>19.4 	metrics for the design model 523<br/>	19.4.1	architectural design metrics 523<br/>	19.4.2	component-level design metrics 526<br/>	19.4.3	interface design metrics 530<br/>19.5	metrics for source code 531<br/>19.6	metrics for testing 532<br/>19.7	metrics for maintenance 533<br/>19.8	summary 534<br/>References 534<br/>Problems and points to ponder 536<br/>Further reading and other information sources 537<br/>Part four-object-oriented software engineering 539<br/>Chapter 20	object-oriented concepts and <br/>Principles 541<br/>20.1	the object-oriented paradigm 542<br/>20.2	object-oriented concepts 544<br/>	20.2.1	classes and objects 546<br/>	20.2.2	attributes 547<br/>	20.2.3	operations, methods, and services 548<br/>	20.2.4	messages 548<br/>	20.2.5	encapsulation, inheritance, and polymorphism 550<br/>20.3	identifying the elements of an object model 553<br/>	20.3.1	identifying classes and objects 553<br/>	20.3.2	specifying attributes 557<br/>	20.3.3	defining operations 558<br/>	20.3.4	finalizing the object definition 559<br/>20.4	management of object-oriented software projects 560<br/>	20.4.1	the common process framework for oo 560<br/>	20.4.2	oo project metrics and estimation 562<br/>	20.4.3	an oo estimating and scheduling approach 564<br/>	20.4.4	tracking progress for an oo project 565<br/>20.5	summary 566<br/>References 566<br/>Problems and points to ponder 567<br/>Further readings and information sources 568<br/>Chapter 21	object-oriented analysis 571<br/>21.1	object-oriented analysis 572<br/>	21.1.1	conventional vs. Oo approaches 572<br/>	21.1.2	the ooa landscape 573<br/>	21.1.3	a unified approach to ooa 575<br/>21.2	domain analysis 576<br/>	21.2.1	reuse and domain analysis 577<br/>	21.2.2	the domain analysis process 577<br/>21.3	generic components of the oo analysis model 579<br/>21.4	the ooa process 581<br/>	21.4.1	use-cases 581<br/>	21.4.2	class-responsibility-collaborator modeling 582<br/>	21.4.3	defining structures and hierarchies 588<br/>	21.4.4	defining subjects and subsystems 590<br/>21.5	the object-relationship model 591<br/>21.6	the object-behavior model 594<br/>	21.6.1	event identification with use-cases 594<br/>	21.6.2	state representations 595<br/>21.7	summary 598<br/>References 599<br/>Problems and points to ponder 600<br/>Further readings and information sources 601<br/>Chapter 22	object-oriented design 603<br/>22.1	design for object-oriented systems 604<br/>	22.1.1	conventional vs. Oo approaches 605<br/>	22.1.2	design issues 607<br/>	22.1.3	the ood landscape 608<br/>	22.1.4	a unified approach to ood 610<br/>22.2	the system design process 611<br/>	22.2.1	partitioning the analysis model 612<br/>	22.2.2	concurrency and subsystem allocation 613<br/>	22.2.3	the task management component 614<br/>	22.2.4	the user interface component 615<br/>	22.2.5	the data management component 615<br/>	22.2.6	the resource management component 616<br/>	22.2.7	intersubsystem communication 616<br/>22.3	the object design process 618<br/>	22.3.1	object descriptions 618<br/>	22.3.2	designing algorithms and data structures 619<br/>	22.3.3	program components and interfaces 621<br/>22.4	design patterns 624<br/>	22.4.1	describing a design pattern 624<br/>	22.4.2	using patterns in design 625<br/>22.5	object-oriented programming 625<br/>22.6	summary 626<br/>References 627<br/>Problems and points to ponder 628<br/>Further readings and information sources 629<br/>Chapter 23	object-oriented testing 631<br/>23.1	broadening the view of testing 632<br/>23.2	testing ooa and ood models 633<br/>	23.2.1	correctness of ooa and ood models 633<br/>	23.2.2	consistency of ooa and ood models 634<br/>23.3	object-oriented testing strategies 636<br/>	23.3.1	unit testing in the oo context 636<br/>	23.3.2	integration testing in the oo context 637<br/>	23.3.3	validation testing in an oo context 637<br/>23.4 	test case design for oo software 637<br/>	23.4.1	the test case design implications of oo concepts 638<br/>	23.4.2	applicability of conventional test case design <br/>			methods 638<br/>	23.4.3	fault-based testing 639<br/>	23.4.4	the impact of oo programming on testing 640<br/>	23.4.5	test cases and the class hierarchy 641<br/>	23.4.6	scenario-based test design 641<br/>	23.4.7	testing surface structure and deep structure 643<br/>23.5	testing methods applicable at the class level 644<br/>	23.5.1	random testing for oo classes 644<br/>	23.5.2	partition testing at the class level 644<br/>23.6	interclass test case design 645<br/>	23.6.1	multiple class testing 645<br/>	23.6.2	tests derived from behavior models 647<br/>23.7	summary 648<br/>References 649<br/>Problems and points to ponder 649<br/>Further readings and information sources 650<br/>Chapter 24	technical metrics for object-oriented <br/>	systems 653<br/>24.1	the intent of object-oriented metrics 654<br/>24.2	the distinguishing characteristics of object-oriented metrics 654<br/>	24.2.1	localization 655<br/>	24.2.2	encapsulation 655<br/>	24.2.3	information hiding 655<br/>	24.2.4	inheritance 656<br/>	24.2.5	abstraction 656<br/>24.3	metrics for the oo design model 656<br/>24.4	class-oriented metrics 658<br/>	24.4.1 	the ck metrics suite 658<br/>	24.4.2	metrics proposed by lorenz and kidd 661<br/>	24.4.3	the mood metrics suite 662<br/>24.5	operation-oriented metrics 664<br/>24.6	metrics for object-oriented testing 664<br/>24.7	metrics for object-oriented projects 665<br/>24.8	summary 666<br/>References 667<br/>Problems and points to ponder 668<br/>Further readings and information sources 669<br/>Part five-advanced topics in software engineering 671<br/>Chapter 25	formal methods 673<br/>25.1	basic concepts 674<br/>	25.1.1	deficiencies of less formal approaches 675<br/>	25.1.2	mathematics in software development 676<br/>	25.1.3	formal methods concepts 677<br/>25.2	mathematical preliminaries 682<br/>	25.2.1	sets and constructive specification 683<br/>	25.2.2	set operators 684<br/>	25.2.3	logic operators 686<br/>	25.2.4	sequences 686<br/>25.3	applying mathematical notation for formal specification 687<br/>25.4	formal specification languages 689<br/>25.5	using z to represent an example software component 690<br/>25.6	the ten commandments of formal methods 693<br/>25.7 	formal methods-the road ahead 694<br/>25.8	summary 695<br/>References 695<br/>Problems and points to ponder 696<br/>Further readings and information sources 697<br/>Chapter 26	cleanroom software engineering 699<br/>26.1	the cleanroom approach 700<br/>	26.1.1	the cleanroom strategy 701<br/>	26.1.2	what makes cleanroom different? 703<br/>26.2	functional specification 703<br/>	26.2.1	black-box specification 705<br/>	26.2.2	state-box specification 705<br/>	26.2.3	clear-box specification 706<br/>26.3	cleanroom design 706<br/>	26.3.1	design refinement and verification 707<br/>	26.3.2	advantages of design verification 710<br/>26.4	cleanroom testing 712<br/>	26.4.1	statistical use testing 712<br/>	26.4.2	certification 714<br/>26.5	summary 714<br/>References 715<br/>Problems and points to ponder 716<br/>Further readings and information sources 717<br/>Chapter 27	component-based software <br/>Engineering 721<br/>27.1	engineering of component-based systems 722<br/>27.2	the cbse process 724<br/>27.3	domain engineering 725<br/>	27.3.1	the domain analysis process 726<br/>	27.3.2	characterization functions 727<br/>	27.3.3	structural modeling and structure points 728<br/>27.4	component-based development 730<br/>	27.4.1	component qualification, adaptation, and <br/>			composition 730<br/>	27.4 2	component engineering 734<br/>	27.4.3	analysis and design for reuse 734<br/>27.5	classifying and retrieving components 735<br/>	27.5.1	describing reusable components 736<br/>	27.5.2	the reuse environment 738<br/>27.6	economics of cbse 739<br/>	27.6.1	impact on quality, productivity, and cost 739<br/>	27.6.2	cost analysis using structure points 741<br/>	27.6.3	reuse metrics 741<br/>27.7	summary 742<br/>References 743<br/>Problems and points to ponder 744<br/>Further readings and information sources 745<br/>Chapter 28	client/server software engineering 747<br/>28.1	the structure of client/server systems 748<br/>	28.1.1	software components for c/s systems 750<br/>	28.1.2	the distribution of software components 750<br/>	28.1.3	guidelines for distributing application subsystems 752<br/>	28.1.4	linking c/s software subsystems 753<br/>	28.1.5	middleware and object request broker architectures 753<br/>28.2	software engineering for c/s systems 755<br/>28.3	analysis modeling issues 755<br/>28.4	design for c/s systems 755<br/>	28.4.1	architectural design for client/server systems 756<br/>	28.4.2	conventional design approaches for application <br/>			software 757<br/>	28.4.3	database design 758<br/>	28.4.4	an overview of a design approach 759<br/>	28.4.5	process design iteration 761<br/>28.5	testing issues 761<br/>	28.5.1	overall c/s testing strategy 762<br/>	28.5.2	c/s testing tactics 763<br/>28.6	summary 764<br/>References 764<br/>Problems and points to ponder 765<br/>Further readings and information sources 766<br/>Chapter 29	web engineering 769<br/>29.1	the attributes of web-based applications 771<br/>	29.1.1	quality attributes 773<br/>	29.1.2	the technologies 773<br/>29.2	the webe process 774<br/>29.3	a framework for webe 775<br/>29.4	formulating/analyzing web-based systems 776<br/>	29.4.1	formulation 776<br/>	29.4.2	analysis 778<br/>29.5	design for web-based applications 779<br/>	29.5.1	architectural design 780<br/>	29.5.2	navigation design 783<br/>	29.5.3	interface design 785<br/>29.6	testing web-based applications 786<br/>29.7	management issues 787<br/>	29.7.1	the webe team 788<br/>	29.7.2	project management 789<br/>	29.7.3	scm issues for webe 792<br/>29.8	summary 794<br/>References 795<br/>Problems and points to ponder 796<br/>Further readings and information sources 797<br/>Chapter 30	reengineering 799<br/>30.1	business process reengineering 800<br/>	30.1.1 	business processes 800<br/>	30.1.2	principles of business process reengineering 801<br/>	30.1.3	a bpr model 802<br/>	30.1.4	words of warning 804<br/>30.2	software reengineering 804<br/>	30.2.1	software maintenance 804<br/>	30.2.2	a software reengineering process model 805<br/>30.3	reverse engineering 809<br/>	30.3.1	reverse engineering to understand processing 810<br/>	30.3.2	reverse engineering to understand data 811<br/>	30.3.3	reverse engineering user interfaces 812<br/>30.4 	restructuring 813<br/>	30.4.1	code restructuring 814<br/>	30.4.2	data restructuring 814<br/>30.5 	forward engineering 814<br/>	30.5.1	forward engineering for client/server architectures 816<br/>	30.5.2	forward engineering for object-oriented <br/>Architectures 817<br/>	30.5.3	forward engineering user interfaces 818<br/>30.6 	the economics of reengineering 819<br/>30.7	summary 820<br/>References 820<br/>Problems and points to ponder 822<br/>Further readings and information sources 823<br/>Chapter 31	computer-aided software engineering 825<br/>31.1	what is case? 826<br/>31.2	building blocks for case 826<br/>31.3	a taxonomy of case tools 828<br/>31.4 	integrated case environments 833<br/>31.5	the integration architecture 834<br/>31.6 	the case repository 836<br/>	31.6.1	the role of the repository in i-case 836<br/>	31.6.2	features and content 837<br/>31.7	summary 841<br/>References 842<br/>Problems and points to ponder 842<br/>Further readings and information sources 843<br/>Chapter 32	the road ahead 845<br/>32.1	the importance of software-revisited 846<br/>32.2	the scope of change 847<br/>32.3	people and the way they build systems 847<br/>32.4	the "new" software engineering process 848<br/>32.5	new modes for representing information 849<br/>32.6	technology as a driver 851<br/>32.7	a concluding comment 852<br/>References 853<br/>Problems and points to ponder 853<br/>Further readings and information sources 853<br/> 
<br/><br/><label>ISBN: </label>9780071240833 
<br/><br/><label>Subjects--Topical Terms: </label><br/>Software engineering.
<br/><br/><label>Dewey Class. No.: </label>005.1  / P9357