1 / 8

Comprehensive Overview of Object-Oriented Software Engineering in COP 3331

This course, COP 3331 Object-Oriented Analysis and Design led by Bob Myers, delves into software engineering, emphasizing its multifaceted nature beyond mere coding. It covers essential stages such as problem definition, analysis, system design, class/object design, implementation, and maintenance. Students will learn about UML (Unified Modeling Language) for modeling software through use case diagrams, class diagrams, sequence diagrams, and statechart diagrams. The course also addresses critical real-world software engineering issues, including requirements analysis, communication, management, and quality assurance.

harsha
Télécharger la présentation

Comprehensive Overview of Object-Oriented Software Engineering in COP 3331

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. COP 3331 OBJECT-ORIENTED ANALYSIS AND DESIGN Bob Myers Department of Computer Science

  2. COP 3331: Object Oriented Software Engineering • What is Software Engineering (SE)? • Involves more than just coding • Problem Definition • Problem Analysis • High level system design (including hardware!) • Design of classes/objects • Implementation • Testing • Maintenance

  3. Modeling! • Modeling is a nice way to abstract and simplify some of the activities in software engineering • There are many modeling notations • UML - Unified Modeling Language • A nice way of representing things with diagrams • Different types of diagrams for use with different stages of software engineering • Works well with OOP.

  4. UML First Pass: Use Case Diagrams Package SimpleWatch Actor ReadTime SetTime WatchUser WatchRepairPerson Use case ChangeBattery Use case diagrams represent the functionality of the system from user’s point of view

  5. UML First Pass: Class Diagrams Class Multiplicity Association SimpleWatch 1 1 1 1 1 1 2 2 PushButton state push()release() LCDDisplay Battery load() Time now() blinkIdx blinkSeconds() blinkMinutes() blinkHours() stopBlinking() referesh() Attributes Operations Class diagrams represent the structure of the system

  6. :SimpleWatch :LCDDisplay :Time UML First Pass: Sequence Diagram Object :WatchUser pressButton1() blinkHours() pressButton1() blinkMinutes() pressButton2() incrementMinutes() refresh() pressButtons1And2() commitNewTime() stopBlinking() Message Activation Sequence diagrams represent the behavior as interactions

  7. Increment Hours Increment Minutes Increment Seconds UML First Pass: Statechart Diagrams Initial state State Event button2Pressed button1&2Pressed Blink Hours Transition button1Pressed button2Pressed button1&2Pressed Blink Minutes button1Pressed button1&2Pressed button2Pressed Blink Stop Seconds Blinking Final state

  8. Other SE issues • Requirements Elicitation and Analysis • Communication • Management Issues • Testing and Quality Assurance • Design Patterns • This is the stuff you will have to deal with in the real world, if you work for a company doing software development.

More Related