Prototyping and Testing – to ensure that the project is in
good quality especially in the early stages. Workshop – bringing stakeholders
together to discuss what else is needed and ensure that everyone is on the right
track. Modelling and Configuration management – visualising the domain and
producing the final product making sure the deliverables are well managed for
this to achieved.
Advantages: It is managed
properly. Each team member has a role in the system. The Project Manager
ensures that the team carries out their tasks swiftly and up to quality and
communication is a vital key in this development to ensure mistakes and changes
are addressed. Time and resources are well used in order to stay within the
deadline and the budget set.
Disadvantages: As it is heavily
team based with different roles, mutual understandings can be difficult especially
if each role has a different take on the project.
DB Design (DB Normalization), GUI Design (forms and reports), Data
Physical DB Design, Design Elements – Classes, Systems, Components –
can combine, split or eliminate classes, GUI Design, Booch, UML, RAD
Scrum, Timeboxing, Extreme Programming
Based on objects instead of data or processes. Object is a structured
that contains attributes and behaviours of a real-world entity
Focuses on the communication and involvement of all stakeholders in
the system to produce a successful outcome.
Smaller projects that are planned out with precise and known
Bigger Projects that have a higher risk of user changing the
Small/Medium size team projects. If any bigger it can be too much work
to manage and won’t be as efficient
DFDs, Structured English, Decision Table/Tree, ER Analysis. (Decision
Tables can be made which represents the logic of a decision and specifies the
possible conditions for the decision which results in an outcome – best used
for complicated decisions and logic)
Uses Case Models (Flow of Events, Activity Diagram), Object Model –
Object Interaction – Object to ER Mapping
8 Principles for team to get into the right attitude and mindset in,
Timeboxing – ensuring team breaks down tasks and meets deadlines, MoSCoW – technique
for prioritising work items or requirements
There is little room for flexibility as most of the techniques used in
Structured is linear and therefore leaves little to no room when it comes to
needing to change something midway through.
In Object Oriented approaches, the outcome is always being changed or
extended which provides a good advantage to certain businesses that need to
be flexible to a lot of changes and additional things such as game
A lot of flexibility in every project kind. Advantageous if change is
needed to be done when an issue arises – will not be an issue to do a change
in this Dynamic approach.
Not much influence as the cycle and data is linear and set. If changes
are made it would make it complicated and will most likely not make the system
Have a lot of influence as they are able to provide change in between
and after the system. The diagrams and flow charts provided to them gives
them guideline and awareness of what is happening in each cycle.
In Dynamic approach, as everyone is working together and following a
system to ensure they are on the right track – each team member will be able
to voice out their opinions so the Project Managers can keep an eye out for
any possible complications than can be avoided.