System Development Methodologies Cheat Sheet

by Natalie Moore (NatalieMoore) via cheatography.com/19119/cs/9758/

Key aspects of a method​ology Extreme Progra​mming (XP) Method​ology Extreme Progra​mming (XP) Method​ology
(cont) (cont)
Should promote activity which is:

- Purposeful - Design Improv​ement Testing code is good. Therefore, in XP, tests

are written before the code is written. The code
- Small Releases
- Controlled
is considered complete when it passes the tests
- Shared unders​tanding
- Rigorous (but then it needs refact​oring to remove
- Simple design comple​xity). The system is period​ically, or
and produce results that are:
- System metaphor immedi​ately tested using all pre-ex​isting
- Meaningful
automated tests to assure that it works. See
- Reprod​ucible - Collective code ownership
test-d​riven develo​pment.
- Coding standards or coding
- Relevant
conven​tions
What can go wrong?
Remember that a method​ology is only a means
- Programmer welfare
to an end and not an end in itself Deadlines
- Sustai​nable pace (i.e. forty hour week)
Equipment
Dynamic Systems Develo​pment Method Coro​llary practi​ces
Requir​ements
Image
Intera​ction between developers and customers
Vendors
is good. Therefore, an XP team is supposed to
have a customer on site, who specifies and
Re-use - Search for ‘Short​-Cuts’
priori​tizes work for the team, and who can
answer questions as soon as they arise. (In Re-use, clone, develop
practice, this role is sometimes fulfilled by a
Packages (modif​y/t​ailor)
customer proxy.)
Share code/l​ibr​ari​es/​buy-in
If learning is good, take it to extremes: Reduce
the length of develo​pment and feedback Build new interfaces

cycles. Test early. Umbrella systems

Simple code is more likely to work. Therefore, Leverage existing system​s/e​xpe​rience

extreme progra​mmers only write code to meet
actual needs at the present time in a project, Top tips
and go to some lengths to reduce complexity
Extreme Progra​mming (XP) Method​ology and duplic​ation in their code. Avoid Poor Estimating and/or Scheduling

For creating software within a very unstable If simple code is good, re-write code when it Avoid Ineffe​ctive Stakeh​older Management
enviro​nment becomes complex. Avoid Insuff​icient Risk Management

Allows flexib​ility within the modelling process Code reviews are good. Therefore XP Avoid Insuff​icient Planning

Main goal to lower the cost of change in progra​mmers work in pairs, sharing one screen
Avoid Shortc​hanging Quality Assurance
software requir​ements and keyboard (which also improves
commun​ica​tion) so that all code is reviewed as Avoid Weak Personnel and/or Team Issues
XP Core Practi​ces
it is written. Avoid Insuff​icient Project Sponso​rship
- Fine scale feedback

- Test driven develo​pment Why do we have different types?

- Planning game Degrees of the problem domain, hard and soft

- Whole team Peoples particular mind sets

- Pair progra​mming Easier to use hard approaches

- Continuous process rather than batch Soft provide greater insight

- Continuous Integr​ation

By Natalie Moore Published 8th November, 2016. Sponsored by CrosswordCheats.com

(NatalieMoore) Last updated 8th November, 2016. Learn to solve cryptic crosswords!
cheatography.com/nataliemoore/ Page 1 of 3. http://crosswordcheats.com
www.speedwell.com.au/
 System Development Methodologies Cheat Sheet
by Natalie Moore (NatalieMoore) via cheatography.com/19119/cs/9758/

Dynamic Systems Develo​pment Method Dynamic Systems Develo​pment Method Systems Develo​pment Life Cycle (SDLC)
(DSDM) (DSDM) (cont) Method​ology (cont)

Princi​ples: - Long iteration of refine​men​t/a​gre​ement 4. System is developed

- Active user involv​ement is imperative - Contacting key partie​s/a​rra​nging meetings - Components and programs must be
obtained and installed.
- Focus is on frequent delivery of products - Cycle of meetings

- DSDM teams must be empowered to make - Resolving different views/​per​spe​ctives - Users must be trained

decisions - Perfor​mance must be tested.

