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
-
.mymetadata file
-
.myeclipse folder
-
an ejb-jar.xml file
-
An application.xml
A
Correct answer
Explanation
When creating a Web Application in MyEclipse, the .mymetadata file is automatically added to the project structure. This file stores MyEclipse-specific configuration and deployment settings for the web application. The .myeclipse folder and deployment descriptors like ejb-jar.xml serve different purposes.
-
It defines MyEclipse-specific information such as the location of the web-root folder and other important details required by MyEclipse web tools for their proper operation.
-
It is an optional file and may contain some project related information.
-
It is an empty folder to cache information.
-
None of these
A
Correct answer
Explanation
The .mymetadata file is a configuration file generated by MyEclipse to store project-specific metadata, such as the context root, web-root folder location, and project type, which are required for deployment and tooling operations.
-
Tomcat
-
Oracle
-
BEA
-
All of the above
D
Correct answer
Explanation
MyEclipse is an IDE that supports integration with various application servers and servlet containers, including Apache Tomcat, Oracle WebLogic, and BEA WebLogic. Thus, all of the listed servers can be plugged in.
-
Interface Injection
-
Setter Injection
-
Constructoir Injection
-
Constructor Arguments
A,B,C
Correct answer
Explanation
Inversion of Control/Dependency Injection in Spring can be implemented through three main types: Interface Injection (where dependencies are injected through interfaces), Setter Injection (through setter methods), and Constructor Injection (through constructor parameters).
-
At least one <servlet> element must be present.
-
<welcome-file> is a child element of <welcome-file-list>.
-
<web-application> is the root element
-
<servlet> elements must all be declared before <servlet-mapping> elements.
-
At least one element must be present.
B,E
Correct answer
Explanation
In Java web.xml deployment descriptors: (A) is false - servlet elements are optional. (B) is true - is a child of . (C) is false - the root element is , not . (D) is false - servlet and servlet-mapping elements can be in any order. (E) is true - at least one element must be present. The correct answers are B and E.
-
Describe Baseline Business Architecture
-
To Select relevant tools and techniques to be used in association with selected view points
-
To Select the relevant architecture view points that will enable the Architect to demonstrate how the stake holder concerns are addressed in Business Architecture
-
To Define the Business Requirements
-
All of the Above
D
Correct answer
Explanation
Phase B Business Architecture focuses on describing the baseline and target architectures, selecting tools and viewpoints, and addressing stakeholder concerns. Defining business requirements happens in earlier phases (Preliminary/Phase A), making D the exception.
-
Business Process Models
-
Use-Case Models
-
Class Models
-
Information Exchange Matrix
-
Traceability Matrix
E
Correct answer
Explanation
Business Process Models, Use-Case Models, Class Models, and Information Exchange Matrix are all modeling techniques for capturing business aspects. The Traceability Matrix is a requirements management tool for tracking requirements to implementations, not a business modeling tool.
-
Process Gap
-
Tools Gaps
-
Financial Gaps
-
Information Gaps
-
No one of the above
E
Correct answer
Explanation
The question asks which is NOT a suggested step for gap analysis. All the options listed (Process Gap, Tools Gaps, Financial Gaps, Information Gaps) are valid gap types that should be analyzed. Since none of them should be excluded from gap analysis, E (none of the above) is correct.
-
Deliverable base-lining
-
Defect prevention
-
Management reporting
-
None of the above
A
Correct answer
Explanation
Defect Management focuses on tracking logged defects after they're found, not preventing them upfront. The process includes defect prevention activities, management reporting, and tracking - but deliverable base-lining is a configuration management activity, not part of defect management workflow.
-
Refined statements of business goals and strategic drivers
-
Architecture Principles
-
Baseline Technology Architecture
-
Target Application Architecture
-
All of the above
E
Correct answer
Explanation
Phase B (Business Architecture) of TOGAF ADM receives inputs from the Preliminary Phase and Phase A. These include refined business goals, Architecture Principles, and the existing baseline architectures (Technology and Application). All listed items are valid inputs to Business Architecture work.
-
Create Architecture Models
-
Conduct a review workshop with Known Industry experts
-
Identify Reference Models, View points and Tools
-
Develop Baseline business architecture description
-
Select Business Architecture Building Blocks
B
Correct answer
Explanation
Phase B steps include developing baseline descriptions, selecting building blocks, identifying reference models/tools, and creating architecture models. Conducting external expert workshops is not a documented TOGAF ADM step - this would be part of stakeholder engagement, not a formal ADM phase step.
-
Business Services
-
Business Functions
-
Business Process, including measures and deliverables
-
Key business Goals
-
Updated business requirement
D
Correct answer
Explanation
Business Architecture outputs include Business Services, Functions, Processes (with measures), and updated requirements. Key business goals are INPUTS to Phase B from Phase A, not outputs. The phase delivers architecture descriptions, not the goals themselves.
-
Deliverable base-lining
-
Defect prevention
-
Management reporting
-
None of the above
A
Correct answer
Explanation
Defect management involves preventing defects, managing the lifecycle of found defects, and providing management visibility. Deliverable base-lining (A) is a configuration management practice for version control, not part of tracking and resolving defects. Prevention (B), reporting (C), and process management are all core to defect management. Option D (None of the above) is incorrect since A is indeed not included.
-
A Key objective of the Phase B is reuse of the existing software components available in the existing applications.
-
As a Part of the Phase B, the Architecture team will need to consider what relevant Business Architecture resources are available from the enterprise continuum
-
Knowledge of Bsiness architecture is a prerequisite for architecture work in any other domain.
-
The normal approach to Target Architecture development is top-down
-
In Practical terms, the business architecture is also often necessary as a means of demonstrating the business value of subsequent Technical Architecture work to key stake holders
-
Establish the Project
-
Define Scope
-
Create Architecture Models
-
Review Architecture Principles including business principles
-
Identify Business Goals and Drivers
C
Correct answer
Explanation
TOGAF ADM Phase A (Architecture Vision) focuses on preparation: establishing the project (A), scoping (B), reviewing principles (D), and identifying business goals (E). Creating detailed architecture models (C) happens in later phases (B, C, D) when developing specific domain architectures. Phase A is about vision and preparation, not detailed modeling. The marked answer C is correct - modeling is not a key step in Phase A.