AKTU MBA 3rd Sem Software Engineering And Management PYQs

Software Engineering And Management is an important Information Technology specialization subject in AKTU MBA 3rd Semester. The subject focuses on software development processes, software project planning, requirements, system design, testing, quality, maintenance, project estimation, team management, risk management, and the managerial aspects of software projects.

Practicing AKTU MBA 3rd Sem Software Engineering And Management PYQs helps students understand how software-development concepts, project-management methods, software life-cycle models, testing, estimation, quality, and project-risk topics are framed in university examinations. Since the subject combines technical understanding with managerial decision-making, students should prepare both conceptual and application-based questions carefully.

Students can explore AKTU MBA previous-year question papers and related academic resources on NotesGallery. For official university notices, examination announcements, academic circulars, and authoritative information, students should refer to the AKTU Official Website.

AKTU MBA 3rd Semester Subject Details

The subject details are:

Subject Code	Subject Name	Specialization
BMB IT 01	Software Engineering And Management	Information Technology

Software Engineering And Management is part of the Information Technology specialization in MBA Semester 3.

The other Information Technology specialization subjects shown alongside it are:

Code	Subject
BMB IT 02	Emerging Technologies for Business
BMB IT 03	Database Management System

MBA 3rd Semester also includes the core subject Strategic Management (BMB301) along with specialization electives from Marketing, Human Resource Management, Financial Management, Operation Management, International Business, and Cooperative Management.

About Software Engineering And Management

Software Engineering deals with the systematic development, operation, maintenance, and improvement of software.

Software Management focuses on planning and controlling software projects so that they can be completed within:

• required scope
• expected quality
• available budget
• planned schedule

The subject therefore combines technical software-development principles with project-management concepts.

Meaning of Software Engineering

Software Engineering applies systematic methods to software development.

It may involve:

• requirements analysis
• system design
• coding
• testing
• deployment
• maintenance

The objective is to develop software that is:

• reliable
• maintainable
• efficient
• usable
• secure
• suitable for user requirements

Need for Software Engineering

Software systems can become complex because of:

• large codebases
• multiple users
• changing requirements
• integration with other systems
• security requirements
• long-term maintenance

Without a systematic development approach, software projects may experience:

• delays
• budget overruns
• quality problems
• requirement mismatch
• maintenance difficulty

Software Engineering helps reduce these risks.

Characteristics of Good Software

Good software may be evaluated using characteristics such as:

• functionality
• reliability
• usability
• efficiency
• maintainability
• portability
• security

Different projects may give different importance to each characteristic.

Software Development Life Cycle

The Software Development Life Cycle (SDLC) describes the stages involved in developing software.

A general SDLC may include:

1. Planning
2. Requirements analysis
3. Design
4. Development
5. Testing
6. Deployment
7. Maintenance

Students should understand the purpose of each stage.

Planning

Planning involves identifying:

• project objectives
• scope
• resources
• estimated cost
• schedule
• major risks

Good planning helps reduce uncertainty before development begins.

Requirements Analysis

Requirements Analysis identifies what users and stakeholders need from the software.

Requirements may include:

• functional requirements
• non-functional requirements

Clear requirements reduce misunderstanding between users and developers.

Functional Requirements

Functional requirements describe what the system should do.

Examples may include:

• user login
• report generation
• payment processing
• inventory update

Non-Functional Requirements

Non-functional requirements describe how the system should perform.

Examples may include:

• performance
• security
• usability
• reliability
• scalability

Requirement Gathering

Requirement gathering may involve:

• interviews
• questionnaires
• observation
• workshops
• document analysis

The selected technique depends on the project and stakeholders.

Software Requirement Specification

A Software Requirement Specification (SRS) documents the requirements of a software system.

It may include:

• system purpose
• functional requirements
• non-functional requirements
• constraints
• interfaces

A good SRS improves communication between stakeholders and the development team.

System Design

System design converts requirements into a technical solution.

It may involve:

