DESCRIPTION PROCESS MODEL [DPM]

WATERFALL MODEL


ACTIVITY INPUT ARTIFACTS OUTPUT
ARTIFACTS
ROLES TECHNIQUES/
TOOLS
PROJECT
PLANNING
PROJECT DECISION
INTRODUCTION
BASIC
REQUIRMENT
PROJECT
MANAGER
INTERVIEW
LIST OF REQUIRMENT
FACTORS ;
PROJECT BUDGET,
PROJECT MILESTONES,
RESOURCES ALLOCATION.
PROJECT PLAN PROJECT
MANAGER AND
SENIOR
MANAGMENT
NONE
REQUIRMENT
ANALYSIS AND
DEFINITION
PROJECT PLAN REQUIRMENT
SPECIFICATION
KEY
CUSTOMERS
INTERVIEW\CRO
WDSOURCING
REQUIRMENT
SPECIFICATION
SET OF USE CASES FEATURE
OWNER AND
CHIEF
ARCHITECT
NONE
SET OF USE CASES INFO. EFFORT
ESTIMATES AND USE
CASES
FEATURE
OWNER AND
CHIEF
ARCHITECT
NONE
SYSTEM AND
SOFTWARE
DESIGN
SPECIFICATION
DOCUMENT
SYSTEM
ARCHITECTURE
KNOWN AS HIGH-
LEVEL DESIGN
ARCHITECT GRAPHICAL
NOTATION
THE SYSTEM
ARCHITECTURE
@
HIGH-LEVEL DESIGN
SUB-SYSTEM OR
MODULES ALSO
KNOWN AS LOW-
LEVEL DESIGN
CHIEF
ARCHITECTURE
NONE
SUB-SYSTEM OR
MODULES ALSO
KNOWN AS LOW-LEVEL
DESCRIPTION OF
MODULES INTERFACE
CLASSES
PROJECT
MANAGER AND
FEW KEY
GRAPHICAL
MODELLING
LANGUAGE

HALAMAN 1
DESIGN DEVELOPERS
JAVA CODING IMPLEMENTED
MODULES
DEVELOPERS ECLIPSE
DEVELOPMENT
ENVIRONMENT
IMPLEMENTAT
ION AND UNIT
TESTING
SYSTEM TESTING COMPUTER AND
CORRECT OF THE
FUNCTIONAL AND
NON-FUNCTIONAL
REQUIRMENT
TESTER NONE
FUNCTIONAL AND
NON-FUNCTIONAL
REQUIRMENT
STATEMENT
COVERAGE
TESTER NONE
FAILURE REPORTS CORRECTION IN
SOURCE CODE
DEVELOPERS ANALYZING
ACCEPTANCE TEST FAILURE REPORT SET OF PILOT
CUSTOMERS
PROTOTYPING
FAILURE REPORT REWORK THE SOURCE DEVELOPERS NONE
[ON GOING] UPDATED SYSTEM SET OF PILOT
CUSTOMERS
REPORT


A)
As we talked about Waterfall Model, its a framework for software development in which
development proceeds sequentially through a series of phases, starting with system
requirements analysis and leading to product release and maintenance. But, there is a
advantages and drawback to this Model. As at the end of the activity that we asked to carried out
by our lecture we noticed that this model is simple and easy to use. It also easy to manage due to
the rigidity of the model where each phase has specific deliveries and review process. The phases
are processed and completed one at a time so there is no skipping process been done. This
model works well for smaller projects where requirements are very well understood. The process
also has its drawback where once the application is in the testing stage, it is very difficult to go
back and change something that was not well-thought out in the concept stage. If the early stage
not well carried out its defect the whole software making process so sure that there is no
working software is produced until late during the life cycle. This whole project will be put into
delayed and also has a high amounts of risk and uncertainty. Waterfall Model also not a good
model for complex and object-oriented projects. It is a poor model for long and ongoing projects
and not suitable for the projects where requirements are at the moderate to high risk of
changing. We used Waterfall Model where the requirements are very well known, clear and
fixed. The product definition also has to be stable and the technology is well understood. There
are no ambiguous requirements and ample resources with required expertise are available freely.
One last thing to keep in mind is that this Model is suitable for short project only.
Along the way of making the process, we noticed that theres a few suitable and
unsuitable process as that we have to change. As for this Company ABC, we dont really know
how big is the development should be due to the lack of information regarding on the project
cost and budget. But, as we know first stage on the Waterfall Model is that the first stage which
HALAMAN 2
is PROJECT PLANNING where it is a crucial part where the project early development is all
about. So, it is very suitable for any project development either big or small project. But as we
noticed along the way, we come across this second stage known as REQUIRMENT ANALYSIS
AND DEFINITION. The stage is not really necessarily when we already plan everything at the
first stage and we can combine the second stage and by any meant we are not saying that the
stage is not important but it is combined into one stage that is PROJECT PLANNING where this
two stages will be combined into one phases but yet two different thing.


