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 84.
3. lappuse
... shown a reversal from the early years , as is shown in Figure 1.1 [ Boe76 ] . The main reason for the high cost of software is that software development is still labor - intensive . To get an absolute idea of the costs involved , let us ...
... shown a reversal from the early years , as is shown in Figure 1.1 [ Boe76 ] . The main reason for the high cost of software is that software development is still labor - intensive . To get an absolute idea of the costs involved , let us ...
9. lappuse
... shown in Figure 1.2 . As shown in the figure , when dealing with a small software project , the technology requirement is low ( all you need to know is how to program and a bit of testing ) and the project management requirement is also ...
... shown in Figure 1.2 . As shown in the figure , when dealing with a small software project , the technology requirement is low ( all you need to know is how to program and a bit of testing ) and the project management requirement is also ...
11. lappuse
... shown in Figure 1.3 [ CM78 ] . Correctness is the extent to which a program satisfies its specifications . Reliability is the property that defines how well the software meets its requirements . Efficiency is a factor in all issues ...
... shown in Figure 1.3 [ CM78 ] . Correctness is the extent to which a program satisfies its specifications . Reliability is the property that defines how well the software meets its requirements . Efficiency is a factor in all issues ...
19. lappuse
... shown in Figure 6.13 . The system here is not an interactive system ; hence dynamic modeling is rather straightforward . The normal scenario is that the inputs are given and the outputs are produced . There are at least two different ...
... shown in Figure 6.13 . The system here is not an interactive system ; hence dynamic modeling is rather straightforward . The normal scenario is that the inputs are given and the outputs are produced . There are at least two different ...
24. lappuse
... shown in Figure 2.1 . Software Process | | \ Project1 Project Projectn Product , Product2 Productm FIGURE 2.1 . Processes , projects , and products . A pertinent question that comes up is if the sequence 24 2. Software Processes.
... shown in Figure 2.1 . Software Process | | \ Project1 Project Projectn Product , Product2 Productm FIGURE 2.1 . Processes , projects , and products . A pertinent question that comes up is if the sequence 24 2. Software Processes.
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