You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,3 +42,14 @@ Our original class visitors are still around but where we were printing to the o
42
42
Adding the ability to do sequence digrams required us to make a new type of visitor for it. To be able to just refence and class method and depth also required us to make a recursive Method visitor. These extended our normal visitors. Our normal visitors would work for a sequence diagram like a whitelist while this new one would just grab everything that was called to the given depth.
43
43
44
44
We Pair programmed at the start but after 30+ hours working on it we split up one to work on the code while the other wrote test cases for that code. After the first deadline passed we both just worked on it as much as we could to figgure out the bugs with how method names where being inialized.
45
+
46
+
47
+
MileStone 4:
48
+
49
+
!! NEED IMAGE !!
50
+
51
+
We added the capability of checking for the Singleton class instance by adding an Interface that implements a check method and by adding a class that implements that method specifically for the Singleton case. This should allow easy adding for further class checks of this type.
52
+
53
+
Besides the addition of the above interface and class, no design changes from MileStone 3 had to be made.
54
+
55
+
We pair programmed for the beginning of MileStone 4 and discussed how we wanted to implement the check for the UML diagram. After deciding how we wanted to do it and we did a little pair programming, we split off for finishing MileStone 4 code and test cases.
0 commit comments