Technical Specifaction

Road Runner
05-17-2002, 03:14 AM
Hi all

im starting a new project soon and i have to plan it out by doing a "Technical Specifaction". As far as i know this just means how you navigate through the forms and what tables each form is using.

Thing is i have never done anything like this before and i was wondering if anyone had a template or a sample "Technical Specifaction" that i could look at to help get me started.

Any help appricated.

Thanx
Shane
:)

Banjo
05-17-2002, 03:28 AM
Interface layout and the reasoning behind is important. However, more important are the critical algorithms that you will be using, how the various code modules link together and interact, how data flows through the app and how error conditions are to be handled.

Thinker
05-17-2002, 07:52 AM
Technical specifications would include all sorts of things that you
really shouldn't know until your design phase is almost complete.
Like database layouts and the things that Banjo mentioned.

According to the MS model for Solution Architectures, you should...
1. Analyze the Business Requirements
2. Define the Technical Architecture
3. Develop a Conceptual and Logical Design
4. Develop the Data Models
5. Design User Interface/User Services
6. Derive the Physical Design

Road Runner
05-17-2002, 08:03 AM
Thanks for the replies Thinker + Banjo:)

I have a better idea at what im at now.

EZ Archive Ads Plugin for vBulletin Copyright 2006 Computer Help Forum