Introduction to OOAD
1. What is Object-Oriented Analysis?
During object-oriented analysis there is an emphasis on finding and describing the objects or concepts in the problem domain. For example, in the case of the flight information system, some of the concepts include Plane, Flight, and Pilot.
2. What is Object-Oriented Design?
During object-oriented design (or simply, object design) there is an emphasis on defining software objects and how they collaborate to fulfill the requirements. The combination of these two concepts shortly known as object oriented analysis and design.
3. What is Object-Oriented Analysis and Design?
During object-oriented analysis there is an emphasis on finding and describing the objects or concepts in the problem domain. For example, in the case of the flight information system, some of the concepts include Plane, Flight, and Pilot. During object-oriented design (or simply, object design) there is an emphasis on defining software objects and how they collaborate to fulfill the requirements. The combination of these two concepts shortly known as object oriented analysis and design.
4. What is Analysis and Design?
Analysis emphasizes an investigation of the problem and requirements, rather than a solution. Design emphasizes a conceptual solution (in software and hardware) that fulfills the requirements, rather than its implementation. For example, a description of a database schema and software objects.
5. Define Design Class Diagrams
A static view of the class definitions is usefully shown with a design class diagram. This illustrates the attributes and methods of the classes.
6. What is the UML?
The Unified Modeling Language is a visual language for specifying, constructing and documenting the artifacts of systems.
7. What are the three ways and perspectives to Apply UML?
Ways-UML as sketch, UML as blueprint, UML as programming language Perspectives-Conceptualperspective, Specification (software) perspective, Implementation (Software) perspective.
8. What is Inception?
Inception is the initial short step to establish a common vision and basic scope for the Project. It will include analysis of perhaps 10% of the use cases, analysis of the critical non- Functional requirement, creation of a business case, and preparation of the development Environment so that programming can start in the elaboration phase. Inception in one Sentence: Envision the product scope, vision, and business case.
9. What Artifacts May Start in Inception?
Some sample artifacts are Vision and Business Case, Use-Case Model, Supplementary Specification, Glossary, Risk List & Risk Management Plan, Prototypes and proof-of-concepts etc.
10. Define Requirements and mention its types.
Requirements are capabilities and conditions to which the system and more broadly, the project must conform.
11. What are Actors?
An actor is something with behavior, such as a person (identified by role), computer system, or organization; for example, a cashier.
12. What is a scenario?
A scenario is a specific sequence of actions and interactions between actors and the system; it is also called a use case instance. It is one particular story of using a system, or one path through the use case; for example, the scenario of successfully purchasing items with cash, or the scenario of failing to purchase items because of a credit payment denial.
13. Define Use case.
A use case is a collection of related success and failure scenarios that describe an actor using a system to support a goal. Use cases are text documents, not diagrams, and use-case modeling is primarily an act of writing text, not drawing diagrams.
14. What are Three Kinds of Actors?
Primary actor, Supporting actor, offstage actor.
15. What Tests Can Help Find Useful Use Cases?
1. The Boss Test
2. The EBP Test
3. The Size Test
16. What are Use Case Diagrams?
A use case diagram is an excellent picture of the system context; it makes a good context diagram that is, showing the boundary of a system, what lies outside of it, and how it gets used.It serves as a communication tool that summarizes the behavior of a system and its actors.
17. What are Activity Diagrams?
A diagram which is useful to visualize workflows and business processes. These can be a useful alternative or adjunct to writing the use case text, especially for business use cases that describe complex workflows involving many parties and concurrent actions.
1. Explain about POS generation systems.
-The Next Gen POS System
-Architectural Layers and Case Study Emphasis
-Iterative Development and Iterative Learning
2. Define Inception. Explain about artifacts of Inception
-Inception: An Analogy 36
-What Artifacts May Start in Inception
-You Know You Didn't Understand Inception When...
3. Explain about Unified process phases.
- Iterative Development
-Additional UP Best Practices and Concepts
-The UP Phases and Schedule
-The UP Disciplines (was Workflows)
-Process Customization and the Development Case
-The Agile UP
-The Sequential "Waterfall
4. Explain about Use-Case Model and its Writing Requirements in Context.
-Use Cases and Adding Value
-Use Cases and Functional Requirements
-Use Case Types and Formats
-Fully Dressed Example: Process Sale
5. List out the components of Object-Oriented Analysis and Design.
-Applying UML and Patterns in OOA/D
-What Is Analysis and Design?
-What Is Object-Oriented Analysis and Design?
6.Explain Relating Use cases and Next Gen POS system
object represents entity of the system
Object-oriented analysis (OOA) applies object-modelling techniques to analyze the functional requirements for a system.
Object-oriented design (OOD) elaborates the analysis models to produce implementation specifications
Unified Modelling Language
Unified Modelling Language (UML) is the set of notations,models and diagrams used when developing object-oriented (OO) systems
Unified Software Development Process
Unified Software Development Process or Unified Process is a popular iterative and incremental software development process framework
Milestone evaluates the basic viability of the project.
Use Case Model
The Use Case Model describes the proposed functionality of the new system.
An Actor is a user of the system.
Constraints are the formal rules and limitations
Scenarios are formal descriptions of the flow of events
Extend relationship between use cases is shown by a dashed arrow with an open arrowhead from the extending use case to the extended (base) use case.
An include relationship is a directed relationship between two use cases Inception phase
The core idea is developed into a product vision. Elaboration phase
The majority of the Use Cases are specified in detail and the system architecture is designed.
The product is moved from the architectural baseline to a system complete enough to transition to the user community
The goal is to ensure that the requirements have been met to the satisfaction of the stakeholders.