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 61.
2. lappuse
... detected . And because the product may be used in a variety of environments , perhaps on a variety of hardware platforms , portability is a key issue . Clearly , a program to solve a problem and a programming systems product to solve ...
... detected . And because the product may be used in a variety of environments , perhaps on a variety of hardware platforms , portability is a key issue . Clearly , a program to solve a problem and a programming systems product to solve ...
17. lappuse
... detect coding errors . After this , the modules are gradually integrated into subsystems , which are then integrated to eventually form the entire system . During integration of modules , integration testing is performed to detect ...
... detect coding errors . After this , the modules are gradually integrated into subsystems , which are then integrated to eventually form the entire system . During integration of modules , integration testing is performed to detect ...
22. lappuse
... detect software errors in the early phases ( when im- plementation is not yet complete ) . 7. What are the major reasons for having a phased process ? How does it help in project management ? 8. If absolutely no metrics are used , can ...
... detect software errors in the early phases ( when im- plementation is not yet complete ) . 7. What are the major reasons for having a phased process ? How does it help in project management ? 8. If absolutely no metrics are used , can ...
29. lappuse
... detected at what stage of the development , and then use to determine if the quality assurance activities are being performed properly . This can only be done if the process is predictable ; based on the past experience of such a ...
... detected at what stage of the development , and then use to determine if the quality assurance activities are being performed properly . This can only be done if the process is predictable ; based on the past experience of such a ...
32. lappuse
... detected and corrected . The relative cost of correcting requirement errors as a function of where they are detected is shown in Figure 2.4 [ Boe81 ] . As one would expect , the greater the delay in detecting an error after it occurs ...
... detected and corrected . The relative cost of correcting requirement errors as a function of where they are detected is shown in Figure 2.4 [ Boe81 ] . As one would expect , the greater the delay in detecting an error after it occurs ...
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