5 elements of any process (elements of a generic process model)
- activities/methods
- artifacts
- roles
- tools
- milestones
In general what is activity orientation
A step-by-step set of activities detailing how to perform each task within a given process
5 advantages of the activity-orientation principle
- gives a detailed description of the work process
- defines the order of tasks in time
- detailed instructions for action
- reference to all affected artifacts
- good integration of “active” methods
DAD Gives a detailed description of Active methods
5 disadvantages of the activity-orientation principle
- restrictive (provides only one way of doing things)
- requires extensive planning
- quality of the results are hard to assess
- can lead to under specification of artifacts
- efficiency is dependent on the quality and extent of activity descriptions
Restricting Quality Can lead to Extensive Efficiency
In general, what is the artifact-orientation principle
a detailed specification of the resulting artifacts for each task in a process and who is responsible for the result.
The completion of each task is only dependent on the creation of a given artifact according to the specification
6 advantages of the artifact-orientation principle
- provides a detailed description of the quality requirements for results
- doesn’t specify any one method while yielding consistent results
- quality able to be easily assessed due to the given description and dependencies
- good for scalability in terms of results extent
- provides clear responsibilities
- allows for use of consistent terminology across all projects
A detailed description of Clear responsibilities Allows for Scalability, Quality, and Consistent results
3 disadvantages of the artifact-orientation principle
- high learning curve
- selection and tailoring of adequate methods
- deduction of plans is costly
What is solution-orientation?
when the customer proposes a solution to a problem they are having and the developer then starts to implement that solution
3 dangers of solution-orientation principle
- the achieved solution may be sub-optimal
- mismatch between the solution and problem (proposed solution does not solve the correct problem)
- proposed solution is a work-around rather than a solution
what is problem-orientation
customer proposes a problem and the developers thoroughly explore the problem space in order to fully understand the problem
8 steps to thoroughly explore the problem space
1) collect domain knowledge
2) identify stakeholders
3) document goals and constraints
4) analyze the current situation (strengths, weaknesses)
5) analyze the user-visible functionality
6) define the functionality and quality
7) iteratively transform into a system specification
