week1

# Introductions

DAEN 640 Capstone Senior Design

---

# Plan for today

.box-2.medium[Introductions]

.box-3.medium[Goals & Expectations]

.box-4.medium[Semester Overview]

.box-5.medium[Grading & Assessment]

.box-6.medium[Code of Conduct]

---

# Instructors

---

.pull-left-3.center[
.box-inv-2[Alexander Abuabara]
<figure class="zoom-figure">
<img src="images/Alexander.png" alt="Alexander" title="Alexander" width="100%">
</zoom-figure>
]

.pull-middle-3[
.box-inv-2[Jose Vazquez]
<figure class="zoom-figure">
<img src="images/Vazquez.png" alt="Jose" title="Jose" width="100%">
</zoom-figure>
]

.pull-right-3[
.box-inv-2[Jon Elizondo]
<figure class="zoom-figure">
<img src="images/Jon.png" alt="JP" title="JP" width="100%">
</zoom-figure>
]

---

layout: false
name: slides
class: center middle section-title section-title-3 animated fadeIn

# Goals and Expectations

---

---

# What is The Most Important Thing?

.box-inv-3.sp-after[*In life*, the most important thing is subjective]

.box-3.sp-after[
Health, Love & Relationships, Purpose & Meaning, 
Gratitude, Freedom, Learning & Growth, Self-Care
]

.box-inv-3.SMALL.sp-after[
These dimensions makes a conceptual backbone for our capstone, 
framing it not as a purely technical culmination experience, 
but as a 

professional & personal transition course

]

---

.box-3.sp-after-short[
The Bridge Between Academic Training & Life 
(After Graduation)
]

.box-inv-3.SMALL.sp-after-short[
Comprehensive technical expertise!
]

.box-3.sp-after-short[
Learn to go beyond working your team's project, 
develop the ability to work in any project!
]

.box-inv-3.SMALL.sp-after-short[
Success is fully achieved when combined with 

strong communication!

]

---

&nbsp;

.center[
<figure>
<img src="images/Yoda_communication.png" alt="Yoda" title="Yoda" width="50%">
</figure>
]

---

&nbsp;

.box-3.SMALL.sp-after[
Capstone Design represents the culmination of an educational journey
]

.box-inv-3.sp-after[
It's where **theory** meets **practice**, **abstraction** meets **reality**
]

.box-3.sp-after[
The individual student transitions from learning concepts 
to creating, evaluating, and owning a complete system
]

---

---

---

# Goals

.box-6.sp-after-veryshort[Apply data engineering knowledge]
--
.box-inv-6.sp-after-veryshort[Develop end-to-end project skills]
.box-6.SMALL.sp-after-veryshort[Plan, document, execute projects using a structured framework (V-Model)]
.box-inv-6.sp-after-veryshort[Foster collaboration & professional skills]
.box-6.SMALL.sp-after-veryshort[Build a portfolio demonstrating technical & teamwork skills]
.box-inv-6.sp-after-veryshort[Prepare for industry & research]
.box-6.sp-after-veryshort[Strengthen problem-solving & critical thinking]
.box-inv-6.sp-after-veryshort[Experience working under professional expectations]

---

#  Expectations

.box-6.sp-after-short[Active Participation]
--
.box-inv-6.sp-after-short[Ownership & Accountability]

.box-6.sp-after-short[Professional Communication]

.box-inv-6.sp-after-short[Quality & Documentation]
--
.box-6.sp-after-short[Ethical Conduct]

---

---

# ISEN Mission Statement

> 
 **To serve**
 
 
 the state, nation and global community by educating 
 industrial engineering students to be well founded in engineering 
 fundamentals and
 
 
 **to have the knowledge and skills**
 
 
 required 
 
 
 **to design, develop, improve, implement and control**
 
 
 sophisticated production and service
 
 
 **systems**
 
 
 in an environment characterized by
 
 
 **complex technical and social challenges**
 
 
 . Throughout this educational process, students will be instilled with the
 
 **highest standards of professional and ethical behavior**.

.center[
<figure>
<img src="images/TAMU-Industrial-and-Systems-Enginnering.png" alt="ISEN TAMU logo" title="ISEN TAMU" width="47%">
</figure>
]

---

# Semester Overview

---

---

---

# Discover: Understand the Problem

.box-inv-4.SMALL.sp-after-short[
Purpose: Explore and learn before building
]

