Read more
Informationen zum Autor Rick Lutowski Klappentext Software Requirements: Encapsulation! Quality! and Reuse describes how to make requirements! and their implementing code! easier to change through the use of Freedom methodology. Freedom reduces software life cycle costs by making requirements quickly adaptable to changing technology and business needs. This book examines the definition of requirements and explains how they can be encapsulated within so software engineers and analysts can understand the nature of the requirements. With the theoretical underpinnings established! the book reviews the Freedom Requirements process and details the individual tasks of the process in a how-to fashion! explaining relevant terminology! recording notations! and more. Zusammenfassung Describes how to make requirements easy to change by using encapsulation. This book provides an overview of the Freedom methodology and details the individual tasks of the methodology in a 'how-to' fashion. It shows how the Freedom requirements methodology can be used as a part of an overall software development methodology. Inhaltsverzeichnis OverviewWhy Freedom?Freedom Methodology OverviewMethodology Benefits of FreedomEconomic Benefits of FreedomInformation-Hiding SecretsChapter OverviewInformation-Hiding ConceptsContrast with Traditional Design Contrast with Current OO PracticeWhat Are Requirements? Chapter OverviewDefinition of RequirementsDefinition of DesignDefinition of Implementation Design and Implementation Constraints Freedom Requirements Process Chapter OverviewEnterprise Process Models Bounding the Black Box Context DiagramsRequirements Process Example Problem Enterprise Process ModelExample Problem Black Box BoundingExample Problem Context Diagram Quality Requirements Chapter OverviewTypes of Requirements Measuring Software Quality Where's the Developer? 'ility Mapping Example Problem Quality RequirementsStimulus Identification and CohesionChapter OverviewWhat Is a Stimulus? Stimulus SetsFunctionality Screens Programmatic Protocols Example Problem Functionality ScreenExample Problem Programmatic ProtocolStimulus Organization and ArchitectureChapter OverviewStimulus Set Architecture New Stimulus ResponseFunctionality Trees Sample Functionality Tree Example Problem: Programmatic Interface Functionality TreeExample Problem: Reverse Engineering the ExternalInterface ArchitectureExample Problem Functionality TreeAlternate Kickoff Approaches Functionality Tree NeutralityReusable RequirementsChapter OverviewRepetitive and Reusable Stimulus Sets Reusable Requirements ComponentsExample Reusable Requirements Component Example Problem Reusable RequirementsIncremental DevelopmentChapter OverviewRequirements Prioritization Example Problem Requirements PrioritiesResponses and Behavior TablesChapter OverviewTypes of ResponsesBehavior TablesResponse Recording Languages Response Recording SyntaxExample Problem Behavior TablesRequirements Encapsulation DesignChapter OverviewRequirements Encapsulation Design Rule Canonical Design ArchitectureExample Problem Functionality Module ArchitectureRequirements EncapsulationChapter OverviewFunctionality ModulesCommon Service Modules Functionality Module Structure Example Problem Functionality Module Interface PrototypingChapter OverviewPurpose of PrototypesTypes of Prototypes Example Problem Interface Mockup Requirements Evolution Chapter OverviewHandling the Ripple Effect of ChangeRequirements Change ExampleAppendicesA Software Requirements SpecificationB Cost Savings Estimate DetailsC Glossary ...
