Ãëàâíàÿ    Ex Libris    Êíèãè    Æóðíàëû    Ñòàòüè    Ñåðèè    Êàòàëîã    Wanted    Çàãðóçêà    ÕóäËèò    Ñïðàâêà    Ïîèñê ïî èíäåêñàì    Ïîèñê    Ôîðóì   
blank
Àâòîðèçàöèÿ

       
blank
Ïîèñê ïî óêàçàòåëÿì

blank
blank
blank
Êðàñîòà
blank
Lecky-Thompson G.W. — Corporate Software Project Management
Lecky-Thompson G.W. — Corporate Software Project Management



Îáñóäèòå êíèãó íà íàó÷íîì ôîðóìå



Íàøëè îïå÷àòêó?
Âûäåëèòå åå ìûøêîé è íàæìèòå Ctrl+Enter


Íàçâàíèå: Corporate Software Project Management

Àâòîð: Lecky-Thompson G.W.

Àííîòàöèÿ:

It has long been accepted in the software industry that projects will be late, over budget, and lacking in agreed upon features due to technical or time limitations. As more companies become involved with the development and deployment of large-scale software projects, it is necessary to define ways to ensure that quality products are produced. Corporate Software Project Management teaches the three main areas for efficient software development: management, quality, and client relations. It provides a series of globally applicable methods that can enhance productivity and reduce costs within software teams, without sacrificing quality. The book deals with both the management aspects and the technical side of software engineering. Examples of how software can be designed to maximize code for future projects are also included. Corporate Software Project Management provides managers, developers, and programmers with methodologies and techniques that will help them produce quality products from start to finish.


ßçûê: en

Ðóáðèêà: Òåõíîëîãèÿ/

Ñòàòóñ ïðåäìåòíîãî óêàçàòåëÿ: Ãîòîâ óêàçàòåëü ñ íîìåðàìè ñòðàíèö

ed2k: ed2k stats

Ãîä èçäàíèÿ: 2005

Êîëè÷åñòâî ñòðàíèö: 350

Äîáàâëåíà â êàòàëîã: 05.05.2006

