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 82.
4. lappuse
... needed . The project was scrapped ( evidently , the extra cost of $ 3.6 million was not worth the returns ! ) . Many such disaster examples are given in [ Mcf89 , Rot89 ] . A survey reported in [ Rot89 ] states that of the 600 firms ...
... needed . The project was scrapped ( evidently , the extra cost of $ 3.6 million was not worth the returns ! ) . Many such disaster examples are given in [ Mcf89 , Rot89 ] . A survey reported in [ Rot89 ] states that of the 600 firms ...
5. lappuse
... needed for software , when software does not age ? Software needs to be maintained not because some of its components wear out and need to be replaced , but because there are often some residual errors remaining in the system that must ...
... needed for software , when software does not age ? Software needs to be maintained not because some of its components wear out and need to be replaced , but because there are often some residual errors remaining in the system that must ...
8. lappuse
... needed for software development . This is where software engineering comes in . Software engineering is defined as [ IEE87 ] : Software engineering is the systematic approach to the development , operation , maintenance , and retirement ...
... needed for software development . This is where software engineering comes in . Software engineering is defined as [ IEE87 ] : Software engineering is the systematic approach to the development , operation , maintenance , and retirement ...
10. lappuse
... needed by the business be small . Similarly , there are examples , particularly in the financial sector , where the window of opportunity is small . Hence , any software needed to exploit this window of opportunity will have to be done ...
... needed by the business be small . Similarly , there are examples , particularly in the financial sector , where the window of opportunity is small . Hence , any software needed to exploit this window of opportunity will have to be done ...
14. lappuse
... needed to perform it efficiently and correctly . Each of these activities is a major task for large software projects . These basic phases are briefly described here ; each one of them will be discussed in more detail during the course ...
... needed to perform it efficiently and correctly . Each of these activities is a major task for large software projects . These basic phases are briefly described here ; each one of them will be discussed in more detail during the course ...
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