Class was broken down into teams in order to specialize and tackle the
enormous task ahead of us. Teams are as follows:
Business Team
-------------
Team Leader: Alan
Members: Ben, Bryce, Mike, Sunny, Wilson, Xue
Responsibilities:
1) Understand problem domain. What is the problem we need to solve? How
can we cut costs for companies and/or up their revenue? How is business
currently done? Will we enhance or revolutionize current business
procedures? What business are we after? What business transactions will we
address?
2) Produce Project Document. Document consists of:
I) Project Objectives, which are (SMART):
a) Specific
b) Measurable
c) Attainable
d) Realistic
e) Time-limited
What is the desired outcome? How will we know when we have achieved it?
II) Identified Target Users, *possibly* involving:
a) market research
b) consulting with experts in business focus
III) Project Scope
a) a culmination of definition efforts
b) enumeration of key elements in project (closely related to objectives)
c) breakdown of key elements into tasks, and tasks into subtasks
d) often includes software diagrams, schematics, UI sketches, hardware
layout
Joe will try and find examples. If Joe forgets, please yell at him.
Coders
------
Team Leader: Scott
Members: Burt, Chris, Joe
Responsibilities:
1) Practice C#.
2) Practice XML.
3) Practice writing "Web Services".
4) Practice designing/writing P2P servent-based architectures.
5) Practice with Visual Studio.Net.
6) Be ready to code if/when scope is done.
IT Architects
-------------
Team Leader: Burt
Members: Ben, Sunny, Xue
Responsibilities:
1) How does XML, C#, .Net, UDDI, Soap, ASP.net?, ADO.net?, Biztalk work
together to form a solution?
2) How can we leverage the above for businesses (once identified)?
3) Select most predominant standards, and most likely to be adopted
standards (ie which Schemas should we use?)
System Administration
---------------------
Team Leader: Daniel
Members: Chris, Scott, Wilson
Responsibilities:
1) Take care of CVS solution. Most likely going with www.sourceforge.net.
2) Get our W2K server up. Determine exact use (if any) of that server.
3) Lock down and firewall as necessary any server of ours.
4) Get an awesome site up on www.openbuy.ics.hawaii.edu.
5) Take care of OSI licensing and source distribution as needed.
Management
----------
Joe
Responsibilities:
1) Set deadlines.
2) Coordinate effort.
By Friday:
1) individual teams schedule own meeting time outside of class
2) read applicable materials already handed to us regarding specialty area
3) read more than what we were handed regarding specialty areas
4) have an oral report (one per team) to present to rest of class
5) weekly progress reports (one per team) each Wednesday
Thank you for your cooperation, and have a nice day.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello all,
Just our meeting notes for everybody's reference:
Class was broken down into teams in order to specialize and tackle the
enormous task ahead of us. Teams are as follows:
Business Team
-------------
Team Leader: Alan
Members: Ben, Bryce, Mike, Sunny, Wilson, Xue
Responsibilities:
1) Understand problem domain. What is the problem we need to solve? How
can we cut costs for companies and/or up their revenue? How is business
currently done? Will we enhance or revolutionize current business
procedures? What business are we after? What business transactions will we
address?
2) Produce Project Document. Document consists of:
I) Project Objectives, which are (SMART):
a) Specific
b) Measurable
c) Attainable
d) Realistic
e) Time-limited
What is the desired outcome? How will we know when we have achieved it?
II) Identified Target Users, *possibly* involving:
a) market research
b) consulting with experts in business focus
III) Project Scope
a) a culmination of definition efforts
b) enumeration of key elements in project (closely related to objectives)
c) breakdown of key elements into tasks, and tasks into subtasks
d) often includes software diagrams, schematics, UI sketches, hardware
layout
Joe will try and find examples. If Joe forgets, please yell at him.
Coders
------
Team Leader: Scott
Members: Burt, Chris, Joe
Responsibilities:
1) Practice C#.
2) Practice XML.
3) Practice writing "Web Services".
4) Practice designing/writing P2P servent-based architectures.
5) Practice with Visual Studio.Net.
6) Be ready to code if/when scope is done.
IT Architects
-------------
Team Leader: Burt
Members: Ben, Sunny, Xue
Responsibilities:
1) How does XML, C#, .Net, UDDI, Soap, ASP.net?, ADO.net?, Biztalk work
together to form a solution?
2) How can we leverage the above for businesses (once identified)?
3) Select most predominant standards, and most likely to be adopted
standards (ie which Schemas should we use?)
System Administration
---------------------
Team Leader: Daniel
Members: Chris, Scott, Wilson
Responsibilities:
1) Take care of CVS solution. Most likely going with www.sourceforge.net.
2) Get our W2K server up. Determine exact use (if any) of that server.
3) Lock down and firewall as necessary any server of ours.
4) Get an awesome site up on www.openbuy.ics.hawaii.edu.
5) Take care of OSI licensing and source distribution as needed.
Management
----------
Joe
Responsibilities:
1) Set deadlines.
2) Coordinate effort.
By Friday:
1) individual teams schedule own meeting time outside of class
2) read applicable materials already handed to us regarding specialty area
3) read more than what we were handed regarding specialty areas
4) have an oral report (one per team) to present to rest of class
5) weekly progress reports (one per team) each Wednesday
Thank you for your cooperation, and have a nice day.