| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Hacettepe University | |||||||||||||||||||||||||
2 | BBM 382-Software Engineering | |||||||||||||||||||||||||
3 | BBM 384-Software Engineering Lab | |||||||||||||||||||||||||
4 | Spring 2024-25 | |||||||||||||||||||||||||
5 | ||||||||||||||||||||||||||
6 | ||||||||||||||||||||||||||
7 | Course page on Piazza: | |||||||||||||||||||||||||
8 | https://piazza.com/hacettepe.edu.tr/spring2025/bbm382384/home | |||||||||||||||||||||||||
9 | ||||||||||||||||||||||||||
10 | BBM 382-Software Engineering | BBM 384-Software Engineering Lab | ||||||||||||||||||||||||
11 | Instructors: | TAs (teaching assistants): | ||||||||||||||||||||||||
12 | Office Hours | Office Hours | ||||||||||||||||||||||||
13 | Assoc. Prof. Dr. Ayça Kolukısa | atarhan@cs.hacettepe.edu.tr | By appointment | M. Aslı Taşgetiren | aslitasgetiren@cs.hacettepe.edu.tr | By appointment | ||||||||||||||||||||
14 | Assoc. Prof. Dr. Ebru Gökalp | ebrugokalp@cs.hacettepe.edu.tr | By appointment | Sevginur İnce | sevginurince@cs.hacettepe.edu.tr | By appointment | ||||||||||||||||||||
15 | Asst. Prof. Tuğba Erdoğan | tugba@cs.hacettepe.edu.tr | By appointment | Zehra Sena Noğay | zehranogay@cs.hacettepe.edu.tr | |||||||||||||||||||||
16 | ||||||||||||||||||||||||||
17 | ||||||||||||||||||||||||||
18 | Slides | https://piazza.com/hacettepe.edu.tr/spring2025/bbm382384/resources | Slides and materials | https://piazza.com/hacettepe.edu.tr/spring2025/bbm382384/resources | ||||||||||||||||||||||
19 | Development Process to be followed | BBM384 Software Development Lifecycle | ||||||||||||||||||||||||
20 | Reading Assignments | https://piazza.com/hacettepe.edu.tr/spring2025/bbm382384/resources | UML tool | www.visual-paradigm.com/download/community.jsp | ||||||||||||||||||||||
21 | ||||||||||||||||||||||||||
22 | Textbooks | Software Engineering | Components | Assignments (deliverables) | 100.00% | |||||||||||||||||||||
23 | Ian Sommerville, Addison-Wesley; 10th ed, 2015 | |||||||||||||||||||||||||
24 | 100.00% | |||||||||||||||||||||||||
25 | Book PDFs | https://drive.google.com/drive/folders/1kn65UTZl4b_OQrx1AADVIKxJWWyvoyNG?usp=sharing | ||||||||||||||||||||||||
26 | https://www.nobelyayin.com/detay.asp?u=14776 | (Turkish, translated from 10th Ed) | Groupings: | List of groups: | ||||||||||||||||||||||
27 | https://leanpub.com/visualising-software-architecture/read | The Art of Visualising Software Architecture: | Students should form groups of 5 people and let us know it via the link below until March 2, Sunday | |||||||||||||||||||||||
28 | https://docs.google.com/spreadsheets/d/1LE5MVg5Dk8Yi_F0f8CV4PvV7_DeJ8xd8/edit?usp=sharing&ouid=111194363704975968097&rtpof=true&sd=true | |||||||||||||||||||||||||
29 | ||||||||||||||||||||||||||
30 | Components | Final Exam | 40.00% | Software system to be developed in the lab: | TO BE ANNOUNCED | |||||||||||||||||||||
31 | Midterm-1 | 30.00% | Requirements of the system: | Explained in the experiment sheet | ||||||||||||||||||||||
32 | Midterm-2 | 25.00% | GUI building in Eclipse using WindowBuilder | https://eclipse.org/windowbuilder/ | ||||||||||||||||||||||
33 | Attendance | 5.00% | ||||||||||||||||||||||||
34 | ||||||||||||||||||||||||||
35 | Total | 100.00% | Gitlab | Students should use Gitlab to host and track their source code and the document deliverables | ||||||||||||||||||||||
36 | Software system to be discussed in lecture: | Flight ticketing system | www.gitlab.com | |||||||||||||||||||||||
37 | https://docs.google.com/presentation/d/11aOE24Gj0yUGXDsB8nKc5RFZpiufC9G95C0j4pfYiG4/edit?usp=drive_link | |||||||||||||||||||||||||
38 | ||||||||||||||||||||||||||
39 | ||||||||||||||||||||||||||
40 | BBM382 | Reading Asignments | BBM384 | Deliverables Due Date (see below) | ||||||||||||||||||||||
41 | Week # | Date | Content | Book Ch's | Due dates | Week # | Date | Content | Ch's | Other References | Return | |||||||||||||||
42 | 1 | February 20, 2025 | Introduction, Waterfall SD | 1, 2, 22, 23 | 1 | February 21, 2025 | Introduction | 1.2 | SDLC & Dev.Schedule , Gitlab | |||||||||||||||||
43 | 2 | February 27, 2025 | Prj. Mgt & Planning & Risk Mgt. | 2 | February 28, 2025 | UML & Tool Intro & Context D.+ Gantt, System Description | 2.3 | Sw.Vision & Prj.Plan Temp. Sw.Vision & Prj.Plan Examples | ||||||||||||||||||
44 | 3 | March 6, 2025 | Software Requirements and UML | 4 | RA-1 | 3 | March 7, 2025 | Live question-answer session | 4 | GitLab | ||||||||||||||||
45 | 4 | March 13, 2025 | Exercise in class-System: BILSIS | 4 | 4 | March 14, 2025 | UML Modeling (Use Case, Activity D.) | 4 | SRS Template(UCD, GUI, Data model), Sys.Test Case Temp | DEL #1 : Deadline: March 14, 2025, 23:00 | ||||||||||||||||
46 | 5 | March 20, 2025 | System Modeling | 5,6 | 5 | March 21, 2025 | Live question-answer session | 5.6 | SRS Example, Sys.Test Case Example | |||||||||||||||||
47 | 6 | March 27, 2025 | Architectural Design | 6 | RA-2 | 6 | March 28, 2025 | UML Modeling (Package, Component, Deployment D.) Example Arch. & HL Design Modeling with UML | 6,7 | Arch.Notebook Temp. | DEL #2 : Deadline: March 29, 2025, 23:00 | |||||||||||||||
48 | 7 | April 3, 2025 | No Lecture- Ramazan Eid | 7 | April 4, 2025 | Online Lecture | Arch.Notebook Temp. example | |||||||||||||||||||
49 | 8 | April 10, 2025 | Design & Implementation | 7 | 8 | April 11, 2025 | Demo presentations | DEL #3: Architecturel Notebook, Demo 1 + due date: April 11, 2025 09:30 | ||||||||||||||||||
50 | 9 | April 17, 2025 | MIDTERM | 9 | April 18, 2025 | No Lecture | ||||||||||||||||||||
51 | 10 | April 24, 2025 | Software Testing | 8 | RA-3 | 10 | April 25, 2025 | UML Modeling (Statechart, Class, Sequence D.), Example Design & Impl. Modeling with UML | 8 | Coding Std & Sys.Test Report Temp | ||||||||||||||||
52 | 11 | May 1, 2025 | No Lecture- International Workers' Day | 11 | May 2, 2025 | Demo presentations | DEL #4 [Demo 2]: Deadline: May 2, 2025, 23:00 | |||||||||||||||||||
53 | 12 | May 8, 2025 | Software Evolution and Maintenance | 9 | 12 | May 9, 2025 | No Lecture | 9 | ||||||||||||||||||
54 | 13 | May 15, 2025 | Change/Configuration Management | 25 | 13 | May 16, 2025 | Final Demo Q&A | |||||||||||||||||||
55 | 14 | May 22, 2025 | Quality Management | 24 | RA-4 | 14 | May 23, 2025 | Project presentations | Final Project: DEL #5: Deadline: May 23,2025, 23:00 | |||||||||||||||||
56 | ||||||||||||||||||||||||||
57 | Reading Assignments (RA): | Project deliveries: | Documentation: | Software / code: | Mark % | Total milestone mark | ||||||||||||||||||||
58 | RA-1 | Thayer, "Software System Engineering—A Tutorial", IEEE Computer, 2002. | DEL #1 | Software Vision | 4% | 10% | ||||||||||||||||||||
59 | RA-2 | Alexander, "Misuse Cases—Use Cases with Hostile Intent", IEEE Software, 2003. | Project Plan | 6% | ||||||||||||||||||||||
60 | RA-3 | Kruchten, "Architectural Blueprints—The “4+ 1” View Model of Software Architecture", IEEE Software, 1995. | DEL #2 | Software Requirements Document | 12% | 15% | ||||||||||||||||||||
61 | RA-4 | Whittaker, "What Is Software Testing_And Why Is It So Hard", IEEE Software, 2000. | List of System Test Case Definitions | 3% | ||||||||||||||||||||||
62 | DEL #3 | Architectural Notebook | 5% | 20% | ||||||||||||||||||||||
63 | READING ASSIGNMENTS | Prototype 1: demo of 3 critical use cases | 10% | |||||||||||||||||||||||
64 | Risks management report (see tab "Writing risk mng report") | 2% | ||||||||||||||||||||||||
65 | What to do: | GitLab & Configuration/change management report (see tab "Writing change mng report") | 3% | |||||||||||||||||||||||
66 | Read & summarize each paper in titles of it, and IN YOUR OWN WORDS. | DEL #4 | Prototype 2: half of the remaining system | 10% | 21% | |||||||||||||||||||||
67 | Submit your summary via the gform | Software Test RESULT Report + test cases (for all running test cases) | 4% | |||||||||||||||||||||||
68 | Coding Standard | 2% | ||||||||||||||||||||||||
69 | IMPORTANT: | Design Diagram Document (Updated Class diagram, Updated ER diagram, sequence diagrams for all use-cases, state diagram for a class) | 5% | |||||||||||||||||||||||
70 | DEL #5 | Gitlab Configuration Data | 5% | 34% | ||||||||||||||||||||||
71 | Do NOT COPY/PASTE the material from the papers into your assignment! | Presentation (EACH STUDENT should say what s/he has done) | 5% | |||||||||||||||||||||||
72 | Release: Final demo of software product (all use cases) | 24% | ||||||||||||||||||||||||
73 | UML assignment: | 100% | 100% | |||||||||||||||||||||||
74 | For XXX application, draw: -Context diagram -Use case diagram -Activity diagram for three use cases -Class diagram -Sequence diagram for three use cases -Statemachine diagram for two class objects -Package diagram for your software architecture | |||||||||||||||||||||||||
75 | 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 instructors). One report by each student. | |||||||||||||||||||||||||
76 | As the UML tool, you should use the Visual Paradigm tool | |||||||||||||||||||||||||
77 | http://www.visual-paradigm.com/download/community.jsp | |||||||||||||||||||||||||
78 | ||||||||||||||||||||||||||
79 | ||||||||||||||||||||||||||
80 | ||||||||||||||||||||||||||
81 | ||||||||||||||||||||||||||
82 | ||||||||||||||||||||||||||
83 | ||||||||||||||||||||||||||
84 | ||||||||||||||||||||||||||
85 | ||||||||||||||||||||||||||
86 | ||||||||||||||||||||||||||
87 | ||||||||||||||||||||||||||
88 | ||||||||||||||||||||||||||
89 | ||||||||||||||||||||||||||
90 | ||||||||||||||||||||||||||
91 | ||||||||||||||||||||||||||
92 | ||||||||||||||||||||||||||
93 | ||||||||||||||||||||||||||
94 | ||||||||||||||||||||||||||
95 | ||||||||||||||||||||||||||
96 | ||||||||||||||||||||||||||
97 | ||||||||||||||||||||||||||
98 | ||||||||||||||||||||||||||
99 | ||||||||||||||||||||||||||
100 | ||||||||||||||||||||||||||