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 93.
vii. lappuse
... major outputs of the project , such as the project plan , design 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 ...
... major outputs of the project , such as the project plan , design 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 ...
2. lappuse
... major reasons for the " software problem . " Then we discuss the major problems that software engineering faces . This is followed by the basic approach followed by software engineering to handle the software crisis . In the rest of the ...
... major reasons for the " software problem . " Then we discuss the major problems that software engineering faces . This is followed by the basic approach followed by software engineering to handle the software crisis . In the rest of the ...
4. lappuse
... major component of the total automated system , with the hardware forming a very small component . 1.1.2 Late , Costly , and Unreliable There are many instances quoted about software projects that are behind schedule and have heavy cost ...
... major component of the total automated system , with the hardware forming a very small component . 1.1.2 Late , Costly , and Unreliable There are many instances quoted about software projects that are behind schedule and have heavy cost ...
5. lappuse
... major contributors to the software crisis . A note about the cause of unreliability in software : Software failures are different from failures of , say , mechanical or electrical systems . Products of these other engineering ...
... major contributors to the software crisis . A note about the cause of unreliability in software : Software failures are different from failures of , say , mechanical or electrical systems . Products of these other engineering ...
7. lappuse
... major problem of the software industry . It is estimated that rework costs are 30 to 40 % of the development cost [ Boe87 ] . In other words , of the total development effort , rework due to various changes consume about 30 to 40 % of ...
... major problem of the software industry . It is estimated that rework costs are 30 to 40 % of the development cost [ Boe87 ] . In other words , of the total development effort , rework due to various changes consume about 30 to 40 % of ...
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