Îïåðàöèè: Ïîëîæèòü íà ïîëêó | Ñêîïèðîâàòü ññûëêó äëÿ ôîðóìà | Ñêîïèðîâàòü ID
blank
Ïðåäìåòíûé óêàçàòåëü
Reporting of problems by users      261—263
Reporting, benchmark      282—283
Reporting, line and feedback      310—314
Reporting, Problem Reports      177
Reporting, process, Liaison Center support      321—322
Reporting, templates for      35—36
Reporting, test results      77—78
Repository      see "Object Repository"
Request for Proposals (RFPs)      28 72
Requirements Definition document      91—94 108 228
Requirements specification and Requirements Definition document      93—94 104 108
Requirements specification, introduction to      107—108
Requirements specification, program definition language      119—122
Requirements specification, skeleton document structure      108—119
Requirements specification, validating the system      123—126
Requirements, analysis phase      95
Requirements, capture      95—98 331—335
Requirements, defining and documenting      29—30
Requirements, multi-user      116—117
Requirements, relationship to specifications      142—143
Resource, dependencies, documenting      201—202
Resource, editors, compilers      220
Resource, management, Liaison Center task      7—8
Response time to user problems      263
Responsiveness, surveying for client satisfaction      327—328
Reusing code and Object reuse process model      62
Reusing code, guidelines generally      168—169
Reusing code, planning product development      60
Reviews, peer, of specifications      45
Reviews, quality      275—277
Risk assessment      309—310
Robustness, testing for      288 299
RSM (mSquaredTechnologies)      32 364
Satisfaction, client, planning for failure, managing expectations      331—340
Satisfaction, client, testing for      326—331
Scalar variables, limits of      84—86
SCCS versioning system      188
Scheduling      7 327
Scripted programming languages      219
Scripting, data testing      81
scripting, languages      214—215
SDLC      see "Software Development Life Cycle"
Searchable executable code      207
searching, database records      114
Searching, source code      173—174 196—200
Security and interpreted languages      213—214
Security in delivered package      257
Security, multiuser networked applications      117—118
Service delivery      266
service level agreements      282 323
Small companies, corporate environment of      346—348
Small companies, development and testing in      356—357
Small companies, Liaison Center role in      351—353
Small companies, quality assurance at      359—360
Software Development Life Cycle (SDLC), described      3—4
Software Development Life Cycle (SDLC), models and paradigms      62—68
Software Development Life Cycle (SDLC), specifications      39
Software Development Life Cycle (SDLC), testing in      295
Software development, frameworks and environments      221
Software development, paradigms for, choosing      146—150
Software development, quality, managing and documenting      275—284
Software engineering, principles of corporate      89—90
Software engineering, quality products as goal      329—331
Software projects      see "Projects"
Software requirements document      103—104
Solutions, proprietary      195
Sorting routines for source code management      196—197
Source code in Programmer's Guide      201
Source code, control issues      176
Source code, control systems      188—192
Source code, directory in repository      194
Source code, documentation      171—172
Source code, implementing management system for      192—196
Source code, making searchable      196—200
Source code, Open Source      180—181
Source code, open source-acquired      169
Specifications      see also "Specific specification"
Specifications and product development      65
Specifications, common mistakes in      44—48
Specifications, described      39—40
Specifications, diagrams and      48—54
Specifications, Media Requirements      118—119
Specifications, nontechnical      139—140
Specifications, parties involved      40—44
Specifications, poor quality      339—340
Specifications, prototyping and testing      245—246
Specifications, relationship with definitions      110—112
Specifications, requirements      107—126
Specifications, Requirements Definition vs.      93—94
Specifications, terminology      46—47
Specifications, testing      72—73
Speed, and database performance      114—115
spell checking      22—23 277
Spiral process model      62 68
splash screens      232
SQL (Structured Query Language) database requirements      113
staff      see "Personnel"
Standard Query Language (SQL)      216
Standards Officer      352
Standards, conventions      see "Conventions"
Standards, data collection      34—35
Standards, defining      20—26
Standards, introduction to      19—20
Standards, ISO      135—137
Standards, notational, in Functional Specification      135
Standards, reporting templates      35—36
Startup companies, corporate environment of      345—346
Startup companies, development and testing in      354—356
Startup companies, Liaison Center role in      349—351
Startup companies, quality assurance at      359
Storage, central      113
Storage, mass, and requirements specifications      109—110
Storage, permanent      118—119
String handling      80
Structured documents, layout and sections of      15—16
Structured Query Language      see "SQL"
Structures, data structure diagrams      147—149
Structures, operating      18
Style guide      23 35
Style, meeting minutes      25—26
Style, writing standards      23
Subversion (SVN)      190 364
Surveying for client satisfaction      327—329
SuSE (Linux distributor)      358
System Failure Metric (SFM)      320
System model      99—101
System, boundary described      98—99
System, dependencies, preventing, curing      301
System, granularity      177—180
System, layers, and programming languages      209—215
System, overview of in User Guide      260
System, requirements for CD-ROM      363—364
System, testing      see "Testing"
System, user customization      264
System, validating the      123—126
Systems information management      16—18
Table of Contents section of structured document      16
Tabular collection diagrams      99
Target platforms      112—113
Task-by-Task Guide      260
Tasks of Liaison Center      6—10
TCP/IP protocol and specific languages      215—216
Teams in small companies      346—348
Teams in startup companies      345—346
Teams, involved during SDLC      3—4
Teams, makeup and coordination      8
teams, managing      330
Teams, project      239—240 245
Teams, testing and development      310
Technical specifications in Functional Specification      138
Technical writers' role in specifications development      44
Templates, reporting      35—36
Terminology, glossary, and requirements specification      102
Terminology, specifications      46—47
Test Case Failure Ratio (TCFR)      319
Test cases, certification      305—306
Test cases, documenting      206
Test data and scenarios      290
Test data, scalar      84—86
Testing and quality      297—300
Testing and quality control procedures      335—336
Testing for client satisfaction      326—331
Testing vs. certification      304—306
Testing, documenting results      77—78
Testing, GUI (graphical user interface)      81
Testing, introduction to      71—72
Testing, memory storage/retrieval      86—87
Testing, nonfunctional requirements against user needs      124—126
Testing, objects      162—165
Testing, pre-delivery      255—256
Testing, procedures      72—77 287—288
Testing, programs      78—81
Testing, prototype units      247—249
testing, regression      291—292
Testing, strong      294—297
Testing, system dependencies      300—304
Testing, test data types, analysis      78—87
Testing, user interface      250
Testing, weak vs. strong      294—297
Testing, weak, consequences of      288—294
Third-party components      142
Third-party maintained source code      169
Third-party open source      see "Open Source"
Time and database performance speed      114—115
Time, response, to problems      263
Time, standards, documentation      20—21
Timing of software development phases      54—57
Tools, internal, as system dependencies      302
Tools, source code control systems      188—192
Tools-based alternative to Liaison Center      353—354
Total quality management (TQM)      278—279 316—317 326 327
Training and requirements specification      125
Training as part of delivery      265—266
Training, client education      340
Troubleshooting, client satisfaction issues      333
troubleshooting, debugging      87—88
Troubleshooting, section in User Guide      260—261
Type hierarchy in network diagramming      155
Unified Modeling Language (UML)      154
Unit testing      73—75 288
USB ports      257—258
Use cases in process diagram      129
User Guide      30—31 97 259—261
User interface, designing      47—48
User interface, testing      81
User interface, testing functionality of      250
Usernames, standards      22
Users, acceptance testing      73
Users, end, and specifications development      43—44
Users, multi-user requirements      116—117
Users, reporting problems      261—263
Validating, the system      123—126
Validating, use cases      129—130
Value Matrix, and client satisfaction      327—329
Values and documentation standards      23—24
Values, test case      87
Variable-length fields      135—137
Variables, making searchable      198—199
Verification return path, Waterfall process model      64
Versions, defining standards      21
Versions, structuring source code by      194
Versions, using versioning systems      188—192
Videotaping prototype demonstration      236
Viewpoints and problem area design      49—51
Viewpoints in tabular collection diagrams      99
Virtual machines (VM) and coding      213
Virtual machines (VM), Java Virtual Machine (JVM)      221
Visual Basic (VB) for prototyping      229
Visual SourceSafe (VSS)      188 195
Waterfall process model      62—68 146
web sites, Linux Journal      32
Web sites, Open Source Initiative FAQ      183
White box testing      88
WinCvs, installing      364
WinRunner (Microsoft)      81
WinZip file compression      196
Wirth, Niklaus      160
Word Perfect      47
Word, user interface      47
Working data      100—101
World Wide Web      see "Internet the"
Writers, technical, and specifications development      44
Writing, notations in specifications      48—49
Writing, style, and documentation standards      23
XML (Extensible Markup Language) documents      217
1 2 3
blank
Ðåêëàìà
blank
blank
HR
@Mail.ru
       © Ýëåêòðîííàÿ áèáëèîòåêà ïîïå÷èòåëüñêîãî ñîâåòà ìåõìàòà ÌÃÓ, 2004-2024
Ýëåêòðîííàÿ áèáëèîòåêà ìåõìàòà ÌÃÓ | Valid HTML 4.01! | Valid CSS! Î ïðîåêòå