Mid Term Examination Fall Semester 2020

Student Name: Reg. ID:

Program: Instructor: Engr. Darakhshan
Syed/ Rida Fatima Muddassir /
Saira Khurram/ Dr. Aisha
Subject: Software Engineering Max. Marks: 25

Q. No. 1 2 3 4
Total Marks
Obtained Marks

Please follow the instructions carefully:

1. Write your answers in a Word file and upload the file before the due date on Blackboard.
2. Write your name and registration ID on the first page of your Word file.
3. Answer scripts can be uploaded on BB any time before its deadline. Therefore, do
not wait for the last hour to avoid any unforeseen problems.
4. Submission of answer copy (ies) will be considered acceptable through BB only.
Therefore, do not submit your document through email or any other medium.
5. Use 12 pt. font size and Times New Roman font style along with 1-inch page margins.
6. Follow the requirements of the word limit and the marking criteria while writing your
answers.
7. Provide relevant, original and conceptual answers, as this exam aims to test your ability
to examine, explain, modify or develop concepts discussed in class.
8. Do not copy answers from the internet or other sources. The plagiarism of your answers
may be checked through Turnitin.
9. Recheck your answers before the submission on BB to correct any content or language
related errors.
10. Double check your word file before uploading it on BB to ensure that you have uploaded
the correct file with your answers.

Page 1 of 7
 Q. No. Briefly ( max. 120 words ) define the following: Max Marks 15
1

a. Define the importance of feasibility study. Is there any possibility of not opting for it?
b. How would you relate reparability with maintainability?
c. Illustrate the idea of waterfall model with the help of graphical diagram.
d. Explain the need of project management. Is there any possibility of not opting for it?
e. Managers control confidence and excitement at both ends. Demonstrate their role with the help of a real
world example.
f. Mention a real world example of requirement capturing dilemma.
g. SRS should not have statements like “Work as expected”. Comment.

Solution:

a. Most people ignore the fact of planning with specificity. We only consider rough estimates while
planning for any project or for business ideas if you are thinking of a startup. This is where we will
need someone who would do the feasibility study. Here we consider all possible factor(also analyze
it ) which we come across while working on a project

The project manager plays an important role in executing a project smoothly. The project manager
closely works with the guy who is carrying out the feasibility study. I personally find no reason for
not opting for these beautiful learnings.

b. For a feasibility study, you will have to perform certain statistical analyses.
 Maintenance is required or to ensure longevity(life long) of the thing that you are working on.

 Repair is something which you do to a part when it is not working.

 If you are working on the longevity of a project then please go for the Waterfall model.

c. It basically is a sequential procedure in which we tackle things one after the other in order to get an
efficient product Requirements Product requirements document Design Software architecture
Implementation Verification Maintenancein the end.

Page 2 of 7
 d. In fact, you cannot move to the next step before completing the first . You have to give your best to
follow up with this model.

e. Requirement capturing tells the developers what their system must do and therefore must cover the
issues of the system inputs, outputs, functions, and attributes, along with the attributes of the system
environment. It gives all the info which the feasibility study does not.

f. SRS is documentation that includes all the parameters required and the goal to be reached. Since it
does not talk about the efficiency of the work which is being carried out, It does not have the
statement "Work as expected"

g. The manager is the one who is responsible for a smooth flow while handling a project, Hence he/she
should be confident enough to be able to lead a team all by him/her self, If he/she shows positive
confident and excitement then things can go pretty evenly.

Q. No. Select the best option with proper JUSTIFICATION. Max Marks 04
2

a. What are the characteristics of software?

i. Software is developed or engineered iii. Software can be custom built.
ii. Software does “wear out”. iv. i and iii.
Correct option: ________________________________________________
Justification: _______________________________________________________________________

b. Which falls under the maintainability of the software?

h. Reparability and Evolvability iii. Efficiency and reusability.
ii. Performance iv. All of the above
Correct option: ________________________________________________
Justification: _______________________________________________________________________

c. If the software behaves reasonably in the situations not anticipated in SRS then the software is:
i. Robust iii. Usable
ii. Available iv. Efficient
Correct option: ________________________________________________
Justification: _______________________________________________________________________

d. The solution of requirements of requirements capturing dilemma is:

