CIS 375 SOFTWARE ENGINEERING

University Of Michigan-Dearborn

Dr. Bruce Maxim, Instructor

CASE Tools:

    1. Analytic tools.

      2. (used during software development)

    2. Which assist in development and maintenance of software.

Upper CASE (Front-End Tools):

Lower CASE:

taxonomy of CASE tools:
    1. Information engineering tools.
    2. Process modeling and management tools.
    3. Project planning tools.
    1. Cost / effect estimation.
    2. Project scheduling tools.
    1. Risk analysis tools.
    2. Project management tools.

      3. (Monitor project & maintain management plan)

    3. Requirements tracing tools.
    4. Metrics & management tools.
    5. Documentation tools.
    6. System software tools.
    7. Q.A. tools.
    8. Database management tools.
    9. Software configuration management tools.
    10. Analysis & design tools.
    11. PRO / SIM tools.
    12. Interface design tools.
    13. Prototyping tools.
    14. Programming tools.

      15. (Compilers, editors, etc.)

    15. Integration & testing tools.
    16. Static analysis tools.
    17. Dynamic analysis tools.
    18. Test management tools.
    19. Client/server testing tools
    20. Reengineering tools

"Life Cycle" CASE:

("integrated" CASE = I-CASE)

I-CASE Environment:
    1. Mechanism for sharing SE information among tools.
    2. Tracking change.
    3. Version control & configuration management.
    4. Direct access to any tool.
    5. Automating the work breakdown that matches tools.
    6. Support communication among software engineers.
    7. Collect metrics & management.

Integration Architecture:
    1. User interface layer.
    2. Tools management services (TSM).
    3. Object management layer.
    4. Shared responsibility layer (CASE database)

Case Repository (DB) In I-CASE:

Role:
    1. Data integrity.
    2. Information sharing.
    3. Data /tool integration.
    4. Data /data integration.
    5. Methodology enforcement.
    6. Document standardization.

Content:
    1. Problem to be solved.
    2. Problem domain.
    3. Emerging solution.
    4. Rules pertaining to software process methodology.
    5. Project plan.
    6. Organizational content.

DBMS:
    1. Non-redundant data storage.
    2. Data access at high level
    3. Data independent.
    4. Transaction control.
    5. Security.
    6. Ad hoc queries & reports.
    7. Openness (import/export).
    8. Multi-user support.