* Investigate the problem domain
* Identify stakeholders and users
* Study existing solutions and technologies
* Gather data (surveys, literature, benchmarks)
* Uncover unmet needs and constraints

.box-inv-4.SMALL.sp-after-short[
Outcome: Clear understanding of what problem matters and why
]

---

# Define: Frame the Right Problem

.box-inv-4.SMALL.sp-after-short[
Purpose: Turn research into a focused project
]

* Synthesize findings into insights
* Write a precise problem statement
* Define scope, objectives, and constraints
* Establish functional and performance requirements
* Set success metrics and milestones

.box-inv-4.SMALL.sp-after-short[
Outcome: A well-scoped, testable project definition
]

---

# Develop: Design and Build

.box-inv-4.SMALL.sp-after-short[
Purpose: Create and validate the solution
]

* Generate and compare design concepts
* Select the optimal solution
* Create system architecture and models
* Build prototypes or minimum viable products
* Test, iterate, and refine based on data

.box-inv-4.SMALL.sp-after-short[
Outcome: A functional, validated engineering solution
]

---

# Deliver: Validate and Communicate

.box-inv-4.SMALL.sp-after-short[
Purpose: Prepare for real-world use and evaluation
]

* Perform final verification and validation
* Confirm performance meets requirements
* Finalize documentation, code, and design artifacts
* Prepare reports, posters, and presentations
* Demonstrate the solution to stakeholders

.box-inv-4.small.sp-after-short[
Outcome: A complete, defensible project ready for deployment and assessment
]

---

# Weekly Schedule

.small[
| Week | Date | Topic |
|------|------|-------|
| 1    | 1/13 | Introductions + Comm Requirements |
| 2    | 1/20 | Integrate Engineering Design (*The Toaster Project*) |
]

</div>

&nbsp;

.center[
<figure>
<img src="images/today.jpg" alt="Today calendar" title="Today!" width="17%">
</figure>
]

---

# Weekly Schedule

.small[
| Week | Date | Topic |
|:-----|:----:|-------|
| 3    | 1/27 | Phase 1 Kickoff |
| 4    | 2/3  | Phase 1 Presentations - Groups BH & COE |
| 5    | 2/10 | Phase 1 Presentations - Groups ML |
|      |      |       |
| 6    | 2/17 | Phase 2 Kickoff |
| 7    | 2/24 | Phase 2 Presentations - Groups BH & COE |
| 8    | 3/3  | Phase 2 Presentations - Groups ML |
]

</div>

---

.box-4.normal.sp-after-short[
March 7-15
]

.center[
<figure>
<img src="images/SpringBreak3.png" alt="Spring Break" title="Spring Break" width="60%">
</figure>
]

---

---

# Weekly Schedule

.small[
| Week | Date | Topic |
|:-----|:----:|-------|
| 9    | 3/17 | Phase 3 Kickoff |
| 10   | 3/24 | Phase 3 Presentations - Groups BH & COE |
| 11   | 3/31 | Phase 3 Presentations - Groups ML |
|      |      |   |
| 12   | 4/7  | Phase 4 Kickoff |
| 13   | 4/14 | Phase 4 Presentations - Groups BH & COE |
| 14   | 4/21 | Phase 4 Presentations - Groups ML |
]

</div>

---

# Attendance

* Mandatory attendance for everyone:

* First two weeks of class
  * Phase kick-offs

* Team presentation days:

* All team members must stay for the entire class!
  * Other students are welcome & encouraged to attend

---

# Again

.box-inv-4.sp-after-short[Phase Kickoff Weeks]

* Entire team must be present
* Details on phase
 * Content
 * Deliverables (checklist)
* Communications Activities
* Project guidance/tips

---

# And Again

.box-inv-4.sp-after-short[Presentation Weeks]

* On the day for your group, ALL team members must be present, the entire time!
 * Appropriate attire
 * Be a good listener
 * Ask questions, participate!
* You are welcomed/encouraged to attend presentations on the day of the other group

---

# Faculty Advisor

.box-inv-4.SMALL.sp-after-short[
Each team must select a Texas A&M faculty advisor.
]

* Advisors are chosen for their expertise or interest in the project topic.

* Instructors may assist in identifying advisors if needed.

---

# Faculty Advisor

* Advisors serve as the team's subject matter expert, providing guidance & recommendations.

* Biweekly meetings are recommended, based on advisor availability.

* Advisors take an active advisory role but are not responsible for developing solutions.

