Seminars & Workshops
Object-Oriented Systems Development—A 5-Day Workshop
(UML Compliant)
|
|
Hands On Training
|
 Based on Complete, In-Depth, Case Studies
From Concept to Code in One Week
Nothing is Left to the Imagination!
Taught by the Author of a Leading Object-Oriented Text Book
Prentice-Hall Text Book and Case Study Diskette Included
Booch/OMT (Rumbaugh)/Jacobson Unified Modeling Language (UML 1.0) Compliant
40 solid hours of training include breakfast and working lunches
|
What's it all About?
|
Building and delivering large, complex software systems on schedule and within budget is more difficult than ever. Object-oriented technology holds real promise of dramatically increasing productivity and reducing development time. There's no question that object technology will be the dominant software development method of the future.
This in-depth, down-to-earth workshop brings you from concept to code in 5 days. Nothing is left to the imagination. You will leave this workshop with a diskette containing your working case studies and all workproducts.
TWO REALISTIC, in-depth, case studies are developed from user problem statement through object-oriented analysis, design and into implementation. Case studies are designed for both business and engineering developers.
Practical "rules of thumb" are introduced and explained.
All techniques and notation are compliant with the Booch/OMT (Rumbaugh)/Jacobson Unified Modeling Language (UML 1.0) but are applicable to virtually every version of object-oriented analysis and design.
Your instructor is the co-author of a leading object-oriented textbook published by Prentice Hall.
|
Who Should Attend?
|
This workshop is intended for those who desire an in-depth, down-to-earth presentation of object-oriented analysis, design and implementation techniques. Analysts, systems and software engineers, project managers and project leaders, and programmers will benefit from this workshop. No prior exposure to object-oriented concepts is required. Prior exposure to software system analysis and design techniques is desirable but not required.
|
What Makes this Workshop Unique?
|
Students do more than just work on "exercises" or "examples." Students bring their case study from concept to implementation by developing workproducts. Every major object-oriented workproduct is developed by small, energetic teams; workproducts are then reviewed and discussed. Team interactions provide an exciting and dynamic dimension to this workshop. Your instructor personally critiques workproducts providing insight and suggestions.
No other public seminar or workshop provides this level of hands-on, in-depth participation. Forty solid hours of training include breakfast and working lunches.
Students receive a copy of Case Studies in Object-Oriented Analysis & Design by Ed Yourdon and Carl Argila.
|
You Will Learn...
|
- What is Object Technology? And why you should care!
- How to create an initial object model from an informal statement of system requirements.
- How to refine and formalize the object model.
- How to document and review the object-oriented analysis model.
- How to move smoothly from analysis to design.
- The components and structure of the object-oriented design model.
- How to specify and prototype the human interface.
- How to incorporate operating system and platform technology issues into the object-oriented design.
- How to incorporate existing database technology into the object-oriented design.
- What are critical quality issues.
- How to document and review the design.
- How to move into implementation.
- What is an iterative software development process.
- How to test object-based designs
- How to effect a successful transition to object-oriented technology.
|
TOPICS
GETTING STARTED WITH OBJECTS
What makes object-technology different than conventional software development methods? Most software developers are familiar with traditional top-down, functional decomposition approaches. Object-technology involves a change in "mind-set." Developers must now think in terms of a "middle-out" collaboration of objects.
- Introduction to Object-Technology
- Why Object Technology?
- What's this "Paradigm Shift" all about?
- Re-Use? Re-Use of What???
- Key Object Concepts and Principles:
- Polymorphism, Encapsulation, Abstraction, etc.
- Process vs. Method
- Are Objects Right for you?
Case Studies
- Two In-Depth Case Studies
- The Subscription Management System
- (A typical transaction-based, management information system.)
- The Elevator Control System
- (A real-time, event-response system.)
Finding and Keeping Good Objects
- What is an Object??? A Class???
- Kinds of Objects and Classes
- Object Discovery Strategies
- Traditional Analysis Tools
- 3-View Modeling
- "Use Cases"
Class and Object Identification
- Information Analysis Techniques
- Identifying Application Domain Concepts
- Finding the "Right" Objects
- Creating the OOAD Worksheet
BUILDING THE OBJECT-ORIENTED ANALYSIS MODEL
Understanding and capturing user requirements from an object-oriented perspective. The traditional "Victorian novel" specification has proven to be an ineffective way to capture complex software requirements. The object-oriented analysis model combines both visual and textual forms to precisely specify user requirements from an object-oriented perspective.
- Class and Object Refinement
- Object Identification Criteria
- Use of the OOAD Worksheet
- Notation and Techniques
- Creating the Object Model
Things Objects Remember: Identifying Attributes
- How Objects Store Data
- Kinds of Object Attributes
- Attribute Definitions vs. Values
- Attributes in Structures
- Notation and Techniques
- Incorporating Attributes into the Object Model
- Object Constraints: Identifying Links & Associations
- "Business Rules" as Application Domain Constraints
- How Objects Capture Business Rules
- Establishing Links & Associations
- Cardinality and Conditionality
- Notation and Techniques
- Incorporating Links & Associations into the Object Model
- Dealing with Complexity: Identifying Structures
- Establishing Aggregations
- The Concept of Inheritance
- Establishing Generalizations and Specializations
- Discriminators
- Multiple Inheritance
- Notation and Techniques
- Incorporating Structures into the Object Model
- Dealing with Complexity: Identifying Class Categories
- Partitioning the Application Domain
- Class Categories
- Notation and Techniques
- Incorporating Class Categories into the Object Model
Things Objects Do and Say: Identifying Operations & Messages
- Events, Scenarios and Use Cases
- Modeling Dynamic Behavior
- Events, States and State-Transition Diagrams
- Modeling Functional Behavior
- The Role of Pseudo-code, Structured English, etc.
- Notation and Techniques
- Relationship to the Object Model
REVIEWING AND DOCUMENTING THE ANALYSIS MODEL
Did we build the right model? Did we build the model right? It is essential that the object-oriented analysis model be presented in a form which assures that the user can clearly visualize the proposed system.
- Quality Issues-Completeness/Consistency of the Analysis Model
- Syntactic vs. Semantic Correctness
- Checking Model Components
- The Role and Proper use of CASE Tools
Documenting the Analysis Model
- "Good" vs. "Bad" Documentation
- Paper vs. Electronic Documentation
- Mapping Model to Document
- Content of Analysis-Level Documentation
- "User Focused" Documentation
- "Designer Focused" Documentation
Reviewing and Revising the Analysis Model
- The Purpose and Types of Reviews
- The Model-Reviewer's Check-List
- Conducting the Review Meeting
- Automated Support for the Review Meeting
BUILDING THE OBJECT-ORIENTED DESIGN MODEL
Specifying the system implementation from an object-oriented perspective. The user statement of requirements must be cast within the framework of an implementation technology.
Transitioning into Design
- Why OOA vs. OOD?
- Key Design Concepts
- Portability and Extensibility
- Overcoming the "Perfect Technology" Assumption
- OOD Model Notation and Architecture
- Transition Strategies
- Problem Domain Issues
- Performance Issues
- Accommodating Implementation Technology Constraints
- Accommodating Available Inheritance
- Incorporating Re-Usable Classes
- Specifying the Problem Domain in the OOD Model
Specifying the Human Interface
- Human Interface Design Issues
- Prototyping the Human Interface
- Process Issues: When to Start?
- Portability and Extensibility of the Human Interface
- Revealing Human Interface Events
- Integration with the OOD Model
Task Management Issues
- Platform Technology Issues
- Portability and Extensibility Issues
- Modeling Interrupts, Tasks, etc.
- Revealing Platform Events
- Integration with the OOD Model
Specifying Database Design
- Database Technology Issues
- Relational vs. Object-Oriented Databases
- Modeling Database Components
- Revealing Database Events
- Integration with the OOD Model
EVALUATING AND DOCUMENTING THE OBJECT-ORIENTED DESIGN
Effective presentation of the design. Designs must be evaluated from many different, conflicting perspectives. The design must be clearly presented for implementation.
- Quality Issues at the Design Level
- What Make a Class "Good?"
- Coupling and Cohesion Considerations
- Criteria for Good Attributes, Operations, and Messages
- Hierarchy and Factoring Guidelines
- Clarity and Simplicity of Design
Documenting and Reviewing the Design Model
- Design Documentation Considerations
- The "Litmus Test" for Design-Level Documentation
- Living vs. "Frozen" Documentation
- Ability to Review by Scenario
MOVING INTO OBJECT-TECHNOLOGY
Getting an object-based system from design to delivery. The successful implementation of object-technology involves far more than technical problems. Developer mind-sets and corporate cultures must change.
Implementation Issues
- Programming Language Considerations
- Implementation Platform Considerations
- Comparison of Programming Languages
- Object-Oriented Systems with NON-Object-Oriented Languages?
- Implementing the Object-Oriented Constructs
- Synthesizing Structured with Object-Oriented Methods
- The Proper Use of CASE Technology
Process & Life-Cycle Issues
- Waterfall vs. Iterative Processes
- Thread-Based Implementation
- Daily Builds
- Alpha Releases
- Micro-Metrics
- Rapid Application Development (RAD) Environments
- Guidelines for Object-Oriented RAD
- CASE at the Process Level
Testing Object-Based Designs
- Testing Philosophies: "Good Enough" vs. "Never Enough"
- System vs. Object-Level Testing
- Black vs. Clear Box Testing
- Requirements for an "Object Test Bed"
Transitioning to Object Technology
- Managing the Object-Oriented Project
- Managing the Object-Oriented Person
- Non-Technical Aspects of the Problem
- Training and Support: "Just in Time," vs. "Just too Late"
- How to Evaluate: Pros, Cons, Costs and Risks
About your instructor
|
Dr. Carl Argila is co-author, with Ed Yourdon, of Case Studies in Object-Oriented Analysis & Design (Prentice Hall, 1996). Dr. Argila offers over 30 years experience in the analysis, design and implementation of large software systems. Over the past five years, Dr. Argila has presented this workshop throughout North America, Europe, India and the Pacific Rim.
Dr. Argila is president of aLigra Systems; his consultancy offers a broad range of software engineering consulting and training services in the areas of software systems analysis and design, software development methods, software project management and the application of CASE technology.
|
Student Comments
|
- "A difficult course discussed in a high-intensity, high efficiency environment that keeps you glued to your seat."
Orlando
- "The course and case study was excellent. This helped in using the various models and learning. Instructor did an excellent job and teaching this subject."
Athens
- "The class was insightful and informative, it also was entertaining and interesting..."
Hong Kong
- "Class was extremely valuable information & heightened my awareness."
Bombay
- "Excellent course. Covered material in sufficient detail and added levity to an intense topic."
Washington, DC
- "Excellent presentation style. One of the better courses I've seen in terms of keeping students attentive by the use of real-world anecdotes & examples."
Toronto
|
Copyright © 1997 by aLigra Systems, Inc.
Please send your comments to: aligra@acm.org
