Abstract
The paper addresses the acquisition, organisation and reuse of knowledge in the design of real-time software systems. Experiences from capturing and making explicit software design alternatives and their selection criteria are evaluated. Generic, software design task-specific and domain-specific types of knowledge are discussed and illustrated using real-life design examples. A prototype of a CASE tool is also described, which incorporates a repository of reusable software components as a source of design alternatives and assists a designer both in selecting them and in analysing the results.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
