1.1 Course Introduction Software Design & Architecture

You might also like

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 28

+

1.1 Course Introduction


Software Design &
Architecture

+
Class Structure

Classes
will be a combination of lecture material and
discussions

We will frequently have design and architecture discussions


and
activities in class that involve concrete examples

Lecture slides will be posted,discussions and activities will


not

+
Key Information Source

courses.finki.ukim.mk

Watch

for updates and notifications on the course page

+
Resource Availability

Slides
and will be posted on the course web page

Slides are mainly theoretical,concrete examples are covered


in class

In class activities will not be posted

+
Reference Materials
There

are NO prime textbooks for this course

These
may
be VERY helpful:
Software
Architecture:Foundations,Theory,and

Essential Software Architecture

May

find it online..
Mythical Man Month

Practice

+
Intended Learning Outcomes

Critique
an existing architecture or design.

By the end of the course you should be able to:

Differentiate
how various architectural styles and design
patterns enhance and degrade a systems functional-and
non-functional properties.

+
Intended Learning Outcomes

Generate
and justify and architecture and/or design given a
collection of requirements.

Produce and present concise and unambiguous architecture


and
design descriptions.

Create and implement an architecture and design,refining


it into a complete system.

+
Expectations
Be

Professional

Questions

Attend

in class,email,interactions with TAs

Lectures

C
ommunicate with your teammates if you are away
Participate
Discussions,activities,group

Provide
This

project

Feedback

course is a cooperative endeavor

+
Your Expectations?
What

do you hope to get out of the course?

+
Project:Mobile Applications
Goals:
Make

something useful
Learn something new

Leverage current technology


Have fun

+
Project
Constraints
Be

useful,novel,and leverage technology


Cannot require crowd involvement

Cannot be a CRUD application,web front-end,or require


extensive server-side code
Must use at least two external data sources

+
Platforms

Must

be demoed on a mobile phone from any of the


following platforms:
iOS,Android,

WP, BB10

App

should conform to the platform (e.g.,support hardware


back button if available while hiding on- screen navigation
controls).
Integrate with appropriate platform services.

+
Motivation

This is anopportunity to do something


design andbuildsomething special.
_great_.The project isflexible and is worth
a significant portion of your final grade.Use this to

+
Deliverables

Deliverable

0:Background/Team (P/F)

Deliverable

1:Project proposal + presentation (5%)

Deliverable

2:Architecture activity (P/F)

Deliverable

3:Prototype demo (5%)

+
Deliverables

PIVOT

Deliverable

4:Design activity (P/F)

Deliverable

5:Project arch + design (30%)

Deliverable

6:Project presentation + video (10%)

+
Assessment
Project

deliverables:50%

2% best proposal (most useful + best idea)


+ 2% best prototype demo

+ 2% best final demo (most useful + best idea)

+ 2% accepted to curated app store

Final

Exam:50%

Notes

Some deliverables

will be pass/fail
MUST pass final exam(over 50%) and ALL pass/fail elements

+
Project Scaling
Project

deliverables:50%

(project + bonus) * scale = final project grade


5:completeness

(compared to proposal)

Scale
will range between 0.75 and 1.0 (25 points)
5:utility

5:polish
10:difficulty

+
D1:Project Proposal
Electronic

Submission

Presentation in class

Value:5%

Written

description of your project


Contents:
In-class 5 minutepitchto the class

Details posted on the course website

+
D2:Architecture Activity
Activity

in class

Value:Pass

Each

/ Fail

group will be assigned an architectural style.


Details:
Your job will be to come up with a project idea that takes

advantage of the style.


Each project will be discussed concretely in class.

+
D3:Prototype Demo
Electronic

submission

Presentation
Apps

In class

will be demoed in class.


Details:
~10 minutes per group.

Apps should be ~80% complete.

+
Pivot

+
Pivot Details
Email

from me when time

Details:

The architecture

and design of your app will facilitate certain


kinds of software evolution.
As your client,I will ask for some kind of new feature or other
change.

You will add this feature to your project for the final demo,and
reflect on how your design enabled / inhibited this change.

+
D4:Design Activity
ActivityIn

class

Value:Pass

Each

/ Fail

group will be assigned design pattern.


Details:
Your job will be to come up with a project idea that takes

advantage of the pattern.


Each project will be discussed concretely in class.

+
D5:Architecture and Design
Review

Electronic

Submission

Design Review Meeting in class (20minutes)

Value:30%

medium-length description of your apps architecture and


Details:
design,and why you made the design decisions you did will be
submitted electronically.
Each group will take part in a 20 minute discussion describing
(and answering questions about) their design decisions.

+
D6:Presentation andVideo
Electronic

Submission

Presentations: In Class

Value:10%

short description of how the project turned out,along with a


reflection on the pivot will be submitted electronically.
Details:
Final demos (~10 minutes) will be given in class.

+
Academic Integrity
Much

of this course is collaborative

Plagiarism

is not acceptable
Cheating is not acceptable

Team

members are expected to do their required share of


the work
Any individual deliverables are expected to be done
appropriately

This is important!

+
Deliverable 0
Submit
a two paragraph text file (.TXT) to the link on courses

Subject:

D0 Design Impressions

Paragraph

1:

Your

name and a high level overview of development experience.


Include a sentence about what you would like from this course.

Paragraph

2:

description of how you have encounteredarchitectureand/or


designin your experience.

for next class 25.09.2016 at 23:55


Due

+
Upcoming Deadlines
Form

project groups September 30 23:55 (we will talk about this on


October 03 in class if you do not have a group!)
Submit

to appropriate link:

Team

member names, studentid, team leader that will submit


This is important be ACCURATE

D1:Project

Proposal

Submit
proposal on the courses link October 02 23:55

Short presentation in class October 03

Start thinking about this now!

You might also like