Q1 What do you mean by 99 % Complete Syndrome that software project man- agers sometimes

face? What are its underlined causes? What problems does it create for project management and
what are its remedies?

99% complete syndrome happens. If you ask developer about the progress he/she may say
development is in final stage of just 1% is left .Most probably, this last 1% will drag on to days,
weeks, and even few months. Either something was wrong in the SDLC or they failed to follow up.
Developers should evaluate the amount of effort needed to complete remaining tasks in hour.
Usually instead of this people tend to consider the amount of work gone through against the original
estimate.If you hear someone saying that they are 99% complete, it indicates that they have got
much to complete and the person probably has no idea when it will be completed.

Causes:

1. In software development if you do not follow SDLC (Software Development Life Cycle) 99
complete syndrome happens.

2. Inadequate Planning.

3. Insufficient Defect Containment.

4. Misleading Status Tracking.

Remedies:

1. Sizing and Estimating Best Practices.

2. Planning Best Practices.

Q2 Consider that the software development project that is to be set with many risk but assume
that it is not possible to anticipate all the risk in the project at the start of the project and some of
the risk can only be identified much after the development is underway as the project manager
recommend the use of prototyping or the spiral model explain your answer

Spiral Model will be used in this case

The Spiral Model is widely used in the software industry as it is in sync with the natural development
process of any product, i.e. learning with maturity which involves minimum risk for the customer as
well as the development firms.

The following pointers explain the typical uses of a Spiral Model −

1.When there is a budget constraint and risk evaluation is important.

2.For medium to high-risk projects.

3.Long-term project commitment because of potential changes to economic priorities as the

requirements change with time.

4.Customer is not sure of their requirements which is usually the case.

5.Requirements are complex and need evaluation to get clarity.

6.New product line which should be released in phases to get enough customer feedback.

7.Significant changes are expected in the product during the development cycle.

Q3 Suppose a travel agency needs a software for automating its book keeping activities the set of
activities to be automated are rather simple and are at presently being carried out manually.The
Travel agency has indicated that it is unsure about the time of user interface which would be
suitable for its employees and customer would it be proper for development team to use spiral
model for this software?

V-Model comes into the picture.V Model Software Development Life Cycle, based on same
information(requirement specification document) the development and testing activity is started.
Based on the requirement document developer team started working on the design and after
completion on design start actual implementation and testing team starts working on test planning.
Spiral model can also be used but it has some disadvantages in this case:-

1. It is a complicated approach especially for projects with a clear SRS.

2. Rules and protocols should be followed properly to effectively implement this model. Doing so,
through-out the span of project is tough.

3. It is not suitable for low risk projects.

Q4 Assume that software development company is already experienced in developing pay roll
software and has developed similar software for several customer.Assume that Software
development company has received the request for developing a payroll software for this
organization.Which life cycle model should be used Justify your answer?

Prototype model should be used when the desired system needs to have a lot of interaction with the
end users. Typically, online systems, web interfaces have a very high amount of interaction with end
users, are best suited for Prototype model. It might take a while for a system to be built that allows
ease of use and needs minimal training for the end user.

1. Since in this methodology a working model of the system is provided, the users get a better
understanding of the system being developed.

2. Quicker user feedback is available leading to better solutions.

3. It is not suitable for low risk projects.

4. Missing functionality can be identified easily.

Q5 Assume that software development company is already experienced in developing pay roll
software and has developed similar software for several customer. Assume that Software
development company has received the request for developing a payroll software for this
organization. Which life cycle model should be used Justify your answer?

Suggested model for this type of requirement is RAD model because

1. Reduced development time.

2. Increases reusability of components

3. Quick initial reviews occur

4. Encourages customer feedback

5. Integration from very beginning solves a lot of integration issue

6. software development company is already experienced

Q6 Suppose you are developing a software product of organic type you have estimated the size of
product to be 1 Lakh LOC .Compute the nominal effort and development type

Effort = (2.4)(100k)1.05 = 2.4(125.89) = 302.142.

Error = 302.142.

Tdev = (2.5)(302.142)0.38 months = 2.5(8.75)months = 21 months

Q7 For following C Program estimate the Halsteads Length and volume measure further compare
Halstead Length and volume measure with LOC measure.

main()

int a,b,c,avg;

scanf("%d%d%d",&a,&b,&c);

avg=(a+b+c)/3;

printf("avg=%d",avg);

Unique operators: main, (), {}, int, scanf, =, +, /, printf,“ ”,‘ ’,;

Unique operands: a,b,c, a, b, c, a+b+c, avg, 3,%d %d %d, avg=%d

Therefore, n1 = 12, n2 = 11

Estimated length = (12 * log 12 + 11 * log 11)=81

Volume = Length * log(23) = 81 *4.52= 366