1 / 7

Object-Oriented Software Engineering Development Activities and Products

This chapter provides an introduction to software engineering project activities, work products, and resources, using a UML class diagram. It covers key concepts such as problem statement, requirements elicitation, analysis, system design, object design, implementation, and testing.

jsouth
Download Presentation

Object-Oriented Software Engineering Development Activities and Products

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Art for Chapter 1,Introduction to Software Engineering

  2. Project Activity WorkProduct Task Resources System Participant Model Time Document Equipment Figure 1-1, Software engineering concepts, depicted as a UML class diagram. * is produced by consumes * * *

  3. Figure 1-2, An overview of object-oriented software engineering development activities and their products. problem statement Requirements elicitation ( Ch.4) nonfunctionalrequirements functionalmodel use case diagram Analysis (Ch.5) class diagram analysis object model statechart diagram dynamic model System design sequence diagram ( Ch.6 & 7 )

  4. Figure 1-2, An overview of object-oriented software engineering development activities and their products. (continued) System design (Ch. 6 & 7) subsystem decomposition design goals Object design (Ch. 8 & 9) class diagram object design model Implementation (Ch. 10) source code Test (Ch. 11) deliverable system

  5. Figure 1-4, A dynamic model for the TicketDistributor. :TicketDistributor :Zone :Balance :Traveler selectZone() getPrice() amountDue insertChange() updateBalance() amountDue insertChange() updateBalance() acknowledgement :Ticket «create» printedTicket

  6. Transaction Ticket Zone Coin Balance Bill Figure 1-5, An object model for the TicketDistributor. valid for results into amount paid

  7. Updater Traveler Interface Local Tariff Central Tariff Figure 1-6, A subsystem decomposition for the TicketDistributor.

More Related