1.Throwaway prototyping Methodology
This methodology is almost the same with prototyping-based Methodology,
only on the methodology of this phase of the analysis done first to capture the concept
of a system that will be created. Phase analysis, design and Implementation,
which is conducted with the prototype design will result, not the system as a prototype
produced Methodology-based prototyping. Design work is not a prototype system,
but the product that represents part of the system that need to be refined,
which only contain enough detail for users to issues in the development process.
For instance, analysts will create some HTML to the line can be accessed
by a user to design a system that is being built.
Advantages of this methodology is the use of the prototype that can overcome the main
problems in the development of the system before it was built.
This methodology requires more processing time than with the long-Based
Prototyping Methodology given the prototype produced is not a system, but the methodology
is usually generate a system that is more stable and more reliable.
2. Agile Development Methodology
This methodology has rules that simple, so easy to follow. This methodology focused
on the improvement of the SDLC methodology with the modeling and documentation to eliminate excessive and reduce the time needed to perform the work. Examples of this methodology is the Extreme programming (XP), Scrum and Dynamic System Development Method (DSDM).
3. Extreme Programming
Extreme programming (XP) by 4 based on the value of primary, namely communication,
simplicity, feedback and courage. XP is usually used for project development information
system, which is the main constraint of time, where the owner desires a system of
information quickly finished because soon will be used for operations.
Three main principles that should be held in a developing system using XP is continually
testing, simple coding done by the developer and interaction with end users to build
systems quickly and precisely.
For projects that its small scope with high motivation, kohesif, stable and have
experienced team members, XP will be very appropriate use. However, for projects
that have a large scope with the condition of the team members who are less compact,
how this will affect the success of the project.
In addition to the above methodology, the development of information systems strategy
also can be outsourced to third parties to minimize risk. There are several considerations
that must be considered before the company decided to mengoutsource development of
the system, because if not, then the results will be obtained kauh worse than
developing their own (In-house).