| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Hacettepe University | |||||||||||||||||
2 | BBM 382-Software Engineering | |||||||||||||||||
3 | BBM 487-Software Engineering Lab | |||||||||||||||||
4 | Spring 2017 | |||||||||||||||||
5 | ||||||||||||||||||
6 | Instructors: | |||||||||||||||||
7 | Dr. Ayça Tarhan | atarhan@hacettepe.edu.tr | http://web.cs.hacettepe.edu.tr/~atarhan/ | |||||||||||||||
8 | Dr. Vahid Garousi | vahid.garousi@hacettepe.edu.tr | http://web.cs.hacettepe.edu.tr/~vahid/ | |||||||||||||||
9 | ||||||||||||||||||
10 | Course page on Piazza: | BBM 487-Software Engineering Lab | ||||||||||||||||
11 | www.piazza.com/hacettepe.edu.tr/spring2017/bbm382bbm487 | TAs (teaching assistants): | ||||||||||||||||
12 | Nebi Yilmaz | yilmaz@cs.hacettepe.edu.tr | ||||||||||||||||
13 | Slides | https://drive.google.com/folderview?id=0B6dKdxaNjBENM2IybFhRVmtPZXc&usp=sharing#list | Feyza Nur Çubukçuoğlu | feyzanur@cs.hacettepe.edu.tr | ||||||||||||||
14 | Reading Assignments (RA) | https://drive.google.com/folderview?id=0B6dKdxaNjBENTkZ5Vm4wMkFlcG8&usp=sharing#list | Gültekin Işık | gultekin@cs.hacettepe.edu.tr | ||||||||||||||
15 | Sample EXAMS from last years: | https://drive.google.com/folderview?id=0B6dKdxaNjBENN1hiSVNEU3dnUTg&usp=sharing | ||||||||||||||||
16 | ||||||||||||||||||
17 | Textbooks | Software Engineering | Slides and materials | https://drive.google.com/open?id=0B6dKdxaNjBENaWJlOFBjZ3Ffb3M | ||||||||||||||
18 | Ian Sommerville, Addison-Wesley; 9 edition, 2010 | UML tool | http://www.visual-paradigm.com/download/community.jsp | |||||||||||||||
19 | Full-text PDF: | |||||||||||||||||
20 | https://drive.google.com/open?id=0B6dKdxaNjBENQVEtOU5hNTNPSUU | Components | Assignments (deliverables) | 80% | ||||||||||||||
21 | Attendance | 10% | ||||||||||||||||
22 | Object-Oriented Analysis and Design with Applications-3rd Edition | UML for Java Programmers | Filling team cohesion forms on time | 10% | ||||||||||||||
23 | PDF: | PDF: | 100% | |||||||||||||||
24 | https://drive.google.com/file/d/0B6dKdxaNjBENREZ0b3RWSGRuWDQ/view?usp=sharing | https://drive.google.com/file/d/0B6dKdxaNjBENRjRqUDZUby1xMFE/view?usp=sharing | Groupings: | List of groups: | ||||||||||||||
25 | The Art of Visualising Software Architecture | https://drive.google.com/open?id=0BxGF2OCLGB9mQmpUUElhZFB5S2s | ||||||||||||||||
26 | https://leanpub.com/visualising-software-architecture/read | By Friday Feb. 17, students shall fill out the online personality test in this website: | ||||||||||||||||
27 | http://www.16personalities.com/free-personality-test | |||||||||||||||||
28 | Components | Midterm Exam | 25% | |||||||||||||||
29 | Final Exam | 40% | Software system to be developed in the lab: | Library book loan system | GitHub | Students should use GitHub to host and track their source code and the document deliverables | ||||||||||||
30 | UML assignment | 5% | Requirements of the system: See slide #5 "Library Book Loan System –Requirements" in: | https://drive.google.com/file/d/0B7TOHOTJD96ySWI4ZXlPRnVWb1k/view?usp=sharing | www.github.com | |||||||||||||
31 | Reading Assignments (RA) | 20% | Install "GitHub for Eclipse" | |||||||||||||||
32 | Attendance | 10% | GUI building in Eclipse using WindowBuilder | https://eclipse.org/windowbuilder/ | https://eclipse.github.io/ | |||||||||||||
33 | Total | 100% | Naming convention for projects: bbm487s2017g#, where # is your group number, such as: bbm487s2017g2 | |||||||||||||||
34 | Not following the naming convention and other advices given by the instructors will lead to reduction of your marks | |||||||||||||||||
35 | Software system to be discussed in lecture: | Flight ticketing system | A good client for GitHub: https://www.sourcetreeapp.com | |||||||||||||||
36 | ||||||||||||||||||
37 | BBM382 | Reading Asgn. (see below) | BBM487 | Deliverables (see below) | ||||||||||||||
38 | Week # | Date | Content | Ch's | Due dates | Teaching by: | Slides updated by: | Date | Content | Ch's | Other References | Return | Report team cohesion (in EACH DELIVERY): | |||||
39 | 1 | February 14, 2017 | Introduction, Waterfall SD | 1, 2, 22, 23 | Both | AT | February 14, 2017 | OpenUP / Lab. SDLC, Assets Introduction & Personality Test | 1.2 | SDLC & Dev.Schedule | ||||||||
40 | 2 | February 21, 2017 | Prj. Mgt, Prj. Planning & Risk Mgt. | Both | AT | February 21, 2017 | UML & Tool Intro. | 2.3 | Sw.Vision & Prj.Plan Temp.s | |||||||||
41 | 3 | February 28, 2017 | Software Requirements and UML | 4 | RA-1 | Both | AT | February 28, 2017 | UML Modeling (Context, Use Case, Activity D.) | 4 | SRS Template | |||||||
42 | 4 | March 7, 2017 | Exercise in class-System: BILSIS | 4 | Both | VG | March 7, 2017 | Example Requirements Modeling with UML | 4 | GUI & Data Model Temp. | DEL #1 (on March 11) | http://goo.gl/forms/PIIXEPZJ2W | ||||||
43 | 5 | March 14, 2017 | System Modeling | 5,6 | RA-2 | VG in seminer odasi | VG | March 14, 2017 | UML Modeling (Package, Component, Deployment D.) | 5.6 | Sys.Test Case Temp. | http://goo.gl/forms/PIIXEPZJ2W | ||||||
44 | 6 | March 21, 2017 | Architectural Design | 6 | AT in seminer odasi | VG | March 21, 2017 | Exam prep and Reviews | DEL #2 | |||||||||
45 | 7 | March 28, 2017 | Design & Imp. (UML modeling) / UML assignment (see below) | 7 | RA-3 | AT in seminer odasi | VG | March 28, 2017 | Example Arch. & HL Design Modeling with UML | 6.7 | Arch.Notebook Temp. | |||||||
46 | 8 | April 4, 2017 | MIDTERM | - | - | April 4, 2017 | UML Modeling (Statechart, Class, Sequence D.) - 1 | 7 | Example Coding Std. | DEL #3 | http://goo.gl/forms/PIIXEPZJ2W | |||||||
47 | 9 | April 11, 2017 | Software Testing 1 | 8 | VG in seminer odasi | VG | April 11, 2017 | UML Modeling (Statechart, Class, Sequence D.) - 2 | 8 | SDD Template | demo | |||||||
48 | 10 | April 18, 2017 | Software Testing 2 | 9 | RA-4 | VG in seminer odasi | VG | April 18, 2017 | Example Design & Impl. Modeling with UML | 9 | Sys.Test Report Temp. | |||||||
49 | 11 | April 25, 2017 | Software Evolution and Maintenance | 9 | VG in seminer odasi | VG | April 25, 2017 | Exam prep and Reviews | DEL #4, demo | http://goo.gl/forms/PIIXEPZJ2W | ||||||||
50 | 12 | May 2, 2017 | Change/Configuration Management | 24 | RA-5 | AT in seminer odasi | AT | May 2, 2017 | Project presentations | |||||||||
51 | 13 | May 9, 2017 | Quality Management | 3 | AT in seminer odasi | AT | May 9, 2017 | Project presentations | ||||||||||
52 | 14 | May 16, 2017 | Software Process (Others) | 3 | RA-6 | AT in seminer odasi | AT | May 16, 2017 | Project presentations | DEL #5 | http://goo.gl/forms/PIIXEPZJ2W | |||||||
53 | ||||||||||||||||||
54 | Reading Assignments (RA): submit them during the lab sessions | |||||||||||||||||
55 | RA-1 | Thayer, "Software Syst. Eng.", IEEE Computer, 2002. | ||||||||||||||||
56 | RA-2 | Go & Carrol, "The Blind Men and The Elephant", Interactions, 2004. | OpenUP / Exampler Site / All templates will be used from this site / Basic Roles will be used | |||||||||||||||
57 | RA-3 | Lang et al., "UML Software Architecture and Design Description", IEEE Software, 2006. | http://epf.eclipse.org/wikis/openup/ | |||||||||||||||
58 | RA-4 | Louridas, "Test Management", IEEE Software, 2011. | ||||||||||||||||
59 | RA-5 | Jones, "Software Project Management Practices", Crosstalk, 2004. | Project deliveries: | Documentation: | Software / code: | Mark % | Total milestone mark | |||||||||||
60 | RA-6 | Frequently Forgotten Fundamental Facts about Software Engineering | DEL #1 | Software Vision | 4% | 10% | ||||||||||||
61 | Project Plan | 6% | ||||||||||||||||
62 | Get the PDFs from: | DEL #2 | Software Requirements Document | 15% | 15% | |||||||||||||
63 | https://drive.google.com/folderview?id=0B6dKdxaNjBENTkZ5Vm4wMkFlcG8&usp=sharing#list | DEL #3 | Architectural Notebook | 5% | 20% | |||||||||||||
64 | What to do: | List of System Test Case Definitions | 3% | |||||||||||||||
65 | Read & summarize each paper in max 2 A4 pages, IN YOUR OWN WORDS. | Prototype 1: demo of a single use case | 5% | |||||||||||||||
66 | Submit your summary via the "Submit " system | Risks management report (see tab "Writing risk mng report") | 3% | |||||||||||||||
67 | https://submit.cs.hacettepe.edu.tr/ | Configuration/change management report (see tab "Writing change mng report") | 4% | |||||||||||||||
68 | IMPORTANT: | DEL #4 | Software Design document (UML models) | 10% | 20% | |||||||||||||
69 | Do NOT COPY/PASTE the material from the papers into your assignment! | Coding Standard | 2% | |||||||||||||||
70 | Prototype 2: demo at least 6 use cases (half of system) | 8% | ||||||||||||||||
71 | UML assignment: | DEL #5 | Software Test RESULT Report | 5% | 35% | |||||||||||||
72 | For the WhatsApp application, draw: -Context diagram -Use case diagram -Activity diagram for four use cases -Class diagram -Sequence diagram for four use cases | Risks management report (see tab "Writing risk mng report") | 5% | |||||||||||||||
73 | Put all your models (UML diagrams) in a single Word / PDF file and submit the SINGLE file by the deadline in the SUBMIT system (if you have issues, contact the TAs). One report by each student. | Configuration/change management report (see tab "Writing change mng report") | 5% | |||||||||||||||
74 | As the UML tool, you should use the Visual Paradigm tool | Presentation (EACH STUDENT should say what s/he has done) | 5% | |||||||||||||||
75 | http://www.visual-paradigm.com/download/community.jsp | Release: Final demo of software product (all use cases) | 15% | |||||||||||||||
76 | 100% | 100% | ||||||||||||||||
77 | ||||||||||||||||||
78 | ||||||||||||||||||
79 | ||||||||||||||||||