An Integrated Approach to Software EngineeringSpringer Science & Business Media, 2012. gada 6. dec. - 497 lappuses A lot has changed in the fast-moving area of software engineering since the first edition of this book came out. However, two particularly dominant trends are clearly discernible: focus on software processes and object-orientation. A lot more attention is now given to software processes because process improvement is con sidered one of the basic mechanisms for improving quality and productivity. And the object-oriented approach is considered by many one of the best hopes for solving some of the problems faced by software developers. In this second edition, these two trends are clearly highlighted. Aseparate chapter has been included entited "Software Processes. " In addition to talking about the various development process models, the chapter discusses other processes in soft ware development and other issues related to processes. Object-orientation figures in many chapters. Object-oriented analysis is discussed in the chapter on require ments, while there is a complete chapter entitled "Object-Oriented Design. " Some aspects of object-oriented programming are discussed in the chapter on coding, while specific techniques for testing object-oriented programs are discussed in the chapter on testing. Overall, if one wants to develop software using the paradigm of object -orientation, aB aspects of development that require different handling are discussed. Most of the other chapters have also been enhanced in various ways. In particular, the chapters on requirements specification and testing have been considerably enhanced. |
No grāmatas satura
1.–5. rezultāts no 92.
vii. lappuse
... document , code , test plan , test report , and so on , are shown for the case study . It is important , and very instructive , to not only teach the principles of software engineering but also apply them to a software development ...
... document , code , test plan , test report , and so on , are shown for the case study . It is important , and very instructive , to not only teach the principles of software engineering but also apply them to a software development ...
x. lappuse
... Document 130 3.4 Validation 133 3.4.1 Requirement Reviews 134 . 3.4.2 Other Methods 136 · 3.5 Metrics 137 3.5.1 Size Measures 138 3.5.2 Quality Metrics 143 4.1 Cost Estimation 4.1.1 3.6 Summary Exercises Case Study 4 X Contents.
... Document 130 3.4 Validation 133 3.4.1 Requirement Reviews 134 . 3.4.2 Other Methods 136 · 3.5 Metrics 137 3.5.1 Size Measures 138 3.5.2 Quality Metrics 143 4.1 Cost Estimation 4.1.1 3.6 Summary Exercises Case Study 4 X Contents.
xiii. lappuse
... Documentation 366 8.1.6 Law of Demeter for OO Programs 366 8.2 Verification 369 8.2.1 Code Reading . 369 8.2.2 Static Analysis 370 8.2.3 Symbolic Execution . 373 8.2.4 Proving Correctness 378 8.2.5 Code Inspections or Reviews 384 8.2.6 ...
... Documentation 366 8.1.6 Law of Demeter for OO Programs 366 8.2 Verification 369 8.2.1 Code Reading . 369 8.2.2 Static Analysis 370 8.2.3 Symbolic Execution . 373 8.2.4 Proving Correctness 378 8.2.5 Code Inspections or Reviews 384 8.2.6 ...
2. lappuse
... documentation or other aids to help other people use the program . Because the author is the user , the presence of " bugs " is not a major concern ; if the program crashes , the author will fix the program and start using it again ...
... documentation or other aids to help other people use the program . Because the author is the user , the presence of " bugs " is not a major concern ; if the program crashes , the author will fix the program and start using it again ...
3. lappuse
... documentation and data [ IEE87 ] . This definition clearly states that software is not just programs , but includes all the associated documentation and data . This implies that the discipline dealing with the development of software ...
... documentation and data [ IEE87 ] . This definition clearly states that software is not just programs , but includes all the associated documentation and data . This implies that the discipline dealing with the development of software ...
Saturs
1 | |
25 | |
34 | |
1 | 50 |
2 | 83 |
Other Modeling Approaches | 119 |
123 | 123 |
5 | 129 |
Case Study | 253 |
ObjectOriented Design | 277 |
FunctionOriented Design | 311 |
Exercises | 353 |
2 | 369 |
Testing | 409 |
Psychology of Testing | 412 |
Exercises | 468 |
Planning a Software Project | 146 |
8 | 148 |
25 | 169 |
Detailed Design | 193 |
Exercises | 251 |
28 | 475 |
Index | 489 |
403 | 492 |
Citi izdevumi - Skatīt visu
Bieži izmantoti vārdi un frāzes
activities analysis approach attributes axioms basic behavior bool Btree central transform char client COCOMO cohesion complexity components compute considered cost estimation cost estimation models coupling CourseDB courses with preferences cyclomatic cyclomatic complexity data flow diagram data structures defined design methodology detailed design detected determine development process discuss effort entity errors evaluation example execution factors function-oriented given goal graph Hence hierarchy identify implementation information hiding inheritance input module interface language major methods metrics module needed node object diagram object model object-oriented design operations overall parameters partitioning performed PG courses prefs problem domain produce project management prototype relationship represent requirements analysis scenarios SchCourses shown in Figure software development software system specified statements structure chart subclasses SUBORDINATES superclass system design techniques TimeTable total number unit testing validation variables waterfall model words