Title: Project Management, Class Diagrams and Exam Review
1Project Management, Class Diagrams and Exam Review
2Agenda
- Lab 5 next Friday 4 Person Teams
- Where are we?
- Project Management Lecture
- UML Class Diagrams
- Exam Review
3Why do Planning?
- Tells the team what has to be done
- Builds a shared understanding of project
- Builds shared commitment to project
4Project Management
- Meeting Management
- Decision Making
- Scheduling
- Estimation
5Meeting Management
- Have an agenda
- Start/Stop on time
- Make decisions
- Have a strawman
- Keep on topic
- Have recorder and timekeeper
- Handle dysfunctional behavior
6Sample Agenda
Review Previous Decisions 5 minutes
Analyze Requirements 15 minutes
Create WBS 20 minutes
Summarize Decisions 5 minutes
7Making Decisions 9 Step Plan
- Define Problem
- Decide on method of attack
- Generate alternatives
- Test alternatives for reality
- Choose alternative
- Plan for action
- Implement plan
- Evaluate effectiveness
- Determine next steps
8Scheduling
- Realistic Schedule
- Overly Optimistic Schedules
- Impossible Schedules
Completion P
Schedule
9Techniques
- Forward Plan
- Backwards Plan
What do we have to do?
What has to be done first?
How long does it take?
How will we monitor our progress?
10Determining Tasks
Work Breakdown Structure (WBS) avoid
design to organization
Mail Utilities
1. Preparation
2. Design
3. Implementation
4. Test
1.1 Mail Formats
2.1 Module ID
4.2 UT
4.1 Plan
4.3 IT
3.1 Code Modules
3.2 Create Make
11Determine Dependencies
3.2
12Determine Durations
3.2
0745 Fri
0800 Fri
SWAG
13Schedule
- Schedules Tasks Dependencies Milestones
Resources - What is the sequence we are doing things?
- Who is responsible for each thing?
- What checkpoints do we have to detect when things
are going bad?
14Project Management for Labs
- First Lab
- Team meets and analyzes NFO
- Before leaving lab show your TA
- Team member names, mail ids
- Team name
- Preliminary WBS (Doesnt have to be formal)
- Preliminary Design Ideas
- CVS Plan
- Date of next meeting
15Project Management for Labs
- Second Lab (for multi-week labs)
- Before Leaving lab show TA
- Revised WBS
- Task Progress (Person-Hours Worked)
- Current Design
- Estimate of of code completed
- Problems/Issues
- ID design components that are not started
16Class Diagrams
- A static picture of the design
- What are the classes, their attributes and
operations, and their relationships - We are covering this early so you can use the
information on your early projects.
17Really basic class diagram
Employee
Company
name String age int
name String
getSalary int
Major public classes, operations, attributes
18Exam Review
Quality Process Product Relationship
Error Lifecycle
Defns Error, Fault(Defect/Bug), Failure
Code Standards / Reviews
Team vs Groups
Communications Modes Noise Channels
Active Listening Feedback
Team Lifecycle
Team Roles
Importance of Team Rules
MBTI in situation
Problem Team Members
Project Plans
OLD EXAMS POSTED ON WEB!!!!