CASE STUDY

IT Concepts and Systems Analysis and Design

Submitted to:
Retardo, John Christopher R.

Gryffindor
BSA 2-12

Leader: Apostol Vernie Anne

Members:
Aberca, Mary Cris M.
Ariola, Hazel Ann Kristine
Castro Nio Fernando
Gutierrez, Ruffa Mae

I. Background of the Case

 The discussion centers as Karey Williams and Tom Petroff, IT professionals (of Mondock
Co.) assigned in a new manufacturing system project, tries to determine and implement the
appropriate methodology to be used.
This project concerns with using their new relational database management system,
making this project more complex, which conflicts with the oncoming deadline beseeched by
the sponsor.
Concurrently, they are considering the Rapid Application Development (RAD)
methodology, which is faster to conduct, and to which they have no sufficient experience, for
this project.
Because the manufacturing people are not sensible about the new database system
capabilities, there is a minor argument about the actual implementation and use of the
database management system.
This study seeks to examine which methodology is appropriate to use by the IS Project
leader (Karey) considering the target date, with the intent to meet the particular needs of the
users and consequently make their work more cost-effective.

II. Statement of the Problem

Which methodology should the system development team use in this project?

What are the factors that discouraged Karey, IS project leader, from using the
organizations traditional SDLC?

III. Case Objective

i. Identify the actions that can be taken regarding the project.
ii. Assess the consequences and feasibility of each action to the fulfilment of the
project.
iii. Select the most appropriate action for the project.

IV. Alternative Courses of Action

1. Execute the project using RAD methodology.

Pros Cons

- Reduced development time. - Depends on strong team and individual

- Increases reusability of components
- Quick initial reviews occur
- Encourages customer feedback
-Integration from very beginning solves a lot
of integration issues.
performances for identifying business
requirements.
- Only system that can be modularized can be
built using RAD
- Requires highly skilled developers/designers.
- High dependency on modeling skills
- Inapplicable to cheaper projects as cost of
modeling and automated code generation is very
high.
 2. Execute the project using the traditional SDLC methodology (waterfall model)

Pros Cons

- The systems development team is more

- Time consuming
familiar with this methodology.
- Never backward (Traditional)
- Stable project requirements
- Little room for iteration
- Progress of system is measurable
- Difficulty responding to changes

3. Find another approach (e.g. agile development)

Pros Cons

- good and organized involvement of

customer and stake holder - Planning can be sometimes be dubious.
- continuous feedback - Time and efforts will be continually
- more flexible to changes required from product resources.
- team motivation - Team members must be highly skilled
- very transparent when tracing progress V.
V.
Evaluation of Courses of Action
Areas of Consideration
Software Reliability 25%
Scale and Complexity 25%
Time efficiency 20%
Cost Effectiveness 15%
Interactivity 15%
Total 100%

Based on the alternative courses of action stated, the project will be assess by the following
areas of consideration:

1. Software Reliability (25%)

This area focuses on error prevention, ways to identify potentially cause errors that might
happen at different life cycle phases and measures how closely a system matches its stated
specification.

2. Scale and Complexity (25%)

 This field shows the growing mismatch between the new relational database software of the
manufacturing project and the human ability to understand and interact with the program. It
intends to address scalability, complexity issues and the adaptability of the software.

3. Time Efficiency (20%)

This section refers to the least amount of time possible to complete the project by utilizing
the available resources necessary for the implementation, evaluation and integration of all
processes and systems.

4. Cost Effectiveness (15%)

This region sought the broad view of costs and benefits, including short and longer-term
effects that reflects the interests of project sponsor as well as the organizations employee
who will be affected by the software program.

5. Interactivity
This part distinguishes the communication process that takes place between the user which
is the manufacturing people and the new relational database system. Allowing the software
to accept and respond from the input receive.

Software Scale and Time Cost

Interactivity TOTAL
Reliability Complexity Efficiency Effectiveness
(15%) (100%)
(25%) (25%) (20%) (15%)

ACA i 10% 7% 8% 5% 3% 33%

ACA ii 8% 10% 6% 7% 7% 38%
ACA iii 7% 8% 6% 3% 5% 29%
The table above gives information on what the system development team should use among the three
approaches which has been ranked based on the given areas of considerations. The percentage showed
on each alternative courses of action (ACA) is based on the pros and cons stated. As a result, ACA ii
ranked first which also has the highest percentage of scale and complexity (10%) but the lowest
percentage of time efficiency (6%).

VI. Recommendation

After a careful examination of the implementation of the new relational database software and appropriate
methodology to use the following propositions can be made.

First, the effectiveness and scalability using the traditional SDLC methodology enables to find solutions to
more complex problems.
Secondly, traditional SDLC methodology will require time to take but it is easier to adapt by the team since
they had more experienced in using this kind of methodology.

Third, the change of manufacturing people negative attitude to the new and modernized software can be
achieved by fitting the software to the companys environment and ability to re-learn.

To conclude, it can be said that as the company use the traditional SDLC methodology, effectiveness of
the project can be assured though it will take time to finish the said approach.

VII. Bibliography:

SDLC: SDLC models Advantages & Disadvantages. (2008, October 20). Retrieved from
http://www.drdobbs.com/architecture-and-design/sdlc-sdlc-models-advantages-
disadvantage/228701074

What is RAD model- advantages, disadvantages and when to use it? (2016). Retrieved from
http://istqbexamcertification.com/what-is-rad-model-advantages-disadvantages-and-when-to-use-
it/

Rosenblatt, H. J. (2013). Understanding System Analysis and Design. Philippines: Cengage

Learning Asia Pte Ltd.

Rouse, M. Systems development life cycle (SDLC). (2016). Retrieved from

http://searchsoftwarequality.techtarget.com/definition/systems-development-life- cycle

Software development lifecycle (SDLC). (2016). Retrieved from

http://www.veracode.com/security/software-development-lifecycle