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 86.
vi. lappuse
... implementing the final structured design of the case study ( both the initial and the final versions ) . 3. The C ++ code implementing the object - oriented design of the case study . 4. The following tools which have been used in the ...
... implementing the final structured design of the case study ( both the initial and the final versions ) . 3. The C ++ code implementing the object - oriented design of the case study . 4. The following tools which have been used in the ...
16. lappuse
... implemented . In system design the focus is on identifying the modules , whereas during detailed design the focus is on designing the logic for each of the modules . In other words , in system design the attention is on what components ...
... implemented . In system design the focus is on identifying the modules , whereas during detailed design the focus is on designing the logic for each of the modules . In other words , in system design the attention is on what components ...
19. lappuse
... implementation concerns . Many new issues come up here . First , we decided to have a generic template class , which can be used to implement the various DBs , as all DBs are performing similar functions . Hence , we defined a template ...
... implementation concerns . Many new issues come up here . First , we decided to have a generic template class , which can be used to implement the various DBs , as all DBs are performing similar functions . Hence , we defined a template ...
25. lappuse
... implementing " them in a project is not straightforward . To clarify this , let us take the example of traveling . A process for traveling to a destination will be something like this : Set objectives for the travel ( tourism , business ...
... implementing " them in a project is not straightforward . To clarify this , let us take the example of traveling . A process for traveling to a destination will be something like this : Set objectives for the travel ( tourism , business ...
34. lappuse
... performed . However , when implementing a process model , there are some practical issues like when to initiate a step and when to terminate a step that 34 2. Software Processes A Process Step Specification Waterfall Model 1.
... performed . However , when implementing a process model , there are some practical issues like when to initiate a step and when to terminate a step that 34 2. Software Processes A Process Step Specification Waterfall Model 1.
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