• architecture
• components
• interfaces
• database design
• user interface design

The design should support both current requirements and future maintainability.

Software Architecture

Software architecture describes the high-level structure of a software system.

It explains:

• major components
• interaction among components
• data movement
• system organisation

Good architecture can improve scalability and maintainability.

Coding

Coding is the implementation stage where developers convert designs into executable software.

Good coding practices may include:

• readable code
• consistent standards
• modular design
• documentation
• testing

Coding quality can strongly influence maintenance cost.

Software Testing

Software Testing evaluates whether software works as expected and helps identify defects.

Testing may occur at several levels.

Common testing types include:

• unit testing
• integration testing
• system testing
• acceptance testing

Unit Testing

Unit testing checks individual software components or modules.

The goal is to identify errors at a small functional level.

Integration Testing

Integration testing checks whether multiple modules work correctly together.

It helps identify interface and communication problems.

System Testing

System testing evaluates the complete software system against defined requirements.

Acceptance Testing

Acceptance testing evaluates whether the software is suitable for users or customers.

It is often performed near the end of development before final acceptance.

Verification and Validation

Verification and validation are related but different.

Verification

Verification broadly asks:

Are we building the product correctly?

It focuses on whether development activities follow specifications.

Validation

Validation broadly asks:

Are we building the correct product?

It focuses on whether the software actually satisfies user needs.

Verification vs Validation

Verification	Validation
Focuses on correctness against specifications	Focuses on user needs
Process-oriented	Product-oriented
Checks whether work is done correctly	Checks whether the right product is developed

Software Maintenance

Software maintenance occurs after deployment.

It may involve:

• correcting defects
• adapting software
• improving performance
• adding features

Maintenance can continue for many years after initial development.

Types of Software Maintenance

Common categories include:

• corrective maintenance
• adaptive maintenance
• perfective maintenance
• preventive maintenance

Corrective Maintenance

Corrective maintenance fixes software defects discovered after deployment.

Adaptive Maintenance

Adaptive maintenance changes software so it can continue functioning in a changed environment.

Examples may include:

• operating-system changes
• regulatory changes
• hardware changes

Perfective Maintenance

Perfective maintenance improves software by adding features or improving performance.

Preventive Maintenance

Preventive maintenance improves internal quality to reduce the possibility of future problems.

Software Process Model

A software process model provides a structured approach to organising software-development activities.

Common models include:

• Waterfall Model
• Prototype Model
• Spiral Model
• Incremental Model
• Agile approaches

Waterfall Model

The Waterfall Model follows a sequential approach.

A simplified sequence is:

Requirements → Design → Development → Testing → Deployment

Advantages

• easy to understand
• clear stages
• suitable where requirements are stable

Limitations

• difficult to accommodate major changes
• working software appears relatively late
• problems may be discovered late

Prototype Model

The Prototype Model develops an early version of the system to help clarify requirements.

It can be useful when:

• requirements are unclear
• user feedback is important
• interface design needs validation

Spiral Model

The Spiral Model combines iterative development with strong risk analysis.

Each cycle may involve:

• planning
• risk analysis
• development
• evaluation

It can be useful for large and high-risk projects.

Incremental Model

The Incremental Model develops the system in smaller functional parts.

Benefits may include:

• earlier delivery
• easier testing
• ability to incorporate feedback

Agile Software Development

Agile focuses on iterative and incremental software development.

Important ideas include:

• frequent delivery
• customer collaboration
• adaptability
• continuous feedback
• cross-functional teams

Agile is especially useful where requirements may change.

Agile vs Waterfall

Agile	Waterfall
Iterative	Sequential
Supports changing requirements	Best suited to stable requirements
Delivers in increments	Delivers after major sequential stages
Frequent customer feedback	Customer involvement may be lower during development
Flexible	More structured and fixed

Scrum

Scrum is an Agile framework used for iterative development.

Important concepts may include:

• product backlog
• sprint
• daily meeting
• sprint review
• sprint retrospective

