66 CIS -Management Information Systems - Group Work #9
4/3/12 11:30 PM
Group Work #9 SOLUTION - "Systems - Development Approaches" ....due dates in-class Sec #4507
(April 16, 2008) & online Sec #5414 (April 19, 2008)
What kind of approach (methodology) would you choose for the following application solutions? Justify your
decision. (e.g., Traditional systems life cycle, prototyping, software package-based development, fourthgeneration development and outsourcing) Refer to Ch#14 pgs 506-523 (Sec 14.3 - Overview of Systems
Development and Sec 14.4 - Alternative Systems-Building Approaches)
The answer will depend on the package selected but the purpose of the exercise is to get students to think
about how well packages can or can't meet information system requirements and the types of questions they
should be asking. For example, for a payroll package, a student might ask whether there are any limits on the
number of employees that can be paid at one time or maintained on the system; how many different kinds of
overtime calculations the system will handle; how many different kinds of deductions the package will support;
whether the package will cut checks; the kind of check forms required by the package for cutting checks, etc.
The student must ask about hardware and operating system requirements for the package (what kind of
machine it runs on, RAM size required to run the package, operating system required by the package, etc.
a)
A system for tracking job applicants at six different branches of a nationwide retail chain.
Tracking job applicants, like accounts payable or payroll, is a function performed similarly by all organizations.
Therefore, software package-based development would be appropriate. A software package is recommended
for this application because tracking job applicants is a standard need for almost all businesses. Software
packages are designed to solve problems, which are encountered by all organizations and require the same
or very similar system information solutions.
b)
A money market account system for a major regional bank.
This system will be heavily transaction oriented and therefore will probably require a large mainframe-based
system with highly complex, technical requirements. The problem is a clearly defined one and should be
appropriate for traditional systems life cycle development. Prototyping this application is dangerous because
this approach does not stress testing and documentation and because the system is too massive and
complex, although it could be used for input screens and reports. Fourth-generation solutions are also
inadequate because they require more computer resources to process information than conventional
languages and, as a result, do not have the capacity to handle large transaction-based applications.
c)
A system to evaluate the financial and tax consequences of purchasing rental property.
This is a small decision-oriented application, which would lend itself to prototyping. However, the application is
fairly small and simple and could easily be implemented on spreadsheet software or with microcomputer
application software package. Prototyping might not be required.
d)
A medical and dental claims administration and payment system for 14,000 employees of a
major corporation.
Data requirements and processing rules in such a system are very straightforward and clearly defined.
Calculations in a claim administration system are not as complex as those in a money market account system.
Although the system services 14,000 employees, only a small portion send in claims every day, so the daily
transaction volume is quite small. This system might be a candidate for fourth generation development
(although it could also be developed using the traditional life cycle approach).
______________________________________________
Sujan Sarkar - CIS Instructor, Santa Rosa Junior College
Updated Wednesday August 20, 2008
http://www.santarosa.edu/~ssarkar/cs66fl08/gw/gw9s.htm
Page 1 of 1