KSU SWE 3313 2025 TEST 2 QUESTIONS ANSWERED CORRECTLY
AGILE : Methods - Answers 1.Short Releases
2.Multiple Iterations
3.Incremental Development
4.User Involvement
5.Minimal Documentation
6.Informal Communication
7.Assuming Change
AGILE : Manifesto - Answers 1.Individuals/Interactions over Tools/Processes
2.Working Software over Comprehensive Documentation
3.Customer Collaboration over Contract Negotiation
4.Responding to change over Following plan dogmatically
SCRUM : Approach - Answers 1.Incremental and iterative development
2."Sprints" or small sections of functionality programmed in 2/3 week periods
SCRUM : Main Roles - Answers 1.Product Owner: Talks to users and helps to decide the content
of each sprint
2.SCRUM Master: Runs the Sprints
3.SCRUM Team: 7-8 members who develop the Sprints
Crystal : Criticality - Answers Criticality is the losses that a system malfunction would cause
Crystal : Project Classification - Answers 1.Clear : For non critical projects with 6-8 people
2.Orange : For critical projects with up to 40 people
3.Orange Web : For web development
Crystal : Methodologies - Answers 1.Larger methodologies for larger teams
2.Use heavier methodologies for more critical projects
3.Give preference to lighter methodologies, weight is costly
4.Give preference to interactive face-to-face communication rather than formal written
, documentation
5.Understand that people vary within a team and with time
6. Assume people want to be helpful and take initiative
XP : Core Values - Answers 1. Communication
2. Simplicity
3. Feedback
4. Courage
XP : Core Fundamentals - Answers 1. Rapid Feedback
2. Simplicity
3. Incremental Change
4. Embrace Change
5. Quality Work
XP : Basic Premises - Answers Proposes that only strictly necessary documentation is created,
where code and unit tests should serve as documentation
Requirements Engineering - Answers Activities related to the development and agreement of the
final set of requirement specifications
Requirement Engineering Activities - Answers 1.Elicitation
2.Documentation and Definition
3.Specification
4.Prototyping
5.Analysis
6.Review and Validation
7.Agreement and Acceptance
High Level Requirements - Answers Functional and Non-Functional Requirements, very general,
what program needs to do and how it needs to do it
6 Requirement Categories - Answers 1.Individual Functionality
2.Buisness Flow
AGILE : Methods - Answers 1.Short Releases
2.Multiple Iterations
3.Incremental Development
4.User Involvement
5.Minimal Documentation
6.Informal Communication
7.Assuming Change
AGILE : Manifesto - Answers 1.Individuals/Interactions over Tools/Processes
2.Working Software over Comprehensive Documentation
3.Customer Collaboration over Contract Negotiation
4.Responding to change over Following plan dogmatically
SCRUM : Approach - Answers 1.Incremental and iterative development
2."Sprints" or small sections of functionality programmed in 2/3 week periods
SCRUM : Main Roles - Answers 1.Product Owner: Talks to users and helps to decide the content
of each sprint
2.SCRUM Master: Runs the Sprints
3.SCRUM Team: 7-8 members who develop the Sprints
Crystal : Criticality - Answers Criticality is the losses that a system malfunction would cause
Crystal : Project Classification - Answers 1.Clear : For non critical projects with 6-8 people
2.Orange : For critical projects with up to 40 people
3.Orange Web : For web development
Crystal : Methodologies - Answers 1.Larger methodologies for larger teams
2.Use heavier methodologies for more critical projects
3.Give preference to lighter methodologies, weight is costly
4.Give preference to interactive face-to-face communication rather than formal written
, documentation
5.Understand that people vary within a team and with time
6. Assume people want to be helpful and take initiative
XP : Core Values - Answers 1. Communication
2. Simplicity
3. Feedback
4. Courage
XP : Core Fundamentals - Answers 1. Rapid Feedback
2. Simplicity
3. Incremental Change
4. Embrace Change
5. Quality Work
XP : Basic Premises - Answers Proposes that only strictly necessary documentation is created,
where code and unit tests should serve as documentation
Requirements Engineering - Answers Activities related to the development and agreement of the
final set of requirement specifications
Requirement Engineering Activities - Answers 1.Elicitation
2.Documentation and Definition
3.Specification
4.Prototyping
5.Analysis
6.Review and Validation
7.Agreement and Acceptance
High Level Requirements - Answers Functional and Non-Functional Requirements, very general,
what program needs to do and how it needs to do it
6 Requirement Categories - Answers 1.Individual Functionality
2.Buisness Flow
