Click here to Skip to main content

Design and Architecture

   

 
You must Sign In to use this message board. (secure sign-in)
 
Search this forum  
 FAQ
    Noise  Layout  Per page  Show 
  Refresh
GeneralRe: Data dictionary SQLServer versions PinmemberOChristiaanse20:06 29 Feb '12  
QuestionWPF and sqlserver 2008 express Pinmemberradhwane14:48 14 Feb '12  
AnswerRe: WPF and sqlserver 2008 express PinmvpRichard MacCutchan22:38 14 Feb '12  
AnswerRe: WPF and sqlserver 2008 express PinmemberPaul Conrad18:39 16 Feb '12  
AnswerRe: WPF and sqlserver 2008 express PinmvpAbhinav S20:27 20 Feb '12  
GeneralConclusion of drafting Solution&Design document Pinmemberaoe.Dylan20:24 12 Feb '12  
GeneralRe: Conclusion of drafting Solution&Design document PinmemberBernhard Hiller21:37 12 Feb '12  
When customers / sales people / product managers etc. request a change, they are not at all interested in code. They look at the functionality only. Such requirements often start with a headline only, it is then the duty of requirements engineering / product management to precisely describe the requested functionality, possibly with user stories. When appropriate, the description will show the differences to the present situation. Now you have a functional specification.
Next, development has to scrutinize the requested change, and see how the application has to be designed: which interfaces, classes are needed, how they are distributed between server and client, etc. They have to look at the present code and its re-usability. Now you have a technical specification, and you can estimate the efforts for development.
Of course, the "functional" guys may talk with the "technical" guys when they create their functional specification.
When you eventually develop the functionality, you'll document differences from the original plan.
With "big" projects, you'll start with the main functionality, and while the customers can already use that core functionality, more details will be added as outlined in the steps above.
GeneralRe: Conclusion of drafting Solution&Design document Pinmemberjschell13:45 14 Feb '12  
AnswerRe: Conclusion of drafting Solution&Design document Pinmemberaoe.Dylan17:43 16 Feb '12  
GeneralRe: Conclusion of drafting Solution&Design document Pinmemberjschell7:34 17 Feb '12  
QuestionOnline Learning Industry Pinmembermauricemcse13:53 3 Feb '12  
AnswerRe: Online Learning Industry PinmemberAlbert Holguin14:05 3 Feb '12  
AnswerRe: Online Learning Industry Pinmemberjschell10:00 4 Feb '12  
AnswerRe: Online Learning Industry PinmemberRobCroll11:33 5 Mar '12  
NewsMessage Automatically Removed PinmemberProEnggSoft20:21 29 Jan '12  
AnswerRe: Object Oriented Design Principles - IDEAL CHALK. Why I have voted to have this removed. PinPopularprotectorPete O'Hanlon20:35 29 Jan '12  
AnswerRe: Object Oriented Design Principles - IDEAL CHALK PinmvpAbhinav S20:38 29 Jan '12  
GeneralRe: Object Oriented Design Principles - IDEAL CHALK PinprotectorPete O'Hanlon21:56 3 Feb '12  
GeneralRe: Object Oriented Design Principles - IDEAL CHALK PinmvpAbhinav S22:35 3 Feb '12  
GeneralRe: Object Oriented Design Principles - MAY BE DELETED PinmemberProEnggSoft22:46 29 Jan '12  
GeneralRe: Object Oriented Design Principles - MAY BE DELETED PinmemberSimon_Whale22:55 29 Jan '12  
GeneralRe: Object Oriented Design Principles - MAY BE DELETED PinmemberProEnggSoft23:13 29 Jan '12  
QuestionArchitecture for mobile app Pinmembernitin_ion16:27 25 Jan '12  
SuggestionRe: Architecture for mobile app PinmemberRobCroll11:10 29 Jan '12  
QuestionMaking multiple teams coexist Pinmember_Zorro_4:21 23 Jan '12  

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.


Advertise | Privacy | Mobile
Beta | 2.5.120517.1 | Last Updated 22 May 2012
Copyright © CodeProject, 1999-2012
All Rights Reserved. Terms of Use
Layout: fixed | fluid