This course provides an introduction to Simplified Linear Design (SLIDE), a revolutionary new technique that enables anyone to quickly learn object-oriented design through a step-by-step process. Students will learn simple yet powerful techniques for taking any IT project through all phases of development -- from requirements to deployment. This is a hands-on course that teaches the complete SLIDE technique and can be used with any tools or object-oriented language.
Prerequisites: Hands-on experience with computer programming. No previous knowledge of Object Oriented programming, Java, or formal methodology experience necessary.
Who Should Attend: Programmers and technology leaders looking for a simple and effective technique for doing Object-Oriented Design.
Duration: 4 days
Price: $1600
Understanding Design
- Why Do Design?
- Elements of Good Design
- Recognizing Bad Design
- Understanding Process Methodology
- Comparing SLIDE to RUP and XP
|
Overview of the SLIDE Process
- What is SLIDE?
- How is SLIDE Different
?
- Scope of the Methodology
- Phases of Development
|
Designing for Testability
- Achieving Quality with Limited Testing
- Design Reviews
- Code Inspections
- Smart Use of Test Automation
- Idealism vs. Realism in Testing
- Realistic Quality Assurance Planning
|
Building on Solid Foundations
- Coding Standards
- Software Environments
- Configuration Management
- Issue Tracking
- Communication via the Project Portal
|
Design Tools
- What Tools Can Do For You
- Where Tools Fail
- Tool Use Traps
|
Requirements
- Formal vs. Informal Requirements
- Features vs. Behavior
- Traceability
- A Model Requirements Document
|
|
Prototyping
- Understanding Rapid Visual Phototyping
- When Is Enough, Enough?
- Reviewing Your Prototype
|
UML
- Simplified UML for SLIDE-based design
- What to use from UML, when and why
- Where UML is not enough
- Examples of complete and correct design artifacts
|
Architecture
- Importance of Architecture in Design
- Classic Future-proof Architectures
- Hybrid Architectures
- Borrow, Don't Invent
|
Components
- Understanding Component-Based Design
- Decomposing Requirements Into Components
- Modeling components as UML
- Modeling behavior as UML
|
Design
- Finding the Hidden Objects in Requirements
- Discovering Patterns in Requirements
- Translating UML Designs Into Working Code
- Design Evaluation Techniques
|
Workshop
- Turning Interviews Into Requirements
- Evaluating Requirements Completeness
- Selecting an Architectural Model
- Modeling Behavior Implied by Requirements
- Detailed Designs From Your Models
- Group Design Review
|
|
Register Now
This page is printer friendly.