- Week 4
- Jan 24, 2001 through Jan 30, 2001
- Action items
- Our meeting time with client will be Monday afternoons at 3pm in Dey Hall 103.
Meetings will take place approximately bi-weekly, perhaps more towards the beginning
of the semester and less towards the end of the semester.
- Necessary files during the execution and completion of our application will be stored
on the networkhood within the Foreign Language domain.
- Our naming convention will follow the naming convention mentioned in our supplemental documents.
The user will name the prefix of the files which will carry across all created files. The suffix
of all files will follow convention.
- Email scripts within our application will notify the editor when a lesson has been create with
necessary information that the editor needs to create the website (ie. special instructions, file
name prefix, etc.).
- Audio file conversion should be a feature, but is not of top priority. If we get to the audio
conversion feature, we are only required to handle CD extraction.
- The necessary features have been clarified:
- Create versus Modify options
- Word execution for text input (lyrics)
- Graphic supplied by either file or URL
- Special instructions for any part of the lesson
- CD extraction
- Security prompts where needed
- File transfer to network neighborhood
- Email scripts for communication between the user and the editor
- Administrator's menu
- Graphics preview
- Audio preview
- Copy and renaming of files within the application
- Browsing capability
- The language that we will now use for development is Visual Basic. We have chosen
this language instead of C++ for the ease of implementing a GUI. VB hosts a built-in GUI.
- We no longer need to find a GUI due to the selection of VB as our development language.
- GUI flow defined (roughly) from start to finish of the application.
- We are still unsure about the legal rights of using freeware. This will come into play
when we are looking into using libraries for CD extraction or other features.
- We need to look into VPN.
- What is it?
- How does it work?
- Does any implementation change when using it compared to using the network neighborhood?
- We don't necessarily agree with the way that client suggests for file organization.
He suggests that all of the new files are created and saved in the same folder not separated
from each lesson.
- There are some upcoming assignments and deadlines--Contract and Schedule.
- Outstanding problems
- We still need development tools. VB is now on some SN machines, however we need copies
for home development. We also need books for training and learning since this is a new
language for our team.
- Plans to address outstanding problems
- SN will give us copies of VB.
- If copies are not immediately available, we will receive a copy through Microsoft.
- Hopefully through our Microsoft representative, our team will receive training materials--books.
- Hours worked for each team member
- This week:
- Karen Parker: 8
- Brianne Roth: 7.5
- Sean Rielly: 10.75
- Jason Howell: 13.75
- Sam Adu: 2.75 (+ other)
- Total so far:
- Karen Parker: 18.5
- Brianne Roth: 13.5
- Sean Rielly: 14.75
- Jason Howell: 23.25
- Sam Adu: 3.75
- Milestones (schedule status)
- Second meeting scheduled and occurred with client along involving
clarifications on features and requirements.
- We will be using VB and machines in SN have been set up for this.
- Approaching (next week):
- GUI development should start ASAP
- Research emailing scripts, opening another application (Word) through system calls,
CD extraction, and audio and graphics preview.
- Contract and Schedule deadline approaching--Feb 6.
- Problems/slips and plans to address:
- By this time I had hoped that our team would be beginning the GUI prototype phase,
however, this will not begin at least until next week, if not the week after due to
other assignments being due--Contract and Schedule. This does not hinder the final
finish time at this moment. Thus, there are no slips to report at this time other than
this may be a problem later depending on other future events.