Scrum encourages short development cycles and regular feedback.

Sprint

A sprint is a fixed development period during which the team completes selected work.

At the end of the sprint, a usable increment is usually expected.

Product Backlog

The product backlog is a prioritised list of work or features required for the product.

It is updated as requirements and priorities change.

Software Project Management

Software Project Management focuses on planning, organising, monitoring, and controlling software projects.

It may include:

• scope management
• cost management
• schedule management
• resource management
• risk management
• quality management
• communication

Software Project Objectives

A software project generally aims to achieve:

• required functionality
• acceptable quality
• completion on time
• completion within budget

Managers must balance these objectives.

Project Scope

Project scope defines what is included and excluded from the project.

A poorly defined scope may lead to:

• confusion
• additional work
• delays
• budget problems

Clear scope is essential for effective project management.

Scope Creep

Scope Creep occurs when new requirements or features are added without proper control.

It may cause:

• schedule delays
• higher cost
• resource pressure
• quality problems

Change-control processes can help manage scope creep.

Project Planning

Software project planning may include:

• project scope
• tasks
• schedule
• resources
• budget
• quality requirements
• risk

Planning creates the baseline for project monitoring.

Work Breakdown Structure

A Work Breakdown Structure (WBS) divides a large project into smaller manageable tasks.

A WBS helps:

• estimate effort
• assign responsibility
• create schedules
• monitor progress

Project Scheduling

Project scheduling determines:

• which tasks need to be completed
• task sequence
• duration
• dependencies
• deadlines

Scheduling supports better coordination.

Gantt Chart

A Gantt Chart visually displays project activities over time.

It can show:

• tasks
• start dates
• finish dates
• durations
• progress

Gantt charts are useful for project monitoring.

Network Techniques

Network techniques can help identify relationships among project activities.

They may support:

• scheduling
• critical activity identification
• time planning

Students may encounter concepts such as PERT and CPM where included in the syllabus.

PERT

Program Evaluation and Review Technique (PERT) can be used for project scheduling when activity durations involve uncertainty.

It helps managers evaluate project timelines.

CPM

Critical Path Method (CPM) identifies the sequence of critical project activities that determines the overall project duration.

Delays in critical activities may delay the entire project.

Project Estimation

Project estimation involves predicting:

• effort
• time
• cost
• resources

Software estimation is difficult because software development includes uncertainty.

Software Effort Estimation

Effort estimation attempts to determine the amount of human work required to complete the software project.

Poor estimation can lead to unrealistic schedules and budgets.

Software Cost Estimation

Software cost may include:

• employee cost
• technology
• infrastructure
• licensing
• testing
• maintenance

Cost estimation should consider both direct and indirect expenses.

COCOMO

COCOMO is a software cost-estimation model associated with estimating software-development effort and cost based on project characteristics and software size.

Students should understand its purpose and broad role where included in their prescribed syllabus.

Function Point Analysis

Function Point Analysis estimates software size based on user-visible functions rather than only source-code length.

It may consider elements such as:

• inputs
• outputs
• files
• interfaces

It can support software estimation.

Software Project Risk

A project risk is an uncertain event that may negatively affect project objectives.

Software-project risks may include:

• requirement changes
• technology problems
• employee turnover
• inaccurate estimates
• schedule delays
• security issues

Risk Management Process

A general risk-management process may include:

1. Identify risks
2. Analyse probability and impact
3. Prioritise risks
4. Develop responses
5. Monitor risks

Risk management should continue throughout the project.

Technical Risk

Technical risk may arise from:

• new technology
• system complexity
• integration difficulty
• performance problems

Project Risk

Project risk may include:

• schedule delays
• budget overruns
• staff shortages
• weak planning

Business Risk

Business risk may arise when the project does not produce expected organisational value.

Examples may include:

• changing market needs
• loss of funding
• product no longer required

Software Quality Management

Software Quality Management focuses on ensuring that software meets required standards and user expectations.

