Q.
Object-Oriented Analysis and Design (OOAD) is a software engineering
methodology that involves using object-oriented concepts to design and
implement software systems. OOAD involves a number of techniques and
practices, including object-oriented programming, design patterns, UML
diagrams, and use cases. Here are some important aspects of OOAD:
1. Object-Oriented Programming: Object-oriented programming involves
modeling real-world objects as software objects, with properties and
methods that represent the behavior of those objects. OOAD uses this
approach to design and implement software systems.
2. Design Patterns: Design patterns are reusable solutions to common
problems in software design. OOAD uses design patterns to help developers
create more maintainable and efficient software systems.
3. UML Diagrams: Unified Modeling Language (UML) is a standardized
notation for creating diagrams that represent different aspects of a software
system. OOAD uses UML diagrams to represent the different components
and interactions of a software system.
4. Use Cases: Use cases are a way of describing the different ways in which
users interact with a software system. OOAD uses use cases to help
developers understand the requirements of a system and to design software
systems that meet those requirements.
There are several advantages to using OOAD in software
engineering:
1. Reusability: OOAD emphasizes the use of reusable components and design
patterns, which can save time and effort in software development.
2. Scalability: OOAD can help developers design software systems that are
scalable and can handle changes in user demand and business
requirements over time.
3. Maintainability: OOAD emphasizes modular design and can help developers
create software systems that are easier to maintain and update over time.
4. Flexibility: OOAD can help developers design software systems that are
flexible and can adapt to changing business requirements over time.
5. However, there are also some potential disadvantages to using OOAD:
6. Complexity: OOAD can be complex and may require significant expertise to
implement effectively.
7. Time-consuming: OOAD can be a time-consuming process that involves
significant upfront planning and documentation.
8. Rigidity: Once a software system has been designed using OOAD, it can be
difficult to make changes without significant time and expense.
9. Cost: OOAD can be more expensive than other software engineering
methodologies due to the upfront planning and documentation required.
10. Overall, OOAD can be an effective approach to designing and
implementing software systems, particularly for complex or large-scale
projects. However, it’s important to weigh the advantages and disadvantages
carefully before adopting this approach.
Q.2
Use-Case Model
The Use-case model is defined as a model which is used to show how users
interact with the system in order to solve a problem. As such, the use case
model defines the user's objective, the interactions between the system and
the user, and the system's behavior required to meet these objectives.
Various model elements are contained in use-case model, such as actors,
use cases, and the association between them.
We use a use-case diagram to graphically portray a subset of the model in
order to make the communication simpler. There will regularly be a
numerous use-case diagram which is related to the given model, each
demonstrating a subset of the model components related to a specific
purpose. A similar model component might be appearing on a few use-case
diagrams; however, each use-case should be consistent. If, in order to handle
the use-case model, tools are used then this consistency restriction is
automated so that any variations to the component of the model (changing
the name, for instance) will be reflected automatically on each use-case
diagram, which shows that component.
Packages may include a use-case model, which is used to organize the
model to simplify the analysis, planning, navigation, communication,
development and maintenance.
Various use-case models are textual and the text captured in the use-case
specifications, which are linked with the element of every use-case model.
The flow of events of the use case is described with the help of these
specifications.
The use-case model acts as an integrated thread in the development of the
entire system. The use-case model is used like the main specification of the
system functional requirements as the basis for design and analysis, as the
basis for user documentation, as the basis of defining test cases, and as an
input to iteration planning.
Origin of Use-Case
Nowadays, use case modeling is frequently connected with UML, in spite of
the fact that it has been presented before UML existed. Its short history is:
Q.3
. Comparison Between Traditional Approach and Object-Oriented
Approach to Development in Software Engineering
Summarize the comparison between Traditional Approach and Object-Oriented
Approach shows through the table 1.
Q.4
Requirement analysis can be said to identify investigation, documenting and
analysing requirements of the system. The first investigation step of the
need of a system is a major activity of problem analysis. This is the role of a
system analyst to determine the actual requirement of a system. Sometimes,
system analyst may make mistake in discovering the requirements and in
trying to analyse a problem. As a result, they may come up with the wrong
solution in designing and implementation of a solution. And the solution will
not be able to solve the real problem and even cause a new problem in later
system analysis process. Therefore, this paper looks at one of the effective
methods (fact-finding) for system analyst to help them in gathering
information.
Get Help With Your Essay
If you need assistance with writing your essay, our professional essay writing
service is here to help!
Essay Writing Service
Definition of Fact-finding Techniques
Fact finding is process of collection of data and information based on
techniques which contain sampling of existing documents, research,
observation, questionnaires, interviews, prototyping and joint requirements
planning. System analyst uses suitable fact-finding techniques to develop
and implement the current existing system. Collecting required facts are
very important to apply tools in System Development Life Cycle because
tools cannot be used efficiently and effectively without proper extracting
from facts. Fact-finding techniques are used in the early stage of System
Development Life Cycle including system analysis phase, design and post
implementation review. Facts included in any information system can be
tested based on three steps: data- facts used to create useful information,
process- functions to perform the objectives and interface- designs to
interact with users
Q.5
Requirement analysis can be said to identify investigation, documenting and analysing
requirements of the system. The first investigation step of the need of a system is a major
activity of problem analysis. This is the role of a system analyst to determine the actual
requirement of a system. Sometimes, system analyst may make mistake in discovering the
requirements and in trying to analyse a problem. As a result, they may come up with the
wrong solution in designing and implementation of a solution. And the solution will not be
able to solve the real problem and even cause a new problem in later system analysis
process. Therefore, this paper looks at one of the effective methods (fact-finding) for system
analyst to help them in gathering information.
Get Help With Your Essay
If you need assistance with writing your essay, our professional essay writing service is here
to help!
Essay Writing Service
Definition of Fact-finding Techniques
Fact finding is process of collection of data and information based on techniques which
contain sampling of existing documents, research, observation, questionnaires, interviews,
prototyping and joint requirements planning. System analyst uses suitable fact-finding
techniques to develop and implement the current existing system. Collecting required facts
are very important to apply tools in System Development Life Cycle because tools cannot be
used efficiently and effectively without proper extracting from facts. Fact-finding techniques
are used in the early stage of System Development Life Cycle including system analysis
phase, design and post implementation review. Facts included in any information system
can be tested based on three steps: data- facts used to create useful information, process-
functions to perform the objectives and interface- designs to interact with users
