Task ID: Not Applicable
Last night I sat down and dedicated time to identifying the tasks required to complete the first half of this project. Now, provided I have all the bases covered, I can develop a Gantt chart by estimating (from my personal experience) how much time the tasks will take to complete. This project is going to be huge.
Tonight I sent an email to Leone, the project supervisor, asking her if she feels I’m on the right track. I really want to get great marks for this project and I’d love to see and hear about creative little critters using BRAINtastic and making wonderful music.
The current list of tasks I have identified are (quoted from the email I sent to Leone):
I have developed a list of activities or tasks that can be done during the analysis stage – can you please let me know if these are not acceptable or not meeting the purpose of the analysis stage?
- Conceptual Storyboards (preferably developed by EdAlive: communicate essential UI needs).
- Data Flow Diagrams (how data flows between and is processed by the BRAINtastic API and the plug in musical composition game as well as instrument or composition data being read, loaded and presented on the screen).
- Data Dictionary (document elements identified in DFD including data exchanged by the BRAINtastic API and the game).
- Process Narrative (to accompany the storyboards, describing the transition between storyboards as well as how a composition is arranged).
- ERD (describe how the composition is structured in memory and in a file to be used at a later date).
I feel that these forms of documentation adequately describe the needs of EdAlive and the data used, the logic needed to structure the data and the processes to manipulate that data. If you (EdAlive or Leone) feel their are any things I might be missing out on or thoughts that might guide me to producing a good analysis, please let me know. It would be much appreciated.
I have also developed a list of activities or tasks that can be done during the design stage – can you please let me know if these are not acceptable or not meeting the purpose of the design stage?
- Interface Designs/Storyboards
- Report Detailing:
- Targeted software platform and intended system requirements (is this necessary?).
- Design paradigms used to develop the software (I’d like to use an Object Oriented, Model-View-Controller approach using the Publish/Subscribe [or similar] pattern, don’t know yet if Lingo will let me).
- File arrangement (stating something like instruments must be stored in a folder like “./instruments/”).
- File Structure documentation (I’m thinking a UML class diagram might be made redundant here).
- Class Responsibility Collaboration (CRC) Cards (to help determine how objects are related)
- UML
- Use Cases
- Class Diagrams
- Sequence Diagrams
- State Transition Diagrams
- Activity Diagrams
- Pseudocode to detail logic behind:
- Composition saving and restoring
- Playback of compositions (namely the relationship between the arrangement of instruments on the screen and the timing of an instrument’s playback)
- Definitions of the callback functions I need to implement for the BRAINtastic API
Again, I feel these forms of documentation together cover the logic behind an event driven program. Please let me know if you feel I might have gone off track or missing out on some critical thoughts or concerns of the project.
