SOFTWARE PROJECT MANAGEMENT

ASSIGNMENT#2

BS(SE)-2018

Submitted By: Abeera Afridi

Submitted To: Dr. Muhammad Shahab Siddiqui

20th July 2021

DEPARTMENT OF COMPUTER SCIENCE AND SOFTWARE ENGINEERING

Jinnah University for Women

5-C NAZIMABAD, KARACHI 74600

 Jinnah University for Women
Department of Computer Science and Software Engineering
Batch: BS SE 2018
Course Name: Software Project Management
Course Code: CSS-4191 (3+0)
Assignment No. 2
Submission Date: Tuesday, 20thJuly 2021
Instructions:
 The assignment must be submitted on JUW LMS. Email submission will not be accepted.
 Each student should solve the assignment individually.
 You are advised to go through the related topics solving the assignment.
 Make your work clear and understandable.
 Plagiarism may lead to marks deduction
 Use references where necessary

Max. Marks: 15

Q.1. With respect to the attached Case Study on Quality Assurance; How Quality
Assurance impact on the working of SDLC by Software Project Manager?

[3 Marks]

Answer:

According to the case study, Maxwell Huffman says that I guess quality assurance testing is
always about trying to mitigate risk. There’s only so much testing that is realistic to do, you
know, you could test forever and never release your product, and that’s not good for business.
It’s really about balancing, like how likely is it that the customer is going to encounter how much
time and energy would be required to fix it. Overall company reputation, impact, there’s all sorts
of different metrics. Every customer’s unique, really, they get to set the pace.

A good Software Development Lifecycle process has QA involved at each stage, right from
planning through support and maintenance. Quality Assurance ensures the quality of the
software development life cycle (SDLC) and its results. These processes involve far more insight
and interpretation than basic “Testing” encompasses. QA engineers have a clear overview of the
entire SDLC process and can point out inefficiencies and gaps. QA engineers have a clear
overview of the entire SDLC process and can point out inefficiencies and gaps through out the
software management.
Q.2. With respect to the attached Case Study on Software Build Vs Buy; How Software
Project Manager takes decision on Software Build Vs Buy?

[3 Marks]

Answer:

According to the case study, there’s tons of factors and a lot of it comes natural depending on

what we’ve done in the past as individuals. Like, what is the business need? What’s the business

tradeoffs? What are all these different things that we have to evaluate? So cost is definitely the

first thing that comes to mind. Just what are we financially spending? But there’s also a lot of

other types of costs and other types of rewards that we like to evaluate in the work that we do.

According to Dam Moore, there’s a lot of hidden costs when buying solutions off the shelf and

we see that in terms of integration costs or cost to other sides of the business. So, if you’re not

building software that is unique and specifically tailored around your business operations, that

you already have set up your buying software off the shelf and have to readjust the business

operations to match the software.

Adam Conrad says that if you start going through that build process, you know, what kind of

signals are you looking for, where you realize, okay, maybe we do need to reach back out or, you

know, our internal solution just isn’t cutting it the way we thought it was going to.

The Software Project Manager makes a decision Based on the costs and risks associated with

them. Making build vs. buy decisions frequently can be a challenge. Often, we do not have

enough information and things can change during the decision-making process. However, it must

be remembered that the aim should be to make a "good decision”.

Q.3. With respect to the attached Case Study on Software Telemetry; How Software
Telemetry impact on the development effort managed by the Software Project Manager?

[3 Marks]

Answer:

Software telemetry is the discipline of tracing, logging, and monitoring infrastructure by

observing and analyzing the events generated by the system.

In the case study of Software Telemetry, Jamie Riedesel said that its broadest level, software
telemetry is what we all use to figure out what our software’s actually doing. Quite frankly. I
mean, when you’re writing software, what is, how is it that you find out that it’s doing what it
should? And that’s only a little rhetorical because if it’s working exactly the way it should great,
but if it doesn’t software telemetry tells you why. Software telemetry tells you what’s going on
in the black box.

Optimizing telemetry utilization and workflow can provide increased capacity, improved

efficiency, decreased length of stay, reduced workforce costs, and reduced device and supply
use. The bottom line can include a solid return on investment.

Q.4. With respect to the attached Case Study on 97 things java programmers must know;

How these java skills impact on the working of Programming effort managed by Software

Project Manager? [3 Marks]

Answer:

We know that a Java Developer is responsible for the design, development, and management of
Java-based applications. Because Java is used so widely, particularly by large organizations, the
daily roles vary widely. And so, all the 97 things that are mentioned in the case study are
important for java programmers to know. While a Java Developer might work with or report to
a Project Manager, it’s important that they themselves have project management skills.
All these skills if present makes a huge impact on the programmer as well as the Project
manager. A project manager closely monitors the development process, and all these skills
matter a lot. Such as, it is mentioned that one of the skills is “Learn to Estimate” so as a
programmer you need to be able to provide estimates to your managers, colleagues, and users for
the tasks you need to perform, so that they will have a reasonably accurate idea of the time,
costs, technology, and other resources needed to achieve their goals. The programmer, at the end,
comes up with an "estimate" that matches what is acceptable for the manager.

Similarly, all other skills more or less makes an impact on the programming effort made by
developer as well as the project manager.

Q.5. With respect to the attached Case Study on good software; How good software
parameters impact on the overall software development managed by Software Project
Manager?

[3 Marks]

Answer:

According to the case study, the professor Marco Faella says that you should be aware of the
techniques that you can use to, to improve those qualities. And on a kind of a third level, you
should have the experience and the capacity to judge which quality to focus on among all those
qualities that are always present somehow. So, your software has to do his job. That’s the
correctness, that’s the functional requirements. Then it has to do it in an efficient manner and so
on and so forth. So, you have to be aware of these dimensions, then you have to know specific
techniques to work on those dimensions, to improve on those dimensions. And then finally you
or your coworkers or your boss have to have the vision to pick the right balance among these
properties.

Another important parameter is time efficiency, it is simply achieving your task in, as little time

as possible. Also, it is still good to have general understanding of, how much memory a hash

table takes compared to how much memory NRA takes in most implementation a hash table.
Those are the kind of simple comparisons that, that every programmer should be, should be

aware of, regardless of the specific domain calling all developers.

Professor also mentioned some other good software parameters like readability, reusability,
complexity level, testing, measurability, reliability, threat safety and much more. All these
parameters effect the development and management of Software project in a positive way.