Software Project Management MCQs

• Software Project Management (SPM) and Systems Analysis and Design (SAD) are crucial aspects of software development.
• These notes cover 500 MCQs related to SPM and SAD.

Software Project Management (SPM) MCQs

• SPM involves planning, organizing, monitoring, and controlling software projects.

• Its primary goal is to deliver a software product on time, within budget, and meeting requirements.

• A project is a temporary endeavor undertaken to create a unique product, service, or result.

• Project management includes processes like initiation, planning, execution, monitoring & controlling, and closure.

• Scope management defines and controls what is and is not included in the project.

• Time management involves estimating, scheduling, and controlling project activities.

• Cost management includes planning, estimating, budgeting, and controlling project costs.

• Quality management ensures that the project meets the required quality standards.

• Human resource management involves organizing and leading the project team.

• Communication management focuses on generating, collecting, disseminating, and storing project information.

• Risk management identifies, analyzes, and responds to project risks.

• Procurement management acquires goods and services from outside the organization.

• Project integration management coordinates all project management processes.

• Work Breakdown Structure (WBS) is a hierarchical decomposition of the project scope.

• Gantt charts are used for project scheduling and visualizing timelines.

• Critical Path Method (CPM) identifies the longest sequence of activities to determine project duration.

• Earned Value Management (EVM) integrates scope, time, and cost data to measure project performance.

• Project stakeholders are individuals or groups that have an interest in the project.

• A project management office (PMO) standardizes project-related governance processes.

Systems Analysis and Design (SAD) MCQs

• SAD is a systematic approach to developing information systems.

• It involves analyzing the business problem or opportunity and designing a solution.

• Systems analysis involves understanding the current system and defining the requirements for the new system.

• Systems design involves creating a blueprint for the new system.

• The System Development Life Cycle (SDLC) provides a structured framework for system development.

• Common SDLC models include Waterfall, Agile, Spiral, and Iterative.

• Requirements elicitation involves gathering information from stakeholders about system needs.

• Functional requirements specify what the system should do.

• Non-functional requirements specify how the system should perform.

• Data flow diagrams (DFDs) model the flow of data through a system.

• Entity-relationship diagrams (ERDs) model the data structures and relationships in a system.

• Use case diagrams describe the interactions between users and the system.

• Unified Modeling Language (UML) is a standardized modeling language for software development.

• System architecture defines the overall structure of the system.

• User interface design focuses on creating an intuitive and user-friendly interface.

• Database design involves creating the data structures and relationships to store system data.

• Testing ensures that the system meets the specified requirements.

• Implementation involves putting the system into operation.

• Maintenance involves keeping the system running and making necessary changes.

• Agile methodologies emphasize iterative development, collaboration, and flexibility.

• Waterfall model is a sequential, phase-based approach to system development.

• Spiral model combines iterative development with risk management.

• Prototyping involves creating a preliminary version of the system to gather feedback.

Overlapping Concepts

• Project management techniques are used to manage SAD projects.
• Understanding system requirements is crucial for project scope definition.
• Communication and stakeholder management are important in both SPM and SAD.
• Risk management is essential in both software project management and system development.
• Quality assurance is a key activity in both disciplines.
• Configuration management ensures proper control and tracking of software and system components.
• Change management manages the transitions and changes associated with projects and system implementations.

Detailed Breakdown

• Scope Creep: Uncontrolled changes or continuous growth in a project’s scope

• Triple Constraint: Scope, Time and Cost form the vertices of a triangle with Quality as the central theme.

• Requirements Traceability Matrix: A document that links requirements throughout the validation process.

• Risk Assessment: Identifying potential risks and evaluating their impact.

• Configuration Management: Systematically manage changes to the project's product configuration.

• Feasibility Study: Determines if the project is viable technically, economically, and operationally.

• System Requirements Specification (SRS): A document detailing what a system should perform.

• Data Dictionary: Centralized repository of information about data.

• Black Box Testing: Testing without knowledge of the internal structure or code of the system.