* Teams must treat advisors with professional respect & courtesy.

---

# Sponsors

* The project sponsor is the **client**, owner of the project problem or opportunity.

* Each team must assign a *Point of Contact* to manage sponsor communication.

* Communication frequency & format should be defined based on sponsor availability.

* Regular **face-to-face** meetings (in person or video) are required; email alone is insufficient!

---

# Sponsors

.box-inv-4.SMALL.sp-after-short[ALL team members should attend sponsor meetings; absences must be acknowledged with reasons]

* Meetings are scheduled by the POC and sponsor and must start and end on time with an agenda.

* Only the sponsor may cancel meetings; cancellations must be reported in technical presentations.

* If meeting frequency is unacceptable to the sponsor, document it and consult the primary instructor.

---

# Confidentiality & Non-attribution

* Course data, client info, and project discussions are confidential

* Share information only with classmates or instructors, following confidentiality rules

* Keep confidential materials secure

* In a folder, binder, or password-protected device

* On your person or in a safe location (room, backpack, car)

---

# Confidentiality & Non-attribution

* Don’t attribute information to specific people or teams

* Use phrases like: "It’s my understanding that…"

* Treat NDAs seriously!

.center[
<figure>
<img src="images/Important.png" alt="Important" title="Important" width="20%">
</figure>
]

---

layout: false
name: slides
class: center middle section-title section-title-5 animated fadeIn

# Grading & Assessment

---

.small[
| Team Grades | Weight on the Final Grade | Grade Type |
|:------------|:-------------------------:|:----------:|
| Mini Management Packet | 5% | Technical |
| Phase 1-3 Presentations | 15% (5% each) | " |
| Phase 4 Presentation | 10% | " |
| Showcase Poster | 5% | " |
| Communication Log | 2% (1% each) | " |
| Final Report | 18% | " |
| | | |
| **Individual Grades** | &nbsp; | &nbsp; |
| Phase Presentations | 15% | Communication |
| Writing Assignments | 18% | Writing |
| Peer Performance | 12% | &nbsp; |
]

</div>

---

---

# Deliverables

* Code of Conduct: will not be graded but MUST be turned in as a group assignment!
 * As well other things in the deliverables table: Showcase Registration, Meeting Logs, etc.

* Next week: more details on the Engineering Showcase, Phase Presentations, etc.
.center[
<figure>
<img src="images/stay-tuned.png" alt="stay tuned" title="stay tuned" width="30%">
</figure>
]

---

# Deliverables

* Check Canvas for all due dates
 * They’re final unless we send a notice by Canvas + email
* You can resubmit assignments for a better grade after the due date
* All regrade work must be in by the assignment’s close date
--

* When resubmitting, make sure to:
 * Highlight what you changed
 * Address ALL feedback from class, presentations, or office hours

---

# Use AI responsibly and within limits

* Brainstorm ideas
* Check your work for grammar, spelling, clarity, and brevity

.box-5.sp-after-veryshort[
AI = tool, not shortcut!
]

--
.box-inv-5.SMALL.sp-after-veryshort[
AI should support learning, not replace it! 
Always ask questions and participate in class
]

.box-5.small.sp-after-veryshort[
Use AI in ways you could confidently explain to your instructor or classmates.
]

---

# You may NOT use AI to

* Write assignments for you
* Solve major problems or programming tasks
* Generate analyses or substantive content

.box-inv-5.SMALL.sp-after-short[
All work must reflect your own effort 
Misuse may be treated as academic dishonesty!
]

.box-5.SMALL.sp-after-short[
Do NOT input confidential sponsor information into AI tools
]

---

# Team Work

.pull-left-3[
&nbsp;
<figure>
<img src="images/Fry1.png" alt="Fry" title="Fry" width="94%">
</figure>
]

.pull-middle-3[
&nbsp;
.box-inv-5.SMALL.sp-after-short[
In industry, project failure is rarely caused by lack of technical skill.
]
]

.pull-right-3[
.box-inv-5.small.sp-after-veryshort[Most often caused by:]
.box-5.small.sp-after-veryshort[Unclear expectations]
.box-5.small.sp-after-veryshort[Poor communication]
.box-5.pequeno.sp-after-veryshort[Uneven workload distribution]
.box-5.small.sp-after-veryshort[Missed deadlines]
.box-5.small.sp-after-veryshort[Unresolved conflict]
.box-5.small.sp-after-veryshort[Unprofessional behavior]
]

