Object-Oriented Analysis & Design syllabus
Browse the units
Object-Oriented Analysis & Design
8 units
1 Introduction (6 LHs)
- System Development Life Cycle (Planning, Analysis, Design, Implementation)
- Systems Development Methodologies (Structured Design
- Rapid Application Development
- Selecting the Appropriate Development Methodology
- Characteristics of Object-Oriented Systems
- Object-Oriented Systems Analysis and Design
- Benefits of Object-Oriented Systems Analysis and Design
- Unified Process and Unified Modeling Language
2 Requirements Determination (5 LHs)
3 Business Process and Functional Modeling (7 LHs)
4 Structural Modeling (9 LHs)
7 Construction, Installation, and Operations (4 LHs)
8 Laboratory Work
- The laboratory work focuses on turning theory into practical system development skills
- Creating use-case models
- Drawing activity diagrams
- And developing structural models using CRC cards and class diagrams
- And state machine diagrams
- Including package diagrams
- Class and method designs
- Data access components
- User interface prototypes
- And physical architecture plans
1. Introduction (6 LHs)
- System Development Life Cycle (Planning, Analysis, Design, Implementation)
- System Development Life Cycle (Planning, Analysis, Design, Implementation)
- Systems Development Methodologies (Structured Design
- Systems Development Methodologies (Structured Design
- Rapid Application Development
- Rapid Application Development
- Agile Development)
- Selecting the Appropriate Development Methodology
- Selecting the Appropriate Development Methodology
- Characteristics of Object-Oriented Systems
- Characteristics of Object-Oriented Systems (Classes and Objects, Methods and Messages, Encapsulation and Information Hiding, Inheritance, Polymorphism and Dynamic Binding)
- Object-Oriented Systems Analysis and Design
- Object-Oriented Systems Analysis and Design (Use-Case Driven, Architecture-Centric, Iterative and Incremental)
- Benefits of Object-Oriented Systems Analysis and Design
- Benefits of Object-Oriented Systems Analysis and Design
- Unified Process and Unified Modeling Language
- Unified Process and Unified Modeling Language.
2. Requirements Determination (5 LHs)
- Requirements Determination
- Requirements Determination
- Requirements Analysis Strategies
- Requirements Analysis Strategies (Problem Analysis, Root Cause Analysis, Duration Analysis, Activity-Based Costing, Informal Benchmarking, Outcome Analysis, Technology Analysis, Activity Elimination)
- Requirements-Gathering Techniques
- Requirements-Gathering Techniques (Interviews, Joint Application Development, Questionnaires, Document Analysis, Observation, Concept Maps, User Stories)
- System Proposal.
3. Business Process and Functional Modeling (7 LHs)
- Business Process Identification with Use Cases and Use-Case Diagrams
- Business Process Identification with Use Cases and Use-Case Diagrams
- Business Process Modeling with Activity Diagrams
- Business Process Modeling with Activity Diagrams
- Business Process Documentation with Use Cases and Use-Case Descriptions
- Business Process Documentation with Use Cases and Use-Case Descriptions
- Verifying and Validating the Business Processes and Functional Models
- Verifying and Validating the Business Processes and Functional Models.
4. Structural Modeling (9 LHs)
- Structural Models
- Structural Models
- Object Identification
- Object Identification
- CRC Cards
- Class Diagrams
- Creating Structural Models Using CRC Cards and Class Diagrams
- Creating Structural Models Using CRC Cards and Class Diagrams
5. Behavioral Modeling (7 LHs)
- Behavioral Models
- Behavioral Models
- Interaction Diagrams
- Interaction Diagrams
- Behavioral State Machines
- Behavioral State Machines
- Creating and Verifying, and Validating the Behavioral Model
- Creating and Verifying, and Validating the Behavioral Model
6. Design Modeling (10 LHs)
- Verifying and Validating Analysis Models
- Verifying and Validating Analysis Models
- Evolving Analysis Models into Design Models
- Evolving Analysis Models into Design Models
- Packages and Package Diagrams
- Packages and Package Diagrams
- Class and Method Design
- Class and Method Design
- Design Criteria
- Verifying and Validating Class and Method Design
- Verifying and Validating Class and Method Design
- Data Management Layer Design
- Data Management Layer Design (Mapping Problem Domain Objects to Object Persistence Formats, Designing Data Access and Manipulation Classes)
- User Interface Design
- User Interface Design (Principles of User- Centered Design, Developing Interface Structure and Prototypes, Designing Forms, Reports and Navigation, Usability Testing and Feedback)
- Physical Architecture Layer Design
- Physical Architecture Layer Design (Elements of the Physical Architecture Layer, Architectural Components, Server-Based Architectures, Client-Based Architectures, Client–Server Architectures, Client–Server Tiers, Selecting a Physical Architecture, Cloud Computing).
7. Construction, Installation, and Operations (4 LHs)
- Construction
- Construction
- Managing Programming
- Managing Programming
- Developing Documentation
- Developing Documentation
- Designing Tests
- Conversion
- Change Management
- Post-Implementation Activities
- Post-Implementation Activities.
8. Laboratory Work
- The laboratory work focuses on turning theory into practical system development skills
- The laboratory work focuses on turning theory into practical system development skills. Students practice identifying system requirements
- Creating use-case models
- creating use-case models
- Drawing activity diagrams
- drawing activity diagrams
- And developing structural models using CRC cards and class diagrams
- and developing structural models using CRC cards and class diagrams. They also build behavioral models such as sequence
- communication
- And state machine diagrams
- and state machine diagrams. The lab helps students transform their analysis into complete design models
- Including package diagrams
- including package diagrams
- Class and method designs
- class and method designs
- Data access components
- data access components
- User interface prototypes
- user interface prototypes
- And physical architecture plans
- and physical architecture plans. Students are also encouraged to develop a mini project in which they apply these concepts to design and model a complete object- oriented system.