Scribd
Upload
0 views

Software_Project_Management_Notes

The document outlines key processes in Software Project Management, including Risk Management, Requirement Analysis, and Function Point Analysis. It details the steps involved in each process, such as risk identification, requirement elicitation, and functional component identification. Additionally, it discusses Object-Oriented Software Development and Black Box Testing methodologies, emphasizing their advantages and techniques.

Uploaded by

shaikhtas15
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0 views

Software_Project_Management_Notes

The document outlines key processes in Software Project Management, including Risk Management, Requirement Analysis, and Function Point Analysis. It details the steps involved in each process, such as risk identification, requirement elicitation, and functional component identification. Additionally, it discusses Object-Oriented Software Development and Black Box Testing methodologies, emphasizing their advantages and techniques.

Uploaded by

shaikhtas15
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Software Project Management & Engineering - Detailed Notes

Q16. How is Risk Management performed in Software Project


Management?

Risk Management Process:


1. Risk Identification:
- Recognize potential risks (technical, project, business, external).
- Tools: Brainstorming, Checklists, Historical Data.

2. Risk Analysis:
- Assess:
- Probability (High, Medium, Low)
- Impact (Cost, Time, Quality)
- Techniques: Qualitative & Quantitative Analysis.

3. Risk Prioritization:
- Use Risk Matrix to rank risks based on severity.

4. Risk Planning:
- Mitigation Plan: Actions to reduce probability/impact.
- Contingency Plan: Backup plans if risk occurs.

5. Risk Monitoring & Control:


- Continuous tracking of risks.
- Update risk register.
- Conduct regular reviews.

--------------------------------------------------

Q17. Describe Requirement Analysis and Specification in Software


Project Management.
Requirement Analysis:
1. Requirement Elicitation:
- Techniques: Interviews, Surveys, Observation, Document
Analysis.

2. Requirement Analysis Activities:


- Resolve conflicts.
- Remove ambiguities and redundancies.
- Prioritize requirements.

3. Modeling Requirements:
- Use Use Case Diagrams, DFDs, ERDs to represent requirements
visually.

Requirement Specification:
- Prepare Software Requirement Specification (SRS) document.

SRS Components:
1. Functional Requirements: Specific features (e.g., user login,
transaction processing).
2. Non-Functional Requirements: Performance, Security, Scalability,
Usability.
3. System Interfaces: External hardware, software, or other system
interactions.
4. Constraints & Assumptions: Technology limitations, legal
constraints.

--------------------------------------------------

Q18. Discuss Function Point Analysis.

Steps in Function Point Analysis (FPA):


1. Identify Functional Components:
- External Inputs (EI)
- External Outputs (EO)
- External Inquiries (EQ)
- Internal Logical Files (ILF)
- External Interface Files (EIF)

2. Assign Weights: Based on complexity (Low, Average, High).


3. Calculate Unadjusted Function Points (UFP): Sum the weighted
counts.
4. Apply Adjustment Factor: Based on factors like performance,
reusability.
5. Final Function Points Calculation: Final FP = UFP × Adjustment
Factor

Applications:
- Project size estimation
- Cost estimation
- Productivity measurement

--------------------------------------------------

UNIT 2

Q1. What is Object-Oriented Software Development (OOSD)?

Definition:
- A methodology based on objects which bundle data and behavior.

Key Concepts:
1. Object: Contains data (attributes) and behavior (methods).
2. Class: Template for creating objects.
3. Encapsulation: Hiding internal details.
4. Inheritance: Reusing existing classes.
5. Polymorphism: One interface, multiple forms.
6. Abstraction: Simplifying complex reality.

Phases of OOSD:
1. Object-Oriented Analysis (OOA)
2. Object-Oriented Design (OOD)
3. Object-Oriented Programming (OOP)

Advantages:
- Modularity, Reusability, Maintainability, Scalability.

--------------------------------------------------

Q2. How is Black Box Testing performed in Software Engineering?

Definition:
- Testing software without knowledge of internal code/logic.

Steps:
1. Understand Requirements: Study specifications, use cases.
2. Design Test Cases: Inputs + Expected Outputs.
3. Execute Tests: Provide inputs, observe outputs.
4. Compare Results: Match actual outputs with expected results.
5. Report Defects: Log deviations and bugs.

Common Black Box Testing Techniques:


1. Equivalence Partitioning
2. Boundary Value Analysis
3. Decision Table Testing
4. State Transition Testing

Advantages:
- No need to understand code.
- Helps find interface & functional errors.

You might also like