Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Software Engineering II - Solved Assignments - Semester Spring 2010

Software Engineering II - Solved Assignments - Semester Spring 2010

Ratings: (0)|Views: 2,349|Likes:
Published by Muhammad Umair
Software Engineering II - Solved Assignments - Semester Spring 2010
Software Engineering II - Solved Assignments - Semester Spring 2010

More info:

Published by: Muhammad Umair on Aug 23, 2010
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





Software Engineering IISolved AssignmentsSemester Spring 2010
 Assignment 1
A software xyz company is developing IT Services and products for different organizations.Most of their projects, when delivered to the customer didn’t fulfill the customers’ expectations.During the testing phase they found lot of defects which require more cost and resources to fixthem. As a result most of their projects fail or they have to modify the project in order to make itaccording to the customer’s expectations. At the moment they have their own ad-hoc processmodel for Software Development. Now Company hired you as a project manager. So as a projectmanager:
Q No.1: Identify the reasons why project fails?
Answer.A number of reasons contribute to Projects Failure. Some of them are outlined below.
The product scope is poorly defined.
One of the main reasons of Project failure is that Project scope is not clearly defined. TheScope Statement should includes the list of users using the product, as well as the featuresin the resulting product, however, when any of these things are missed or are not giventoo much importance in the Project Scope Statement, then Projects usually fail, or if theysucceed, then they succeed only after so many changes.
Changes are managed poorly.
Another reason for failures of software project is that Changes in the existing system aremanaged poorly. Changes can be changes in the existing system or even changes in theother aspects of software projects, like deadline of software.
Businesses needs change or are ill-defined.
When the business needs change and are not managed properly then the result is softwarefailure. Business Needs should also be defined clearly in Software Requirementsdocuments.
Deadlines are unrealistic.
This happens when the deadlines of software change unexpectedly. If not managedproperly, software fails.
The project team lacks people with appropriate skills.
As we know that software engineers work on projects that do not belong to their domain.So, when the software engineer could not understand the domain of the softwarecorrectly, then it results in project failures. Even if succeeded, software includes lot of bugs which are fixed time to time, and thus cost of software project increases.
Miscommunication among Project members
Miscommunication among Project Staff also leads to software failures. When softwaredevelopers do not interact with each other to solve problems that they face, then thesoftware development usually takes more time then it should.
Inadequate software Testing
In many cases software testing is left to users who are not able to fully exercise thesystem. Regression testing is not performed at each release and functionality formerlypresent in the software is not verified and can be lost.
Frequent or large changes to project scope
.Scope changes can significantly impact the cost, schedule, risks and quality of the entireeffort. Software Project managers should watch out for early and frequent changes to thesoftware project scope.
Risk Management
 Risk management is an important factor towards software project failure if it's notmanaged timely and effectively. As nothing can be predicted that what will happen infuture so we have to take the necessary steps in the present to take any uncertain situationin the future. Risk management means dealing with a concern before it becomes a crisis.
Q No.2: Give the recommendation in order to avoid the failure.
Starting on the right Path:
Lot of projects do not start on the right path, i.e. the objectives and the problem that is to be solveis not stated clearly. For successful software projects, one should work hard to understand theproblem that is to be solved and then setting realistic objects and expectations for every one whowill be involved in the project. It can be reinforced by building the right team and giving theteam the autonomy, authority, and technology needed to do the job.
Maintain Momentum:
Lot of projects fails because of the fact that that the momentum does not remains the same in allthe stages of software development. To maintain momentum, the project manager must provideincentives to keep turnover of personnel to an absolute minimum, the team should emphasizequality in every task it performs, and senior management should do everything possible to stayout of the team’s way.
Track Progress:
The manager should track progress of all the ongoing activities of software development. It notonly includes tracking the progress of software deliverables, source code, use case diagrams etc.etc. but also requires for the software manager to keep track of the software developers, andshould try to remove the problems that are hindering the development of software.

Activity (20)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
gauridaran liked this
Ihas Mohammed liked this
Ihas Mohammed liked this
gauridaran liked this
Kannan Karuppiah liked this
monicakindo liked this
Muthu Pandi liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->