Senin, 21 Oktober 2024

Case Tools

Components of CASE Tools

  • Central Repository CASE Tools: A central repository is required by the tools to serve as a common source of integrated and consistent information. The central place of storage consisting of specifications of product, documents requirement, diagrams and reports and information about the management is a central repository.  The central repository also acts as a data dictionary.
  • Upper CASE Tools ( U-Case Tools ): Planning, requirement analysis, system modelling and high-level designing of different stages ( early stages ) of the software development life cycle can be performed using upper case. Examples of U-CASE tools include IBM Rational Rose, Sparx Systems Enterprise Architect, and Microsoft Visio.
    • Requirements Modeling Tools for capturing, organizing, and visualizing software requirements using techniques like :
      • Use Case Diagrams;
      • Entity-Relationship Diagrams
    • Diagramming Support for creating various diagrams, including :
      • Data Flow Diagrams, 
      • Entity-Relationship Diagrams,
      • State Transition Diagrams.
    • Modeling Languages: U-CASE tools often support modeling languages such as Unified Modeling Language (UML) for system modeling and design.
  • Lower CASE Tools ( L-Case Tools ): Implementation, testing, and maintenance ( later stages ) can be performed using lower case. Examples of L-CASE tools include Microsoft Visual Studio, JetBrains IntelliJ IDEA, and Git for version control.
    • Code Generation or Source Code Editor or IDE ( Integrated Development Environmet ) or Rapid Application Development Tools : Tools that automatically generate code based on design specifications or models, reducing manual coding efforts.
    • Source Code Management: Support for version control, change tracking, and collaborative development by multiple developers.
    • Debugging and Testing: Tools that aid in code debugging, unit testing, and code quality analysis.
  • Integrated: All the stages of the software development life cycle right from the gathering of requirements for testing and documentation can be performed using integrated tools.
  • CASE Management Tools:
    CASE management tools focus on project management aspects, including scheduling, resource allocation, version control, and documentation management. They help teams coordinate their efforts and ensure that projects are delivered on time and within budget. Key functionalities of CASE management tools include:
    • Project Planning: Tools for creating project plans, defining tasks, estimating resource requirements, and setting project milestones.
    • Document Management: Features for managing project documentation, including version control, document tracking, and access control.
    • Workflow Automation: Automation of workflow processes, such as code reviews, approvals, and change management.
    • Examples of CASE management tools include Microsoft Project, Atlassian Jira, and Redmine.
Top 13 Types of CASE Tools
  1. Diagram Tools:
    The components of the system, data flow, control flow and the structure of the system can be represented in graphical form using diagram tools.
  2. Process Modeling:
    The software process model can be created using process modelling tools for software development. The managers can choose a process model using process modelling tools or make modifications depending upon the software product requirements.
  3. Project Management
    Planning of the project, estimation of cost and efforts, scheduling of project and organizing of resources can be done using project management tools.
  4. Documentation Tools
    Before the beginning of software process, documentation of the software project must begin. This documentation must cover the all the software development life cycle phases and the completion of the software development phase as well. The documents are generated by the documentation tools for both technical and end users. The in-house professionals in the development team who refer the manual maintained for the system, manual maintained for reference, manual for training, manuals for installation etc. is described in the technical users documents. The functioning of the system and how system works is described in the end user documents.
  5. Analysis
    Requirements gathering, inconsistency checks, diagrams inaccuracy, redundancies in the data etc. can be checked using analysis.
  6. Design
    The block structure of the software can be designed by the software designers using design tools which are again broken down into smaller modules using techniques of refinement. The detailing of every module and the interconnections between the modules can be done using this.
  7. Configuration Management Tools
    Whenever one version of software instance is released, configuration management tools deals with the following:
    • Management of revision and version.
    • Configuration management of baseline.
    • Change control management.
    Automatic tracking, management of version, and management of release can be done with the help of configuration management.
  8. Change Control
    Change Control are a part of configuration management. The changes that occur in the software after fixing its baseline or after the first release of the software are dealt by change control tools. Tracking the changes, management of files, management of codes etc. can be automated using change control. The change policy of the organization can be enforced by using change control.
  9. Programming
    The programming environments like integrated development environment , library consisting of in built modules, simulation are all included in programming tools. The development of software product is aided by these and simulation and testing features are included.
  10. Prototyping
    The simulated version of the software product to be built is called a prototype in software. The look and feel of the product is provided by the prototype and several aspects of the actual product can be simulated using prototyping. Graphical libraries are contained in the prototyping tools. User interfaces and design that are hardware independent can be created using prototyping. Rapid prototypes can be built using prototyping based on the existing information. The software prototype can be simulated using prototyping tools.
  11. Web Development
    The web pages like forms, text, script, graphic etc. can be designed using web development tools. The web page that is being developed can be previewed to see how it looks after completion using web development.
  12. Quality Assurance
    Monitoring the engineering process and methods used for software development to ensure the quality is as per the standards of the organization can be performed using quality assurance tools. The configuration change control and software testing tools come under the category of QA tools.
  13. Maintenance
    If there are any modifications after the delivery of the software product can be done through software maintenance tools. Techniques for automatically logging, error reporting, generation of error tickets automatically and root cause analysis are used in the maintenance phase of the software development life cycle to help the software organizations.


Related Post

Tidak ada komentar:

Posting Komentar

Various Other Posts