Friday, March 21, 2014

undefined undefined

Component Based Software Engineering

No comments
  • Emphasizes the design and construction of computer based systems using software “components”.
  • The process relies on reusable software components.
  • Similar to the characteristics of the spiral model.

    • Requirement specification and validation steps are similar to the other processes.

    Component Analysis

    During this stage try to find the software components need for the implementation once the requirements are specified.

    Requirements Modification

    Analyze the discovered software components to find out whether it is able to achieve the specified requirements.

    System Design with Reuse

    The frame work of the system is designed to get the maximum use of discovered components. New software may have to design if the reusable components are not available.

    Development and integration

    Software that cannot be discovered is developed, and the reusable components are integrated to create the new system. The integration process, may be part of the development process rather than a separate activity.


    Related Posts:

    • Problems of software development Large software is usually designed to solve 'wicked' problems. Software engineering requires a great deal of coordination across disciplines.      -Almost infinite possibilities for design trade-offs acro… Read More
    • Problems with the Waterfall Model Real projects rarely follow the sequential flow that the model proposes. Although the Waterfall model can accommodate iteration, it does so indirectly. It is often very difficult for the customer to state all requirements ex… Read More
    • Throw away Prototyping The objective is to understand the system requirements clearly.Starts with poorly understood requirements. Once the requirements are cleared, the system will be developed from the beginning.This model is suitable if the req… Read More
    • Waterfall model Software Requirement Analysis and Specification The system’s services, constraints and goals are established with the consultation with the users. This would include the understanding of the information domain for the sof… Read More
    • Evolutionary Prototyping Advantages Effort of prototype is not wasted. Faster than the Waterfall model. High level of user involvement from the start. Technical or other problems discovered early – risk reduced. A working system is available ear… Read More

    0 comments:

    Post a Comment

    Subscribe to: Post Comments (Atom)
    Copyright © 2025 Software Engineering Fundamentals | Powered by Blogger
    Design by N.Design Studio | Blogger Theme by NewBloggerThemes.com