- Changing requir​ements during process
Adjust​ments must be made at this stage.
- Fitness for business purpose is the - Loss of moment​um/​com​mitment
essential criterion for acceptance of 5. System is deployed
Deliver on time to budget
delive​rables
- might be phased in
Does not cut important corners
- Develo​pment is iterative and increm​ental
- shut down the old system and implement
Results from practical experience
- All changes during develo​pment are the new system all at once
reversible
6. Monitor and maintain
Systems Develo​pment Life Cycle (SDLC)
- Requir​ements are baselined at a high level - Evaluate system post deploy
Method​ology
- Testing is integrated throughout lifecycle - Mainte​nance must be kept up
Conceptual model used in project management
- Collab​orative and co-ope​rative approach - Users should be kept up to date
between stakeh​olders is essential Water fall was original
Bene​fits
Key Features Describes the stages involved in systems dev
project Clear project object​ives.
- Deliver quickly and often (timeb​oxing)
Docume​ntation is crucial Stable project requir​ements
- Critical functi​onality delivered (MoSCoW)
Docume​ntation is done in parallel with the Progress of system is measurable
- Joint Applic​ation Develo​pment workshops
develo​pment process
(JAD) Strict sign-off requir​ements
Most important factor project success may be Disa​dva​nta​ges
- Protot​ypi​ng/​tools used to validate user
how closely the plan was followed
requir​ements Time consuming
Steps:
- Re-use Little room for iteration
1. If there is an existing system its
- Extreme Progra​mming (user stories, paired Difficulty responding to changes
defici​encies are identi​fied. Iterview users,
progra​ming, focus on commun​ication and
consult with support personnel
teamwork) Protot​yping
2. New system requir​ements are defined
- Requir​ements not fully defined before
Protot​ypi​ng/CASE tools
develo​pment - addressing any defici​encies
Ability to deliver quickly
- Culture change - with specific proposals for improv​ement

3. System is designed, plans created for: Experi​men​t/try out ideas

Benefits - overcomes:
- hardware Project management

Encourages re-use
- operating systems

- progra​mming Version control

- security issues Automates testin​g/s​ystem cut-over

Prototype is the technical specif​ica​tion, a

repository provides self docume​ntation

By Natalie Moore Published 8th November, 2016. Sponsored by CrosswordCheats.com

(NatalieMoore) Last updated 8th November, 2016. Learn to solve cryptic crosswords!
cheatography.com/nataliemoore/ Page 2 of 3. http://crosswordcheats.com
www.speedwell.com.au/
 System Development Methodologies Cheat Sheet
by Natalie Moore (NatalieMoore) via cheatography.com/19119/cs/9758/

Rapid Applic​ation Develo​pment (RAD) Scrum Method​ology Practi​tioner Advice

Different versions exist Agile method Senior management should support the project

DSDM (Dynamic Systems Develo​pment Goal is to dramat​ically improve produc​tivity in whole heartedly

Method) teams previously paralyzed by heavier, Detailed planning should be undertaken

proces​s-laden method​ologies Project management principles should be
MOSCOW Rules Char​act​erized by applied

Must have – without these features the project - A living backlog of priori​tized work to be The key business objectives should be
is not viable (min. CSFs) done identified and kept in focus

Should have – to gain maximum benefit, these - Completion of a largely fixed set of backlog Requir​ements should be evolved over time by
features will be delivered items in a series of short iterations or the use of protot​ypes.
sprints Organi​sat​ional politics must be considered and
Could have – if time and resources allow these
features will be delivered - A brief daily meeting (called a scrum), at navigated
which progress is explained, upcoming Ensure adequate investment is made
Won’t have – these features will not be
work is described, and obstacles are raised
delivered Develop realistic implem​ent​ation timescales
- A brief planning session in which the
Use an approp​riate develo​pment
backlog items for the sprint will be defined
Waterfall (a.k.a. Tradit​ional) Method​ology approa​ch/​method for the context
- A brief heartbeat retros​pec​tive, at which all
Version of the systems develo​pment life cycle Identify users and stakeh​olders and involve
team members reflect about the past sprint
model them
- Facili​tated by a scrum master
Classic approach Ensure you have skilled, proactive IT/IS people
Scrum master role
Rigid and linear Changing requir​ements should be recognised
- Primary job is to remove impedi​ments of as a normal occurrence and systems need to
Distinct goals for each phase of develo​pment
team to deliver sprint goal be put in place to facilitate this
Each phase is completed before the next one is
- Not leader of team (team is self-o​rga​nizing) The technology itself should be proven
started
- Acts as produc​tivity buffer between team Any contra​ctors should be managed as if they
There is no turning back
and destab​ilizing influences were an internal team
Benefits
Bene​fits: Problems should be evaluated and where
- allows for depart​men​tal​ization relevant resolved as they are encoun​tered and
Enables creation of self-o​rga​nizing teams
- allows for managerial control not ignored
Encourages verbal commun​ication across
- Deadlines team members and across discip​lines As a last resort, if serious problems are
encoun​tered, project timescale should be
- In theory project will be delivered on time Adopts an empirical approach - accepting the
delayed, rather than risk a disaster
due to planning and process problem cannot be fully understood or defined,
Problems focusing instead on maximizing the team's
ability to respond in an agile manner to
- often falls short of expect​ations
emerging challe​nges.
- does not embrace the inevitable changes
and revisions that become necessary with
most projects

- Once an applic​ation is in the testing stage, it

is very difficult to go back and change
something that was not thought of in the
concept stage

By Natalie Moore Published 8th November, 2016. Sponsored by CrosswordCheats.com

(NatalieMoore) Last updated 8th November, 2016. Learn to solve cryptic crosswords!
cheatography.com/nataliemoore/ Page 3 of 3. http://crosswordcheats.com
www.speedwell.com.au/