Software Engineering Notes in Plain Language

This link blog intends to complement my course on software engineering. Pressman's book has been adopted for use in this course. Therefore the blog follows the organization of the text book. I hope the blog will be helpful to you.

Sunday, July 22, 2007

7 Requirements Engineering

7.2 Requirements Engineering Tasks
7.2.7 Requirements Management
7.6 Technical Representation
7.8 Validating Requirements

Miscellaneous Lists
Software Requirments Specification
Requirements Tools

Posted by Software Engineering Notes at 3:55 AM  

No comments:

Post a Comment

Newer Post Older Post Home
Subscribe to: Post Comments (Atom)

About Me

Software Engineering Notes
View my complete profile

Table of Contents

  • Home
  • 7 Requirements Engineering
  • 8 Analysis Model
  • 9 Design Engineering
  • 10 Architechural Design
  • 11 Component Level Design
  • 12 User Interface Design
  • 13 Testing Strategies
  • 14 Testing Tactics
  • 15 Product Metrics
  • SAP Business One
  • Software Development Rhythms

Blog Archive

  • ▼  2007 (88)
    • ▼  July (88)
      • Data Slice
      • The Mood Metrics Suite
      • Lack of cohesion in methods
      • The CK Metrics Suite
      • Response for a class
      • Exercise of Coupling between object classes (CBO)
      • Exercise of Depth of the inheritance tree
      • Exercise of cyclomatic complexity
      • Weighted Methods per Class
      • In-process metrics
      • Code Coverage
      • Testing Effectiveness
      • Defect-related metrics
      • Metrics for Source Code (Halstead's Theory)
      • User Interface Metrics
      • Lines Of Code
      • Architectural Design Metrics
      • Function Point (FP)
      • Product Metrics Landscape
      • Fault-Based Testing
      • Black Box Testing
      • Boundary Value Analysis
      • Equivalence Partitioning
      • Data Flow Testing
      • Common types of computer bugs with pseudocode example
      • Stress Testing
      • Alpha and Beta Testing
      • Object Oriented Testing
      • Smoke Testing
      • Criteria for Completion of Testing
      • Strategic Issues (Antibugging)
      • Verification and Validation
      • Organizing for Software Testing
      • 15 Product Metrics
      • 14 Testing Tactics
      • 13 Testing Strategies
      • What is SAP Business One
      • Analysis of the Work Enviornment
      • SAP Business One
      • User Interface Design Process
      • 12 Performing User Interface Design
      • Program Design Language
      • Basic Design Principles
      • Coupling
      • Collaboration Diagram
      • OCL
      • 11 Modeling Component-Level Design
      • Component Diagram
      • Agile Architecture Modeling
      • Exercise
      • Mapping Data Flow into a Software Architecture
      • Call and Return Architecture
      • Layered Architecture
      • Data-flow Architecture
      • Data-centered Architecture
      • Architectural Complexity
      • Architecture Trade-Off Analysis Method
      • Describing Instantiations of the System
      • Refining the Architecture into Components
      • Defining Archetypes
      • Representing the system in Context
      • 10.2.2 Data Design at the Component Level
      • 10.2 Data Design
      • Exercise
      • 10 Creating an architechural design
      • Pattern-Based Software Design
      • ? Design Model
      • Design Concepts
      • Software Requirements Specification
      • 9 Design Engineering
      • Exercise of Analysis Model
      • State Diagram
      • DFD Example
      • Flow-oriented modeling
      • Writing use cases
      • Tools to Draw Diagrams
      • Data Objects
      • Analysis Model Approaches
      • Domain Analysis
      • Analysis Rules of Thumb
      • 8 Building The Analysis Model
      • 7 Requirements Engineering
      • Technical representation
      • Analysis Model
      • Requirments Management Tool
      • Validating Requirments
      • Requirments Management
      • Requirements Engineering Tasks