Overview of Software Project Management

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

2. 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. CEN 4010 Class 6 - 09/15

3. 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] Dependency relationship Department name:string ssnList:string Employee update(emp:Employee) printList() CEN 4010 Class 6 - 09/15

4. 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. CEN 4010 Class 6 - 09/15

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

6. 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: • Name – describes nature of relationship. • Role – identifies role played in relationship. • Multiplicity – how many objects may be connected. • Aggregation – is a “whole/part” or “has-a” relationship; special kind of association. CEN 4010 Class 6 - 09/15

7. More Class Diagrams cont Association multiplicity 1..* 1 Works for Person College employee name employer roles * 1 Department College part aggregation whole CEN 4010 Class 6 - 09/15

8. 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. CEN 4010 Class 6 - 09/15

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

10. 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. CEN 4010 Class 6 - 09/15

11. 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 CEN 4010 Class 6 - 09/15

12. 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. CEN 4010 Class 6 - 09/15

13. 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. CEN 4010 Class 6 - 09/15

14. 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. CEN 4010 Class 6 - 09/15

15. 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. CEN 4010 Class 6 - 09/15

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