The learning objective is to give you some exposure to real-world software
process definitions and reflect upon how they correspond to the processes in
the Vee model.
Use the slide format for your handin you've already seen, including putting
your name and Andrew ID on each slide. All homeworks and group assignments for
the course use that format unless explicitly stated otherwise. If you don't use
that format, expect to have to re-do the hand-in.
Note: hand all assignments in on Canvas. Use file name:
HW03_FAMILYNAME_FirstName_AndrewID.ppt for hand in. Also acceptable:
pptx and .pdf file extensions depending upon file type. Please do NOT zip, tar
or otherwise encapsulate the file unless the homework specifically asks for
that. Use the same file naming system (with different HW numbers) for other
homework hand-ins. These hand-in rules apply to ALL homeworks this semester
(single slide file for each homework) even if we don't repeat this requirement
explicitly.
For this homework you should have one slide per question (one slide for 3-1,
a second slide for 3-2, both in one file).
3-1:Pick your favorite Agile software methodology. (If you don't have
a favorite, pick one at random from this list: XP, Scrum, AUP/RUP, RAD,
Iconix). If you need some brush-up on this topic the Wikipedia entry is not a
bad starting point:
https://en.wikipedia.org/wiki/Agile_software_development.
Your answer must be all on one slide as follows:
- 3-1a. State the name of the Agile technique you picked. Do not use the Vee
model.
- 3-1b. Show an existing picture of the Agile process from a
source with a citation. Do NOT just use a figure from the course lecture --
find a real reference.
- 3-1c. Annotate that existing picture with labels for the
following process components in a contrasting font color (either the document
or the activity that produces the document, depending upon how the figure has
been drawn):
- Product Requirements
- Software Requirements
- High Level Design
- Detailed Design
- Implementation
- Unit Test results
- Integration Test results
- Software Test results
- Acceptance Test results
- Peer Review results
3-2: For the same Agile software methodology you identified in the
previous question, draw a software process chart using the
conventions that the lecture used to describe the Vee model. In other words,
draw a picture for that agile methodology using boxes and arrows, even if the
reference drawing didn't do that. This means that:
- Each box is an activity (e.g., "create user stories")
- Each arrow has a label indicating the written document or other work
product produced (e.g., "high level design").
- You must include all ten items from the previous question (product
requirements ... peer review results).
- You can modify an existing picture or draw your own picture so long as it
is clearly legible and follows the same boxes and arrows convention we used
when drawing the "V" model in lecture.
- Your answer must be all on one slide as a single picture with annotations.
Depending upon the picture you used for the previous question this might end up
being similar, but it might not be. How different it is depends upon which
Agile technique you picked and what its starting picture looked like. If they
are similar, then just consider these easy points.
Rubric: (check-off assignment)
- First slide (3-1)
- Existing picture of Agile process
- Citation of picture source
- Annotated with all elements of 3-1c. If you can't find it, put it in an
approximate place or put it to one side with "(missing)" annotation
- Second slide (3-2)
- Software process chart drawing corresponding to process in first slide
- All elements of 3-1c included
Supplemental Material: