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 94.
x. lappuse
... Analysis and Specification Software Requirements 3.1.1 Need for SRS 46 · 47 49 51 53 55 . • 58 • 59 59 63 69 70 73 74 75 3.1.2 Requirement Process 3.2 Problem Analysis 3.2.1 Analysis Issues 3.2.2 Informal Approach 79 83 84 87 3.2.4 3.2 ...
... Analysis and Specification Software Requirements 3.1.1 Need for SRS 46 · 47 49 51 53 55 . • 58 • 59 59 63 69 70 73 74 75 3.1.2 Requirement Process 3.2 Problem Analysis 3.2.1 Analysis Issues 3.2.2 Informal Approach 79 83 84 87 3.2.4 3.2 ...
xiv. lappuse
... Analysis 414 • 9.2.3 Cause - Effect Graphing 415 · 9.2.4 Special Cases 418 9.3 Structural Testing 419 9.3.1 Control Flow - Based Criteria 419 · 9.3.2 Data Flow - Based Testing 422 • 9.3.3 An Example . 425 9.3.4 Mutation Testing 9.3.5 ...
... Analysis 414 • 9.2.3 Cause - Effect Graphing 415 · 9.2.4 Special Cases 418 9.3 Structural Testing 419 9.3.1 Control Flow - Based Criteria 419 · 9.3.2 Data Flow - Based Testing 422 • 9.3.3 An Example . 425 9.3.4 Mutation Testing 9.3.5 ...
14. lappuse
... Analysis Requirements analysis is done in order to understand the problem the software system is to solve . The problem could be automating an existing manual process , developing a new automated system , or a combination of the two ...
... Analysis Requirements analysis is done in order to understand the problem the software system is to solve . The problem could be automating an existing manual process , developing a new automated system , or a combination of the two ...
15. lappuse
Pankaj Jalote. There are two major activities in this phase : problem understanding or analysis and requirement specification . In problem analysis , the analyst has to understand the problem and its context . Such analysis typically ...
Pankaj Jalote. There are two major activities in this phase : problem understanding or analysis and requirement specification . In problem analysis , the analyst has to understand the problem and its context . Such analysis typically ...
20. lappuse
... Analysis and Specification " and discusses the different aspects of this phase . The desirable qualities of the re- quirements document are discussed , along with the different aspects the document should specify . Different approaches ...
... Analysis and Specification " and discusses the different aspects of this phase . The desirable qualities of the re- quirements document are discussed , along with the different aspects the document should specify . Different approaches ...
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