chapter 7 n.
Skip this Video
Loading SlideShow in 5 Seconds..
Chapter 7 PowerPoint Presentation
Download Presentation
Chapter 7

Loading in 2 Seconds...

play fullscreen
1 / 6

Chapter 7 - PowerPoint PPT Presentation

  • Uploaded on

Chapter 7. The Object-Oriented Approach to Requirements. Overview. System analysis - begins by defining business events and things -business events are documented in the event table which provides the basis for discovering the data

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'Chapter 7' - estefani

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
chapter 7

Chapter 7

The Object-Oriented Approach to Requirements

  • System analysis

-begins by defining business events and things

-business events are documented in the event table

which provides the basis for discovering the data

flows and processes that are included in the new


-things are documented In ERD for the traditional approach and in class diagrams for the object-oriented approach

overview cont
  • Object-Oriented Viewpoint

--the world consists of objects

--Business functions are supported by a set of objects that work together, or collaborate, to implement the function

object oriented requirements
Object-Oriented Requirements
  • Use case diagrams –show the various user roles and how those roles use the system
  • Collaboration diagram –identify which objects collaborate, to accomplish a use case or business function
  • Message –communication between objects within a use case
  • Sequence diagram– shows the sequence of messages among objects during a use case
  • Interaction diagram– A collaboration or sequence diagram that shows the interactions between objects
  • Statechart diagram –a diagram showing the life of an object in states and transitions
the class diagram
The Class Diagram
  • Class Diagrams

--define the components of the system

(tell what the components make up the system)

  • Use case, interaction and Statechart diagrams

--describe the behavioral aspects of the system

(tell what the components do)

the system activities an oo use case scenario view
The System Activities:An OO use case/scenario view
  • Use case– a single use or task performed by the system for those who use the system

(describes an activity that the system carries

out in response to an event)

  • Actor – a role played by a user of the system.