It may involve:

• quality planning
• quality assurance
• quality control
• testing
• process improvement

Software Quality Assurance

Software Quality Assurance (SQA) focuses on processes and standards used to improve software quality.

It may involve:

• reviews
• audits
• standards
• documentation
• process monitoring

SQA is broader than testing alone.

Software Quality Control

Quality control focuses more directly on evaluating software outputs and identifying defects.

It may include:

• testing
• inspections
• defect analysis

Quality Assurance vs Testing

Quality Assurance	Testing
Broader process-oriented approach	Product-evaluation activity
Focuses on preventing defects	Focuses on finding defects
Includes standards and reviews	Includes execution and validation

Software Configuration Management

Software Configuration Management (SCM) helps control changes to software components.

It may involve:

• version control
• change control
• configuration identification
• release management

SCM is important when multiple developers work on the same system.

Version Control

Version control tracks changes made to software files.

It helps teams:

• maintain history
• collaborate
• restore previous versions
• manage parallel development

Change Management

Software requirements often change during a project.

Change management helps evaluate:

• reason for change
• cost impact
• schedule impact
• technical impact
• approval requirements

Uncontrolled changes can create project failure.

Change Control

Change control provides a formal method for managing requested changes.

A general process may include:

1. Submit change request
2. Analyse impact
3. Approve or reject
4. Implement approved change
5. Update documentation

Software Documentation

Documentation records information about the software and development process.

It may include:

• requirements documents
• design documents
• user manuals
• technical documentation
• test documentation

Good documentation improves communication and maintenance.

Software Metrics

Software metrics provide quantitative information about development or software performance.

Metrics may relate to:

• size
• defects
• productivity
• effort
• schedule
• quality

Managers use metrics to improve decision-making.

Defect Metrics

Defect-related metrics may help measure:

• number of defects
• defect rate
• defect severity
• defects discovered at different stages

These metrics can help identify process weaknesses.

Productivity Measurement

Software productivity may compare outputs with resources or effort used.

Managers should interpret productivity carefully because software tasks can vary significantly in complexity.

Project Monitoring

Project monitoring involves comparing actual progress with project plans.

Managers may monitor:

• schedule
• cost
• scope
• quality
• risk

Monitoring allows corrective action before problems become severe.

Project Control

Project control involves responding to deviations from the plan.

Possible actions may include:

• changing resources
• revising schedules
• resolving bottlenecks
• adjusting scope
• managing risks

Software Team Management

Software projects are completed by teams that may include:

• developers
• testers
• analysts
• designers
• project managers

Effective team management is important for project success.

Team Structure

Software teams may be organised according to:

• project
• function
• expertise
• Agile cross-functional teams

The structure should match project complexity and communication needs.

Role of Software Project Manager

A software project manager may be responsible for:

• planning
• scheduling
• budgeting
• assigning resources
• managing risks
• monitoring progress
• communicating with stakeholders

The manager must understand both technical and business issues.

Leadership in Software Projects

Leadership helps:

• motivate teams
• solve conflicts
• clarify goals
• manage uncertainty
• support collaboration

Technical expertise alone may not be sufficient for managing large software projects.

Communication in Software Projects

Poor communication can create:

• misunderstood requirements
• duplicated work
• delays
• conflict

Project communication should involve:

• developers
• users
• managers
• customers
• vendors

Stakeholder Management

Stakeholders may include:

• customers
• users
• management
• developers
• regulators
• vendors

Stakeholder management involves understanding their expectations and maintaining effective communication.

Software Procurement

Organisations may choose to:

• develop software internally
• purchase commercial software
• outsource development

The choice may depend on:

• cost
• strategic importance
• technical capability
• time
• control

Make-or-Buy Decision in Software

A make-or-buy decision compares internal development with purchasing or outsourcing software.

Important factors include:

• cost
• customisation
• security
• maintenance
• vendor reliability
• internal expertise

Software Outsourcing

