- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsHello experts,
I need to write a detailled functional system design document for a software project. Any templates, or road map is appriciated.
Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: thomaswrightPosted on 2007-04-02 at 20:41:35ID: 18841141
You need what's called an SDLC (System Development Life Cycle) template. Here is a roadmap ( a chronological step-by-step process) of an SDLC.
1. Team - A few end users and Information Systems Developers form a development team.
2. Schematic - The initial prototype schematic design is developed.
3. Presentation - The schematic is converted into a simple User Interface (ie GUI).
4. Feedback - After the team gets feedback from users, the protoype is reiterated.
5. Reiteration - Further changes/reiterations and presentations are made.
6. Consultation - The protoype is converted into a finished application.
7. Acceptance - Users review and sign off on their acceptance of the new software system.
8. Installation - The new software system (program) is installed on network servers and workstations.
9. Training - Group training.
Keep in mind it is important to use the roadmap in order. You may have the need to repeat steps but try to avoid it by being very thorough in each step. Use the right tools for the project. I like Microsoft Project (for project management), Microsoft Visio (for the schematics), Microsoft Infopath (for the feedback forms) - but whatever works for you.