DCA7107 SOFTWARE ENGINEERING & PROJECT MANAGEMENT

Description

SESSION	FEB-MARCH 2026
PROGRAM	MASTER OF COMPUTER APPLICATIONS (MCA)
SEMESTER	III
COURSE CODE & NAME	DCA7107 SOFTWARE ENGINEERING & PROJECT MANAGEMENT

 

 

Assignment Set – 1

 

Q.1. Explain the core principles and goals of Software Engineering, and outline the key stages involved in the software development process.

Ans 1.

Core Principles and Goals of Software Engineering

Software engineering is the disciplined application of engineering principles to the design, development as well as the testing and maintenance of software technology. Its main goal is to make software that is secure effective, durable, and that is completed on time and within the budget.

The primary principle is modularity.

 

Its Half solved only

Buy Complete from our online store

 

https://smuassignment.in/online-store/

 

MUJ Fully solved assignment available for session Jan-Feb 2026.

 

Lowest price guarantee with quality.

Charges INR 198 only per assignment. For more information you can get via mail or Whats app also

Mail id is aapkieducation@gmail.com

 

Our website www.smuassignment.in

After mail, we will reply you instant or maximum

1 hour.

Otherwise you can also contact on our

whatsapp no 8791490301.

 

 

 

 

Q.2. Compare the Prototyping Model, Agile Model, and V-Model by examining their workflows, strengths, and limitations.

Ans 2.

Prototyping Model

Prototyping Model: Prototyping Model involves building a functioning prototype of the program at the beginning of the process. It is a prototype version of the system which shows key elements. Users and stakeholders review the prototype, and give feedback. It is refined with feedback from stakeholders until the desired requirements are identified, at which point the final system is created.

The main

 

Q.3. Distinguish between functional and non-functional requirements, and describe the methods used to document software requirements.

Ans 3.

Functional vs Non-Functional Requirements

Functional requirements specify the functions a software system is expected to perform. They specify specific actions or operations that the software must perform. These rules are tied directly to user actions and system responses. For instance, the user must be able to join and log in, the system must generate monthly sales reports, and it must also issue email alerts after each sale. Functional requirements are

 

 

Assignment Set – 2

 

Q.4. Explain the process of Object-Oriented Design and how object identification along with design models contributes to effective software development.

Ans 4.

Object-Oriented Design

Object-Oriented Design (OOD) is an approach to design that organizes a software system by defining it as a set of interconnected objects. Each object is an instance of a class and is a container for information (attributes) and behavior (methods). OOD draws on the requirements obtained during the process of analysis and translate them into a complete plan that is easily implemented using object-oriented programming language

 

Q.5. Describe the various categories of software maintenance, and discuss the concepts of software re-engineering and configuration management.

Ans 5.

Categories of Software Maintenance

Software maintenance refers to the activities that are carried out following software is delivered to modify, improve, or correct it. It’s usually the longest as well as most expensive phase of the software lifecycle. It is divided in four different categories.

Corrective Maintenance consists of correcting defects or issues that are discovered when the software has been put into use. This could mean that the defects were present in the software but were only discovered under specific circumstances during the actual usage. For example, the fix for a

 

 

 

Q.6. Examine different software quality metrics and explain how these metrics are utilized across the phases of analysis, design, coding, testing, and maintenance.

Ans 6.

Software Quality Metrics

Software quality metrics are quantifiable metrics used to assess diverse aspects of software quality. They aid development teams in making well-informed decisions, pinpoint issues, and measure improvements over time.

Lines of Code (LOC) is a measure of the size of software in terms of the quantity of lines coded.