B) INTRODUCING PRINCE2 (Similar to WATERFALL) and SCRUM.

Along the way of choosing the best model and classified it either suitable or not for our
project we should think about various way to make our project manageable and successful and
reduce the risk factor that could make us lost our time and money, So the idea was to combine a
different model to become one model that suit our project perfectly as in mind we have many
different model but what comes in mind is that has the similarity to the Waterfall Model which
is PRINCE2 where many people assume that this model is a process prescribes a Waterfall
approach to the projects execution where a stage is equivalent to a stage in the waterfall
methodology. Where there should be a stage for each of Analysis, Design, Development and
Testing. And before moving from Design to Development, the project requires a locked-down,
complete and comprehensively detailed set of requirements. But sometimes this method is
inappropriate for small projects or where the requirements are expected to change throughout
the project similar to the Waterfall Model. PRINCE2 is a structured approach to project
management. It provide a method for managing the projects within a clearly defined framework.
It coordinate people and activities in a project, based on how to design to how to supervise the
project, and what to do if the project has to be adjusted if it doesnt develop as planned.
PRINCE2 project divided into a number of Management Stages, each forming a distinct unit of
management purposes. It defines the set of products and activities, a life-span, control element,
and an organizational structure. It also identifies the roles rather than jobs. The PRINCE2
methodology applies three key elements to each project and to the Management Stage within a
project. This three elements can be process which drive the project management, Components
and the Techniques, which are used by each of the Processes to effect the management of the
project.

PRINCE2 defines 45 separate sub-processes and organizes these into eight processes:
1) Starting Up A Project (SU)
2) Initiating A Project (IP)
3) Directing A Project ( DP)
4) Controlling A Stage (CS)
5) Managing Product Delivery (SB)
6) Managing Stage Boundaries (SB)
7) Planning (PL)
a) PL1 Design a Plan
b) PL2 Define and analyze products
HALAMAN 3
c) PL3 Identify activities and their dependencies
d) PL4 Estimate effort and each activity
e) PL5 Schedule
f) PL6 Analyze risk
g) PL7 Complete Plan.
8) Closing a Project (CP).



We now can watch closely from our observation that this Two type of model has some
similarities where it is where between the stages Communication with PRINCE2s starting
up a project (SU), Planning with PRINCE2s planning (PL), Controlling a Stage (CS),
Modelling and Construction with PRINCE2s initiating a Project (IP), Directing (DP),
Managing Product Delivery (MP), Managing Stage Boundaries (SB) and Deployment with
PRINCE2 is another version of the WATERFALL model for project managers when used for
software project but in a good way. But using PRINCE2 is not enough when we have several
method that we can incorporated with such as SCRUM where we noticed that by
incorporated this two method produced a good method for developed a better management
where scrum the drawback of when we used only SCRUM is that its demands the
incorporated of the customers (user) in sprint planning and sprint reviews, yet remain a
concerning the involvement of the customer. PRINCE2 in contrast is, unequivocally
demands the incorporation of the customers point of view at senior level in the uppermost
committee of the project. The advantages of the integration lies in the stabilization of the
entire system.

HALAMAN 4




REFERENCES ;
http://www.prince-officialsite.com/AboutPRINCE2/PRINCE2Method.asp
http://agilewaybysuman.blogspot.com/2011/12/prince2-vs-waterfall.html
http://p-a-m.org/2013/05/prince2-with-scrum-%E2%80%93-or-%E2%80%93-scrum-with-
prince2/