• White Box Testing: Testing with knowledge of the internal structure or code of the system.

• Project Charter: A document that formally authorizes the existence of a project.

• Stakeholder Analysis: Identifying and analyzing the needs of project stakeholders.

• Critical Path: Longest sequence of activities in a project plan which determines the shortest possible project duration.

• Resource Allocation: Assigning resources to project activities.

• Project Closure: Formalizing project completion and disseminating information.

• Version Control Systems: Tools like Git manage changes to source code over time.

• Object-Oriented Analysis and Design (OOAD): A software engineering approach that models a system as a group of interacting objects.

• Use Case: Describes a sequence of interactions between a system and its users.

• UML Diagrams: Standardized visual language for specifying, constructing, and documenting software systems.

• User Stories: Short, simple descriptions of a feature told from the perspective of the user.

• Test Cases: Specific scenarios to test the system.

• Risk Mitigation: Actions taken to reduce the likelihood or impact of a risk.

• Earned Value: A measure of the value of work performed expressed in terms of the budget authorized for that work.

• Return on Investment (ROI): A profitability metric used to evaluate the efficiency of an investment.

• Total Cost of Ownership (TCO): An estimate of all direct and indirect costs associated with acquiring and using a product or system.

• Agile Manifesto: A statement of values and principles behind Agile software development.

• Scrum: An Agile framework for managing complex projects.

• Kanban: A visual system for managing workflow.

• Sprint: Short, time-boxed periods in Scrum during which a team works to complete a set amount of work.

• Daily Stand-up: A short meeting held each day in Scrum to coordinate the team's activities.

• Product Backlog: A prioritized list of features or requirements for the system.

Key Terms to Understand

• Activity on Node (AON): A project management technique where activities are represented as nodes and dependencies as arrows.

• Bottom-Up Estimating: Estimating project costs by summing the estimates of individual work packages.

• Change Control Board (CCB): A group responsible for reviewing and approving changes to the project.

• Cost-Benefit Analysis: A systematic approach to estimating the strengths and weaknesses of alternatives.

• Decision Tree Analysis: A diagramming technique to analyze and evaluate decisions under uncertainty.

• Delphi Technique: Gathering expert opinions to forecast future outcomes.

• Fishbone Diagram (Ishikawa): A cause-and-effect diagram to identify potential causes of a problem.

• Force Field Analysis: A technique for identifying forces driving and restraining change.

• Gap Analysis: Comparing actual performance with potential or desired performance.

• Heuristic: A problem-solving approach using practical methods, not always guaranteed to be optimal.

• Ishikawa Diagram: Another name for the fishbone diagram used for cause-and-effect analysis.

• Just-In-Time (JIT): An inventory management strategy to reduce waste.

• Knowledge Management: The process of creating, sharing, using and managing the knowledge and information of an organization.

• Lessons Learned: Documenting experiences and insights gained during a project.

• Monte Carlo Simulation: A computerized technique that generates multiple scenarios of potential outcomes.

• Net Present Value (NPV): The difference between the present value of cash inflows and the present value of cash outflows over a period of time.

• Pareto Chart: A bar chart showing the relative frequency of different categories.

• Quality Assurance (QA): Systematic processes to ensure that a product or service meets specified requirements.

• Regression Testing: Re-running tests after changes to ensure no new defects have been introduced.

• Six Sigma: A set of techniques and tools for process improvement.

• SWOT Analysis: Strengths, Weaknesses, Opportunities, and Threats analysis.

• Timeboxing: Allocating a fixed time period for an activity.

• Use Case Diagram: A visual representation of the interactions between actors and the system.

• Validation: Ensuring that the software meets the user's needs.

• Verification: Ensuring the software meets its specifications.

• Waterfall Model: A sequential design process, often used in software development processes.

• eXtreme Programming (XP): An Agile software development framework that aims to improve software quality and responsiveness to changing customer requirements.

• Zero Defects: A quality management goal to eliminate all defects.