Software Quality ManagementUnit – 3

G. Roy Antony Arnoldy yAsst. Professor / CSE 

GRAA

• Computer‐Aided Software Engineering (CASE)Computer Aided Software Engineering (CASE) is the scientific application of a set of tools and methods to a software system which isand methods to a software system which is meant to result in high‐quality, defect‐free, and maintainable software productsand maintainable software products.

• CASE tools automate methods for designing, documenting and producing structureddocumenting, and producing structured computer code in the desired programming llanguage.

GRAA

• Architecture Management– Model, design, and rapidly build Software, Systems, and Computer Application Programs.

• Change and Release Management• Change and Release Management– Improve software delivery and lifecycle  traceability, from requirements through deploymentrequirements through deployment.

• Software Development Management– Align projects for improved productivity and predictabilityAlign projects for improved productivity and predictability.

• Quality Management– Ensure software functionality, reliability and performanceEnsure software functionality, reliability and performance throughout development and production.

GRAA

• CASE software supports the software process activities such as requirement engineering, design, program development and testing. 

• Therefore, CASE tools include design editors, data dictionaries, compilers, debuggers, system building tools, etc.

• The term CASE was originally coined by software g y ycompany Nastec Corporation of Southfield, Michigan in 1982 with their original integrated g g ggraphics and text editor GraphiText

GRAA

• Supply basic functionality, do routine tasks pp y y,automatically– Be able to support editing of code in the particular programming language, supply refactoring tools

• Enhance productivity– Generate code pieces automatically

• Increase software quality• Intuitive use• Integration with other toolsg

– For example, code editor works with code repository

GRAA

• They classified as Upper, Lower and Integrated CASE tools.• Upper CASE Tools support strategic planning and construction

of concept‐level products and ignore the design aspect, suchas ER diagrams, Data flow diagram, Structure charts,Decision Trees, Decision tables, etc. E.g. ExceleratorL CAS l h b k d i i i f• Lower CASE Tools concentrate on the back end activities ofthe software life cycle, such as physical design, debugging,construction testing component integration maintenanceconstruction, testing, component integration, maintenance,reengineering and reverse engineering. E.g. Telon

• Integrated CASE Tools aim to support the whole developmentIntegrated CASE Tools aim to support the whole developmentcycle. E.g. IEF (Information Engineering Facility)

GRAA

Requirement Analysis System Design Coding Testing Operation & 

Maintenance

Integrated CASE Tools (ICASE)

e.g. IEF

Upper CASE / Front End Lower CASE / Back End

e.g. Excelerator e.g. Telon

Upper CASE Mid CASE Lower CASE / Back End

GRAA

• It is also called as front end CASE ToolsIt is also called as front end CASE Tools• They assist in requirement analysis & design• They may be tied to a specific methodology or may allow the use of the user’s ownmay allow the use of the user s own methodology.E l• Example: 

• These tools are associated with analysis and ydesign methodologies such as SAM or SSADM

GRAA

• The typical responsibilities of an UpperCASE Tool are to support the following tasks:– Requirement Analysis:

• Application Visioning• Application Visioning• Requirements Reuse• Requirements IdentificationR i A l i• Requirements Analysis

• Requirements Specification– Design:g

• Design Production• Design Refactoring• Design ReuseDesign Reuse• Design Documentation

GRAA

• These tools are concerned with theThese tools are concerned  with the implementation stages of the lifecycle, typically coding testing and documentationtypically coding, testing and documentation.

• They aim to increase the reliability, adaptability and productivity of the delivered code.code.

• 4GLs may be considered as back‐end CASE T l h T lTools, such as Telon.

GRAA

• The typical responsibilities of a LowerCASE Tool is The typical responsibilities of a owerCAS Tool isto support the performance of the following tasks: – Implementation: 

• Implementation Reuse• Programming• Debugging

– Integration Tasks: • Integration PlanningC t I t ti• Component Integration

• Integration Reporting

GRAA

• Aim to support the whole development cycleAim to support the whole development cycle and are linked to specific methodologies.

• They are often complex and expensive but• They are often complex and expensive, but offer the developer the greatest integrity of all approaches through the use of a single dataapproaches through the use of a single data encyclopaedia throughout the lifecycle. 

( f• Example: IEF (Information Engineering Facility), IEW (Information Engineering Workbench)

GRAA

• Help standardization of notations and diagrams p g• Productivity increases• Help communication between development teamHelp communication between development team members

• Automates the methodology – this improves gy pconsistency, but restricts creativity.

• Reduction of time and effort• Automated tools are provided to prepare documentation

• Complexity of maintenance decreases.

GRAA

• Cost Increases: Costs for purchase + trainingCost Increases: Costs for purchase + training• Expertise needed• Training issues• Not mapping to current methods or• Not mapping to current methods orapplications.

• May lead to restriction to the tool’scapabilitiesp

• Limitations in flexibility of documentation

• Common CASE risks and associated controlsCommon CASE risks and associated controls include:

I d d di i– Inadequate standardization– Unrealistic expectations– Slow implementation– Weak repository controlsWeak repository controls

GRAA