Jacobson Process

Download as pdf or txt
Download as pdf or txt
You are on page 1of 14

You should be able to define and understand

Object Oriented methodologies.

- Jacobson’s methodologies
Patterns
Frameworks

8/8/2019 1
JACOBSON METHODOLOGIES

◼ Use Cases.
◼ Object Oriented Software Engineering.
◼ Object Oriented Business Engineering.

8/8/2019 2

Use Cases
Understanding system requirements
◼ Interaction between Users and Systems
◼ The use case description must contain
◼ How and when the use case begins and ends.
◼ The Interaction between the use case and its actors,
including when the interaction occurs and what is
exchanged.
◼ How and when the use case will need data stored in the
system.
◼ Exception to the flow of events
◼ How and when concepts of the problem domain are
handled.

8/8/2019 3
OOSE
◼ Object Oriented Software Engineering.
◼ Objectory is built models
◼ Use case model---The Use case model
defines the outside and inside of the
system behavior
◼ Domain object model-----The objects of the
real world are mapped into the domain
object model

8/8/2019 4
◼ Analysis object model---The analysis
object model presents how the source
code should be carried out and written
◼ Implementation model-It represents the
implementation of the system
◼ Test model----It constitutes the test
plans specifications and reports.

8/8/2019 5
OOBE
◼ Object Oriented Business Engineering---
Use Case again are the central vehicle for modelling, providing
traceability throughout the software engineering process.

◼ OOBE is object modeling at the


enterprise level.
◼ Analysis phase-----The analysis phase defines the system to be
built in terms of the problem domain object model.
◼ Design and Implementation phase----This includes DBMS,
distribution of process, available component libraries and
incorporation of graphical user interface tools.

8/8/2019 6
◼ Testing phase
◼ E.g. Unit testing, integration and
system testing

8/8/2019 7
PATTERNS
◼ It is an instructive information that
captures the essential structure and
insight of a successful family of proven
solutions to a recurring problem that
arises within a certain context and
system of forces.

8/8/2019 8
Good Pattern will do the
following
◼ It solves a problem.
◼ It is a proven concept.
◼ The Solution is not obvious.
◼ It describes a relationship.
◼ The pattern has a significant human
component.

8/8/2019 9
Patterns

Patterns

Generative Patterns Non Generative Patterns


(describe recurring phenomena (describe recurring phenomena
with saying how to without saying how to
reproduce them) reproduce them)
8/8/2019 10
Patterns Template
◼ Essential Components should be clearly recognizable
on reading a pattern:
◼ Name
◼ Problem
◼ Context
◼ Forces
◼ Solution
◼ Examples
◼ Resulting context
◼ Rationale
◼ Related Patterns
◼ Known uses

8/8/2019 11
Frameworks
◼ Way of delivering application
development patterns to support best
practice sharing during application
development.

◼ Can be viewed as the implementation


of a system of design patterns.

8/8/2019 12
Benefits of Frameworks
◼ Reusability
◼ Modularity
◼ Extensibility
◼ Inversion of Control

8/8/2019 13
Difference between Patterns and
Frameworks
◼ Design patterns are more abstract than
frameworks.
◼ Design patterns are smaller
architectural elements than
frameworks.
◼ Design patterns are less specialized
than frameworks.

8/8/2019 14

You might also like