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
-
Project Preparation > Business Blue Print > User Acceptance > Go Live
-
Project Preparation > Realization > Business Blue Print > Go Live
-
Project Preparation > Business Blue print > Realization > Final Preparation > Go live and support
-
Project Preparation > Business Blue print > Realization > Final Preparation > Data Migration > Go live and support
C
Correct answer
Explanation
The Accelerated SAP (ASAP) methodology is structured into five sequential phases to ensure efficient ERP implementation: Project Preparation, Business Blueprint, Realization, Final Preparation, and Go-Live and Support. This standard lifecycle guides the planning, configuration, testing, and deployment of SAP systems.
-
Model View Controller
-
Composite Entity
-
Fast Lane Reader
-
View Helper
C
Correct answer
Explanation
Fast Lane Reader is specifically designed to improve read performance for tabular data by bypassing complex EJB (Enterprise JavaBean) overhead. It directly accesses data using simpler mechanisms like JDBC, providing faster reads for simple queries. This pattern is ideal when you need quick, read-only access to tabular data without full transactional overhead.
-
Init
-
setup
-
teardown
-
tearup
-
the documentation is poor, so it takes longer to find out what the software is doing.
-
wages are rising
-
the fault has been built into more documentation,code,tests, etc
-
none of the above
C
Correct answer
Explanation
Faults discovered later require rework across more artifacts: code that depends on the faulty logic, tests that assumed incorrect behavior, documentation describing the wrong behavior, and potentially deployed systems. This cascade increases cost exponentially. Option A is a specific case, not the general principle.
-
Header
-
Title
-
Detail
-
JasperReports
D
Correct answer
Explanation
The root element is mandatory in every JRXML file as it defines the entire report structure and contains all other sections. All other tags like header, title, and detail are optional child elements within this root.
-
JRPrint file
-
Jasper file
-
html file
-
None of the above
B
Correct answer
Explanation
Compiling a JRXML source file (.jrxml) in JasperReports produces a compiled Jasper file (.jasper), which contains the serialized report template. The JRPrint file is only generated after filling the report with data, making the distractors incorrect.
-
Skeleton of the original report
-
compiled XML file
-
Plain XML file with data
-
Report Template file structure
A,D
Correct answer
Explanation
JRXML files are source XML files containing the report template structure and layout definition. They serve as the blueprint that gets compiled into .jasper files and do not contain actual report data.
-
Business Analyst
-
Solution Designer / IT Architect
-
Test Manager
-
Delivery Manager
A
Correct answer
Explanation
Business Analysts are primarily responsible for identifying and documenting the business impact of requirements or business processes. They work with stakeholders to understand business value and consequences. Option A correctly assigns this responsibility to Business Analysts, who bridge business needs and technical solutions.
-
Business Analyst
-
Solution Designer / IT Architect
-
Test Manager
-
Delivery Manager
B
Correct answer
Explanation
Solution Designers and IT Architects are primarily responsible for identifying the probability of failure for requirements or business processes. They assess technical feasibility, system constraints, and implementation complexity. Option B correctly assigns this technical risk assessment to Solution Designers/IT Architects who understand technical challenges.
-
depends on project size
-
none
-
one
-
two
C
Correct answer
Explanation
Each repository in Informatica requires exactly one Repository Service to manage it. Multiple repositories would each need their own Repository Service, but a single repository is managed by one service instance.
-
MS Access
-
Microsoft SQL Server
-
File System
-
None of the Above
B
Correct answer
Explanation
Team Foundation Server 2010 uses Microsoft SQL Server as its backend data store for all version control, work item tracking, build data, and other metadata. It does not use MS Access or a file system for the backend.
-
Code Analysis
-
Branching
-
Shelving
-
Folder Diff
-
Parallel Development
-
Multiple Releases
-
Branch Visualization
-
None of the above
C
Correct answer
Explanation
Microsoft Visual Studio Team Foundation Server 2010 introduced Branch Visualization as a major new feature to help teams graphically view branching and merging relationships across projects. The other options were either present earlier or are general concepts.
-
During flow execution as process conrtol advances from one task to another
-
At the end of activity step,after invoking the method, but before any transition step
-
Upon database commit when any object is saved to database
-
All of the above
D
Correct answer
Explanation
Declare rules execute at multiple points in PEGA processing. Some run during flow execution as control moves between tasks, others at activity step boundaries after method invocation but before transitions, and Declare Trigger rules specifically run when objects are committed to the database. The declare keyword provides automatic rule execution across these contexts.
-
Class Structure, Properties, User Interface, Activities
-
Class Structure, Properties, Activities,User Interface
-
Properties, Class Structure, User Interface, Activities
-
Class Structure, Activities,Properties, User Interface
A
Correct answer
Explanation
SmartBuild in PEGA follows a logical development sequence starting with Class Structure (defining data model), then Properties (individual attributes), User Interface (forms and screens for user interaction), and finally Activities (business logic and processing). This sequence ensures foundational elements are established before building dependent components.