Procedure Modules Flashcards
Definition Procedure Model
…organizes a process in different structured phases
…have specific methods and techniques for each phase
…are helpful organizational devices for concrete tasks
…can be adapted (tailoring) for individual/specific problem
…lead to a concrete action plans
…follow a stepwise approach from problem/task to solution
…have a systematic rational procedure
…phases are idealistic
…have very often a iterative characterization
…should include milestones to mitigate risks, costs and failing
…are very often used for projects
![](https://s3.amazonaws.com/brainscape-prod/system/cm/281/952/055/a_image_thumb.png?1562347197)
Problem Solving including some methods and techniques ( Six-Step Problem Solving Model)
Steps are repeatable
• At any point a return to an earlier step is possible
• Could be used for improvement projects too
• To evolve, adjust the solution continually
• Repeating the Six Steps
![](https://s3.amazonaws.com/brainscape-prod/system/cm/281/952/104/a_image_thumb.png?1562347248)
STEP 1:
Techniques:
• Brainstorming
• Interviewing
• Questionnaires
![](https://s3.amazonaws.com/brainscape-prod/system/cm/281/952/141/a_image_thumb.png?1562347340)
STEP 2:
Techniques:
• Fishbone Diagrams
• Pareto Analysis
• Affinity Diagrams
![](https://s3.amazonaws.com/brainscape-prod/system/cm/281/952/167/a_image_thumb.png?1562347407)
STEP 3:
Creating as many solutions to the problem (anything goes, no constraints)
• Looking at how each solution relates to the root causes and symptoms of the problem
• Deciding if different solutions can be merged (problem may be better solved)
• Eliminate options that will proves less effective at dealing with both the symptoms and the root
causes
![](https://s3.amazonaws.com/brainscape-prod/system/cm/281/952/183/a_image_thumb.png?1562347441)
STEP 4:
• Which solution is most feasible?
• Which solution is favored by
implementers and users?
Feasible Solution…
o …can be implemented within
acceptable timeframe
o …is cost effective, reliable and realistic
o …makes resource usage more effective
o …adaptable to conditions as they
evolve and change
o …has manageable risks
o …benefits the organization
![](https://s3.amazonaws.com/brainscape-prod/system/cm/281/952/200/a_image_thumb.png?1562347501)
STEP 5:
Project planning begins:
• Project manager, milestones, project start, additional support, actions to implement the solution
etc.
![](https://s3.amazonaws.com/brainscape-prod/system/cm/281/952/228/a_image_thumb.png?1562347536)
STEP 6:
Monitoring / Controlling of Project:
• Milestones, costs, work completion
• Step relies on:
• Collection of data, accurate/defined reporting mechanisms etc.
![](https://s3.amazonaws.com/brainscape-prod/system/cm/281/952/233/a_image_thumb.png?1562347578)
Software Development
Main definition and approaches / Practices / Methodologies
Software Development
• is the process of dividing software development work into distinct phases to improve design,
product management, and project management.
• the methodology may include the pre-definition of specific deliverables and artifacts that are
created and completed by a project team to develop or maintain an application
Practices:
- Continuous integration
- Prototyping
- Incremental Development
- Rapid application development
Methodologies:
- Waterfall development
- Spiral Development
- Agile development
Waterfall Development
is a relatively linear sequential design approach for certain areas of engineering design
• in software development, it tends to be among the less iterative and flexible approaches, as progress flows
in largely one direction (“downwards” like a waterfall) through the phases of conception, initiation, analysis,
design, construction, testing, deployment and maintenance
• this model is originated in the manufacturing and construction industries; where the highly structured
physical environments meant that design changes became prohibitively expensive much sooner in the
development process
![](https://s3.amazonaws.com/brainscape-prod/system/cm/281/952/264/a_image_thumb.png?1562347669)
Agile Software Development
describes an approach to software
development under which requirements
and solutions evolve through the
collaborative effort of self-organizing and
cross-functional teams and their
customer(s)/end user(s)
• it advocates adaptive planning, evolutionary
development, early delivery, and
continual improvement, and it encourages
rapid and flexible response to change
• there is significant anecdotal evidence that
adopting agile practices and values
improves the agility of software professionals,
teams and organizations
![](https://s3.amazonaws.com/brainscape-prod/system/cm/281/952/276/a_image_thumb.png?1562347726)
Maturity Models – Process Improvement
Processes needs to be: planned,
standardized, controlled
Reference Model: universal model from
which specific models can be derived
Aims of an process reference model:
• Primary – Improvement of an
organization’s work
• Secondary – verification of actual
maturity
Companies which use reference models:
- Aviation industry
- Automotive industry
- Software development
- Banking
![](https://s3.amazonaws.com/brainscape-prod/system/cm/281/952/282/a_image_thumb.png?1562347770)