i. Waterfall model iii. Agile development
ii. Prototyping iv. Spiral model
Correct option: ________________________________________________
Justification: _______________________________________________________________________

Solution:

1)

Correct Option : iv

Justification: Unlike hardware,software is logical rather than physical.It has to be designed well before producing it. In

Page 3 of 7
spite of availability of many automated software development tools, it is the skill of the individual, creativity of the
developers and proper management by the project manager that counts for a good software product.

Most software is custom-built,rather than being assembled from existing components:--Most of the engineered products
are first designed before they are manufactured, Designing includes identifying various components for the product
before they are actually assembled. Here several people can work independently on these components thus making the
manufacturing system highly flexible. In software, breading a program into modules is difficult task , since each module
is highly interlinked with other modules. Further, it requires lot of skill to integrate different modules into one.Now a
days the term component is widely used in software industry where object oriented system is in use.

2)

Correct Option : All of the above

Justification: In software development, the maintenance phase of a software system often spans 10 years or more.
During most of this time, there is a continuous stream of issues that need to be resolved (corrective and adaptive
maintenance) and enhancement requests that have to be met (perfective maintenance). The efficiency and effectiveness
with which issues can be resolved and enhancements can be realized is therefore important for stakeholders.

Another reason why maintainability is a special aspect of software quality is that it acts as an enabler for other quality
characteristics. When a system has high maintainability, it is easier to make improvements in the other quality areas,
such as fixing a security bug. More generally speaking, optimizing a software system requires modifications to its
source code, whether for performance, functional suitability, security, or any other of the seven nonmaintainability
characteristics defined by ISO 25010.

3)

Correct Option: i ( Robust )

Justification : Software behaves reasonably even in circumstances that were not anticipated in the requirements
specification.

4)

Correct Option : i ( Waterfall Model)

Justification : The waterfall model is a software model that can be adapted to produce the software. The main thing is
that if the software team adapts the waterfall model for the production of software than proper detailed planning and
proper accurate work is needed in every phase of the waterfall model. This is because while following the waterfall
model, the software team is not allowed to move to the previous phase.

Page 4 of 7
 Q. No. 3 Produce the Activity Network Diagram for the following tasks, also mention all the possible path and
highlight the critical path. Max Marks 03

Task Duration Dependency

T1 10 -
T2 15 T1
T3 5 T1
T4 5 T2
T5 5 T3
Solution:
To draw the Activity Network Diagram we need to schedule the tasks considering their Dependencies.

In the given problem Task T2 and T3 are dependent on Task T1, thus both could not be scheduled before Task T1.
Similarly, Task T4 is dependent on task T2 and Task T5 is dependent on Task T3. Considering the dependencies the
Activity Task Diagram is plotted and illustrated below.

The Critical Path is a sequence of activities considering the node which takes the highest time among a set of
candidate nodes. In the given problem (refer to Figure-1) the tasks T2, T3 are executed parallel, however, node T2 has
been considered for the critical path as it is critical taking 15 units of time. Whereas among task T4 and T5 anyone
could be considered for the critical path as both require 5 units of time.

Page 5 of 7
 Q. No. 4 Produce the results by applying COCOMO Model on the given data.
A small size project of 100 KLOC is to be developed. Software development team need to have good
experience. The project schedule is not very tight. Calculate the Effort, development time, average staff
size, and productivity of the project.
Max Marks 03

Solution:

COCOMO is constructive cost model which is used to estimate the cost, effort, development time of the software
project. There are three modes of software development in the COCOMO model-- organic, semi-detached and
embedded
The organic model is used for small sized projects where the project schedules are not very tight .The
basic equations of COCOMO to find the Effort and development times is given by formula

Effort =  

Where a = 2.4 and b =1.05 are constants which are fixed for small sized projects(organic mode)  
Lines of code KLOC = 100 KLOC
Substituting these values in above Effort formula

The Effort E in person month is 302.13 PM

The development time D is given the equation

Where c =2.5 and d =0.38 for small sized projects and effort E =302.13

The development time D in months is 21.87 M

Average staff size SS is given by equation

Effort E =302.13 PM

Development Time D = 21.87 M

The average staff size SS is 13.81 persons

The productivity P is given by equation

Page 6 of 7
KLOC = 100

Effort E = 302.13 PM

The productivity is 0.33 KLOC/PM

Page 7 of 7