COLLEGE OF COMPUTER STUDIES
SYSTEMS INTEGRATION AND
ARCHITECTURE 1
EXERCISE
2
DEVELOPMENT MODELS AND ITS PRACTICE
Student Name / Group
Name:
Name
Members (if Group):
Section:
Professor:
TX31
Sir. John Darryll Mercado
Role
I.
PROGRAM OUTCOME/S (PO) ADDRESSED BY THE LABORATORY EXERCISE
●
Apply knowledge through the use of current techniques and tools necessary for the IT profession . [PO: I]
II. COURSE LEARNING OUTCOME/S (CLO) ADDRESSED BY THE LABORATORY EXERCISE
● Analyze the appropriateness of a decision to in-source or outsource IT services in a given solution. [CLO: 1]
● Apply testing environment and design a stress test using appropriate tools and techniques that impact
system performance. [CLO: 2]
III. INTENDED LEARNING OUTCOME/S (ILO) OF THE LABORATORY EXERCISE
At the end of this exercise, students must be able to:
●
●
Apply the principles of agile development and its practices.
IV. BACKGROUND INFORMATION
Agile is a process by which a team can manage a project by breaking it up into several stages and
involving constant collaboration with stakeholders and continuous improvement and iteration at every
stage. The Agile methodology begins with clients describing how the end product will be used and what
problem it will solve. This clarifies the customer's expectations to the project team. Once the work begins,
teams cycle through a process of planning, executing, and evaluating — which might just change the
final deliverable to fit the customer's needs better. Continuous collaboration is key, both among team
members and with project stakeholders, to make fully-informed decisions.
V. GRADING SYSTEM / RUBRIC (please see separate sheet)
VI. LABORATORY ACTIVITY
Background: In the early years of computers applications, the focus of the development and
innovation
were on hardware. Software was largely views as an afterthought. Computer
programming was an art.
Programmers did not follow any disciplined or formalized approaches.
This way of doing things was adequate for a while, until the sophisticated of computer applications
outgrow. Software soon took over
and more functions which were done manually. A software
houses begin to develop for widespread
distribution. Software development projects produced
thousands of source program statement. With the
increase in the size and complexity of the
software, following situation resulted is collectively termed as
software crisis.
1.
Time Slippage
Systems Integration and Architecture 1
Page 2 of 4
2.
3.
4.
Cost Slippage
Failure at customer Site
Intractable Error after delivery
VII. QUESTION AND ANSWER
Problem Description: In the context of this background, for each of the scenario mentioned below,
identify the most appropriate problem related to 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 station at 12.00 AM (mid-night) as per the plan. The system worked quite fine till the next day
12.00 PM (noon). The system crashed at 12.00 PM and the railways authorities could not continue using
software for reservation till 02.00 PM. It took two hours to fix the defect in the software in the software.
Scenario B: A polar satellite launch vehicle was scheduled for the launch on August 15th. The auto-pilot
of the rocket to be delivered for integration of the rocket on may 15th. The design and development of
the software for the auto-pilot more effort because of which the auto-pilot was delivered for the
integration on June 15th (delayed by a month). The rocket was launched on Sep 15th (delayed by a
month).
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.
Scenario D: Due to the defect in the software for the baggage handling system. There was also a loss of
$2M of revenues for the airport authorities.
Scenario
A
B
C
D
Situation (as given A to D)
Time Slippage
Failure at customer Site
Intractable Error after delivery
Cost Slippage
Systems Integration and Architecture 1
Page 3 of 4
Scenario A: Customers were unable to use the program to reserve seats between 12:00 PM and 02:00
PM due to a system crash. The system crash could have been caused by the time format utilized during
development. It might have employed a 12-hour format. This situation is comparable to the global
dilemma of the year 2000. It's a Time Slippage issue.
A possible option is to use a 24-hour format while building or patching the software.
Scenario B: This problem statement can be classified as a Failure at the Customer Site. The rocket's
autopilot was ready for delivery on time. However, the software's design required more time, thus it was
delayed. Without the software, the autopilot could not be implemented.
A possible answer is to begin the software development process as early as possible.
Scenario C: This problem statement falls into the category of "intractable error after delivery." The
software had been released to consumers when an insurmountable fault was discovered. Because the
software was so large and complicated, it was impossible for software developers to identify and correct
the issue.
A possible method would be to divide the entire software into modules during development. It
would be easier to track and solve errors if the software was built in multiple modules rather than a large
number of statements in one or two.
Scenario D: This problem statement can be classified as "Cost Slippage". Sometimes a minor error or
fault in software might result in a significant loss for an organization. This is what occurs here.
A possible option is to test the software at different stages of development, such as unit testing,
integration testing, and so on. Some businesses may need to hire ethical hackers to test for various
vulnerabilities.
VIII.REFERENCES
● Imani, M and Radziwill, N. (2020). Computerized Maintenance and Asset Management: Improving
Quality Through Systems Integration. Software Quality Professional.
● Dube, M. et. al (20202). Preventing Harm: Testing and Implementing Health Care Protocols
Using Systems Integration and Learner-Focused Simulations: A Case Study of a New Postcardiac
Surgery, Cardiac Arrest Protocol.Clinical Simulation
Systems Integration and Architecture 1
Page 4 of 4