Meeting Objective(s) - GoogleCode

farmacridInternet και Εφαρμογές Web

2 Φεβ 2013 (πριν από 4 χρόνια και 4 μήνες)

195 εμφανίσεις

9
-
8
-
2011

All team members are expected to meet in class today


---
discuss Process model to follow

Agile Process Model (Incremental)


Potentially hybrid between component
based and agile process model

---
identify team leader, pick a


corporation name

Austin Laugesen, MacroHARD

----
assess their actual skills

Austin
-

9 internships (4 summer
-

5 academic semester) lots of coding
experience

Paul
-

class experience c/c++/java. Worked on team projects.

Brandon
-

Motorola internship flash/c/c++/java Perl so
me web dev little version
control exp.

Josh
-

graduate student assistant, c/c++/java, undergrad. researcher

Yamini
-

Received BS in India some programming on the side, java

----
training needs

SVN
tutorial


Austin will provide this tutorial to the group

Si
lverlight? C#?



Austin will provide this demo

----
prepare initial project report for submission in ICON

TODO:

create tutorial



9
-
9
-
2011

Attendance: everyone but Brandon


Meeting Objective(s):

1.

Ideally, we’ll know exactly what technology we plan to use by
the end of the meeting. We can start by adding technology we
want to use to the list below and cross out things we don’t want
to use. We’ll collectively discuss why we should or should not
pursu
e a technology. Some things will be obvious to cross off the
list, such as Python and its web framework Django because our
group lacks much knowledge around the technology.



Two things I think we should keep in mind:

1.

Do we want to build something from the

ground up or utilize
open source software and build on top of a foundation?

2.

“Changes to content must be easy for non
-
programming staff.”


This means we need to build a Content Management System
(CMS)

3.

Team isn’t opposed to using open source CMS and buildi
ng on
top of it.

9
-
9
-
2011



Technology options:

Build from the scratch


common implementations:

1.

LAMP

(Linux, Apache, MySQL, PHP)

2.

Windows, IIS, SQL Server, C#.NET (
asp .NET
)

3.

X
Python Django

4.

Ruby on Rails

5.

JSP (Java Server Pages) hosted through apache web server

6.

Flash

7.




Build on open source foundation


both of which are CMSs:

1.

Joomla (PHP & MySQL)
link is here



j
query

extensions
exist

to
‘liven’ up the site, here’s
another

2.

Drupal

(PHP & MySQL)



Stuff to think about down the road...



Things we’ll have to explicitly ask Raman wh
en we meet with him.



“Wep application for banking operations… and support mobile
devices.”

1.

Is this for internal use (employees only) or external use, e.g.
customers? (We shouldn’t assume anything.

)

2.

How will people interact with this website? (Some cust
om
interactivity might be hard with generic CMS such as Joomla or
Drupal).

3.

What do we want to allow our customers to edit (what aspects
can a non
-
programmer edit)?

4.

Is it fair to assume this web
-
app is a browser application? Or a
rich client that pulls stuf
f from the web.

5.

Mobile support: browser or rich clients?

6.

What level of security?

7.

Who are the users? What’s the intuitive understanding of users?

8.

The System must provide three levels of users a. Drivers

9.

b. Passengers c. System Administrators

Can admins modify users’ accounts


Requirements for Raman:

Svn