1. Overview of Software Project Management Review – Class 5 UML diagrams cont Overview of Software Project Management - Communication CEN 4010 Class 6 – 09/15

2. CEN 4010 Class 6 - 09/152 More Class Diagrams Points to note: –Object names are underlined. –Class names start with an uppercase letter. –Object names are unique. A link represents a connection between two objects. An object diagram shows a set of objects and their relationships. (Requirement analysis) A relationship is a connection among things.

3. CEN 4010 Class 6 - 09/153 More Class Diagrams cont A dependency is a using relationship that states a change in specification of one thing may affect another thing that uses it, but not necessarily the reverse. [Booch ’99] Department name:string ssnList:string update(emp:Employee) printList() Employee Dependency relationship

4. CEN 4010 Class 6 - 09/154 More Class Diagrams cont A generalization is a relationship between a general thing (superclass or parent) and a more specific kind of thing (subclass or child). A.k.a “is-a-kind-of” relationship. Note objects of the child maybe used anywhere the parent may appear, but not the reverse. [Booch ’99] A child inherits the properties of it parents. An operation of the child that has the same signature as an operation of the parent overrides the operation of the parent.

5. CEN 4010 Class 6 - 09/155 More Class Diagrams cont Employee ssn: string name: string getName(): string getSSN(): string Manager mangID: string getMangID(): string Clerk station: int getStation(): int base class derived classes Generalization

6. CEN 4010 Class 6 - 09/156 More Class Diagrams cont An association is a structural relationship that specifies that objects of one thing are connected to objects of another. Graphically represented as a solid line connecting the same or different classes. Four adornments apply to associations: 1.Name – describes nature of relationship. 2.Role – identifies role played in relationship. 3.Multiplicity – how many objects may be connected. 4.Aggregation – is a “whole/part” or “has-a” relationship; special kind of association.

7. CEN 4010 Class 6 - 09/157 More Class Diagrams cont PersonCollege employeeemployer 1..* 1 multiplicity roles DepartmentCollege *1 partwholeaggregation Works for name Association

8. CEN 4010 Class 6 - 09/158 More Class Diagrams cont Class diagrams are used –for describing the structure of a system. –during analysis to formalize domain knowledge. Classes represent participating objects found in use cases and sequence diagrams, and describe their attributes and operations. A package is a grouping of model elements, such as use cases, classes, or activities, defining scopes of understanding.

9. CEN 4010 Class 6 - 09/159 More Class Diagrams cont Packages are used to model complexity in a system (see p. 67 in text) SIS Schedule Classes Submit Grades Check Grades Some of the use cases in the FIU Student Information System. Student Faculty

10. CEN 4010 Class 6 - 09/1510 Overview of S/W Project Management Software engineering is a collaborative effort. Involves domain experts, analysts, designers, programmers, managers, etc.. Communication is essential! Definitions:  Communication mode - a type of information exchange that has defined objectives and scope.  Communication mechanism - a tool or procedure that can be used to transmit and receive information and support a communication mode.

11. CEN 4010 Class 6 - 09/1511 Overview of S/W Project Manag. cont Modes of communication: Scheduled – Problem defn., client reviews, project reviews, inspection/walkthroughs, status review, brainstorming, releases, postmortem. Event-driven – Request for clarification, request for change, issue resolution. Go through Tables 3.1 and 3.2

12. CEN 4010 Class 6 - 09/1512 Overview of S/W Project Manag. cont Mechanisms of communication: Synchronous – Hallway conversations, questionnaires and structured reviews, meetings, same-time, and different-place groupware. Asynchronous – Email, newsgroups, WWW, and Lotus Notes.

13. CEN 4010 Class 6 - 09/1513 Overview of S/W Project Manag. cont Meetings: Primary facilitator – responsible for –organizing the meeting and guiding its execution. –writing the agenda describing the objective and the scope of the meeting. Minute taker – responsible for recording the meeting i.e. information for the diary. Time keeper – responsible for keeping track of time and notifying the facilitator if a discussion consumes more time than is allocated. A vote might be required to continue discussion or move on to the next point.

14. CEN 4010 Class 6 - 09/1514 Project Stuff Class Project: Select a team leader for each phase. Keep a diary (minutes) of the meetings and other activities e.g. class presentation. Try to limit the number of uses cases to four (4) per team member. At team meetings each team member should present the use cases they worked on.

15. CEN 4010 Class 6 - 09/1515 Project Stuff Class Project: The first pass of the use cases should be completed by 09/29. That is, use cases should be written and UML diagrams with documentation completed. For each use case identify the non-functional requirements. I will ask a team member from each team to present a use case in class week 09/27, 09/29.

16. CEN 4010 Class 6 - 09/1516 Questions Use case template Example use case SRD document outline