Soften G

It's fine to celebrate success but it is more important to heed the lessons of failure.
20 copies
ACTS COMPUTER COLLEGE

Infanta, Quezon
Prelim Examination
Second Semester 2015
Name:
______________________________
Subject: SOFTWARE ENGINEERING
Score:
45
Date: _____________________
Course/Section: ____________
I. IDENTIFICATION
_________________ 1.It is an engineering discipline which is concerned with all aspects
of software production.
_________________ 2.These are events that can be used for telling the status of the
project.
_________________ 3.It is a software systems which are designed to support routine
activities in the software process such as editing design diagrams, checking
diagram consistency and keeping track of program tests which have been run.
_________________ 4.It is the fundamental process of understanding why an
information system should be built and determining how the project team will go
about building it.
_________________ 5.This software lifecycle model was first described by Royce in
1970.
_________________ 6.He proposed the incremental model.
_________________ 7.Software products developed for a single customer according to
their specification.
_________________ 8.It is a set of activities whose goal is the development or
evolution of software.
_________________ 9.It is a simplified representation of a software process, presented
from a specific perspective.
_________________ 10.
This document describes how to use the finished
software.
II. ESSAY (5 points each correct answer)
1. How do linear and iterative process models differ? What are their strengths and
weaknesses?
2. Many authors have discussed the impact of the "information era." Provide a
number of examples (both positive and negative) that indicate the impact of
software on our society with a detailed explanation.
3. Why do we need to study Software Engineering?
2ndSem~cristy_2015
Learning something new is always difficult at the start
Page 1
III. CASE SCENARIO

SCENARIO #1
Many companies are undergoing server virtualization. This is the concept of
putting multiple virtual servers onto one physical device. The payoffs can be
significant: fewer servers, less electricity, less generated heat, less air
conditioning, less infrastructure and administration costs, increased flexibility,
less physical presence (that is, smaller server rooms), faster maintenance of
servers, and more. There are costs, of course, such as licensing the virtualization
software, labor costs in establishing the virtual servers onto a physical device,
labor costs in updating tables, and access. But determining the return on
investment can be a challenge. Some companies have lost money on server
virtualization, while most would say that they have gained a positive return on
investment but have not really quantified the results.
QUESTIONS:
1. How might a company really determine the return on investment for server
virtualization?
2. Is this a project that a systems analyst might be involved in? Why or why not?
SCENARIO #2
The South Dakota Department of Labor, Workers Compensation division was
sinking under a load of paper files. As a state agency which ascertains that
employees are treated fairly when they are injured on the job, the agency had
a plethora of paper files and filing cabinets. If a person (or company) called to
see the status of an injury claim, the clerk who received the call would have to
take a message, get the paper file, review the status, and call the person back.
Files were stored in huge filing cabinets and were entered by year and case
number (for example, the 415th person injured in 2008 would be in a file
numbered
08-415). But most callers did not remember the file number and would give
their name and address and the date of injury. The clerk would look in a spiral
notebook for the last name around the date that was givenand then find the
file number to retrieve the folder. Some folders were smallpossibly
documenting a minor cut or minor injury, and the employee was back to work
after a brief treatment period. Other folders could be very large, with
numerous medical reports from several doctors verifying the extent of a
serious injury and treatment (such as an arm amputation). A digital solution
was suggestedreports could be submitted online via a secure website.
Medical reports could be submitted electronically, either as a pdf file or as a
faxed digital file. This solution would also mean that the clerk taking the phone
call could query the database by the persons name and access the
2ndSem~cristy_2015
Page 2
information in a matter of seconds.

There were legal hurdles to implementing a digital solution to handle
workers compensation claims. One hurdle was that the previous paper
method had physical signatures from employees signing off that they had
received treatment or that the doctor had signed off on medical treatment
performed. How could such permissions be preserved and duplicated digitally?
In addition, some clerks were afraid that the digital solution might not
work. What if they could not find an electronic file on the computer? What if a
hard drive crashed or the files were accidentally deleted? What if they could
not retrieve the electronic file?
QUESTIONS:
1. What legal issues might arise from having only digital signatures or only
electronic/paper copies of documents instead of physical documents? How
do these issues affect the projects feasibility?
2. In terms of organizational feasibility and adoption, what might an analyst

do to convince these clerks to adopt and use the new technology?
2ndSem~cristy_2015
Page 3

Soften G

Uploaded by

Copyright:

Available Formats

Soften G

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Soften G

Uploaded by

Copyright:

Available Formats

It's fine to celebrate success but it is more important to heed the lessons of failure.

ACTS COMPUTER COLLEGE

3. Why do we need to study Software Engineering?

Learning something new is always difficult at the start

III. CASE SCENARIO

Learning something new is always difficult at the start

information in a matter of seconds.

2. In terms of organizational feasibility and adoption, what might an analyst

Learning something new is always difficult at the start

You might also like