---

.center[
<figure>
<img src="images/what-is-social-loafing.png" alt="what is social loafing" title="what is social loafing" width="75%">
</figure>
]

---

---

# Examples of social loafing

* Disappearing after class and not responding to messages.
* Continuing poor communication even after being made aware of the issue.
* Expecting the team to adjust around your personal schedule.
* Missing meetings, arriving late, or leaving early on a regular basis.
* Failing to complete assigned work, or turning in work that is incomplete, careless, or must be redone by teammates.
* Working on off-topic ideas without team approval and expecting credit.
* Attending meetings but being distracted (by phone instead of participating).
--
.box-5.small.sp-after-veryshort[
All team members MUST be reliable, communicative, prepared, and engaged!
]

---

.box-5.normal.sp-after-short[
Social Loafing means not contributing your fair share to team work
]

.center[
<figure>
<img src="images/social-loafing.png" alt="Social Loafing" title="Social Loafing" width="80%">
</figure>
]

.box-inv-5.sp-after-short[
This behavior creates serious problems for teams 
and is taken very seriously in this course
]

---

layout: false
name: slides
class: center middle section-title section-title-6 animated fadeIn

# Code of Conduct

---

---

# Code of Conduct

&nbsp;

.box-inv-6.normal.sp-after[
Let us prevent these problems BEFORE they occur
]

---

# Professional Standards of Conduct

* .small[Learning includes respectfully engaging with different opinions & keeping an open mind.]

* .small[All in this course is expected to treat others with **courtesy, respect, and professionalism**.]

* .small[These expectations apply to **all** course-related activities & meetings.]

* .small[Communication should be factual, constructive, and free of harassing, offensive, or demeaning language.]

---

# Professional Standards of Conduct

* .small[Disagreements are allowed, ... but they must be fact-based & civil in tone.]

* .small[Abusive, disruptive, threatening, harassing behavior and profanity are **NOT** acceptable.]

* .small[If an issue occurs, individuals will usually be informed and guided on appropriate behavior, and are expected to correct it.]

* .small[Serious violations may result in University disciplinary action.]

* .small[Students are responsible for knowing and following all student rules and policies.]

---

layout: false
name: slides
class: center middle section-title section-title-7 animated fadeIn

# Next Week Preview

---

---

# Project Charter Adjustments

.center[
<figure>
<img src="images/ProjectCharterIntegration.png" alt="Project Charter Integration" title="Project Charter Integration" width="80%">
</figure>
]

---

# V-Model

.center[
<figure>
<img src="images/SystemsEngineeringVeeEdited.png" alt="vee-model" title="vee-model" width="70%">
</figure>
]

---

&nbsp;

.box-inv-7.large.sp-after-short[
What is a Configuration Item?
]

.box-7.large.sp-after-short[
What is a Configuration Item 
in Data Engineering?
]

---

---

# What is a Configuration Item (CI)?

.center[
.small.sp-after-veryveryshort[Any hardware, software, firmware, document, or combination thereof that is:]
]

.box-inv-7.small.sp-after-veryveryshort[
Individually identifiable
]

.box-inv-7.small.sp-after-veryveryshort[
Formally baselined
]

.box-inv-7.small.sp-after-veryveryshort[
Controlled under configuration management
]

.box-inv-7.small.sp-after-veryveryshort[
Verified against approved specifications
]

.center[
.small[

In other words, a CI is anything the organization has decided must be controlled, versioned, and verified as its own official product element.]
]

---

# What Counts as a CI in a Data Platform

* In data engineering, a CI is:

* Any version-controlled, independently testable, production-quality component of a data system that has formal requirements, formal tests, and formal approval.

* A CI is no longer "just a file", it becomes a certified system component.

---

.small[
| CI Area        | Examples                         |
|----------------|----------------------------------|
| Sources        | Ingest schema, API feed          |
| Pipelines      | ETL job, stream proc             |
| Storage        | Warehouse schema, lakehouse      |
| Code           | Feature lib, validation          |
| Models         | Forecast, classifier             |
| Orchestration  | Airflow DAG, dbt                 |
| Interfaces     | API, data contracts              |
| Governance     | Quality rules, PII mask          |
| Docs           | Data dict, lineage               |
]

</div>

---

&nbsp;

Check out ...

https://www.thomasthwaites.com/the-toaster-project/
]

---

Make it a GREAT semester! ツ