News Articles for
COM 3205 Fundamentals of Software Engineering
Winter 2001

• Syllabus
• Requirements for the first assignment
• Tools for the assignments
• Earlier edition of the textbook
• XMI format
• Example of the use of UML
• Example of tracing
• Exporting XMI files
• Questions about scenarios
• Questions about use cases
• Infrastructure and nodes
• What is an actor?
• Questions about the IDVTCS
• What the textbook says about use cases and scenarios
• Grader's address and Assignment #1 submission deadline
• Naming actors
• Sequence diagrams in Assignment #1
• Communication as a use case
• Example of scope
• How to show the traces
• Where is the project goal documented?
• Negotiation
• Still more suggestions about how to submit your homework
• More on submitting homework
• Still more on submitting homework
• Tracing
• TCP/IP can be assumed
• Preliminary solution to Assignment #1
• Due date has been postponed
• What should the subsystems be?
• Is a tool such as MS Project necessary?
• Tracing
• There is class on Monday, February 19
• Collaboration diagrams
• Analysis model objects
• Sequences diagrams do not have a loop construct
• Grading Scale for Assignment #1
• Files generated by javadoc
• Branching in sequence diagrams
• Subsystem analysis
• Gantt charts
• What are analysis classes?
• The task network
• Request Information Scenario
• Collaboration diagrams should avoid implementation artifacts if possible
• Collaboration diagrams should avoid implementation artifacts if possible
• Collaboration diagrams should avoid implementation artifacts if possible
• Subsystems should not be used as objects in sequence diagrams
• Choosing subsystems and analysis classes
• Gantt chart question
• Question about Location and Sense Use Cases
• Subsystems and sequence diagrams
• Question about Sense Use Case
• Question about Sense Use Case
• System architecture
• Question about the Sense Use Case
• Question about the Gantt chart
• Identifying control objects
• Object names in sequence/collaboration diagrams
• The meaning of X in a sequence diagram
• Deliverables for Assignment #3
• Class diagrams
• Statecharts versus sequence diagrams
• What information in the database may be requested?
• The University is closed on 3/5/01
• There was an error in one sequence diagram
• Obtaining results from the GPS and sensors
• Environment and obstacle
• Office hours this week
• System architecture
• Placing classes in subsystems
• Identifying design classes
• Analysis versus design classes
• Truncated news article
• Truncated news article
• Truncated news article
• Choosing the global control flow
• Question about sensor functionality
• Final project deliverables
• Submitting the final project
• Exceptions
• Question about design classes
• You must send Assignment #3 part 4 electronically
• Deadline
• Off-the-shelf components
• Nodes and obstacles
• Makeup class
• Finding design classes
• Obstacles
• Preconditions, postconditions and invariants
• The <> relationship
• Verifying locations
• Messages and Associations
• Callbacks
• Makeup class
• Using a class in the diagram of a different subsystem
• Remote information request
• Negotiation
• Design patterns
• Information in the database
• Sense Scenario
• Hard real-time system
• Design patterns can cross subsystems
• Class diagrams
• Sensor and Database
• Questions about the database
• Determining what is current
• Callback objects
• Sensor is dependent on Database
• Streets and intersections should have sensors
• Example of a facade class
• More database questions
• Parameter and return value classes
• Callbacks again
• The Database Management subsystem is the lowest layer
• Actors and entities
• Missing return statement
• Classes occurring in several class diagrams
• Effects of changing the dependencies of the subsystem decomposition
• Rationale for the global control flow
• Associations with Exception classes
• Representing global flow control
• Additional subsystem decompositions