In assessment number 5, we
need to consider our school which is University of Southeastern Philippines of how
do we know that the life cycle was developed there, and also how do we know if it meets our needs?
Well, in answering this question I refer it from my previous assessment
for the system development model’s framework which is the Waterfall Model for
the cycle that out university has. Yet, waterfall model is the basis of other
system to have a progress for model’s framework. Upang matukoy nang maigi ang
Waterfall Model, ay mariing ibibigay ko muna ang kaangkop angkop na definition
nito, ito ay isang chronogical software development on which it can be seen
tulad nang isang pinong tubig na umaagos pababa na hinahalintulad sa isang
water falls. And because it so sequential and flowing in an organized manner, so
this model passes in different kind of phases. There is a process on which the
Waterfall Model has, on which one should move sa kasunod na phase only if the
preceding phase or process ay kompleto na at perpekto. The consequence of
discrete, and walang pag-iskip sa kung saan man parte ito o ang pag-exceed
between them are the developments of every phase in the waterfall model.
Nowadays, many professionals that see this approach as rigid in particular. Ang
modify and edit or develop sa waterfall model has been created all throughout
the years. Moreover, new variants of the model have been emerged. However, how
many years had passed, ang waterfall model ay nagawa sa kapanahonang iyon ni
Royce. Royce did propose as the popular named “The Waterfall Model” na
pangunahing konsepto. According to Royce, he said that the model he had created
was flawed. However, time passed and then his documentation and supported facts
about these matter ware explored by others kung papaano madevelop ng maayos ang
waterfall model to an Iterative Model. Kung naguguluhan ka kung ano ito, ito
ang modelo na may ibang method of effective structured system development
model. Maraming mga feedbacks, reviews and comments sa kanyang mga ginawang mga
theorya tungkol sa waterfall model. Lalung-lalo na sa kanyang mga nagawang
dokumentasyon kaukol nito. And one of the feedbacks is that it comes from each
phase that influences the previous phases, which is the same and comparable to
other system development models. Yet, this models is used widely and highly
regarded by many in the current days. Even if the intention of Royce of his
waterfall model idea is good to have a better and improve changing model which
is Iterative model, the Waterfall Model is still widely use in the present
because of its purely sequential and effective chronological process. And the
structure of Waterfall Model in software development ay palaging ini-rerefer to
any other approaches to software creation which is seen as inflexible and
non-iterative. Despite those obstacles and problems th waterfall model engaged
by always been attacking of how many years for being too unrealistic when it
comes in meeting the needs of the clients quickly and easily. Moreover, having
the theoretical basis for other prosesong modelo o process models because it is
for the closest resemble of generic model for improving and developing
software. May mga phases ang water model, these are the following phases, and it
is sequential order, first is Requirements Specifications, System Design,
Implementation, Integration, Testing, Installation, and Maintenance. The Requirement
specification phase, it captures all possible requirements of the system to be
developed and improved. Ang lahat nang requirements na ito on which it must be
gathered from the end user (who will be using the system) at the start of the
software development phase, peru ang mga requirements must have some set of
functions and constraints that the end user expects from the system. Pagkatapos
mangalap ng mga information o mag-gather ng datum, ang mga requirements are
analyzed for their validity whether it is valid or not or available or
unavailable. And also studied for the possibility and probability of
incorporating the requirements in the system to be developed and improved. At
ang panghuli, ito ay ang creation of a document of requirement specification
which serves the purpose of guideline para sa nasabing kasunod na phase nito.
Peru ang ibang sources had a statement that a System Conceptualization ang pinakaunang step
para sa prosesong ito because it refers to the consideration of all aspects of
the targeted business or companies’ function or process, with the aims of
determining how each of those aspects relates with one another, and which
aspects will be incorporated into the system, and the extensive communication
between the customer or client and the developer is essential or very important.
Nang dahil dito, the first step is mainly the job of a system analyst na
napakahalaga sa ganitong aspeto. The purpose of his profession in a team
project of collecting and gathering ng mga facts and detailed information and
datum. In addition to that, ang pagkakaroon ng matinding analysis on the
gathered data with the aims and goal of determining and defining how these
requirements and issues will be
accommodated in the system. At ang pinaka-unang proseso nang waterfall model is
very crucial in the hands of the system analyst and project manager because ito
ay ang foundation of the software development, and for some instances that the
system requirements they have gathered are incorrect or didn’t meet the needs
of the customers or client. And next is, they proceed in the next phase kahit na hindi
kompleto o perpekto for gathering and analysis of the system requirement, there
is a case on which in the earlier part of the doings that there is no sure for
having the proper output of making the software development and then it leads
to project failure para sa grupo. In this case, waterfall model is very
important of having a perfect na pagsisimula sa isang phase bago simulan ang
susunod na process para walang aberya mangyayari sa project at tuloy tuloy na
ito sa tamang proseso o daan sa pagtatapos nang software development. Napakahalaga
sa aspetong ito, na lahat ng kalahok sa grupong sotware development ay
mapag-matyag at mapag-obserba para matukoy o malaman kaagad ang problema sa
simula pa lamang. Kung may ganitong karakteristiks ang mga tao sa isang grupo
sa pagdevelop ng software development, malamang ay successful sila at the last
and final phase of the project. In the System and Software Design, it is really
essential in understanding the requirements well of the end user and having an
idea on how should the end product looks like before starting the actual coding
phase. Knowing it first is very important, and maintindihan mabuti anf problem
and sample output’s client. Ang pinaka unang phase of requirements
specifications are studied in the second phase and a system design is prepared.
System Design ay nakakatulong to define the overall system architecture, and
specifying hardware and system requirements. The specifications of system
design must serve as an input for the next phase. Kinakailangang mabuti na
maidentify ang mga detalye on how the system will be constructed to perform
necessary tasks after the requirements have been collected and analyzed. Thus, the System Design phase is focused on the data
requirements, and software and interface construction. Ang basehan ng second
phase’s success depends on the completion and perfection of the first phase’s
requirements gathering and analysis because the design is mainly dependable kung
gaano katama, akma o accurate, and also how worthy the data gathered from the
sources. Designing a system maybe difficult if the gathered data is inaccurate
in some reason that limited resources or limited information with the system
analyst’s lack of responsibility in working his tasks. Ang kasunod ay ang
Implementation phase, the actual coding is started here. Dito nagsisimula ang
lahat, and the work is divided in
modules or units after receiving the system design documents. The system is the
first to be developed of one small programs called units. Units, which are
integrated in the next phase. Every unit is developed or improve and tested for
their functionality and it is called unit testing. The purpose of unit testing
is to verify if the modules or units meet their specification or not. Ang
implementasyong ito ay ang phase na kung saan it can also be called programming
because this process is mainly worked by coding all those design presented
using any programming languages like java or c++ and etc. It
involves the creation of the system software. All those requirements and
systems specifications are all translated into machine readable computer code
from the System Design phase.
In the coding phase or implementation phase, one of
the important phases in the software development. Yet, there are lots of individuals must be grouped
in this process because of the complexity and kalakihan ng project of the
process that must be worked out, but it depends on the system they are working
with and the skills of the programmer possess kung gaaano ba sila kagaling o
madiskarte. Well, and also the programmer must always interact with the
designer to make their work complement each other because having
misunderstanding with their works may cause major disaster in the software
development and may also cause of wasting the important time they might use in
creating and implementing the desired design. Kung hindi nila
makipagcommunicate ng maayos sa isa’t isa ay maaring magkakaroon sila nang
communication breakdown. At kung magkakaroon ng communication breakdown ay
napakatinding abala ito para sa ibang kagrupo sa trabaho na team project kung
tatawagin. Kelangan din ang matinding team spirit sa parting ito nang sa ganuon
ay magkaroon ng epektibong output para sa mga kliyente. After creating and
implementing the designed system, it is important to have some testing of the
coded software to ensure that the system created is working well. Try and try
until it works successfully, and test and test over and over again to have the
correct output. Testing and also detecting some bugs and errors in the
programmed system are also important because working a large system might
encounter some technical errors due to overlapping statements and
functionalities in the program. In Integration and System testing, it is first
divided the system into units which are developed and tested for their
functions. After that, the units will be integrated into a complete system
during integration phase and have some testing to check if all modules or units
can coordinate each other, and the system as a whole behaves as per the
specification. Pagkatapos ng napaka successful na testing and error checking,
at ito ay wala nang mali pa sa pag- test sa mga softwares, then it is finally
delivered to the client or customer. Testing has generally focused on two
areas. These two areas are include the following: internal efficiency and external
effectiveness. The external effectiveness goal is to have verification on the
software if it is functioning according to the system design, and that it is
performing all the important functions or sub-functions. While the internal
efficiency goal testing is to make sure that the program codes is standardized,
efficient, and well documented. Nang
dahil sa iterative nature, internal
efficiency testing can be a labor intensive process. Then, ang pinakahuling
step ay ang waterfall model is the
maintenance phase, and the operations and maintenance phase is the phase of the
waterfall model which is virtually a never-ending phase. All in all, ang lahat
ng mga problema na maaring makita sa paggawa at pagdevelop ng system, ngunit
hindi ito nakikita sa panahong development life cycle, ay maari lamang malaman
at makita pagkatapos nitong i-deploy at gamitin ng mga customer kasi hindi
lahat ng mga problema maaaring mangyari ay medaling madetect habang pinaplano
at ginagawa pa ito bilang isang proyekto. Kaya ang mga isyung nauugnay sa isang
system ay maari lamang masolusyunan kapag ito ay pagkatapos maideploy ang
system. The problems are not all come into picture directly and easily but they
arise from time to time and need to be solved as fast as possible, that is why
this process is called maintenance. Ang pagmamaintain ng software ay mahalaga
din sa bawat phase na ito. Maintanance is also modifying over and over again to
have a better and improved software systems. Sa lahat ng system that have
created in any individual, establishments, companies, and organization, there
has always been a maintenance process in the software system they are using
because of the reason that there is no perfect software system that a man had
created in the technological age, and every devices, every software we are
using must have a maintenance in its lifetime. Technology is changing every
moment, therefore maintenance is very important. May mga advantages sa paggamit nang Waterfall Model in
the software development, one of it is that the work and control in the
waterfall model has a clear compartmentalization because it is easier to set
schedule for everyone’s tasks to be completed within a specific period of time
since there is a compartmentalization. Ang isa pang advantage nito is that the
waterfall model if the work of the particular phase has over after it was done
working, it is the time para makapagsimula sa kasunod na phase of the model.
Because of it, there is no overlapping of every phases or the product does not
need to have to go through different iterative steps. And most of the time managers are prefer to use the waterfall model
in their software project because it is the easiest model to use and to
implement due to its linear model. Thus, the managers are like to reduced in a
large extent the cost of its resources because the processes of the waterfall
model are carried out in a linear manner. This in turn ay nakakatulong nga
malaki in reducing the cost of the project considerably. Ang pinakahuli-hulihan
is the creation of documentation and running a test happens at the end of each
phase, which in turn, helps in maintaining the quality of the project. Kung
mayroong advantage in using a waterfall
model in a particular system development, then mayroong ding some disadvantages
with the usage of that model. Isa sa mga disadvantages is the time consuming of
gathering in all the important requirement specifications and the analysis of
all the data, because it is very essential to collect and gather all the
possible requirements in the process of requirement gathering and analysis
phase in order to properly design the system, peru hindi lahat nang panahon is that the requirements are received at once due
to some lack of cooperation of some end users or customers. Kadalasan ,
ang requirements na kelangan para gather
o collect galling sa mga customer ay pwedeng mailagay sa listahan kahit pagkatapos ng end of the process of
requirement gathering and analysis phase na makakaapekto sa system development
process and the success and development of solving the sa negatibong aspeto. And
also, kadalasan sa mga programmers na nakaka-experience na gumawa o lumikha ng
database design ay nakakaexperience din with this kind of problem arising from not well planned
project and one of it is the problem in the early phase are never been solved
completely during the timeline of working that phase. Lastly, it is a fact na
maraming mga difficulties at problema sa particular phase na hindi nasosolve
and move to the next phase of the process because ang nakikita lang nila ay ang
mga problema and errors of the previous phase when there are some mismatch and
flaws of the two phases. At ang resulta nito ay halatang-halata na not good ang
structured system design inside and outside nang dahil sa hindi lahat nang problems
are related to that phase are solved during the same phase. Yet, the other reason
is that the project is not partitioned in every phases in a flexible way
because of its linear manner. Kaya nga ang pinili kong sulosyon para maresolba
ang mga problema tungkol sa mga problema sa unibersidad, kayaga ng kabagalan ng
enrollment system, ay ang paggamit ng waterfall model kasi ang mga process nito
ay angkop para sa unibersidad. Kasi ginagawa
ng waterfall model ang striktong pagpaplano sa mga problema at masolusyunan
kaagad ang mga nakikitang depekto sa sistema.
No comments:
Post a Comment