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 79.
8. lappuse
... defined as [ IEE87 ] : Software engineering is the systematic approach to the development , operation , maintenance , and retirement of software . Another definition from the economic and human perspective is given by Boehm [ Boe81 ] by ...
... defined as [ IEE87 ] : Software engineering is the systematic approach to the development , operation , maintenance , and retirement of software . Another definition from the economic and human perspective is given by Boehm [ Boe81 ] by ...
12. lappuse
... definition of quality is used , what a defect is has to be clearly defined . A defect could be some problem in the software that causes the software to crash or a problem that causes an output to be not properly aligned or one that ...
... definition of quality is used , what a defect is has to be clearly defined . A defect could be some problem in the software that causes the software to crash or a problem that causes an output to be not properly aligned or one that ...
19. lappuse
... defined a template class List . When considering the main issue of scheduling , we notice that scheduling UG courses with preferences , as discussed in the Chapter 5 , is not straightforward , as the system has to ensure that it does ...
... defined a template class List . When considering the main issue of scheduling , we notice that scheduling UG courses with preferences , as discussed in the Chapter 5 , is not straightforward , as the system has to ensure that it does ...
34. lappuse
... defined activity leading toward the satisfaction of the project goals , with the output of one step forming the input of the next one . Most process models specify the steps that need to be performed and the order in which they need to ...
... defined activity leading toward the satisfaction of the project goals , with the output of one step forming the input of the next one . Most process models specify the steps that need to be performed and the order in which they need to ...
35. lappuse
... defined output of a phase , which can be verified by some means and can form input to the next phase ( which may be performed by other people ) . In other words , it is not acceptable to say that the output of a phase is an idea or a ...
... defined output of a phase , which can be verified by some means and can form input to the next phase ( which may be performed by other people ) . In other words , it is not acceptable to say that the output of a phase is an idea or a ...
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