Airlie Software Council

Ada COCOMO, 26, 269-274 Ada 83, 34-36 Ada 95, 34-36

Adaptability metric, 197-198, 286-287,

292,296, 344-345 Adversarial stakeholder relationships, 15-16, 225

Airlie Software Council, 202, 232

nine best practices, 233-235 Architectural risk, 217 Architecture baseline, 110,114-115 management perspective, 110-111 team, 161-162

technical perspective, 111-115 Architecture-first approach, 63, 64, 68, 118,

119, 231,233,234 Artifacts, 83-107 artifact sets, 84-95 associated with each workflow, 120 deployment set, 88-92 design set, 87 engineering, 103-105 engineering sets, 86-92 evolution over the life cycle, 92-93 implementation set, 87-88, 90-92 management, 96-102 management set, 85-86 pragmatic, 105-107

requirements set, 86 test, 93-95 Assessment workflow, 118-124 Automation improving through software environments, 46^18 tools, 168-172

Boehm, Barry, 17-20, 44^15, 75,126,140, 242-245,266,271, 274, 292 staffing principles, 44^45 top 10 software metrics, 17-20, 242-245 Bohr-bugs, 199 Booch, Grady, 36, 37 Bottom-up software cost estimation, 28 Breakage and modularity metric, 197 Brown, Norm, 202, 232 Budgeted cost and expenditures metric,

191-195 Business case, 96-97 Business context, 146

C language, 34-36 C++ language, 34-36 Capability Maturity Model, 68, 363-390 CCPDS-R case study, 15, 299-362 artifacts, 323-326 component evolution, 318-320

CCPDS-R case study (cont.)

computer software configuration items,

305-307 core metrics, 337-348 incremental design process, 315-317 incremental test process, 321-323 major milestone demonstration, 329-336 metrics, 318-321, 337-356 minor milestones, 315-318 people factors, 356-359 process overview, 309-326 project organization, 304-306 risk management, 312-314 software acquisition process, 301-304 software architecture skeleton, 307-309 software artifacts, 323-326 Change management, 174-181 configuration baseline, 178-179 Configuration Control Board, 179-181 environment, 63, 64, 67, 232, 233, 234 software change orders, 175-178 Change metrics, 283-298 Change traffic and stability metric,

196-197 Checkpoints, 125-134 major milestones, 126-132 minor milestones, 132-133 periodic status assessments, 133-134 COBOL language, 34-35 COCOMO, 26, 43,265-281 COCOMO II, 26, 67, 274-281 Commercial components 39^40 Component-based development, 33, 63, 64,

68,231,233 Component view, 112-114 Configurable process, 65, 67, 232, 233 Configuration baseline, 178-180 Configuration Control Board, 179-181, 286

Configured baseline, 286 Construction phase, 79 Construction team, 166

Continuous integration, 226-227 Conventional software engineering principles, 55-63 Conventional software management, 5-20 cost allocations, 227 design reviews, 17 quality, 49

work breakdown structures, 140-142 Cost estimation, 26-29, 265-281 Culture shifts, 248-251

Davis, Alan, 55-62

Defense Science Board Task Force, 5,

263-264 DeMarco, Tom, 284

Demonstration-based approach, 65,68,119,

232,233 Deployment documents, 101 Deployment set, 88-92 Deployment view, 112-114 Deployment workflow, 118-124 Design breakage, late, 12-13, 225 Design set, 87 Design view, 112-114 Design workflow, 118-124 Development environment, 172 Diseconomies of scale, 22, 210, 245 Document-driven approach, 14-17, 225 Domain experience, 217-218

Early risk resolution, 227-228 Earned value system, 191-195 Economy of scale, 24, 65 Elaboration phase, 77-78 End-product quality metrics, 291-293 Engineering artifacts, 103-105 architecture description, 104-105 software user manual, 104-105 vision document, 103-104 Engineering sets, 86-92 deployment set, 88-92 design set, 87

implementation set, 87-88, 90-92 requirements set, 86 Engineering stage, 74-76 Environment, 101 change management, 63, 64, 67,232,233, 234

project, 172-185 software, 46-48 workflow, 118-124 Evolutionary requirements, 228-230 Evolutionary work breakdown structures, 142-146

Evolving levels of detail, 65, 67, 232, 233, 234

Expenditures metric, 191-195, 345-348

Formal inspections, 234 FORTRAN 77 language, 34 Forward engineering, 47 Functional decomposition, requirements-

driven, 14-15, 225 Function points, 34-36, 241

Heisen-bugs, 199 Horowitz, Ellis, 274, 363 Humphrey, Watts, 155

Implementation set, 87-88, 90-92

Implementation workflow, 118-124

Improving software economics, 31-53

Inception phase, 76-77

Independent software cost estimation, 28

Infrastructures, 181-184

Initial operational capability milestone,

130-131 In-progress indicators, 293-297 Inspections, 10, 51-53, 234 Integrated life-cycle environments, 49 Integration continuous, 226-227 conventional software process, 50 protracted, 12-13, 225

Iteration workflows, 121-124 Iterative life-cycle process, 63, 64, 67, 119, 231,233

Iterative process planning, 139-154 Java, 34

Jones, Capers, 5,27, 34, 36,259-261,285 Kruchten, Philippe, 111 Languages, 34-36

Life-cycle architecture milestone, 129-131 Life-cycle objectives milestone, 128-129 Life-cycle phases, 73-81 construction phase, 79 effort and schedule, 268 elaboration phase, 77-78 inception phase, 76-77 transition phase, 80-81 Life-cycle stages engineering, 74-76 production, 74-76 Life-cycle testing, 51 Line-of-business organizations, 155-158

Macroprocesses, 40—41,168 Maintainability, 287, 292-293 Maintenance environment, 172 Major milestones, 126-132, 231

initial operational capability milestone, 130-131

life-cycle architecture milestone, 129-131 life-cycle objectives milestone, 128-129 product release milestone, 132 Management artifacts, 96-102 business case, 96 deployment, 101 environment, 101 release descriptions, 100 release specifications, 98 sequences, 101-102

software change order database, 98-100

Management artifacts (cont.)

software development plan, 96-97 status assessments, 100-101 work breakdown structure, 97 Management indicators, 188-196 Management reviews, 125-134 Management set, 85-86 Management workflow, 118-124 Maturity metric, 198-199, 287, 292,

296-297,345-346 Metaprocesses, 40-41, 168 Metrics adaptability, 286-287 attributes, 189-190 automation, 202-207 change, 283-298

characteristics of a good metric, 201-202 classes, 204-205 collected statistics, 288-291 core metrics, 188-202 derivation, 286-297 dynamic trend, 188 end-product quality, 291-293 in-progress indicators, 293-297 life-cycle expectations, 199-200 maintainability, 287 management indicators, 190-196 maturity, 287 modularity, 286 software change orders, 285 software quality, 284-285 source lines of code, 285 static value, 188 Microprocesses, 40-41, 168 Minor milestones, 132-133 Model-based notation, 65, 68, 232, 233, 234 Model-based software architectures, 109-115 architecture baseline, 114-115 architecture descriptions, 114 component view, 114 deployment view, 114 design view, 114

management perspective, 110-111

process view, 114 technical perspective, 111-115 use case view, 112-113 Modern project profiles, 225-235 Modern software economics, 242-245 Modern software management principles,

Project Management Made Easy

Project Management Made Easy

What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.

Get My Free Ebook


Responses

  • Ilse
    What is airlie software council?
    4 years ago

Post a comment