Status report

[Kirk-Amoah]

This is the second week of iteration. We conducted 5 more interviews this week. As a group we have a total of 13 interviews which consists of lecturers, students and faculty interns. We have had a total of 80 insights to help build our system.These interviews and insights have been put in a factoid spreadsheet. An affinity diagram has been generated from the spreadsheet and with the diagram, the stickys has been grouped according to user desired functionalities. We created a cultural diagram which consists of stakeholders we identified and how they influence the system. A flow diagram has been created. The flow diagram shows all tasks the stakeholder have and how they communicate with each other. A sequence diagram for the various stakeholders was developed and it shows all the automated process each stakeholder goes through.We also acquired physical artefacts in the form of current forms been used currently.We have made changes to our technical spike by taking away the node.js and including PHP Rest services. We also have developed a paper prototype which was done form interviews gathered so far. This shows how our system would be like. We have listed 6 issues so far for implementation and finally a technical spike has been done. The technical spike indicates what technical details we would use and prospective challenges we would face. This week has been a fruitful week.

[0xfauzi]

Client Project Week 2 Grade

Team: Score: 80.5/90

Grader: Fauzi

Overall

Breakdown

Score	Possible	Description	Comments
8	10	Presentation on Tuesday
10	10	Factoid spreadsheet with 10 total interviews (Thursday)
10	10	Paper prototypes
14	15	Main CD Models consolidated from interviews: Cultural/Context model (3), Flow (4), Sequence(4), Physical(2), and Artifact(2). Flow and sequence should have at a minimum 3 constituencies. 3-4 sequences related to your scenario should be identified. Models can be done on paper and turned in via a high-resolution picture OR be built online using a drawing tool. Physical and Artifact are lower priorities and worth a smaller number of points. (Thursday)
9	10	Affinity Diagram from factoid spreadsheet. On paper or in sticky sorter (Thursday) 30 or more facts grouped appropriately
5	5	Email report (cc’ing faculty team member) to client about who you have interviewed, and what you’ve learned. Attach your Tuesday presentation and cc your faculty member (Thursday)
5	5	Any Revisions to the architectural diagram in the wiki. (Thursday)
7.5	10	Define and implement a technical spike in your target tool set (Thursday)	Technical spike was defined but not implemented
7	10	Initial Story Backlog in Github (Thursday)
5	5	Pull Request with status report (may not have much code yet, Thursday)