Software outsourcing involves assigning software-development or maintenance work to an external provider.

Benefits may include:

• access to expertise
• cost efficiency
• faster development

Risks may include:

• reduced control
• security concerns
• vendor dependency
• communication problems

Vendor Management

Vendor management involves selecting and monitoring external technology providers.

Important considerations include:

• technical capability
• cost
• service quality
• security
• contractual obligations
• support

Software Contracts

Software projects involving external vendors may require agreements addressing:

• scope
• cost
• timeline
• ownership
• confidentiality
• support
• service requirements

Clear contracts reduce disputes.

Service Level Agreement

A Service Level Agreement (SLA) defines expected service performance between provider and customer.

It may specify:

• availability
• response time
• support
• performance levels

SLAs are particularly important in outsourced IT services.

Software Security Management

Security should be considered throughout software development.

Important areas may include:

• access control
• authentication
• data protection
• secure coding
• vulnerability management

Security failures can create significant business risk.

Secure Software Development

Secure development integrates security practices into the development life cycle rather than adding security only at the end.

It may involve:

• security requirements
• code reviews
• testing
• vulnerability assessment

DevOps

DevOps combines development and operations practices to improve software delivery and collaboration.

It emphasises:

• automation
• continuous integration
• continuous delivery
• collaboration
• monitoring

Continuous Integration

Continuous Integration involves regularly integrating code changes into a shared system and checking them through automated processes.

It can help identify integration problems earlier.

Continuous Delivery

Continuous Delivery focuses on keeping software in a state that can be released reliably and frequently.

It can reduce delays between development and deployment.

DevOps vs Traditional Development

DevOps	Traditional Approach
Strong development-operations collaboration	Development and operations may be more separate
Frequent releases	Releases may be less frequent
High automation	More manual processes possible
Continuous monitoring	Monitoring may be more separated

Software Project Success

A software project may be considered successful when it:

• meets requirements
• remains within reasonable budget
• meets schedule expectations
• achieves required quality
• creates business value

Success should not be judged by technical completion alone.

Reasons for Software Project Failure

Projects may fail because of:

• unclear requirements
• unrealistic estimates
• poor planning
• scope creep
• weak communication
• lack of user involvement
• technical problems
• inadequate risk management

Understanding failure factors is important for project managers.

Software Project Audit

A project audit reviews how a project has been planned and managed.

It may evaluate:

• cost
• schedule
• quality
• risk
• compliance

Audits can support learning and process improvement.

Software Project Closure

Project closure occurs after project objectives are completed or the project is formally ended.

Activities may include:

• final acceptance
• documentation
• lessons learned
• release of resources
• project review

Lessons Learned

Lessons learned capture knowledge about:

• what worked
• what failed
• what should be improved

This information can improve future software projects.

Software Engineering and Business Strategy

Software has become strategically important in many organisations.

Software projects may support:

• digital transformation
• customer service
• process automation
• analytics
• e-commerce
• competitive advantage

Managers therefore need to evaluate software as a business investment.

Relationship With Emerging Technologies for Business

Software Engineering And Management connects directly with Emerging Technologies for Business (BMB IT 02).

Emerging technologies such as:

• Artificial Intelligence
• cloud computing
• Internet of Things
• blockchain

often require software projects for business implementation.

Software Engineering provides the structured development approach required to convert these technologies into usable business systems.

Relationship With Database Management System

It also connects with Database Management System (BMB IT 03).

Most software applications depend on databases for:

• storing information
• processing transactions
• retrieving data
• reporting

Software design and database design therefore need to be coordinated.

Relationship With Strategic Management

The core subject Strategic Management (BMB301) connects with Software Engineering And Management because technology projects should support broader organisational objectives.

Software investments may influence:

• digital strategy
• customer experience
• cost efficiency
• innovation
• competitive position

Why Solve AKTU MBA Software Engineering And Management PYQs?

Understand the Examination Pattern

Previous-year papers can help students identify whether topics are asked as:

