Software EngineeringS. Chand Publishing, 2007 - 374 lappuses This book is a comprehensive, step-by-step guide to software engineering.This book provides an introduction to software engineering for students in undergraduate and post graduate programs in computers. |
No grāmatas satura
1.–5. rezultāts no 82.
. lappuse
... Effort 114 Estimating Software Schedule 114 Factors for the complexity of estimation process 115 Project Complexity 115 Project size 115 Structural Uncertainty 115 Historical Information 4.3 . Resources 4.4 . Estimation Techniques ...
... Effort 114 Estimating Software Schedule 114 Factors for the complexity of estimation process 115 Project Complexity 115 Project size 115 Structural Uncertainty 115 Historical Information 4.3 . Resources 4.4 . Estimation Techniques ...
5. lappuse
... effort Software is easy to reproduce • Cost is in its development in other engineering products , manufacturing is the costly stage The industry is labor - intensive • Hard to automate Untrained people can hack something together ...
... effort Software is easy to reproduce • Cost is in its development in other engineering products , manufacturing is the costly stage The industry is labor - intensive • Hard to automate Untrained people can hack something together ...
5. lappuse
... Effort 1.30 % development 1. 40 % analysis and design 2 . 20 % implementation 3. 40 % validation 2.70 % maintenance 1 . 20 % adaptive 2 . 60 % perfective 3 . 3. 20 % corrective Productivity for maintenance is much lower than for ...
... Effort 1.30 % development 1. 40 % analysis and design 2 . 20 % implementation 3. 40 % validation 2.70 % maintenance 1 . 20 % adaptive 2 . 60 % perfective 3 . 3. 20 % corrective Productivity for maintenance is much lower than for ...
21. lappuse
... efforts , the completely ' generic ' modules that are written almost certainly have some degree of context dependency . Put those same modules in a different context , and unpredictable things can happen . This myth is particularly ...
... efforts , the completely ' generic ' modules that are written almost certainly have some degree of context dependency . Put those same modules in a different context , and unpredictable things can happen . This myth is particularly ...
31. lappuse
... effort , together with the use of prototyping technologies , seeks to trade - off or otherwise reduce downstream software design activities and iterations , as well as simplify the software implementation effort . Software prototypes ...
... effort , together with the use of prototyping technologies , seeks to trade - off or otherwise reduce downstream software design activities and iterations , as well as simplify the software implementation effort . Software prototypes ...
Saturs
SOFTWARE REQUIREMENTS SPECIFICATION 133 174 | 133 |
SOFTWARE DESIGN 175 256 | 163 |
Object Oriented Design | 200 |
e Software Design In the Large | 209 |
CODING 257277 | 257 |
SOFTWARE TESTING 279302 | 279 |
SOFTWARE QUALITY ASSURANCE 303334 | 303 |
SOFTWARE MAINTENANCE 335357 | 335 |
METRICS | 75 |
Ten Traps to Avoi | 89 |
Requirements for an Effective Metrics Program | 99 |
ESTIMATION 107 132 | 107 |
Factors for the complexity of estimation process | 115 |
Maintenance is inevitable | 342 |
Glossary 358370 | 358 |
Bibliography 371374 | 371 |
Citi izdevumi - Skatīt visu
Bieži izmantoti vārdi un frāzes
activities analysis application architecture attributes automated Black Box Testing bugs Cleanroom COCOMO complete components configuration constraints correct cost estimation create data flow data flow diagram database defect-free defined describe detailed development process diagrams document effort environment errors evaluation example external Extreme Programming factors feedback formal function points goal hardware identify implementation important improve input integration interaction language lines of code maintenance measure ment modules object object-oriented operating organization performance phase problem procedures project management prototype reengineering reliability reuse schedule scope software assurance software cost software design software development software development process software engineering software maintenance software project software quality Software Requirements software system software testing solution stage standards steps task techniques tion understand unit testing user interface validation variable verification waterfall model white box tests