-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
49d868a
commit eea69b4
Showing
1 changed file
with
99 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,99 @@ | ||
# 00 - Welcome | ||
|
||
## Content | ||
|
||
- Administrative presentation | ||
- What is Designing? | ||
- Architecure & Methodology | ||
- Next lecture activities | ||
|
||
## Administrative Presentation | ||
|
||
- **First partial** | ||
- _Domain Design_ | ||
- **Second Partial** | ||
- _Persistency_ | ||
- _UI_ | ||
- _Architecture_ | ||
|
||
### Anual Assigment | ||
|
||
- Party up to 7 | ||
- Intercourse within Friday courses | ||
- One **Helper** assigned per group to canalize questions. | ||
- Approving | ||
- 3 Checkpoints per Quarter | ||
- Only one B(ad) per Quarter | ||
|
||
### Individual Assignments | ||
|
||
- Oriented to implenting coding | ||
- Quick evaluation | ||
- Same **Herlper** as in groupal assignment | ||
- Approving | ||
- 3 Checkpoints per Quarter | ||
- Only one B(ad) per Quarter | ||
|
||
### In-class practice | ||
|
||
- Design | ||
- Oriented to designing solutions | ||
- Functional implementation is not required | ||
- Mandatories | ||
- Necessary to understanding the in-class explanation | ||
- 50% required to promote | ||
- Corrections | ||
- Random showcase | ||
- At least 1 member of a party | ||
|
||
## What is Designing? | ||
|
||
**Problem Solving** | ||
|
||
`Problem -> Bulding -> Solution -> Information System` | ||
|
||
**Software** _vs_ **Information System** | ||
|
||
### Designing a System | ||
|
||
`Analysis -> Problem understanding -> Requirements definitions -> Designing solution shape` | ||
|
||
Designis is | ||
|
||
- Evaluate alternativas | ||
- Ponderate Qualities | ||
- Take decisions | ||
|
||
#### Systems' Definition | ||
|
||
- Components | ||
- Funtionalities/objects/classes | ||
- Responsabilities | ||
- What thing is solved by what | ||
- Relationships | ||
- Interactions | ||
|
||
## Architecture & Methodology | ||
|
||
### Development Metholodogy | ||
|
||
Iterative and Incremental. | ||
|
||
In each iteration adds valueto the product. | ||
|
||
### Architecture | ||
|
||
- Presentation: User interaction | ||
- Domain | ||
- Persistency: Focus on data storage | ||
|
||
Technology will go trhough the design. Even though a design must not be married to a technology, it must be aware of it. | ||
|
||
### Next class | ||
|
||
- Go over [Objects](https://www.pdep.com.ar/material/apuntes) | ||
- Do [Macowins](https://docs.google.com/document/d/1mjWKl9YH9Bb39iIUl1bQj_xhx_-CjCAMpcAXRqKhVjU) | ||
- Read [Java](https://docs.google.com/document/d/1VYBey56M0UU6C0689hAClAvF9ILE6E7nKIuOqrRJnWQ/edit) | ||
- Read [Communicatig a Desing](https://docs.google.com/document/d/1eXLlNppAX-7E2M8Xxs0MCckdn4XVEYmeQNaS_E1RqTc/edit) | ||
- Read [Qualities of a Desing](https://docs.google.com/document/d/14HdvHvS33WqYb6Ak0BGa0IeCTbzeCRSDKs-1Ot-qLDw) | ||
- Read [Design of Error Managing](https://docs.google.com/document/d/1u7t9eKDdAVwhQVAkstV0nkfAGIJsY2O_UEHKJJVje6c/edit#heading=h.x500jbxzopra) |