• definitions
• short notes
• SDLC questions
• process-model comparisons
• project-management questions
• software-quality questions
• case-based applications

Improve Process-Based Answers

Many topics can be prepared using logical sequences, such as:

Requirements → Design → Development → Testing → Deployment → Maintenance

Improve Comparison Questions

Important comparisons may include:

• Agile vs Waterfall
• verification vs validation
• Quality Assurance vs Testing
• corrective vs adaptive maintenance
• make vs buy

Improve Managerial Understanding

Students should connect software concepts with business decisions involving:

• cost
• time
• quality
• risk
• resources
• vendors

Important Topics for Exam Preparation

While practicing AKTU MBA 3rd Sem Software Engineering And Management PYQs, students should pay particular attention to:

• Software Engineering
• software characteristics
• SDLC
• requirement analysis
• SRS
• functional requirements
• non-functional requirements
• system design
• software architecture
• software testing
• verification and validation
• software maintenance
• software process models
• Waterfall Model
• Prototype Model
• Spiral Model
• Incremental Model
• Agile
• Scrum
• software project management
• project scope
• scope creep
• WBS
• project scheduling
• Gantt Chart
• PERT
• CPM
• software estimation
• COCOMO
• Function Point Analysis
• software-project risks
• Software Quality Assurance
• configuration management
• version control
• change management
• software metrics
• project monitoring
• stakeholder management
• outsourcing
• vendor management
• SLA
• software security
• DevOps
• Continuous Integration
• Continuous Delivery
• reasons for software project failure

Students should still prepare the complete prescribed syllabus rather than relying only on repeated PYQ topics.

How to Practice Software Engineering And Management PYQs

Step 1: Understand the Software Life Cycle

Start with the complete development process before studying individual models.

Step 2: Learn Major Process Models

For each model, prepare:

• meaning
• stages
• advantages
• limitations
• suitable situations

Step 3: Study Software Project Management

Understand:

• scope
• cost
• schedule
• resources
• quality
• risk

Step 4: Attempt Related PYQs

Write answers without referring to notes.

Step 5: Prepare Diagrams

Simple diagrams can improve answers related to:

• SDLC
• Waterfall
• Spiral
• Agile
• software-project cycle

Step 6: Prepare Comparison Tables

Use tables for similar concepts that are easy to confuse.

Step 7: Add Business Perspective

For managerial questions, explain how the concept affects:

• project cost
• delivery time
• software quality
• organisational value

Step 8: Solve a Complete Paper

After syllabus revision, attempt a complete previous-year paper within a fixed time.

This improves:

• recall
• technical terminology
• answer structure
• managerial understanding
• time management

Quick Revision Strategy

For final revision, divide the subject into four broad areas.

Software Engineering Fundamentals

Revise:

• SDLC
• requirements
• SRS
• design
• coding
• testing
• maintenance

Software Process Models

Revise:

• Waterfall
• Prototype
• Spiral
• Incremental
• Agile
• Scrum

Software Project Management

Revise:

• scope
• WBS
• schedule
• PERT
• CPM
• estimation
• risk
• team management

Software Quality and Modern Practices

Revise:

• SQA
• testing
• configuration management
• change control
• outsourcing
• security
• DevOps
• Continuous Integration
• Continuous Delivery

After revision, attempt selected PYQs without referring to your notes.

Useful Resources for AKTU MBA Students

Students can explore AKTU MBA previous-year question papers, notes, and related academic resources through NotesGallery.

For official university notices, examination announcements, academic circulars, and authoritative information, students should refer to the AKTU Official Website.

NotesGallery is an independent educational resource platform and should not be considered the official website of Dr. A.P.J. Abdul Kalam Technical University.

Related MBA Third Semester Study Materials

MBA 3rd Semester All Subject PYQs
→


MBA 3rd Semester All Subject Notes
→


MBA 3rd Semester All Subject Syllabus
→

Frequently Asked Questions