I posted this to the community list earlier, but as far as I can tell it appears that topica has dropped the ball again. Maybe this is not too far off topic.
------- I am getting started in the process of putting together a pretty large application and it will be my first "major" fusebox application. I am going to follow the entire process of wireframing -> prototyping -> mind map -> fusedocs, but I was wanting to see if I could get some "expert" opinions as to what kind of time I would be looking at for each step of the process. As this point, I am going to be doing the entire application myself, so the purpose of this schedule is to show my boss what kind of time requirements I am looking at and to encourage him to provide me with some help. I have never put together an application of this magnitude utilizing the Fusebox / FLiP process, so I would like to find out what some other "experts" have to say with regards to a schedule to verify the ideas I have right now. I don't have all of the specifics of the app yet (and it would take to much space), but here is a rough outline of everything. ------- The application is a project management system for computer hardware R&D teams. The main core of the application is a "workarea" where the project team can collaborate. All of the application is secure using data that has to be retrieved real time from an LDAP server. The project manager can create their own workarea in real-time and then select from a series of "plug-ins" for additional functionality. Basically the workarea is just the front page of the project area that ties all of the plug-ins together. The list of plug-in applications right now include (all of which have to be designed in a modular plug and play fashion to work with each other and the workarea as well as have the ability for new modules to be added in the future) - Calendar app - - Similar feature set to MS Outlook - Weekly vs. Monthly calendar views - Schedule recurring events - Attach files and or links to events - Send email to all event participants - Download events to MS Outlook Email Reflector / Archive - Receive and broadcast email messages received through specified email address. - Strip attachments off email messages, store on server, and insert link to attachment in broadcast email messages. - All message archive to be viewed and searched via web interface Document Management System - Post and organize documents in a nestable folder structure - Create and rearrange folders - Documents may have revision control (user specified) allowing for tracking, check-in / check-out, locking, etc. - All version notes to be entered when a new version of a document is uploaded. Document Sign-Off - Post a specification and specify a list of "reviewers" - Email notification of new document to list of "reviewers" - Each reviewer can respond with approve / disapprove and comments - Documents can be nested (main document with chapter sections) where each section can have a different set of reviewers Issue Tracker - Each issue tracker will have a certain set of required fields - Ability to add custom fields in addition to required fields - Post and update issues - Ability for user to attach a file to an issue - Search for specific text, user, date in issues Discussion List - Threaded discussion list - Email notification upon thread update (if user chooses to be notified) - Ability for user to attach a file to a message - Capability for a manager to stop a discussion and call for a vote (manager specified voting options, time period, etc.) - Search capabilities HTML Page - Ability for user to create a "flat" html page through a built in WYSIWYG editor (no access to html). - Options would include fonts, colors, tables, links, and images. Change Request Tracker - User can log new change request and attach supporting documentation - Each change request has a list of users that must reply to change request with an approve / disapprove vote and comments - Email notification of new change request to list of "reviewers" One other note on security - each of the modules can be individually secured (with roll-down permissions similar to Windows permissions) which means that just because John Doe has access to the workarea, does not mean he has access to the calendar. As if this was not bad enough, the project workareas also have to be nestable meaning that a design team may include individual groups for manufacturing, etc. that could each have their own "sub-workarea" under the main project team workarea. ------- I realize this list / description is fairly generic, but if anybody felt like throwing out a ball-park time frame for each step of the Fusebox / FLiP design process for this app, I would really appreciate any input. I know the prototype process is dependent on the client, but for this process I would assume a fairly slow response to any requests for client interaction. Out of morbid curiosity, and I probably don't want to know since I am paid salary, but what would anybody charge for developing this kind of app? Thanks for the help -- Jeff Chastain ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
