Computer Knowledge
Software Development and Management
3,064 Questions
Software development and management focuses on the system development life cycle, enterprise architecture, and configuration management. It tests your familiarity with system analysis, design models, and IT project planning. This subject is essential for specialist and banking officer scale examinations.
System analysis and designSoftware development life cycleConfiguration managementEnterprise architectureObject oriented design
Software Development and Management Questions
-
Velocity
-
Burned down
-
SPRINTS
-
None of the above
A
Correct answer
Explanation
In SCRUM, velocity is the metric that measures a team's productivity - specifically, the amount of work (usually in story points or hours) the team completes per sprint. A burn-down chart tracks remaining work over time, sprints are time-boxes, and velocity is used for predictable planning.
-
Product owner
-
SCRUM Master and team
-
End users / other stakeholders
-
All of the above
D
Correct answer
Explanation
Sprint reviews are open to all stakeholders including the Product Owner, Scrum Master, team members, and importantly, end users and other external stakeholders. The purpose is to demonstrate working software and gather feedback, so transparency and broad participation are encouraged.
-
system planning and selection
-
systems design
-
systems analysis
-
systems implementation and operation
-
systems evaluation
C
Correct answer
Explanation
Conceptual data modeling occurs during systems analysis, which is when requirements are gathered and analyzed. It happens in parallel with other requirements analysis activities to understand what data the business needs before detailed technical design begins.
-
REPOSITORY
-
DESIGNER
-
MAPPING
-
FLOWCHART
A
Correct answer
Explanation
The question asks which option is NOT related to Informatica. Repository, Designer, and Mapping are all core Informatica PowerCenter components. A Flowchart is a general diagramming tool, not specific to Informatica - making it the correct answer to the negative question.
-
Water falls model
-
Spiral Model
-
V-model
-
Linear model
C
Correct answer
Explanation
The V-Model (option C) emphasizes that for every development phase, there is a corresponding testing phase. Testing begins in parallel with development activities - test planning starts during requirements, test cases during design, etc. Waterfall has sequential phases. Spiral is iterative risk-based. Linear is sequential like waterfall.
-
Plan(P)------>Check(C)------>Act(A)----->Do(D)
-
Plan(P)------>Do(D)------>Check(C)----->Act(A)
-
Plan(P)------>Do(D)------>Act(A)----->Check(C)
-
None
B
Correct answer
Explanation
The Plan-Do-Check-Act (PDCA) cycle follows the sequence: Plan (P) → Do (D) → Check (C) → Act (A). Option B correctly shows this order. This is the Deming Cycle/Shewhart Cycle used for continuous improvement in quality management.
-
Establish robust Foundation
-
Design Intent driven processing
-
Design Event Driven Processing
-
Build For Change
C
Correct answer
Explanation
Pega’s official guardrails guide developers to build robust, maintainable applications. Core guardrails include establishing a robust foundation, designing intent-driven processing, and building for change. While event-driven concepts exist in software architecture, Design Event Driven Processing is not defined as a standard Pega guardrail.
-
Assign-WorkList
-
Assign-WorkBasket
-
Either
-
None
C
Correct answer
Explanation
An assignment in Pega is an instance of either the Assign-Worklist class (when assigned to an individual operator) or the Assign-Workbasket class (when assigned to a work queue/basket). Therefore, 'Either' is correct.
-
Rule-Message
-
Rule-Error-Message
-
Rule-Set-Message
-
Rule-Obj-Message
A
Correct answer
Explanation
Rule-Message rules define reusable error message text and templates in Pega. These messages are associated with properties or pages to flag validation issues, whereas other listed options are not valid Pega rule types.
-
Only Project Risks
-
Only Product Risks
-
Project Risks and Product Risks
-
Project Risks or Product Risks
B
Correct answer
Explanation
According to ISTQB risk categorization, poor software characteristics like poor performance, poor usability, or poor security are classified as Product Risks. Product risks are risks that the software will not meet its quality characteristics. Project Risks are different - they're about schedule, budget, resources, and organizational issues. Options A, C, D are incorrect because poor software quality is specifically a product risk, not a project risk.
-
Water Fall Model
-
V-Model
-
RAD Model
-
Spiral Model
B
Correct answer
Explanation
The V-Model is specifically designed to have testing levels that mirror development levels, but it allows for customization based on project needs. Additional testing levels like component integration and system integration can be inserted as needed. Waterfall has fixed sequential phases, RAD focuses on rapid prototyping, and Spiral is risk-driven with iterative cycles; all are less flexible about testing level insertion than V-Model.
-
Microsoft for threat modelling
-
HP for performance testing of applications
-
Symantec for security testing
-
Fortis for vulnerability assessments
A
Correct answer
Explanation
STRIDE is a threat modeling methodology developed by Microsoft. It's an acronym for Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege - categories of security threats. Option A is correct. Options B (HP for performance), C (Symantec for testing), D (Fortis for assessments) are incorrect.
-
Release of CR
-
maintenance of application
-
release of patch
-
interim release of CR
C
Correct answer
Explanation
A patch is a software update designed to fix a bug or vulnerability identified in production after the product is already released. Terms like 'release of patch' accurately represent this interim update, whereas 'maintenance' is a broad phase rather than the release package itself.
-
The execution support
-
Assembly name
-
Application_ReleaseRequest state
-
Application_Authenticate request
-
Application_Begin request
C
Correct answer
Explanation
This method is called to store any state associated with this session.
-
Static method
-
Application_EndRequest
-
Windows form
-
DoStackSnapshot
-
The execution support
D
Correct answer
Explanation
This method uses the same stack walker used by the garbage collector, security system, etc.