Team Meeting
- allocate job assignments for each team member regarding the RAD
1. Charles
2. Yow-Hann Lee
3. John and Carter and Aaron
4. Sunae and Seung Hoi
5. " "
6. " "
- Tuesday Deadline for individual RAD sections (rough draft)
- 4-5 hours each section
- Thursday Deadline for Good Copy of RAD
- give client username and password to our team site
- inquire TA for suggestions on Quesions
- keep track of hours in textfile with one line description, date and forward to
Carter weekly
Section 2_______________________________________
User Characteristics
customers - zero technical knowledge
Constraints
1
- supervisor allowed to monitor all chats
- authentication requirements (valid license key)
3
- web browser enabled
- internet connection
8
- clients connecting to server
10
- MTBF?
- redundant servers
- automatic database backup for recovery (RAID)
- if MS Access, required to setup up interface to query from Access
11
- only admin allowed to monitor conversations
- only user and chat support can view the current conversation
- encryption?
- creation of separate webapp for clients vs. administrator
- application located on server; therefore, client would not have access
Assumptions and Dependency
- supplied with database
Section 3___________________________________________
3.1 External Interfaces
- write log simultaneously as live chat with encryption?
- ask client: How will the log be stored??
3.2 Functions
- creation of own account for chat support system?
- provide visual support??
TA Meeting
- Introductions with TA and team members
- Andy aka Seung Hoi
- Trevor to act as a project manager/consultant
- leader of meetings to run agenda of meetings in the future
- alternate between team members of who leads meetings
- Structure of design requirements is pretty relaxed
- feel free to explore extreme programming or other programming styles if
necessary
- showed Trevor rough format of RAD
- showed Trevor Phase Leader and Management Roles
- justified why there are some Managerial roles not assigned
- Trevor strongly suggests for Risk Manager and Software Version Control Manager
- unvealed First Meeting with Client Questions to be asked to Trevor
- Trevor advises for our questions to be more specific and geared towards
technical individual with extensive programming background
- potential for functionality difficulties (i.e. JVM versions)
- provide remote access connections
- Trevor advises to prioritize functionality of software
- most likely will not be able to implement everything client wants
- contact client of functionalities that you will cut from implementation (thoughout
the course of the project)
- Trevor advises to clarify with the client the possibility of using open source
- (this will depend on the licensing i.e. OPENGPL)
- Jabber is instant messaging platform that you can develop on top
- How client feels towards open source?
- Coding Documentation, design documentation may have to be created on your own
if not provided by open source
- objective of the course is more oriented towards professional/practical
experience; therefore, open source code may not be regarded as plagarism
- ambiguous statement: integrate with web browser and .net applications
- if you have questions for client, tell the client your suggestion for what you
want to do as well as including the question
- there may be a long return time in e-mail interactions
- meetings to be changed to Wednesdays from 4-5pm - to be confirmed by Trevor
- Trevor may or may not attend meeting with Robert Hui
- decided on the meeting leader for next week: Charles
- templates of documentation may be discarded
- submission of documentation process
- marked out of total of 10
- first marked out of 8
- returned by TA and then given few days for revision
- reassessed by TA for final 2 marks
- given to the client for review
- management of word documents
- may want to consider CVS
- proposed method is to use FTP Server with text file notifying changes
- Trevor advises for central repository for version control of code
- CVS most successfully run from home account
- Charles will be responsible for setting up CVS
- Presentations to be given in meetings (i.e. Charles gives everyone an update
on how to work with CVS)