CS605 Assignment 1 Solution and Discussion

[zareen]

Assignment No. 01
Semester: Fall 2019
CS605 - Software Engineering-II
Total Marks: 10

Due Date: 19/11/2019

Assignment no. 1 covers Lec#1 to Lec#8.

Objectives of Assignment:

• To learn the basic objective of software process models.
• To understand the applications of different SDLC models.
• To learn about the different phases of these process models.

Uploading instructions:

• Your assignment must be in .doc format.(Any other formats like scan images, PDF, Zip, rar, bmp, docx etc will not be accepted).
• No assignment will be accepted through email.

Rules for Marking:

It should be clear that your assignment will not get any credit if:

• The assignment is submitted after due date.
• The submitted assignment does not open or file is corrupted.
• Your assignment is copied from internet, handouts or from any other student
(Strict disciplinary action will be taken in this case).

Question no. 1: 5 Marks

Suppose you are developing a large software project that has multiple dependable modules. It will be faster and cheaper to fix the encountered bugs before you write the subsequent new code. Why?
Give at least two reasons. Each reason should be at maximum two sentences long.

Question no. 2: 5 Marks

Suppose you are a Project Manager at a large organization and your team has been assigned a project to develop an ERP system for your Organization.
State (with 02 valid reasons) which Software Process Model you will use and Why ?

NOTE: Submit “.doc” file only. Every student should provide his/her own work, exact copying of the assignment (or some portion of the assignment) from the internet or other students will lead to copy case and zero marks will be awarded. Do not put any query on MDB about this assignment, if you have any query then email us at [email protected]

Deadline:
Your assignment must be uploaded/submitted on or before 19th November 2019.

[zareen]

@zareen said in CS605 Assignment 1 Solution and Discussion:

Question no. 2: 5 Marks
Suppose you are a Project Manager at a large organization and your team has been assigned a project to develop an ERP system for your Organization.
State (with 02 valid reasons) which Software Process Model you will use and Why ?

Answer:

Spiral Model is the most appropriate model for developing such type of systems.

1. Requirements are complex and need evaluation / feedback to get clarity. Significant changes are expected in the product during the development cycle due to nature of the system.
2. Development can be divided into smaller parts and the risky parts can be developed earlier which helps in better risk management.

[zareen]

@zareen said in CS605 Assignment 1 Solution and Discussion:

Question no. 1: 5 Marks
Suppose you are developing a large software project that has multiple dependable modules. It will be faster and cheaper to fix the encountered bugs before you write the subsequent new code. Why?
Give at least two reasons. Each reason should be at maximum two sentences long.

Answer:

1. You are familiar with the project requirements, modules (and their dependencies) and the code, the bugs will be harder to find and fix later. Leaving all the bugs to the end will make it hard to understand and the overall schedule may slip.

2. Later code may depend on the current code; therefore, it needs to be corrected before moving on the next modules (to avoid the ripple effect).

[zareen]

@zareen said in CS605 Assignment 1 Solution and Discussion:

Question no. 2: 5 Marks
Suppose you are a Project Manager at a large organization and your team has been assigned a project to develop an ERP system for your Organization.
State (with 02 valid reasons) which Software Process Model you will use and Why ?

Implementing an ERP solution provides many benefits to an organization, including process efficiencies, improved user interface, technology enhancements, lower maintenance costs and the ability to leverage leading industry practices. Iterative planning on an ERP project provides many benefits: major risks are identified and addressed early in the project; requirement changes are identified and prioritized efficiently; project team utilization is optimized; and progress and quality are continuously monitored and corrected.
Layered Approach
ERP project plans need to be scalable for different project sizes and complexity and contain the right level of detail for the current planning horizon. Plans that are too detailed are almost instantly inaccurate and obscure key objectives. On the other hand, plans that are too high level will not allow for measurement of project progress nor keep the project team focused on their day-to-day activities.
ERP project plans also need to display the appropriate level of detail and planning horizon for specific audiences.

Partitioning
In a large and/or complex ERP project, the project manager should consider breaking the project into several product partitions — one for each major release of the product to be developed, implemented, or upgraded. Projects which are more than a year in duration, those with high risk factors, projects where there is business value to be gained from delivery of a sub-set of the overall functionality, and/or those where resources are constrained are all candidates for partitioning. This approach allows risk to be spread over a number of releases and permits business value to be delivered sooner.

Note: - We are not responsible for any mistake, this is for your idea or help, need to verify yourself.

[zareen]

@zareen said in CS605 Assignment 1 Solution and Discussion:

Suppose you are developing a large software project that has multiple dependable modules. It will be faster and cheaper to fix the encountered bugs before you write the subsequent new code. Why?
Give at least two reasons. Each reason should be at maximum two sentences long.

If you find a bug in code that has already shipped, you’re going to incur incredible expense getting it fixed.
That’s one reason to fix bugs right away: because it takes less time. There’s another reason, which relates to the fact that it’s easier to predict how long it will take to write new code than to fix an existing bug.

Another great thing about keeping the bug count at zero is that you can respond much faster to competition. Some programmer’s think of this as keeping the product ready to ship at all times. Then if your competitor introduces a killer new feature that is stealing your customers, you can implement just that feature and ship on the spot, without having to fix a large number of accumulated bugs.