| View previous topic :: View next topic |
| Author |
Discovering the Top-Level System Diagram |
mabel
Joined: 28 Jan 2011
Posts: 4
|
 Posted: Wed Feb 02, 2011 2:01 pm Post subject: |
 |
|
Mr. Cuchulainn,
You are right here. This is really most important point in a software process. Not only OO but few little things are also complicated and can create process in-correction. SRP itself creates many issues which requires to be resolved correctly.
_________________
"Going High"
resume service |
|
| Back to top |
|
 |
Cuchulainn
Joined: 18 Dec 2006
Posts: 501
Location: Amsterdam, the Netherlands
|
| Posted: Thu Sep 20, 2007 9:19 pm Post subject: |
|
|
The Parnas Decomposition Principle
http://sunnyday.mit.edu/16.355/parnas-criteria.html
| Quote: |
We have tried to demonstrate by these examples that it is almost always incorrect to begin the decomposition of a system into modules on the basis of a flowchart. We propose instead that one begins with a list of difficult design decisions or design decisions which are likely to change. Each module is then designed to hide such a decision from the others. Since, in most cases, design decisions transcend time of execution, modules will not correspond to steps in the processing. To achieve an efficient implementation we must abandon the assumption that a module is one or more subroutines, and instead allow subroutines and programs to be assembled collections of code from various modules.
|
|
|
| Back to top |
|
|
Cuchulainn
Joined: 18 Dec 2006
Posts: 501
Location: Amsterdam, the Netherlands
|
| Posted: Thu Sep 20, 2007 9:18 pm Post subject: |
|
|
Single Responsibility Principle (Cohesion)
http://en.wikipedia.org/wiki/Single_responsibility_principle
| Quote: |
In computer science, the single responsibility principle was introduced by Tom DeMarco in his book Structured Analysis and Systems Specification, Yourdon Press Computing Series, 1979. It states that every object should have a single responsibility, and that all its services should be narrowly aligned with that responsibility. The principle forms part of cohesion, a concept widely used in software development.
|
Last edited by Cuchulainn on Thu Sep 20, 2007 9:21 pm; edited 1 time in total
|
|
| Back to top |
|
|
Cuchulainn
Joined: 18 Dec 2006
Posts: 501
Location: Amsterdam, the Netherlands
|
| Posted: Thu Sep 20, 2007 9:16 pm Post subject: Discovering the Top-Level System Diagram |
|
|
| This is the most difficult part of the s/w process. Using OO at this stage is too fine-grained. That's why we have to go to the 70's. |
|
| Back to top |
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
FAQ 
Search 
Memberlist 
Usergroups 
Register 
Profile 
Log in to check your private messages 
Log in 
