CS615 Midterm Subjective

CS615 - Software Project Management · Reference Short Notes for Mid Term Papers · Muhammad Faisal Dar · MIT 4th Semester · The 80:20 Rule: (page 11)

The 80:20, rule was originated by Vilfredo Pareto, an Italian economist who studies the distribution of wealth in a variety of countries around 1900. He discovered a common phenomenon: about 80% of the wealth in most countries was controlled by a consistent minority -- about 20% of the people. Pareto called this a "predictable imbalance." His observation eventually became known as either the "80:20 rule" or " Pareto's Principle."

A project has five phases: (page 13)

⇒ Initiation ⇒ Planning ⇒ Executing ⇒ Controlling ⇒ Closing

Project Life Cycle includes the following Phases: (page 16)

A. Concept Phase B. Requirements Phase C. Design Phase D. Development Phase E. Operation Phase

(page 29)

In managing competing project requirements Project managers often talk of a triple constraint:

• Project scope
• Time and
• Cost

(page 31)

The role of the Leader in project management is one of great responsibility. It's the project manager's job to direct and supervise the project from beginning to end. Here are some other roles:

(a) Leadership (b) Communications (c) Problem Solving (d) Negotiating (e) Influencing the Organization (f) Mentoring (g) Process and technical expertise

PM’s nine Knowledge Areas

(page37)

1. Project Integration Management
2. Project Scope Management
3. Project Time Management
4. Project Cost Management
5. Project Quality Management
6. Project Human Resource Management
7. Project Communications Management
8. Project Risk management
9. Project Procurement Management

Difference between Leaders and Managers: (page45)

Leadership is path finding Management is path following Management is about doing things right Leadership is about doing the right things

Supporting detail

(page57)

Supporting detail for organizational planning varies by application area and project size. Information frequently supplied as supporting detail.

Software engineering practices: (page58)

•  Span of control
•  Authority
•  Responsibility
•  Delegation
•  Chain of command
•  Accountability
•  Line authority
•  Staff departments

The Software Crisis: (page60)

Some of the reasons to which you can attribute the software crisis include:

• Software developers used-multiple programming languages.
• Most of the requirements were complex with regard to the existing capabilities,
• Software developers poorly mapped requirements to the actual product.
• Software maintenance was costly.
• Hardware developed at a faster rate than software.

Status reports: (page62)

Status reports should be required from every member of the development team, without exception. The reports should be submitted periodically, usually weekly or bi-weekly, and should contain at least the following three sections.

1. Activities during the report period
2. Planned activities for the next report period
3. Problems

A typical software project includes the following phases: (page67)

•  Software requirement analysis phase
•  Software Design Phase
•  Software Planning Phase
•  Software construction phase
•  Software testing phase
•  Software acceptance and maintenance phase