How can I componentize an existing software system in terms of its specific functionality characteristics and make it reusable component for further reuse to save time and cost.
Any generic architectural model can address this problem, and if yes, then what are your suggestions and expectation from such generic model?
There are a large number of componentizing models available. Some from Microsoft, others from Unix, and many more. For example: OLE, COM, .Net, Unix modularity, POSIX (weak example), and many built upon those, too numerous to list. Each of these is highly specific, imho.
If you have need of a 'new' system, look up IDEF modeling specifications. Very hard to learn them. But worth knowing about, even if one does not master them. These specs were designed to model abstractions, concepts and details, of anything. Some you can not learn from a book, and must have an expert teacher, for a half year.
If you need a model for a specific purpose, a project you have in mind, then best supply some details.
Dear Gopal,
it is widely regarded that there is no silver bullet for component oriented software architecture. Each piece of software needs to be looked at individually. Your approach should depend on the type of software. It makes a difference wether it is a webapp or an industrial software. Unfortunately, there is no generic pattern or framework that suits all types of software. SOA and MVC architectural patterns are suitable for web applications but not necessairily for for non-web applications. My recommendations for further reading are "Software Engineering with Reusable Components" by J. Sametinger and "Component-Based Software Engineering: Putting the Pieces Together" by Heinemann and Councill. In your case it might be useful to look at the different functions as modules. Try to isolate logical tasks performed by your software and then separate them into modules.
Best regards,
Analyzing coupling and dependencies is a good starting point, if you wish to reuse existing code as much as possible. Depending on the language that the software is written, you may find various automated documentation tools, possibly producing charts of how variables and control is shared among functions. Completing such internal documentation should give you a sharp idea of how the system is structured.
You may also want to use a profiler, even if you are not going to optimize the system (yet). Performance analysis gives you a dynamic counterpart of control coupling.
- Badges
- Science topic
- Similar topics
- Computer Science and Engineering
- Computer Software