Software Development and Management

There is no fixed percentage allocation for development and testing budgets because project requirements vary. The budget split depends directly on the criticality of the application, regulatory requirements, and risk factors, making standard splits like 50-50, 40-60, or 60-40 inaccurate generalizations.

The Business Analyst (BA) is responsible for producing design specifications in a project. BAs bridge business requirements and technical implementation, documenting system behavior, user interactions, data structures, and business rules. VTM (likely Team Lead), DL (possibly Delivery Lead), and SPONSOR are roles focused on delivery management, governance, and funding rather than detailed specification creation.

Maintenance is a non-functional quality characteristic because it describes HOW the system performs (ease of modification, updating, or repairing) rather than WHAT it does functionally. Non-functional characteristics include attributes like usability, reliability, performance, and maintainability. Feasibility (A) is a project consideration, Usability (B) is also non-functional, and Regression (D) refers to a type of functional testing.

Different Software Development Life Cycle (SDLC) models suit different project types based on factors like requirements clarity, timeline flexibility, risk level, and team size. For example, Waterfall works well for stable requirements, while Agile is better for projects needing frequent adaptation. Choosing the right model is critical for project success.

In software quality models like McCall's or ISO/IEC 9126, reusability is classified as a transition characteristic along with portability and interoperability. Transition characteristics describe how easily software can be adapted to new environments or reused in different contexts. Operational characteristics refer to runtime behavior like efficiency and reliability, while revision characteristics relate to maintainability.

Software maintenance encompasses three primary types: corrective maintenance fixes bugs, adaptive maintenance modifies software to work in new environments, and preventive (also called perfective) maintenance improves performance or maintainability to prevent future issues. Since all these are valid maintenance activities, 'all of the above' is the correct answer.

Changeman is a change management system designed to manage and automate the process of migrating software changes. It helps organizations track, control, and deploy changes from development through testing to production environments. Option A correctly identifies its primary purpose as migrating software changes.

A Change Package represents a collection of related changes moved together. The standard deployment flow moves changes from the development environment to the production environment. This is the controlled promotion path where tested changes are deployed to live production systems.

Staging is the process through which components are introduced into a Change Package. During staging, components are copied from the baseline to the staging area and become part of the change package. Editing and Accessing are separate activities, and Locking is a mechanism used during checkout.

Project risks are high-level organizational and managerial concerns that could impact project delivery, such as unclear requirements, stakeholder conflicts, poor communication, unrealistic deadlines, inadequate resources, or organizational changes. Options B, C, and D describe product risks (technical risks related to the software itself) rather than project risks.

A walkthrough is an informal peer review technique characterized by: meeting scenarios where the author presents the work, conducting a dry run through the document/code, and involving a peer group of colleagues. Key characteristics include its informal nature, lack of formal training requirements, minimal preparation, and absence of formal follow-up processes or metrics collection.

In ILOG BRMS, the correct hierarchy is Repository→Ruleset→Package→Rules. The Repository is the top-level container, Rulesets group related packages, Packages organize rules, and Rules are the individual business rule units. This hierarchy enables modular organization and governance of large rule bases.

Scrum is a widely-adopted Agile framework for software development. It emphasizes iterative development, self-organizing teams, regular sprints, and continuous improvement through ceremonies like daily standups, sprint planning, and retrospectives.