Selection of methodology - System Analysis and Design

Selection of
Methodology
By Sivasankar Sutharshan
Batch of IT- 41
British College Of Applied Studies

What is Methodology and why its important?
• It’s and approach to managing the Project Life Cycle from beginning to end of a project.
(Project can be a system designing or any kind of organization projects)
• Provides a consistent approach to managing all kind of projects. (small, medium and
large)
• Provides a predictable roadmap for organizing and storing information on projects.
• Provides a framework for continuous improvement, analyze and improve efficiencies of
work efforts and resource utilization of a projects.
• Examples:
Process-Centered
Data-Centered
Object-Oriented

Rapid Application Development
• RAD is an object-oriented approach to systems development that includes a method of
development as well as software tools. (Use programming methods which are objectoriented for hardware and software to accomplish a rapid development cycle)
• RAD life cycle is composed of the following Stages :
Requirements
Planning Phase
•Meeting of clients,
managers and
developers to discuss the
needs, project scope and
requirements of the
system that need to be
developed.
•This phase done when
agreement and the
managers give the
approve to continue.

User Design Phase
• Design the process
where clients see a
working prototype and
give input on new
requirements to the
changes id its needed.
• Use CASE Tools,
Design Methods to
create and understand
requirements. This
phase repeatedly
carried until the
clients agree upon a
prototype.

Construction
Phase
• Develop actual
system based on
the design.
• Clients can
interact with this
phase and give
input on changes
they would like to
see even during
the system
development.

Cutover Phase
• Includes data
conversion, testing
and
implementation of
chosen system.
• Finally, user
training.

Waterfall Model
• This model developed for software development that is to create software which develops
systematically from one phase to other. There is no overlapping in the phases. ( it can be
implemented for any size project)
• Waterfall model is composed of the following Stages :
Feasibility
Study
• Checks
whether
development
system is
possible to
achievable or
not.

Analysis
Phase
• Gathering
all
requirement
s of the
system to be
developed
and would
be
documented

Design
• It involves in
formulating
the basic
design
system based
on
requirements

Development
• After the
basic
design gets
approved
the develop
design can
be process
based on
design.

Implementation
• The source
code of the
programs is
written or
implementing
system into
client
environment.

Integration
and testing
• The system
is put under
a test to
check its
functionality
.
• The client
puts it in use
after the
system has
been
successfully
tested

Maintenance
• Check the
system is
working
and ensure
that the
system will
continue to
perform as
desired.

Comparison
Waterfall Model


•

Old Development Model.

•

•

Can implement and manageable for any kind of projects.

•

Can implement and easy manageable for small projects.

Relatively slower because it takes long time between
system proposal and delivery of new system.

•

Relatively faster because it’s a faster development life cycle.

•
•

•

Client involved only in requirements analysis phase.
Once this phase done is impossible to add or update the
requirements of client.

High amounts of risk and uncertainty.

•

•

Newer Development Model which means decentralized
development where most tasks are broken down into
separate stages.

Customer involved throughout the complete life cycle. Its
possible to add or update the requirements of client before
completion.

Reduce Risk.

Comparison
Waterfall Model


•

Uses outdated documentation and testing techniques.

•

Can corporate new techniques.

•

Low customer satisfaction.

•

High customer satisfaction.

•
•

•
•

Increase end-user functionality. (which means more
complexity )

If client requirements may change the Waterfall model
may not work.

Documentation is relatively process at each stage.

Inflexible because in real projects rarely follow the
sequential flow and phases overlap.

•
•

Decreased end-user functionality. (which means reduced
complexity )

If client requirements may change the RAD model may
work.

•

Documentation is relatively less.

•

Flexible.

Selected Development Model is RAD
• Faster Deliver time of system: rapid prototyping and by using automated tools such as Computer Aided Software or
CASE tools will be enable the developers to generated codes easily and saves the time needed for manual coding.
• Better Quality: RAD improves the system quality by meeting the requirements of the clients at every stage and by
providing a considerable reduction in the errors by the use of automation tools and prototyping.

• Reduced cycle time and improved productivity with fewer people which means lower costs.
• Minimize risks because the time-box approach of RAD model may mitigates cost and schedule risk.

• Can meet client satisfaction and business need of BCAS because client involved throughout the complete life cycle.
• Implementation is less stressful since users or clients helped to design the business aspects of the system.

Selected Development Model is RAD
• More developers can be involved in the development stages.
• Each person gets smaller tasks but plays an important role so the performance would be more efficient.
• Simplicity and usability of GUI design. So students and staffs would interest in the development.
• The selection of RAD model meets the following, appropriate and ensure RAD model is strong enough for course
management system.
 The scope of Course management system is well defined and narrow.
 Data for Course management system is already available in the admin department.
 Decisions would made by a small number of people. (Managers and Staffs)
 The project team is small because the Course management system for BCAS is smaller system
compare to current industry.
 The technical requirements are affordable for Course management system.

References
• Tutorialspoint (NA), SDLC Waterfall Model(Online), NA, Available at:

http://www.tutorialspoint.com/sdlc/sdlc_waterfall_model.htm [25th of Sep 2013]
• Dave Rooney (NA), Waterfall vs. RAD vs. RUP vs. Agile (Scrum, XP, etc.) (Online), NA, Available at:
http://practicalagility.blogspot.com/2008/11/waterfall-vs-rad-vs-rup-vs-agile-scrum.html [25th of Sep 2013]
• Myriaddevices (2012), Part 1 of 2: Mini Enterprise and Rapid Application Development (Online), NA, Available
at: https://www.myriaddevices.com/part-1-of-2-mini-enterprise-and-rapid-application-development/ [25th of Sep
2013]
• Bauer, M. (2005). Successful Web Development Methodologies Article. [Online] Available at:
http://www.sitepoint.com/successful-development/ [25th of Sep 2013]
• Sommerville, I., (2001), Software Prototyping. In: A. D. MacGettrick, ed. Software Engineering. 6th ed. India:

Pearson Education, pp. 175-179.
• Welling, L. ( 2006), Applying A Waterfall Methodology to Web Development [Online] Available at:
http://www.waterfall2006.com/welling.html [25th Sep 2013]

Any Questions and
Improvements are
Welcome  !!!!!

Presented By Sivasankar Sutharshan
Batch of IT- 41
British College Of Applied Studies

Selection of methodology - System Analysis and Design

More Related Content

What's hot (20)

Similar to Selection of methodology - System Analysis and Design (20)

Recently uploaded (20)

Selection of methodology - System Analysis and Design

Editor's Notes