Professional Documents
Culture Documents
Lab No1 SCD Mubashir Hussain 4979
Lab No1 SCD Mubashir Hussain 4979
Lab No1 SCD Mubashir Hussain 4979
01
Software Engineering Process Infrastructure
Following are the lab objectives:
Scenerio 01:
1. Stakeholder Analysis:
Stakeholders:
1. Foreman of warehouse
2. Warehouse worker
3. Truck driver
4. Forklift operator
5. customers
Stakeholders can include team members, customers, any individual who is
impacted by the project or it can be a supplier. Stakeholder analysis is done to
identify the stakeholders who will be impacted by the system.
In this scenario above mentioned stakeholders are involved to analyzing to
improve business.
2. Survey/Questionnaire:
In this scenario survey/ Questionnaire elicitation technique is used to better
collaboration with customers to increase sells.
3. Focus group:
By using a focus group, you can get information about a product, service from a
group. The Focus group includes subject matter experts. The objective of this group
is to discuss the topic and provide information. A moderator manages this session.
4. Document Analysis/Review
This technique is used to gather business information by reviewing/examining the
available materials that describe the business environment. This analysis is helpful to
validate the implementation of current solutions and is also helpful in understanding
the business need.
SCENERIO 02
In the context of this background, for each of the scenarios mentioned below, identify
the most appropriate problem related to the software crisis and mention the same in the
table provided.
Scenario A
Railways reservation software was delivered to the customer and was installed in one of the
metro stations at 12.00 AM (mid-night) as per the plan. The system worked quite fine till the
next day at 12.00 PM (noon). The system crashed at 12.00 PM and the railway authorities
could not continue using software for reservation till 02.00 M. It took two hours to fix the
defect in the software.
Ans:
In above scenario Time Slippage and Failure at customer Site is collectively termed as a
software crisis.
Time Slippage because the system crashed at 12.00 PM and the railway authorities could not
continue using software for reservation till 02.00 M. It took two hours to fix the defect in the
software.
Failure at Customer Site it took two hours to fix the defect in the software it took two hours
to fix the defect in the software for that time system failure at customer site.
Scenario B
A polar satellite launch vehicle was scheduled for the launch on August 14 th. The auto-pilot
of the rocket to be delivered for integration of the rocket on May 15 th. The design and
development of the software for the auto-pilot took more effort because of which the auto-
pilot was delivered for the integration on June 15 th (delayed by a month). The rocket was
launched on Sep 15th (delayed by a month).
Ans:
In above scenario Time Slippage is collectively termed as a software crisis.
Time Slippage is because the rocket was launched delay of one month, time-consuming.
Scenario C
Software for financial systems was delivered to the customer. Customer informed the
development team about a mal-function in the system. As the software was huge and
complex, the development team could not identify the defect in the software.
Ans:
In above scenario Intractable Error and Failure at Customer Site is collectively termed as
a software crisis.
Intractable Error is because Customer informed the development team about a mal-function
in the system. As the software was huge and complex, the development team could not
identify the defect in the software.
Scenario D
Due to the defect in the software for the baggage handling system. There was also of & 2M
of revenues for the airport authorities.
Ans:
In above scenario Cost Slippage is collectively termed as a software crisis.
Cost Slippage is because due to effect in the software for baggage handling system loss of 2
million dollars of revenues for the airport authorities.
The End