System Modelling. Lecture

Transcription

1 System Modelling Lecture

2 Lecture Objectives GUI design with Story-Driven Modelling Class Diagram to Code (revistited) Automatic Code Generation Intro to project Mancala game: 35pts

3 Wireframes or Mockups 3/31

4 Wireframes or Mockups Often created manually on paper For customer it is difficult to differentiate GUI elements of editor from the designed application Often GUI is refined together with customer who is often missing design app. skills Designers vs Developers Usability vs code complexity 4/31

5 1. Karli, Bobby, and Olga agree to have a pot luck barbeque, but want to share the cost evenly. On the day of the barbeque, Karli brings his notebook running the Group Register application. He assumes that Bobby and Olga will bring enough for them all, so he does not bring any food items. After starting the application it shows the initial screen of the application with no entries. This step mentions that we have an application with an initial screen

6 2. Karli adds himself, Bobby, and Olga to the list of participants This step mentions a list of participants. Therefore we need a list showing the names of the participants. But how we will actually get the participants into the list? 6/31

7 A B C

8 a) Just editing the table *This requires complex handling of a single dummy line in the end of the table and might pose some diculties in programming b) Having some fields and an add button underneath to enter one person at a time c) An add button on top which creates an empty line, which is editable * Combined idea from a) and b) but still needs more programming than b) Lets say that customer agreed decision b) 8/31

9 3. Bobby shows up and brings some beer for 12 EUR. Karli enters that Bobby brought beer for 12 EUR into the system. Olga brings bread for 4.50 EUR and salad for 3.00 EUR. Karli enters the items for Bobby and Karli to the system. From this step, we can derive that we need something to store bought items, the person who bought it, and the price of each. This also suggests to use some kind of table with the columns person name, item description, and price. Also here, we could discuss different options to fill in the values like in the last step, but also here we will settle on the option of adding some entry fields and an add button. This could be done in a different window, but we will put it in the same to make all information visible at all 9/31

10 10/31

11 4. The food items sum up to EUR. Therefore, the share of each participants equals to 6.50 EUR. As Karli has not spent any money for food items, he has to pay the full share of 6.50 EUR. As Bobby has already spent 12 EUR, he has to receive back 5.50 EUR. Olga has spent 7.50, so she has to receive 1 EUR back. So far we have not taken into account that we want to also see the amounts of the balance each participant has to pay to the register. We could now either add a button to compute the balance and show a different window with the results or we could also show the balance all the time in the participant's list. Let us assume that our potential customer prefers the version seeing the balance all the time. We therefore add a column Amounts.

12 12/31

13 Refining the Storyboard Further playing with these wireframes might lead to some further requirements and ideas Will it be possible to remove items from the list? How exactly? Will it be possible to edit the names of the participants? Client might discover that he needs to be able to adjust the price of the food items /31

14 Revisited: Class Diagram to Code class class Student Student 14/31

15 Revisited: Class Diagram to Code class class Student Student private private String String name name ;; void void setname setname (String (String name) name) this.name this.name = = name; name; String String getname getname (()) return return name name ;; 15/31

16 Revisited: Class Diagram to Code class class Student Student private private String String name name ; ; void void setname setname (String (String name) name) if if (name (name == == null) null) throw throw new new IllegalArgumentException("Student.name IllegalArgumentException("Student.name must must not not be be null!"); null!"); this.name this.name = = name; name; /31

17 class class Student Student private private University University university; university; void void setuniversity setuniversity (University (University university) university) this.university this.university = = university; university; University University getuniversity() getuniversity() return return university; university; /31

18 import import java.util.hashset; java.util.hashset; class class Course Course private private HashSet<Student> HashSet<Student> students students = = new new HashSet<Student>( HashSet<Student>( ); ); void void addstudent addstudent (Student (Student student) student) students.add students.add (student) (student) ; ; void void removestudent removestudent (Student (Student student) student) students.remove students.remove (student) (student) ; ; HashSet<Student> HashSet<Student> getstudents getstudents ( ( ) ) return return students; students; 18/31

19 Courses Courses course course =....; ; course.getstudents course.getstudents (().clear ).clear( () ); ; course.getstudents course.getstudents (().add ).add(new EvilStudent EvilStudent (() )); ; // // now now all all student student references references are are gone gone // // possible possible parameter parameter check check of of addstudent addstudent ( ( ) ) is is skipped! skipped! 19/31

20 import import java.util.collections; java.util.collections; import import java.util.hashset; java.util.hashset; import import java.util.set; java.util.set; class class Course Course private private Set<Student> Set<Student> students students = = new new HashSet<Student> HashSet<Student> ( ( ); ); boolean boolean addstudent addstudent (Student (Student student) student) return return students.add students.add (student); (student); boolean boolean removestudent removestudent (Student (Student student) student) return return students.remove students.remove (student) (student) ; ; Set<Student> Set<Student> getstudents getstudents ( ( ) ) // don't expose the concrete container class // don't expose the concrete container class return return Collections.unmodifiableSet Collections.unmodifiableSet (students) (students) ; ; int int sizeofstudents sizeofstudents ( ( ) ) return return students.size students.size ( ( ); ); 20/31

21 class class LectureHall LectureHall private private Course Course course; course; void void setcourse setcourse (Course (Course course) course) if if (this.course (this.course!=!= course course ) ) Course Course oldvalue oldvalue = = this.course; this.course; this.course this.course = = course; course; if if (oldvalue (oldvalue!=!= null) null) oldvalue.setlecturehall(null); oldvalue.setlecturehall(null); if if (course (course!=!= null) null) course.setlecturehall(this); course.setlecturehall(this); /31

22 Same for the Course class class class Course Course private private LectureHall LectureHall lecturehall; lecturehall; void void setlecturehall setlecturehall (LectureHall (LectureHall lecturehall) lecturehall) if if (this.lecturehall (this.lecturehall!=!= lecturehall lecturehall ) ) LectureHall LectureHall oldvalue oldvalue = = this.lecturehall; this.lecturehall; this.lecturehall this.lecturehall = = lecturehall; lecturehall; if if (oldvalue (oldvalue!=!= null) null) oldvalue.setcourse(null); oldvalue.setcourse(null); if if (lecturehall (lecturehall!=!= null) null) course.setcourse(this); course.setcourse(this); /31

23 UML Lab Demo

24 Choosing the Right Container Class java.util.set java.util.hashset java.util.treeset 24/31

25 Choosing the Right Container Class java.util.set java.util.hashset java.util.treeset java.util.list java.util.arraylist java.util.linkedlist java.util.vector 25/31

26 Choosing the Right Container Class java.util.set java.util.hashset java.util.treeset java.util.list java.util.arraylist java.util.linkedlist java.util.vector java.util.map 26/31

27 SDM Method Discussion

28 Course Project Develop a multiplayer version of the game Mancala in this course as course project using Story-Driven Modelling method You can see an example implementation Wikipedia has a compact description 28/31

29 Taken from:

30 Project Documentation The project report you will have to hand in has to consist of: A guide through your project (and repository) Your project plan (scheduler, requirements, aims..) Project log (progress) User manual Storyboard(as detailed as possible and reasonable) Also simulate customer discussion, try to find 3-5 features you missed before Video of discussion will be considered as a bonus 30/31

31 Project Presentation The deadline for the assignment is (23:59) Separate session on course project presentations is on Talk about solved/not solved problems How you organized the work Some notes about the SDM method Application demo 31/31