Audience The targeted audiences for this curriculum are System Administrators, Application Developers, System Analysts, Software Engineers and Programmer/Analysts. Learners should be familiar with the concept of object orientation and have experience with application development. It would be helpful for learners to be familiar with distributed programming (multi-tier architecture), relational or object database programming, transactions, and component technology. Total Learning Time 24 to 32 hours 86026 - Object-Oriented Analysis and Design with UML Part 1: Introduction and PlanningThis first course in the series introduces OOAD and the UML, describes the OOAD development process and teaches how to plan for a project. The section about the development covers how to follow an iterative and incremental process. The planning sections cover identifying program requirements and using use cases to understand those requirements.Learn To • Identify the benefits of OOAD. • Identify the advantages and concepts of UML. • Identify the types of development process and analyze the artifacts created in the requirements phase of a development process. • Create, analyze, and evaluate use cases. Audience The targeted audiences for this course are System Administrators, Application Developers, System Analysts, Software Engineers and Programmer/Analysts. Learners should be familiar with the concept of object orientation and have experience with application development. It would be helpful for learners to be familiar with distributed programming (multi-tier architecture), relational or object database programming, transactions, and component technology. Total Learning Time 6 to 8 hours 86026 Objectives Unit 1: OOAD and UML: Concepts 2 - 3 hours • Identify the benefits of using OOAD in a specific situation. • Match the steps in organizing a business with the steps in the OOAD process. • Identify the advantages of using UML in a specific situation. • Match the type of UML model with the information that it represents. • Match UML diagram types with the situations in which they are used. Unit 2: Development Process Cycle 2 - 3 hours • Identify the reason for selecting a development process model in a specific scenario. • Match the phases of a development process with the OOAD artifacts that are generated in each phase. • Identify the artifacts that describe the requirements of a system in a specific scenario. • Identify the types of system functions performed by a system in a specific scenario. • Match system attributes with scenarios in which they are most appropriate. Unit 3: Use Cases 2 hours • Identify the specifications that are necessary to write use cases in a specific situation. • Select the diagram that correctly represents a use case in a specific situation. • Develop a use case that focuses on a specific problem domain. • Match the relationships that exist between the use cases that are displayed in a use case diagram with their names. • Rank a use case in a specific problem domain. • Identify the project activities that are driven by the use cases created for a specific problem domain. • Identify the artifacts that can be derived from a use case in a specific problem domain. • Develop multiple use cases for a specific scenario. • Evaluate a use case for its ability to describe the sequence of events in a specific scenario. 86027 - Object-Oriented Analysis and Design with UML Part 2: Analysis, State Diagrams and Activity DiagramsThis second course in the series focuses on analyzing and modeling system behavior. It describes how to create a conceptual model that identifies the concepts in a problem domain and how to model the system events that actors generate with system sequence diagrams. This course also introduces dynamic modeling with state and activity diagrams.Learn To • Identify how to analyze requirements to develop, interpret and evaluate a conceptual model. • Identify how to analyze system behavior and represent, interpret, create, and evaluate system diagrams and system operation contract documents. • Identify how to represent, interpret, create, and evaluate state and activity diagrams. Audience The targeted audiences for this course are System Administrators, Application Developers, System Analysts, Software Engineers and Programmer/Analysts. Learners should be familiar with the concept of object orientation and have experience with application development. It would be helpful for learners to be familiar with distributed programming (multi-tier architecture), relational or object database programming, transactions, and component technology. Total Learning Time 6 to 8 hours 86027 Objectives Unit 1: Conceptual Model 2 - 3 hours • Identify the set of valid candidate concepts that can be used for creating a meaningful conceptual model in a specific scenario. • Identify the situations in which specification concepts can be applied. • Select a diagram that correctly represents an association between the concepts for a specific situation. • Match the relationship between concepts in a specific scenario with the categories of associations. • Create a conceptual model to represent associations between the concepts for a specific scenario. • Evaluate the conceptual model for its ability to represent associations between the concepts for a specific scenario. • Select a diagram that accurately represents the attributes of concepts in a specific situation. • Select the valid attributes necessary to fulfill the information requirements of a specific scenario. • Create a conceptual model to represent the associations and attributes of concepts for a specific scenario. • Evaluate the conceptual model for its ability to represent the associations and attributes for a specific scenario. • Identify a diagram that accurately represents an associative type in the conceptual model of a specific scenario. • Identify a diagram that accurately represents aggregation between concepts in the conceptual model of a specific scenario. • Select a diagram that accurately represents the roles in associations and the roles as concepts in a specific scenario. Unit 2: Analyzing System Behavior 2 - 3 hours • Identify the correct representation of a system sequence diagram. • Identify the interpretation of the sections of a system sequence diagram. • Create a system sequence diagram to represent a use case for a specific scenario. • Evaluate a system sequence diagram for its ability to represent a use case for a specific scenario. • Select the system operation contract that has the correct format. • Identify the interpretation of the various sections of a system operation contract document based on the guidelines used to create it. • Create a system operation contract to describe the behavior of a specific system. • Evaluate a system operation contract for its ability to represent the behavior of a specific system. Unit 3: Diagrams: State and Activity 2 hours • Identify the appropriate object that can be represented in a state diagram for a specific scenario. • Identify the correct representation of a state diagram. • Identify the interpretation of the sections of a state diagram that is used to represent events, states, transitions, and guards. • Create a state diagram to represent a specific scenario. • Evaluate a state diagram that illustrates the events and states of an object in a specific scenario. • Identify the correct representation of an activity diagram. • Identify the interpretation of the sections of an activity diagram that represents a specific scenario. • Create an activity diagram to represent a sequence of activities in a specific scenario. • Evaluate an activity diagram that represents a sequence of activities in a specific scenario. 86028 - Object-Oriented Analysis and Design with UML Part 3: Interaction Diagrams, Class Diagrams and PackagesThis third course in the series finishes covering dynamic modeling and moves on to static modeling. The dynamic modeling content covers the interaction diagrams, sequence and collaboration, and how they illustrate the message interactions between instances and classes in the class model. The static modeling content covers using class diagrams. This course also covers using packages to illustrate groups of elements or subsystems.Learn To • Identify how to create and interpret diagrams that represent a dynamic model of a system. • Identify how to create diagrams that represent a static model of a system. Audience The targeted audiences for this course are System Administrators, Application Developers, System Analysts, Software Engineers and Programmer/Analysts. Learners should be familiar with the concept of object orientation and have experience with application development. It would be helpful for learners to be familiar with distributed programming (multi-tier architecture), relational or object database programming, transactions, and component technology. Total Learning Time 6 to 8 hours 86028 Objectives Unit 1: Dynamic Modeling 3 - 4 hours • Identify the appropriate interaction diagram to be used in a specified situation. • Identify the accurate syntax for a specified core element of an interaction diagram. • Identify the accurate representation of a specified type of interaction diagram. • Identify the interpretation of a sequence diagram that represents a specified scenario. • Create a sequence diagram to meet the requirements of a specified scenario. • Evaluate the accuracy of a sequence diagram that represents a specified scenario. • Identify the interpretation of a collaboration diagram that represents a specified scenario. • Create a collaboration diagram to meet the requirements of a specified scenario. • Evaluate the accuracy of a collaboration diagram that represents a specified scenario. Unit 2: Static Modeling 3 - 4 hours • Match the perspectives to be used in drawing a class diagram with the situations in which the class diagram is to be drawn. • Match the perspectives related to an association with the situations in which the associations are used. • Match the perspectives related to attributes with the intention of using the attributes. • Identify the class diagram that represents the operations obtained from a specified interaction diagram. • Apply constraints to a class diagram that meets the requirements of a specified scenario. • Create a basic design of a class diagram to meet the requirements of a specified scenario. • Evaluate a class diagram that uses basic UML concepts to represent a specified scenario. • Identify the class diagram with the correct representation of stereotypes for a specified situation. • Identify the type of classification that is used in the class diagram for a specified situation. • Identify the class diagram that correctly represents generalization for a specified situation. • Identify the class diagram that represents a specified type of aggregation. • Complete the class diagram that uses qualified association to represent a specified situation. • Identify the class diagram that uses an association class to represent a specified situation. • Identify the levels of visibility for the elements in the class diagram for a specified situation. • Create an advanced design of a class diagram to meet the requirements of a specified scenario. • Evaluate a class diagram that uses advanced UML concepts to represent a specified scenario. • Identify the appropriate package architecture that represents a specified scenario. • Identify the dependency that exists between specified packages. • Create a package diagram to meet the requirements of a specified scenario. 86029 - Object-Oriented Analysis and Design with UML Part 4: Patterns, Implementation and ConstructionThis final course in the four-part series teaches about using patterns in the design process and about implementing and constructing the program. It covers when and how to use the two types of implementation diagrams, deployment and component, as well as how to construct the program with code. It also addresses some issues of iterative and incremental development.Learn To • Identify how to apply patterns to assign responsibilities to classes, CRC card design, and the benefits and design qualities of frameworks. • Identify the interpretation of deployment diagrams, component diagrams, and their combination. • Identify how to map designs with a programming language and the benefits of iterative and incremental development process. Audience The targeted audiences for this course are System Administrators, Application Developers, System Analysts, Software Engineers and Programmer/Analysts. Learners should be familiar with the concept of object orientation and have experience with application development. It would be helpful for learners to be familiar with distributed programming (multi-tier architecture), relational or object database programming, transactions, and component technology. Total Learning Time 6 to 8 hours 86029 Objectives Unit 1: Patterns and Frameworks 3 - 4 hours • Match basic GRASP patterns with the situations in which they are applicable. • Apply the Expert pattern to assign responsibilities to classes in a specified scenario. • Apply the Creator pattern to assign responsibilities to classes in a specified scenario. • Apply the High Cohesion pattern to assign responsibilities to classes in a specified scenario. • Apply the Low Coupling pattern to assign responsibilities to classes in a specified scenario. • Apply the Controller pattern to assign responsibilities to classes in a specified scenario. • Evaluate a basic GRASP pattern for its accuracy in a specified scenario. • Match advanced GRASP patterns with the situations in which they are applicable. • Apply the Polymorphism pattern to assign responsibilities to classes in a specified scenario. • Apply the Pure Fabrication pattern to assign responsibilities to classes in a specified scenario. • Apply the Indirection pattern to assign responsibilities to classes in a specified scenario. • Apply the Don't Talk to Strangers pattern for assigning responsibilities to classes in a specified scenario. • Evaluate an advanced GRASP pattern for its accuracy in a specified scenario. • Match GOF patterns with the situations in which they are applicable. • Apply the State pattern to assign responsibilities to classes in a specified scenario. • Apply the Singleton pattern to assign responsibilities to classes in a specified scenario. • Apply the Proxy pattern to assign responsibilities to classes in a specified scenario. • Apply the Facade pattern to assign responsibilities to classes in a specified scenario. • Apply the Command pattern to assign responsibilities to classes in a specified scenario. • Evaluate a GOF pattern for its accuracy in a specified scenario. • Match the benefits of frameworks with the situations in which the benefits are applied. • Identify the design quality of a persistence framework that is being violated in a specified situation. • Identify the most appropriate design for a specified scenario based on the Database Broker pattern. • Sequence the steps involved in the development of CRC cards. • Identify an appropriate CRC card design based on layout specifications. Unit 2: OOAD Construct Phase 3 - 4 hours • Identify the correct interpretation of a specified deployment diagram. • Identify the correct interpretation of a specified component diagram. • Identify the correct interpretation of a combination diagram. • Identify the correct class definition according to a specified class diagram. • Identify the correct declaration of methods according to the sequence of messages in a collaboration diagram. • Label classes in the correct order of implementation according to a specified class diagram. • Match a specified situation with the benefit of iterative development applicable to it. • Match a specified situation with the benefit of incremental development applicable to it. • Identify the modification in an existing application that represents refactoring. • Identify the appropriate solution for a specified OOAD implementation issue. Single User License |
|
|
|
**Register Today and Save $$ with Planetlearn.com**
Prices are for single user. If you are looking for internet/intranet or LAN solutions and have specific training needs not listed, please call 207-671-1666 or E-Mail sales@planetlearn.com
Partner Sites
Planetlearn Order securely online or call 207-671-1666 |